|
The "can't find setup.tcl" message is caused by whatever it is that gets added
at the end
of tclkit: the VFS with all runtime files is at the end of tclkit, and is read
by starting from
the end. The 'addition' you describe breaks that mechanism.
Hm. What exactly are you doing? The "kit.exe" files are *not* complete tclkits.
Please
get /pub/tk/8.4.2/tclkit-win32.upx.exe and try again - I wonder
what kit.exe's you're using? These do indeed look for a setup, but that's because
the
apps are incomplete and you'tr triggering some sort of build completion.
Note that Tclkit builds have changed completely over the past years. Could there
be
some stale docs that are leading you down a wrong (obsolete) avenue? |
|
I've just finished unwrapping the latest 8.4.2 tclkit-win32.upx.exe
and tclkit-win32-sh.upx.exe and all the files are as they should be.
I then closed my file explorer (this is win98)and reopened it and
found the following bug:
application-specific initialization failed: couldn't open "setup.tcl":
no such file or directory
can't find package starkit
while executing
"package require starkit"
(file "sdx.kit" line 4)
A breif note on file sizes before and after for upx.exe's:
tclkit tclkitsh
before 937,496 460,944
after 1,115,902 639,236
Strange to say the least! |