Images on the OSR 5 CD

  • Creating Installation Boot Floppy Disks
  • Adaptec 2940 driver
  • On the 5.0.2 CD

    Creating Installation Boot Floppy Disk

    Your SCO OpenServer product distribution probably included a floppy disk to boot from for product installation. If, somehow, that disk has been lost or damaged, there is an image of it on the CDROM that can be used to create a new boot floppy.

    To create a floppy disk for installing SCO software, you can copy the media image to formatted floppy disk using the dd(C) command.

    The boot image is in the /images/boot/ directory on the CD-ROM.

    Assuming you have mounted the CDROM on /mnt and your 1.44MB floppy drive is the first drive on the controller:

    1. To make an operating system boot floppy disk, enter this command:

        dd if=/mnt/images/boot/N00 of=/dev/rfd0

    2. The directory that contains the image file also contains a file with the checksum for each floppy disk. Use this to verify the checksum of the floppy disk that you make. For the operating system boot floppy disk, the output of the command

        sum -r /dev/rfd0

      should match the contents of the file /mnt/images/boot/sums.

    If you only have access to a MSDOS machine you can use the rawrite utility in tls096.zip to generate the new disk.


    Resolving Adaptec alad driver conflicts

    If you have problems installing your system and you are using an Adaptec host adapter controlled by the alad device driver (for example, an Adaptec 2940 or 3940 series SCSI host adapter or an Adaptec 78xx series SCSI chipset on your motherboard), the alad driver might be conflicting with other peripherals or drivers. Try installing your system with an earlier version of the alad driver. To do so, create a new boot diskette:

    1. Insert a blank floppy into your diskette drive.
    2. Enter:
         mount /dev/cd0 /mnt
         cd /mnt/images/alad
         dd if=N00 of=/dev/rfd0 bs=18k conv=sync
         umount /mnt
    3. Verify that the image was correctly copied:
         sum -r /dev/rfd0
         sum -r N00
      The numbers in the left-hand column should be the same.
    4. Reinstall your system using the new boot diskette instead of the N0 diskette you originally used.

    After installation, if your system hangs while booting (in particular, during the hd_config phase of the boot), try removing the current alad driver and reinstalling an earlier version. To do so, boot a UNIX(R) kernel that does not experience this hang (for example, unix.old or unix.install), and install the older version of the alad driver by entering:

       mount /dev/cd0 /mnt
       cd /etc/conf/pack.d/alad
       mv Driver.o Driver.o.orig
       mv space.c space.c.orig
       cp /mnt/images/alad/Driver.o .
       cp /mnt/images/alad/space.c .
       cd /etc/conf/cf.d
       ./link_unix -y
       umount /mnt

    Images on the OSR 5.0.2 CD

    The are several disk images on the 3.2v5.0.2 cdrom. The bottom of /readme.txt contains instructions for creating the boot disk and the BTLD (AHS 5.2) disk.

    /images/ahsbtld AHS 5.2 BTLD disk image.
    /images/boot 3.2v5.0.2 N00 boot disk image.
    /images/ipxspx NVT.EXE Novell Virtual Terminal.
    /images/nuc Two disks for NUC (Netware Unix Client) NLM's for Novell 3.1x and 4.0 and a bunch of goodies (TELNETD.NLM).

    Trick: If you want a directory listing of what's inside these msdos disk images, run:

    	cd /mnt/images/nuc
    	/usr/bin/dosdir 01		(01 is the name of the image file)
    	/usr/bin/dosdir 01:/SYSTEM/*	(SYSTEM is a subdirectory)
    Also, you can identify disk image types with:
    	cd /mnt/images/nuc
    	/bin/dtype 01

    Comments and suggestions always welcome -