ProComm Diagnosis? 2

[zywex]

Might anyone have any (or seen them around?) applications that test ProComm outside of it's shell?

To clarify, say there's a Winsock error using one method of connectivity (broadband) but it works with another without issue (dial-up). Does anyone have any applications that test the protocols/ ports for stable connections that ProComm might use?

 

[kodr]

If I understand correctly, you're not looking to test Procomm actually, but the possible connections themselves?

 

[zywex]

Basically. To determine if an issue is coming from the ProComm install itself or if there's something a bit less-obvious affecting it.

 

[kodr]

Well, the simplist way (in my opinion) to test for the winsock error is to use windows built in Telnet. Try and connect that way. There are various tools available to track an IP related problem ( traceroute, ping, etc...)

In XP you can access Telnet by getting a command prompt and typing 'telnet'. ( without the leading and trailing ' marks )

 

[zywex]

An excellent point by itself (thanks by the way!). But what about with the integrated FTP client itself? Might anyone have any thoughts on testing that?

Or would the FTP client in DOS work essentially the same?

 

[knob]

The FTP client in Procomm is pretty limited, so I would think the DOS FTP client should be OK. If I recall correctly, Procomm's FTP client is based on the old freeware WSFTP program, so that is another avenue.

http://www.aspectscripting.com

 

[zywex]

Awesome. I didn't think it'd work out quite that simply. Thanks folks!