System Sentry
Version 2.2

by Easy Desk Software


Information About System Sentry

Program Tabs

About Duplicate DLLs
Before Replacing Files
How To Use System Sentry
Interpreting the Data
System Sentry hangs
What you need to know first
Why do you need System Sentry

Inflate a file
Clean System Folder
Cyclic Redundancy Checker
Extension Association
Files not replaced
Find Dependencies
Redundant DLL Checker
Quick Scan
System Version Checker

Please review this help file carefully, so that you have a full understanding of System Sentry!
You can find more help for System Sentry at our help site.


Inflate a File

This feature of NT System Sentry is used when you wish to expand a compressed file, such as the one used on your Windows CD installation disk. A compressed file normally has an underscore at the end of the file name. Such as Shell32.dl_ .


Duplicate DLLs

Duplicate DLLs and OCXs are just a waste of hard drive space. Windows can only have one version of a DLL or OCX in memory at any one time. When any program looks for a DLL, it first looks in its own folder, then into the Windows Folder and then into Windows\System. When loading a DLL into memory Windows checks the Registry and then looks into the System folder.

After removing the duplicate DLL and OCX files, it is recommended that you use a Registry cleaner and re-register all the System files. Our program Perfect Companion can do this for you automatically. If you skip this step some programs may not work because the DLL or OCX is registered to a location other than the System folder.

Note that files that are in the Common Files folder and in the Windows\System folder generally belong in the Common Files folder only. You can do a search in the Registry to make sure that the reference points only to the Common Files folder. If you find references that point only to a file name you should include the path to the Common Files folder. Which is normally C:\Program Files\Common Files. There is should be no reason why you need two of the same files on your system. If you remove a file from the System folder you should register it in Common Files. You will probably need a program like our utility "Perfect Companion" to clean out the invalid paths in the Registry first. To register the file, from the Windows System Folder use the command line "Regsrv32.exe C:\Program Files\Common File\and_the_rest_of_the_path_and_file_name".

Extension Association

This utility allows you to view all the registered file extension in the Registry. Once the extensions are loaded, it will allow you edit any of the values by simply double clicking on one of the 4 black windows on the utility. You may elect to have System Sentry open the Registry Editor and take you to the Key or Associated main Key for review. You may elect to delete a file extension or main Key. But if you attempt to delete a main Key that other file extensions use, System Sentry will stop you. An example can be the file extension ".z". If you delete the extension .z, which System Sentry will allow you to then attempt to delete the associated main Key which might be "WinZip" System Sentry will stop you because the WinZip Key is still referred to by the ".zip" Key.

This utility is very useful to fix the common problem so many people have written to Easy Desk Software about. When you click on a file and Windows pops up a Window, Cannot Find Program C:\some_deleted_ program.exe; this is the tool to fix it. Simply delete that extension and the main associated main Key. If you moved the application, simply edit the path in the Open With window. Just click on the bottom black window that reads "Open With: " and an edit window will appear.

You can customize the Icons used. If you change the icon association then make sure you use a number value at the end of the statement. So that the entry looks like C:\Windows\Notepad.exe, 0 or what ever number Icon you choose; click on the Icon window.

One word of caution; review and backup any Key before modifying or deleting it if you are unfamiliar with the file extension.


This function is very quick, it is the ideal tool to use to discover dependencies of a running program. Using this function on the Import\Export tab may help you find a DLL that is dropped from memory after an error message is displayed.

Example: you are running program XYZ and you get an error message like "Unknown has caused an error in Kernel32.dll and will be closed", or "WINHLP32 caused an invalid page fault in
module WINHLP32.EXE at 016f:004099b0". If this happens, click on "Tasks" after XYZ program is running, and then, just before the error appears, refresh the list to see if any additional modules have been added and then when the error message appears, refresh the list before closing the error message. Note the modules loaded. Close the error box and refresh the list again and review the list once more.

Clean System Folder

