OK, a bit perplexing.
Acquired an IBM Inttellistation (6889-11U) with dual P2-400's.
Old, yeah but free and will use it as a test machine, storage, back-up...

Upped the BIOS to the latest, loaded Win2K server and everything was
cool.
Re-booted and still good. Then a re-boot and "No OS found" error.
For kicks and giggles bought a Maxtor 200GB drive with an ATA/133
card.
Loaded the OS (XP) and all was good, re-booted and still good.
Re-booted later and again "No OS found".
Any complete and through places to look for answers (Maxtor site is
not helpful) or things to try?
thanks in advance!!
creature@techie.com

---

Clarification of Question by creature2-ga on 20 Jun 2003 20:06 PDT

thanks for the suggestion but in my former life I was a lot more hands
on and made sure that this was not the case.....

Make sure you don't have a diskette in the diskette drive.  That's
often been the cause of this problem in my experience.

Are you booting off of the ATA card?  If you are, check your bios
settings each time you reboot and see if they revert back to default. 
This would cause the problems you are seeing and if this is the case,
you will need to replace the battery on the motherboard.  This is what
stores your settings while the computer is off.  If you aren't booting
off the ATA card, try fdisking the master boot record of your hard
drive (which *will* blow away your OS, so make sure you have a backup
of anything you need).  This command, from a DOS prompt, is fdisk
/mbr.  Reinstall the OS and see how it goes.  Chances are, however,
that the battery on your motherboard is dying.

thanks, that may be it but will find out after trying a new battery...

Ran fdisk /mbr earlier in this science project and am booting from the
ATA card. There is nothing on this drive *yet* that I can't replace,
just OS.

I have a strong feeling that the data in the Win2K boot loader file
(boot.ini?) isn't being written properly.  On your install/reboot the
first time, I don't think this file is being consulted; on the second,
perhaps it is.  If it is being written properly, it's probably
incorrect, referencing wrong drives and partitions for the booting
data on the HDD.

make sure to set an active partition when fdisking

Thanks for the help, once I swapped in a new battery for the CMOS I've
loaded OSes and generally did what I wanted, re-booting as needed and
running strong.

Gonna close this string, appreciate this info channel!!
Creature