Main Forum > Tweaking.com Support & Help
Improvements for WindowsRepair
Shane:
I will be updating Windows Repair today.
I will add this command to all command windows that are ran
set path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
This should make sure the repairs run on systems who's path is messed up :-)
Shane
Willy2:
I am lost. I tried a number of things to get the commands (Psexec and subinacl), as specified above, run without generating errors. Tried to use no, one and two quotation marks, with and without ampersands (""&""). Tried to use PsExec.exe and subinacl in a number of configurations but to no avail.
When I look at the entire picture then the thing that would make the most sense to me is that WR would issue/issues a ""PsExec Subinacl ...... "" command for every main directory on the C: drive. But then the question becomes: what's the purpose of the other commands ?
Are the commands ""takeown"" and ""inacls" not found in XP and in e.g. Vista and Win 7 only ? Does the entire set of commands/repair jobs work without errors on Vista and/or Win 7 only ?
In WR v1.0.0 ""reset file permissions"" seemed to work. So, Because it worked in WR version 1.0.0 what major changes have been made after that version ? Or perhaps you could make a separate version for XP only ?
In WR v1.5.4 you introduced a fix for the ""PATH"" problem. But I came across that ""PATH"" problem in SPB as well. So, I think you should improve that program, bring out a new improved version as well.
Shane:
Thats what I love about the bat files.
"takeown"" and ""inacls" is vista and 7. And if there is an error the bat file keeps on going, no harm no foul :wink:
--- Quote ---In WR v1.5.4 you introduced a fix for the ""PATH"" problem. But I came across that ""PATH"" problem in SPB as well. So, I think you should improve that program, bring out a new improved version as well.
--- End quote ---
Yes in SPB the only bat commands are for the services since I have it using the SC command.
I have to rewrite how I have it doing it. Right now it just runs the sc command directly. It isnt making a bat file.
SO I either need to have it make a bat file then run with the path command or just put the full path of the SC and that should work as well :wink:
Shane
Willy2:
About the ""PATH"" problem. To make it more clear: It seems SPB generates an error when it wants to use/access the programs ""netsh.exe"" (in ""C:\windows\system32"") and ""framedyn.dll"" (in ""C:\windows\system32\wbem"") (in a *.bat file ?). Are those things services (SC command) related ?
If these two files are accessed with a *.bat file then I think adding ""set path= ... "" would suffice.
I understand the advantages of a bat file. Because you do the same whe one wants to set the Services back to a safe/default state. But then the ""subinacl"" problem remains in WR. It generates a "" ....... security ID ...."" error and skips those files. See one of my posts above. Is this XP related only ? I'll try WR on a Win 7 machine. Perhaps everything works on such machine.
And this ""subinacl.exe"" problem begs other questions. In what other repair jobs is this same command used. It seems it doesn't work in e.g. repairing registry permissons of one (two, three, ......) registry hives and it does work when it wants to repair one other registry hive. I know there's more than one hive and only when WR processes one (the last ??) hive it shows a screen that clearly indicates that it's going across the registry keys of that hive. It even repots that resetting some of those permissions has failed.
Im sorry, but now I start to question whether these batch files work in any of the other repair jobs in XP. Because during other repair jobs CMD.exe opens and then it closes so fast as well that I can't determine what commands are executed and which generate a (non fatal) error in CMD.exe. And I DO want this program to work in XP as well, not in Vista and Win 7 only. :confused: , extremely :confused:.
Shane:
The program works just fine in XP.
subinacl.exe is a Microsoft file that is used for setting permissions. You will see some errors, on keys that it doesn't set or isn't allowed to set. Not a big deal. Some of the folders and and reg sections are small and so they get done very fast. The bigger reg sections and folders is where you will see the cmd window stay open longer. The windows directory and the hkey local machine are 2 large ones.
During the process of doing the repairs I found that on Windows 7 the trusted installer refused to let some keys get reset for the permissions. Only the system is allowed to touch them. Proble is when the permissions are messed up or changed by a virus. So the trick is then to use psexec.exe which is a sysinternals file that allows the cmd.exe to be ran under the system account. The repairs now have full permission on Windows 7 like they do on XP. (XP didnt have the annoying trusted installer)
I forgot about the netsh.exe in SPB, yes it is a another command that is called directly. And since the path isnt set on your machine you get the error. I just need to update SPB to point directly to the folder then it will be fine for you :-)
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version