Main Forum > Tweaking.com Support & Help

Improvements for WindowsRepair

<< < (4/8) > >>

Willy2:
WEIRD !!!! I ran it that task two times and now it took 13 seconds and 1 minute 5 seconds. Yes, sometimes the CMD.EXE windows open (and close (of course)) all at the same time and then they open one after another. :confused: Perhaps one should close as much programs as possible.

Is my system to blame (outdated ???). One problem was solved by removing one program that helped me to update my NOKIA mobile phone. But even then WR should behave in - IMO - a more regular/stable fashion. Perhaps I should try the separate programs that contain only ONE repair job to see what's going on.

I noticed something else. In one repair job it processes all the files the ""System32"" folder. Then it tries to switch to a "".....WOW64......"" folder and it (of course) fails. Because I use XP and not Vista or Windows 7. But nonetheless it processes that same folder (System32\*.*) again. I think you should use Windows System variables that direct WR to the proper folder. (%rootdir% (????)).

I also noticed there's a new version of WR (v1.5.3) out. So. I'll install it and run it. To be continued !!!

Shane:
Yeah if the syswow folder isnt there it just skips it, nothing hurt.

In the same folder as the program is a files folder.
subinacl.exe and psexec.exe are used for that repair, make sure those files are there. :-)

Shane

Willy2:
Yes, I agree it doesn't hurt but then it does process the ""......System32......"" folder twice. And that's where Windows systemvariable could help to speed up WR.

Willy2:
I ran the program (with ""Reset File permissions"" ticked only). And the folders ""Documents & Settings"", ""Program Files"" and ""Windows"" were processed in a record time (every folder only 2 (!!!) seconds). Although these folders are 2.0 Gb, 1.2 Gb and  2.3 Gb in size (on my laptop with Win XP). This suggests that WR fails to process all the subfolders of every main folder on my drive C:. That's why the time for this repair job is so ridiculous low. Did you change something in the program code between two versions ?

I also ran ""Reset Registry permissions"" and I watched what would appear in the CMD.exe window. A number of times it said things like ""Command not recognized"" and ""file not found"". :confused:

Shane:
You never answered this


--- Quote ---In the same folder as the program is a files folder.
subinacl.exe and psexec.exe are used for that repair, make sure those files are there. :-)
--- End quote ---

Those files are used in the repair, see if they are there  :wink:

Shane

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version