Procomm Plus 2.0 for Windows By Al Shing NaSPA member Al Shing has more than 20 years computing experience, specializing in operating systems programming and support. He is experienced in supporting PC environments such as Microsoft Windows and MS-DOS, open systems environments such as Unix, and large system environments such as MVS/ESA. He can be reached through NaSCOM ID Shinalbk. Callout: Communications programs, like modems, are a lot like shoes--they are a bit rough when they are new, but once they have been broken in, they become comfortable and you can use them for years. Communications programs, like modems, are a lot like shoes--they are a bit rough when they are new, but once they have been broken in, they become comfortable and you can use them for years. When the time comes to upgrade, you do not look forward to breaking in a new program or modem because of the time and effort involved in configuring and learning how to use them. Over time, you become accustomed to the quirks, idiosyncrasies and shortcuts of the old program, and you feel lost when using a new program. Perhaps this is why Datastorm upgrades their program so infrequently. I purchased Procomm Plus 1.0 for Windows in June 1992. The first major upgrade of that program comes more than two years later. Prior to Procomm Plus for Windows, I had used Procomm Plus 1.1B for DOS since January 1990. Before the Windows version was released, that program had not been updated over the two and a half years I used it. I still use Procomm Plus 1.1B regularly to run a script that would not convert properly to Procomm Plus 1.0 for Windows (this is the script that dials my phone in the morning to wake me up). It is also handy to keep the DOS version around in case Windows fails to start and I need to use a bulletin board system (BBS) to troubleshoot it. The trend in recent years has been to use specialized programs to access specific on-line services. For example, CompuServe Information Manager for Windows and TAPCIS are used for CompuServe access; Aladdin is used for GEnie; and America On- line and Prodigy supply their own access programs. Many BBSes are using the RIP graphics interface, which requires a RIP communications program for access. This diminishes the usefulness of a general communications program such as Procomm Plus for Windows, which continues to supply scripts for accessing all the major on-line services, even though it is unlikely that one would use it today for accessing those services. Nevertheless, there are many situations where the general communications program is still useful, such as accessing a Unix shell account or dialing into a mainframe. Perhaps as a response to the movement to specialized communications programs, Procomm Plus for Windows 2.0 has added features above and beyond that expected of a communications program. The strength of Procomm Plus has always been its ease of use, its support of hundreds of popular modems and its low cost. That tradition, more or less, has been carried forward into Procomm Plus 2.0 for Windows. The upgrade adds some useful features, including fax modem support, the IND$FILE protocol for use with IBM mainframes and network support. The upgrade also cleans up the user interface that was a bit rough in the 1.0 release. In general, the interface is much improved and has similarities to a Microsoft Office application interface. Unfortunately, a few useful features were moved a level lower in the menu structure, making them harder to find and use. Installation By default, Procomm Plus 2.0 for Windows (PROWIN2) installs itself into a new directory separate from Version 1.0. It is a good idea to allow the installation program to do so, so the existing working version can be relied upon to still function in case of problems with the new version. The installation procedure attempts to autodetect the modem and, if successful, will set itself up to use the appropriate modem initialization commands for both the data and fax portions of the modem. The program was able to autodetect my Practical Peripherals PM14400FXSA modem, but unable to autodetect my older Practical Peripherals PM2400SA MNP5 modem. For this older modem, the traditional procedure of selecting the modem from a long list was still available for configuring the program to use the modem. One of the grievances with Version 1.0 was that it would not fill up the entire available screen space when using a 1024x768 driver, but, instead, used a framed window which filled up only about 75 percent of the space. Within this window, it used a small, difficult to read font that could not be made larger. Version 2.0 offers a choice during installation of a framed window or a full-screen window. Both choices use much more of the available window space than did Version 1.0. With the larger window, Version 2 also uses a much larger font. The font is now changeable, and the product comes with a selection of fonts, including some True Type fonts that can be used to replace the default font. The installation process converts an existing dialing directory to the new format, which now has room for fax and voice phone numbers, in addition to the traditional data phone number for each entry. I found one or two of my phone numbers were misconverted into long-distance calls when, in fact, they were local calls. These were numbers that had a prefix code associated with them. In this case, the *70 code that turns off call waiting. It would be a good idea to check each number after the conversion to ensure that local calls do not become expensive long-distance calls. As with previous versions, the installation procedure runs a conversion procedure to convert scripts from the previous version to the current version. Like the previous version, this conversion procedure did not successfully convert my alarm script, which produced a large number of errors when it was compiled. The conversion program will not even look at Procomm Plus for DOS scripts by default. The program will think the DOS version script is a Procomm Plus for Windows 1.0 script and will not convert it correctly. Anyone migrating from Procomm Plus 1.1B should probably convert their scripts to PROWIN 1.0 scripts first, and then convert the converted script to a PROWIN 2.0 script. The final step in installation is auto-registration of the program. Auto-registration collects the appropriate name and address information from the user, and then dials a toll-free number to register the program with Datastorm. Auto-registration is more convenient than the conventional postcard method, which tends to be put off and forgotten until the card is either lost or the next version of the program is due to be released. The Basics The dialing directory (Figure 1) has been expanded to include fax and voice numbers, in addition to the usual data phone number. Information such as the area and country codes have been split off from the main phone numbers. These are used if the directory entry is set up to be a long-distance or international call. Otherwise, an entry can be set up as an internal or local call. Each entry can be customized to use particular terminal emulations, file transfer protocols, port settings, fonts and terminal colors, and action bar buttons specific to working with each bulletin board. There is also room in the directory entry for saving the user ID and password, company name, and notes about the entry. Once the directory entry is set up, the entry appears in the Rapid Dial-Data list in the action bar. Dialing the entry is as simple as selecting it with the mouse from the list. In Version 1.0, a button on the action bar had to be selected to scroll back in the terminal window. During scroll back mode, it was not possible to send commands or data to the serial port until scroll back mode was turned off. Text in the terminal window could not be selected with the mouse unless the terminal was in scroll back mode. There was also a limited number of pages that were retained for scroll back. Version 2.0 has eliminated the scroll back mode, so it is always possible to scroll back in the terminal window (Figure 2), for up to 1,300 pages (default 100 pages). Text in the terminal window or scroll back buffer can be selected at any time with the mouse. Selecting text elicits a pop-up box (Figure 3), with options to copy the selected text to the port, with or without an Enter key, or copy it to a file or the Windows clipboard. There is an option to save the entire scroll back buffer to a file, which is handy for capturing text that has been sent without a capture file being opened. These features save a lot of typing because file names or long Usenet newsgroup names can be selected from the scroll back buffer and sent back to the port as part of a command. Downloads can be set up to start automatically, as soon as the BBS is ready to send. Procomm Plus will automatically obtain the file name from the download protocol. With this release, Zmodem downloads have the ability to crash recover from a failed download, or overwrite or rename an existing file with the same name as the incoming file. The previous release did not have crash recovery and aborted if an existing file had the same name as the incoming file. If the incoming file is a .GIF (CompuServe's Graphics Interchange File format) file, Procomm Plus can display the .GIF as it is being downloaded with the included GIF viewer. Uploads are a little more difficult. They are not started automatically, but must be started by selecting the Send File button on the action bar or selecting the Send File option from the on-line menu. Procomm Plus will respond with the common dialog box for selecting files (usually encountered when opening a file in a Windows program). The drive letter, directory and, finally, the file name are selected with the dialog box, while the BBS waits for the upload to begin. Double clicking the file name closes the dialog box and begins the upload. At the bottom of the terminal window, a number of metakeys can be defined. These keys can be selected with a mouse or hot-key sequence and result in a character string associated with the metakey being typed into the port. Metakeys are defined via the Setup dialog (Figure 4). As many as 40 such keys can be defined as a set, using the zero through 9 keys, combined with the Alt, Alt-Shift, Alt-Ctrl and Alt-Shift-Ctrl keys. Each set is saved as a .KEY file, and many such files can be created and saved. These keys are useful for saving canned responses to prompts for user IDs, passwords, etc. The action bar has a selection list for scripts. Scripts can be written by the user, and several are included with the product. The most useful of the supplied scripts is the host script. This script establishes a rudimentary BBS (called host mode) running under Procomm Plus for Windows, so defined users can dial up the system and transfer files. Users are defined using the hostutil script, which is also supplied. The system can be open (meaning new users can dial up and create accounts) or closed (so only predefined users can log on to the system). With the host script, the system can be set up to answer calls and determine if the call is a fax or data call. This feature is called adaptive answer. The Version 2.0 script language is enhanced from the Version 1.0 language and is significantly different from the DOS script language. The language, called ASPECT, borrows some elements from the C language and some elements from the PASCAL language. Scripts must be compiled using the script compiler (ASPCOMPW.EXE) before they can be run. The language contains support for modem dialing and sensing operations, and for faxing operations. Scripts can have string and integer variables and arrays, and can use a number of built-in functions or define their own procedures. Fax Modem Operations Procomm Plus 2.0 for Windows supports a number of popular fax modems. The initialization strings for these modems are contained in a file called WMODEMS.DAT. This file is regularly updated and can be downloaded from Datastorm's BBS or CompuServe forum to obtain support for new modems. If a particular modem is not contained in the current WMODEMS.DAT file, the correct initialization string can be determined by checking the modem's manual, or by contacting Datastorm or the modem manufacturer's technical support number. Like Microsoft's At Work Fax support, Procomm Plus supports faxing by installing a printer into Print Manager that can be selected by Windows programs. Faxing is then performed by selecting the Procomm Plus Fax Printer in the Select Printer dialog that generally appears in the File menu. Printing from the program will then bring up the fax dialog (Figure 5). This dialog is where the recipient's fax number and addressing information is specified, and a cover page is selected. The fax can be sent immediately or scheduled for a specific time, such as when long-distance charges are lowest. Files can also be faxed from within Procomm Plus for Windows, which has a menu for sending, receiving and managing faxes. There is also a Fax Status applet used to check the status of pending faxes and the fax modem. This applet can also start the dialog for sending and receiving faxes. The host mode script has facilities for using the adaptive answer feature of fax modems to distinguish between incoming faxes and data modem calls. This allows the same modem and phone line to be set up to receive faxes and perform file transfers while running unattended. In adaptive answer mode, the modem will first answer a call as if it were a fax call. If connection is unsuccessful after a certain time period, the modem will switch to data modem mode and attempt to connect to an incoming data call. Unfortunately, Procomm Plus 2.0 for Windows has problems with this feature on my modem, and the modem will not answer an incoming call at all when this mode is selected. Auto-answer only works when the Data Only mode is selected. Datastorm and the modem manufacturer (Practical Peripherals) are trying to resolve this problem. Using the IND$FILE Protocol IND$FILE is a protocol used for transferring files between a PC and an IBM mainframe. It works by breaking up the data and sending it as a screen of 3270 data, one screen at a time. I use it extensively at the office over a direct coax connection to the mainframe using Attachmate Extra! for Windows (Attachmate Corporation, Bellevue, Wash.). The ability to transfer data between my home PC and the mainframe over a modem is one of the most appealing features of this upgrade. I tested this feature by first connecting to IBM's IBMLink system over a modem and transferring a file. I generally connect to IBMLink as a VT100 terminal and experience no problems downloading using the IND$FILE protocol. Next, I connected to the office mainframe and attempted the same operation. I like to use the TVI950 emulation for connecting to the office, because the PC's function keys are mapped to the 3270 terminal's PF keys and is closer to using a real 3270 than the VT100 emulation. With a VT100, PF keys are mapped to the ESC-n key sequence (e.g., ESC-1 is PF1, ESC-5 is PF5, etc.) and requires two keystrokes instead of one for using a PF key. Unfortunately, the IND$FILE protocol does not work with the TVI950 emulation. The TVI950 and 3270 terminal emulations have a status bar at the bottom of the screen that looks like the real 3270 terminal's status bar. This is the bar that has the "clock" or "X-SYSTEM" status when the terminal is busy. The data for the status bar is apparently sent with each screen of 3270 data and confuses the IND$FILE protocol. Downloads and uploads kept failing with "Bad Block Number" messages. However, file transfers were successful when I connected using the VT100 emulation. The scroll back buffer for failed download and upload attempts using the TVI950 emulation were sent to Datastorm for analysis and problem resolution. I did not find a completely satisfactory terminal emulation for connecting to a mainframe. The TVI950 emulation does not map the Tab key on the PC to the 3270's Tab key. The CTRL-F9 key must be used for the Tab function instead. The IBM3101 terminal emulation did not map the 3270 Enter key to either the PC's Enter key or the right CTRL key, which would generally be expected for a mainframe terminal emulation. The keys can be remapped using a keyboard remapper utility, but I would expect the product should be shipped using the key mappings that mainframe users would most likely prefer. Conclusion Overall, Procomm Plus 2.0 for Windows is much improved over its predecessor. I especially like the new scroll back buffer capabilities, which allows many more pages to be retained and allows the data in the buffer to be captured, either by selecting portions of it with the mouse or by saving the entire buffer as a file. The new faxing capability is a nice feature for users who do not have a dedicated fax program or other faxing capabilities, such as Microsoft At Work. The addition of IND$FILE should be a welcome addition for users who work with IBM mainframes and would like to transfer files between work and home. I have encountered several difficulties in getting some of the new functions to work. In resolving these problems, I found the technical support personnel on the CompuServe DATASTORM forum to be diligent in getting to the bottom of the problems. They never failed to respond within a day or two with helpful advice that generally led to the solution. When they could not provide a solution, they would report the problem to the developers. Datastorm kept track of the message threads so the history of a problem and the actions taken to resolve the problem were maintained. The quality of the support provided by Datastorm is rare among vendors who provide on-line support. This reflects the quality of the products Datastorm has produced in the past and in the current release of Procomm Plus for Windows. Contact Information Datastorm Procomm Plus 2.0 for Windows address city, state, zip phone/fax Was this article of value to you? If so, please let us know by circling Reader Response Card No. . Figure 1: Procomm Plus 2.0 for Windows Terminal Window Figure 2: Setup Dialog Figure 3: Dialing Directory Entry Figure 4: Selected Text Pop-Up Window Figure 5: Send Fax Dialog