SCO Free OSR5 IDE and ATAPI CDROM Installation Instructions.

by Jeff Liebermann at http://www.cruzio.com/~jeffl/sco/ide.htm

V1.10 Mon Feb 17 18:00:00 PST 1997
SCO Free OSR5 IDE and ATAPI CDROM Installation Instructions.
This is NOT an official SCO document.  I don't work for SCO.
Ver 1.10 

(Section numbers will be assigned when I get this organized)
=> Introduction [Optional]
=> Buzzwords [Optional]
=> Hardware that works:
=> Hardware that doesn't work:
=> Hardware that you may have trouble with:
=> Hardware that you will have trouble with:
=> Where to look for hardware updates:
=> Minimum RAM and diskspace.
=> The Documentation  [Mandatory]
=> Installation and Release notes [Gotcha]
=> Licencing  [Mandatory]
=> MSDOS utilities partition  [Optional]
=> Existing partitions and different operating systems  [Optional]
=> Primary Secondary Master and Slave  [Manditory]
=> Complex boot strings. [Optional]
=> BTLD  (Boot Time Loadable Drivers).
=> Which boot drive?
=> Bogus BIOS battles.
=> Examples of boot strings and IQM.
=> OpenServer 5 Installation  [Mandatory]
=> Potential Problem with News [Advisory]
=> OSR5 Configuration [Advisory]
=> Shutdown and Reboot Cerimony [Mandatory]
=> Hardware Suppliment Installation [Mandatory]
=> Development System (C Compiler) Installation [Optional]
=> Layered Products Installation [Optional]
=> Libraries and fixes [Don't Install]
=> Licencable Products [Optional]
=> Client (Windoze) Demo Software Installation [Optional]
=> Skunkware 96 Usenet Ported Code Installation [Optional]
=> How do I ...?
=> Useful URL's [Optional]
=> Revision History.

=> Introduction [Optional]

This document deals with Free Open Server 5 (OSR5) 3.2v5.0.2
as supplied on CDROM with 2ea floppy disks (boot and AHS 5.2).
This document does NOT detail any of the updates and fixes
that should be applied and need to be downloaded from the
SCO web site.  See URL's at bottom.

OSR5 was originally designed as a high uptime file server.
Free OSR5 tends to be used as a workstation.  The differences
are minimal, but should be recognized:

	Server					Workstation
Emphasis on server software.		Emphasis on client software.
Emphasis on reliability.		Emphasis of features and functions.
SCSI and RAID.				IDE/EIDE and ATAPI.  No RAID.
All partitions are Unix.		Many partitions and operating systems.
No multimedia.				Sound and fancy video.
Internal modem.				Intelligent serial + external modems.
14" VGA mostly for admin.		17"-19" VGA for applications.
A few major applications.		A large number of ported GPL apps.


=> Buzzwords [Optional]

IDE	A hard disk access method that emulates the Western Digital
	cylinders/heads/sectors method found on older MFM drives.
	The controller is actually on the drive.
EIDE	Enhanced IDE to circumvent the 512MB table limit of IDE
	drives by allowing more than 1024 cylinders.
LBA	Logical Block Addressing.  An extension to EIDE that retains
	the 1024 cylinder limit but increases the number of heads
	beyond the 16 head limit.
ATAPI	IDE emulation of a SCSI cdrom drive to make it look like
	an EIDE device.  Includes an IDE interface.

Drive		A physical hard disk.  Also known as a disk drive.
Partition	Part of a disk drive occupied by ONE operating system.
File System	Sub-division of a partition within an operating system.


=> Hardware that works:

IDE/EIDE/LBA/ATAPI disk drives and cdrom drive.


=> Hardware that doesn't work:

- Proprietary cdrom interfaces.  Most of these do NOT use the
40pin IDE interface cable.
- Sound card IDE/SCSI ports.  These require driver support to
initialize the card to enable the port.  If you have an ATAPI CDROM
drive attached to one of these, move it to an IDE port that is NOT
on the sound card.
- Floppy tape drives.  Although SCO supports some (not all) of the
currently manufactured floppy tape drives, I consider them all to
be unreliable junk.  The problem is that almost all big and reliable
tape drives require a SCSI adapter and cost new 8-10 times as much
as a floppy tape drive.


=> Hardware that you may have trouble with:

Some PCI video cards do not initialize to generic VGA mode and will
display garbage during the installation.  I suggest you "borrow" a
generic ISA VGA card for the installation, install the entire AHS
5.2 driver updates (included on floppy), and then run:
	scoadmin video
to experiment with various video drivers and configurations.


=> Hardware that you will have trouble with:

Plug and Play network and modem cards.  OSR5 does NOT support plug
and play.  Most cards allow for "software configurable" or "jumper
configurable".  Use one of these to setup the card.  Be sure to
write down your settings.

Diskdrives over 2.5GBytes will require a patch to operate.  See:
oss451a.ltr
oss451a.Z

You can use either LBA or EIDE mode.  However, if you switch modes
in the CMOS BIOS setup, power down (not just reset) the computer
to be sure that the drive knows that the mode has changed.

The mouse should be on COM1: or use a bus mouse (usually IRQ=12).
You cannot share IRQ's between serial devices.  Therefore, each
16550 serial port and modem must have its own IRQ.

If your EISA or PCI cards require jumpering or running a
configuration utility, do so before starting the installation.
Write down the settings.


=> Where to look for hardware updates:

Check the:
HCH (hardware compatibility handbook).
If it lists the driver as "vendor supplied" you will need to check
that vendors web page for drivers and/or updates.


=> Minimum RAM and diskspace.

I suggest 16MB ram minimum and 500MB of diskspace.  At least
15MB of diskspace must be reserved on the boot drive for the
boot (/stand) filesystem.  This filesystem must be located
at the equivalent of less than cylinder 1024.  This is not
an issue with LBA which never has more than 1024 cylinders
but may be a problem with "normal" EIDE.


=> The Documentation  [Mandatory]

Read the Installation Instructions in the booklet that came
with the CDROM using an MSDOS computer.  All the text
documentation and HTML documents can be read from MSDOS.
All references to a "single user" system really mean two user.

Read the read me:
	E:\README.TXT
Read the cover letter:
	E:\INFO\OPENSRVR\EN_CVLET.TXT
Read the open server read me stuff:
	E:\INFO\OPENSRVR\README.TXT
Read the installation instructions:
	E:\INFO\OPENSRVR\EN_INST.TXT
Read the installation release notes:
	E:\INFO\OPENSRVR\NOTES.TXT

Also read the following files on the CDROM.
	E:\LICENSE\LICENSE.TXT
	E:\INFO\ARCSERV\README.TXT
	E:\INFO\OPENSRVR\README.TXT
	E:\INFO\DOCTOR\README.TXT
	E:\INFO\DEVSYS\README.TXT
	E:\INFO\AHS\README.TXT
There are many other files worth reading on the CDROM.  Run:
	E:
	CD \
	DIR *.TXT /B/S
for a list.  You may want to print the installation instructions
as the CDROM will be unavailable for reading during installation.

If you have a Windoze machine with an HTML viewer (Netscape or
MS Internet Explorer), you can view numerous HTML files on the
CDROM.  Most are in subdirectories labeled MKTGLIT (Marketing
Literature). For a list, run:
	E:
	CD \
	DIR *.HTM /B/S
You may want to be connected to the Internet when you do this as
some of the HTML documents have URL's that point to various documents
on the net.


=> Installation and Release notes [Gotcha]

The CDROM makes reference to the printed versions of the
Installation Handbook and Release Notes which are usually
included with the commercial incantation of OpenServer 5.
Online versions of these were not included with the free
CDROM.  See Online Documentation at:
www2.sco.com:1996/dochome.html
and Release Notes at: 
www3.sco.com/Products/freeunix/relnotes.htm.
Read the "Handbook" and the Release Notes.


=> Licencing  [Mandatory]

Get your Free SCO Unix licences from:
http://www3.sco.com/Products.
Be sure to have a printer attached as the codes are best
printed rather than trans-scribbled longhand.


=> MSDOS utilities partition  [Optional]

Boot an MSDOS 6.22 floppy.
Clean the hard disk by deleting any disk managers with FDISK.

Create an MSDOS 6.22 partition no larger than 440MB.  I use 20MB.
This is where I store my DOS diagnostics, EISA setup, ethernet
setup, and anything useful for testing the system.  Configure the
CONFIG.SYS and AUTOEXEC.BAT to recognize the CDROM drive.


=> Existing partitions and different operating systems  [Optional]

??????  blah...blah...blah...blah...blah.  Help??????


=> Primary Secondary Master and Slave  [Manditory]

The installation is going to assume that you are installing
OSR5 on the first physical disk drive.  This is the Master
on the Primary IDE port.  You do not need to install any kind
of special driver as the wd ide driver is built into the
installation kernel.  The boot drive must have at least 15MB
of diskspace for the boot partition (/stand).

It is possible to install the rest of OSR5 on a different drive.

??????  blah...blah...blah...blah...blah.  Help??????

The CDROM may be installed as either a Master or Slave on
either the Primary or Secondary IDE port.  You will need to
know where it is connected before proceeding.  SCO recommends
you read the initial hardware configuration display screen
after booting from floppy.  This is worthless because it only
stays on the screen for 10 seconds.

OSR5 treats the CDROM as a SCSI device.  CDROM drives are inherently
block counting (SCSI) devices.  (Quiz: How many tracks on a cdrom
disk)?  ATAPI makes this SCSI device look like an IDE device with
cylinders/heads/sectors.  SCO turns it back into a SCSI device.
There really is a SCSI cdrom drive hidden under all those acronyms.

Your ATAPI CDROM should be *ONE* of the following.
   	IDE PORT      CDROM     HA    ID    LUN   BUS
   	Primary	      Master     0     0     0     0
   	Primary       Slave      0     1     0     0
   	Secondary     Master     1     0     0     0
   	Secondary     Slave      1     1     0     0
   	

=> Complex boot strings. [Optional]

Much of the following is from the SCO OSR5 "Handbook" in
the "Using bootstrings" section.  (Some boot string command
lines are different in 3.2v5.0.0d).

The boot process is controlled by the program "bootos".  The
kernel is fairly smart about detecting hardware but cannot
anticipate all manner and combinations of hardware.  If you
thrive on complexity, the kernel will need some help on the
boot: command line.  The first arguement is always "defbootstr"
which defines the default ram disk, swap location, and boot
device as defined in /etc/default/boot.  This saves considerable
typing.

If you have an ATAPI CDROM, add "disable=dptr" to prevent
the IQM from mistakenly recognizing the CDROM drive as a DPT
SCSI adapter.

SCSI devices are defined with:
	periph=adapter(HA,BUS,ID,LUN)
where:
	periph=		Sdsk	SCSI hard disk
			Srom	SCSI CDROM
			Stp	SCSI tape
			Sflp	SCSI floptical
	adapter= 	Host adapter driver name or BTLD name.
	HA=		Host adapter number 0-7.  Default=0.
	BUS=		Host adapter bus 0-1.  Default=0.
	ID=		SCSI device ID. 0-7 (SCSI-2) or 0-15 (16bit SCSI-2)
			Default=0.
	LUN=		SCSI device Logical Unit Number 0-7.
			This applies to juke boxes and RAID.  Default=0.

Note that the above is a mixture of host adapter and SCSI device
parameters.  I use the term "adapter" to mean the SCSI host
adapter card and "device" to refer to the peripheral device
(disk drive or cdrom).  See below for examples.

SCSI adapters are defined with:
	adapter=driver(base,int,dma)
where:
	driver=		Host adapter driver name or BTLD name.
	base=		Host adapter I/O (hex) base address (e.g. 0x220)
	int=		Host adapter IRQ (decimal) number. (e.g. 11)
	dma=		Host adapter DMA (decimal) channel number.
Try not to get confused between the mix of hex and decimal numbers.
There are no defaults for adapter configuration.  See below for examples.

=> BTLD  (Boot Time Loadable Drivers).

BTLD's are supplied on a floppy labeled AHS 5.2 (Advanced Hardware
Supplement 5.2).  The OSR5 kernel cannot include every conceivable
device driver.  BTLD's allow drivers to be added during the boot process.
For SCSI host adapters, BTLD's must be installed during installation
or the host adapter will not be recognized.  Network cards and graphic
devices (video) cards may be added AFTER the installation.

