Troubleshooting H/PC-to-Desktop Computer Connectivity (162116)

MORE INFORMATION

The following resources provide information for troubleshooting connectivity problems between your H/PC and your desktop computer using H/PC Explorer:

• Chapter 14, "Fine-Tuning And Troubleshooting," in the "Handheld PC User's Guide."
• The "Communication Troubleshooter" and "I have trouble connecting after my desktop computer wakes up from Suspend (or Sleep) mode" topics in H/PC Explorer Help.

If you continue to experience connectivity problems after following the instructions in these resources, perform the following steps. After performing each step, check to see if the problem has been resolved.

NOTE: These instructions assume that Windows is installed in the Windows folder on drive C. If you are using a different drive or folder, adjust the following instructions accordingly.

1. You may experience connectivity problems if there is not enough available program memory. To resolve this issue, follow these steps:
   
   
   1. Tap the Start button, tap Settings, and then double-tap System.
   2. Tap the Memory tab, move the slider to the left to free at least 135K of program memory, and then tap OK.
   3. Close all running programs, and then press the Reset button on your H/PC.
2. On your desktop computer, remove all the communications ports listed in Device Manager, and then restart your computer. If your computer does not redetect the communication ports when Windows starts, run the Add New Hardware wizard to redetect the ports.
3. On your desktop computer, remove H/PC Explorer and Direct Cable Connection using the Add/Remove Programs tool in Control Panel, remove all networking components, and then restart your computer. When your computer restarts, reinstall H/PC Explorer, which will reinstall the TCP/IP protocol, the Dial-Up adapter, and Direct Cable Connection.
4. Check for multiple copies of the Winsock.dll and Wsock32.dll files on your desktop computer's hard disk. The Winsock.dll file should be located in the Windows folder with a size of 42,080 bytes and a date of 07-11-95. The Wsock32.dll file should be located in the Windows\ System folder with a size of 66,560 bytes and a date of 07-11-95. Rename any other copies of the files.
5. Lower the baud rate. To do so, follow these steps.
   
   NOTE: These instructions require that your H/PC serial cable is connected to COM1 on your desktop computer.
   
   
   1. On your H/PC, tap the Start button, tap Programs, double-tap Communication, and then double-tap Remote Networking.
   2. Double-tap Make New Connection, type a name for the new connection in the "Type a name for the connection" box, tap Direct Connection, and then tap Next.
   3. In the "Select the device that you want to use" box, tap Serial Cable On COM1, and then tap Configure.
   4. In the Baud Rate box, tap a speed less than 19,200, tap OK, and then tap Finish.
   5. In Control Panel, double-tap Communications, tap the PC Connection tab, and then tap Change.
   6. In the Connect To Desktop Computer Using box, tap the name of the Remote Networking connection you created in step B, tap OK, and then tap OK again.
   7. On your desktop computer, double-click System in Control Panel, and then click the Device Manager tab.
   8. Double-click the Modems branch to expand it.
   9. Double-click Serial Cable On COM1 to open the Serial Cable On COM1 properties, and then click the Modem tab.
   10. In the Maximum Speed box, click the same speed (or baud rate) that you selected in step D, click OK, and then click OK again.
   11. Restart your computer.
6. Low battery power may result in connectivity problems. If your H/PC is equipped with an AC adapter, try to connect your H/PC and desktop computer while the H/PC is powered by the AC adapter. If your H/PC is battery-powered only, install new batteries and then try to connect.
7. If your desktop computer has more than one serial port, connect the cable to a different 9-pin serial port.
8. Try to connect using a different H/PC serial cable.
9. Disable all lines in the [386Enh] section of the System.ini file that have either of the following forms:

   device=<filename>.386
   						

   -or-

   com<number>=irq<number>
   						

   To disable a line, place a semicolon (;) at the beginning of the line. After disabling all such lines, restart the computer. If this resolves the problem, use the following process to determine which lines cause the problem:
   
   
   1. Re-enable one disabled line, and then restart the computer.
   2. If you do not experience connectivity problems, leave the line enabled. If you do experience connectivity problems, disable the line again.
   3. Repeat steps A-B until you have tested each line.
10. Disable the "load=" and "run=" lines in the [Windows] section of the Win.ini file by placing a semicolon at the beginning of each line, remove any programs from the Startup folder, and then restart the computer. If this resolves the problem, test each program on the "load=" and "run=" lines to determine which program causes the problem.
11. To eliminate the possibility of real-mode terminate-and-stay-resident programs (TSRs) and device drivers causing a problem, restart your computer. When you see the "Starting Windows 95/98" message, press the F8 key, choose Step-By-Step Confirmation from the Startup menu, and then load the following items when you are prompted:
    
    
    • Dblspace driver (if the hard disk is compressed).
    • Do not process the Config.sys file.
    • Himem.sys.
    • Ifshlp.sys.
    • Dblbuff.sys (if you are prompted).
    • Do not process the Autoexec.bat file.
    • Load the Windows graphical user interface (GUI), choosing to load all Windows drivers.
    If this resolves the problem, isolate the conflict with a TSR or real- mode device driver using the step-by-step confirmation function.
12. To create a new System.ini file that does not load third-party device drivers, follow these steps:
    
    
    1. Restart your computer to a command prompt. To do so, restart your computer, press the F8 key when you see the "Starting Windows 95/98" message, and then choose Command Prompt Only from the Startup menu.
    2. Type the following lines, pressing ENTER after each line:

                 cd \windows
                 ren system.ini system.xxx
                 copy system.cb system.ini
                 edit system.ini
       								

    3. Add the following lines at the top of the System.ini file:

                 [boot]
                 mouse.drv=mouse.drv
                 drivers=mmsystem.dll
       								

    4. Add the following line in the [386Enh] section of the file:

                 mouse=*vmouse
       								

    5. Save the System.ini file and then quit the editor.
    6. Type win to start Windows.
       
       NOTE: If your mouse does not work when Windows starts, it is likely that it is not supported by the standard Windows mouse driver. You can install the Windows 3.1 driver included with your mouse to regain mouse functionality. For information about installing the driver, consult the documentation included with the mouse.
13. Restore the registry files. For information about troubleshooting the registry files, see the "Using System.1st" and "Reinstalling Windows 95" sections in the following article in the Microsoft Knowledge Base:

    131431 How to Troubleshoot Registry Errors in Windows 95

14. Reinstall Windows to a new folder. This step helps to establish whether the problem is related to a remnant of the previous operating system (such as a configuration setting) or a hardware problem. For information about reinstalling Windows to a new folder, see the following article in the Microsoft Knowledge Base:

    142096 How to Reinstall Windows 95 to a New Folder

15. Install H/PC Explorer on a different desktop computer, and then connect your H/PC to the new computer. If you can successfully connect your H/PC to a different desktop computer, there may be a hardware problem with the serial port(s) on your desktop computer. If you cannot successfully connect to the new computer, perform steps 1-14 on the new desktop computer.

If you still cannot connect your H/PC to a desktop computer, the connectivity problem may be the result of a hardware issue such as a malfunctioning serial cable or H/PC. Contact the manufacturer of your H/PC.