If an error message appears that Edpd has cuased an error in ????.dll, open the noload.ini file and
add the file name=1,not Edpd, to the [Error] section.

You can also have System Sentry display what file is currently been worked on by Edpd; in the [Error] section add Show=1, if the section [Error] does not exist create it. Edpd will enter the path and file name of the file currently being worked on. In the Noload.ini the entry will appear under the [Error] Section as Last= ??????. You will need to open the Noload.ini file after an error occurs but before you click OK. If you are unable to open the file during the error message, close System Sentry down first before clicking OK to the error message.

When using this function, you may have other programs open, but do not use them. It is recommended that after System Sentry has reviewed "files in use", which occurs within the first 30 seconds of the process, you should close as many programs as you can. Do not open any new programs, do not use any other program until System Sentry has finished. Running other programs can cause System Sentry to hang. If System Sentry does hang, let it try to fix itself, do not attempt to close System Sentry or cancel the search for at least 30 seconds. If System Sentry hangs for more then 90 seconds, you will need to shut it down.

16 bit DLLs cannot be loaded and mapped by a 32 bit program, there may be several in the list that should not be archived. If they are required and have been archived you can have System Sentry restore them.

It is also possible that some 32 bit DLLs listed for archiving may be used by programs on your system. These DLLs were not loaded by any binary file that was checked. However, they may be loaded only on demand by a program. This means that they are not loaded in memory when the parent binary file is loaded.

So when archiving files, use some caution, Click on each file to view the manufacturer and purpose of the file. Once archived, DO NOT DELETE them for a while. If after archiving them, you discover that a program requires one or more of the archived files, have System Sentry restore the file(s). This way, System Sentry will learn not to archive the file in the future.

When you double click on a file to remove it from the list of files to be archived, System Sentry remembers not to include it in the archive list in the future.

NOTE: System Sentry will not delete any files in this function. The files will be archived to Windows\Bckupdll\16 bit and Windows\Bckupdll\32 bit folders.

Find Dependencies

The file opened with "Find File to View" is the Dependent file and the files it requires to run are its Dependencies.

This is the tool to use when you get an error message like "Cannot find entry point in dynamic link library Sosandso.dll" or "This program has caused an illegal operation and will be shut down".

To help locate the problem, select "Find File to View" and select the executable file (.exe, .dll, .drv, etc), the program that is causing the problem, and work your way through the list using the function as described below.

This tool will display all the DLL and DRV files involved with the program in question. Two windows will be displayed. The left window displays the direct dependencies shown in capital letters, if that file has dependencies they will be displayed, indented and in lower case letters. The Right windows displays all sub dependencies found in the left window.

Each file in the list is checked for its existence; if it is not in the program folder and not in the Windows folder or Windows sub folders it will display "File not found in path" next to it.

If you click on a file in the right window you can get its dependencies by selecting "Show Sub Dependencies". The file in the right window will now become the dependent file and you will be able to view third and forth level dependencies. If you select "DLL Info" it will check the selected file's date, version as well as its CRC if the file is located in the System folder. In order to check the CRC you need to have saved CRCs using the Cyclic Redundancy Checker already.

