AutoHotkey Community

Konnichiwa Ladiko-San

I would really like to know, how your Compiler changes the 'Versioninformation' of the Executable.
I already studied the Source-Code, but I can't understand the half of it.
I would really appreciate it, if you could help me, because I need a small 'Compiler' for a Application of mine.

Many thanks in advance,
ed

Guten Tag Shocked

What do you want your compiler to do what compile_ahk can't do? If it is a common useable feature, maybe it is easier to include it to compile_ahk instead of reinventing the wheel.

but never the less, take a look at the part starting at line 1828.

* short version:
versioninfo.txt -> versioninfo.res -> AutoHotkeySC.bin -> Compiled Script

* long version:
at first you need gorc.exe and reshacker.exe

create a text file f.e. versioninfo.txt and add the information you want / need. the default ahk-content looks like this:


then you callwhich produces a file named versioninfo.res which has be added to the autohotkeySC.bin via:

cause of a bug in reshacker (see line 1919), you have to call this too on non en-us systems:

now use this AutoHotkeySC.bin to compile your script and it has a changed VersionInfo.

Would you be able to allow 4 digits for the first field in Product/File version? Instead of using traditional file versions, I prefer to use the current date in the form of YYYY.MM.DD.

Thank you in advance for your consideration. CD

i changed the range to 9999 and will be available in the next version.

Hello,
I've found a bug: When Compile_AHK II reads the .ahk.ini file,
if Set_Version_Info is not set the Resource_Files key is not processed.
The problem is here (around line 1304):



Put the resource loading code before those lines to fix the problem.

thank you fince

Update of 2009-01-14

+ Fixed: if Set_Version_Info is not set the Resource_Files key is not processed
+ Changed: Range for all version fields raised to 4 digits

Download Compile_AHK

Hoping yal can help. Just upgraded to Vista, but the scripts that I compile in Vista won't run. Well, they run, but then it says, "The application has failed to start because it's side-by-side configuration is incorrect. Please see the application event log for more detail." Or, on other occassions (and different programs) it will say that the program has stopped working, it then "tries to fix the problem", but ultimately fails and then asks me to close the program.

I didn't have this problem in XP Eventually I'll compile some code on my old laptop (running XP) and see if I can't run them in Vista, but until then, hopefully yal can help.

_________________
As always, if you have any further questions, don't hesitate to ask.

Add OOP to your scripts via the Class Library. Check out my scripts.

at first:
is it possible to run uncompiled scripts?
is it possible to run compiled scripts?

at second:
the side-by-side configuration refers to the folder C:\Windows\WinSxS

as i understand the sense of this folder, it is like that:
cause of the problem of having the same dll used by different programs in different version and program X only works with the dll in version Y and program Z only works with the dll in version W ... instead of having the dll in C:\Windows\System32\ the side-by-side folder was introduced to separate the different version. the different versions exist side-by-side and windows manages which version is used by which program. but don't ask what's wrong with the winsxs-configuration and better don't touch the folder if you don't know what you do and off course don't delete nothing inside of WinSxS!

like the error message told you, start a application that fails and take a look at the windows event log:
Start -> eventvwr.msc -> windows logs -> application
and have a look for an entry that refers to your application.

edit:
i read your entry a second time and ... did you install vista to a fresh and clean partition/hdd or did you upgrade to vista over a existing xp installation?

yeah, I can run uncompiled fine, just not uncompiled. Haven't tested scripts compiled on XP running on vista yet. Actually... I used your compile_ahk program, isn't that a compiled script...? It ran fine, and even compiled the code - just had problems on run.

Never knew about event viewer. And, now that you showed me it, I'm not sure what to do with it. The program that closed says "faulting module ntdll.dll" and the side-by-side error one says "Error in manifest or policy file "C:\Users\Me\Documents\AutoHotKey\Test Code\BitCompress.exe" on line 0. Invalid Xml syntax."

_________________
As always, if you have any further questions, don't hesitate to ask.

Add OOP to your scripts via the Class Library. Check out my scripts.

animeaime,

Did you perform a custom Windows Vista install using a utility like vlite? You may have removed components that are required by AutoHotkey.

I use Vista at work and at home and I haven't experienced what you are reporting, but after performing a few searches on the Internet there are a few known causes of your issue.

1. Do you have Service Pack 1 installed on Windows Vista? If not, install it.
2. Try installing one of these: Visual C++ 2005 SP1 Runtime, Visual C++ 2008 Runtime, Visual C++ 2008 SP1 Runtime. They can be downloaded from the Microsoft website, I would recommend trying 2005 SP1 first.
3. Try installing .NET Framework 3.5 SP1.

Let me know if this helps.

Try to redownload and reinstall the AutoHotkey package - it's possible the .bin that you're trying to edit may be corrupt.

To be on the safe side, I'd recommend redownloading the Compile_AHK II script/exe too.

_________________
AHK tools by Drugwash (AHK 1.0.48.05 and Win98SE)

it works!!! thank you, thank you, thank you. Not sure if it's one of the updates or the fact I reinstalled autohotkey and the compilier, but it works!! did I mention thank you

my guess is that i had a bad autohotkey file. I've been moving them around some and also, I think I was using the new autohotkey but with the old bin... but, who cares, now to see if it was the update or not, and if not, remove them.

but again, thank you all so much.

_________________
As always, if you have any further questions, don't hesitate to ask.

Add OOP to your scripts via the Class Library. Check out my scripts.

line 296
Gui , Add , Edit , Center x+0 yp h20 w509 vGui_TPV2 ,
should be
Gui , Add , Edit , Center x+0 yp h20 w50 vGui_TPV2 ,




also around line 1304
IniRead , s_INI , %s_Ini_File% , %RES_Section% , Resource_Files , ERROR
If (s_INI != "ERROR") {
Resource_Files := s_INI
}

should put before
IniRead , s_INI , %s_Ini_File% , %RES_Section% , Set_Version_Info , ERROR

otherwise Set_Version_Info would be wrong set as Resource_Files