Occasional Odd Characters (wodSSH / wodSSH.NET)

Ive been working on a tool that will send and recieve files with a telnet server automatically, and right now I just have the basics in place. Right now the program is operated by hand. None of the automation code has been written yet. However I still see odd charcters being sent just after I finish calling SendFile or RecieveFile. I recorded a session so you can see what I am talking about. My Comments appear between {}. Any Idea whats causing this or how to stop it? These characters will make automation much more difficult if I can't make it stop.

-William

[code]
MAIN MENU

1) Logoff
2) Receive/Send File(s)
3) Change File Transfer Protocol [ZMODEM]
4) Change Compression Method [GZIP]
5) Request Transmission Status Report
6) Change Password

Enter your choice: 5

EFS ready for Report download.

{contents of the transfered files appear here.}

Report File transmission complete.

MAIN MENU

1) Logoff
2) Receive/Send File(s)
3) Change File Transfer Protocol [ZMODEM]
4) Change Compression Method [GZIP]
5) Request Transmission Status Report
6) Change Password

Enter your choice: ÿþ{I did not type this}
ÿü{or this}

Invalid menu selection. Try again.

MAIN MENU

1) Logoff
2) Receive/Send File(s)
3) Change File Transfer Protocol [ZMODEM]
4) Change Compression Method [GZIP]
5) Request Transmission Status Report
6) Change Password

Enter your choice:
[/code]

Because it may also be relevant to the problem,
I am connecting using SSLTelnetImp, And VT100 Emulation. I have tried adjusting these two properties but I am unable to connect with other settings.

William,

you use ZModem, right? Looks to me like client/server didn't negotiate with each other when transfer has finished, thus few garbage characters were sent to remote side.

Any chance we could duplicate that somehow? Can I connect to that server? If I can, can you send details to techsupport@weonlydo.com ?

Any chance we could duplicate that somehow? Can I connect to that server?

The information needed to connect has been sent. I am able to duplicate this 100 of the time. I suspect you will be able to as well. The only trouble is that this machine is a government computer, so we have no control over the other side of the connection.

William,

I got your email, will check it out later today.

I was thinking.. Why don't you set Prompt property to remote prompt, so that it fires when prompt is found. At that point you can discard any received information (garbled data) and proceed safely. If you look at helpfile for Prompt, you will see you can use regular expression that most probably covers your prompt too.

But I will be able to tell you more after I check it out.

At that point you can discard any received information (garbled data) and proceed safely.

The only problem I see with that is that it appears I am sending unintended data. It doesn't look like I am recieving anything I shouldn't.

If I'm correct, only one linefeed was sent after the upload.

This is now fixed - please request update.

Let me know how it goes!

I have been able to confirm that updating resolves this problem. Many thanks for your quick and helpfull support.

-William