Ref: 99970022 Title: Administrator's Release Notes: 3+ Version 1.2.1 1913.04 Date: 05-30-88 Copyright 3Com Corporation, 1991. All rights reserved. A member of the 3+ family of products. For use with DOS 3.1, 3.2 ,or 3.3 3Com Corporation 3165 Kifer Rd. Santa Clara, CA 95052-8145 1987 by 3Com Corporation. All rights reserved. Printed in the U.S.A. Part Number 1913-04 Version 1.2.1 Administrator Release Notes This document provides information related to the installation, configuration, and administration of 3+ Version 1.2.1 network software. Read this information carefully (particularly if you have a Token Ring network) before installing or using your 3+ software. User release notes included along with the administrator's release notes. This set of release notes is divided into four sections; installation release notes (information relating to the installation and configuration of 3+ network software), administration release notes (information relating to the administration of 3+ network software), 3+ applications release notes (information relating to the use of 3+ applications and including all user release notes), and a special set of information relating to Token Ring networks. The abbreviated titles for the guides the release notes reference are: I&C 3+ Installation and Configuration Guide Admin 3+ AdministratorUs Guide Menus 3+Menus Reference Guide Minder 3+Mail Minder Guide Start 3+Start Supplement NBSup NetBIOS Supplement Remote 3+Remote User Guide .H1;Installation Release Notes .h2;3+Start Master Disks/Start Vols. Information in the 3+Start Supplement and in Chapter 2 of the NetBIOS Supplement supersedes information in the 3+ Installation and Configuration Guide with respect to creating 3+Start workstation diskettes. To save workstation memory, a workstation's startup diskette should not contain the full NetBIOS implementation unless that workstation will be running NetBIOS applications. To get the full NetBIOS implementation or to use the new 1.2.1 drivers: Create new 3+Start master diskettes using information from the NetBIOS Supplement. Create new workstation start volumes using information from the 3+Start Supplement. .h2;3 1/2 Inch Diskettes Your product package contains both 5 1/4 and 3 1/2 inch diskettes. You can use the 3 1/2 in diskettes to install PC server services. 3Server3 software is not installable from 3 1/2 inch diskettes. The 3 1/2 inch 3+Name diskette does not have the network number on it. When installing PC server Name service, use the network number on the 5 1/4 inch 3+Name diskette. .h2;3Console Connection NBSup, p. 2-10 When making a 3Console connection to a server that does not have a Locator, use a workstation startup diskette created with the standard 3+ configuration (not one created with the full NetBIOS option). NetBIOS workstation diskettes require that a Locator exist when they start up. If the server doesn't have a Locator, a workstation diskette created with the full NetBIOS option will not start up. .h2;3Server3 Disk Formatting If you have a 3Server3 with a serial number below F1570 and the server has never been used before, you should reformat the disk before installing 1.2.1 software (no reformat is required for serial numbers above F1570). If you have any 3Server 70 that has never been used, you must reformat the disk . Follow the instructions in the Guide for your server and use the 3Server/3+ System Diskette provided in the 1.2 package. .h2;3Server3 Sector Sizes I&C, p. 3-3, 3-9 The partition or physical drive on which 3+ services are installed no longer need to have a sector size of 512 bytes. To change sector sizes, reformat the hard disk using 3Com's 3Disk utility. (We do not recommend that you use third-party disk formatting utilities.) .h2;CacheCard Diskette If you are using a 3Server3, you may have received a diskette with the CacheCard (3C1011). This diskette is only for use with 3+ version 1.0 and should not be used with 3+ version 1.2.1. Discard the diskette (part #2984). No replacement diskette is required; the software used by the CacheCard is included with 3+ version 1.2.1. .h2;CacheCard Parameters I&C, p. D-16 When using a CacheCard, do not change the user or services parameters on the device=pro.sys line. If these values are set to anything other than 0 (or blank), the system does not function properly. Change the number of processes according to your needs. The device=pro.sys line contains the following parameters: number of processes (default is 32) user (default is 0) services (default is 0) I&C, p. A-1 If the server LCD constantly displays Loading but the services seem to be running correctly, increase the number of processes (default is 32) on the device=pro.sys line in the CONFIG.SYS file. In the following example, the number of processes has been set to 48 but the user and services parameters have been left at 0 (zero): device=pro.sys 48 0 0 .h2;Cache Card with 3Servers I&C, p. 4-11 To avoid having the EMS field reset to 0 when you install a standard library configuration of services on a server with a CacheCard, modify the EMS memory allocation after the services have been installed from the library. .h2;CIOSYS Configuration I&C, p. 3-7, 5-28 Floppy drives (drives A and B) are no longer displayed on the CIOSYS configuration screen as the guide indicates. .h2;CIOSYS Threads I&C 4-10, 5-36 Do not set the number of threads on the Configuration screen to 1 or the server may not function properly. If you have chosen standard configuration #13 (5-user Share, Name, TurboShare and a concurrent user) on a PC server, you must manually set the number of threads on the CIOSYS Configuration screen to 2. (This results in a reduction of 1074 bytes of memory available for the concurrent user.) To change the number of CIOSYS threads, follow these steps: 1. Highlight #4, Configure Parameters and Peripherals from the 3INSTALL program's main menu and press [Enter]. 2. Highlight CIOSYS or TurboShare and press [C]. 3. Highlight #2, Adjust CIOSYS parameters and press [Enter]. 4. Move the cursor to the Threads parameter and change the value from 1 to 2. 5. Press [Ctrl]+[A] to accept the new value. 6. Press [Ctrl]+[A] again. 7. Press [K] to keep the new configuration and exit to the 3INSTALL main menu. .h2;Combining 3+ Versions I&C, p.1-5 3+ versions 1.1, 1.2, and 1.2.1 can co-exist on the same server. However, 3+ version 1.0 cannot co-exist with version 1.1, 1.2, or 1.2.1. Any combinations of versions can exist on the same network if they are on separate servers. .h2;Configuration Report (memory available) I&C, p.5-15 The configuration report may not always reflect the current memory consumption of the drivers. To get a correct figure, run 3Install and select Configure Parameters and Peripherals. This updates the driver information file and the configuration report will now display the correct memory information. .h2;Connecting Multiple Networks I&C, p.4-13 When installing multi-server configurations that use 3+Mail and 3+Route to connect multiple networks, be careful in arranging services on servers and in setting up dialing schedules for 3+Route or you may not be able to send mail at the times you expect. 3+Mail uses the router (and the dialing schedule) on its server, unless another workstation (using some other network router) has already made a connection to the destination network. (In this case the mail service uses the router that has already established the connection.) For example, if the router on the mail server has a schedule that permits dialing at any time of day, and another router on the network has a schedule that permits dialing only between the hours of 4:00 AM and 6:00AM (to get cheaper phone rates for instance), you will not get the cheaper phone rates because 3+Mail dials the destination network according to the schedule of the router on its server--any time of day. To ensure that dialing schedules are consistent, use the same set of dial-out routes on all route servers. .h2;Copy Protection For your convenience, copy protection has been removed from all 3+ products. Please disregard references regarding copy protection. 5-user and n-user administration is still required for 3+Share PC and 3+Mail. When you use version 1.2.1 3+Share/PC to take either version 1.1 or version 1.2 from 5-user to N-user, the resulting code is not copy protected. The same is true for 3+Share/Server and for 3+Mail. Installation and deinstallation are still supported as installation options through the normal installation and configuration procedures. .h2;Crosstalk and IBM Asynchronous Server Do not attempt to run the IBM Asynchronous Server and the Crosstalk (any version) programs concurrently on a PC used as a concurrent server. To use Crosstalk with the IBM Asynchronous Server program, use the server running the IBM Asynchronous Server program as a communications server and move the Crosstalk program to another PC. .h2;Database Performance I&C, p. D-7 If you are running primarily multiuser database applications on your network, setting the /z parameter on the MSREDIR line of the AUTOEXEC.BAT file to 1024 may improve performance (the default is 4096). .h2;DOS 3.3 Support 3+ Version 1.2.1 now supports DOS 3.3 for both PC servers and workstations. Because of the larger code size of DOS 3.3, certain changes have been made to the Default Library Configurations. See Library Configurations (default) for details. .h2;EMS Memory (PC Server) I&C, p. 1-7 EMS memory can be used by the server (with 3+TurboShare) or by concurrent user applications, but not by both at the same time. EMS memory can be used for applications only if 3+TurboShare is not installed. .h2;ETH Needs More B I&C, p. D-15 If you continue to get ETH needs more B messages, set the ETH buffers to 65 or higher. .h2;Fatal Process Error If you are using EtherTerm and get the message : Fatal process error change the number of processes on the device=pro.sys line of the workstationUs CONFIG.SYS file to at least 10. .h2;File Service Sessions I&C, p.5-37, 5-50 If you increase the number of file service sessions, you may need to increase the number of CIOSYS file sharing processes as well (each file sharing session requires 10 additional bytes of memory). .h2;IBM AT as a Server I&C, p. 1-7 A bug in the IBM AT ROM BIOS can cause the clients of an AT used as a server to occasionally display a DOS file access error message such as Not ready reading drive or General failure This condition typically occurs when reading data from the hard disk of a very heavily loaded server. If the disk read operation is retried enough times it eventually succeeds. However, if the error handler of an application running on the network does not retry the read operation, the application itself can stop running. 3Com provides a program called ATFIX.EXE that corrects the problem for IBM AT computers (6 MHz) with a ROM BIOS dated 01/10/84 or earlier that are running only DOS 3.1 NOTE: No other combination of AT models and DOS versions can be corrected with this fix. .h2;IBM PS/2 Support 3+ Version 1.2.1 supports the IBM PS/2 (all models) both as a server and as a workstation. The IBM Model 30 is not supported for NetConnect, however. Due to the hardware design of the Model 30, the DMA channels NetConnect requires are unavailable. NetConnect is supported for all other IBM PS/2 models. 3+ Version 1.2.1 also supports the IBM Token Ring Network PS/2 adapter (using the tokibm.sys driver). .h2;Interrupting an Installation I&C, p. 4-1 If an installation is interrupted or fails in any way, you must rerun 3INSTALL. See chapters 3 and 4 in the 3+ Installation and Configuration Guide for details about running 3INSTALL. .h2;Library Configurations (default) I&C, p. 4-7 Memory values listed for standard library configurations are approximations. The amount of memory required depends upon your particular combination of printers, disk drives, and modems. p. 4-13 The 3+ NetBIOS Supplement (p. B-2) contains four standard configurations not included in the I&C guide. .h2;Library Configurations and DOS 3.3 Because of the larger size of DOS 3.3, services have had their parameters changed so that standard library configurations fit in memory. When you install a standard library configuration (and accept the default parameters for its services), the installation process overwrites existing configuration file information. This deletes existing information such as parameters you manually changed, 3+Share printer designations and 3+Route phone numbers. To make it easier to re-enter this information, print a configuration report (see the 3+ Installation and Configuration Guide, page 5-12 for details) before installing the standard library configuration. After the configuration is installed, use the configuration report to remind you of the information you need to re-enter. I&C, p.4-10 You can choose to keep your old parameters and configuration information by not accepting the preset parameter values for the standard configuration. In this case, you may have to adjust parameters manually to get the configuration to fit in memory. I&C, p.5-105 The default parameters for 3+Start have been changed from the values shown on page 5-105 to the following: Maximum number of start volumes = 3 Maximum number of start users = 3 Maximum number of receive buffers = 1 .h2;Library Configurations and EMS Memory I&C, p. 4-9 When installing standard library configurations on a server with an EMS board, the standard configuration may expect more memory than your EMS board contains. If the EMS board has less than 2 MB of memory, you may need to change the memory allocated to CIOSYS, depending upon the particular configuration. (Make this change after you have installed the standard library configuration.) .h2;Login Library Parameter (new) I&C, p. D-17 The login library manager (LGL.SYS) has a new parameter (-mx) that lets you set the maximum number of entries for the login library. he allowable range is from 4 to 64 entries. The default is 8 entries for a workstation and 32 entries for a server. Each entry requires 88 bytes. The following example sets the -mx parameter to 12: device=lgl.sys -m12 Each time you issue a 3F LINK, 3F DIR, 3P LINK, 3P DIR, or 3N ASSIGN command, an entry is made in the login library. If the number of entries exceeds the maximum set by the -Mx command, the manager displays the message: Internal error Duplicate entries are not counted, and you can clear all entries in the current Login Library by starting up the workstation again. When you reset the number of entries, you must also change the NetBIOS /s parameter (see NBSup, Chapter 3 for details) You will also need to change MSREDIR /s and MSREDIR /l parameters (see I&C, p. D-4 for details). .h2;Macintosh 3+ Installation You must have 3+ Share installed before you install 3+ for the Macintosh. Use the 1.2.1 drivers to build your workstation diskettes. .h2;Null Modem Connection I&C, p.C-6 If you are using a NULL modem connection between two networks, or between a 3+Remote PC workstation and a network, make sure each of the following timeout values are 0. (Using timeout values of 0 keeps the NULL modem connection open all the time, providing better performance and reliability.) Port Timeout value for the port on which the NULL modem is installed (on both networks). Dial-Out Route Timeout value for each route that uses the NULL modem port. TIMEOUT=0 in the PROFILE.SYS file for a remote PC that has a NULL modem connection to a network. Set the Port and Dial-out Route timeouts using the 3INSTALL program. Change the TIMEOUT value in the PROFILE.SYS by editing the PROFILE.SYS file. Admin, p. 5-36 Changes to dial-out routes for 3+Route take effect within five minutes without having to restart the server. If you change the port or buffer configurations, you must restart the 3+Route server. .h2;SERVGO Failures If you experience SERVGO failures, try setting the 3PRO.SYS parameters to 40 0 0. .h2;Tandy 4000 Support 3+ Version 1.2.1 now supports the Tandy 4000 computer. .h2;Unable to Create Directory I&C, p. A-30 The message: Unable to create directory appears if you run the installation batch file more than once because the batch file is not allowed to create a directory that already exists. This message requires no action--the batch file continues and the installation completes properly. .h1;Administration Release Notes .h2;3Com XCOPY Utility User, p. C-1 The XCOPY utility has been renamed to 3COPY because DOS 3.2 and 3.3 also contain a program called XCOPY. .h2;AUTOEXEC.BAT Files (page correction ) Admin, p. C-18 .br;I&C, p. B-31 The 3f link d: line should read: 3f link d:\sys\apps ; link e: not 3f link d: \\sys\sys; link e: .h2;LGL Not Loaded User, p. A-16 If the error message: LGL Not Loaded Appears after formatting a diskette, list the diskette's directory using the DOS DIR command. You should then be able to continue. .h2;Can't Access 3Com Process Manager User, p. A-16 If the error message: Can't Access 3Com Process Manager Appears after formatting a diskette, list the diskette's directory using the DOS DIR command. You should then be able to continue. .h2;Compaq Portable or Deskpro Computers For proper operation a Compaq Portable or Deskpro requires ROM Revision J. To find out what Compaq ROMs you have: 1. Start your Compaq using the Compaq diagnostics diskette. 2. Type test and press [Enter]. 3. Choose option 5, ROMREV. The version of your ROMs is displayed. (ROM upgrades are available only from your Compaq dealer.) .h2;Disconnecting a Server's Network If the network link for a 3Server is broken (the cable connection is disconnected or there is a missing terminator), the server LCD displays the message: Edit command error or ETH trap E403 when it is restarted. When you see this message, find the broken or missing link, fix it, and reboot the server. .h2;Installing Menus Admin, p.5-27, 5-31 References in the 3+ Administrator's Guide to the installation menu item Configure Server Parameters should read Configure Parameters and Peripherals. Internal Error User, p. A-15 The message: Internal error means you have exceeded the maximum number of entries established for the Login Library Manager. Each time you give a 3F LINK, 3F DIR, 3P LINK, 3P DIR, or 3N ASSIGN command, an entry is made in the Login Library (the default is eight and duplicate entries are not counted). I&C, p.D-17/ If a user regularly needs more than eight entries, adjust the number of entries allowed by changing the -m parameter. For information about the -m parameter, see Login Library Parameter (new) in these release notes. (To remove all current Login Library entries, reboot the workstation.) .h2;LASTDRIVE Command Admin, p. 2-20 For information about using the LASTDRIVE command, see page D-18 in the 3+ Installation and Configuration Guide. .h2;MailMinder Guide Admin, p.2-23 For information on using 3+Mail Minder, see the 3+Mail Minder Guide shipped with the 3+Mail 1.2.1 package. .h2;Modifying a Private Start Volume Admin, p.4-51, A-12 When modifying a private 3+Start volume, do not use the DOS command VERIFY=ON or COPY with the /V parameter. If VERIFY is used, 3+ displays: General error writing to drive C: Should this happen, type the DOS command VERIFY=OFF and repeat the operation. .h2;Preconfigured Administration Submenus Admin, p.4-3, 4-27 When using the preconfigured administration submenus, always check the file location of each menu item to assure that it matches your installation's configuration. To check an item, select it from the administration submenu and use the /Modify Change command to look at the file location (disk:directory) listing. Make sure the location shown is the location of the submenus. .h2;Sharename (page correction) Admin, p. 1-5 Assign the \3PLUS\3CONFIG directory the sharename CONFIG (without the forward slash), not /CONFIG as the guide shows. .h2;Sharing the Start Directory Admin, p.4-43 When sharing the \3PLUS\3START\STARTDIR directory, assign read-write-create (RWC) access rights, not public (PUB). .h2;Tape Backup Menu File Admin , p.4-5 The menu file for Tape Backup functions is ADMIN6.MNI, not ADMIN5.MNI as shown in table 4-1. .h2;Too Many Redirections User, p. A-31 The message: Too many redirections indicates you have used more links than you are allowed for your workstation. Increase the number of NetBIOS and MSREDIR sessions for your workstation. .h1;3+ File and Print .h2;3P QSTAT Command User, p. 9-17 The 3P QSTAT command lists the files in a printerUs queue. When QSTAT lists these files, the status line indicates the condition of each file, as follows: Intercept: You have not finished sending data to the queue. This condition occurs when you use the 3P SET/HOLD option, when you are printing from an application and you have not yet pressed [Ctrl]+[Alt]+[Prtsc], or when you are printing from an application that does not send a DOS CLOSE command (and you have not exited the application). Exiting an application automatically sends a DOS CLOSE command. Deferred: Your job has been sent to the queue, but you specified that the printing of the job should be delayed with the 3P SET /DEFER command. Waiting: Your job has been sent to the queue, but another job has a higher priority. Your job will print when those with a higher priority finish. Printing: Your job is currently printing. Print error: An error has occurred at the printer. This message usually means the printer is out of paper or off- line. File error: The server is out of disk space for the print queue files. .h2;UNSHARE Command User, p. 7-19 The 3F UNSHARE command deletes only the specified sharename, not the directory assigned to the sharename, as the 3+Share User Guide states. (To delete an empty directory, use the DOS RMDIR command.) .h2;Using a New-Style IBM Keyboard User, p. 5-1 If you are using an IBM keyboard that does not have [Prtsc] and [*] on the same key, close print spool files with [Ctrl] + [Alt] + [*] (where [*] is the key directly above the [9] on the numeric keypad). .h1;3+Menus .h2;APPEND Command Menus, p.1-9 The APPEND.COM is on the 3+Share User #1 diskette. (You can also use DOS 3.x version of APPEND.COM). .h2;Circular Menus References Menus, p.5-10 With 3+Menus, any submenu can point to any other menu in your 3+Menus system. This makes recursive (circular) menu references possible. While occasionally useful, this is not a good practice, and should be avoided. To break a recursive menu reference, modify the file name in one of the submenus. Select the desired menu item and change (/Modify Change) the name of the file referenced in the Menu File field. Two or more menus may reference a common submenu as long as the references are not circular. .h2;Color Screen Attributes Menus, p. B-1 The attributes j and k should be: j - Current field in forms k - Message line and the background for forms .h2;Failure Starting Your Editor Menus, p. C-5 The message: Failure starting your editor means 3+Menus cannot find the editor or the editor program file is corrupted. (Check that your editor is in the path searched by DOS or reload a fresh copy of the editor file.) .h2;Installing 3+ Menus Delete existing EM.EXE and MENUS.EXE files from the apps sharename or directory before trying to install the 1.2.1 version of 3+Menus. If the 3+Menus install program finds these programs it does not install a new version. When you install the new version of 3+Menus, your existing 3+Menus configuration files are not changed. .h2;Quitting 3+Menus Menus, p. 2-2, 2-25; How To, p. 2-14; When the 3+Menus program is on a network drive and you log out using the Log Out item (on the Main Menu), 3+Menus exits to DOS. The drive you specified on the Log Out form is the default drive. For example, if you chose A as the default drive, the A> prompt appears. There are two cases, however, in which logging out using the Log Out item can produce the message: Not ready error reading drive E Abort, Retry, Ignore? Case 1: If you are using 3+Menus on a network drive, and start it from a batch file that is also on a network drive, when you log out you will break the link to the batch fileUs network drive. This means COMMAND.COM cannot return to the batch file. To keep the link to the batch fileUs drive, either the 3+Menus program or the batch file that starts the 3+Menus program must reside on a local drive, a RAM disk, or a 3+Start volume. Case 2: If you are using 3+Menus on a local drive, but you start it from a batch file on a network drive, you can log out and 3+Menus continues to run. (This lets you run local applications from the 3+Menus interface while not logged in to the network.) Before you quit 3+Menus, however, you must log in again and re-establish the links to the sharename containing the batch file that started 3+Menus. .h2;Specifying a Menu Task Item Menus, p. 5-17 When choosing Run File or Command on a Task Item form, you do not need to include an extension. If you include an extension, make sure the extension is correct and that it matches the Run File Type. For example, specifying the batch file BATCHFIL.BAT but giving it a Run File Type of program, causes an error because 3+Menus treats the batch file as if it were a program. .h2;SYS as Default Server Name Menus, p.5-21 The convention of using SYS to represent the default server name is allowed when defining automatic linking for a menu item. User name and alias are now permitted in the second page of the Create/Modify Task form for \\. .h2;Using Memory Resident Programs Menus, p. 2-2 Terminate and stay resident programs (such as 3+Mail Minder) with 3+Menus, must be loaded before you run MENUS. .h1;3+Mail .h2;Attachments Mail, p. 2-8, 5-4 You can add up to 25 attachments to a message. .h2;Can't find ... Mail, p.C-6 The message: Can't find But domain is a Remote Domain ... means you have tried to send a message to a user who cannot be found in the local Name service. The domain specified, however, does exist in the local Name service. To send the message anyway, respond Y and the 3+Mail server will attempt delivery of the message to the remote domain:organization. If the user cannot be found on the remote network, the mail server returns the message as undelivered mail. To avoid this prompt when sending mail to users in remote domains, use the /NP parameter when running the mail program (for example, MAIL E: /NP). .h2;Color Graphics Mail, p.3-4 3+Mail version 1.2.1 supports color on color graphics and enhanced color graphics systems. To display mail in color, type: MAIL /DISPLAYTYPE=x where x is B, D, or E. Each of these letters represents a different color combination, as shown on the next page. .h2;Filing Mail Messages to Multiple Floppy Diskettes Mail, p. 6-5 When filing mail messages to a workstation with a single diskette drive, do not simply insert a new diskette into the same drive and continue filing messages (for example when the first diskette fills up). Doing so results in false directory information on the new diskette and makes its files inaccessible. If you want to file messages to another diskette, use the following steps: 1. Exit 3+Mail. 2. Remove the current diskette. 3. Insert a formatted diskette. 4. Use the DOS DIR command to list the directory of the new diskette. 5. Run 3+Mail again. You can now file messages to the new diskette. If your workstation has two diskette drives and you are running mail from a network drive, you can safely file messages to two diskettes by placing one in drive A and one in drive B. .h2;Running 3+Mail from a Dual Floppy System Mail, p. A-2 If you want to run 3+Mail locally using dual floppy drives, insert the diskette containing the MAIL.EXE program in drive A and a formatted diskette in drive B. With drive A as your current drive, use the command A>MAIL B: to start the 3+Mail program. Do not file mail to the diskette containing the MAIL.EXE program or you may lose files and directories. .h1;3+Route and 3+Remote .h2;Mixing Hayes and Microcom Modems If you are sending data from a Hayes modem to a Microcom modem or vice versa and you begin to experience slow or unreliable data transfer, put the Microcom modem into Hayes emulation mode. If your particular Microcom modem does not have a Hayes emulation mode, either replace it with a modem that does emulate a Hayes modem or replace the Hayes modem with a Microcom modem. .h2;Using 3+MailMinder Minder, p.1-4 The 3+Mail Minder program is now included on the 3+Mail User diskette. To display 3+MailMinder in color, start it with the command: MMinder /color=on. .h2;Using 4800, 9600 and 19,200 Baud Remote, p. 2-4, 3-12 3+Route and 3+Remote now support baud rates of 4800, 9600 and 19,200 (19,200 rate is supported only for the DCA Fastlink and Telebit Trailblazer modems). NOTE: To use these baud rates on a PC server, the PC must be a 80286 or equivalent, a dedicated server, and you must use the EtherLink Plus or TokenLink Plus card. If you plan to use 19,200 baud on a 3Server or 3Server3, you should use a port on the 3Server Port Expansion Board (part number 3C1050N) or you may not get the performance you expect. You must also set the 3+Remote or 3+Route receive buffers (I&C, p. 5-94, 5-97), and the ETH.SYS -h buffer (I&C, p. D-15), to 8. If you have more than one modem, determine the number of buffers with the following formula: (#modems times 6) plus 2. I&C, p. 5-92 The modem statement that specifies the type of modem connected to your computer (MODTYPE) can now include Hayes, Microcom, Fastlink, Trailblazer, or other (default is Hayes). .h1;NetBIOS Supplement .h2;Locator not responding NBSup, p. 4-8 If the node running the Locator loses power or is shut off (and if the Locator is not running on the Name server), NetBIOS continues to function normally (for example, links to networked resources are unaffected) until it tries to access the absent Locator. When the access fails, NetBIOS displays the message: Locator not responding. The SETNAME command (in your workstation AUTOEXEC.BAT file) requires a functioning Locator, so do not start up your workstation if a Locator is not available. The first Locator activated automatically detects the appearance of other Locators that try to appear on the network and ignores them. When a workstation with another locator tries to boot, it senses the that there is already a locator on the network, and terminates its boot process immediately. (This avoids the problem of a network having duplicate Locators with inconsistent name databases.) (For programmatic reference, NetBIOS continues to function normally without a Locator as long as no ADD NAME, ADD GROUP NAME, DELETE NAME, CALL NCBs, or SEND DATAGRAM commands are used.) .h2;NetBIOS /C Switch NBSup, p. 3-12 Unless you are running only 3+ services, use the /C switch on the NetBIOS line of the AUTOEXEC.BAT file. NetBIOS assumes that timeout errors on SEND and RECEIVE, as well as Locator operations that do not complete, are the result of physical network problems. To avoid terminating sessions because of such problems, NetBIOS displays the message: Network Retrying ... or Locator Not Responding You can wait for the network problem to go away or you can return the timeout error to the application immediately by pressing [Ctrl] + [Break]. When a NetBIOS application relies on getting these timeout errors as a normal part of its operation, using the /C switch returns the timeout error to the application immediately without displaying a message. .h2;NetBIOS /M Switch NBSup, p. 3-13, 4-6 The IBM Asynchronous Communications Server and the IBM PC LAN programs require the /M switch. .h2;NetBIOS and the Locator NBSup, p. C-4 References to the 3Com Session Interface in step 9, should be references to the interrupt interface. NBSup, p. 4-1 The Locator, in addition to acting as a centralized name server for NetBIOS, informs its client workstations when another machine running NetBIOS has gone offline (for example, someone rebooting the workstation). When a machine goes off-line, the Locator terminates its sessions. To let the Locator detect when a machine goes off-line, each NetBIOS machine periodically sends a heartbeat message to the Locator. If the Locator does not receive a heartbeat from a given machine every 30 seconds (every 20 minutes for remote PCs), the Locator assumes the machine has gone off-line and informs the other workstations when it responds to their heartbeats. (Sessions established through 3F are not subject to termination via this heartbeat mechanism.) For NetBIOS to send heartbeats, the timer interrupt must not be disabled. Two common conditions that disable the timer interrupt are: A local printer that is off-line while the CPU is trying to print. A program debugger that disables interrupts when it is active. Either of these conditions cause the Locator to think that the machine is off-line and thus terminate its NetBIOS sessions. You can avoid disabling the timer interrupt by calculating a new (and longer) interval and patching this new interval into NetBIOS.EXE, as explained in the following steps: 1. Choose a new interval (in seconds). The initial value for the interval is 15 seconds. (The Locator gives a grace period by automatically doubling this value.) Keep in mind that the new interval must be long enough to handle the maximum time that the interrupts will be disabled, but not so long that it creates a problem for other workstations. (Workstations will not be able to end sessions established with your machine until the timeout interval has elapsed.) 2. Convert the number to timer ticks by dividing it by .055. 3. Convert the resulting number to hexadecimal. The following steps assume the use of IBMUs Debug program to patch the new interval into NetBIOS.EXE: 1. C>copy netbios.exe netbios.sav 2. C>ren netbios.exe netbios.new 3. C>debug 4. -N netbios.new 5. -L 6. -E cs:49CA 7. -11 xx 01 yy (the last two digits of the hex number you computed above become xx and the first two digits become yy.) 8. -W 9. -Q 10. C>ren netbios.new netbios.exe .h2;Shutting Down the Server Using the full NetBIOS to execute a 3F shutdown causes NetBIOS to display: Share server not responding or Transmission error but properly shuts down the server. .h1;Token Ring Networks for 3+ Version 1.2.1 With 3+ Version 1.2.1, all Token Ring adapters have new drivers. This change provides: An industry standard method for SNAP (sub network access protocol) headers on token frames. The capability for third-party vendors to communicate with 3Com Token Ring networks (as has been possible with Ethernet networks). NOTE: The new Token Ring drivers are not compatible with Version 1.0 or 1.1 drivers. This means all workstations and servers must have drivers upgraded to version 1.2.1 at the same time. .h2;Installing the TokenLink Driver The driver for the TokenLink card is shipped with the card, and is not on the 1.2.1 3+ Installation #1 (Drivers) diskette. Instructions for modifying the CONFIG.SYS file to load the new TokenLink driver are in the TokenLink Installation Guide. .h2;Updating Token Ring Drivers All 3+ adapter drivers except the driver for the TokenLink card are on the 3+ Installation #1 (Drivers) diskette and are loaded automatically when you install 3+ Version 1.2.1 software. (The version number for the new drivers is either 3.0 or 3.0.1, depending on the driver.) .h2;Updating Server ROMs 3Server3s with ROM level G10 and a Token connection work unmodified with 1.2.1 software. 3Server3s with ROM levels below G10 require an upgrade to ROMs of at least level G10 to use the new Token Ring drivers. 3Servers with a Token connection must upgrade to D10 ROMS. .h2;Getting an Upgrade Kit The Token Connection 1.2.1 Upgrade Kit is available from your local reseller, or you can call 3Com Customer Relations, (1-800-876-3COM). If you call, specify whether you have a 3Server3 or a 3Server. Installing an IBM Token Ring and the Intel AboveBoard 3Com software utilizes the Intel AboveBoard as expanded memory rather than extended memory. This may cause the physical address of the AboveBoard to conflict with the address of the IBM Token Ring Adapter I or Token Ring Adapter II cards (because as expanded memory, the physical address of the AboveBoard is below the 1 megabyte address range). To change the starting address of either of these IBM Token Ring Adapter cards, change the setting of switch block 1. If you are using the Intel AboveBoard, change the switch setting to put this starting address to A0000h (at the 640K boundary). To set switch block 1 for this address, switch 2 must be off, switches 1 and 3-6 must be on (Switches 7 and 8 control interrupt levels) For instructions about changing switch settings and interrupt levels, see IBM's Guide to Operations, Token Ring Network Adapter Hardware Reference Library. NOTE: The IBM Guide to Operations, Token Ring Network Adapter Hardware Reference Library describes address space availability as if the space is used by only two (primary or alternate) addresses. In actuality, any of 64 addresses above the half megabyte boundary (8000h) can be used. The two addresses referred to in the IBM guide are the addresses of the default primary and alternate board addresses (as shipped by IBM).