BTLD drivers are defined with:
	ahslink=driver1,driver2

The list of BTLD names in AHS 5.2 on the cdrom is incomplete.  See:
http://www.cruzio.com/~jeffl/sco/btld.htm
for a better list.

=> Which boot drive?

Mixed systems (IDE and SCSI) confuse the kernel as to which drive
is the boot drive.  OSR5 recognizes the wd driver (IDE) before the
Sdsk (SCSI) or ida (Compaq imbedded SCSI) drivers.  If you have
a SCSI hard disk and an ATAPI cdrom, it will get confused.  You
must specify the boot device with:
	hd=driver_name
where driver_name=:
	wd0	IDE drive as master on the primary ide port.
	Sdsk	SCSI disk drive.
	ida0	Compaq IDA SCSI adapter.
	esdi	ESDI disk controller.
There is no mention in the docs on how to name an IDE drive
as a slave or on the secondary IDE port.  Help?

=> Bogus BIOS battles.

EIDE drives work by convincing the bios that it really has more
cylinders, heads and sectors per track than the partition table
will allow.  OSR5 may have some trouble making the distinction
and could use some help.  Add:
	biosgeom=cyl,hds,sec
where:
	cyl	Number of cylinders.
	hds	Number of heads.
	sec	Number of sectors per track.
