Title: CoSession Technical Bulletins Compiled Updated: 03/12/96 Analyst: dczw This bulletin presents technical information about one topic related to your LANtastic network. Bulletins are available to help you with many aspects of managing or enhancing your network and with the installation of many compatible products. Bulletins are available: By fax from the Artisoft FaxReturn System at (520) 884-1397; request document 2 for a current list of all available bulletins, document 2001 for a list of compatible applications and other software, document 2044 for a list of compatible network interface cards and other hardware; Through the Artisoft Home Page http://www.artisoft.com on the World Wide Web; As ASCII text or Acrobat Text Enriched (PDF) files from the Artisoft Arti-Facts BBS at (520) 884-8648 (1200 baud - 28.8 Kbps, 8 data bits, 1 stop bit, no parity, full duplex), the GO ARTISOFT forum on CompuServe, or the Artisoft anonymous FTP site ftp.artisoft.com; download !BLTXREF.TXT from the BULLETIN section for a current list of all available bulletins, APPCOM.TXT for a list of compatible applications and other software, NICCOM.TXT for a list of compatible network interface cards and other hardware. Credits: DMB - Dina M. Barreto GN - George Nicewicz MAD - M. Anthony DiNatale KMR - Kevin M. Russell EKK - Elizabeth K. Krumov MJR - Michael Ruszkowski AP - Anthony Pelliccio AHT - Albert H. Thompson CHS - Chris H. Shuster TB#10100 14,400 BPS Modems Versions : 6.1j or earlier KMR 4/20/93 Setting the baud rate for high speed modems can be tricky. Since these modems are all advertised as 14,400 bps modems, it seems only natural to select that as the baud rate. Unfortunately, these 14,400 modems will not understand data if it is sent to them at 14,400 bps. The chip sets of these modems do not allow the modem to operate at this speed. The modem manufacturers will tell you that the most optimum setting is 38,400 or 57,600 bps. What they don't tell you is that some serial ports do not support these high speed connections. In order to get the best performance out of your high speed modem you should set the baud rate to 19,200 or 9,600 bps. If you know that you have a 16550 UART chip on your serial port, you can set the baud rate to 38,400 bps or above. TB#10101 General Modem Information KMR 4/20/93 Updated By MJR 1/25/96 OVERVIEW When installing CoSession there is some basic information about your modem that you must know in order to install it successfully. This information is, * What Com Port the modem is connected to. * If it is an internal modem, what IRQ the modem is using * What baud rate the modem is capable of. * What brand or type of modem you are using. You will need this information during the CoSession installation process. If you are unsure and you insert the incorrect Com Port or IRQ, it may cause your machine to lock-up when you attempt to run CoSession. If it is possible please verify this information before running the install. COMMON PROBLEMS What modem to select in CoSession if your modem is not listed... * We try to keep our modem selection list up to date with the most current and newest modems on the market today. If your modem is not listed, there are some generic modem types you should try. If it is a 2400 baud modem you can try either the Hayes Standard, or the Generic 2400. If it is a high speed modem, a 9,600, 14,400 or 28,800, choose either the Hayes Ultra or the Generic High Speed. * CoSession also supplies Custom 1 through Custom 8 which is where you are able to create your own modem control scripts. This should be the last option if one of the generic strings does not work. When loading Host, an error message is returned saying Unsuccessful Wait Dial-in Set... * This message means that CoSession could not set the modem to Auto Answer mode. This is usually because CoSession is not correctly configured. Check the Port number, the Baud rate, and the Modem type that are set in the Host's default phone book entry. If the port and baud rate are correctly set, try changing the modem type to a generic setting as listed above. When attempting a call from Remote, an error message is returned stating Unsuccessful Connection Attempt... * This message means that CoSession was unable to communicate with the modem. This is usually because CoSession is not correctly configured. Check the Port number, the Baud rate, and the Modem type that are set in the Remote's default phone book entry. If the port and baud rate are correctly set, try changing the modem type to a generic setting as listed above. After making the call the modems connect but CoSession returns an error message saying Login Failed Remote Wait Time Out Response... * This message is returned by the Remote generally because it does not receive a response from the Host that it is trying to connect to. The most common cause of this is that the modem on the Host is incorrectly set in the phone book entry. Change the modem type to a generic setting and try making the connection again. * If the modem type is already at a generic setting and you still have the problem, try lowering the baud rate to 2400 bps and try reconnecting. This problem may also be caused by noise being introduced on the telephone line which then causes the data coming back from the Host to be inaccurate or lost during transmission. * The modem is in a AutoAnswer mode but CoSession Host is not in a Wait-for-Call state yet. After making the call the modems connect but CoSession returns an error message stating, Login Failed Login ID Not Accepted... * This message is only returned if Password Protection is set to 'YES' on the Host, and the Login and Password that the Remote is sending do not match with those specified on the Host. The first thing to do is to turn Password Protection to 'No' under the Security options in the Host options menus. With this set option set to 'No' you should get connected. If you do get a connection go back and check to make sure that the Login and Password in the Sending phone book of the Remote entry match exactly with those in one of the Host's phone book entries. (Login and Password are case sensitive) TB#10102 Windows 3.x Information Versions : Host & Remote 6.1s or earlier, ACS Host & Remote 6.2a or earlier, X.25 Host & Remote 6.1k or earlier, Lan II Host & Remote 6.2e or earlier KMR 4/23/93 Overview In order to run Windows remotely while using CoSession the following requirements must be adhered to... Display driver must only display a maximum of 16 colors. Host must be allowed to update the Windows System.ini file. CoSession Windows driver files are copied into the Windows\System directory on the Host. Host is loaded outside of Windows at the DOS prompt. Driver Installation CoSession will update the Windows System.ini file, and will also place drivers in the Windows\System directory on the Host. The CoSession drivers start with the characters CS$. The Host installation program will use C:\Windows as the default when adding the drivers to the System.ini file, and C:\Windows\System as the default directory for placing the driver files. If your windows setup is different, make sure you enter the correct Drive and Path to your Windows files during the installation. Network installations of Windows have a user or home directory where the System.ini file and other essential Windows configuration files are stored. This is where the Host installation program must make the changes to the System.ini file. Network installations also have a single directory where all of the driver files used by Windows are placed. It is in this directory where the CoSession driver files must be copied to because this is where Windows has been pathed to look for its drivers. Common Problems: Mouse Problems : Host Mouse is not working within Windows... During the Host installation, a line called HostMouse= is added to the Windows System.ini file. The driver that is pointed to by this line must be in the Windows\System directory for the mouse to work within Windows. If the driver being pointed to is not present, copy the Mouse.drv file to the name of the driver pointed to by the Hostmouse= line in the System.ini file. If the Host machine has a Serial Mouse, take out the Device=*VMD, or Device=*LMD if you have a Logitech mouse. Remote Mouse not working within Windows... In order for the Remote user to have mouse control they must have a Mouse.com, or Mouse.sys driver resident in memory before Remote is loaded before connection. Also check to insure that the mouse does not share the IRQ with the Modem. This may cause the mouse to function improperly when a connection is made to the Host. Lastly Remote Mouse Operation must be set to 'YES' in the under Hardware in the Remote Options Menu. Blank Screen on the Host when Windows is loaded in Standard mode without a connection to the Remote... Check to see that the HostMouse= line in the System.ini file is not equal to Mouse.drv. If it is, rename the Mouse.drv file to Cmouse.drv, and then place it into the Windows\System directory. Then change the HostMouse= line to Cmouse.drv. Check to see if the driver that HostDisplay= is pointing to is a 16 color display driver. If you are unsure how many colors it is displaying, change the value of HostDisplay= to Vga.drv, or Supervga.drv, and place that driver in the Windows\System directory. Blank screen on Host when Windows is loaded in 386 Enhanced mode with a connection to the Remote... Try running Windows in standard mode with a connection to see if it works in that mode. If Windows does not load please follow the steps listed above. If Windows does load, replace the Device=CS$VCD.386 line in the 386ENH section of the System.ini file with Device=*vcd. If Windows still will not run after the Device=CS$VCD.386 driver has been replaced, remove the Device=CS$CBUF.386 line with Device=*combuff. Then restore the Device=CS$VCD.386 to the System.ini file and remove the Device=*vcd, the ComXBASE and the ComXIRQ lines. Windows loads on the Host, but the Remote screen stays blank... Check to see if the Display.drv= line in the Boot Section of the System.ini file is pointing to CS$DISP.DRV. If it is not, change the value of Display.drv= to CS$DISP.DRV. Make sure RWIN.EXE was loaded on the Remote before the connection to the Host was established. Remote display of Windows screen is garbled or the colors are incorrect... Be sure the Remote display adapter can display the resolution graphics that the Host is displaying. If it cannot handle the resolution the colors will not display properly. Turn Keyboard and Screen Error Correction to 'YES' in the Remote Options Menu under Performance. Try lowering the baud rate to the next lower speed if there is a modem connection. Sometimes line noise or data overruns will cause incorrect screen images. Windows communication packages will not operate after CoSession modified the System.ini file... Try replacing the Device=CS$VCD.386 line in the 386ENH section of the System.ini file with Device=*VCD. Also add the following two lines: ComXBASE=-1 and ComXIRQ=-1 also in the 386ENH section. In both lines the "X" represents the comport the modem is on. When Windows is run an error stating that an Invalid Linkcall to VxD has occurred... Check to see that the CoSession driver files are correctly installed into the Windows\System directory. Choppy or rubber band mouse control on the Remote side... Check to see if the mouse driver that you are using is the current Windows 3.1 driver. The current Microsoft Mouse.drv file is approximately 10,762 bytes. The current Logitech Lmouse.drv file is approximately 12,000 bytes. When Windows loads an error occurs with the Pointer.exe program stating that the Microsoft Mouse Driver must be the 8.2 version... Currently the changes that CoSession makes to the System.ini file are not compatible with the Pointer.exe program. Support for this program should be added in later versions. Windows 3.x Information TB#10103 CoSession ACS Information AP 4/23/93 You CANNOT load the Host and/or Remote that came in your ACS package on a STANDALONE machine. These are not CoSession Asynch versions, but special INT14 versions. You must purchase Asynchronous Remote/Host, which have options available for connections with ACS Remote/Host. The PC that will act as your CommServer, will also be called the Mshare machine. STEPS TO FOLLOW Initial Set-Up Done by Supervisor NOTE: (The following two commands need to be done by the supervisor or a supervisor equivalent because of the need for full rights to the network) LMCONFIG is the first program to be run. This is where you define your modems and all information concerning the modems. Then run MTRUSTEE*, and insert the number of modems to be used. i.e., if you have a CoSession 2 Modem ACS, You'll have the following in your Mtrustee menu: LanMODEM01 LanMODEM02 * Note - Skip this Mtrustee command if you are on a Net BIOS Network. NOTE: (The following commands DO NOT require a supervisor or a supervisor equivalent) MSHARE Mshare comes with three loading options: MSHARE /g This puts Mshare in a Gateway mode. This gives you the ability to put the modem into an Auto Answer mode, without tying up the modem, thus, being able to Dial Out while in an Auto Answer mode. MSHARE /i This instructs Mshare to allow the modem Dial In access only, no Dial Out access. MSHARE /o This instructs Mshare to allow the modem Dial Out access only, no Dial In access. Mshare tries to accommodate different sized networks. Additional commands: /alocal This instructs Mshare to look locally at the segment that the local FS is attached to, and your Mshare machine. /ahop="n" This instructs Mshare to search for FS "n" hops away from the Mshare machine. This command is used for large networks, with many segments. /lite This command is used when it's not desired to log fully onto the network. It does require IPX and NETX to be loaded though. If you run two different modems on the CommServer, you can tell Mshare which one specifically you want to initialize. Example: MSHARE /g=01 1, tells Mshare to initialize LanMODEM01 on COM1. MSHARE /g=02 2, tells Mshare to initialize LanMODEM02 on COM2. If loading more than one modem on one CommServer, you must preface the /g command with MSHARE /l="n". Example: MSHARE /l=2 MSHARE /g=01 1 MSHARE /g=02 2 Different than the above scenario, you can have two different machines running one modem each. In essence, you will have 2 CommServers (dedicated or non-dedicated, depending upon your choice). On each CommServer you would run the respective MSHARE /g or /i or /o command After loading Mshare, you should get favorable messages that the comport was found and your modem was initialized. To make sure of this, run MSHARE /s (status). It will come up with a box detailing the IRQ, Address and Status of the Mshare modems. You should see GATEWAY as a status, or, if you defined as /i, or /o, INBOUND and/or OUTBOUND. Once you get favorable responses from MSHARE /s, you are ready to run NETPORT and CoSession ACS Host or Remote (or your favorite third party INT14 Network version communication software). NETPORT You are now ready to load NETPORT on a workstation. The workstation you want to load Netport on could be the CommServer/Mshare machine or could be a workstation attached to the Mshare machine through the LAN. If You are Using CoSession Remote and/or Host ACS Load: NETPORT /l (Netport /l simply loads Netport into memory.)Then, ACS Remote and/or Host will open the port for you, giving you the ability to dial out through the shared modem.) REMOTE or HOST -L1st_PC (the "-L" after Host will allow you to designate certain PC's to the user. When a CoSession Remote Asynch or ACS Remote calls into this Host, the Remote user will see an AVAILABLE STATION LISTING box on their screen, with the certain PC highlighted as "01 1st_PC". This is most useful when calling into an Mshare with multiple Hosts waiting.) When using ACS REMOTE, you must also define the Phone Book to match the modem that you have designated in Lmcomfig. CoSession will use it's own SESSION.MDM file to initialize the modem and dial out. Keep the Port at 1 in the CoSession Phone Entry and it will automatically search up if the first port is busy. If You are Using a Third Party INT14 Package other than CoSession ACS Load: NETPORT /c="n" ("n" represents the LanMODEM number you wish to directly connect to. For example the command NETPORT /c=01 will attach you directly to LanMODEM 01.) Then load your Third Party INT14 software according to their manual. TB#10104 SessionXL Information DMB 5/11/93 You receive the error "Problem Loading Driver" The most common reason for this problem is that there is a CoSession Remote or Host already loaded on the PC that is trying to run SessionXL. You are having a problem connecting to the Host PC This problem should be looked at just as if the SessionXL was a CoSession Remote. Check the modem type and the ComPort parameters on both the SessionXL side and the Host and be sure they are correct. If all is fine then try to make a connection from a CoSession Asynch Remote to the Host and see if a connection is possible. The KEY commands are going to the Host too fast and keystrokes are being lost There are a few things you can do: * Try adding a /W# to the end of your KEY command in the job file. "#" represents the number of seconds to wait before going to the next command. * You can place PAUSE commands in between the KEY commands. For example try PAUSE S2 between the KEY commands to pause 2 seconds. * Lastly, there is a command line option that you can use when loading the SessionXL out at DOS. This command line option is - kx. The "x" is equal to 0 through 9 and represents the speed at which the KEY commands will be issued. 0 is the fastest and works its way to 9 which is the slowest. The default is 5. This command is wonderful when using high speed modems and the Host is a "slow" (10 - 16 MHz) machine. Using commands with H! and R! The H! and the R! actually mean the same thing when doing any commands that require them. In the earlier versions the R! meant the Host machine and in the newer versions the H! represents the Host machine. You get file transfer error using wildcards in the COPY command: Wildcards are allowed when specifying the SOURCE files but are not allowed when designating the DESTINATION files. If you have any wildcards for the destination files just delete them. For example: COPY C:\TEMP\*.* H!G:\USER1\*.* (This command will not work because of the ending *.*) COPY C:\TEMP\*.* H!G:\USER1\ (This is the correct command - note there is no ending *.*) TB#10105 CoSession X.25 Information DMB 5/11/93 ODI Drivers and ECXPAD If you are using ODI drivers and ECXPAD on the Host or Remote PC then you must make sure that you are using the very latest version of CoSession X25. This version is currently 6.1k or later. This allows for the use of ODI Drivers on the network. If you are not using the latest you may be getting errors such as ITI.SYS must be loaded. You are using ECXPAD on the Remote X.25 and you cannot make a connection to the Host X.25 If you are using ECXPAD on the Remote X.25 then you must be sure the Phone Book Entry you are trying to connect with is set for Manual instead of Automatic. You must then also use a CXL script to help complete the connection. A sample CXL script comes with the CoSession X.25 called X25.CXL. The Remote (X.25 or Asynch) gets a Waiting Login when trying to access the Host X.25 Be sure that the Host X.25 has issued the proper listen to the X.25 Eicon gateway. This can be verified by getting a status of the gateway. If the listen is registered with the gateway and you continue to get the problem then you should trace the connection. The way to do this is to begin the ECTRACE on the Host X.25 PC, make the connection from the Remote (X.25 or Asynch), get the waiting login error, disconnect from the Remote, and then view the ECTRACE that now exists on the Host X.25 machine. This will give you important information as to whether or not a valid connection is being made and if there is a connection what if anything is being sent back and forth. You want to use Call User Data on the Host X.25 In the Phone Book Entry (Default) you will need to set up Call User Data to later be detected by the CoSession Host X.25. The Call User Data is placed in the Receiving Login Field and must be 10 characters long with no spaces. The Host X.25 will then issue the listen to the gateway when it does the Wait For Call. However, on the command line of the Host you need to give it the -u parameter to tell it to look for incoming Call User Data, for example HOST -u. The Remote then is required to send across Call User Data when trying to connect. Connecting from Remote X.25 The Call User Data is placed in the Sending Login Field of the Remote's Phone Book Entry that is being used for the connection to the Host X.25. Connecting from Remote Asynch The Call User Data is normally paced on the line where you give the PAD the address of the Host gateway. The syntax and exact placement of the Call User Data is different depending on the X.25 carrier you have. Check with their manual for further details. TB#10106 Non-Dial Up Connections KMR 5/10/93 CoSession has two modem selections for non Dial Up links. One is Direct Connect and the other is Direct-Flow Control. These modem type options have specific uses and should only be used under the following conditions: * Direct Connect should be chosen as the modem type when the Host and Remote computers are attached with a null modem cable, or if they are using two modems that already have carrier established. * Direct-Flow Control should be used when either the Host or Remote is connected to a Multiplexer instead of a modem. With the Direct-Flow Control type selected, CoSession will tell the hardware (RTS/CTS) to perform the flow control instead of depending on software (X/ON X/OFF) to do it. TB#10107 Windows DOS APP KMR 5/10/93 On certain systems there have been problems reported when Remotely running full screen DOS applications under Windows. Certain video adapters can bank switch their video memory in such a way as to allow Windows to invisibly update its video in the second bank. When this happens Windows will not inform the display driver that the Windows video memory has been switched to the background, so CoSession Remote is not made aware of changes to the Host's display. A line can be added to the [386Enhanced] section of the Windows System.ini file which will solve this problem. That line is as follows: SysVMin2ndBank=FALSE TB#10108 Intelligent DigiBoards AP 7/2/93 The new version of CoSession ACS now works with Intelligent DigiBoards, as well as the Non-Intelligent DigiBoard. However, the setup is quite different. There is additional software to run as well as CoSession ACS. * You must first configure your intelligent DigiBoard according to it's manual. Unlike the Non-intelligent DigiBoad, there are no banks of dip switches to configure for each port. There are only two banks. One sets the IRQ and the other sets the memory address along with port address. You must make sure the IRQ and addresses are "free", so that no other devices or boards will conflict. This is explained in the DigiBoard manual. * Insert the 4, 8, or 16 port intelligent DigiBoard into your PC, J&L or Cubix environment. * You must now software configure your Intelligent DigiBoard. This .sys file will be added to your CONFIG.SYS and will initialize the DigiBoard upon boot-up of your processor. This is also explained in detail in the Intelligent DigiBoard manual. You will know if errors occur during boot-up. Below is an example on how to run CoSession ACS with your Intelligent DigiBoard: 4 Port Intelligent DigiBoard MSHARDIG /L=04 * MSHARDIG /DIGI=1 /TY=1 /M=A000 /H=100 /Q=7 ** MSHARDIG /G=01 1 MSHARDIG /G=02 2 MSHARDIG /G-03 3 MSHARDIG /G=04 4 * This line indicates how many DigiBoards are being used, it's type, the memory address you configured for it, the I/O address you configured for it, and the IRQ you configured for it. Unlike the Non-intelligent DigiBoard, the I/O address is the same for all ports on the board. ** This line tells MSHARDIG to locate LANMODEM01 (configured by you in LMCONFIG) on Com1 (Digiboard's P1). TB#10109 Non-Intelligent DigiBoards AP 7/2/93 CoSession ACS works very well with Non-Intelligent DigiBoards. There is no additional software required other than CoSession ACS. * You must first configure your Non-Intelligent DigiBoard according to it's manual. This board comes with banks of dip switches, with each dip switch bank corresponding to each port on the board. The lone larger bank is for the Status Port setting. The smaller banks are for the I/O port address settings. * After setting up the ports, the next step is to set the IRQ on the board. Again, the DigiBoard manual explains. * Insert the 4, 8, or 16 port Non-Intelligent DigiBoard into your PC, J&L or Cubix environment. Below is an example on how to run CoSession ACS with your Non- Intelligent DigiBoard: 4 Port Non-Intelligent DigiBoard MSHARE /L=04 * MSHARE /G=03 3 /q=7 /h=100 MSHARE /G=04 4 /q=7 /h=108 MSHARE /G=05 5 /q=7 /h=110 MSHARE /G=06 6 /q=7 /h=118 * This line tells MSHARE to locate LANMODEM03 (configured by you in LMCONFIG) on Com3 (DigiBoard's actual P1) with 7 as the IRQ and with the unique address of 100. Note: /G=03 pertains to LANMODEM03 in LMCONFIG and /G=04 to LANMODEM04 and so on. We start out this way in order to keep our PC's local Com1 and Com2 still available. For ease of use, you may run the above scenario in a batch file. This will eliminate input error if manually done, which will, in turn, eliminate periodic lock-ups. TB#10110 WAN Configuration Options for Netware GN 7/2/93 If you are having a problem connecting node to node with CoSession LAN II on a wide-area-network (WAN) you need to change settings in the NET.CFG file. The following is a list of notes that relate to options that can be modified in NET.CFG if the user is running CoSession in this environment. IPX RETRY COUNT = XX (Default = 20) This parameter sets the number of times the workstation re-sends a packet. On networks that lose many packets, this retry count may need to be increased. (suggest XX = 50) SPX ABORT TIMEOUT = XXX (Default = 540 ticks or 30 seconds) This parameter adjusts the amount of time that SPX will wait, without receiving any response from the other side of the connection, before it terminates the session. The time-out number is in ticks. There are 18.21 ticks per second. (suggest XXX = 850) SPX LISTEN TIMEOUT = XXX (Default = 108 ticks or 6 seconds) This parameter adjusts the time that SPX will wait, without receiving a packet from the other side of the connection, before it starts requesting the other side to send back a packet assuring the connection is still valid. If SPX has not heard from the other side of connection within this time, it will send packets to the other side asking for verification that the connection still exists. (suggest XXX = 850) SPX VERIFY TIMEOUT = XXX (Default = 54 ticks or 3 seconds) This parameter adjusts the frequency at which SPX sends a packet to the other side of a connection to inform it that its side of a connection to inform it that it's side is still alive. If no packets are being exchanged on the SPX connection by the software that established the session, SPX will send packets at regular intervals to make sure that the connection is still functioning. (suggest XXX = 540) TB#10111 Modem Set-up DMB 8/2/93 Updated By MJR 1/25/96 When using CoSession with a new modem or a modem that is not currently on our list, the user may wish to customize the initialization modem strings. The following will give you an idea of how to set-up modems from the very basic to the very complex. Note: Keep in mind that if you have a 2400 baud modem and it is not listed, CoSession provides a HAYES STANDARD or GENERIC 2400 setting that should work. If you are using a 9600, 14,400 or 28,800 baud modem that is not listed, the HAYES ULTRA or GENERIC HIGH SPEED setting should work for these modems. Both of these modem types set the modems up for factory defaults to allow them to perform at their fullest capacity. Note: All Hayes compatible modems offer an &F command that sets the modem to their factory default settings. In the higher speed V-Series modems this &F command is very useful. Check the manual and be sure to use the command if it carries the characteristics of the following three scenarios stated below. Place the &F towards the start of the initialize line in case you need to add other commands that contradict what the &F is setting up. BASIC MODEM SET-UP The following commands are used as the base for ALL modems, however it is the complete set-up string for 2400 baud non-error correcting modems. GENERAL * Initially the modem needs to be reset. This is useful just in case there is a "still active" connection it will disconnect the line for you. * The modem needs to be set for it to return verbose result codes. Anything that the modem sends to the screen will come back in words not numbers. * Enabling the result codes is important if there are any problems with the connection. * The DCD needs to track the state of data carrier from the remote modem. This is considered their normal setting. DCD should not be forced on, true, or ignored. * When DTR is dropped it must hang up the line and enter into command mode. This is also considered the normal setting. DTR should not be on, true, or ignored. * CoSession's modem set-up gives you three options in the bottom right corner. For low speed, non-error correcting modems they should be set as follows: Inter-Char Delay NO Fix Baud Rate NO H/W Flow Control NO SPECIFIC Initialize: ATZ\,ATV1Q0&C1&D2\;OK#3;] * Most all modem initialize lines begin with ATZ. The AT tells the modem that commands are to follow. The Z resets the modem. * The \ and the , are CoSession commands. The \ is a carriage return while the , is a two second pause. * V1 sets the modem for verbose result codes. * Q0 enables result codes. * &C1 allows DCD to track the state of data carrier from the remote modem. * &D2 monitors DTR and when it is dropped it will hang up the line and enter into command mode. MNP MODEMS The following commands are used by both 2400 and 9600 MNP modems. GENERAL * Initially the modem needs to be reset. This is useful just in case there is a "still active" connection it will disconnect the line for you. * The modem needs to be set for it to return verbose result codes. Anything that the modem sends to the screen will come back in words not numbers. * Enabling the result codes is important if there are any problems with the connection. * The DCD needs to track the state of data carrier from the remote modem. This is considered their normal setting. DCD should not be forced on, true, or ignored. * When DTR is dropped it must hang up the line and enter into command mode. This is also considered the normal setting. DTR should not be on, true, or ignored. * Set the modem for auto-reliable mode. The modem will attempt error correction but will fall back to normal mode if unable to establish an MNP link. * Enable bi-directional hardware (RTS/CTS) flow control. CoSession H/W Flow Control works in conjunction with this command. * Turns off the baud rate adjustment feature of the modem. This allows the serial port rate to be independent of the rate of the connection between the two modems. CoSession Fix Baud Rate feature work in conjunction with this command. * The bottom right corner should be set as follows: Inter-Char Delay NO Fix Baud Rate YES H/W Flow Control YES SPECIFIC A sample initialize line would be as follows: ATZ\,ATV1Q0&C1&D2/\N3/\Q3/\J0\;OK#3;] * Most all modem initialize lines begin with ATZ. The AT tells the modem that commands are to follow. The Z resets the modem. * The \ and the , are CoSession commands. The \ is a carriage return while the , is a two second pause. * V1 sets the modem for verbose result codes. * Q0 enables result codes. * &C1 allows DCD to track the state of data carrier from the remote modem. * &D2 monitors DTR and when it is dropped it will hang up the line and enter into command mode. The newer "extended AT" commands in this string relate to the use and ability of MNP modems. * \N3 sets the modem for auto-reliable mode. * \Q3 enables bi-directional hardware (RTS/CTS) flow control. * \J0 turns off the baud rate adjustment feature of the modem. Note: Before each extended AT command there is a /. This / is a CoSession command. It tells the modem that the very next symbol to appear is a modem command. If you did not put the / in front of the \ it would treat the \ as one of CoSession's carriage returns (as previously explained above). V.32bis & V.42bis MODEMS The following commands are for V.32 & V.42bis and non-bis modems. GENERAL * Initially the modem needs to be reset. This is useful just in case there is a "still active" connection it will disconnect the line for you. * The modem needs to be set for it to return verbose result codes. Anything that the modem sends to the screen will come back in words not numbers. * Enabling the result codes is important if there are any problems with the connection. * The DCD needs to track the state of data carrier from the remote modem. This is considered their normal setting. DCD should not be forced on, true, or ignored. * When DTR is dropped it must hang up the line and enter into command mode. This is also considered the normal setting. DTR should not be on, true, or ignored. * Set the modem up with its factory default settings. In the V-Series modems (as stated in the above note) this is a useful command so as not to have to input every command manually to the modem. Most of the necessary commands are defaults and the &F will take care of this for you. * Allows all necessary result codes to be echoed to the user. * Enable the use of hardware (RTS/CTS) flow control. * Select error control mode of operation with the ability for negotiation fallback to normal mode if necessary. * The bottom right corner should be set as follows: Inter-Char Delay NO Fix Baud Rate YES H/W Flow Control YES SPECIFIC Here is a sample initialize line: ATZ\,ATV1Q0&FX4&C1&D2&K3&Q5\;OK#3;] * Most all modem initialize lines begin with ATZ. The AT tells the modem that commands are to follow. The Z resets the modem. * The \ and the , are CoSession commands. The \ is a carriage return while the , is a two second pause. * V1 sets the modem for verbose result codes. * Q0 enables result codes. * &F sets the modem up with its factory default settings. * X4 allows all of the necessary result codes to be echoed to the user. * &C1 allows DCD to track the state of data carrier from the remote modem. * &D2 monitors DTR and when it is dropped it will hang up the line and enter into command mode. * &K3 enables the use of hardware (RTS/CTS) flow control. * &Q5 selects error control mode. TB#10112 Network Drive Mapping KMR 7/8/93 When using CoSession it is important that the Host TSR segment always have access to the directory, and drive where its files have been installed. This is especially relevant when Host is installed on a network drive. With CoSession on an network drive, be sure that the drive and volume where CoSession was loaded from is the same throughout the connection. As an example, the Host progam may be stored in F:\Login\Host, on the System Volume of the network. At the time of loading, CoSession is fine because the network mapping points to F:\Login on the System Volume. A problem may arise later if a user calls in and loads an application that switches the network volumes to Volume1. This may change the drive mapping of F: to point to a different directory structure that does not include \Login\Host. When CoSession then tries to access it's files, it will not find the directory, which will result in inconsistant performance. This can be avoided by assuring that the home directory of CoSession is consistantly mapped to the correct drive and network volume where it is stored. TB#10113 Desqview MAD 7/07/93 The "read-me" file that comes with the CoSession Host software describes how to set-up Host within a Desqview Window, however, the settings for loading Desqview after Host are slightly different. In the Host's Options program Special Keyboard Handling must be set to YES. You must also modify the User Setup File for Desqview. This is done in different ways depending on the environment. DesqView is run in a network environment * Run SETUP * Select PERFORMANCE * Change : Keyboard - Maintain Separate Shift States = YES * Save the file in the user's sub-directory on the network. The saved file is called DVSETUP.DV DesqView is run on a stand-alone PC * Run SETUP * Select PERFORMANCE * Change : Keyboard - Maintain Separate Shift States = YES * Save the file on the user's hard-drive. The saved file is called DVSETUP.DV TB#10114 X.25 Transparency Issues DMB 8/27/93 One of the most common scenerios used with CoSession X.25 is to have an Asynchronous version of CoSession dialing into the CoSession X.25 Host. This would mean that the Remote is dialing into a public or private PAD. Transparency is a key issue when you are dialing onto an X.25 PAD. This is achieved by properly setting the X.3 parameters of the PAD. Transparency in most X.25 PADs is done as follows: All parameters should be set to 0 except for parameter 4 which is set to 1. Configuring the PAD for the settings above is different depending on the carrier of the X.25 network. In some cases you must send all the parameters individually to the PAD with the SET command, i.e. SET 1:0,2:0,3:0,4:1,5:0,etc... On the other hand there may be a "transprency parameter" and all you need to send is a SET 33:0; where, 33 is the parameter for transparency and setting it to zero should be enough. TB#10115 OS/2 Tips KMR 8/27/93 Although CoSession does not support running in the OS/2 environment, testing, done by customers, has found that on certain systems CoSession will run in a OS/2 DOS box. If you plan to use CoSession in this scenario it is suggested that you use the -UX option when loading both the Host and Remote programs. This option sets CoSession to only allocate convention memory and has been found to be more stable while using it. TB#10116 Host Batch File Execution KMR 8/27/93 Executing CoSession Host from a batch file can sometimes be tricky. The problem is that Host may not have finished setting up the modem before the next DOS command is executed in the batch file. Dealing with this problem however is simple. The first thing you should do is set Auto Answer on Loading to 'NO' in the Options menus under the Connect section. Then modify the batch file to execute the following : CD\Host Host Host -Aphonebook_entry_name What these lines will do is first change to the Host directory. Second load Host so that it becomes resident in memory. And lastly, tell Host to go into a Wait For Call under the specified Phone Book Entry. This method of execution will ensure that CoSession has adequate time to prepare itself for incoming calls before the next DOS statement is executed. TB#10117 Using DOS Edit KMR 8/30/93 In order to use the DOS Edit program when remotely controlling a Host PC, you must have Special Keyboard Handling set to YES on the Host. This option can be found under the Hardware selection in the Options program. With this option enabled the remote user will be able to use the Alternate Key to manipulate the menu functions of Edit. Without this option, enabled only the Remote mouse will be able to utilize the menus of Edit. TB#10118 Disabling the Blink Register MAD 7/09/93 Certain programs affect the blink bit status of the video to display differences in a program. CoSession Host and Remote reset the blink bit upon loading. To have CoSession not reset the bit, load Host or Remote with a "-o32768" command line option. TB#10119 Boca 14.4bps Modems MAD 07/15/93 If you have a Boca 14,400 baud modem and are having problems where the modem is constantly re-training itself upon a connection you need to have the modem modified. Open the modem and examine the ROM chip, it will have a version number on it. If it is ROM version "V 1.20", then contact Boca Research for an updated ROM chip which will upgrade the modem to a version "V 1.27" ROM chip. TB#10120 Path Restriction for CoSession KMR 8/30/93 When creating a directory to install CoSession, the length of the path for that directory must be less than twenty characters. For example, C:\Apps\Comm\CoSession has a path length of 22 characters, which is not valid for the installation of CoSession. If the path exceeds twenty characters, CoSession will not be able to find it's files once it's loaded as a TSR, and will cause CoSession errors to occur. TB#10121 CD Drops when Windows is Executed KMR 8/30/93 If a DOS application, like CoSession, is actively controlling a serial port when Windows is run in enhanced mode, Windows will disrupt the serial port and cause the modem to disconnect. This problem can be remedied by adding three lines to the "Enhanced" section of the System.ini file. These three lines are as follows: ComXAutoAssign=0 ComXBase=-1 ComXIRQ=-1 * X is eqaul to the serial port that the modem is using. These three lines attempt to fool Windows into looking for the serial port at a different Address and IRQ than where it is actually located so that it will not be disrupted. TB#10122 Flow Control XON/XOFF MAD 07/15/93 XON/XOFF (Software flow control) sends a signal from one system to the other by adding bits to the data stream. The receiving system responds by suspending the transmission of the data or resuming the flow of data. XON turns the data flow on, XOFF turns it off. Flow control prevents loss of excess data. CoSession uses the following: XON Hex 11 91- XOFF Hex 13 93- (Both High Bit) CoSession is transparent to this. If Hardware flow control (RTS/CTS) is set to NO, then CoSession will utilize the XON/XOFF flow control. TB#10123 GDI Error With Windows KMR 12/28/93 If you have recently upgraded from an earlier of 6.1 to the latest version of CoSession, you may run into a problem with running Windows. You may receive a GDI Error when loading Windows after the install of the new CoSession Windows drivers. This is because the latest CoSession Windows drivers do not change the display.drv and the mouse.drv lines in the System.ini file. In the previous versions these lines were changed to incorporate CoSession drivers. If these drivers are placed in the System.ini file, and the new drivers are installed in the Windows\System directory, you will receive this GDI error. In order to fix this you will need to copy the value of the HostDisplay line to the display.drv line, and then copy the value of the HostMouse line to the mouse.drv line. Once these values have been changed, you can then remove the HostDisplay and HostMouse lines from the System.ini file. With these lines changed this error should clear up. Example : Existing Lines Change to HostDisplay=vga.drv display.drv=cs$disp.drv display.drv=vga.drv HostMouse=mouse.drv mouse.drv=cs$mouse.drv mouse.drv=mouse.drv TB#10124 Arnet Multiport Boards AP 12/28/93 CoSession ACS now supports Arnet Corporation's Multiport Serial Port Boards (the 4 and 8 multiport boards). These boards are NON-INTELLIGENT and do not require any additional software for configuring. In the Arnet User's Manual, refer to page 57 (Appendix B) for MS- DOS Setups. You'll note that out of the 3 sets of DIP switches, you'll only use 2 sets; UART I/O address and the IRQ selection. The other set for I/O addresses is not used with CoSession ACS. If the settings found on page 57 are not viable with your computers' configuration because of address/IRQ conflicts, refer to page 59 (Appendix C) for optional UART addresses and page 67 (Appendix E) for optional IRQ selections. Since all of the UART I/O addresses are in hexadecimal format, you must follow this format in succession when configuring MSHARE. Example: if you were to choose UART I/O address of 100h and IRQ 7: MSHARE /L=8 (tells MSHARE that up to 8 modems will be loaded) MSHARE /G=01 1 /Q=7 /H=100 MSHARE /G=02 2 /Q=7 /H=108 MSHARE /G=03 3 /Q=7 /H=110 MSHARE /G=04 4 /Q=7 /H=118 MSHARE /G=05 5 /Q=7 /H=120 MSHARE /G=06 6 /Q=7 /H=128 MSHARE /G=07 7 /Q=7 /H=130 MSHARE /G=08 8 /Q=7 /H=138 /G="n" - is the corresponding LANMODEM set up in LMCONFIG /G=n "n" - is the corresponding PORT (octagon cable, D-sub connector box, or RJ 45 connector block) that Arnet supplies with the board One additional note: CoSession ACS ONLY supports 1 (one) non-intelligent Multiport board at a time in 1 (one) PC. If you were to utilize the entire 8 ports of the board, you would NOT be able to use your local PC's comports for additional modem support. TB#10125 SessionXL SDRIVER Share Violation Error KMR 12/30/93 In some cases the DOS program Share.exe has caused problems with the Sdriver.exe program that SessionXL uses. If Share is loaded in your machine you will get a Share Violation Error when you attempt to load the Sdriver.exe program. To eliminate this problem you should do the following: * Remove Share from your Autoexec.bat file * Reboot your machine * Flag the Sdriver.exe file with Attrib command as Read Only * Place Share back into the Autoexec.bat file * Reboot your machine * Problem should now be eliminated TB#10126 Supporting the Pointer Program Versions : Host 6.03 - 6.1s, ACS Host 6.02 - 6.2a, X.25 Host 6.0 - 6.1k, Lan II 6.02 - 6.2e AHT 2/25/94 Last Update By KMR 5/23/94 Problem : With earlier versions of our CoSession software (6.1s or earlier) some customers have reported that while attempting to run Windows, they have received the following error message: This version of Pointer.exe requires an 8.2 or later Mouse driver. The Cause for the Error Pointer.exe is looking specifically for the mouse.drv driver, which was previously changed to cmouse.drv by the CoSession installation. Upon not finding this mouse.drv driver Pointer.exe returns the stated error message. The Fix We currently do not support the Pointer.exe driver. There are two solutions: You may choose to simply ignore the error message and bypass it when entering Windows. Get rid of the error message by editing the Win.ini and removing the Pointer.exe from the Load line. NOTE: The two fixes above have no affect on the running of Windows. NOTE: Our newest version of Windows drivers (that come with CoSession version 6.1x or later) no longer have this problem. TB#10127 Windows Won't Run After Installing CoSession for DOS Host Versions : Host 6.03 - 6.1s, ACS Host 6.0 - 6.2a, X.25 Host 6.0 - 6.1k, Lan II Host 6.02 - 6.2e MJR 2/25/94 Last Updated by KMR 5/23/94 Problem : In order to remotely control Windows, CoSession Host needs to install and modify drivers in the system.ini file. In doing this possible conflicts may arise between the CoSession drivers and the existing drivers already in place in the system.ini file. If after installation of CoSession Host, you are unable to run Windows locally on the Host machine, It is probably due to one or both of the following conflicts. What to do : First the CoSession changes to your system.ini file should be taken out so that Windows can be run locally. To accomplish this follow these two steps ; change to your Windows directory: CD \WINDOWS copy system.sav to system.ini: COPY SYSTEM.SAV SYSTEM.INI This will restore the system.ini file that was in place before CoSession was installed. This will however render running Windows remotely temporarily impossible, but will restore local operation of Windows back to normal. NOTE: Running DOS remotely is not affected by any of these changes. Possible cause of conflict : Now that the original system.ini is in place, and Windows is operating normally, the following items should be verified. The most common cause of conflicts is that the current Windows resolution that is in place is beyond that of CoSession's supported range. For the versions mentioned above, CoSession only supports up to a 800x600 display, with a maximum of 16 colors. Using Window's Setup program verify that the display driver in place is in the supported range. If it is not, then run Setup to change the display driver to one that is 800x600x16 colors or less.(Microsoft supplies two that fall in this range, VGA.DRV, SuperVGA.DRV). The Microsoft Windows install diskettes may be needed to change the drivers, so make sure they are available. After the display driver has been verified or changed, exit Setup and return to the C:\Windows prompt. The existing mouse driver may also be causing a conflict with the CoSession drivers. To check to see if this is the case, edit the system.ini file by typing the following : Change to your Windows directory ; CD\Windows Edit the system.ini file ; Edit system.ini This will open the up the system.ini file for editing and viewing. Once the file is up, look for the Mouse.drv= line that is located in the [boot] section of the system.ini file. If the line is equal to anything with a path in it (i.e. Mouse.drv=C:\mouse\mouse.drv), then is must be changed. If the line has no path in it then no extra steps need to be taken. If there is a path please make a note of the drive and directory that are specified in the Mouse.drv= line, then modify the line to equal Mouse.drv=cmouse.drv. After this line is modified, save the file by pressing Alt-F, then S for Save. Next exit Edit by typing Alt-F, then X for Exit. This will place you back at the DOS prompt. Next you will need to actually create the driver that was just created in the system.ini file. This is done by following these steps ; Change to the Windows System directory CD\Windows\System Copy the mouse driver from the pathed drive and directory to cmouse.drv ; Copy C:\Mouse\mouse.drv cmouse.drv (NOTE : C:\Mouse is an example drive and directory, it may in actuality be different) After these two drivers have been either verified or changed, the CoSession Host's Windows drivers should be reinstalled. This can be done by inserting the Host diskette into the disk drive and run the install.exe program. Then select the third item off of the installation menu, which is Install The Host Windows Drivers. After this installation of the Windows drivers, everything should work normally. (NOTE : Newer versions of CoSession for DOS Host will no longer have these problems due to a change in CoSession driver technology. Upgrades to newer versions are available through the Sales Department of Triton Technologies Inc., 908-855-9440) TB#10128 Running TSRs Remotely EKK 2/28/94 Last Updated by KMR 5/23/94 Problem : When running a TSR (Terminate and Stay Resident) program, like email or a mainframe emulation program, and having the Host appear to lock up when calling in from the Remote. What to do : The Host TSR program may not actually be locked up, it just may be that the Host is not responding to the keystrokes from the Remote that activate the Hot Keys to get into the TSR program. The first step to take in fixing this problem would be to turn Special Keyboard Handling to YES on the Host. This is done by first changing to the directory where CoSession Host is stored, and running the Options.exe program. Choose the Hardware selection off the menu, and change the Special Keyboard Handling option to Yes by hitting the space bar. If this does not solve the problem when running the TSR from the Remote, try altering the order of loading Host and the other TSR. If Host is loaded before the other TSR, try loading it after, or visa versa. Also if it is a 6.1 or later version of Host, it will attempt to load into upper memory. This may be where the conflict is occurring, so Host should be loaded in conventional memory by using the -ux command line parameter (i.e. Host -ux ) to see if this helps. TB#10129 International Keyboards DMB 4/13/94 The following diagram describes the different instances of how the Remote and Host will react during a connection when there are international keyboard drivers installed: REMOTE HOST INTERACTIVE CHAT KEYB KEYB SKBH Remote Host Remote Host GR GR YES German German German German GR GR NO US German German German US GR YES German German US German US GR NO US German US German GR US YES US US German US GR US NO US US German US Description of Fields: Main Headings Remote and Host refer to the two computers in the active connection. Interactive mode pertains to the activity between the Remote and Host during an active remote control session. (i.e. doing a DIR out at the DOS prompt) Chat mode refers to the Remote and Host engaging in a CoSession Chat. Sub Headings KEYB refers to the KEYB.SYS command or KEYB.COM that is done on the Remote and Host in the CONFIG.SYS file or in the AUTOEXEC.BAT file respectively. (i.e. KEYB GR tells DOS that the keyboard on the machine is to act as a German keyboard) SKBH (appears under the main heading of Host) stands for Special Keyboard Handling which is an option set to either YES or NO on the Host machine under the OPTIONS program. Under the main headings of Interactive and Chat appear Remote and Host. This tells you how the two different computers will act during a connection either in Interactive mode or Chat mode. Let's look at the first line across and see how to read the chart: The Remote and Host are both running the KEYB command specifying that the keyboards are both German. The Host also has Special Keyboard Handling set to YES. The Remote and Host in Interactive mode will both act as German keyboards. The Remote and Host in Chat mode will also act as German keyboards. TB#10130 Problem Creating Destination File During Setup and Network Install Version : CSW 1.0 - 1.0e KMR 4/13/94 Last Updated by KMR 5/23/94 Problem : During a CoSession for Windows Host installation, a failure occurs at about the 60%-65% mark on the installation complete meter, and CSW returns a error message stating Problem Creating Destination File. What to do: It is at this point in the installation that the CoSession for Windows Setup program is attempting to modify the system.ini file in order to install the CoSession Windows drivers. Setup needs to have the proper access rights to modify the system.ini file, as well as copying the driver files themselves into the Windows\System directory where the other driver files reside. If Setup does not have the proper rights to these directories, the install will fail at this point. On standard installations of Windows which are on a local hard drive (i.e. C:\Windows), there should not be a problem with access rights. However, if the Windows directory is on a network drive, the directory may be write protected so that no program can modify files stored in it. If using a network installation of Windows check with the network administrator to verify access rights. More on Network Installations of Windows : On a network installation of Windows, it is sometimes set up so that the system.ini and related files, including the Win.com file will reside in a users directory, while the *.drv, *.386, and *.fon files are on a separate drive altogether, so a \system directory does not exist. This is important because the CoSession for Windows Setup program is expecting to find a \system directory underneath the directory where the Win.com file is located. If this directory does not exist, then the mentioned error, Problem creating destination file will occur. To bypass this error in the install, you need to do two things. First find the directory where the Win.com file is located. Next verify that there is a system.ini file in this directory. There should be, but if there isn't check with the network administrator for guidance. Then make a system directory underneath this directory by typing the following ; Make system directory ; MD SYSTEM Next load Windows, and run the Setup for CoSession for Windows again. This time it should complete the Setup. Then exit Windows, and change to your newly created system directory. Once in this directory, you should do a DIR command and verify that there are eight files that all being with a CS$. At this point you will need to copy these eight files over to the drive and directory where all of the other Windows drivers are stored. Again, if there is any doubt check with the network administrator. Once these files are copied over, the installation of the CoSession for Windows Host is truly 100% complete. TB#10131 CSOPTIONS Setting Version : CSW 1.0 - 1.0f CSD 7.0a and above KMR 7/10/94 In order to have a CoSession DOS Remote call into a CoSession for Windows Host and control Windows remotely, an additional line must be added in the boot section of the Host's System.ini file. This line should appear as follows: CSOPTIONS=L While this setting must be placed in the boot section, it can go anywhere in that section. This setting will alert the CoSession for Windows Host display driver to the fact that a DOS Remote is operating on the remote end of the connection. NOTE: In the above scenario, not implementing CSOPTIONS=L will result in a a checkered pattern on the Remote screen (as if the screen is trashed) upon going into Windows on the Host. TB#10132 TCP/IP Address Format in LAN II Phonebook Version : Lan II 6.2 or later KMR 4/13/94 When configuring an address in a CoSession Lan II phone book entry for FTP'S TCP/IP protocol, it is important that the following format is used: Address as it appears in TCP/IP (Made up of 4 Octets separated by periods) 25.159.38.1 Same address in a Lan II phone book entry 025159038001 NOTE: The periods "." denoting a field delimiter are left out and leading zeros have been added to each octet so that they are three characters in length. TB#10133 Lan II Setup for NACS or Netware Connect Version : Lan II 6.0 or later KMR 4/13/94 Last Updated by KMR 5/23/94 Use the following steps when setting up CoSession Lan II with Novell's Netware Connect Access Server product. To set up the Host machine to Wait for a Call do the following: First load the NASI redirector driver (this must be loaded prior to loading Host) Next Verify that the CoSession Phone Book is set up properly by either loading Phone.exe in the Host directory, or by loading Hostmenu.exe Then check to insure that the Default Phone Book Entry has the protocol selection set NASI Next hit the PgDn key to view the Service field to verify that the proper dial in Service is selected. If it is not press enter to view the list of available Services, and select the proper one. If there is any question as to which to select, the Netware administrator should be contacted Then check to see that the modem type of Direct-Flow is selected, if it is not, press enter to view the list of available modem types and choose Direct-Flow Next the baud rate setting must match the speed of that NACS OR NETWARE CONNECT is set to. Finally hit F10 to exit back to the DOS prompt and load Host -a, or if using Hostmenu press F10 twice to get to the call menu, and select F2 for Wait for Call The Lan II Host software should now be waiting for a incoming call from a Remote from outside the network. See Dialing in for details on how the Remote is set up to call into the Host. To set up Lan II Remote to dial out through the NACS or Netware Connect Server do the following: First load the NASI redirector driver (this must be loaded prior to loading Remote) Then load the Lan II Remote software by typing Remote in the directory where it is stored Next change to the Phone Book menu or Remote, and verify that the entry being used to call out, has the Protocol type set to NASI Then hit the PgDn key and check to insure that the proper dial out service is selected. If it is not, hit enter on service to get the list of available services, and select the proper one Next check that the modem type and baud rate match that of the modem that is connected to the service that was specified above. If there are any doubts as to the accuracy of this selection verify with the network administrator Then add the phone number of the Host modem that is being called Lastly, hit F10 until the call menu is selected, and hit F1 to initiate the call. With these settings in place the Remote is set for making calls out to a Host computer that is located outside the network. Dialing in to a Lan II Host from a stand alone Remote: There are one of two ways to use Remote to dial into the NACS or Netware Connect Server . They depend upon how the Communications Server is set up. The NACS or Netware Connect Server can be setup so that an application (i.e. Host or Hostmenu) that is set for a particular Service is the sole user of that Service (Modem), or it can be set so that a user dialing in must select the specific Service they want to access. In this case the CoSession Host would be the sole user of the Service that it has selected in the Phone Book entry. This means that it would be the only application to be utilizing the modem that was attached to that particular Service. This would mean that the Remote dialing in would not have to change anything about the default set up of the phone book, other than entering the phone number of the NACS or Netware Connect 's modem designated for that Service. If the NACS or Netware Connect Server is set so that a incoming caller must enter in his or her desired service, then there are some additional steps which must be followed. If the Remote user is running CoSession Remote version 6.1s or later, then the Terminal type of Other-ACS may be used. With this Terminal type, the Remote user will be presented with a TTY type screen immediately upon the modem connection. At this point the prompt from NACS or Netware Connect Server asking what Service is desired, and what ever information is required from NACS or netware Connect Server can be entered. After the Host's Service is selected, and the Remote caller has been routed through to the proper Service, then ALT-R can be hit on the Remote keyboard to send the CoSession Login. This Login is the handshaking that CoSession goes through at the start of a connection. If the login is successful, which it should be if the Host has been configured as detailed above, then the Remote user should see the Host's screen. If the version of CoSession Remote being used is not 6.1s or later, or if the Remote is from one of Triton's other product lines (i.e. ACS, X.25, Session XL, Lan II, CSW), then a CXL script must be used. CXL Scripting is detailed in the CoSession Remote manual in Appendix E Post Connection Scripting. The CXL script's purpose is to send the necessary text strings to get the Remote to call through an intermediary device or software, to the Host PC. In order to write a CXL script, the information that is needed to route the Remote to the Host must be known. If this is not known, then a call should be placed in to the NACS or Netware Connect Server with either a third party communications package, or with CoSession Remote's Com Port Window. By making this type of standard connection, it should be easy to obtain what information is being asked for by the NACS or Netware Connect Server . With this information, a CXL script can be written using a standard text editor, such as MS-DOS's Edit. For information on CXL usage and commands refer to Appendix E of the Remote manual. A sample CXL script file for Dialing in to a NACS or Netware Connect Server is provided below. Depending on how the NACS or Netware Connect Server routes the incoming calls, this script may or may not need to be modified. ;;; Sample CXL Script for NACS or Netware Connect Dial In ;;; PAUSE S5 ;;; Wake up Comm Server ;;; SEND "\" ;;; Wait for Comm Server Prompt ;;; WAITFOR S10 | "Service Name" ;;; If Comm Server Answers, Send Service Info ;;; IF WAITFOR GOTO Goodcall ENDIF ;;; No response from Comm Server ;;; GOTO Badcall ;;; If Comm Server responded to wake up ;;; Goodcall: PAUSE S2 ;;; Send Service Information ;;; SEND "Hostservice\" PAUSE S2 ;;; Wait for Connect from Comm Server ;;; WAITFOR S10 | * IF WAITFOR = "Connect" GOTO Goodconn ENDIF GOTO Badcall ;;; No response from Comm Server ;;; Badcall: PAUSE S1 ;;; Hang up Modem and Exit CXL Script ;;; DISCONNECT ;;; If Comm Server Connection successful ;;; Goodconn: PAUSE S2 ;;; Start CoSession Remote Login ;;; EXIT TB#10134 CSOPTIONS Line Version : CSD Version 7.0a CHS 6/9/94 For CoSession for DOS Remote running RWIN to be able to access Windows on the CSW Host 1.0e or earlier, or the CSD 7.0a Host, it is necessary to add the line csoptions=L, with the L in upper case, to the Host's System.ini file (ref. TB#10131). CoSession for DOS Host version 7.0a automatically adds this line to the System.ini upon installation. When a CSW Host is installed on a computer, it alters the System.ini to install CoSession's Windows drivers, but it does not install the csoptions=L line because it is not required for communication when using a CSW Remote. Therefore, if a CSD 7.0a Host is installed prior to a CSW Host on the same machine, the result will be a removal of the csoptions=L line from the System.ini. This line must be put back into the boot section if communication using a CSD Remote running RWIN is to be supported. Note: Versions later than CSW 1.0ea and CSD 7.0aa no longer require the csoptions=L line in the System.ini. TB#10135 SPX on IPXODI Networks for CoSession (Lan II, ACS and CSW 2.0 and up)Versions : All CHS 6/16/94 The Open Data-Link Interface (ODI) is a specification developed by Novell to enable multiple protocol support on a single NIC (Network Interface Card) driver. Novell NetWare is an IPX/SPX network. IPX (Internet Packet eXchange) provides the ability to send data across the network. SPX (Sequenced Packet eXchange) tracks the data sent by establishing a virtual circuit, which creates a larger overhead and uses almost 2K of RAM. On an IPXODI network, SPX becomes an option, as it is often not necessary for internal operation. It is not loaded when using the command line IPXODI A, which loads only IPX. CoSession LAN II and ACS (for MSHARE) products require SPX to function. These products rely on that virtual circuit that SPX creates and the guarantees it provides. If a user is on an IPXODI network (usually Novell) and SPX has not been loaded, SPX must be installed in order to be compatible with these CoSession products. The command lines IPXODI and IPXODI D include the loading of SPX when installing the network. TB#10136 ACS Netport Error 34: "IPX Socket Is Full" Version : ACS 6.0 and above CHS 7/06/94 The CoSession ACS code "Netport Error 34: IPX Socket Is Full" refers to the inability of the workstation to assign a unique socket number to Netport for transporting of packets across the network. A socket is a data structure that is used to send and receive packets at a particular software address within a station. It is used to distinguish the software address from the station number and node address, which is assigned to each workstation on an IPX network (such as Novell NetWare) but not unique to the software applications residing on that station. In this situation, IPX Sockets need to be created to handle the software needs. These are created in the workstation's NET.CFG file, which resides in the directory that contains the IPX.COM and NETx.EXE files. Locate the line "IPX SOCKETS=##" (## being a numerical value): 1. Increase value by increments of 20 until the error stops; 2. If this line does not exist, enter it as "IPX SOCKETS=60" (if NET.CFG does not exist, the file can be created exclusively for this line). TB#10137 Printing From DaVinci Email Versions : CoSession Aysnch 6.1j - 7.0a, CoSession for Windows 1.0 - 1.0e AHT 7/08/94 When using CoSession to perform remote printing from the DOS version of DaVinci, the following settings must be adhered to: The Print Page Setup within DaVinci, defaults to 80 x 60 this should be changed to 60 x 60. TB#10138 Interrupt 65 Conflict All CSD and CSW Hosts (Versions 1.0 - 2.5 and CSW 6.0 RMHOST) CHS & AP 7/12/94 The CoSession Host and Hostmenu programs utilize Interrupt 65 for communicating between their DOS and Windows components. Sometimes other applications may use the same interrupt, which will cause a conflict with either their execution or CoSession's execution in relation to some DOS and Windows functions. One such conflict occurs when using WinFax Pro 3.0 while CSW 1.0e Host is waiting for a call. This situation causes the functions listed in the WinFax Pro pull-down menus to not execute. By changing the CSW Host from Interrupt 65 to Interrupt 63, operation of these menu functions is restored to WinFax Pro. There are two steps to correcting an INT65 conflict: 1) In CSWH.INI, change the "Host Interrupt Vector" to 63; Host Interrupt Vector=63 2) At DOS, load Host with the -iv63 command line option. Host -iv63 If using CoSession for DOS, there is no need to perform step1, only step 2. TB#10139 ATI MACH32 Video Adapter Versions: CSW CHS & AP 8/22/94 All versions of CoSession for Windows (CSW) are compatible with the ATI MACH32 Video Adapter on the Host PC only with the following ADVANCED settings in the Mach FlexDesk Control Panel: 256 Color Palette=ON Dithering=FAST Device BitMaps=OFF Any variations to these settings can result in an improper Windows display on the Remote PC. TB#10140 Using CoSession With 28.8 Modems At Bauds Above 57,600 Versions: All CHS & AP 8/22/94 When using CoSession with a 28.8 modem and a 16550 UART chip, baud rates up to 57,600 can be effectively supported. However, bauds above 57,600 will cause data overruns actually slowing down transmissions. CoSession attempts to retransmit the overrun data, which considerably slows the data rate. Speeds above 57,600 require the use of a specialized serial board like the Hayes ESP Accelerator Board or an advanced Windows' Comm driver package like TURBOCOM/2 from Pacific CommWare. The Hayes board uses a 1Kb buffer compared to the 8 byte buffer of the 16550 UART. Both the Hayes board and the Turbocom/2 package install their own communication drivers and make the necessary modifications to the Windows' System.ini to optimize performance of Windows at these higher speeds. TB#10141 Mode CO80 for Monochrome Displays Versions: CSW Remote CHS 10/5/94 A monochrome display on a machine running CoSession for DOS or CoSession for Windows Host will not display properly on a machine running CSW Remote with a color display. To enable the display to function properly on the Remote, the following DOS command must be issued at the DOS prompt on the Host computer: MODE CO80 This command will set the screen to display 80 columns in color. Even though this command will not affect the monochrome display on the Host side (as it will not be able to display in color), it will change the mode of the display signal being sent to the Remote computer to provide compatibility. TB#10142 Dialing Into Triton's BBS MJR 7/20/94 This bulletin details proper procedures for calling into the Triton BBS using CoSession or another communications software. The BBS supports X, Y, Z and Kermit downloads. When using CoSession for DOS to call in, make sure that the term type is set to TTY in the phone book entry you are creating. This procedure if intended for a first time caller. - Dial into the BBS - What is your first name? "Enter your first name and press ENTER" - What is your last name? "Enter your last name and press ENTER" - Your name " NAME" was not found in the user data base. Is your name spelled correctly [Y/N]? Enter "Y" and press ENTER. - Please select a password. ******** "Enter a password" - Re-enter your password. ******** "Re-enter password" - Press [C] and ENTER to Continue. - Would you like to view the bulletin menu? "Press [N] and ENTER to continue." - What is your company name ? "Enter company name, or leave blank if you are an individual" - What is your street address ? "Enter your address and press ENTER" - Is there a suite, floor number or mail stop. "Enter appropriate information and press ENTER" - What is your city? "Enter your city and press ENTER" - What is your state? "Enter your state and press ENTER" - What is your ZIP or postal code? "Enter appropriate information and press ENTER" - What is your country? "Enter your country or leave blank for USA, and press ENTER" - What is your daytime voice phone number? "Enter appropriate number and press ENTER" - You entered "phone number" is this correct? "Press Y for yes and then ENTER" - What is your fax number? "Enter your fax number and then press ENTER" - Is this your correct fax number? "Press Y for yes and then ENTER" - Which of Tritons' products do you currently own? "Enter choice or [R]elist - Do you own any other Triton products? "Y or N then ENTER" - The newsletter has been updated. Would you like to view it? "Y or N then ENTER" - Would you like to view the bulletin menu "Y or N and Press [ENTER} to continue" - Command >>? (F)iles menu - Command >>? (D)ownload a file. - File #1? "Enter file name as given to you by tech support" - Enter password? "Enter the password" - File #2? "Just hit ENTER if only one file is to be downloaded or enter next file name" - Automatically log off after last download is completed [Y/N]? "Press Y and then ENTER" - Please select a Protocol: "CoSession supports X Modem protocol Press [X] and ENTER" - Please begin your X modem download now, OR X to abort. - Press to get to the TTY Menu. - Press for receive X Modem. - Enter the file name that you wish to store it in on your PC. It will default to the directory you are currently in, Remote. - File received, press any key to continue. - If you answered YES to automatically log-off after download, simply wait for the BBS to disconnect (about 10 seconds). Otherwise, Press F6 (if using CoSession) from the TTY Menu, to log-off and disconnect from the BBS or disconnect in the manner you usually would using your comm software. TB#10143 CSW Remote Pulse Dialing Versions: CSW Remote 1.0 - Up AHT 11/09/94 If you are using the CoSession for Windows Remote on a phone system that is using Pulse dial as opposed to Tone, the following steps should be taken to modify the modem control script: Open the CoSession's Phone Book and go to Setup under Serial/Modem. Then edit the Dial Prefix line and change the: ATDT command to ATDP. TB#10144 Novell Windows Drivers Versions: All CHS 10/13/94 If problems are occurring when loading Windows via CoSession while the Host machine is logged onto a Novell network (especially using VLMs), the Novell Windows drivers may need to be updated. The symptom of this is usually a difficulty loading Windows remotely such as a disconnect or lockup, with the ability to call into the Host when Windows is already loaded. The following drivers would need to be updated to the SYSTEM subdirectory of Windows: VIPX.386 VNETWARE.386 NETWARE.DRV They can be downloaded from Compuserve by selecting GO NOVFILES and downloading WINDR1.EXE. The two 386 drivers above can be found in the directory VXDS of WINDR1 - these two drivers are updates for both Novell NETX and VLM networks. NETWARE.DRV for VLM networks can be found in the directory VLMDRVS of WINDR1. For a NETX version of NETWARE.DRV, a second file, NET33X.EXE needs to be downloaded. TB#10145 Modem Wait Response Time Out Versions : CSW Remote 1.0 - Up AHT 10/31/94 When using a credit card to dial long distance into a Host, or when making calls into a Host that has power-on device, an the Remote will generally have to wait for a unusually long time to establish carrier with the Host modem. When using CoSession for Windows Remote to make such calls , you will probably need to modify the modem's wait response time. To do this, you will first need to Edit the CSW.INI file which is located in your CSW directory. Go to the section labeled [Serial Setup Window], and change the wait response time= line to an appropriate number of seconds the Remote side will wait for a connection to the Host before it will time out. This value is in seconds, and the default setting is generally 45 seconds. If this value is set higher than 59 seconds, the S7 register in the modem control script may also need to be changed. This can be accessed by going to the Modem/Serial Setup screen, and clicking on the More button. This will bring up all of the Modem commands that the Remote sends to the modem. The S7 register setting is contained in the Dial Prefix line, and can be modified to an appropriate value. Note that modems usually have a limit to how high this value can be set, but it is generally 255 seconds. TB#10146 CoSession DOS to CSW phone book conversion procedure Versions: For all CSD 5.01 or higher and all CSW MJR 10/13/94 To convert your CoSession for DOS phone book to a CoSession for Windows phone book you will first need to use the Convert.exe utility for CoSession. This utility can be download from the Triton BBS. The file name on the BBS for this utility is UTILCONV.EXE. The password for the file is RMPTOPBK. If this is your first time using CoSession to download from the BBS refer to Tech Bulletin TB#10142 for assistance. After downloading the file, copy it into your CoSession for DOS Host or Remote directory. Then type UTILCONV to unzip the compressed BBS file. This will create the CONVERT.EXE utility. Next type CONVERT , to start the conversion process on the Session.rmp file. Note : Only phone book entries with a term type of CoSession will be converted, all others will be bypassed. The new resulting file will be saved as CSW.PBK, which is the format of the CoSession for Windows Remote version. This file should now be copied into the CSW Remote directory. To use phone books from CoSession for DOS Host or Remote in the CoSession for Windows Host software, simply copy the session.rmp from the CSD directories into the CSW directory. Note : This will save all of the phone book entries, and phone numbers, but each entry should be checked to insure that the modem selections are correct. TB#10147 Leased Line Setup Versions: All CSD CHS 1/6/95 When CoSession is being used over a leased line with high speed modems or multiplexers, the Modem Type must be set to Direct Flow-Control, the baud should be set to 9600, and the modems must be configured for leased line operation as per the modem manual. If there is no hardware device using flow control such as a null- modem cable, then the Modem Type must be set to Direct Connect. If after these settings are verified a "failed login" occurs, there are three ways to perform a connectivity test: 1. With the modems that are set to leased line operation, open the COM Windows in both Hostmenu and Remote. Type ATZ . With this setup, an is not expected. Instead, ATZ should appear on the other PC. If an is returned, the modems were not configured for leased line operation and are still in command mode. If garbage appears on the other PC, there is a hardware problem. If nothing appears, there is a connection problem. 2. With the modems that are set for command mode operation, open the COM Windows in both Hostmenu and Remote. On the Remote side, type ATZ and wait for an (if an is not returned, there is a problem connecting to the port -- there may be an IRQ conflict or the port may already be initialized by another software). After the is received, type ATX1D . On the Host machine in Hostmenu, type ATZ and wait for . Then type ATA and wait for a connect message. Now, anything typed on either side should appear on the other PC. If garbage appears, it is a hardware problem. If nothing appears, it is a connection problem. 3. With a null-modem cable or multiplexers that are not using flow control, open the COM Windows in both Hostmenu and Remote. Type ATZ . With this setup, an is not expected. Instead, ATZ should appear on the other PC. If garbage appears on the other PC, there is a hardware problem. If nothing appears, there is a connection problem. TB#10148 Immediate Disconnect Upon Connect Versions: All Versions CHS 1/24/95 CoSession and CoSession for Windows enact an "other end OK" message at the point of the initial connection and at least once per minute throughout the session. This is to ensure both sides are communicating. If Carrier Detect is not sensed upon initial connection, an immediate disconnect will occur. If an "other end OK" message is not returned at any time during a session, a "keep alive timer" is enacted and the connection is broken after a 90 second time-out. If the connection is terminated immediately upon connecting, the "other end OK" message can be suppressed to retain a connection between Remote and Host. To suppress the "other end OK" in CoSession for DOS, take the following steps: 1. In the Remote Options, choose "Performance Options" and set KB/SCREEN ERROR CORRECTION to YES; 2. When loading Remote into memory, load it as : Remote -o2048 (using the letter o as in "options") 3. When loading Host, load it as: Host -o2048 To suppress the "other end OK" in CoSession for Windows, take the following steps: 1. In the Remote Control Center in Windows, open the Phonebook, go into Terminal Setup, and remove the blue check from "keep alive timer". Also, be sure there is a blue check beside "error correction". 2. On the Host, edit the batch file you are using to load Host and add to the first mention of Host: Host -o2048 TB#10149 Files Required When Loading CoSession From a Boot Disk Versions: All CSD and CSW Host CHS 1/26/95 CHS Revised 7/19/95 CHS Revised 1/24/96 When loading CoSession from a boot disk, the following files are needed: For CSD Remote: Remote.exe, Session.mdm, Session.rmp, Session.cfg, and optionally Rwin.exe (if running Windows on the Host), and Sunload.exe (if unloading is required). For CSD Host: Host.exe, Session.mdm, Session.rmp, Session.cfg, and optionally - Sunload.exe (to unload CSD Host), Phone.exe (access phonebook), and Options.exe (to access option settings). For CSW 1.0 Host (DOS Only): Host.exe, Session.mdm, Session.rmp, Session.cfg, and optionally - Phone.exe (to access phonebook) and Options.exe (to access options settings). For CSW 2.0 and 2.5 Host (DOS Only): Host.exe, Session.mdm, Session.phn, Session.opt, and optionally - Phone.exe (to access phonebook) and Options.exe (to access options settings). For CSW 6.0 and up RMHost (DOS Only): RMHost.exe, Session.mdm, Session.phn, Session.opt, and optionally Phone.exe (to access phonebook) and Options.exe (to access options settings). TB#10150 Possible Software Conflicts with CoSession Versions: All CSD and CSW CHS 3/2/95 There are some conflicts that may occur between CoSession and other communication software packages. Communication packages usually require control of the modem and COMport as well as control of the Windows drivers. Most notably in conflict would be fax software and other remote control packages. Fax TSRs Fax software usually loads as a TSR in DOS or in STARTUP under Windows in "receive mode", so it is ready for any incoming faxes. At that point, the fax program takes control of the modem, and sometimes the interrupt vector as well (see TB#10138), and if CoSession tries to load, it will not be able to attach to the COMport. Remote Control TSRs Other Remote Control applications may also load TSRs. If there are any Remote Control applications, other than CoSession, loading from AUTOEXEC.BAT or from a LOAD tatement in WIN.INI, this will cause CoSession to have a problem attaching to the COMport, or may inhibit the performance of CoSession. Windows Drivers Most communications applications make changes and load proprietary drivers to the SYSTEM.INI file. For these applications to run, they depend on their drivers being loaded and active during a Windows session. CoSession is no different. If another application's drivers are loading into the SYSTEM.INI, CoSession will not recognize them, and cause Windows not to load either Remotely upon a connection, or sometimes even locally after the Host TSR has been loaded into memory. Usually a distinguishing prefix precedes these drivers to specify the application that is loading them (ex. cs$ for CoSession drivers). TB#10151 Setting up & Running Mapdrv Versions: CSD 7.0 and all CSW AHT 3/13/95 The following steps must be followed in order to successfully setup and execute the CoSession Drive Redirector program: Load MAPDRV.COM: First, mapdrv.com must be loaded in DOS on both the Host & Remote PCs (it can be loaded in CSW via the batch file WINCSWR.BAT - in CSW Remote - and WINCSWH.BAT - in CSW Host). Then the desired drives to be redirected should be mapped on the local PC by running MAPSETUP in CoSession for DOS (CSD) or clicking on the Drive Redirector icon in the CSW Control Center. This should be done prior to connecting. To verify Mapdrv parameters: If you wish to verify the Mapdrv parameters and currently mapped drives, then Mapdrv should be loaded with the -P switch (i.e. MAPDRV -P). For a list of other switches and commands please use the: -H or ? (i.e. MAPDRV -H or MAPDRV ?). Consult your CoSession 7.0 supplement or CSW manual for more detail. Accessing a "mapped drive": After connecting, to access a mapped drive on the CSD Remote, you must first "Suspend" the connection and return to your local system. To Suspend , go to the CoSession Main Menu and select "F8", which is the Support Menu, and select "F1" Suspend/Resume. Then you will return to your local C: prompt. To access a mapped drive on the CSW Remote, return to the local Windows screen and minimize the Remote Control Window. To access mapped drives from the Host PC, simply change to the redirected drives upon connect. Please Note : Only Virtual drives should be mapped and NOT Physical drives. These drive letters must be within range of the "LASTDRIVE =" statement, found in your system's CONFIG.SYS file. Be sure not to load MAPDRV.COM in a Windows DOSbox. This TSR can only be loaded in DOS before Windows is booted. TB#10152 Customization of Port Address and IRQ's Versions: All CSD and CSW 1.0 AHT 3/13/95 With the integration of different types of serial communication devices, the possibility of an IRQ conflict is greater than ever. To avoid this problem, the following modification was made to the CoSession Phone Book COMport setting: COMports 1 through 3 are assigned their respective system default addresses and IRQs. However, to deal with possible conflicts, the Port 4 address may be customized and IRQs 3 through 8 are supported. Note: If you are using CoSession for Windows version 2.0 or greater, customization of Com 3 is also supported. TB#10153 Hayes Compatible Modem Settings Versions: All CSD and CSW 1.0 CHS 3/15/95 In CoSession, there are several HAYES modem settings to choose from. This occasionally causes confusion in the choice of a generic setting for a HAYES compatible modem. Here are a few guidelines to consider: Modem Selection Modem Type HAYES BASIC 2400 baud Hayes Compatible with dip switches - for setting DTR and CD. HAYES STANDARD 2400 baud Hayes Compatible without dip switches - for setting DTR and CD. HAYES EXTENDED 2400 baud Hayes Compatible without dip switches - for setting DTR and CD. HAYES ULTRA 9600, 14400, and 28800 baud Hayes Compatible. HAYES OPTIMA Hayes Optima modems only. HAYES V SERIES Hayes V Series modems only. HAYES SMARTMODEM Hayes Smartmodems only. For best results, generic Hayes compatible modems should choose from three selections only: Hayes Basic; Hayes Standard; and Hayes Ultra. In CoSession for Windows version 2.0, the selections of GENERIC 2400bps and GENERIC HIGH SPEED were added. These settings match the HAYES STANDARD and HAYES ULTRA settings, respectively. TB#10154 Dialing Into Triton's BBS using Windows Terminal MJR 3- 23-95 This bulletin details proper procedures for calling into the Triton BBS using Windows Terminal. This procedure is intended for a first time caller. - Start up windows. - Double click on the Terminal icon in the Accessories group. - Click on phone and then click on dial. - Enter the BBS number and click on OK. This will dial and connect you to the BBS. - What is your first name? - What is your last name? - Your name " NAME" was not found in the user data base. Is your name spelled correctly [Y/N]? Enter "Y" and press ENTER. - Please select a password. ******** - Re-enter your password. ******** - Press [C] and ENTER to Continue. - Would you like to view the bulletin menu? - What is your company name ? - What is your street address ? - Is there a suite, floor number or mail stop? - What is your city? - What is your state? - What is your ZIP or postal code? - What is your country? - What is your daytime voice phone number? - You entered "phone number" is this correct? - What is your fax number? - Is this your correct fax number? - Which of Tritons' products do you currently own? - Do you own any other Triton products? - The newsletter has been updated. Would you like to view it? - Would you like to view the bulletin menu - Command >>? <(F)iles menu> - Command >>? <(D)ownload a file.> - File #1? - Enter password? - File #2? - Automatically log off after last download is completed [Y/N]? - Please select a Protocol: - Please begin your X modem download now. - Click on transfer and then receive binary file. - Enter the name for the file you are receiving. - If you answered YES to automatically log-off after download, simply wait for the BBS to disconnect (about 10 seconds). TB#10155 Problem Accessing the Modem After the Initial Connection Versions: CSD 6.1 and Up and CSW Host MJR 3/23/95 Problem: It has been found that on certain machines CoSession has a problem accessing the modem more than one time. This has occurred with CoSession Host for DOS or Windows and DOS Remote. When the problem occurs from the Host, the modem will set wait dial in and operate normally during the first call in. From that point the modem will not set wait dial in again unless the modem is turned off and back on (for internals the PC power needs to be turned off) and unload and reload Host. I the case of CoSession for DOS Remote the first call would proceed as normal and correctly dial out. But when you would try to place a second call the modem would not be able to initialize properly. What to do: When loading Host or Remote, add the command line argument: -n8 (i.e. Host -n8 or Remote -n8). This will suppress CoSession's use of the 16550 UART's FIFO buffers and successive connections to the modem can be made. TB#10156 System.ini modifications made by CoSession Versions: CSD 6.1 to 7.0aa and CSW 1.0 to 2.0 CHS 3/20/95 In order for Cosession to provide Remote Control support of Windows, certain Windows' drivers must be controlled by the CoSession Host program. To do this, changes are automatically made to the Host machine's System.ini file during the CoSession install. CoSession Host installs its own drivers replacing the original Windows drivers with CoSession drivers containing a "cs$" prefix. The specific drivers that are modified vary among the different versions of CoSession. The following is a list of the specific drivers that are modified by CoSession Host per version number: CoSession vers. 6.1 to 6.1j (backup of original saved as SYSTEM.SAV) Original Modified [boot] section [boot] section mouse.drv=mouse.drv mouse.drv=cs$mouse.drv HostMouse=cmouse.drv comm.drv=comm.drv comm.drv=cs$comm.drv (optional) Hostcomm=ccomm.drv keyboard.drv=keyboard.drv keyboard.drv=cs$kbd.drv display.drv=vga.drv display.drv=cs$disp.drv HostDisplay=vga.drv [386enh] section [386enh] section keyboard=*vkd keyboard=cs$vkd.386 device=*vcd device=cs$vcd.386 device=*combuf device=cs$cbuf.386 CoSession ver. 6.1s (backup of original saved as SYSTEM.SAV) Original Modified [boot] section [boot] section mouse.drv=mouse.drv mouse.drv=cs$mouse.drv HostMouse=cmouse.drv comm.drv=comm.drv comm.drv=cs$comm.drv (optional change) Hostcomm=ccomm.drv keyboard.drv=keyboard.drv keyboard.drv=cs$kbd.drv display.drv=vga.drv display.drv=cs$disp.drv HostDisplay=vga.drv [386enh] section [386enh] device=*vcd device=cs$vcd.386 device=*combuf device=cs$cbuf.386 device=cs$vxd CoSession vers. 6.1x, 6.5b, 6.5c, 7.0aa & (backup of original saved as SYSTEM.SAV) CoSession for Windows vers. 1.0 - 1.0j (original saved as SYSTEM.000 or the next consecutive number relative to the number of CoSession Host installs) Original Modified [boot] section [boot] section keyboard.drv=keyboard.drv keyboard.drv=cs$kbd.drv [386enh] section [386enh] section csoptions=L (in CoSession for DOS versions) device=*vcd device=cs$vcd.386 device=*combuf device=cs$cbuf.386 device=cs$vxd.386 CoSession for Windows ver. 2.0 (original saved as SYSTEM.000 or the next consecutive number relative to the number of CoSession Host installs) Original Modified [boot] section [boot] section None None [386enh] section [386enh] section device=*vcd device=c:\csw20\cs$vcd.386 device=*combuf device=c:\csw20\cs$cbuf.386 Note: In each version, (with the exception of CSW2.0) the CoSession Windows drivers are stored in the \windows\system directory. These must either be stored in the windows\system directory or in whatever directory the other Windows drivers reside (for further information, ref. TB10130). They cannot be pathed and stored in a directory different from the directory the other Windows drivers are in. - This excludes CoSession for Windows version 2.0, which paths the Windows drivers to the \csw20 directory. TB#10157 Enhanced Color Display for 65k Drivers Version: CSW 2.0 CHS 5/2/95 It has been found that some display drivers, when set to 65k colors, require an alternate color setting in CoSession Remote to correctly view the Windows colors remotely. This can be adjusted by editing the CSW.INI of the Remote PC. Most display drivers use the default settings already established in the CSW.INI. But, if the colors appear incorrect (most notably in the gray area containing the minimize/maximize arrows in the upper right corner of an application window) when viewing the Host screen from the Remote PC, edit the CSW.INI file, found in the CSW20 directory in DOS, as follows: In the [CoSession Terminal] section, locate the lines: Enhanced Red=NO Enhanced Green=NO Enhanced Blue=YES And change them to: Enhanced Red=YES Enhanced Green=YES Enhanced Blue=YES The second configuration is the second most used with the 65k color displays. But, if the colors are still displaying incorrectly after making this change, other variations of these settings may need to be tried. TB#10158 Error "Cannot Find METER.DLL" Version: All CSW CHS 5/2/95 Problem: When installing CoSession for Windows after downloading the files from the Triton BBS, it gives the error message "Cannot Find METER.DLL". Cause: The files are being installed to the same directory they are installing from, thereby zeroing themselves out. Solution: When downloading the CoSession for Windows files, place them into a temporary directory or to a floppy, then install them to a different named directory (preferably with CSW in the name). TB#10159 Using CoSession ACS with NetWare 4.0 or higher Version: CoSession ACS CHS 5/4/95 In Novell's NetWare version 4.0 and above, the title of NetWare Administrator in the software has been changed from SUPERVISOR to ADMINISTRATOR. Because earlier versions of NetWare use the term SUPERVISOR, CoSession ACS is designed to recognize that term for RIGHTS assignments, and not ADMINISTRATOR. To work around this, users of NetWare 4.0 and above must run NetWare with Bindery Emulation or use the MSHARE /lite and NETPORT /lite command options in CoSession ACS to bypass the need for MTRUSTEE and the requirement of SUPERVISOR to set that up. For more information regarding the /lite commands refer to the CoSession ACS README file or Technical Bulletin #10103 "CoSession ACS Information". TB#10160 Tips for Running CSW 2.0 Host with Windows for Workgroups 3.11 Version: CSW 2.0 Host CHS 6/1/95 When using CoSession for Windows 2.0 Host on a computer running Windows for Workgroups version 3.11 with 32-Bit File Access turned on, there are some modifications that need to be made to the CoSession Host Windows drivers. The modifications are: In the [boot] section of the C:\WINDOWS> SYSTEM.INI file, path the CoSession keyboard driver from the CSW directory (or whatever directory the CoSession files were installed to) as: keyboard.drv=C:\CSW\cs$kbd.drv Copy all the cs$*.* drivers from the C:\CSW> directory to the C:\WINDOWS\SYSTEM> directory: C:\CSW> COPY CS$*.* C:\WINDOWS\SYSTEM The alternative to making these modifications would be to turn off 32-Bit File Access. To do this, double click on the Windows Control Panel in the MAIN group in Windows , then double click the 386enh icon, select Virtual Memory, then Change, and remove the check from the box next to "Use 32-Bit File Access". Note: CoSession Host should not have difficulty loading or transmitting Windows when 32-Bit Disk Access is turned on while 32-Bit File Access is turned off. TB#10161 New Session.md2 File Versions: All CSW 1.0 /CSD 7.0a or Earlier MJR 6/8/95 Problem: When session.mdm is downloaded from the BBS or taken from a CSW 2.0 version and copied to CSW 1.0 or CSD 7.0a or earlier, all modem selections from the U's through the Z's will be corrupted. Cause: As modem types were added to session.mdm, we surpassed the area allocated to hold this file in these previous versions of CoSession. Solution: We used the present session.mdm, but edited out all of the 1200 and outdated 2400 BPS modems. The new file is called session.md2. It is for use with earlier versions to make all selections A through Z available. Procedure: Download session.md2 from Triton's BBS to a temp directory. (c:\temp). Rename it session.mdm (ren session.md2 session.mdm). Copy the file to the appropriate directory (Host, Remote or CSW). Go into the phone book and select the appropriate modem. Save the selection. Note: The session.md2 file does not require a password to download. To check that the new file is properly installed, change to the CoSession directory and type dir and enter. Session.md2 is approximately 64K. The old session.mdm is approximately 78.8K. TB#10162 Installation of CSW Host on Non-Windows PC Versions: All CSW MJR 8-23-95 1- Insert disk into appropriate drive and change to that drive. To do this type A: or B: and then from the C:\ prompt. NOTE: Only disk 1 of 2 is required. 2- Now at the A:\ prompt type SETUP and then . 3- In a moment the “Host Installation Procedure - DOS Only” screen will appear. Press to continue. 4- The install will prompt you to Install CoSession Host files or Define Phone Book Settings. Type 1 and then . 5- You will then be asked to enter the disk drive on which the files will be stored. If Host is to be installed to the local hard drive, type “C” and then . 6- Press again to accept C:\CSW as the directory to which the files will be installed. Or type in the desired path. Type “Y” and then enter. The Host files will now be copied to the hard drive. 7- If you have the modem information (ie. Comm Port, Modem type and Model) type “Y” and then . Enter the appropriate information. If you do not have the modem information at this time, don’t worry. It can be entered later by simply typing “phone” and then at the C:\CSW directory. 8- The installation is now complete. 9- To have the Host “waiting call in” change to the CSW directory and type Host -a and then . 10- To verify host is “waiting call in” press and to bring up the chat mode. View the status bar above the Chat screen. It should display Host Inactive Waiting Call In. TB#10163 Procedure for Loading CSW Host with NMODI Version: CSW 2.0 and 2.5 Host CHS 9/1/95 There is a conflict that exists when loading CoSession for Windows' version 2.0 and 2.5 Host and Mapdrv programs with Net Manager's NMODI network driver. This conflict is caused by both programs attempting to access the same multiplex interrupt address of C1. The multiplex interrupt address that CoSession Host and Mapdrv access can be changed from their default of C1 to C2 by loading: mapdrv -ic2 host -irc2 Host and mapdrv, or just host, can be loaded in the following ways: from the Autoexec.bat file; from DOS in the \CSW directory; from one of the batch files created during install (edit WINHOST.BAT or WINCSWH.BAT to add this as the first host and mapdrv command line option); by double clicking the Host icon in Windows -- after editing WINHOST.BAT in the \CSW directory to include -irc2 as the first host command line option. TB#10164 Procedure for Using the Internet to Make a CoSession Connection Version: CSW 6.0 CHS 12/1/95 CoSession for Windows version 6.0 has the capability to make a remote control connection across the Internet using winsocks. Before making this connection, the following is required: You must subscribe to an Internet provider; You must know the IP address of the PC that will be used as the CoSession Host. And, the following steps must be taken: 1. You must have TCP/IP loaded on the CSW Host PC and have Windows set for Winsock support; 2. You must load the CSW Host in Windows into a Wait for Call, after selecting "Winsock" as the protocol in the Host's Wait for Call record; 3. You must select "Winsock" as the protocol in the CSW Viewer's phonebook and enter the IP address in the "Network ID" field; 4. You must connect to the Internet on the CSW Viewer PC via your Internet provider, and be loaded for Winsock support; 5. You must click the "Call" button in the CSW Viewer Control Center. You should then be able to establish a CoSession Remote Control session. Note: Performance may vary depending upon your Internet connection. TB#10165 Tips for Remote Printing with CSW under Windows 95 Version: CSW 6.0 CHS & AHT 1/3/96 When using CoSession for Windows to redirect the printing to the CSW Viewer from a CSW Host running under Windows 95, the following tips will ensure success. To setup the Print Redirection in Windows 95 on the Host PC: Click -- START, SETTINGS, PRINTERS; Click on the icon for the Printer that your Host PC is using as its Default; Be sure to set it as the Default Printer; Click -- PROPERTIES, choose the DETAILS folder; Click -- the down arrow beside "Print to the following port"; Choose "CoSession Print Redirection". To optimize print performance from the Windows 95 CSW Host: Click -- START, SETTINGS, PRINTERS; Click on the icon for the Printer that your Host PC is using as its Default; Click -- PROPERTIES, choose the DETAILS folder; Click -- SPOOL SETTINGS; Check the box for "Spool print jobs so program finishes printing faster"; Check the box for "Start printing after the first page is spooled"; Under the heading "Spool data format", select EMF; Click -- OK. Note: With the "Print to the following port" setting set to CoSession Print Redirection, CoSession has control of the Host's printing. To return to local printing, be sure to change this setting back to the correct LPT port. TB#10166 Host Error Messages "cs-disp error" and "unable to lock memory area" Version: CSW 6.0 CHS 1/5/96 "cs-disp error" This error occurs after installing CSW, then loading CSW Host. Problem It occurs because a conflict during the CSW installation caused the Host drivers to not install to the system.ini. Cause There may have been an old version of CoSession on the system and the new version had difficulty installing over it. Fix Run the CSW Uninstall program and then rerun the install for CSW 6.0. If the drivers still do not install to the system.ini, install them manually by Editing the system.ini file found in the c:\windows directory and placing them into the [386enh] section as follows: For systems running Windows 95: [386enh] device=C:\CSW60\cssafe95.386 device=C:\CSW60\csldr.386 device=C:\CSW60\csdvxd.386 For systems running Windows 3.x: [386enh] device=C:\CSW60\cssafe3x.386 device=C:\CSW60\csldr.386 device=C:\CSW60\csdvxd.386 "unable to lock memory area" This error also occurs after installing CSW, then loading CSW Host. Problem There may be a conflict with other communication drivers in the system.ini. Cause There may have been another communication or remote control program that installed proprietary drivers on the system that were not sensed by CoSession during the install. Fix Locate the conflicting drivers and remove them from the system.ini. Be sure the CSW 6.0 drivers listed above are in place. TB#10167 Tips for Remotely Viewing Windows When Loading RMHOST Version: CSW 6.0 Windows: 3.1 and 3.11 CHS 1/22/96 When loading RMHOST.EXE, the DOS TSR for CSW 6.0 Host, there may be additional CoSession drivers required in the Host's system.ini file for optimum remote support of Windows 3.x. These drivers ensure the proper communication between the CSW DOS RMHOST and the Windows 3.x drivers. They need to be manually changed in the system.ini as follows: Comment out (using a ;): [386enh] device=*vcd device=*combuff And replace with: [386enh] device=C:\CSW60\cs$vcd.386 device=C:\CSW60\cs$cbuf.386 Note: Be sure that any drivers prefixed cs$ that may have been installed to the c:\windows\system by previous versions of CoSession are eliminated. If the black screen when viewing Windows remotely remains after these changes have been made and Windows has been rebooted, then remove the line: device=C:\CSW\cs$vcd.386; or check under Control Panel - 386enh - Virtual Memory to see if 32-bit File Access is enabled. If it is, either disable 32-bit File Access or reference TB#10160 for a workaround procedure. TB#10168 Tips For Using CSW with NetWare Connect Versions: CSW 6.0 and up; NetWare Connect 1.0 and 2.0 Windows: 3.1, 3.11, and 95 CHS 2/19/96 CoSession for Windows (CSW) 6.0 and above can be used with Novell's NetWare Connect in the following manner: The NetWare Connect add-on, WNCS11.EXE (version 1.11c of Win2NCS), provides the ability for a COMport in Windows to be redirected to NASI, thereby adding a means for asynchronous communication applications to access the NetWare Connect modem server using standard Windows API calls. WNCS11.EXE can be obtained by contacting Novell or from the NW Connectivity section of the NetWare General Files Forum on CompuServe. To Setup the CSW Viewer for Dial Out: Install NetWare Connect and the WNCS11.EXE add-on as instructed, to setup NASI for redirecting a Windows' COMport to the NetWare Connect modem server; Install CSW 6.0 or above and set up the CSW Viewer's phonebook for Serial/Modem. Specify the COMport that is being redirected by NetWare Connect's WNCS11.EXE add-on. And set the Modem Name and Baud to match the modem being used on the modem server; Simply click the CSW Viewer's Call button to dial the phone number that is specified in the Phone ID. To Setup the CSW Host to Wait for a Call: Install NetWare Connect and the WNCS11.EXE add-on as instructed, to setup NASI for redirecting a Windows' COMport to the NetWare Connect modem server; Install CSW 6.0 or above and set up the CSW Host's Phonebook Wait for Call Settings for Serial/Modem. Specify the COMport that is being redirected by NetWare Connect's WNCS11.EXE add-on. And set the Modem Name and Baud to match the modem being used on the modem server; Simply click the CSW Host's Wait Call button to set it into a Wait for Call mode. To Dial in to the CSW Host: Follow the above steps to load CSW Host into a Wait for Call mode, using the NetWare Connect redirected COMport; On the CSW Viewer that will be calling to the NetWare Connect Server from outside of the network, create a CXL Post Connect script that will guide the connection through the server to the Host on the LAN (see CoSession for Windows manual Appendix E "Post Connect Scripting"); Place the name of the CXL file into the CoSession Viewer Setup under the Viewer's Phonebook, in the space marked "CXL Script:". A sample CXL Script is as follows (see Note: below): ;;; Sample CXL Script for NetWare Connect Dial In ;;; PAUSE S5 ;;; Wake up Comm Server ;;; SEND "\" ;;; Wait for Comm Server Prompt ;;; WAITFOR S10 | "Service Name" ;;; If Comm Server Answers, Send Service Info ;;; IF WAITFOR GOTO Goodcall ENDIF ;;; No response from Comm Server ;;; GOTO Badcall ;;; If Comm Server responded to wake up ;;; Goodcall: PAUSE S2 ;;; Send Service Information ;;; SEND "Hostservice\" PAUSE S2 ;;; Wait for Connect from Comm Server ;;; WAITFOR S10 | * IF WAITFOR = "Connect" GOTO Goodconn ENDIF GOTO Badcall ;;; No response from Comm Server ;;; Badcall: PAUSE S1 ;;; Hang up Modem and Exit CXL Script ;;; DISCONNECT ;;; If Comm Server Connection successful ;;; Goodconn: PAUSE S2 ;;; Start CoSession Remote Login ;;; EXIT Note: In order to write the CXL script, the information that is needed to route the Viewer to the Host must be known. If this is not known, then a call should be placed in to the NetWare Connect Server with either a third party communications package, or with CoSession Viewer's Port Monitor. By making this type of standard connection, it should be easy to obtain what information is being asked for by the NetWare Connect Server . With this information, a CXL script can be written using a standard text editor, such as MS-DOS's Edit. Depending on how the NetWare Connect Server routes the incoming calls, this script may or may not need to be modified. ARTISOFT TECHNICAL SUPPORT: Artisoft offers a wide selection of technical support options. For information regarding technical support services, please refer to our Directory of Support Services, available where you obtained this bulletin (request fax document 4, check Support & Services at our Home Page, or download file DIRLIST.TXT). You can also obtain this information by calling Artisoft at (520) 670-7000. Artisoft makes no warranties as to the completeness or accuracy of this document. Artisoft is not responsible for lost profit or revenue, loss of software use, loss of data, cost of re-creating data, cost of any substitute equipment or program, or any other claim. Artisoft makes no warranty that complying products will operate under any other conditions, or that products will satisfy requirements, or that products will be without defect or error, or that product operation will be uninterrupted. Artisoft’s aggregate liability is limited to the total of payments made by the customer for the Artisoft product and Artisoft shall not in any case be liable for any special, incidental, consequential, indirect, or punitive damages, even if it has been advised of the possibility of those damages. LANtastic is a trademark of Artisoft, Inc. Brand names, company names, and product names are trademarks or registered trademarks of their respective companies. LANtastic Technical Bulletin Page 9 of 64 Artisoft Inc. Sales: Phone 800-846-9728 Fax: 520-870-7359 2202 Forbes Blvd Technical Support: Phone 520-670-7000 Tucson, Arizona 85745 INSYNC Artisoft Making the World your Office. Technical Bulletin COS-TB Technical Bulletin Artisoft, Inc. Sales Consultation Center: (800) 846-9726 FAX (520) 670-7359 2202 N. Forbes Boulevard Product Certification Message Center: (520) 670-7107 FAX (520) 670-7225 Tucson, Arizona 85745-1412 Information regarding Technical Support: (520) 670-7000 BBS (520) 884-8648