Ref: 99980151 Title: EtherSeries Information Date: 9/1/85 Copyright 3Com Corporation, 1991. All rights reserved. The Technical Services Bulletin is distributed monthly to provide the latest technical information to 3Com customers to enhance support of EtherSeries users. .h1;RENAMING PRINTER PROBLEM WITH ETHERPRINT 2.4.1 In reconfiguring a printer, if the user renames the printer with a name having ONE LESS character than the previous name, the error message "CAN'T CREATE PRINTER DATABASE" or "BAD PRINTER DATABASE ... TRY RE - INSTALLING ETHERPRINT" will be displayed. This indicates the reconfiguration did not execute properly. Type "ESC" fourtimes. Then type "R" followed by another "ESC". Now reconfigure the printer specifying a name of greater length than the previous name, or at least 2 two characters less. .h1;USING ETHERSTART WITH DOS 3.1 As per the EtherStart manual (page 1 - 1), EtherStart is compatible with PC - DOS version 2.0 or 2. 1. There is new USER software which will allow an EtherStart volume to be created using DOS 3.l. This software does NOT work with DOS 3.0, nor does it work on an IBM AT. The new software is necessary when using EtherStart with some of the newest IBM XT's. These new USER diskettes are now available; the 3Com product number Is 3C50OU/A. .h1;INSTALLATION OF 3SERVER 2.4.1 SOFTWARE To ensure a successful installation of 3Server Release 2.4.1 software, follow the procedure outlined below. A problem WILL occur during the installation or re - installation of the 3Server application software upgrade, Release 2.4.1 (EtherShare, EtherMall, EtherBack, EtherPrint and System software), if done through the administrative menu per the instructions in the 3Server manual. The following procedure MUST be adhered to: 1. Set the key switch to TEST mode, turn the thumbwheel to POSITION 4, and depress the RESET button. 2. Insert Version 2.4.1 System Software diskette (must use) into drive A of the computer you intend to use as the console on the network. Set the default drive to A:. 3. Type ECONSOLE /START, and wait for the start request. Type "Y" and wait for the LCD message "REMOTE ACTIVE". 4. Type a carrriage return to disply the A > prompt. 5. Insert EACH application diskette and type "AINSTALL" from drive A, starting with the System Software diskette. .h1;3SERVER POWER REQUIREMENTS Power requirements for the 3Server and peripherals are as follows: Base Unit - 150 Watts Expansion Disk Unit - 70 Watts Expansion Tape Unit - 70 Watts The Base Unit figure shown above remains the same if you add a Memory Expansion Board and/or a Port Expansion Board. It Is a good practice to ensure that a system is connected to a power source that can provide the required power with a safety margin of 25%. Thus, if you have a 3Server and Tape Unit, the power source should be rated at a minimum of 275 watts. .h1;ETHERSTART ON IE4 BOARDS The jumper used to enable the EtherStart ROM may be confusing. This jumper is labelled "MemEnab" for Memory Enable and may appear as though the top two pins should be numbered in order to enable the ROM. In fact, the BOTTOM TWO PINS SHOULD BE JUMPERED TO ENABLE THE ROM. The pin closest to the label, Mem Enah, should be left unjumpered in order to enable the ROM. If the jumper is in the wrong position when using EtherStart, the PC will end up in BASIC when powered on. All of the boards are shipped with the Memory Enable jumper in the disabled position. As part of the EtherStart installation, the jumper must be changed to the ENABLE position. .h1;CROSS - LINKING TO OTHER SERVERS Each user name on the network is physically created on a server and has volumes which reside on that server. It is possible to have up to 40 different servers on your network, each with its own group of user names and related volumes. Cross -linking is the ability to access information in (public or shared) volumes that reside on a server or servers other than where your user name is created. EtherShare has limitations to the number of users that can be created and logged in at the same time. The matrix below shows this information for 3Servers and PC Servers using 2.4. (For a complete matrix, see Customer Care Bulletin, February 1985.) Maximum created users 3Server - 100 PC Server with ES 2.4 - 50 Maximum logged - in users 3Server - 50 PC Server with ES 2.4 - 20 The maximum number of users that can be logged in at one time includes cross -links. A cross - link always counts as another user logging in. For example: Assume a network with 2 PC Servers (SERV1 and SERV2), both running ES 2.4. A user logs in and establishes some links as follows: es login userl USER1 logged in to SERV1 es link d: serv2.sys2 SERV2.SYS2 linked to D: [cross - link established] es link e: serv2.program SERV2.PROGRAM linked to E: The status of each server is now as follows: SERV1 - 1 user logged in, 0 volumes linked SERV2 - 1 user logged in, 2 volumes linked A second user logs in and establishes links: es login user2 USER2 logged in to SERV2 es link d: sys.sys2 SERV2.SYS2 linked to D: es link e: serv1.files USER1.FILES linked to E: [cross - link established] The status of each server is now as follows: SERV1 - 2 users logged in, 1 volume linked SERV2 - 2 users logged in, 2 volumes linked As shown in the above examples, once a user has established a cross - link to another server, he can link to multiple volumes on that server and still be counted as only one user logged in. Also note that both users have linked to the volume SERV2.SYS2; however the total number of volumes linked for SERV2 shows as two instead of three. A volume is only counted as linked once. Multiple users may link to the same volume without increasing the linked volume count in the server's status. .h1;CREATING A PAGE BREAK WHEN COPYING FILES When copying files to the printer through DOS, a Control L (-L) may be used to put a page break between files (see the EtherPrint User Guide, page 3 - 8). There are two ways to do this. Example: Files to be printed will be FILE1.DAT and FILE2.DAT. The file created in BASIC will be P (BASIC will name it P.BAS). METHOD 1: At the prompt, type: COPY CON: PRN ^L (CNTRL L) F6 (function key 6) Example: COPY FILE L.DAT PRN COPY CON: PRN ^L (CNTRL L) F6 (function key 6) COPY FILE2.DAT PRN METHOD 2: You may write a BASIC program which will do this. The BASIC program should be as follows: 10 LPRINT CHR$(12) 20 SYSTEM SAVE"P Example: COPY FILE1.DAT PRN BASIC P COPY FILE2.DAT PRN METHOD 2A: You may create a batch file which will will run the BASIC program. copy con p.bat basic p F6 (function key 6) Example: COPY FILE1.BAT PRN P COPY FILE2.BAT PRN .h1;CONFIGURING OTHER SERIAL PRINTERS 3Server EtherSeries 2.4.1 provides the means for configuring other serial printers. This version provides a new selection on the EtherPrint reconfiguration screen called "Other Serial" and implements standard XON/XOFF software handshaking protocol through the software. No hardware handshaking has been implemented; all serial printers must support XON/XOFF in order to be configured on the 3Server. Baud Rate, Parity, Data Bits, Stop Bits When the "Other Serial" selection is chosen from the printer reconfiguration screen, the user is prompted for the reset sequence which must be entered in octal. The user is then prompted for the serial printer mode parameters which must be entered in a string listing the baud rate, parity and data bits, each separated by commas only. Each of these parameters must be present in the correct order, separated by a comma, free of spaces and other extra characters. The parameter string is ended with a carriage return. Example: 9600,N,7,1 XON/XOFF Software Handshaking The XON/XOFF protocol controls the flow of data to the printer by acting as a toggle, toggling off and on the flow of data from the 3Server to the printer. The 3Server begins and continues to send data to the printer until it receives an XOFF (HEX13) character from the printer. This XOFF indicates to the 3Server that the printer's buffer is nearly full and the 3Server should discontinue sending data. The 3Server discontinues sending the data but continues to poll the printer for an XON (HEX 11) character. The XON indicates that the printer's buffer is either empty or nearly empty and that the 3Server may resume sending data. When the 3Server sees the XON, it continues to send the data until it receives an XOFF or until there is no more data to send. Only printers configured to support XON/XOFF can be used. If the printer does not support this handshaking,the 3Server will overflow the printer buffer and the result will be loss of printed data. The 3Server cannot be configured to support any other type of communications between the printer and the 3Server. Serial printers are most commonly set to the XON/XOFF mode by switches found on the printer. Consult your printer manual, your printer manufacturer or your dealer to learn how to set your printer to the XON/XOFF mode. Reset Sequence A reset sequence is a string of control codes that will be sent to the printer before each spooled print job is printed. The purpose is to reset the printer to a default state before the next job is printed. When you select "Other Serial" from the EtherPrint Reconfiguration screen, you will be prompted to input a reset sequence. This reset sequence must be entered in 3 - digit octal codes separated by a slash (i.e., ESC would be entered as \027 and ESCI; would be entered as \027\111\073). Printer manuals list their control characters and the features each character supports. A reset sequence is usually a combination of control characters. The first control character(s) represents the actual "reset" command which sets the printer to a default state (see the printer manual for a description of the printer's default state). Other control characters can be added to the reset sequence to turn on specific printer features. These features are optional and are determined by the desired results of the end user. RS232 Cable Configuration A serial cable is required to connect a serial printer to the 3Server serial port. The 3Server has been designed to comply with FCC regulations for radio frequency emissions. Any cables attached to the 3Server must be FCC compliant shielded cables. The 3Server end of the serial cable must be a female DB - 25 connector. The signal connections are as follows: 3Server Cable End Printer Cable End TXD pin 2 connects to RXD pin 3 RXD pin 3 connects to TXD pin 2 GND pin 7 connects to GND pin 7 Your cable must have this configuration in order for the 3Server to send data to the printer. If your printer requires other pin connections, the 3Server will not support it.