home *** CD-ROM | disk | FTP | other *** search
-
-
-
- APPENDIX M -- RBBS-PC in ORCHID or AST PCnet NETWORK M-1
-
-
- APPENDIX M -- RBBS-PC in ORCHID or AST PCnet NETWORK
- ----------------------------------------------------
- RBBS-PC can be implemented on an Orchid PCnet or AST PCnet Network
- environment. It is assumed that the necessary network hardware is
- installed correctly. The following discussion describes a network
- currently in operation and receiving more than 1000 calls per week on two
- telephone lines for the Computer Connection of Virginia Beach. The
- hardware and software was:
- 1. 80286 based SERVER with 512K running at up to 9 MHz with:
- Parallel-Serial Board on the AT with a serial port addressed as COM1
- AST Rampage memory board configured with 2 megs of expanded memory
- Monochrome Adapter with parallel printer port
- PC Net adapter addressed as 0080 with default jumpers
- Hard disk that can be divided into multiple volumes
- Single High Density [1.2 meg] floppy disk
- External modem and cable connected to COM1
- 2. 8088 based WORKSTATION with 640K running at up to 8 MHz with:
- multifunction board with COM1, a clock, and parallel port
- PC Net adapter addressed as 0011 with default jumpers
- Color Graphics Adapter
- Two 360K floppy drives
- External modem and cable connected to COM1
- 3. Software -
- Operating System = DOS 3.1 network-wide
- Network Software = Orchid PC Net 3.0a
- Disk Caching Software = Orchid CACHE.EXE version 2.2
- RAM Disk = AST FASTDISK
- Installation procedures ---
- 1. Preliminaries
- 1. Backup hard disk, system and network disks.
- 2. If your hardware is different, be sure to resolve INTerrupt conflicts
- with the PC NET adapters. Disable second serial or parallel ports in all
- PC's.
- 2. Using the WORKSTATION, boot with DOS 3.1 then
- 1. Create the SERVER and WORKSTATION boot disks with SPCGEN and UPCGEN
- commands, respectively.
- 2. Copy device drivers for the hard disk, for the RAM disk, and for
- Expanded and Extended memory (REMM.SYS and REX.SYS) to the SERVER boot disk
- as well as CACHE.EXE. Place the following CONFIG.SYS file for the SERVER:
- device=spc.com <-- Network SERVER driver
- device=REMM.SYS <-- Expanded memory driver
- device=rex.sys 1024 <-- 1MB Emulated extended memory
- device=fastdisk.sys 1024 512 128 /e <-- RAM disk in extended memory
- 3. Place the following commands in the AUTOEXEC.BAT file:
- disk13 <-- Network for floppy disk use
- cache [drives] d=128 x=896 /r <-- 128K cache of DOS memory & 896K of
- EMS memory for SERVER drives to reduce the number of disk accesses
- spcbio 138023 <-- Tell network of interrupts used
- 4. Using the SERVER, boot with the newly created SERVER boot disk
- 1. Run the network program SPCINST.
- 2. After naming all the available drives on the server, assign all the
- hard drive volumes to the WORKSTATION # 11 and them all READ/WRITE capable.
- "Remote Execution" need not be enabled.
- 3. The SERVER will then reboot and the network will have the final
- configuration as outlined above.
- 5. Boot the WORKSTATION with the newly created WORKSTATION boot disk and:
- 1. Add FILES = 16 to the CONFIG.SYS file for the WORKSTATION.
- 2. Use the network program UPCINST to communicate with SERVER # 80.
- 3. "Map" in all the drives that were assigned by the SERVER.
-
-
-
- RBBS-PC 17.3A TECHNICAL REFERENCE MANUAL M-2
-
-
- 4. The WORKSTATION will reboot so the changes can take effect.
- 5. After the WORKSTATION reboots, do a DIR C: to see if the directory on
- the SERVER hard disk can be read. If not, recheck cables, plug-in cards
- for INTerrupt conflicts, and network adapter cards to verify all jumper
- settings. If necessary, run the SELFTEST and NETTEST diagnostics for the
- network adapter cards. Also, demonstrate the ability to copy files across
- the network to and from the server then verify the transfer using the COMP
- command.
- 6. Assuming that you are able to do a DIR across the network and copy files
- to and from the SERVER, you are then ready to run CONFIG.EXE of RBBS-PC.
- Run CONFIG and confirm use of RBBS-PC in a multinode environment. Assign
- the number 1 Node to your SERVER.
- 1. Assign all welcome, bulletin, help and menu files to the SERVER's RAM
- drive so the workstation may access them in the fastest way.
- 2. Store FILESEC, PASSWRDS, MESSAGES, USERS and other sensitive files in a
- non-downloadable but sharable drive volume on the SERVER so the workstation
- may have read/write access to them.
- 3. Select a location for the SERVER's CALLERS file and the WORKSTATION's.
- 4. Reflect the node numbers in the BATch file names, e.g. RCTTY1.BAT and
- RCTTY2.BAT, RBBS1.BAT and RBBS2.BAT.
- 5. Choose PCNET as the environment that you are running RBBS-PC under.
-
- Other Considerations--
- VDISK or Extended memory, which is not-emulated memory, should not be used
- on the SERVER but can be used on the Workstation. The network
- configuration most likely to remain operating with very few problems is DOS
- 3.1, Orchid 3.0a PC NET software and CACHE.EXE version 2.2 and an
- Expanded/Extended memory combination using the new Lotus/Intel/Microsoft
- EMS memory boards.
-
- Two nodes can be efficiently set up using the SERVER in non-dedicated mode
- but the danger is that if the SERVER locks up, the whole system locks up.
- The sample PC Net system is set up in this fashion but it is an economical
- approach to a two node system which has been functioning quite well with
- minimal problems. Do not run software on the SERVER that is known to cause
- problems especially memory resident utilities. There is a potential for
- files being CROSS-LINKED in any read/write sharable environment. Frequent
- backups are to be very strongly recommended.
-
- Because of wide variety of hardware combinations and possible network
- permutations, the above is intended ONLY as general guidelines to be
- followed when installing RBBS-PC on your Orchid network.
-
- Rob Cecchino
- SysOp, Computer Connection
- (804) 481-1824 at 1200/2400 for assistance.
-
-