═══ 1. Copyright 1994 DataMirage Software ═══ LiveWire Communications 2.2 Frequently Asked Questions Copyright 1994 DataMirage Software Compiled April, 1994 Please distribute this document as widely as possible ═══ 2. Purpose of this document ═══ This document, compiled by DataMirage Software, serves as a quick reference to common questions and problems. Please review this document for answers to your problems before contacting DataMirage Software support. If this document fails to answer your questions, you may contact DataMirage software in the following ways: BBS: (714) 856-2071 / 9600-8-N-1 Internet: 73631,1233@compuserve.com CompUServe: 73631,1233 (Les Novell) DataMirage Software Support 585 Hyde Park Drive San Jose, CA 95136 Please indicate if you have purchased a copy of LiveWire. ═══ 3. How do I start a script file from the command line? ═══ Q: How do I start a script file from the command line? A: A script may be started from the status line by using the /S parameter. For example, C:\LW22>LW22 /Sdialwork.cmd C:\LW22>LW22 /Shost.cmd ═══ 4. How do I put trailing spaces at the end of my macros? ═══ Q How do I put trailing spaces at the end of my macros? A When entering text in a field LiveWire removes any blank spaces at the end of a string. In some cases it is desirable to have trailing spaces. To include trailing spaces when defining a macro, place a single caret (^) at the end of the spaces. This marks the end of the string and prevents LiveWire from removing the spaces. The caret will not be interpreted as part of the macro, that is it will not be transmitted. ═══ 5. How do I turn off LiveWire's internal Zmodem and make M2Zmodem auto-download? ═══ Q: How do I turn off LiveWire's internal Zmodem and make M2Zmodem auto-download? A: To make M2Zmodem auto-download you must first turn off internal Zmodem auto-download. To do this, enter configuration and pull-down the protocols menu. Select the line in the protocols menu that contains Zmodem 32-batch. A seconary will pop up containing the option "Auto-download." Toggle the auto-download option off, then exit back to the protocols menu by pressing the Escape key. Next, M2Zmodem auto-downloading must be enabled. Select M2Zmodem from the protocols menu to bring up a secondary window. Move the highlight bar down to the "Auto-receive string" option and press ENTER. Type into the field B00, and press ENTER. The field should now contain "B00". Exit configuration, saving your changes. M2Zmodem should download automatically now. Note: If M2Zmodem does not appear in your protocols menu, you have not installed it correctly on your system. Refer to the M2Zmodem documentation. The most likely cause of improper installation is not specifying the M2Zmodem directory in the PATH environment variable. ═══ 6. How do I use 50 line mode with my UNIX host? ═══ Q: How do I use 50 line mode with my UNIX host? A: Most UNIX hosts assume VT-102 has a 24-line screen, so text is automatically restricted to the first 24 lines of the screen. The number of lines available to UNIX can be increased by typing STTY rows 49 at the shell prompt. This command sets the number of lines to the maximum available in a LiveWire session. The UNIX host will now attempt to use all 49 lines. Unfortunately, many UNIX hosts do not reset the VT-102 emulation, so the VT-102 must be reset by hand. VT-102 emulation can be reset by entering the emulation configuration menu briefly, then exiting. In LiveWire keyset emulation this is equivalent to pressing ALT-E followed by ESC. If the terminal is reset properly the screen should clear and the UNIX host should use the entire terminal screen. ═══ 7. How do I turn off BACKSPACE mapping to DEL in VT102 mode? ═══ Q: How do I turn off BACKSPACE mapping to DEL in VT102 mode? A: There are actually two settings for BACKSPACE mapping for the VT-102 emulation. The first, available from the command menu, toggles the GLOBAL backspace mapping on or off. To turn this off, go into the configuration under the Terminal menu and set "Backspace is DEL" off. The second option is available in configuration under the Terminal menu. Select "Setup emulations" and turn off "Backspace=DEL." ═══ 8. How do I use scroll-back search capabilites? ═══ Q: How do I use scroll-back search capabilites? A: The scroll-back buffer can be searched for text that appeared in a session. For example, if a message from John was received earlier in the day but scrolled off the screen, the scroll-back buffer is capable of searching through the text for the word "John." Searching is done in REVERSE. The highlight bar initially lies upon the last line of text received when the scroll-back buffer is viewed. Unlike most editors, scroll-back search will search BACKWARDS from the highlighted line to the begining of the session. The highlight bar will rest upon the line containing the search word when the search has completed. ═══ 9. How do I prevent errors from occuring in high-speed file transfers? ═══ Q: How do I prevent errors from occuring in high-speed file transfers? A: LiveWire's communications routines are capable of capturing data flawlessly at incoming speeds of 57,600 bps. If errors persist in a communications session the problem most likely lies at a lower level, either in the device driver or the hardware. Here is an example of the least reliable serial configuration a PC system might have: -------------- | LiveWire | Maximum reliable speed: 57,600 bps | Serial Port | Maximum incoming buffer: Infinite, to the bounds of available memory | Routines | -------------- ^ | -------------- | COM.SYS | Maximum reliable speed: 57,600 bps | Device | Maximum incoming buffer: 1K | Driver | -------------- ^ | -------------- | UART Chip | Maximum reliable speed: 19,200 bps (8250) / 38,400 (16540) | NS8250/16540 | Maximum incoming buffer: 1 byte (8250 or 16540) | | -------------- The rule that a system is only as strong as its weakest link applies here. No matter how good IBM is at optimizing their COM.SYS, their device driver, the actual chip (the lowest level in the diagram) that receives data is inadequate. Whenever the UART Chip receives information it must interrupt OS/2. Since the most an NS8250 or NS16540 chip can hold is one byte, OS/2 must be interrupted 3,840 TIMES PER SECOND if information is being received at 38,400 bps. The COM.SYS driver must be prepared to answer an interruption immediately. If more than one interruption occurs before COM.SYS answers, data is lost. A shareware driver called SIO.SYS is a direct replacement for COM.SYS. SIO.SYS is faster than COM.SYS at answering interruptions. This results in less data loss, especially in DOS sessions, but enforcing an already strong link is not the best way to solve the problem. Ideally, the most reliable configuration would be: -------------- | LiveWire | Maximum reliable speed: 57,600 bps | Serial Port | Maximum incoming buffer: Infinite, to the bounds of available memory | Routines | -------------- ^ | -------------- | SIO.SYS | Maximum reliable speed: 115,200 bps | Device | Maximum incoming buffer: 4K | Driver | -------------- ^ | -------------- | UART Chip | Maximum reliable speed: >115,200 bps (16550AFN) | NS16550AFN | Maximum incoming buffer: 16 bytes (16550AFN) | | -------------- This diagram demonstrates how to fix the weakest link, the actual UART chip. The National Semiconductor 16550AFN UART is a direct replacement for the 8250 or 16540 UART chips. The 16550AFN chip is capable of speeds in excess of 115,200 bps using a 16-byte incoming buffer. This means that OS/2 need only be interrupted once every 16 characters, or only 240 times per second during a 38,400 bps session! This is an enormous improvement over an 8250 or 16540 chip. Obtaining and installing the SIO.SYS driver will strengthen the connection in two ways. First, SIO.SYS always uses the 16550AFN chip if it is available. IBM's COM.SYS drivers in some instances allow the 16550 to emulate an 16540, which could cause data loss. Secondly, SIO.SYS tends to be faster at accepting interruptions, which reduces CPU load. SIO has a number of additional features the COM.SYS drivers do not have, such has support for more than four ports, interrupt sharing on ISA, and virtual 16550AFN under DOS sessions. ═══ 10. What is a 16550 UART? ═══ Q: What is a 16550 UART? A: A 16550 UART is the chip that receives and sends data over a serial port. It is recommended for use in a multi-tasking operating system such as OS/2 over older compatible chips such as the 8250 and 16540. To replace your 8250 or 16540 you should replace your serial port I/O board with a a serial port I/O board equipped with a 16550 UART. Most computer dealers have single-port 16550 boards for $50. If your modem is internal and you don't have a 16550 UART, call your modem manufacturer for information on how to upgrade to this chip ═══ 11. Do I need a 16550 UART? ═══ Q: Do I need a 16550 UART? A: YES! Almost everyone has a 9600 bps modem with compression, and a 16550 UART will decrease CPU usage and eliminate transmission errors. For more information, refer to How do I prevent errors from occuring in high-speed file transfers? ═══ 12. Where can I get a 16550 UART? ═══ Q: Where can I get a 16550 UART? A: Most computer stores now carry 16550 equipped serial port boards for $40 to $60. ═══ 13. Why does LiveWire get so many file transfer errors, while TE/2* does not? ═══ Q: Why does LiveWire get so many file transfer errors, while TE/2* does not? A: TE/2 1.24, a product of Oberon Software, has been reported as receiving few or no errors when compared with a LiveWire file transfer. Most users report that LiveWire gets a lot of errors while downloading, while TE/2 "just slows down." After inspection of the TE/2 file transfer window, it becomes apparent that there is no place where errors are continually displayed. When an error in a TE/2 file transfer occurs, an error message is displayed briefly and is then quickly overwritten by the file location of the next packet. Since file transfer errors are caused mostly be multi-tasking, by the time a user switches back to the TE/2 window the error has disappeared. While this is fine since the error has been corrected, it leads users to the erroneous conclusion that there no errors occured in file transmission. For more information on transmission errors, refer to How do I prevent errors from occuring in high-speed file transfers? ═══ 14. What is SIO? ═══ Q: What is SIO? A: SIO.SYS is a shareware replacement serial port device driver for IBM's COM.SYS. SIO.SYS, by Raymond L. Gwinn. SIO.SYS can improve your serial port performance and enhances IBM's COM.SYS in many ways. SIO can be found on most OS/2 bulletin boards and ftp sites. To contact the author of SIO you may write to: The Software Division Attn. Raymond L. Gwinn 12469 Cavalier Dr. Woodbridge, Va. 22192 CompuServe 72570,157 Internet 72570.157@compuserve.com FidoNet 1:265/104 (Routed Mail Only) FAX 703-494-0595 ═══ 15. Why has the Ymodem-G protcol been removed? ═══ Q: Why has the Ymodem-G protcol been removed? A: The Ymodem-G protocol is unsafe to use in a multi-tasking environment. Ymodem-G was created for error correcting modems and assumes that the information it receives is correct. No error checking is done, so the file may be corrupted. What the creator of Ymodem-G failed to address is the fact that data can be lost or corrupted after it is received by the modem! Data corruption is unlikely with slow modems and a single-tasking operating system, but with high speed modems and OS/2, data can easily be lost or corrupted. For more information on how errors get into data after it is received, refer to How do I prevent errors from occuring in high-speed file transfers? ═══ 16. My problem isn't in this list, how do I submit a bug? ═══ Q: My problem isn't in this list, how do I submit a bug? A: DataMirage Software is committed to developing and delivering quality, bug-free software that meets your needs. Our bug database allows us to track each bug and suggestion individually. This bug database will be available in May 1994 to callers of the DataMirage BBS. Callers will be able to query for bugs and submit new bugs or suggestions directly to our database. Later, they can call back and view the progress being made on the bug and the release in which it will be fixed. We still accept bugs and suggestions from internet and CompUServe. All bugs submitted must be in the format following. Bugs not in this format are often ambiguous, so please follow this format as closely as possible and provide as much detailed information as possible. Please note, only one bug or suggestion per form. Submission addresses Internet submission : 73631,1233@compuserve.com CompUServe submission: 73631,1233 BBS : 714-856-2071 US Mail : LiveWire Bug Report 585 Hyde Park Drive San Jose, CA 95136 Bug Submission Form Submitter First Name : Submitter Last Name : Submitter Phone # : Submitter EMAIL : One-line description : Severity of bug (1=who cares? - 4=critical crash) : Version of LiveWire : Steps to reproduce bug (many lines) : Complete description of bug or suggestion (many lines) : Have you tested this against other communications software? Describe your hardware setup, if necessary: - CPU - UART type - Modem manufacturer - Remote host ═══ 17. Why does M2Zmodem display "file ZIP not found"? ═══ Q: Why does M2Zmodem display "file ZIP not found"? A: Starting with version 1.24 of M2Zmodem, the directory M2Zmodem resides in must be in the system PATH and DPATH. Follow the instructions included in the M2Zmodem manual about how to modify your CONFIG.SYS. ═══ 18. Why doesn't CKermit start properly? ═══ Q: Why doesn't CKermit start properly? A: The directory CKermit resides in must be in the system PATH and DPATH. Follow the instructions in the CKermit documentation about how to modify your CONFIG.SYS. ═══ 19. Will there be a PM version of LiveWire? ═══ Q: Will there be a PM version of LiveWire? A: Yes, but DataMirage Software is not releasing any details on this product until it has been completed. ═══ 20. How do I prevent the "Carrier lost" message when transferring a file? ═══ Q: How do I prevent the "Carrier lost" message when transferring a file? A: "Carrier lost" messages when transferring a file indicates that the modem modem (or cabling) is not properly reporting whether or not there is a connection. Refer to the modem manual for the proper modem commands to fix the problem. The carrier checking may be turned off by turning "Ignore Carrier Signal" On, located in configuration under the terminal menu. ═══ 21. How can I switch LiveWire from windowed to full screen mode? ═══ Q: How can I switch LiveWire from windowed to full screen mode? A: OS/2 does not allow the familiar DOS box ALT-HOME method of switching between windowed and full screen mode. The only known way of changing from windowed to full screen mode is to start a secondary LiveWire session on the same communications port, then exit the first session. The second session will pick up where the first left off, without hanging up. P. At this point you may need to re-initialize the port by opening the port settings, then exiting. It is necessary to reset the port because as the other copy of LiveWire exits it may reset the serial port to its previous status. ═══ 22. My modem wasn't in the list during installation, what do I do? ═══ Q: My modem wasn't in the list during installation, what do I do? A: First, attempt to find a modem that is close to the capabilities and brand of your modem. With a high degree of likeliness, one modem will operate under the guise of another modem. If problems occur, select "Other modem not listed." An unsupported modem must be hand-configured. There are two main things that must be set up before most modem will work properly. 1. Baud rate: Set it to the highest possible your modem will support 2. Locked Port: If the modem has compression, it may need a locked port to operate at its highest efficiency. Two settings must be changed: the modem must be notified the speed is being locked (sometimes AT&B1), and LiveWire's port setup should have the Locked Port option On. If trouble with the modem persists, contact the modem vendor. ═══ 23. How can I set the dialer so it will re-initialize my modem for each number it dials? ═══ A: How can I set the dialer so it will re-initialize my modem for each number it dials? A: Modem initialization during dialing is not a feature supported in LiveWire. There exists a trick (or kludge) that will work. 1. Remove the "ATDT" from the dial prefix under "Modem Commands..." in the configuration. The prefix ATDT normally instructs the modem to dial. 2. Edit the dialing codes from the dialer. Each dialing code is lettered A through J. Place a different modem initialization string in each dialing code, as desired. 3. Append "^MATDT" to each dialing code. This will initiate the dial. Example: AT &B1 &M2^MATDT 4. Insert the dialing code letter associated with an initialization string at the beginning of the phone number. This procedure works because dial codes (the letters A-J) found in a phone number are expanded to the full dialing code string before the number is dialed.