Sys V/386 R 3.2 V 4.2 harddisk

Sys V/386 R 3.2 V 4.2 harddisk

Post by stefan » Sat, 09 May 1998 04:00:00



To Anyone who can help....

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?

Thanks

 
 
 

Sys V/386 R 3.2 V 4.2 harddisk

Post by James MacDonal » Tue, 12 May 1998 04:00:00



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.

 
 
 

Sys V/386 R 3.2 V 4.2 harddisk

Post by Bela Lubki » Wed, 13 May 1998 04:00:00



> 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?

Probably uod429a.
Quote:>Bela<

 
 
 

1. FS: SCO UNIX Sys V/386 Dev. Sys Release 3.2

SCO UNIX System V/386 Development System, with all manuals, media,
registration cards and activation keys. This is Release 3.2.2,
designed to be installed on Version 2.0 of the SCO UNIX System V/386
Release 3.2 Operating System. Date on Registration card 05/07/91.

All manuals are still shrinkwrapped and the volumes are:
* C Language Guide
* Library Guide
* Programmer's Guide
* Programmer's Reference
* Device Driver Writer's Guide
* Developer's Guide
* CodeView/MASM
* CGI
* ISAM User's Reference
* Product Engineering Toolkit Guide

Media appears to be 5.25" only. 2 pink unfilled registration cards with
attached activation keys are included. Release notes and license agreement
are also present. Package appears to be complete.

Asking $49 + sh. (bulky because of the documentation)
Prepay only. US buyers only please.


2. XFree86 modeline for Hitachi 4419D monitor

3. configuring high speed modem on SYS V/386 Rel 3.2

4. XFree402-hang-up

5. screen slower on Redhat 5.1 on P-90 than 4.2 on a 386

6. can you help me on syscall?

7. Disaster Recovery on V/386 rel 4.2

8. HACMP SYNCRONIZATION

9. INTERACTIVE UNIX System V/386 Release 3.2, Version 4.1

10. TCP/IP Stack for SCO Unix V/386 Release 3.2?

11. uupc connection to Altos UNIX System V/386 Release 3.2

12. Tape labels on SCO UNIX System V/386 Release 3.2

13. SCO Unix System V/386 Release 3.2 TCP/IP Stack?