If your IDE drive displays a radically different, bogus or obviously
corrupted disk geometry on the hardware configuration display during
boot, you need to add this string.


=> Examples of boot strings and IQM.
	
- IDE hard disk and ATAPI cdrom drive.
	boot: disable=dptr
When it asks for the type of cdrom drive, answer:
	scsi
For the type of scsi device, answer:
	wd
See chart above for the fake SCSI settings.

- Supported in kernel SCSI hard disk adapter and an ATAPI cdrom drive.
	boot: disable=dptr
When it asks for the type of cdrom drive, answer:
	scsi
For the type of scsi device, answer:
	wd
See chart above for the fake SCSI settings.

- SCSI hard disk supported with BTLD driver and an ATAPI cdrom drive.
An Adaptec 2940 SCSI adapter:
	boot: defbootstr Sdsk=alad(0,0,0,0) disable=dptr
This takes the default boot string and adds the Sdsk=alad(0,0,0,0)
to the end.  Specifying the Sdsk (SCSI disk) parameter overrides
the automatic hardware probe looking for a hard disk.
When it asks for the type of cdrom drive, answer:
	scsi
For the type of scsi device, answer:
	wd
See chart above for the "fake" SCSI (ATAPI) cdrom settings.

- IDE hard disk and SCSI cdrom drive (scsi adapter driver in kernel).
An Adaptec 1522A SCSI adapter on ID=5 for the cdrom.
	boot: defbootstr Srom=spad(0,0,5,0) hd=wd0