If you click a file in the left window, you can get "DLL Info". The Import\Export function will also be available. This function will display (in new windows) the Calls made by the dependent file to the file you have selected. If you want second level sub dependencies (the dependencies' dependency) you will need to select only the lower case files.

On the Import\Export screen, you will see the Calls made to the dependency you have selected. If you click on a Call (Import) it will automatically locate the matching Export in the dependency. Selecting "Verify Calls", will check all the Imports against the available Exports. If a number such as 617, is displayed as an Import, it probably cannot be matched up to an Export. These Imports or Exports, are Calls that are normally only made by the operating system. They are entry point locations references, therefore they cannot be verified using this method. Many number Imports are pointed to a [NONAME] Export.

Note: In order not to clear the windows, use the GO Back function on the Import\Export tab or click only on the Find Dependencies tab. If you select any other tab the windows will automatically clear.


File not found in path

When a file makes a Call (Import) to a DLL it must be either in its own folder or within Windows folder. It can even be in C:\Program Files\Common Files, but it must be registered in the Registry

If a program (C:\Temp\My.exe) wants to make a Call to Soandso.dll and Soandso.dll is in C:\Program Files\More Fun folder then the DLL is listed as File not found within path. If the program My.exe wants to use C:\Program files\More Fun\Soandso.dll it must register the file in the Windows Registry with this path, or place it in the System folder or in its own folder. System Sentry did not search the Registry for a registered path.


What you need to know

System Sentry is an in depth file tool, dealing with the System files (files in the Windows\System folder). These files, if not the correct version for your system will cause General Protection Errors, screen freezes, program hang-ups, programs to perform incorrectly, and other errors. Do not believe that by simply reinstalling Windows or a program that these errors will all disappear.

Please note that if you upgrade or change the version of Windows after installing System Sentry you will need to delete the System Sentry folder, uninstalling it will not remove all the files. If you do not then System Sentry will be using the wrong information about your file system.

There are many reasons why you get errors, so lets review the most common reasons and what you must know before replacing files.

1) You have the wrong Windows version file on your system; perhaps you have Windows 95 installed as your operating system. And in your System folder you have some Windows 98 files, this can play havoc with your system. Here is example: The file Ddeml.dll should be 4.00.0950 but you installed some program that had a newer version 4.10.1998, this is a Windows 98 file and should not be used on your Windows 95 system. Please note that there are many Windows 98 files that will work on a Windows 95 system, but some such as Ddeml.dll should not be used. When this file was installed Windows let it happen because it was a newer version. The cure for this is to try and replace files Versions known to be from a different operating System with the correct version.

2) Shared DLL files not placed in the correct folder can give you a big headache. Example: If you install program "A" and it installs a file named MyDll.dll version 1.0.00 and places it in the Windows\System folder, then you install program "B", version 2.0.00 and program "B" leaves it in its own folder. This file is most likely registered in the Registry as version 2.0.00 from the installation of program "B". Now in a few more days you install program "C" which needs version 2.0.00 of the file MyDll.dll. Program "C" checks to see that the files exist in Windows\System and checks the Registry for the version rather then reading the version number of the file in the system folder. Program "C" sees that the registered version is version 2.0.00 and the file does exist. So it does not overwrite the file in Windows\System. Now every time you use Program "C" you get a GPF, not because program "C" is a poorly written program, but because program "B" did not install the shared DLL the correct way. The cure for this is to place all the newest versions in the System folder to be shared by all programs.

3) Using the example in number 2, suppose program "B" installed MyDll.dll into the system folder as it should have done and program "C" gets installed and it contain version 1.0.00 and does not check to see what the files is in system or what version is registered in the Registry. It overwrites the 2.0.00 version file with 1.0.00 file. You can see what a mess your system can become.

4) System Sentry will not delete any file in the System folder.

5) If you need to undo a file replacement you will find the log file Action.log in the System Sentry folder. It contains the information on what file was deleted from what folder. It contains the information about what files were replaced in the System Folder. You will also find a folder Windows\Bckupdll that contains the file that was in the System folder before replacing it.

6) The file Wsock32.dll, and the file Winsock.dll are files that may be found in many locations, updating or changing this file in the System or Windows folder can cause your Dialup Connections to stop working. Many program require their own version in order to work. Many programs will copy this file to the System folder when activated; overwriting the existing file. Be sure to make backups for these files before replacing them.

Before Replacing Files

Normally a file with a higher version number is the newer version, as is a file with a newer date. We can even understand that a file released with Microsoft Plus 98 is dated 5/1/98 and the file released with Windows 98 is dated 5/11/98 and both have the same version number. Normally a newer version is larger in size than previous version because new code has been added. But all has changed, Microsoft is now releasing new files with earlier version numbers, newer files smaller in size, and newer version with earlier dates. And to confuse you even more, the system that a program determines the file version by, is not even 100% any more because of how the file is compiled.

