boot error: non-system disk

[news.verizon.net]

hello

Since installing xp-home full, from time to time I'm seeing a "non-system
disk error"

I formatted, did a complete install

384M RAM
Intel 700mhz
20 gig primary drive
6 gig secondary

Set bios first at floppy boot, then c boot. Problem still occurs.

After 3 or 4 attempts, computer boots fine

I checked all cables, etc.

Any suggestions?

Thanks

Jo-Ellen

 

[Guest]

Take the floppy disk out of the drive?

 

[news.verizon.net]

There is no disk there.

Take the floppy disk out of the drive?

 

[David Candy]

It means your hard drive is about to fail. Backup your data now. Should have had a floppy in the driuve, it's cheaper.

 

[Robo-wolf]

When you set your bios. Check all the settings, read the
explainations so you can tell if they apply to you, when I
did this and followed the guide at the bottom of the
screen, the Windows xp booted itself, Remember to partion
the HDD if needed

 

[news.verizon.net]

Thanks . I'll try that.

Jo-Ellen

When you set your bios. Check all the settings, read the
explainations so you can tell if they apply to you, when I
did this and followed the guide at the bottom of the
screen, the Windows xp booted itself, Remember to partion
the HDD if needed

 

[Alex Nichol]

Since installing xp-home full, from time to time I'm seeing a "non-system
disk error"

I formatted, did a complete install

384M RAM
Intel 700mhz
20 gig primary drive
6 gig secondary

Set bios first at floppy boot, then c boot. Problem still occurs.

After 3 or 4 attempts, computer boots fine

This is happening way before XP gets a look in.

Either:

You have a boot sequence of Floppy first and have a data (non-bootable)
floppy in the drive (but I don't think things would get tired of looking
and eventually go to the HD) or else

The initial attempt by the BIOS to access the HD and hence find
something to boot is failing - probably because it has not given the
drive long enough to run-up. Two things might help, by giving more time
- set the BIOS *not* to use a Quick POST check, so it then goes and
counts through all of RAM; and set the boot order to *be* floppy first,
so it goes looking for one, taking time to do so