Hi,
I have installed vista in my comp and now wanted to run WPI stand alone. To avoid UAC, data protection, ownership problem I want to run WPI as an super admin (that is actually hidden unless we enable it). Is there any commandline option or argument hat tI can pass while calling WPI installer?
Thanks in advance,
Pokemon
Full Version: Running WPI in admin mode Vista (Hidden Super admin)
Ummm kinda but you needd to do it manually and reboot first.
Vista is a pain in the a$$....
Vista is a pain in the a$$....
QUOTE (Kelsenellenelvian @ Sep 2 2008, 09:48 PM) 
Ummm kinda but you needd to do it manually and reboot first.
Vista is a pain in the a$$....
Vista is a pain in the a$$....
Thx Kel, can you pls elaborate?
http://www.petri.co.il/disable_uac_in_windows_vista.htm
Method 2 should do fine... Make 2 reg files and run one before WPI then reboot. Add the second one (Re-enabling UAC) to WPI's execute after.
As for elevated abilities you need to do that on a file for file basis.
Study this cmd file here:
I use this to replace the uxtheme files.
You would need to use similiar methods to copy\modify files with WPI
(Please keep in mind though I only adopted Vista AFTER SP1 was released) I had beta tested it and tested it for a little while when it was first released and found that I greatly disliked it.
Now though it's not so bad....
I am pretty sure there is better ways but I don't know them.
Method 2 should do fine... Make 2 reg files and run one before WPI then reboot. Add the second one (Re-enabling UAC) to WPI's execute after.
As for elevated abilities you need to do that on a file for file basis.
Study this cmd file here:
CODE
takeown /f %systemroot%\System32\uxtheme.dll
icacls %systemroot%\System32\uxtheme.dll /grant administrators:F
ren %systemroot%\System32\uxtheme.dll uxtheme.old
xcopy /y %systemroot%\System32\Patches\uxtheme.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\themeui.dll
icacls %systemroot%\System32\themeui.dll /grant administrators:F
ren %systemroot%\System32\themeui.dll themeui.old
xcopy /y %systemroot%\System32\Patches\themeui.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\shsvcs.dll
icacls %systemroot%\System32\shsvcs.dll /grant administrators:F
ren %systemroot%\System32\shsvcs.dll shsvcs.old
xcopy /y %systemroot%\System32\Patches\shsvcs.dll "%systemroot%\System32\"
icacls %systemroot%\System32\uxtheme.dll /grant administrators:F
ren %systemroot%\System32\uxtheme.dll uxtheme.old
xcopy /y %systemroot%\System32\Patches\uxtheme.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\themeui.dll
icacls %systemroot%\System32\themeui.dll /grant administrators:F
ren %systemroot%\System32\themeui.dll themeui.old
xcopy /y %systemroot%\System32\Patches\themeui.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\shsvcs.dll
icacls %systemroot%\System32\shsvcs.dll /grant administrators:F
ren %systemroot%\System32\shsvcs.dll shsvcs.old
xcopy /y %systemroot%\System32\Patches\shsvcs.dll "%systemroot%\System32\"
I use this to replace the uxtheme files.
You would need to use similiar methods to copy\modify files with WPI
(Please keep in mind though I only adopted Vista AFTER SP1 was released) I had beta tested it and tested it for a little while when it was first released and found that I greatly disliked it.
Now though it's not so bad....I am pretty sure there is better ways but I don't know them.
QUOTE (Kelsenellenelvian @ Sep 3 2008, 01:48 AM)
As for elevated abilities you need to do that on a file for file basis.
Study this cmd file here:
I use this to replace the uxtheme files.
You would need to use similiar methods to copy\modify files with WPI
Study this cmd file here:
CODE
takeown /f %systemroot%\System32\uxtheme.dll
icacls %systemroot%\System32\uxtheme.dll /grant administrators:F
ren %systemroot%\System32\uxtheme.dll uxtheme.old
xcopy /y %systemroot%\System32\Patches\uxtheme.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\themeui.dll
icacls %systemroot%\System32\themeui.dll /grant administrators:F
ren %systemroot%\System32\themeui.dll themeui.old
xcopy /y %systemroot%\System32\Patches\themeui.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\shsvcs.dll
icacls %systemroot%\System32\shsvcs.dll /grant administrators:F
ren %systemroot%\System32\shsvcs.dll shsvcs.old
xcopy /y %systemroot%\System32\Patches\shsvcs.dll "%systemroot%\System32\"
icacls %systemroot%\System32\uxtheme.dll /grant administrators:F
ren %systemroot%\System32\uxtheme.dll uxtheme.old
xcopy /y %systemroot%\System32\Patches\uxtheme.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\themeui.dll
icacls %systemroot%\System32\themeui.dll /grant administrators:F
ren %systemroot%\System32\themeui.dll themeui.old
xcopy /y %systemroot%\System32\Patches\themeui.dll "%systemroot%\System32\"
takeown /f %systemroot%\System32\shsvcs.dll
icacls %systemroot%\System32\shsvcs.dll /grant administrators:F
ren %systemroot%\System32\shsvcs.dll shsvcs.old
xcopy /y %systemroot%\System32\Patches\shsvcs.dll "%systemroot%\System32\"
I use this to replace the uxtheme files.
You would need to use similiar methods to copy\modify files with WPI
Thx Kel, eye opener. Any idea whether it is possible to 'take ownership' of complete folder i.e 'Program files' etc using the above mentioned batch. I can do it manually using 'take ownership' reg key and shift+righclick combination however never automated it through batch file.
http://windowsitpro.com/article/articleid/...mmand-line.html
I think this seems like the easiest way..
I think this seems like the easiest way..
Kel, thanks. I will try this but I suspect it may be quite messy as i need to take ownership for each and every file I wud like to copy.
Is there any command line option while calling WPI.hta? It would be quite handy?
Is there any command line option while calling WPI.hta? It would be quite handy?
Command line uses of WPI
WPI supports the use of command line entries for selection of Options, Config files and time for even further customization of your WPI disks or setups.
Example: WPI.hta options=useroptions_mritter.js config=config_mritter.js check=Work timer=30
If a path is not specified for the file, it will assume they are in the WPIScripts folder.
Paths can be full (starting with a drive letter) or relative to WPI.hta (starting with '.\' or '..\') and must end in '.js'.
Spaces are supported only is a path is provided and properly quoted: (config="c:\space in\file path.js")
WPI supports the use of command line entries for selection of Options, Config files and time for even further customization of your WPI disks or setups.
Example: WPI.hta options=useroptions_mritter.js config=config_mritter.js check=Work timer=30
If a path is not specified for the file, it will assume they are in the WPIScripts folder.
Paths can be full (starting with a drive letter) or relative to WPI.hta (starting with '.\' or '..\') and must end in '.js'.
Spaces are supported only is a path is provided and properly quoted: (config="c:\space in\file path.js")
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.