Ref: 11640001 Title: Setting up a 3Station for Use on an EtherSeries Server Date: 8/15/88 Copyright 3Com Corporation, 1991. All rights reserved. This paper outlines the use of a 3Station on an EtherSeries server running EtherSeries 2.4 or later. It assumes that readers are lightly familiar with EtherSeries, that they have both EtherSeries and 3Plus version 1.1 or above software available, and that they are using a workstation that has two 360Kb floppy disk drives. 1. Use IBM PC-DOS version 3.1 or above. Either IBM PC-DOS version 3.1 or above or another manufacturer's version of DOS will work as long as it is compatible with 3+Start. (If it is incompatible, you will get the error message "unexpected s/w int 06" when booting the computer. If the message appears, use PC-DOS.) The version of DOS that you use to create your start volume master diskette should be the same version that is on your EtherSeries workstation startup diskette. When you create the 3Station start volume, the system files for that volume will be taken from the workstation diskette that you used to boot the workstation where you are creating the start volumes. If the versions of DOS are different, the first error message you will see while booting your 3Station will be "incorrect DOS version." 2. Create a master start diskette with epath. Create a 3+Start master start diskette with epath. (Directions for doing this are on pp. 2-5 of the "Installation and Configuration Manual.") Put a diskette that has been formatted with the "/S" option into the B drive. At the B> prompt, enter B>a:install b: When prompted for the type of diskette you are going to make, select "WORKSTATION STARTUP WITH EPATH." You will then be prompted through the rest of the process. 3. Modify the master start diskette. After the "Workstation Startup Diskette" is complete, you will need to make the following modifications. Add two files: BOOTCRD and ES.COM. These two files are on the "USER SOFTWARE AND UTILITIES ETHERSERIES USER SOFTWARE" diskette, Part #1925.01 You will also need to delete eight files: NB.COM, LGL.SYS, 3F.SYS, LOGIN.EXE, LOGOUT.EXE, MINSES.EXE, MSREDIR.EXE, SETNAME.EXE. Finally, you will need to make these changes to the AUTOEXEC.BAT file. Remove the lines: nb minses msredir /z:4096 setname $$3COM$$ :log Delete everything after the :log line. Remove the last command "MINDSLGL" from the "RUNMINDS" line. To work, the AUTOEXEC.BAT file needs only the "RUNMINDS" line and the "prtsc" line if desired. A line to link to the "sys" volume may be added. (The "sys volume" is the EtherSeries equivalent of the 3Plus "apps directory.") To link to the sys volume, enter ES LINK SYS.SYS D: In the config.sys file, change the line DEVICE=PRO.SYS 8 2 2 to DEVICE=PRO.SYS 8 20 2 Remove the line DEVICE=DRIVER.LOD LGL.SYS. 4. Copy BOOTPC.COM and BOOTSTAT.COM to the ETHERSHR directory. There are two files on the 3+Start/Server diskette that should be copied to the server. They are BOOTPC.COM and BOOTSTAT.COM. These two files are located in the 3Start subdirectory of the 3+Start/Server diskette. Make a console connection using "ECONSOLE /START" and copy the two files to the ETHERSHR subdirectory. 5. Create the start volume. Boot the server in the normal mode and log in from the workstation with the ES LOGIN command. To create the start volume, enter the following command. ES CREATE 3STATION /360KB /START (The create screen will be displayed.) 3STATION CREATED FORMATTING........................................ WRITING IBM BIO.COM.....................*WROTE 9564 BYTES WRITING IBM DOS.COM............................*WROTE 27760 BYTES. 3STATION FORMATTED. 6. Copy the start diskette into the volume. Link to the newly created start volume by entering ES LINK F: 3STATION Go to an F> prompt and then copy A:*.* Remove the master start diskette and store it in a safe place. You are now ready to start your 3Station. 7. Boot your 3Station. You will be prompted for your name. At the prompt Your name? type your user name, a space, then "SYS.3STATION" and enter a return. At this point, the 3Station should be set up. If you receive the error message "*** SERVER1.SYS unknown." then check your AUTOEXEC.BAT file to make sure that the volumes you are linking to in the AUTOEXEC.BAT file exist.