If you find a file with the same version numbers but the current file has a newer date than this may be due to Aligning the file. Windows 98 and Millenium  will Align a group of system files during its' installation.

A version number is made up from 3 or 4 parts, sometimes only 2. This all depends on how a file is compiled. A version number can be read as follows; version number 4.00.0950.0 is read as 4=major version number; 00=minor version number; 0950=build number; 0=minor build number. Now, when reviewing a version number that is posted as 4.00.950 is the same as 4.00.0950.0. Notice the build number has 4 digits. If you encounter a file where one version is 4.00.1863 and another file is posted as 4.00.950 then remember that the 4.00.1863 is the newer version. Build numbers should be complied as either 2 or 4 digits. But somewhere along the way Microsoft's rules changed.

If an author only enters a build number as 3 digits and compiles it; then the file version is read as 4.00.950 when the author should have compiled the file with a 4 digit number so it can be read as 4.00.0950. So with this in mind lets do the math. If we strip out the periods we have a number 400950 which mathematically is an older version then 4000950, when actually they are the same.

Unfortunately there is no set system in place any more that you can rely on to know which file is the newer file; or which file you should be using. Microsoft releases files that have newer dates but earlier version numbers. Microsoft also releases newer files that are small in size. If we examine the file Mapi32.dll, you will find that the file released in Windows 98 and Millenium is dated 5/11/98 and its' version is 4.00.410.59, The same file released in Window 95 OSR2 is dated 8/24/96 version 4.00.834.839, Microsoft Office 97 is dated 11/17/96 and its version is 4.00.993.3. In IE 5.01 the file is dated 1/12/00 version 1.0.2536.0, this is the newest version as of this writing. Also another file we are aware of is Mapistub.dll, the newer version is 1.0.2536.1 If you have any question about a Microsoft DLL version you should check the Microsoft web site DLL database. (Note: Windows Millenium replaces the older version with the newer version (1.0) file as the installation is nearing the end.) For more information about file versions visit

A few hints:

1) Lets assume you have Windows 98 installed. It comes with the file Riched.dll dated 5/11/98, version 4.00.834.839. Then you install Office 97, the setup program will overwrite Riched.dll with the file dated 11/17/96 version 4.00.993.4 because the zero is not used. The version 4.00.834.839 should have been compiled as 4.00.8340.839 and the Office 97 file should have been compiled as 4.00.0993.4. So when using the System Version Checker and you see a file that has a newer version and the file is more than a couple months older, check out the file at the Microsoft web site before leaving the newer file on your system.

2) You will find that some VXD file dates change, but the version numbers (if any) do not. Their CRC does not change only the date changes. This is because these VXD files are dynamic. This means that the VXD is build on demand, and rebuilt each time the VXD is required. Files like Drwatson.vxd, Msisys.vxd, and HwInfoD.vxd. There is no reason you need to save these files.

3) Before saving files in the System Version Checker, locate any file that has the same version number but different dates. Replace them from the Windows cabinet files and remove them from the list. Example: Lets assume you have Windows 98 Second Edition (A), and you have the file Alt.dll dated 5/11/98 and the System Version Checker states that the file was changed from 4/23/99. But both version numbers are the same; replace the file. Also if you have Windows 98 (not Second Edition) and you have Alt.dll dated 4/23/99 on your system; then replace it with your Windows cabinet file dated 5/11/98. This will save space on your hard drive when System Sentry goes to save the new and changed files.

As more tech questions come in that are not covered in this help file, we will be posting answers to the common questions about System Sentry at our web site. Come to the site for more answers to your questions about System Sentry. At the time of this writing there is no new information on the page.



How To Use

The first step is to get your system as stable as possible, fix as many errors as possible, using whatever software is available to you. Then follow the steps below.

1) Click on the tab System Version Checker and then System File Checker, you will need to have your Windows Cabinet file available. These are the files that Windows installs from, found on your Windows CD-ROM. You will find them in the Win98, Win95, or Win9x folder of your CD-ROM. System Sentry will create a database of what files and what version were included in your original version of Windows.

