Hiya folks. I've put this great interface design together with ProntoEdit, but I have one "little" problem. I can't get ProntoEdit to talk to the Pronto!

I'm running Windows NT and have set up COM2 as 115200, 8, N, 1. It cannot get a response from the Pronto. I tried COM1 as well, same lack of response. BTW - I can hotsync to my Pilot out of either port.

Is there something magical you have to do with Windows NT to make the two talk?

Thanks!

-greg

Have you tried disabling ALL Pilot-related software? It tends to mess up communications with the Pronto since it constantly monitors the port(s?).

I have ProntoEdit working both on W98 and NT4 (SP4) with no problems. BTW I also have a Pilot on my W98 machine. The Pilot and Pronto are on different COM ports. When I connected it to my NT4 machine, it found it no problem . . .

John Hurlbut, MCP

Thanks for the feedback. Someone from Pronto Support called me back just a moment ago. He seems to think that I've either got a bad cable or there's something wrong with the Pronto itself. He's sending me a new cable to try. Here's hoping it works!

-greg

I am running ProntoEdit on NT4sp3. At first I was trying to use COM3 and ProntoEdit couldn't see the Pronto. I moved things around so that the ProntoEdit could use COM1. Then things worked fine.

Greg,

ProntoEdit should work fine on NT. In fact, I switched from 95 to NT about halfway through the development of ProntoEdit. I think you're experiencing a problem that has troubled more ProntoEdit users which is caused by the 'not quite perfect' serial port scanning approach in ProntoEdit. As Richard suggested, using a different port for your Pronto may fix the problem. You should also check the details of the error message in ProntoEdit to determine if it can open the port your Pronto is connected to or if that port is in use by another application.

I don't think your cable is at fault.

Regards,

Jan

Hi Greg,

I'm running ProntoEdit under Win NT (SP4) with no problems. Except that ProntoEdit seems only to work on COM1. So I had to switch the cable of my Psion to COM2, then it worked. In the PsiWin Settings, I also disabled port scanning for COM1, perhaps there's a similar option in your Hotsync software to ignore COM1.

Regards
Fermin

Make sure you close the PalmPilot HotSync Manager because it does "hold" the COM port even if the cradle is not connected.

I never could get my Pronto to work correctly on any COM port under Windows 98. ProntoEdit could download from the Pronto, but never the other way around, despite all of my other devices working perfectly on both. While trying to update the firmware form within ProntoEdit, the upload failed and corrupted the CCF in the Pronto. From that point on, the Pronto ceased working, and no efforts to reset it (using several different computers) could get it to work again.

I am currently waiting for a replacement from my vendor. I am very nervous about this happening all over again.

I am having problems getting Pronto Edit to install on Windows NT Workstation 4.0. It goes through the install process with no error messages. After the install process is completed, I can not find the "exe" file anywhere on the harddrive. If I click on a CCF file it only starts the install process again.

Can anybody help me out?

Thanks

Hmm, it should install itself into c:\program files\pronto\ - check there.

Make sure that any anti-virus software is turned off, and that the MS Office Toolbar is not loaded. These two things can cause unseen havoc with program installations if they are running in the background.

Not there! I have loaded the setup file again and run the setup program. No luck. It did install to the notebook PC and I am able to get it running there.

Thanks for the thoughts from everyone. However, it still isn't working. I've switched over to COM1 on the NT.

I also tried to talk to it directly with HyperTerminal (by following the directions I found on one of the Mac threads). No luck there either. I never saw the asterisk prompt and no amount of talking to it would work (xmodem send, xmodem receive, etc).

Hopefully the replacement cable will show up tomorrow. Any other ideas?

Thanks!

-greg

Waxdonuts,

Did you logon to NT4 workstation as an administrator, could be the permission issue on NTFS, this is very common.

Monto