Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

The problem with "TclApp" and "Telnet"

1 view
Skip to first unread message

1985zho...@163.com

unread,
Apr 15, 2008, 8:53:10 PM4/15/08
to
Hi,
I have a question about "TclApp" and "Telnet". My program is about the
remote access to a ADSL DSLAM with "Telnet". I handle that with
"Expect". And when the code is Tcl extension, it works well. Then, I
compile it to EXE with TclApp. It turns out a problem. The EXE program
is ok in some PC. Howerver in others, it raises a problem that the
user name is not provided when the DSLAM ask for it. Thus, I fail to
have access to the DSLAM.
I have no idea why. Is there anybody who has a similar problem? And
can someone give me some advice. Thank you!

Regards,
zhoujingyu

Jeff Hobbs

unread,
Apr 16, 2008, 4:58:59 PM4/16/08
to

This has nothing to do with TclApp - it is Expect, and the limitations
that it as (or rather minimum requirements) to work being a specific
dbghelp.dll and no DEP enabled on the machine. See the expect mailing
list for more pointers.

Jeff

1985zho...@163.com

unread,
Apr 16, 2008, 9:22:30 PM4/16/08
to
On 4月17日, 上午4时58分, Jeff Hobbs <jeff.ho...@gmail.com> wrote:
> This has nothing to do with TclApp - it is Expect, and the limitations
> that it as (or rather minimum requirements) to work being a specific
> dbghelp.dll and no DEP enabled on the machine. See the expect mailing
> list for more pointers.
>
> Jeff

You mean that if I shutdown the DEP, like modify "/no execute" to "/
execute" in the boot.ini, My problem will be solved ?
However the PC that works well also has DEP enabled. It is "/no
execute=AlwaysOff" in the boot.ini, but not "/execute....".

Regards,
zhoujingyu

Donal K. Fellows

unread,
Apr 17, 2008, 10:12:22 AM4/17/08
to
1985zho...@163.com wrote:
> You mean that if I shutdown the DEP, like modify "/no execute" to "/
> execute" in the boot.ini, My problem will be solved ?
> However the PC that works well also has DEP enabled. It is "/no
> execute=AlwaysOff" in the boot.ini, but not "/execute....".

Might be easier to use plink.exe (part of the PuTTY suite of programs)
as your "telnet" since it is freely available and yet isn't (on XP at
least) protected by any DEP stuff. Indeed, plink's designed for being
driven by other programs (such as your Tcl/Expect scripts). Don't know
enough about how things work on Vista to know if what I've just said
applies there.

Donal.

1985zho...@163.com

unread,
Apr 17, 2008, 11:42:22 PM4/17/08
to
On 4月17日, 下午10时12分, "Donal K. Fellows"

<donal.k.fell...@manchester.ac.uk> wrote:
> Might be easier to use plink.exe (part of the PuTTY suite of programs)
> as your "telnet" since it is freely available and yet isn't (on XP at
> least) protected by any DEP stuff. Indeed, plink's designed for being
> driven by other programs (such as your Tcl/Expect scripts). Don't know
> enough about how things work on Vista to know if what I've just said
> applies there.
>
> Donal.

It works. Thank you very much!

Regards,
zhoujingyu+

0 new messages