Hi,

I've been using cmdlines.txt to run WIHU for about 8 months with no problem.

Today, I tried to run WIHU with a parameter which required quotes and it seems cmdlines.txt doesn't appreciate.

So I decided to use an autohotkey script. Moreover, I've added some things to it I couldn't do before.

[Commands]
"rundll32 advpack.dll,LaunchINFSection nLite.inf,nLiteReg"
".\AHK\AHK.exe AHK\WIHU.txt"

My CD structure looks like

-$OEM$\AHK\AHK.exe

-$OEM$\AHK\lots_of_ahk_files.txt

Since I run cmdlines.txt to run autohotkey to run WIHU to run some installers, I'd like not to use another batch file.

The autohotkey script is OK, I'm sure about this, I've tested it.

My problem is that AHK.exe simply doesn't run.

How could I do that ?

Thanks for your answers.

I've always made my own VBscript for use with cmdlines.txt to get around the problem with quotes (and some other limitations as well). If you're not handy with VBscript, I'm sure batch could accomplish the same thing for you.

Sorry to ask that but since your text file WIHU.txt is in the same directory as the script, wouldn't you write simply:

".\AHK\AHK.exe WIHU.txt"

???

I don't know AHK, but usually progs are opening files relatively to their location.

Also, the tutorial uses / instead of \, but I don't know if it's a typo or a cmdlines.txt's feature!

Edited March 19, 200620 yr by Djé

Running the script is not the problem right now.

If you only run ahk.exe, a window pops up and if you're trying to load a script that does not exist, it will popup some error.

Also, I've read the guide and I assume this is a typo because using '/' makes absolutely no sense (because of switchs).

RogueSpear, thanks, I thought it was my fault.

Ok for that point.

Now, if you don't have any other solution you may have to check if AHK can be run at all from cmdline.txt.

Do you get the AHK window poping up by doing this?:

".\AHK\AHK.exe"

Just to let you know I've not solved it.

And right now, I'm busy with something else.