2) Click on the tab Redundant DLL Checker, and select the feature Find Newer Versions. Copy the newer version files to the System folder, allowing System Sentry to make backups. Now reboot and check your software.

3) Using the Redundant DLL Checker, select Search for Duplicate, and remove from the list any file(s) that you wish to keep. Also remove all the files in the Windows\Bckupdll folder. These are the backup copies of the files you overwrote in the system folder. Delete the rest, making backups and log all actions so any mistake can be corrected. You will find the log, Action.log in the System Sentry folder. Do not delete the files in Windows\Bckupdll folder until you are sure all your programs are working correctly.

4) Now use the Quick Scan and Scan Files. System Sentry will create a list of what files are in the System folder for future use. System Sentry will report to you if any obvious wrong versions are found. If you have Windows 98 it will report to you files that were written for Windows 95, or Windows NT 4.0 that were not included in the your cabinet files. With the Scan complete you should attempt to locate the proper version files. If these files are not available in your Windows cabinet files, so you will need to search your other software CDs or the Internet for newer versions if they are available. Windows 95 version files are 4.00.950 and 4.00.0950, Windows 98 are 4.10.1998, and Windows NT 4.0 files are 4.00. You may even need to do a search on the Internet and your other software's CDs. Replace the ones you can, some you may not be able to find and you will need to use the existing files.

5) The next time you use the Quick Scan System Sentry will tell you if files have been added or deleted and if any are deleted it will give you a chance to replace them. It will also tell you if any files in the System folder are zero byte files, which can be safely deleted as they contain no information. It will also tell you if you have any Read Only files. Let the Quick Scan remove the Read Only attribute, this attribute prevents the file file being overwrite or updated. With the Read Only attribute you may have problems when installing other software or service packs.

6) At this point your System files need to be verified that they are the newest versions you have. So now click on the System Version Checker tab and Check System Files again. System Sentry will now compare all the System files with the original Windows files and tell you which ones need to be updated.

7) If any files are marked as Date Changed you should replace them with the Windows original file if the current file has an older date. Verify the files that need updating and replace them (read the section Before Replacing Files).

8) If you wish to Align your System files, now is the time, after you have completed step 7.

9) Now you need to click on Save These Files. System Sentry will compress a copy of these files into a cabinet file on your hard drive. This way in the future should a file become corrupted or replaced with any older version, System Sentry will be able to replace the file with the last known copy. This is very different from the File Checker in Windows 98. Windows File Checker can only replace a file with the original, and it can only compare the current file to the last file it checked. System Sentry offers you the same option as well as checking a file to the originals. System Sentry allows you to replace a file with either the original or the last saved file.

10) Once all the files have been changed, use the Cyclic Redundancy Check, and Check System Files. With this complete, at any time in the future System Sentry can tell you if a System File has been altered. If it is corrupted or has become infected with a virus.

11) If you boot to more than one operating system you can have System Sentry's System Version Checker not look at the other operating system. Read the Noload.ini file in the System Sentry folder.

You now have peace of mind that you System files are backed up and under a watchful eye.

If you should need to replace a file that you deleted from a program folder, you can view the log file and get a backup file out of the Windows\Windows\Sysbckup or (System32) folder to replace it.


Why do you need System Sentry

If you have Windows 95 as an operating system, then you currently do not have a system file sentry program available to you; one that watches over your System files, such as System Version Checker, provided in Windows 98. In any event, that program only allows you to replace a corrupt or overwritten file with the Windows original file. This means that you may have to reinstall some of your software if Windows replaces a file. Windows 98 makes you start from the beginning every time it replaces a file. When it thinks, and I use the word THINKS, a file is corrupted it replaces it. I have experienced a situation where Windows replaced a perfectly good file I updated long ago with one from the Windows cabinet files, requiring that I reinstall my software.

