WEB PairWare Installation Documentation Contained in MINIDOC.TXT, filesize = 35630 bytes, date = 3-20-92. Shareware Version Copyright 1991-1992, WEBCORP. All Rights Reserved --------------------------------------------------------------------------- TECHNICAL SUPPORT Technical support is available for WEB PairWare by: BBS: 1-415-331-6515 Free to anyone through May 1, 1992. Free to registered users only after May 1, 1992. PHONE: 1-900-933-4WEB Charge-for-call support after April 1, 1992, to registered and non-registered users. First minute free, $2 for each additional minute will be billed through your telephone company. --------------------------------------------------------------------------- INVENTORY OF FILES WEB PairWare programs and files are distributed in a self-extracting file called SHAREWEB.EXE. Running SHAREWEB unpacks the following two files: README 1ST (some installation instructions) PAIRWARE EXE (another self-extracting packed file) The following files should be unpacked when you run PAIRWARE.EXE: NETWORK HLP 61553 3-20-92 3:20p NETWORK OVL 122896 3-20-92 3:20p SM EXE 61904 3-20-92 3:20p NETWORK EXE 25600 3-20-92 3:20p INSTALL EXE 68321 3-20-92 3:20p REDIRECT EXE 10449 3-20-92 3:20p MINIDOC TXT 35630 3-20-92 3:20p PRODUCTS TXT 6747 3-20-92 3:20p README TXT 6178 3-20-92 3:20p REGISTER TXT 2854 3-20-92 3:20p CONTENTS OF DRIVERS DIRECTORY RS232 OPT 11803 3-20-92 3:20p RS232 OBJ 3503 3-20-92 3:20p If you didn't receive all these files intact, contact WEBCORP for another copy. The options for contacting WEBCORP are in the REGISTER.TXT file. --------------------------------------------------------------------------- DOCUMENTATION The following MINIDOC contains only the bare technical essentials for evaluating WEB PairWare. Upon registering, you'll receive a perfect bound User Manual that will assist you in getting the most out of your WEB network. --------------------------------------------------------------------------- 1. INSTALLING WEB PAIRWARE --------------------------------------------------------------------------- 1.1 SOFTWARE REQUIREMENTS ------------------------- DOS 3.1 or greater. DOS 3.2 not recommended. 1.2 HARDWARE REQUIREMENTS ------------------------- To run WEB PairWare you'll need: (1) two PCs, each with at least one serial port, and (2) one serial cable to connect the two computers together. 1.2.1 CONSTRUCTING A NETWORK CABLE ---------------------------------- If you wish to construct a cable, the following instructions tell you how. The cable itself is simple in design, though constructing it will require some skills with a soldering iron and some basic tools. You will need two connectors at either end of the cable. The type of connector you need depends on the type of computer you have. 1.2.1.1. DB-25 CONNECTORS ------------------------- PC XTs and other machines with 25 pin female connectors will use DB-25 connectors. DB-25 connectors use pins two, three, and seven. Pins two and three are reversed (pin two on one connector is attached to pin three on the other connector and vice versa). Refer to the diagram below when connecting two DB-25 style connectors. DB-25 DB-25 ----- ----- CONNECT PIN 2 >>>>>>>>>>>>>>> PIN 3 CONNECT PIN 3 >>>>>>>>>>>>>>> PIN 2 CONNECT PIN 7 >>>>>>>>>>>>>>> PIN 7 1.2.1.2. DB-9 CONNECTORS ------------------------ PC ATs and other machines that use 9 pin female connectors will use DB-9 connectors. DB-9 connectors use pins two, three, and five. Pins two and three perform the same functions as the DB-25 connector, and therefore must be reversed when connecting two DB-9 connectors. Pin five on a DB-9 performs the same function as pin seven on a DB-25. Refer to the diagram below when connecting two DB-9 style connectors. DB-9 DB-9 ----- ----- CONNECT PIN 2 >>>>>>>>>>>>>>> PIN 3 CONNECT PIN 3 >>>>>>>>>>>>>>> PIN 2 CONNECT PIN 5 >>>>>>>>>>>>>>> PIN 5 1.2.1.3. DB-9 CONNECTOR TO DB-25 CONNECTOR ------------------------------------------ If you need to connect a DB-9 to a DB-25 connector, reverse pins two and three and then connect pin five on the DB-9 to pin seven on the DB- 25 as shown below. DB-9 DB-25 ----- ----- CONNECT PIN 2 >>>>>>>>>>>>>>> PIN 3 CONNECT PIN 3 >>>>>>>>>>>>>>> PIN 2 CONNECT PIN 5 >>>>>>>>>>>>>>> PIN 7 1.2.2 PURCHASING A PRE-MADE NETWORK CABLE ----------------------------------------- If you do not wish to assemble your own cable, you may purchase pre-made cables from any computer or electronics store. One simple alternative is to buy a "null modem" and a "straight-through" cable. The null modem is a small device with two connectors on it that will reverse pins two and three for you. The "straight-through" cable is a three-pin cable that does not reverse pins two and three, and may be purchased in the length that you require. WEBCORP is presently testing cables from leading manufacturers and will list approved sources on our BBS. 1.3. CONFIGURING YOUR SERIAL PORTS ---------------------------------- It is recommended that you read through the Install Notes in Section 1.5 before installing WEB PairWare. When you're ready to install WEB PairWare, connect the serial cable between the serial ports of the two computers you wish to network. Insert the floppy disk containing the WEB PairWare software into the disk drive of one of the computers. Change to the floppy drive. If you have a color monitor, type the command "INSTALL" and press . If you have a monochrome monitor or monochrome laptop, type the command "INSTALL/M" and press . After reading some shareware screens, consenting to the shareware WEBCORP License Agreement, and entering the target drive and directory for installation, you'll be presented with the option to AUTOMATICALLY or MANUALLY configure the serial ports. 1.3.1 AUTOMATIC PORT CONFIGURATION ---------------------------------- If you select this option, the Install program will automatically configure the serial ports on both computers to support the fastest possible network communication between them. Follow the prompts on the screen. 1.3.2 MANUAL PORT CONFIGURATION ------------------------------- If you select this option, you will be required to manually enter the following configuration information on each computer: The COM port you will be using. The interrupt level to assign to the COM port. The baud rate you wish to use (must be the same on both computers). 1.4. COMPLETING INSTALLATION ---------------------------- Answer the questions on the screen to complete the installation process. You may press F1 at any time for context-sensitive help on any question. Many of the questions have default answers you may accept by pressing . Note that you must enter a name for the station before the Install program will let you continue. 1.5. INSTALL NOTES ------------------ 1.5.1. DOS FILES SETTING ------------------------ In order to run the Install program, the FILES setting in your CONFIG.SYS must be at least 10. 1.5.2. DISABLED COM1 -------------------- On most computer systems, when COM1 is disabled, COM2 will logically take its place and become the default COM1 port. This may create confusion when installing WEB PairWare if the user has disabled the COM1 port, since Install will still report COM1 as being active. Refer to your PC hardware manual for details specific to your machine. 1.5.3. MONOCHROME INSTALL ------------------------- If you have trouble viewing the Install screens, you may want to exit the Install program and restart it with the /MONO parameter. This forces all network programs into Monochrome mode. The following is the proper syntax: INSTALL /MONO 1.5.4. AUTOEXEC.BAT CONFIGURATION --------------------------------- If you answer YES to having WEB PairWare automatically start at system boot up and YES to having the Station Manager load as resident, the Install program will add the commands to load these two programs to your AUTOEXEC.BAT file. In some instances, WEB PairWare may not edit AUTOEXEC.BAT properly. The following is the recommended sequence of commands in AUTOEXEC.BAT: PATH C:\,C:\DOS, etc. ----------> Should have a path to DOS directory SHARE.EXE ----------------------> Must appear before NETWORK.EXE REM NETWORK STARTUP PROMPT $P$G C:\NETWORK\APPS\NETWORK.EXE C:\NETWORK\APPS\SM.EXE /R ------> Optional, gone if SM not resident REM END NETWORK STARTUP REM NETWORK PATH PATH=C:\NETWORK\APPS;%PATH% ----> Appends C:\NETWORK\APPS to PATH REM END NETWORK PATH MOUSEDRIVER --------------------> Mouse drivers and TSR's, some may TSR1 work better before NETWORK STARTUP TSR2 and vice versa. 1.5.5. TSR CONFLICTS -------------------- Most TSRs such as screen blankers and mouse drivers will usually run better before the "REM NETWORK STARTUP" line in the AUTOEXEC.BAT file. However, if you are having unexplained hangs or erratic performance, try placing a "REM" statement before the TSR in the AUTOEXEC.BAT file. This has the effect of disabling the TSR. Reboot the PC and check for the symptom. If the symptom disappears, remove the "REM" before the TSR and move the TSR to a position after "REM END NETWORK PATH." Again reboot the system and check for the symptom. Should the symptom remain after moving the TSR to another position, it's likely that the TSR is in conflict with WEB PairWare. Check the TSR manual for various mode settings that may improve compatibility. 1.5.6. DOS SHARE PROGRAM ------------------------ If you set "Multiuser = YES" in the Install program, the command to load the DOS SHARE program will be placed in your AUTOEXEC.BAT file. SHARE.EXE must be placed in AUTOEXEC.BAT on a line BEFORE NETWORK.EXE or SM.EXE. Should SHARE.EXE execute after the network initializes, you may experience system hangs when pressing the Hot-Key to enter the Station Manager; Extended Error 59 during copies or when trying to access remote drives; and other symptoms. Generally, SHARE is only loaded on a machine that is running multiuser software. WEB PairWare uses SHARE for file locking. You still may want to load SHARE just in case. 1.5.7. RESTORING AUTOEXEC.BAT ----------------------------- If you need to run NETSETUP for other than making WEB or SM either resident or non-resident, it is recommended that you answer NO when NETSETUP asks if it's OK to modify AUTOEXEC.BAT. In the event that you answered YES by mistake, go to the root of your boot drive and issue the command: "COPY AUTOEXEC.BAK AUTOEXEC.BAT" and your previous batch file will be restored. 1.5.8. SETTING FILES FOR APPLICATIONS ------------------------------------- The FILES and BUFFERS settings in your CONFIG.SYS must not be less than 20 each. WEB PairWare requires this minimum to operate properly. Therefore, if an application you're running requires 20 FILES to operate properly, you must increase your files setting to 40 (20 for your application + 20 for WEB PairWare. --------------------------------------------------------------------------- 2. NAVIGATING THE WEB PAIRWARE NETWORK --------------------------------------------------------------------------- 2.1. BASICS OF THE NETWORK DRIVE W ---------------------------------- When WEB PairWare is loaded, it automatically creates a network drive on each computer station. The network drive is always drive W. Drive W is one of the most powerful features of the WEB Network Operating System - the heart of WEB PairWare. You may change to the W drive just like any other local drive such as A or C. If you do a DIR listing of the root of drive W, you will see the name of the other station on your WEB PairWare network. If you were running the card-based version of WEB that supports large networks, you would see many stations listed in the root of the W drive instead of just one. WEB treats the other stations as subdirectories of drive W. You can use standard DOS commands to reference the other station on your WEB PairWare network. The following examples show the use of DOS commands to reference files on a machine named JOSH. C:\> _ (the current local drive) C:\> W: (change to the network W: drive) W:\> DIR (list stations in the root of W:) Volume in drive W is other PCs Directory of W:\ JOSH 3-10-92 12:00p (the other station on the net) 1 File(s) 1000000 bytes free W:\> CD JOSH (change to JOSH's station) W:\JOSH> DIR (list drives on JOSH) Volume in drive W has no label Directory of W:\JOSH . 3-10-92 12:00p .. 3-10-92 12:00p A 3-10-92 12:00p (drives on JOSH's station) C 3-10-92 12:00p 1 File(s) 1000000 bytes free W:\JOSH> CD C (change to JOSH's C drive) W:\JOSH\C> _ (doing a DIR here would list all the files and directories in the root of JOSH's drive C) As you can see from the above scenario, WEB lists other stations as directories in the root of the W drive. From the W drive, you can get to any file on another station. Note that a colon (:) is not used when referencing a drive on another station since it is being treated as a subdirectory. Put another way, to reference a file on another station, you must prepend the network path to it (W:STATION): W:\station\drive\filepath All this is done with standard DOS commands and procedures. This is very powerful. Using the path concept, you could issue a command such as this from your local machine: C:\> W:\JOSH\C\WP\WORD W:\JOSH\D\DOCS\REPORT.DOC While remaining logged onto your local C drive, this command would launch the program WORD from the WP subdirectory on JOSH's C drive and at the same time load the file REPORT.DOC from the DOCS subdirectory of JOSH's D drive. If you had a larger WEB network, this concept of a "network path" would let you reference any program and file on the network from within your applications. To begin using the network, treat drive W just like it is a local drive and use the standard DOS commands and navigation procedures you're familiar with. 2.2. THE STATION MANAGER - A GRAPHIC LOOK AT THE W DRIVE -------------------------------------------------------- WEB PairWare includes a GUI (Graphic User Interface) called the Station Manager. The Station Manager lets you: A. browse the files and devices on the network B. view the content of data files C. establish the types of access other network users have to your local files and devices (security) D. change drives and directories E. select your default serial and parallel devices F. manage all print jobs on a local device G. manage your own print jobs on a remote device H. send, receive, and answer electronic mail You may launch the Station Manager in either of two ways: (a) If installed as non-resident, type "SM" on the command line. (b) If installed as resident, press the Hot-Key combination. The default Hot-Key is "Ctrl-Alt-M." Once the Station Manager is launched, press F1 for help on how to manipulate the interface. 2.3. STATION MANAGER NOTES -------------------------- 2.3.1. DON'T REDIRECT THE NETWORK DIRECTORY ------------------------------------------- If you REDIRECT the drive where the Network Operating System files are installed to a remote drive or directory, the Station Manger will not run properly on your local station. We suggest that you either hide or password-protect the directory where the Network Operating System is installed on your local drive. This will prevent the above problem from happening. Don't REDIRECT your boot drive to another remote drive or directory. 2.3.2. FILES SETTING -------------------- If the "FILES=" setting in your CONFIG.SYS file is less than 20, unpredictable behavior will result while the Station Manager is running. 2.3.3. UPDATING STATION LISTINGS -------------------------------- While running the Station Manger, the station names in the tree structure for both F2 and F3 are not dynamically updated. To force the Station Manager to refresh its view of the current network stations, open a directory, volume, or device in the F2 or F3 window. 2.3.4. CONTROL-BREAK -------------------- When you open a drive or directory in the Station Manager, the Station Manager reads the information from disk and displays it on your screen in a tree form. If the level opened contains a large number of entries, this process can take some time. Pressing Ctrl-Break while the Station Manager is reading the disk information will truncate the tree at the point where Ctrl-Break is pressed. --------------------------------------------------------------------------- 3. CONFIGURING WEB PAIRWARE FOR APPLICATIONS --------------------------------------------------------------------------- 3.1 LAUNCHING REMOTE APPLICATIONS --------------------------------- One of the great advantages of using a peer-to-peer local area network is the ability to use applications located on a REMOTE Station. This is usually done by changing to the drive W and navigating to the REMOTE subdirectory containing the program files. For example, lets execute Microsoft Word (WORD.EXE) that's located in a subdirectory called WP on the C drive of DELFIN's station. C:\> W: (change to drive W) W:\> CD \DELFIN\C\WP (CD to the WP directory on DELFIN's C drive) W:\DELFIN\C\WP> WORD (run the word processing program) For the vast majority of applications, this procedure works fine. Some applications, however, expect to find certain files on a specific local drive and won't work properly (or not at all) when launched from a remote station. Symptoms of this condition are errors such as "cannot find OVL file", "INVALID DRIVE" or "CANNOT FIND DATA FILES." When you launch a program on a remote station, the program is loaded into the RAM of your local machine. If the application expects to find its files in a particular directory on drive C, it will look for them on your C drive, not the C drive on the remote machine where the files actually reside. To solve this problem, WEB provides a command called REDIRECT that will point the application to the proper drive and directory. See 3.2.1 below. 3.2. THE REDIRECT COMMAND ------------------------- You may receive help on the parameters and syntax of REDIRECT commands by typing REDIRECT on the command line without any parameters. 3.2.1. REDIRECTING DRIVES ------------------------- The REDIRECT command essentially makes a local drive letter point to another drive and directory on the local machine or a remote machine. After a drive has been "redirected" to another volume, any references to it will be directed to the other volume. For example, if you redirect your local drive D to W:\DELFIN\C (the C drive on Delfin's station) and subsequently do a DIR of drive D, you will see a directory listing of W:\DELFIN\C. This can be convenient if you constantly refer to specific subdirectories on the remote station. You can use REDIRECT and associate a drive letter to each of the remote directories. To use REDIRECT to solve the problem outlined in 3.1 above, you would configure the stations as follows (we'll call one machine LAPTOP and the other DELFIN). DELFIN has a non-partitioned C drive with the word processing program EDITOR stored in C:\WP. LAPTOP also has a non-partitioned C drive and, since there's no word processor stored locally, wants to use the one stored on DELFIN. LAPTOP tried launching the word processor on DELFIN's station but got a "cannot find program files" error. The word processor is looking for certain files on drive C of LAPTOP and can't find them (because they're on Delfin's C drive). The solution for this is to have both machines look in the same place for the application's files. On LAPTOP you would enter this command: REDIRECT D: W:\DELFIN\C This command creates a new drive D on LAPTOP that is redirected to the C drive on DELFIN's machine. Using a text editor, you would add the command above to the batch file that starts WEB PairWare on the LAPTOP station. If it's AUTOEXEC.BAT, add the command after the "REM END NETWORK PATH" line in the file. Amend Laptop's PATH statement to include D:\WP (this may or may not be neccessary, depending on the specific word processor). On DELFIN you would enter this command: REDIRECT D: C:\ This command creates a new drive D on DELFIN that is redirected to Delfin's local C drive. Again using a text editor, add the command above to the batch file that starts WEB PairWare on Delfin's station. If it's AUTOEXEC.BAT, add the command after the command to start the network. Amend DELFIN'S PATH statement to include D:\WP (this may or may not be neccessary, depending on the specific word processor). Note that for this command to work properly, you must have the DOS SHARE command in your path. On DELFIN, run the EDITOR configuration program and tell it to look for its files on drive D. You may need to consult your EDITOR manual for specific instructions on doing this. When all this is accomplished, reboot both machines. On LAPTOP, change to drive D, change to the subdirectory WP, and enter the command: EDITOR. Remember that drive D on LAPTOP is redirected to W:\DELFIN\C where the EDITOR application now expects to find its files. Everything should work fine now. Try calling up some documents and notice that you are now looking at drive D for your files instead of drive C. Exit from the word processor. On DELFIN, change to drive D and invoke EDITOR as usual. Try calling up some documents and notice that you are now looking at drive D for files instead of C. 3.3. USING THE DOS LASTDRIVE COMMAND ------------------------------------ Some applications will not recognize a REDIRECTED drive unless you set LASTDRIVE in your CONFIG.SYS file to a value higher than the network drive you wish to use. For example, if you have REDIRECTED drive G to a remote drive and you want the application to recognize drive G, you must put the following command into your CONFIG.SYS file: LASTDRIVE=G Some applications will not recognize a non-consecutive drive letter like W. In these cases, you must redirect the W: drive to the next consecutive drive letter to enable these applications to use the network. 3.4. RUNNING APPLICATIONS FROM A READ-ONLY DIRECTORY ---------------------------------------------------- Some applications will not run from a directory that has been marked as read/only with the Station Manager. 3.5. STATION MANAGER HAS UNUSUAL COLORS --------------------------------------- With some applications, using the Hot-Key to pop up the Station Manager will cause the Station Manager colors to be modified. The colors should reset properly after exiting from the application. 3.6. USING WINDOWS 3.0 WITH WEB PAIRWARE ---------------------------------------- If you run Windows on your station, you must place the following command in your NETWORK.INI file: ClientSoftwareCompatibility=WINDOWS (long form of the command) CSC=WINDOWS (short form of same command) You must also run the WINDOWS SETUP program to recognize IBM PC LAN as the network running under WINDOWS. The WEB PairWare 2.55 serial driver does not support Windows Enhanced Mode. --------------------------------------------------------------------------- 4. NETWORK.INI PARAMETERS --------------------------------------------------------------------------- 4.1. OVERVIEW ------------- The NETWORK.INI file is used to configure the operation and performance of WEB PairWare. The installation process creates a NETWORK.INI file in the APPS subdirectory under the target directory you specified during installation. The file may or may not contain any settings, depending upon the answers you gave during installation. The settings that may be placed in this file are listed below. If a setting is not placed in the file, either by you or the Install or Netsetup programs, its default value is in effect. Placing or modifying a setting in the file overrides the default. It is highly recommended that you read through these settings before attempting to modify this file. The settings are grouped into NETWORK, CLIENT, and SERVER settings. You may enter the "long form" of the setting (note the capital letters) or the "short form" that just uses the capital letters. The form for each setting is: SETTING=VALUE For example, the NCSF setting would be entered: NCSF=YES NETWORK SETTINGS Short Long Form Default Value Options ----- ------------------ ------------------ ---------------- NCSF NetworkControlSFilter Yes Yes, No NDC NetworkDataCompression Yes (286 & above) Yes, No NSB NetworkStationBias Peer Peer, Server, Client NT NetworkTimeout 30 (seconds) 5-3640 CLIENT SETTINGS Short Long Form Default Value Options ----- ------------------ ------------------ ---------------- CC ClientCache 512 (bytes) 0-32768 CDB ClientDirectoryBlocks 1 (block) 0-25 CDC ClientDirectoryCache 1 (directory) 0-25 CDCT ClientDirectoryCacheTimeout 3 (seconds) 0-3640 CF ClientFiles 20 (files) 0-128 CFCBS ClientFileControlBlockS 16,8(x,y blocks) 0-255,0254 CMDR ClientMaximumDriveRedirections 3 (drives) 0-26 CPIB ClientPrinterInputBuffer 128 (bytes) 0-4096 CPJT ClientPrinterJobTimeout 10 (seconds) 0-3640 CSIB ClientSerialInputBuffer 128 (bytes) 0-4096 CVC ClientVolumeCache 4 (volumes) 0-128 CW ClientWindow 1 (packet) 0-127 SERVER SETTINGS Short Long Form Default Value Options ----- ------------------ ------------------ ---------------- SIOB ServerIOBuffer 512 (bytes) 0-32768 SF ServerFiles (equals DOS FILES) 0-255 SPC ServerPasswordCache 10 (passwords) 0-255 SSET ServerSpoolerErrorTimeout 60 (seconds) 0-3640 SSFF ServerSpoolerFormFeed No No, Yes SSOB ServerSpoolerOutputBuffer 256 (bytes) 0-4096 SSOM ServerSpoolerOutputMethod BIOS BIOS,DOS SSPP ServerSpoolerPriorityPercentage 50 (percent) 0-100 4.2. EXPLANATION OF NETWORK.INI SETTINGS ---------------------------------------- The following are brief explanations of the purpose and use the the settings used in the NETWORK.INI file. NETWORK SETTINGS NetworkControlSFilter Controls whether or not the WEB PairWare intercepts CTL-S key combination. NetworkDataCompression Controls the use of data compression on the network. NetworkStationBias Biases a station toward client, server, or peer-to-peer functionality. NetworkTimeout The time (in seconds) until the network stops retrying a a remote request. CLIENT SETTINGS ClientCache Specifies the size of the client cache, larger caches allow small sequential blocks of data to be read ahead into to the CC and then fed to the application from the CC in large data block sizes. ClientDirectoryBlocks Controls how many blocks of directory entries can be cached for each remote directory path. Higher CDB settings allow more directory entries to be remembered before the network needs to access the remote directory again. 1 Block = 32 directories. ClientDirectoryCache Specifies the number of different remote directories, and their contents, that the client will hold in its cache. ClientDirectoryCacheTimeout Controls the maximum number of seconds that entries from a remote directory will be held in the CDC. CDCT=0 disables the CDC. ClientFiles Specifies the number of CFs for WEB to reserve for accessing remote files. Setting this value too low may cause your application to run out of file handles when accessing files on remote systems. ClientFileControlBlockS Sets the number of allowable file control blocks (x) that may be used on the network, and optionally, the number of safe file control blocks (y). FCBs are mainly for applications written to run under DOS 3.0 and earlier. Refer to your application's documentation to determine the proper FCBs required and modify CFCBS accordingly. ClientMaximumDriveRedirections Specifies the maximum number of drives that can be REDIRECTed. ClientPrinterInputBuffer Sets the amount of memory to reserve for the client spooler to use for spooling parallel printer (LPT) input from applications destined for a local or remote spool file. Increasing CPIB allows the network to send data to the spool file in larger blocks, increasing spooling speed. ClientPrinterJobTimeout Specifies the time that the client spooler should wait before assuming that the last character in a print job has been received from the application. If print jobs end in the middle of a page and continue on another or are combined with other print jobs, then CPJT may be set too low. Enter a value greater than 100 seconds if you are printing lots of graphics or using lots of fonts. ClientSerialInputBuffer Sets the amount of memory to reserve for the client printer redirector to use for spooling serial port (COM) input from applications destined for a local or remote spool file. Effects are similar to CPIB. ClientWindow Defines the maximum number of network packets that a client can receive before sending an acknowledgment to the server. All information transmitted over the network is in units called packets. By default, every packet sent by the server must be acknowledged by the client before the server will send another packet. Increasing CW allows more packets to be received before sending an acknowledgment. However, should the transmission hardware not support the higher throughput, the result of a higher CW setting can actually be decreased throughput due to lost data and re-transmissions. SERVER SETTINGS ServerIOBuffer Specifies the size of the I/O cache. Increasing SIOB decreases the number of times the server has to access the hard drive for data for each client request. ServerFiles Sets the number of SFs for WEB to reserve for serving the needs of remote clients. Defaults to the FILES= setting in the CONFIG.SYS if no parameters are specified. If you are running an application from a remote machine, that machine is acting as a server. Therefore, to provide the correct number of file handles, you should determine how many files the application needs to run and add that number to your current FILES= setting. If this value is set too low, you may get OUT OF FILE HANDLES errors or other application errors on the client. ServerPasswordCache Sets the size of the password cache on a server. Thereafter, when you access a password-protected file or device on a remote station and successfully enter the correct password, the server will record this fact in the SPC. If you access the protected file or device again, access will be granted without you needing to provide the password. Adjust this setting if you are continually asked to re-enter a password you have already entered correctly. ServerSpoolerErrorTimeout Sets the maximum time the spooler should wait before assuming that an error condition is not temporary. After this timeout, the server spooler will halt and an error message will be displayed in the Station Manager in the device's list of files that are waiting to be printed. A short timeout will cause an error status when printing to slow devices. ServerSpoolerFormFeed Setting this value to YES causes the printer to do an automatic formfeed (eject an additional blank page) between print jobs. ServerSpoolerOutputBuffer Sets the amount of memory to reserve for the local server spooler to use when sending spool files to the printer. A higher SSOB setting will decrease the number of times the spooler will have to access the spool file on disk. This increases spooling speed and reduces the impact that printing has on any local applications that may be running or the server. ServerSpoolerOutputMethod Controls the way that the spooler sends data to the printer. By default, the spooler uses BIOS calls to check for printer busy condition and for sending data to the printer. In some rare cases you may find it necessary to use DOS for this purpose. In this event, set SSOM=DOS. ServerSpoolerPriorityPercentage Sets the percentage of time that your computer devotes to printing as opposed to doing the work requested by the application you are running. Raise this value if print output is generated very slowly on your printer. Lower the value if your application runs unacceptably slow while jobs are printing to your printer. --------------------------------------------------------------------------- 5. MISCELLEANEOUS NOTES --------------------------------------------------------------------------- 5.1. ACCESSING STATIONS THAT ARE OFF-LINE ----------------------------------------- If you try to access a machine that has just gone off the network, your machine will pause for up to 30 seconds while it tries to connect to the station before you receive an error message and control of your machine returns to you. 5.2. AVAILABLE DISK SPACE ON W ------------------------------ The amount of available disk space reported when looking in the root directory of drive W and the "volume listing" level (drives listed under stations), is fixed at 4MB. Since these directories are ficticious, any number reported is also ficticious. --------------------------------------------------------------------------- WEB, PairWare, Station Manager, E-Note, and WEBCORP are trademarks of WEBCORP. Microsoft Word is a trademark of Microsoft. --------------------------------------------------------------------------- END OF DOCUMENTATION