Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - GHenry

Pages: [1]
1
Let me say that I appreciate you kind cooperation. As for the planned updates, I myself will be away for some time to Asia and will not be using your program for quite a while.

However, I should like to add one comment: in my view it would be desirable to have the option of undoing ALL changes your tool may have made, although I'm quite aware that that may be too big a challenge. Anyway, as far as I'm concerned, I always make a general backup before doing any major checkup or repair work.

Thanks again!
G.

2
I've been working with Windows computers for over 30 years (and with CP/M before that) and have come to consider Windows not as an operating system but as the biggest virus in the history of computers. So I'm quite accustomed to inexplicable things happening.

I'd be interested to be informed about updates of your program. What I personally would like to emphasize is the possibility of undoing at any time any changes your program may have made.

Thanks for your cooperation.

Kind regards
G.

3
Hi Shane,

thanks for your answer (although I'm not expert enough to understand the details of the 'mum files' procedure - which doesn't matter).

Enclosed you'll find the requested Spooler entry (from the restored registry).

Kind regards
G.

4
I am using TWEAKING version 3.1.4.

5


> My program doesn't remove any system file
Yes, that's what I assumed. The problem(s) may have as a result of a preceding crash of my rollback software and an incorrect restore of the original system. And no, I did not take a screenshot.

It is also possible that, when later checking for the missing REGEDIT file, I restored the mssing version in
c:\windows\ from my system backup. I agree that it cannot have been restored solely because I recovered the original registry.

The fact remains, however, that among numerous other things TWEAKING reported that the PRINTSPOOLER would be repaired, and that afterwards the printer did not work anymore. In addition, in its pre-scan TWEAKING reported 11 files in c:\windows\servicing\packages as corrupt. When, however, I compared those files both with my backup and with the original Windows files, they were identical in date of creation and length. For test purposes I copied the original files back to c:\windows\servicing\packages and ran the TWEAKING pre-scan once more, and again the files were marked by TWEAKING as corrupt.

Unfortunately, after two days of repair work, I'sorry to say that I don't have the time to rerun the whole procedure (although I do understand your wish to find out what happened). Moreover, TWEAKING reported (and tried to correct) a load of errors, so there wasn't just one error screen I could have sent you. During the first run I seem to remember that TWEAKING repaired a number of parse point and environment faults, which did not re-appear in the following pre-scan (after restoration of the registry).

I am enclosing the result file which may give you a more precise idea of what happened.

Kind regards
G


6
Before running tweaking.com, c:\windows DID contain regedit.exe. When printing didn't work either after the repair (PRINTSPOOLER repair), I restored the original registry, and bang - regedit.exe was there again, and the printer worked fine.

So I'm not sure whether I should trust tweaking.com...

7
I clicked those Messages away each time; now I do not know whether the repairs were successful. In a subsequent search it turned out that c:\windows, c:\windows\sysWOW64 and two instances in c:\windows\winsxs did not contain that file.

What should I do?
G. Henry

Pages: [1]