If you use a program like Go Back, like Windows ME Restore feature, you can almost do the same as System Sentry, except you set everything back, including your Doc files, your Registry and anything new that you created or installed. System Sentry lets you stay up to date while protecting your system files. If someone trashes one or more files, System Sentry lets you replace just the trashed files. It even has a System file protection option that will allow you to have System Sentry check these files at boot up. With System Sentry you can even use an older version of a file and have it protected. This is a great feature for people with CD-ROM writers that require an older version of the file Winaspi32.dll in order for them to work. If a program updates the file, System Sentry will automatically replace the file the next time you bootup. Of course it will ask you first.

If you have Windows 98/ME but not Office 2000 installed, Windows will only Align a few programs to load quicker when it installs. This means that as you add programs, you cannot Align them. Windows 98/ME will also only Align a few DLL files. System Sentry will allow you to Align all your programs and DLLs. Not just once but as many times as you reinstall a program or add programs.

When Windows pops up prompting you for a Program to open a file, but that program has been deleted. You must deal with this prompt every time you click on that type file extension until you format. Or until you go into the Registry and do some editing. Scary, since you are really not sure which Keys need to be changed and what the values should be. To fix this simply use the Extension Association utility and delete the extension. Then click on a file with that association and select the program you wish to open it with. Or you can edit the extension in System Sentry.


Quick Scan

The Quick Scan tab has two utilities. The first is the Protected Files feature. This feature will allow you to have System Sentry watch over a few selected files every time you reboot. You need not put all files in this feature because System Sentry already backed up your System Files and can replace them anytime they are altered. Use this feature for files that are most likely to be replaced because they may have earlier version numbers that some software of yours requires. See the section Why do you need System Sentry.

The second utility on this screen is the Quick Scan. This tool when first used will check the number of files in the System folder and report to you any files that have been added or deleted. It will also scan the System folder for files that are compiled for a Windows operating system other than your version and for wrong file versions not included in your cabinet files.

The Quick Scan will also check for Read Only files, file that contain the Read Only attribute. If a system file has this attribute it cannot be over written causing installation of new software or update file to fail. Some virus scanner install this attribute to protect files from viruses. However most viruses will simply remove the attribute and infect the file anyway.

The Quick Scan also checks for zero byte files. It is normally safe to delete these files as they contain no data. Occasionally a piece of software (shareware) will place a zero byte file in the System folder so it knows when it was installed.

If in the event the Quick Scan stalls or creates an error will scanning, and System Sentry closes before finishing, read the file ~256.tmp. The file is located in the System Sentry folder. It will be deleted when System Sentry finishes scanning. You can bypass this file by reading the Noload.ini file in the System Sentry folder.


Redundant DLL Checker

This utility's usage is explained in the How To Use Section. Read both the How to Use section and the Before Replacing a DLL instructions. Before moving any files to the system folder be sure to read Before Replacing a DLL .

When reviewing Duplicate DLLs read this section.

It is important that you follow the steps carefully. MAKE BACKUPS and use a log, make sure both check boxes at the bottom of the windows are checked. System Sentry will do both for you. You will find a log file of all actions preformed using this feature of System Sentry in the application folder of System Sentry - Action.log. It can be view by selecting the Quick Scan tab and View Log File. Once you have finished replacing, updating your system files and verified that all is well with your system you may delete the Action.log file so that in the future it is easier to review.

If there is a folder or drive that you do not want have System Sentry check for files read the Noload.ini

Cyclic Redundancy Checker

This utility is explained on the interface. Use Check System Files to create and verify all the files in the Windows\System folder. Use Check a file to create and verify a file not in the Windows\System folder such as Windows\Explorer.exe. You can store up to 3000 files in this option. It is recommended that you use this feature just for system based files not stored in the System folder.

The first time you use either option it will collect the CRC of the files selected. The next time you use the option it will verify the CRCs of the selected files.


System Version Checker

