Home > Archive > Tcl > January 2006 > Customize properties on Windows starpack
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Customize properties on Windows starpack
|
|
| Kevin Walzer 2006-01-28, 7:56 am |
| I'm wrapping a Windows XP starpack on Mac OS X and have followed the
instructions at the link below for customizing the application icon:
http://www.equi4.com/267
These instructions work. However, the resulting executable, when run on
Windows, still lists "Tclkit--a standalone runtime for Tcl/Tk" in its
file properties, when viewed in Windows explorer.
Is there any way to edit this data on Mac OS X? A properties file
somewhere? Or is there a way to edit it on Windows? I've seen no
documentation on this, and have searched pretty extensively.
Thanks.
--
Cheers,
Kevin Walzer, PhD
WordTech Software - "Tame the Terminal"
http://www.wordtech-software.com
sw at wordtech-software.com
| |
| Steve Landers 2006-01-28, 7:05 pm |
| Kevin Walzer wrote:
> I'm wrapping a Windows XP starpack on Mac OS X and have followed the
> instructions at the link below for customizing the application icon:
>
> http://www.equi4.com/267
>
> These instructions work. However, the resulting executable, when run on
> Windows, still lists "Tclkit--a standalone runtime for Tcl/Tk" in its
> file properties, when viewed in Windows explorer.
>
> Is there any way to edit this data on Mac OS X? A properties file
> somewhere? Or is there a way to edit it on Windows? I've seen no
> documentation on this, and have searched pretty extensively.
Short answer - can't do it on the Mac (at least not a PPC based Mac).
This will help explain why -
http://thread.gmane.org/gmane.comp....cl.starkit/2347
Steve
| |
| Benjamin Riefenstahl 2006-01-29, 3:57 am |
| Hi Kevin,
Kevin Walzer writes:
> I'm wrapping a Windows XP starpack on Mac OS X and have followed the
> instructions at the link below for customizing the application icon:
>
> http://www.equi4.com/267
The method that is described there seems to just search for the
original icon in the executable and replace it with the new icon.
> However, the resulting executable, when run on Windows, still lists
> "Tclkit--a standalone runtime for Tcl/Tk" in its file properties,
> when viewed in Windows explorer.
That would probably be coming from the version resource in the
executable (I can't check, as I don't have XP). You could try to use
the same method for this. Load the whole binary into memory (using
[fconfigure -translation binary], of course). Search for the abovve
string, replace it with your own and save the result back again.
The strings in the version resource are encoded as little-endian
UTF-16 so the string to search for as well as the replacement need to
be in that format. You can use [encoding convertto unicode] to get
native UTF-16 and (only on PPC, not on Intel) a combo of [binary scan
S*] and [binary format s*] to byte-swap that to little-endian.
You also need to make sure that the replacement is not longer than the
original and that it has a string-terminating \u0000 character.
benny
| |
| Ramon Ribó 2006-01-29, 3:57 am |
|
Hello,
Does de information contained in
http://wiki.tcl.tk/8949
is useful?
Regards,
Ramon Ribó
En Sat, 28 Jan 2006 16:50:36 +0100, Benjamin Riefenstahl
<b.riefenstahl@turtle-trading.net> escribió:
> Hi Kevin,
>
>
> Kevin Walzer writes:
>
> The method that is described there seems to just search for the
> original icon in the executable and replace it with the new icon.
>
>
> That would probably be coming from the version resource in the
> executable (I can't check, as I don't have XP). You could try to use
> the same method for this. Load the whole binary into memory (using
> [fconfigure -translation binary], of course). Search for the abovve
> string, replace it with your own and save the result back again.
>
> The strings in the version resource are encoded as little-endian
> UTF-16 so the string to search for as well as the replacement need to
> be in that format. You can use [encoding convertto unicode] to get
> native UTF-16 and (only on PPC, not on Intel) a combo of [binary scan
> S*] and [binary format s*] to byte-swap that to little-endian.
>
> You also need to make sure that the replacement is not longer than the
> original and that it has a string-terminating \u0000 character.
>
>
> benny
--
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ramsan@compassis.com
c/ Tuset, 8 7-2 tel. +34 93 218 19 89
08006 Barcelona, Spain fax. +34 93 396 97 46
|
|
|
|
|