scribbled :
Quote:>Have customer who has been using SCO Unix V/386 R 3.2 V4.2 for several
>years on a system with a 300Meg hard drive. Time to upgrade to a 1 to 2
>Gig hd.
>System seems to load fine with correct parameters etc. However, when
>system reboots
>first time I get "NO OS" and it hangs. Can anyone tell me what update
>this system needs
>for the OS to deal with larger hard disks?
"NO OS" means that the boot loader can't find the system files. Because
the boot loader is accessing the system files hdboot0, hdboot1 and boot
in that order (I think, please correct me) through the BIOS, they must
be below the 1024th cylinder on the hard drive. If they are not, the
BIOS can't find them, returns an error to the bootstrap, and so there
appears to be 'No OS'.
Solution: create two partitions: one =< 1000 cyl to boot from, and then
another for data. E-Z if you read the first, this was even mentioned in
the Xenix docs I was reading about 6 hours ago :)
Message to SCO : less cryptic MBR messages please: I know that BAD TBL =
"invalid partition table (nuked data or bootable flag incorrect), NO OS
= no code where there should be code, but what's CYL OVF? Would that
happen if PART of the boot structure was stashed after the 1023rd
cylinder?
In addition, if the drive size is ~2Gb, you might (will?) need a patch
for the kernel, as OpenServer does.
--
UNIX - Saving you from the Gates of Hell.