HELP, Please!?!

[kar74]

Our Gateway PC is on the fritz and we’re not sure why. When we try to
reboot we get this message:

PXE-MOF: Exiting PXE ROM.
No bootable device - insert boot disk and press any key.

I tried to reinstall Windows XP but it didn’t work. It’s almost like
the computer isn’t recognizing the C drive?!?

Any help would be GREATLY appreciated!

Thank you in advance!

~kar

 

[Grinder]

Our Gateway PC is on the fritz and we’re not sure why. When we try to
reboot we get this message:

PXE-MOF: Exiting PXE ROM.
No bootable device - insert boot disk and press any key.

I tried to reinstall Windows XP but it didn’t work. It’s almost like
the computer isn’t recognizing the C drive?!?

That does sound like it's the case.

Hopefully, though, there's just some craziness going on with the Boot
order as defined in your BIOS. This thread:

http://209.59.143.50/showthread.php?t=41235

....suggests that the error messages you are seeing are from a failed
attempt to boot from a network source.

Check the boot order in your BIOS to insure that the hard drive is
fairly high in the list. Generally, I have it something like this:

(1) Floppy Drive
(2) CD-ROM
(3) Hard Drive

If you do this, will it boot from the hard drive?

Will it boot from a bootable CD?

 

[kony]

Our Gateway PC is on the fritz and we’re not sure why. When we try to
reboot we get this message:

PXE-MOF: Exiting PXE ROM.
No bootable device - insert boot disk and press any key.

I tried to reinstall Windows XP but it didn’t work. It’s almost like
the computer isn’t recognizing the C drive?!?

Any help would be GREATLY appreciated!

Thank you in advance!

~kar

Use the hard drive manufacturer's utility (which makes a
boot floppy), available for download from the respective
website, to check the hard drive.

It's possbile for a bios settings change to produce the
result you're seeing, but if you hadn't touched the bios
settings it is more likely a drive problem, though
occasionally a general system instability (like bad power or
overheating CPU) can foul up the startup sequence if not
elsewhere... but if you had turned on the system from being
off for awhile that's probably not the problem.