[Starkit] Re: SDX string customization of Windows starpacks

Gerald W. Lester glester-hmssoftware at cox.net
Thu Mar 17 16:23:32 CET 2005


jcw at equi4.com wrote:

>Date: Tue, 15 Mar 2005 12:20:54 +0100
>From: Jean-Claude Wippler <jcw at equi4.com>
>Subject: [Starkit] SDX string customization of Windows starpacks
>To: starkit list <starkit at equi4.com>
>Message-ID: <5f0f835322fc3c57147e8c832fb8cf7b at equi4.com>
>Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>There's a new tentative revision of SDX which can customize 
>version/description strings in a Windows executable.  This is 
>particularly useful for Windows XP, which shows such strings as balloon 
>popup when the mouse pointer is hovering over the exe.
>
>This code was submitted a long time ago by Aaron Faupell, and it's 
>taken me ages to get to it and integrate it with SDX.  Better late than 
>never, I hope.
>
>The SDX starkit is at http://www.equi4.com/pub/sk/sdx-new.kit
>
>To use it, create a "tclkit.inf" file at the top level of your app.vfs/ 
>tree.  This is similar in how tclkit.ico customization is done by SDX.  
>The contents of the tclkit.inf file is used in "array get" so it has to 
>contain valid Tcl pairs, for example:
>
>	FileDescription "test description"
>	FileVersion 1.2.3.4
>	LegalCopyright "no copyright"
>	OriginalFilename blah.exe
>	ProductName sdx
>
>The presence of this file *and* the -runtime flag with a file ending in 
>".exe" triggers the replacement logic when you run "sdx wrap".  You 
>have to include all strings you want to see in the exe, because 
>existing strings are dropped and only the ones you specify will go in.
>
>A report of what gets added will be displayed on stdout.  There's a 
>limit on what can go in, since the existing area is overwritten, but it 
>looks like that limit is not very low.
>
>There is one ugly caveat: this only works on little-endian 
>architectures (such as x86), since it requires 2-byte Unicode, and that 
>has a different byte order on for example PowerPC's.  For now, creating 
>a Win32 starpack from Mac OS X will not do the above customization 
>step. ...
>  
>
Second ugly caveat: it dies on building the StarPack if one is using a 
tclkitsh instead of a tclkit (at least it did when attempting to use 
http://www.equi4.com/pub/tk/8.4.9/tclkitsh-win32.upx.exe).

Any ideas?

-- 
+--------------------------------+---------------------------------------+
| Gerald W. Lester               | Email: GLester at hmssoftware.com        |
| Implementation Engineer        | Work: 504-304-6665, FAX: 504-324-6476 |
+--------------------------------+---------------------------------------+
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+




More information about the Starkit mailing list