XENIX System V, Version 2.1.3 by the Santa Cruz Operation (SCO), is a flexible and powerful multi-user, multi-tasking, operating system. It's one of the more popular UNIX-like operating systems for the IBM AT and compatible systems. XENIX was developed specifically for microcomputers. Its target hardware is normally DOS-based, providing the user with UNIX capabilities without requiring the purchase of new and expensive hardware. XENIX offers a number of utility programs. These utilities allow the user to manipulate files created by DOS. For example, the doscp command allows the user to either convert DOS files into UNIX files or visa-versa. Utilities are also available which provide the capability to list, make and delete directories on DOS created diskettes or perform a @ directory listing from a DOS created diskette.

The total XENIX package consists of 29 diskettes and seven manuals, including the optional text processing and program development systems. Since we've already experienced most of the problems that can crop up, we wrote this article to help you through the installation procedure and minimize your frustrations. Here's the first and most important tip. Before beginning the installation procedure, read the Release Notes and Installation Guide thoroughly don't try to wing it.

The documentation recommends a minimum storage requirement of 10 megabytes (MB) of disk storage and 384K RAM available. If you intend to install an application program, your definitely need greater than 10 MB of disk storage. The first decision to make is whether to partition the hard drive as a dedicated XENIX host or to run MS DOS in addition to XENIX. The installation guide provides clear, concise instructions for a straight forward XENIX installation with one partition. However, the instructions for installing a DOS and a XENIX partition aren't as complete.

We decided to use a Z-248 as a dedicated host and network eight other micros to the host through an eight port serial board. The main phases of installation are:

During phase 1, the system floppies are backed up, starting with the boot and file system floppies. These system floppies are crucial to the installation procedure because they contain the programs that boot the system and prompt the user through the installation process.

With phase I completed, the XENIX bootstrap program is loaded from the boot-strap floppy disk, phase 2. The system does a self-check to see if there are any hardware problems. If there are none, the letters A through H will appear, and the user will be prompted for the file system floppy. The remaining letters of the alphabet should be displayed and, after Z, the system will send the message that it is entering System Maintenance Mode. If the letters stop before Z is reached, run the hardware diagnostics and then restart the installation process. If the letters stop again, the manual tells you to call the Support Center (listed on the support information card). Be ready to tell them the letter that the display ended on.

We didn't have hardware problems, so we went to the hard disk initialization, phase 3. As part of this initialization process, the hard disk can be partitioned using the "fdisk" utility . At this point the hard disk can be partitioned to support both DOS and XENIX, or XENIX in the entirety. If the hard disk drive is new or has never been scanned for bad tracks, it should be done with the "badtrk" utility. The XENIX partition won't boot if it starts on a defective track.

The installation program's menu will have several options, including scanning the media and adding bad tracks to the flaw map of the hard disk. It's best to choose "scanning the media7" to check for any bad tracks.

While the installation program scans the hard disk it displays the cylinder and head being scanned. If a bad track is found, it's automatically entered into the "badtrk" table. If "badtrk" isn't run,you run the risk of having your XENIX partition at the beginning of a bad track and not knowing where it is for repartitioning. Note: If the XENIX partition starts on a defective track, it won't boot, and phase 4 will have to be repeated.

Next, the swap allocation must be specified. This is the area XENIX uses to manage user tasks and other simultaneous system tasks and operations. The swap allocation can be between 1200 and 3400 blocks (10, 24, bytes per block) for a 20 MB hard disk. How much swap area is available depends on the amount of disk storage you have. The more users and processes you have the more swap area you need. SCO recommends taking the maximum swap allocation, since the only way to change the swap allocation is to reinstall XENIX. After swap allocation is entered, the system will prompt you to either continue installation or quit. You don't have to install all the system files at once. If you decide to quit for a while, the manuals will instruct you on how to reboot.

To install the remainder of the operating system, the user is prompted with the following menu items: a) Text Processing, b) Operating System and c) Development System. Choose b, for Operating System. Another menu will appear with options. You can install specific files or the entire operating system.

The program will prompt for the disks of the operating system. Once aH the disks have been read, you'll be asked whether or not you wish to install another system. If so, you must go back to the main menu to select the next system you want to install.

After the disks are copied, you should create the Super-user paSSword and the first user account. The system will prompt for the super-user password or control-D for normal set up. Hitting return should bring you into system maintenance mode. To create the root (super-user) password, @: "passwd root" at the pound sign prompt (#) and hit [RETURN].

The system will then prompt you for a password of at least five characters. The password can contain a combination of upper and lower case letters and numbers. You must enter the correct password twice. If the root password is forgotten, the entire XENIX system may need to be reinstalled.

To make the first user account, you can run the "mkuser" utility. SCO suggests making a first account with login name: .. guest and password: "guest". The "mkuser" utility creates the account, gives the user a ".profile" and makes a password entry into the "/etc/passwd" file.

With the XENIX System V, Version 2.1.3 installed, our next step was to configure the system for a network of eight micros. The Operating System Users Guide has a section called Building a Communications Systems which should be read prior to configuring a system. In addition to the host, our network consists of an IBM XT, and IBM AT, an XOR XPC, three Z-248 PC's, an NCR PC8, a COMPAQ and an Okidata Microline 93 dot matrix printer.

To connect the eight users to the host, we ordered an Arnet eight-port serial expansion board.

To communicate with the host, a communications software package needs to be selected. However, before trying to set up communications there's a brief list of commands you should understand such as "enable", "disable", "stty", "TERM" , "ttys", "termcap", "ttytype" and "gettydefs" files. As mentioned earlier. the Operating System Users Guide section called Building a Communications Systems will be very helpful.

Once you've set up your communications software, make sure your ports are enabled and shut the system down using the ,.etc/shutdown" command. Then, power up your system, and you should get a login prompt at the terminal you've just set up. After this is achieved, you can put the proper setting for your terminal in your .profile" file. Each user has his own .profile". To set up a terminal in your .profile", add the following lines:

You have now successfully installed XENIX System V, Version 2.1.3. Enjoy!