Home of the Windows Registry experts

More help for System Sentry

Home Download Software Our Software Toy Room
Ordering Software Software pricing Suggestions Tech Support
Search this site Site Map News Letter

Have you tried our glossary?

CONTENT:
About Aligning
Clean System Folder
Dynamic Link Errors
File backups
Files not to copy
Files are not replaced or are changed back to older version
Program hangs while reading cabinet files
Program hangs while checking CRCs
Quick Scanning
After Formatting or installing a new versions of Windows
Redundant DLL Checker


About Aligning

Before Aligning the System files you should complete the System Version Checker's "Save These Files". This way you will have a complete backup of all the system files before altering them. A backup copy of each file is placed in a subfolder named backup. When system files are aligned,  the folder Windows\System\backup is created, unless you elected to check the box "Do not make backup copies".

After Aligning your programs or system files you MUST defrag your hard drives. If not, you may find that your computer responds slowly.

If you use encryption for your browser some files should not be Aligned. Aligning corrupts the encryption and will disable your ability to visit secure sites and your mail server in Outlook. Version 1.3 of System Sentry is already programmed not to Align the following files which cover the standard Internet Explorer and the 128 bit Explorer: Psbase.dll, Pstores.exe, Sch128c.dll, Advpack.dll, Enhsig.dll, W95inf32.dll, W95inf16.dll, Dssbase.dll, Rsabase.dll, and Rsaenh.dll. If you use a different browser please make a copy of the required files before Aligning the System Folder. Any of these files that have been Aligned will have the date that you Aligned the system files.

If you did not reboot before Aligning the system files, System Sentry will not be able to restore files in use after Aligning. If you find that any of these files have been Aligned, reboot, do not start Outlook, use the System Version Checker and restore the file from the Saved Files or from the Windows original files.

If you find any of the above files were Aligned, after replacing them place them in the Protected files list so that the next time you Align System Files you will not need to worry about them again.

System Sentry backups this file before Aligning, then Aligns all the System files. After the Aligning process it restores these files automatically. The report will show that they have been Aligned, but if you check the actual files you will see that they were not Aligned.


Clean System Folder

If you have a virus scanner that is always on, you need to disable it. If you have Norton Anti Virus, you need to disable the NAVAP.vxd file. If you have anti virus that uses a VXD, it will be loaded during bootup and cannot be disable by simply closing daown the program. It must be removed from the loading Keys in the Registry, and then reboot. Example, Norton uses Navap.vxd loaded at the Key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\NAVAP.

On Windows 9x and ME, you can disable the Vxd using Msconfig or export the Key, delete the Key and then reboot. When you want to restore Norton, double click on your export file to reinstall the Key.

If you get errors or System Sentry crashes and closes you can find the problem by using the Show=1 command in the Noload.ini. You will need to have version 2.1.02 or higher installed. Review your help file on how to setup the Show=1 command.

Edpd.exe is a file loader, it loads files into memory and then reads the memory to see what files are in use, so that System Sentry can remove the in use files from the list of files it will archive. When Show=1, Edpd will record the file it is currently loading to the Last= line in the Noload.ini file. If you get a message box like Mpr.dll is the wrong version, or Mpr.dll is missing. Close System Sentry down, then click ok to the error message, open noload.ini and you will see the file that is calling Mpr.dll.

Using the Show=1 command will slow System Sentry down a slight bit, but you will be able to diagnose many different prolbems that may arise.

Once System Sentry is scanning folders and you get a message that "Edpd as cause an error in module Kernel32.dll" or any other file that is located in the System or System32 folder, do not add the module name=1 to the Noload section. The problem is not in the system module as in the error message "Edpd as cause an error in module Kernel32.dll". The villain will be listed on the "last=" line under the [Error] section in the Nolad.ini file.

What is System Sentry doing? System Sentry is loading all binary files into memory and examines its Import Table. System Sentry removes any dll that the file as listed from the archive list. When a DLL is loaded into memory it will attemp the load any other DLL that it needs, so if a file is missing from your system you may get an error message- ?????.dll is not correctly registered", "Unable to load ?????", or some other message. System Sentry is not going to display any error message about a file during the operating. These messages are coming from the current file loaded by the Edpd.exe program..