- IDE hard disk and SCSI cdrom drive (scsi adapter driver requires BTLD).
An Adaptec 2920 SCSI adapter on ID=5 for the cdrom.
	boot: defbootstr Srom=alad(0,0,5,0) hd=wd0 ahslink=alad

There are many other options and combinations of bootstrings.
I've tried to cover the most common.  At this time, I have no
clue as to how to deal with a boot partition (15MB) in the boot
drive and the rest of Unix on another drive.  Stay tuned.


=> OpenServer 5 Installation  [Mandatory]

Boot from the OpenServer Boot Disk and follow the instructions in
the  E:\INFO\OPENSRVR\EN_INST.TXT  document.  Some hardware devices
require the BTLD (Boot Time Loadable Driver) disk enclosed.  The
basic installation will take approximately 2 hours.   Make a log
of your answers in case you want to do it again or ask questions.


=> Potential Problem with News [Advisory]

Note:  If you're going to be running usenet news and want to create
a /usr/spool/news filesystem during the installation, create it
as /news temporarily.  This is because there is a rather nasty
bug in the SSO procedures that mangles the symbolic links between
/usr/spool and /var/spool.  After the system is running, run:
	mkdir /usr/spool/news
and edit the file:
	/etc/default/filesys
to change the /news mountpoint to /usr/spool/news


=> OSR5 Configuration [Advisory]

When done, you should be able to login to multiscreen #2 with
 and run an X11 session.  If you elected to NOT
