Name: Alan Hutchins Date: June 14, 1999 at 10:50:54 Pacific Subject: RegClean Locks up
Comment:
I have a client that has 6) 95/98 systems on a Novell network that won't run RegClean. It locks up while scanning class identifiers and gives an invalid page fault error. I've downloaded a newer version. Still happens.
Bone & Chip are right I guess although I used it for a couple of years without a problem.Here is a copy of an email I sent to regclean@microsoft.com that came back un-deliverable: Hope you can help me, I have the A version of Widows 95 "4.00.950a and have used RegClean for a long time without a problem until recently.Now it freezes up at "Scanning Type Library Identifiers for errors",always at this same point.I deleted the old copy of RegClean and downloaded it again and it still does the same thing.Any suggestions? Thank you for your help. Gene
Regclean ran okay on my machine up until I installed Explorer 5.0. Now it seems to freeze at "Scanning Type Library Identifiers for errors" too. The Regclean.log shows that it stops at: win32="C:\ProgramFiles\Common.Files\System\AD" HELPDIR="???k"
This folder is not on my machine. The application is searching for a folder that does appear to exist.
Regclean ran okay on my machine up until I installed Explorer 5.0. Now it seems to freeze at "Scanning Type Library Identifiers for errors" too. The Regclean.log shows that it stops at: win32="C:\ProgramFiles\Common.Files\System\AD" HELPDIR="???k"
This folder is not on my machine. The application is searching for a folder that does not appear to exist.
My regclean seems to work okay on Wn98. I'm new at this and while a friend installed the program for me he failed to tell me what I should do with the "undo" files. Any answers?
wow, a whole day of frustration with regclean until finding the solution listed here by JY in the previous message. Running RegClean stopped about 60% through the TypeLib checking for me too. Using "find" with regedit and the search string of HELPDIR I found the key JY mentioned and changed it. Then it ran to about 80%. Another search and found that the next key needed the same fix. all the rest were ok. Thanks again JY !!
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE