Jump to content

Recommended Posts


Posted

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

Posted
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

what?

You saying that

[COMMANDS]
"REGEDIT /S %SYSTEMDRIVE%\INSTALL\RegTweaks.reg"

won't work in cmdlines.txt?

Can anyone verify this?

Posted
cmdlines.txt :
[COMMANDS]
"REGEDIT /S %SYSTEMDRIVE%\INSTALL\RegTweaks.REG"

would this apply then ? the tweak is in $OEM$\$1\INSTALL

If 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"

:thumbup:

Posted

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.

Posted

@prathapml

so, 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 ?

Posted
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!

Posted

i am actually, currently using a double-whammy method.

the above code if for installing all regtweaks that i can, early on, using cmdlines.txt

then 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?

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...