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

Error in TclKit

11 views
Skip to first unread message

Satoshi Imai

unread,
Feb 7, 2004, 8:12:34 PM2/7/04
to
Hello.

I've used the tclkit-win32.upx.exe for Tcl/Tk 8.4.5 on WindowsXP.
I get the startup error in a tk_messagebox:
Title: Error in TclKit

This error does not occur on almost all PCs.
but unfortunately this error occurs on some PCs.
I do not understand the difference.
Which version of UPX does Tclkit use?
Can UPX which Tclkit uses be changed?

Unless it can solve this cause, application of the Starpack version
cannot be distributed.

How do I work around?

-----
Satoshi Imai
s-i...@japan.interq.or.jp

Jean-Claude Wippler

unread,
Feb 8, 2004, 5:37:32 AM2/8/04
to
s-i...@japan.interq.or.jp (Satoshi Imai) wrote...

> I've used the tclkit-win32.upx.exe for Tcl/Tk 8.4.5 on WindowsXP.
> I get the startup error in a tk_messagebox:
> Title: Error in TclKit
>
> This error does not occur on almost all PCs.
> but unfortunately this error occurs on some PCs.
> I do not understand the difference.

There has to be some difference.

Does it happen when you launch Tclkit without args / script?

Does it depend on from where Tclkit is launched (spaces or non-ASCII
characters in path name, server)?

UPX vsn 1.24, but there is also a Tclkit which is not based on UPX:
http://www.equi4.com/pub/tk/8.4.5/tclkit-win32.exe.gz
Please download, uncompress with WinZip, and compare results.

-jcw

s-imai

unread,
Feb 8, 2004, 9:35:37 AM2/8/04
to
Hello.

Even if it does not have an argument, it happens.
A space or non-ASCII character is not on the path of Tclkit.
I've tried the UPS 1.24.
In the environment where Tclkit does not launch, once it does UPX recompression of the Tclkit, it will launch well. Why?

$ upx -d tclkit-win32.upx.exe
$ upx -9 tclkit-win32.upx.exe

-----
Satoshi Imai
s-i...@japan.interq.or.jp


Satoshi Imai

unread,
Feb 8, 2004, 9:23:29 PM2/8/04
to
Hello.

"s-imai" <s-i...@japan.interq.or.jp> wrote...


> Hello.
>
> Even if it does not have an argument, it happens.
> A space or non-ASCII character is not on the path of Tclkit.
> I've tried the UPS 1.24.
> In the environment where Tclkit does not launch, once it does UPX recompression of the Tclkit, it will launch well. Why?
>
> $ upx -d tclkit-win32.upx.exe
> $ upx -9 tclkit-win32.upx.exe

I'm sorry, my writing is corrected.
The non-ASCII character was on the path of Tclkit.

Thank you.

-----
Satoshi Imai
s-i...@japan.interq.or.jp

0 new messages