Red Hat Bugzilla – Bug 83086
Can't install with XP on Compaq 5700t
Last modified: 2007-04-18 12:50:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; T312461)
Description of problem:
When booting from floppy created using rawrite, get "boot failed: please
change disks and press a key to continue". There is no other disk and when
pressing any other key to continue, just repeats.
BIOS does not allow booting from CD.
Tried creating a floppy on a win2000 machine and was able to boot OK.
Therefore, I assume the install CD's are OK.
I'm assuming the problem is with XP on this particular computer, as I've heard
others installing OK with XP.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot into a DOS start up disk
2. create boot floppy using rawrite
3. reboot machine
4. comes to Linux boot prompt
5. hit return key
Actual Results: error noted above appears
Expected Results: start install process
You are saying the Red Hat Linux boot floppy which boots into the installer fine
on another machine will not on the compaq?
I did not try the boot disk created on my Compaq on another machine. I
created a new boot disk on my Win 2000 machine at work and was able to boot
into it on that machine. The one created on the 2000 machine would not boot
on my Compaq either.
Did you run rawrite from 'MSDOS mode'? I am not sure it will work if you are in
the windows GUI environment.
I boot into MS-DOS using a Win 98 boot disk that boots to an ms dos prompt and
use rawrite from there.
I do not know of any problems using rawrite with a Win98 based boot floppy.
You may want to try different media because I know I have had problems with bad
floppy media before.
Tried several different floppies. No go! As stated earlier ... I suspect
it's related to this particular model OR an issue with the BIOS. I'm truly at
a loss of where to go now.
Have you tried Red Hat Linux 8 yet?
Have not tried 8.0. Got 7.3 because star office was part of the package.
I cannot think of anything else to try at this point. It appears to be an issue
with your particular system as we do not see this problem ourselves.