From: "Al Puzzuoli" <alpuzz@comcast.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: instalation problem-- was Re: fc3 download
Date: Sat, 26 Feb 2005 23:43:16 -0500 [thread overview]
Message-ID: <002301c51c86$db091c90$6900a8c0@systemax> (raw)
In-Reply-To: <20050227031020.GA29510@romuald.net.eu.org>
Interesting. What I know for sure based on sighted assistance is that if I
attempt to boot disk 1, the text "boot from CD" flashes for a few seconds,
and then the system falls back to booting Windows. My first thought was
that my boot sequence was messed up, but the boot.iso works just fine.
Weird.
If I have the same problem with disk 1 of the regular set, maybe I'll try
booting it from the other rom on this machine to see if it makes a
difference.
--Al
----- Original Message -----
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, February 26, 2005 10:10 PM
Subject: Re: instalation problem-- was Re: fc3 download
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I seem to recall that there were posts some time back on the list
> indicating that disc1 of fc3 didn't boot on some machines, and did
> boot on others. So, it maybe that there's nothing wrong with John's
> images, and your machine may be one of those that won't boot the first
> disc. Perhaps someone using fc3 who posted on this earlier, or knows
> something about the problem will clarify this.
>
> Greg
>
>
> On Sat, Feb 26, 2005 at 09:15:07PM -0500, Al Puzzuoli wrote:
>> Hi john,
>>
>> Again, thanks very much for posting these and allowing those of us on the
>> list access to them. At this point though, I think I'm going to download
>> the regular FC3 isos and do a BRLTTY install. I'll worry about speakup
>> after the fact. At this point, I think this will be the quickest
>> solution.
>>
>> If you get a chance though, you might want to check your disk 1 image, as
>> there seems to be a problem in that it isn't bootable for some reason.
>> As
>> I said, I downloaded several images from your site and several from the
>> main ftp site. However, the sum of disk1 didn't match the one on the
>> main
>> ftp so I'm assuming I got that one from you.
>> The sum of the one i have that isn't booting is:
>> d016692cfde7456c6ca021b879833903
>>
>>
>> Thanks again,
>>
>> --Al
>>
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFCIToc7s9z/XlyUyARAkV+AJ0a6DMYcv0gJvwHDlS9zxGRjov1BACZAVFi
> yWmcg8jrBOj/+HQca641yP8=
> =2UiC
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
Juan Hernandez
` John McCann
` instalation problem-- was " Al Puzzuoli
` Janina Sajka
` Al Puzzuoli
` Janina Sajka
` Sina Bahram
` Al Puzzuoli
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Janina Sajka
` Sina Bahram
` Al Puzzuoli
` Janina Sajka
` John McCann
` Al Puzzuoli
` John McCann
` Gregory Nowak
` Al Puzzuoli [this message]
` Janina Sajka
` Janina Sajka
` Sina Bahram
` Janina Sajka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002301c51c86$db091c90$6900a8c0@systemax' \
--to=alpuzz@comcast.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).