However, many programs use a delay load of some DLLs; this means that some DLLs that a program uses will not be in the Import Table. Before archiving any file, you should click on the file, and a brief description will be displayed on System Sentry's interface. Remove any file that you think may be required. Should a file get archived that you need simple restore the needed files.

I have a Cannon fax, printer, scanner and I archived several files that the printer required. When I rebooted and tried the print some features would not work. I started System Sentry and selected Restore a file and looked for any Cannon file in the list, and restore it, the printer then worked

The purpose of this tool is design to HELP find unused DLLs left over from uninstalling software. Do not delete the archived files until you are 100% sure all programs are functioning as they should. Remember not all program dependencies can be found in its Import Table.


Program hangs while checking CRCs

Version 2.0 or lower:
If System Sentry should hang while checking the CRCs, locate the file CSU.exe in the System Sentry folder. Then open Notepad or any other text editor. Add the following into Notepad: Csu.exe C:\Windows\System\*.* (change the path if your Windows folder is not C:\Windows). Save the file as Checksum.bat to the System Sentry folder. Double click on it (Checksum.bat). You will then be able to see what is going on.

Version 2.1 or higher:
Please email us to report any problem, The csu.exe file is not use in these versions.


After Formatting or installing a new version of Windows

If you wish to start  saving the original Windows files again, or you just formatted or upgraded Windows, then read this section.

You need to delete the files Ofdata.dat, Lodata.dat, Lodat.cab, Checksum.dat, Checksum.sfc, CRC.dat,CRC.sfc, Action.log, and System.log. This will allow you to set System Sentry up as if you just installed it.

It is recommended that you use System Sentry before installing any other software, and run System Sentry after installation of each piece of software. This will ensure that you have saved the newer versions and if some piece of software overwrites one, you can make immediate repairs. More on this here.


Quick Scanning

When you use the Quick Scan please be sure you understand that the program is only telling you that the files in the list were complied for another version of Windows and MAY NOT be compatible with your version. You should use the link in the System Sentry help file to the Microsoft DLL database and check to see if it is the correct version for your operating system.

Also, you should use the search cabinet file feature in the  Integrator so that files like COMMDLG.DLL are stored as COMMDLG.NEW. You can extract them using QikFix, WinSafe or RegRepair 2000 to an empty folder, rename them and install them. Be sure that you check the properties after renaming the files and before installing them.


Files are not replaced or are changed back to older version

This section pertains to Windows ME, XP, 2000, 2003. These operating systems have a built in System File Checker that watches only certain System files. If a file the SFC is watching gets replace Windows will replace the file automatically, in a second or two.

If System Sentry replaces a file and you check it again after rebooting and it seems to not have changed, the file is being controlled by Windows SFC.

For Windows ME, you will need to reboot into Windows in Safe Mode, then have System Sentry replace the file.

For Windows XP, 2000, 2003, you can do one of two things. The easiest walk around is to rename the folder I386 that is on your hard drive, move it to a different location. Then replace the file. Windows will now tell you about the file being replaced and you can tell Windows to except the new version as the replacement. The second choice is to edit the Registry and disable SFC.


Files not to copy

When using the "Find Newer Version" feature in System Sentry; there are some files that should not be copied.

1) Files in the AOL sub folders that are from a different operating system. AOL uses sub folders named Net\98se and Net\OS etc. Do not copy any file from a different OS to your system. Example. if you have Windows 98 SE then only copy files from the 98se folder. do not copy any files from the OS folder.

2) Files that are in the Program Files\Common Files\Microsoft Shared files  should not be deleted or copied to the System folder. They do not belong in the System folder, these files are registered to the Shared sub folders, or at least should be.


Program hangs while reading cabinet files

If System Sentry hangs while trying to read your cabinet files:

1) Verify the path you told System Sentry your files are located. Open RegEdit and go to the Key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup and check the path at the Value "SourcePath".

2) Verify that all the cabinet files are at this location. You must have cab #1 and every number till the last cab. (Assuming you have WinSE, the last cab is #69) You need Precopy1.cab to Win98_69.cab. It does not matter what the name is, Net(#).cab, Base(#).cab, Driver(#).cab, or Win98_(#).cab, so long as all the #'s are there, 1 through 69.

