ProComm Telnet Capture File work around

[SvenHeadRoom]

I read (here) that Procomm automatically opens capture files (bug) in telnet mode, pisser. I need a work around. Creating the 'Connection Directory' entry in Aspect (dialadd TELNET "ip") then a second script to use the entry (connect TELNET "ip") looks to be my best bet. The boss is still not happy. Any better solutions out there?

 

[kodr]

I've never known Procomm to open a capture file automatically. I've either had to hit the File Capture button, or made it happen with code.

Now, the name of the file is automatic, but you can get around that simply enough with a few lines of code.

 

[knob]

Procomm does not open capture files automatically in telnet (or data) mode, but there is a bug where capture files are not turned on automatically if you have that option selected.

http://www.aspectscripting.com

 

[SvenHeadRoom]

I finally figured it out

The solution:

dialadd TELNET "DWTelnet"
set dialentry access TELNET "DWTelnet"
set dialentry ipaddress "207.186.1.1"
connect TELNET "DWTelnet"
set dialentry access off

Without 'set dialentry off', I had no control over the name of the capture file. Feel free to explain.

Stand by, I'm working on a new one, "detecting Winsock failure".

 

[knob]

I am not seeing the same issue you are. There is a bug in Procomm where a capture file is not opened automatically on connection (only for telnet, works in data mode). Thus, if you specify a script that sets a capture file and opens the capture file, it will use that file instead of what you specified in the Connection Directory.

Can you list the steps you are taking and how your Connection Directory entry is configured with respect to capture files?

http://www.aspectscripting.com