cmdlines.txt

[durex]

Exactly what commands does the cmdlines.txt accept?

Everything a normal batch file can?

System Variables?

Calls to VBScripts?

Calls to executables?

Thanks!

[jbm]

cmdlines.txt is not a batch file. You list files

that you want to run for example if you have to batch files

install.bat and fix.bat then your cmdlines text would look like

[COMMANDS]

"install.bat"

"fix.bat"

you can allso include exe files

this is all in the guide

Jim M

[Alanoll]

CMDLINES.TXT is actually a VERY limited commandline interpreter. The closest similarity of it is the RUN box in windows. But unlike the RUN box, a few file associations are not created, and so depending on the file you have to use the full execution path instead of the shorter version... ie.

msiexec.exe /i setup.msi

vs

setup.msi

[durex]

@jbm

I am well aware of the guide points out... but what youve stated is the only thing the guide outlines, which is not the only function the cmdlines.txt provides as I knew and as Alanoll touches on...

@Alanoll

Thanks for the response... do you know of anything out there that outlines what commands it doesnt and/or doesnt support? I know you can import reg files as well using REGEDIT /S regfile.reg..

thanks again!

[jbm]

I thought that all the files that cmdlines.txt ran had to be in the same folder

as cmdlines.txt. I run two files in mine, regfile.bat and install.bat plus about

6 others. Are you saying instead of putting

"regfile.bat" I could put "regedit /s changes.reg"

But what about the requirement stated above? Or am I missing something?

[MCT]

yes jbm

& the files dont have 2 be in the same folder either, u just have to use . (periods) to point to the file instead

example

[COMMANDS]
"REGEDIT /S ..\Install\Reg\CU_regtweaks.reg"
"..\Install\Xplode\Xplode.exe"

would work if your directory structure is:

Root

........$OEM$

........Install

.................Reg

.................Xplode

[totoymola]

the files dont have 2 be in the same folder either, u just have to use . (periods) to point to the file instead

example

CODE

[COMMANDS]"REGEDIT /S ..\Install\Reg\CU_regtweaks.reg"

"..\Install\Xplode\Xplode.exe"

Hmmm.. That makes sense. Just like in the command CD.. in DOS.

[Alanoll]

like I said, a very LIMITED command line. Sorta like a runbox.

There are a FEW DOS commands that work, but MOST do not. REGEDIT isn't a DOS command, it's a program located in System32.

You can call anything you want from CMDLINES.TXT, whether or not it will run is dependent on the requirements on the system as Windows isn't fully functional, and whether or not you put the correct path (unless the program is already in the %PATH% like REGEDIT) or whether it's an internal DOS functions or now (CD, FOR, IF, CALL, ECHO, TITLE, etc.). For simplicifty, just think of it like the runbox in Windows, as that's almost what it is.

[durex]

Thanks guys

[jbm]

Yes, Thanks guys I've learned something today.

I wonder where I got the idea that the commands had to be in the

same folder.

[MCT]

probly from here jbm

http://unattended.msfn.org/xp/hkcu_registry.htm