3) Go to the folder you have System Sentry installed to. The default is C:\Program Files\Easy Desk Utilities\System Sentry. Then right click the file Extract.exe (Extract) and select "properties". Then select the Program tab and verify that the "Close on Exit" box is checked.

If no errors have been found after completing steps 1 to 3, then ensure that you have a copy of Extract in the Windows\Command folder and proceed to step 4.

4) Create a folder Windows\Temp\Cabs

5) Open a MS DOS window. Type - Extract /E C:\Windows\Options\Install\Precopy1.cab /L C:\Windows\Temp\Cabs

Replace C:\Windows\Options\Install\Precopy1.cab with your Cabinet file path and name of the file it is hanging up on. When you press the enter button you will then be able to see what the problem is.


Redundant DLL Checker

The most common question that I am asked is "I deleted a file using the Redundant DLL Checker, how do I restore the file?".

Well this is very simple, since the Redundant DLL Checker will only display and delete duplicate files that are in the System folder. Your backup is in the System folder. Example: You deleted C:\Program Files\MyProgram\MyDll.dll, you will find MyDll.dll in C:\Windows\System. This is your backup. You will also find the file Action.log in the System Sentry folder that will tell you exactly what files were deleted and from where, if you have selected the option "Log actions".

When you click on a file you will see the file information in the lower right hand corner. Red means do not copy to the System Folder as the file is an older version, black means they are the same version and green means copy it to the System Folder as it is a newer version.

The Redundant DLL Checker should not be used until you have used the System Version Checker and you are sure Windows is working OK. At this point you may delete the file in C:\Windows\Bckupdll folder if you wish. You should not delete any files in your Windows\Options\Cabs or I386 folder, or what ever folder you have your Windows installion files in.


File backups

System Sentry will also have a backup file available so long as the "Make backups before overwriting" box is check on the "Redundant DLL Checker" screen.

How System Sentry makes backups is very simple. When you use the System Version Checker, every file that you select to copy to the System folder, System Sentry will make a backup. System Sentry will create a folder in the Windows folder named Bckupdll. It will then check to see if the file exists here, if not, it will copy the file that is currently in the System Folder to the Bckupdll folder. So long as that file exists in the Bckupdll folder, System Sentry will not overwrite the file in Bckupdll folder.

Example: the file Mydall.dll in the system folder is version 1.00. You want to copy the file Mydll.dll version 2.00 from C:\Myfolder to C:\Windows\System. System Sentry will backup version 1.00. Now you find Mydll.dll version 3.00 in the C:\MyProgram folder and you copy it to the System Folder. System Sentry will not save version 2.00. In order to save version 2.00 you will need to delete version 1.00 from the Bckupdll folder.


Dynamic Link Errors

To help locate a Dynamic Link Error or a missing Import and other DLL error messges using System Sentry to locate them, here are a few senarios to help you find them.

1) If you receive a message during bootup like Cannot find entry point in dynamic link library in Shlwapi.dll, or "Invalid call to .....", or "Missing Dynamic Link ........."; you probaly do not know what file is calling what dll. So using MSConfig remove all startup programs and reboot. If the error is still there then you know it is not a startup program but a DLL or vxd that is being loaded during bootup. You need to view MSInfo and start from there. If you have Win XP or 2000 turn off all services that you do not need to boot up and see if the error disappears when you reboot.

In either case once you stop the error you can now restart each service or startup program one at a time and reboot, till the error returns. Now read the REPAIR.

2) If you receive a message while starting a program or during running a program, you need to file the exe file that you started the program with. If you used a shortcut, simply do a Properties on the shortcut. Now read REPAIR.

REPAIR: Once you have located the the program or service that is causing the problem you can start System Sentry and and use the "Find Dependenies" function. Locate the startup program that is causing the problem. Suppose it is "C:\WINDOWS\scanregw.exe /autorun", you would load Scanregw.exe and if any of the Dependence files are missing, System Sentry will tell you. If no files are missing select the immediate depends and check its Imports and Exports. Then select the sub dependencies and check there imports and exports. Keep going till each file has no dependencies except the Kernel32.

Updated November 07, 2004