The System Version Checker can perform several functions. The first function it must do is to gather the file versions of all the Windows Installation files. To do this you must have you Windows Cabinet file available, they can be found on your Windows CD-ROM. It is suggested that to speed up the process you move them to your hard drive. System Sentry will extract all the files, a cabinet at a time, and get the version numbers from them. Then saves this information for future use so that this process is performed only once. With the Windows version numbers saved you can then click on the Check System Files feature and System Sentry will now find files that contain different version numbers. It will post then as changed with a newer version; date changed - same version, older version - needs updating, and added files. Once you have replaced the desired files you should update using the Restore A File. You may then select the Save These Files feature. System Sentry will then collect all the files that are displayed in the window from the system folder, but no file that is the same as in the Windows cabinet files. Then compress them into a single cabinet file. This normally requires about 32 to 38 Megs of free space on your hard drive that System Sentry is installed on. Now, at any time in the future that you want to check the system files you will be prompted to compare them to the last saved files. If you answer no you will be prompted to compare to Windows' original files.

If you select to compare them to the last saved file list then System Sentry will create only a short list of files that have been checked since the last time you selected Save These Files. If a file has been replaced you will be able to restore it using the System Sentry last saved file or one from the Windows cabinet files. As more added files are installed to your system you will be able to add them to the last saved file list by selecting Check System Files and answering NO when prompted "Check using Last Saved Files List". The System Files will then be compared with the Windows' original files and you will be able to save the new list.

If a file is added after you have used the Saved Files List it will be listed as Added only if it is not a file that is in the Windows Cabinet files. If it is a Windows file and it is not the same version that came with your version or date of Windows then it will be listed as changed. If it is the same version and date then it will not be posted as Added or changed. To find if a DLL was added use the Quick Scan.

Note: System Version Checker will not post files that are not 8.3. These files can be viewed in the Protected Files list for changes. These files cannot be stored in a cabinet file because there is no way of knowing what files can be on your system we cannot create a predetermined list of file names to convert as Windows does when it installs. The second reason is because any DLL that has a long name will most likely not be a vital file. (Such as "Dangerous Creatures.dll".) If you wish you may use the Protected files feature to backup and watch over any of these files you deem as required System files.

Interpreting System Sentry Data

To interpret the information System Sentry will return after files have been added or replaced, use the CRC function to find files that may have changed. Then use the System File Checker and view which files have changed. If both functions report the same files, update the needed file if any file needs to be updated. If only the CRC reports a file changed then that file may have become corrupted and needs replacing. You must remember that the System File Checker will only check for files with the extensions "*.exe;*.Dll;*.ocx;*.vxd;*.sys;*.drv;*.enu". And the CRC will check all files in the System folder.

System Sentry hangs Or missing cab files

If System Sentry seem to hang while trying to extract a file from the Windows cabinet file, locate the folder that they are stored in that System Sentry is using. This is the folder you told System Sentry to use when System Sentry read the cabinet file and saved the information when you first started to use System Sentry. This information is stored in the Noload.ini file.

The cabinet files normally start with "" to what ever number ("Win98_68"). If one number is missing such as "" the program will hang. You need to have all the cabs with the numbers in the folder. It does not matter what the file name is only that the numbers are all there (?????, ?????, ?????, and so on).

If you have Windows 95 you may not have a full set of cabinet file going all the way to Win95_28. You may be using diskettes or an earlier version of Windows 95 that does not have all extra files.

You may also have System Sentry display what error is causing the problem. Restart System Sentry, on the Quick Scan tab double click on the word "Version:" and answer yes. System Sentry will then display all the extraction and CRC windows.

If System Sentry hangs during the "Saving File Information" process you can view the file ~FD636.tmp (located in the System Sentry folder) in notepad. First use the Ctrl-Atl-Delete to shut System Sentry down. If the process completes the ~fd636.tmp file will be deleted.

This process is CPU intensive and can raise the CPU temperature several degrees. An overheated CPU or chassis can cause you machine to crash or reboot. Ensure that your machine has good ventilation.