TECHNICAL BULLETIN #164 - Rev 1.00 (7/31/96) ============================================================================== TITLE : PROCOMM PLUS 3.0 For Windows FAQ PRODUCT : PROCOMM PLUS 3.x for Windows ============================================================================== SETUP FREQUENTLY ASKED QUESTIONS ================================ QUESTION: When I attempt to run SETUP.EXE, I get the error: Microsoft Test Drive [DS] error. Bind Time Error Patch PW not found in Specific Library. -or- Invalid Dynamic Link call to a .DLL File ANSWER: This problem can be caused by an anti-virus program loading in the WIN.INI LOAD= statement, or by Novell redirector communication software loaded in the WIN.INI. To work around this problem, do the following: 1. Are the statements LOAD= and RUN= included in the [Windows] section of your WIN.INI? Is there anything following the "=" sign? Try removing everything following the "=" sign. You can go back later and test by adding each item in one at a time to see which interferes with PROCOMM PLUS for Windows. 2. Search for and rename the following files before installing: MSCOMSTF.DLL MSCUISTF.DLL MSDETSTF.DLL MSINSSTF.DLL MSSHLSTF.DLL MSUILSTF.DLL 3. If you are using Windows 95, rename the following files: CTL3D32.DLL CTL3DV2.DLL CTL3D.DLL If you are still having problems installing, ensure that you are not running Norton Anti-Virus, and attempt to install. If the install fails at this point, and you are running Windows 95, boot into Safe Mode and reinstall. If setup still fails, the final option is to reinstall Windows 95 on top of itself. There is an option to have it check the files and to replace corrupted or old ones with fresh copies. QUESTION: After I install PROCOMM PLUS 3.0 for Windows, my 32-bit programs that are running with Win32s quit working. I'm getting a Page Fault in UNKNOWN MODULE with a W32Sxxxx error message. Sometimes I have errors in COMPOBJ.DLL. ANSWER: The PROCOMM PLUS install looks at each file individually for version information. If that information is not available, the install looks at the date of the file. Unfortunately, these dates are not consistent and the installation program ends up installing only a portion of Win32s files needed for running 32-bit applications. DATASTORM has a script to remedy the situation. It is called w3us0003.exe and is on the BBS/CIS/FTP. The file contains a README.TXT, a TMP.PIF, and w32supdt.wax. KnowledgeBase Entry #23868 contains a copy of the README.TXT which tells... - How to install the script - What the script does - What each file does - How to restore if problems arise - Common problems and solutions NOTE: Our Win32s is not a complete install. You need a previous version to already exist for the program to supplement and upgrade you. If you do not have Win32s, do not use the script. Likewise, if you have a later version than our 1.30.152 version, do not use the script. To be absolutely sure of a proper setup, reinstall your previous version (most applications have a separate install for Win32s) and then run the script. ALTERNATIVE RESOLUTION: If all else fails, you may also reinstall your older Win32s files or install a newer version of Win32s. This is not recommended as we may not work properly on older Win32s and the newer versions are typically 2.5 - 3.0 Megabytes. Microsoft provides updates to Win32s via Application Notes. pw1118.exe (A Microsoft Application Note) is available at the following locations: CompuServe ---------- GO MSL Search for pw1118.exe Display results and download Microsoft Download Service (MSDL) --------------------------------- Dial (206) 936-6735 to connect to MSDL Download pw1118.exe Internet (anonymous FTP) ------------------------ ftp ftp.microsoft.com Change to the \SOFTLIB\MSLFILES directory Get pw1118.exe INTERNET FREQUENTLY ASKED QUESTIONS =================================== QUESTION: When I attempt to use any of the PROCOMM PLUS 3.0 for Windows Internet applets, I receive the following error message: No number to dial. My Internet connection is through my network. What causes this? ANSWER: This problem is caused by an incorrect Internet Connection setting. When installing, you selected Modem over Telephone Line. To work around this problem, do the following: 1. Click on Setup | Internet Connection. 2. Click Add New Connection, and select Local Area Network. 3. Your Current Internet Connection field should say Network Setup. QUESTION: My stack launches, but I am unable to connect to any Internet hosts. What can cause this? ANSWER: The following can cause this problem: - An incorrect DNS setup. - An incorrect or unspecified gateway address. (Usually for SLIP) - Header compression causing data corruption. To work around this problem, do the following: - Make sure that the DNS entries are set up correctly in Setup | Internet | Internet Connection | TCP/IP Settings. - Make sure that the gateway is correctly specified. For PPP, you can usually leave the gateway field in Setup | Internet | Internet Connection | TCP/IP Settings blank or use 0.0.0.0. - Disable header compression by unchecking the "Use Van Jacobsen/CSLIP compression" option in Setup | Internet | Internet Connection | Phone Access Settings. QUESTION: How can I add Proxy Server information? What is the format? ANSWER: Within Setup | Internet | Web Options | Proxies, the Web Proxy server address needs to be entered in this format: http://
: Even thought the http:// is already on the left, you will need to add it again along with the address. If you do not know the port for the proxy server, it is probably 80. QUESTION: How can I connect to Internet MCI or any other ISP that uses CHAP, PAP, or PPP? I can connect using Windows 95's dialer. ANSWER: To work around this problem, close PROCOMM PLUS 3.0 for Windows. Edit the SUPERTCP.INI file located in your \Windows directory. Go to the [PPP1] section and add the following (replace "logon name" and "password" with your specific information): [PPP1] UsrID=logon name UsrPasswd=password PROCOMM PLUS 3.0 for Windows requires an ASPECT script to logon before the stack can be initiated. This script, set in Current Setup | Internet | Internet Connection, should contain three lines: proc Main pause 3 endproc From the Main Terminal window, click on Script | Compile/Edit. Choose New. Create the script shown above. Compile it and name it. Then set it up in Current Setup as mentioned above. QUESTION: My POP3 received mail is not being deleted on my mail server. What can cause this? This problem does not occur with other mail readers ANSWER: There may be several reasons your received mail is not being deleted. Your ISP's POP3 daemon needs to be sent a QUIT command to end the session. PROCOMM PLUS 3.0 for Windows does not send the 'QUIT' command to the server appropriately. The command is sent, but the channel is closed before the QUIT command is received. Since your POP3 server never receives a QUIT command, the server assumes that the mail download failed, and doesn't purge the received mail messages. DATASTORM has confirmed this and has corrected it in an update called w3ul0002.exe. You can obtain this update from the PROCOMM PLUS - Windows Library on the Quarterdeck BBS, on our FTP site (ftp.quarterdeck.com), or on our Web site (support.quarterdeck.com). Other causes: - A corrupt spool file, which is the file on the server that contains all your mail messages. - A really long message that causes the server to timeout during the transfer of the message from the server to the client. This would be similar to an inactivity timeout. Possible timeout out values could be as low as 45 seconds. - All messages need to be retrieved before any will be deleted. The mail server will not delete any messages unless all messages are successfully received by the client. If, for example, there are 4 messages on the server and 3 transfer successfully, but the 4th does not, the server will not delete any messages, even if they transferred successfully. RESOLUTION: If your problems are caused by a corrupted spool file, have your ISP send you your spool file. If your problems are caused by your POP3 server requiring a QUIT command, apply the PROCOMM PLUS 3.0 for Windows update w3ul0002.exe. POP3 Servers that have this problem include: Version 1.0.0.2 of the POP3 daemon on SunOS 4.1.3 Netcom's POP Server QUESTION: When I attempt to create a login script, ISPREC.WAX fails. ANSWER: This problem is caused by a program called LongFileNames. It can be configured for each application. To work around this problem, disable LongFileNames, and you will be able to create your login scripts QUESTION: When I attempt to reply to email using the PROCOMM PLUS 3.0 for Windows's Mail client, my reply signature is located at the beginning of the message instead of at the end of the message. ANSWER: To work around this problem, you need to add the following PW3.INI setting to the [Email] section. [Email] Reply Below=1 Be certain that you place a space between Reply and Below. You may need to exit out of PROCOMM PLUS and restart. WINDOWS NT FREQUENTLY ASKED QUESTIONS ===================================== QUESTION: Can I use PPP or SLIP under Windows NT, using PROCOMM PLUS 3.0 for Windows? ANSWER: Yes. You will not be able to use the PROCOMM PLUS 3.0 for Windows stack, you will need to use Windows NT 3.5x's RAS client to connect to your Internet Service Provider (ISP). Below is an excerpt from the Windows NT 3.5x Remote Access Help: "Windows NT version 3.5 clients negotiate logon and authentication with the server, whether the server is a Microsoft RAS server, a PPP server, or a SLIP server. You can also configure RAS phone book entries to use scripts that can completely automate logon." NOTES: Both PPP and SLIP have been successfully tested. The PROCOMM PLUS 3.0 for Windows 16-bit stack does NOT work under Windows NT. PROCOMM PLUS for Windows 2.x and PROCOMM PLUS 3.0 for Windows work with Windows NT 3.5x's network stack. PROCOMM PLUS for Windows 2.x FTP and Telnet clients will work as well. Contrary to the Stack Compatibility Guide (dated 12/21/94), Windows NT does support SLIP or PPP. Under Setup | Internet | Internet Connection, make sure the Current Internet Connection is set to "External Network/Dialer". QUESTION: When I attempt to create a fax using PROCOMM PLUS, I am unable to do so. I'm running under Windows NT. ANSWER: This problem occurs because Windows NT uses different proprietary hooks for fax and some forms of communication. This information has been requested of Microsoft but to date we have not been able to obtain it, even though Microsoft appears to have provided it to some other companies. NOTE: You will be able to fax any received faxes or any pre-existing .fax files. FAXING FREQUENTLY ASKED QUESTIONS ================================= QUESTION: When I am using the WRPI.DRV replacement COMM.DRV file, and I attempt to generate a fax, my system locks at around 97%. In this case, the modem being used was a USR Sportster 14.4 SI. ANSWER: To work around this problem, change the SYSTEM.INI setting back to COMM.DRV=COMM.DRV. QUESTION: I am unable to send a multiple page document to several locations. It dies at the end of the first page and shows a Fax Protocol Error 2-154. I have a Supra 28.8 modem. ANSWER: Your settings are incorrect. You may have software flow control set instead of hardware flow control. To work around this problem, set your fax init string to AT&K4E0^M, your flow control to Hardware, and the Fax Class to Class 1. General QUESTION: What's the easiest way to automatically start PROCOMM PLUS or a component upon Windows startup? ANSWER: The easiest and least problematic way to do this is to copy the PROCOMM PLUS (or other program) icon or shortcut to the Startup Group. ========================================================================== To ensure that you have the latest version of this document, compare its revision number to that of the same document on any of our support sites. This technical bulletin may be copied and distributed freely as long as it is distributed in its entirety and it is not distributed for profit. Copyright (c) 1996 Quarterdeck All rights reserved. ==========================================================================