start an X11 server, login to any multiscreen as root and run:
	scologin start
If you're not sure, try:
	scologin query
for the current status.  All of the administrative functions
appear on the desktop under System Administration.
If you hate graphic interfaces, simply login as root and run:
	scoadmin
which is the CHARM text based VTCL System Administration.


=> Shutdown and Reboot Cerimony [Mandatory]

If you or the installation procedure relinks the kernel and
the system asks you to reboot, the proper procedure is either:
	init 6
or the more graceful:
	shutdown -g0 -y


=> Hardware Suppliment Installation [Mandatory]

The CDROM includes the latest network and graphics card drivers
as AHS 5.2.  These are NOT installed during the initial installation.
The "easy" way to install everything in AHS 5.2 is:
	login: root  	(this can be done multiuser)
	(Don't mount the cdrom)
	custom -i -p SCO:AHS -m /dev/cd0
	(Wait 55 minutes while the SSO scripts do their thing).
	init 6   	(to reboot)
Verify that the 5.2.x drivers were installed with:
	swconfig
You can also do this installation using custom (Software Manager)
menu from either the command line or X11 desktop.


=> Development System (C Compiler) Installation [Optional]

The CDROM includes the complete OpenServer Development Systems.
You can install either the OSR5 development system or the
ported GNU GCC compiler located on the Skunkware 96 CDROM.
Both compilers can co-exist and be installed on the same machine.

If you plan to run *ONLY* GCC, install just the library files
and linker with:
	custom -i -p SCO:odslite -m /dev/cd0
Installation procedures for GCC are on the Skunkware 96
CDROM in HTML format which may be viewed with Mosaic.
The installation instructions are correct with the exeption
of the instructions for installing the library files.
Use the above command instead.  The best place to start is:
	Insert Skunkware 96 CDROM.
	mount /dev/cd0 /mnt
	Accessories -> Mosaic -> File -> Open Local
	file://localhost/mnt/index2.html   (non-frames version)
	Click on "GNU DevSys"

To install the OSR5 Development System and libraries, run:
	custom -i -p SCO:ods -m /dev/cd0
Install time is about 45 minutes.  You will be prompted
for licence information.


=> Layered Products Installation [Optional]

The CDROM includes functional "lite" versions of SCO Doctor
and ARCServe Lite.  Be sure to read the various README.TXT
files before attempting installation.  Installation was a
bit tedious with the menu based or X11 versions of custom.
The following is a list of packages, a brief description, 
version, the installation command, comments and install time.
Do *NOT* mount the cdrom.  Custom+ will do the mount and
search the entire CDROM for the proper installation files.

SCO Doctor Lite 2.0.0b
Server optimization, monitoring and alarm software.
custom -i -p SCO:DrLite -m /dev/cd0
Install time = 20 min.
After installation, run "doctor" to configure.
You might want to turn off alerts.  I let it run overnight
in the default configuration and was blessed with several
hundred "sort of memory" alerts.

ARCServe Lite 2.1.0e
Network tape backup program.
custom -i -p SCO:ARCserve_lite -m /dev/cd0
Install time = 15 min.
Kernel is relinked and a reboot required.
Make sure your tape drive works before installing.
For some dumb reason, only some of the necessary tape devices
appeared on initial OSR5 installation.  I had to run:
	mkdev tape
to first remove the tape driver and then re-create it.
You can start and stop the tape server with:
	astart and astop
The ARCServe admin program will appear under the "System Admin"
window on the X desktop.  The only problem I had was trying to
access the tape device outside of ARCServe.  "tape reset" would
panic the system (0xE) when the ARCServe daemons are running but
works fine when the daemons are stopped.  Also, don't worry about
the error message on starup where ARCServe scans all available
SCSI ID's for a suitable tape drive.  If you have a gap in ID's,
you will get an error message assuring you that there's really
nothing there.

To remove any of these packages, run:
	custom -r SCO:package_name


=> Libraries and fixes [Don't Install]

The CDROM includes:
SCO Suppliments 5.0.0b.
This turned out to be some LMC (Lan Manager) updates which
are only required AFTER installing SCO Lan Manager.  You
don't need it.

Application Development Libraries and Linker 5.0.2b
These are automagically installed along with the Development
System and need NOT be installed seperately.


=> Licencable Products [Optional]

For a better list of what's on the CDROM, try:
	http://www.sco.com/ssl_reference?482897
For a description of these and other SCO products, see:
	http://www3.sco.com/Products
For a list of SCO generated acronyms, see:
	http://www.cruzio.com/~jeffl/sco/acronym.htm

The CDROM includes products that require licencing to function.
These include:
	AFPS 3.5.1f		Advanced File and Print Server.
	Merge 3.2.2t		MSDOS Emulation with Windoze support.
	SMP Support 5.0.2Dp		Symmetric Multiprocessing.
	MS Client for Advanced Server 3.5.1f	Client for AFPS.
	Virtual Disk Manager 5.0.2Dp	Software RAID disk support.
	WABI 2.0.1d		Windoze Application Binary Interface.
There are also mention of the Enterprise and Host system
in the Software Manager (custom).  Don't bother with these
as the Desktop system includes everything in both.  They're
just there to confuse you.
	Enterprise	Everything including networking.
	Host		Everything exept networking.
	Desktop		Everything including networking 2 user licence.

Some documentation incorrectly claims that the CDROM includes
a single user version of AFPS.  This is incorrect.  AFPS will
not install without a licence.


=> Client (Windoze) Demo Software Installation [Optional]

The CDROM includes Windoze client connectivity demos for
AFPS (Advanced File and Print Server), OpenServer and
VisionWare products.

AFPS is a Windoze slide show.  Run: E:\DEMOS\AFPS\SETUP.EXE
on your Windoze machine to install and run.

The OpenServer demo is a zero length file at:
E:\DEMOS\OPENSRVR\SETUP.EXE.  Conspiracy theories accepted.

The VisonWare Demo installation is broken.  It is looking
for its files in the wrong directories.  It wants its files
in E:\DEMOS\VISION\DISK1\whatever instead of the supplied
E:\DEMOS\VISION\whatever.  Damage control and additional
conspiracy theories accepted.  You can download a working
version from:
	http://www.vision.sco.com/brochure/termvision.html


=> Skunkware 96 Usenet Ported Code Installation [Optional]

If you have the Skunkware 96 (SCO ported software and goodies)
CDROM, install most of the CDROM it with:
	mount /dev/cd0 /mnt
	cd /mnt
	custom -i -p SKUNK96:default -z /mnt/inst/All
	(This will take about an hour to install)
If you wish to install only some parts, copy, edit and run the
file /mnt/INSTALL.  There are a few packages that need to be
installed manually.

Install the other stuff using an HTML browser:
	Insert Skunkware 96 CDROM.
	mount /dev/cd0 /mnt
	Accessories -> Mosaic -> File -> Open Local
	file://localhost/mnt/index2.html   (non-frames version)
For Netscape or other browser that supports frames, use:
	file://localhost/mnt/index.html   (frames version)
Then follow the primrose path or yellow brick road.

Distribution of Skunkware products are currently on hold
due to negotiations over the use of the "Skunkware" trademark.
The contents of all the various Skunkware cdrom's are at:
	http://www.sco.com/Third/Skunk/Skunkware/

=>  How do I ...?

- How do I change screen resolution?	
	mkdev graphics   or   scoadmin video
- How do I install a parallel printer?
	mkdev parallel
	scoadmin printer
- How do I change screens?
	[Ctrl][Alt][F1] thru [Ctrl][Alt][F2]
- How do I configure the network?
	netconfig
- How to find and install updates.
	ftp://ftp.sco.com/osr5/?????
	SSL's, APP's, NET's, UOD's, and such.
	Download the "info" file.
	news://comp.unix.sco.announce
- What's the difference between Free OSR5 and 3.2v5.0.2?
	OOSR5 does not contain: OP-email  popper(pop3)  1 user AFPS
- Where's my POP3?
	ftp://ftp.sco.com/TLS/tls593.ltr
	ftp://ftp.sco.com/TLS/tls593.tar.Z

- What the $%*&! is happening?
	Who am I?				who am i
	Who am I really?			id -l				
	Where am I?				pwd
	What am I doing?			ps -f
	Who did I login as?			logname
	What's my terminal?			tty
	What are my terminal parameters?	stty -a
	Is terminal flow control working?	ls -alR / (look for garbage)
	What is my current crontab file?	crontab -l
	Do I have uucp jobs queued?		uustat
	My uucp system name?			uuname -l
	My version number?			uname -X | grep Release
	What is the system doing?		w
	What versions are installed?		swconfig
	What are my hardware settings?		hwconfig -hc
	Is /etc/passwd correct?			pwck
	Is /etc/group correct?			grpck
	Is /etc/gettydefs correct?		/etc/getty -c /etc/gettydefs
	Do all files have owners?		quot  (look for numeric UID)
	Who is using all the disk space?	quot
	When did joe last login?		last -n 10 joe 
	What files are owned by UID=944?  find / -user 944 -exec l -d {} \;
	Are file perms/owners/links OK?		custom -v symlinks
						custom -v config
	Check uucp file consistency.		/usr/lib/uucp/uucheck
	What are uucp access permissions?	/usr/lib/uucp/uucheck -v
	How do I stop the X11 login?		scologin [options]
	Give me color text!			setcolor

- Tuning and performance
	Has the system been swapping?		swap -l
	How much diskspace is left?		dfspace  or   df -v -i
	Kernel Tuning menu			cd /etc/conf/cf.d; configure
	What are the kernel parameters?		/etc/conf/cf.d/configure -x
	Open files, inodes, processes?		pstat | grep '^[0-9]'
	How is the system running?		vmstat 10

- Peripherals
	How do I boot DOS, NT, etc?		bootos [options]
	What is the print spooler doing?	lpstat -t
	Stop the scheduler.			/usr/lib/lpshut
	Restart a printer.			/usr/lib/accept printer_name ;
						/usr/bin/enable printer_name
	How do I stop this monster?		init 6  or  shutdown -g0 -y
	How do I mount a cdrom?			mount -r /dev/cd0 /mnt
	Where's my DOS partition?		dosdir /dev/hd0d

- Online docs
	Documentation?				man -a command_name
	Whazzat?				whatis command_name
	Which Documentation?			apropos buzz_word

- Networking
	Where am I?				hostname
	Is system foo alive?			ping foo
						ping 192.168.111.1
	What machines are connected?		netstat
	How is the network doing?		netstat 10
	Where are the packets going?		netstat -rn
	Network not work?			netstat -s
	How is the ethernet card doing?		ndstat   or   ndstat -l
	What's my network configuration?	ifconfig -a
	PPP?					pppstat
	

=> Useful URL's
My SCO documents index (by Jeff Liebermann)
	http://www.cruzio.com/~jeffl/sco/index.html
This document.
	http://www.cruzio.com/~jeffl/sco/ide.html
SCO Web Site.
	http://www.sco.com
SCO Support page.  This is a good place to start for
problems, updates, fixes, and documents.
	http://www.sco.com/Support/expert/exprttoc.htm
SCO Support Search.  Be sure to include "OSR5" in the search string
or you will get articles for different SCO products.
	http://www.sco.com/Support/ssl.html
SCO character based support bbs.
	telnet://sosco.sco.com
SCO Bug Report Form.
	http://www.sco.com/Support/bug.html
SCO HCH (Hardware Compatibility Handbook)
	http://www.sco.com/Third/hch/hch.htm
SCO OSR5 Supplements README.  List of fixes to date.
	ftp://ftp.sco.com/README.OSR5.Supplements
SCO Free OSR5 home page.  Also, where to get your licences.
	http://www3.sco.com/Products/openind.html
SCO OSR5 Online Documentation.
	http://www2.sco.com:1996/dochome.html
SCO OSR5 Release Notes.
	http://www3.sco.com/Products/freeunix/relnotes.htm
SCO Unix FAQ (by Stephen Dunn).
	http://www.postino.com/sco/scofaq.html
SCO ported software archive (by Bill Campbell)
	ftp://ftp.celestial.com
SCO newsgroups.
	comp.unix.sco.announce
	comp.unix.sco.misc
	comp.unix.sco.programmer
	comp.unix.xenix.sco

=> Revision History

961115 Initial inscription.
961118 Added complex boot strings, command lines, humor, bad attitude.
961119 Corrected bootstings.  Adjusted bad attitude.  Intro.  URL'S