VisorCentral.com
Show 20 posts from this thread on one page

VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Serial Sycn prog with ThinkPad 600 and NT4.0 (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=1847)


Posted by Julie on 12-10-1999 03:33 PM:

Question

Ok folks, my boss has a new Visor. He bought a serial cradle to interface with his Thinkpad 600 that runs NT4.0. I've tried everything I can think of, but it will not sync at all. You press the button on the cradle and nothing happens on the Thinkpad. We have it set to com1. He has an internal modem (not PCMCIA) that is set to com2. His IR port has been disabled. We've uninstalled and reinstalled the Handspring Desktop. No go. Another person here at work has the same setup (as far as I can tell) and it works fine. Any ideas?


Posted by rdbailey on 12-10-1999 06:25 PM:

Post

I have the exact same setup. My Thinkpad 600 is in a docking station. I have the cradle set to COM1, IR disabled, using NT4.0. I didn't have any problems when I tried to sync. One thing that may be different is that since I'm using a docking station I've disabled my card services when I boot into "Network mode" (I've created a few different hardware profiles). I've had conflicts before because of the PCMCIA cards and since I don't use them disabling them has solved my problems. Good luck!

------------------
Rick Bailey
eFizz.com


Posted by Julie on 12-10-1999 07:18 PM:

Post

He doesn't have his in docking station. He's also using one of the PCMCIA slots for a network card.


Posted by Mr. Wizard on 12-10-1999 09:24 PM:

Post

Julie,
Have you tried connecting an external modem to that COM port? That at least would tell you if the COM port setting is valid. Use Hyperterminal to open up a modem session and use the AT command set to validate that you can talk to the modem.

Similar situation: I had a user with NT Workstation 4.0 trying to connect via null-modem to a Cisco hub. He tried everything and what it came down to was NT had created a device for COM2 when the actual physical connector was setup as COM1.

In order to fix it, I checked the COM port settings in the BIOS, deleted the COM2 port in Control Panel | Ports, and then restarted NT. After the reboot, I looked in Control Panel | Ports and COM1 was now active. I changed the speed settings to 19200 and it worked fine.

I've got a laptop, different model, and have had no problems with the serial cradle for the Visor.

First thing to check is make sure the port is what you think it is and that you can access the modem or other device using it.

Mark


Posted by JHromadka on 12-10-1999 10:42 PM:

Lightbulb

I would follow the procedure Palm has for testing the serial cradle. That way you can make sure that serial is working in NT.

------------------
James Hromadka
VisorCentral.com
Personal Website: http://www.Hromadka.com


All times are GMT. The time now is 03:02 AM.
Show 20 posts from this thread on one page

Powered by: vBulletin Version 2.3.4
Copyright © Jelsoft Enterprises Limited 2000 - 2016.