Change HyperTerminal seconds till timeout on file transfer

[John Hupp]

Hello all.

When you initiate a file transfer (at least with Zmodem) on HyperTerminal,
the transfer must begin within about 30-45 seconds or the transfer will be
stopped by a timeout. That's fine if you're downloading from an automated
bulletin board or the like, but if you are transferring files between
computers that are separated by 100-200 feet and you have to walk between
them to initiate the transfer on the second machine, it won't work. Zmodem
"Auto Downloads," but only if Zmodem is running on both machines before
timing out.

So is there a way to kill the timeout feature, or else set it to, say, twice
as long before it times out? (For instance, can I create a configuration
file that Hyperterminal will look at, or change something in the registry?)

John Hupp
PRP Company

 

[Richard G. Harper]

The timeout is a function of the file transfer protocol, not Windows. You'd
need to modify the Zmodem protocol to allow a longer timeout. There's no
way to do this from Windows.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[John Hupp]

Richard,

Thanks for a clear and authoritative answer, even if it wasn't what I wanted
to hear.

To an off-Windows follow-up: do you perchance know if the timeout wait is
hard-coded into the protocol, or if fuller communications apps typically
open up that setting as user-configurable?

John Hupp

 

[Richard G. Harper]

The timeout is usually hard-coded in the protocol - in this case I know it
is because I've both used and written ZModem protocol-based software. Some
software products do allow you to alter protocol timing but you do this at
your own risk.

For example, if the protocol specifies that ten attempts to connect will be
made three seconds apart then the total wait time is only thirty seconds.
You can change your end of the software to allow, say, 15 attempts five
seconds apart but if the computer at the other end of the protocol isn't
similarly changed it won't make any difference because the other side will
still time out after thirty seconds.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[John Hupp]

That's a point well taken (about it taking two to tango--or communicate),
but in this case I will control both ends of the line.

I did find some specialty software (for a computer-to-machine-tool
application) that appears to allow changing the delays, and it looks like
that will serve.

Thanks again for a clear explanation of the case with HyperTerminal.

The timeout is usually hard-coded in the protocol - in this case I know it
is because I've both used and written ZModem protocol-based software.
Some software products do allow you to alter protocol timing but you do
this at your own risk.

For example, if the protocol specifies that ten attempts to connect will
be made three seconds apart then the total wait time is only thirty
seconds. You can change your end of the software to allow, say, 15
attempts five seconds apart but if the computer at the other end of the
protocol isn't similarly changed it won't make any difference because the
other side will still time out after thirty seconds.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Richard,

Thanks for a clear and authoritative answer, even if it wasn't what I
wanted to hear.

To an off-Windows follow-up: do you perchance know if the timeout wait is
hard-coded into the protocol, or if fuller communications apps typically
open up that setting as user-configurable?

John Hupp

 

[Richard G. Harper]

Glad I could be of assistance.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

That's a point well taken (about it taking two to tango--or communicate),
but in this case I will control both ends of the line.

I did find some specialty software (for a computer-to-machine-tool
application) that appears to allow changing the delays, and it looks like
that will serve.

Thanks again for a clear explanation of the case with HyperTerminal.

The timeout is usually hard-coded in the protocol - in this case I know
it is because I've both used and written ZModem protocol-based software.
Some software products do allow you to alter protocol timing but you do
this at your own risk.

For example, if the protocol specifies that ten attempts to connect will
be made three seconds apart then the total wait time is only thirty
seconds. You can change your end of the software to allow, say, 15
attempts five seconds apart but if the computer at the other end of the
protocol isn't similarly changed it won't make any difference because the
other side will still time out after thirty seconds.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Richard,

Thanks for a clear and authoritative answer, even if it wasn't what I
wanted to hear.

To an off-Windows follow-up: do you perchance know if the timeout wait
is hard-coded into the protocol, or if fuller communications apps
typically open up that setting as user-configurable?

John Hupp