More help for RegRepair 2000

Home Download Software Our Software Toy Room
Ordering Software Software pricing Suggestions Whats new
Search this site Site Map Links to the WWW Link to us
BACK Tech Support  

Have you tried our glossary?

Clean and Compact Grayed Out
RegRepair wants to compact every reboot
RegRepair does not fix all files
RegRepair reports a corrupted Registry
RegRepair reports lots corrupted fonts
I have Windows ME and RegRepair will not Compact the Registry
How to repair a file with an error that is not in the bootlog

Clean and Compact Grayed Out
RegRepair wants to compact every reboot

If the function is disabled (Grayed Out) then it means that the Compacting was not completed the last time you attempted to Cean and Compact. Or The file C:\Autoexec.wos was not deleted.

This problem normally is cause by the user attempting to Compact more than once without rebooting. The Autoexec.bat file is backed up to Autoexec.wos, then need commands are placed inside the Autoexec.bat file. If you force the Compacting a second time without rebooting the new Autoexec.bat file is backed up, overwriting the last backup.

There are two methods used to install the backup copy. One is the Clean.bat file called in the Autoexec.bat file and the second is the wos file. When Windows sees a .wos file it is suppose to rename the file .bat

To remedy this edit the Autoexec.bat file and make sure there are not entries in the file pertaining to the Cleaning and Compacting. If there are then:

Open C:\Autoexec.bat in Notepad.
In DOS, at the C:\Windows> Prompt type "edit C:\Autoexec.bat"
1) remove all the lines starting at the "@echo Off" just above the statement "If exist C:\Autoexec.wos Copy C:\Autoexec.wos C:\Autoexec.bat"
2) Delete the file C:\Autoexec.wos
3) double Click on the file C:\Clean.bat if it exists.
4) Delete the file C:\Clean.bat

I have Windows ME and RegRepair will not Compact the Registry

Windows Millennium does not load the Autoexec.bat file on bootup. Windows ME users must restart their computer with the startup diskette you made when Windows was first installed. If you do not have one you will need to create one. This can be done by accessing the Add/Remove applet in the Control Panel.

With the startup diskette inserted to the A drive reboot. Once you see the boot menu select start computer without CDROM support. You will be brought to a C prompt. At the C prompt type the word "Autoexec" without the quotes. The Compacting process will start.

RegRepair does not fix all files: After running RegRepair 2000 three times you still have errors in the bootlog, you will find an exception list in your help file you may visit our Failed Files page to view explanations and remedies for these files.

RegRepair reports a corrupted Registry: If during the Cleaning and compacting please visit our How to repair your Registry Page. Read the section about Unable to Clean and Compact.

RegRepair reports a lot corrupted fonts

When RegRepair 2000 is reporting a lot of corrupted TTF files; the fonts probably are not all corrupted. But Windows is having a problem loading something, some other driver, a vxd or drv file. So while trying to load the problem file it steps on all your Fonts. To fix this you must remove all the fonts that Windows is reporting as corrupted, code 0016. The LoadFailed code 0016 is from the Font Manager unable to load the file, possible cause is that you have fonts installed that are not located in the Windows\Font Folder causing a delay. Then fix the other IOS errors that RegRepair is reporting. This will allow Windows now to load the fonts with out a problem. But you must have all the IOS errors fix first. Then reinstall the Fonts the RegRepair has removed. If any of them are truly corrupted Windows will then tell you, and not install them.

back to top

How to repair a file with an error that is not in the bootlog

If you find a file that Windows reports as "Cannot load" or "Cannot find" that RegRepair does not find in the bootlog, open the file C:\Bootlog.txt and add the following line: [000AC02A] LoadFailed = C:\WINDOWS\SMARTDRV.EXE
Replace the C:\WINDOWS\SMARTDRV.EXE with the file reported by Windows.
Then rerun the "Find IOS Error" function.



back to top



Updated August 28, 2003