xtremexxx Posted September 26, 2004 Posted September 26, 2004 cmdlines.txt :[COMMANDS]"REGEDIT /S %SYSTEMDRIVE%\INSTALL\RegTweaks.REG"would this apply then ? the tweak is in $OEM$\$1\INSTALL
Tsunami Posted September 26, 2004 Posted September 26, 2004 Yes, and you don't have to open another thread for this. Just ask it in the QuickLaunch Reg Tweak thread
Rico.JohnnY Posted September 26, 2004 Posted September 26, 2004 According to the clarification posted before,Environment Variables were not supported in cmdlines.txt,you should use a batch file to do the job instead,then call the batch file from cmdline.txt using relative path
a06lp Posted September 26, 2004 Posted September 26, 2004 According to the clarification posted before,Environment Variables were not supported in cmdlines.txt,you should use a batch file to do the job instead,then call the batch file from cmdline.txt using relative pathwhat?You saying that [COMMANDS]"REGEDIT /S %SYSTEMDRIVE%\INSTALL\RegTweaks.reg"won't work in cmdlines.txt?Can anyone verify this?
troycicle Posted September 26, 2004 Posted September 26, 2004 Just use this:http://www.msfn.org/board/index.php?showtopic=28125&st=0Download my auto arrange script, and put it in wpihttp://www.msfn.org/board/index.php?act=ST&f=70&t=28238
xtremexxx Posted September 26, 2004 Author Posted September 26, 2004 a06lp I can verify it, you need a cmd to run it to work
prathapml Posted September 26, 2004 Posted September 26, 2004 cmdlines.txt :[COMMANDS]"REGEDIT /S %SYSTEMDRIVE%\INSTALL\RegTweaks.REG"would this apply then ? the tweak is in $OEM$\$1\INSTALLIf this tweak is already on the CD, why bother using variables?The cmdlines.txt essentially behaves like a batch-file. So the below will work(calling the REG directly from its location on CD):[code][COMMANDS]"REGEDIT /S $1\INSTALL\RegTweaks.REG":
xtremexxx Posted September 26, 2004 Author Posted September 26, 2004 But isn't the INSTALL dir copied to hdd at the time of cmdlines.txt is ran ?
prathapml Posted September 26, 2004 Posted September 26, 2004 Yes, but there's some people who can't get their tweaks running, or who were unable to get their CMDs working. The above post is for those situations - a simple, fail-proof solution.
a06lp Posted September 26, 2004 Posted September 26, 2004 @prathapmlso, I DON'T need a seperate .cmd file? I can just call the .reg file like this?[COMMANDS]"REGEDIT /S RegTweaks.reg"or should I move my regtweaks out of $OEM$, and put it in $OEM$\$1\Install ?
prathapml Posted September 26, 2004 Posted September 26, 2004 so, I DON'T need a seperate .cmd file? I can just call the .reg file like this?[COMMANDS]"REGEDIT /S RegTweaks.reg"Yes, if your RegTweaks.reg is located in the $OEM$ folder directly.Please note, that this is not the only way - you can do it your own way, using CMD files as well. What I describe above is only for the case where - if it isn't working for you, use it. If it is already working for you, no need to use this method, because its only to get you started successfully.All the best!
a06lp Posted September 26, 2004 Posted September 26, 2004 i am actually, currently using a double-whammy method.the above code if for installing all regtweaks that i can, early on, using cmdlines.txtthen i run regtweaks again (same file) later, after all other programs install.im hoping this way each tweak will be able yo apply, whether it has to be early or later.good idea? or no?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now