-------------------------------------------------
	
	w i n d o w s  9 8 / 9 8 s e
	
	u s i n g   s y s t e m   f i l e   c h e c k e r 

	-------------------------------------------------
	
	1.  Using the system file checker (SFC) improperly can cause severe
		problems as there is a "flaw" in the way the program works.  SFC
		cannot tell the difference between a corrupt file and one that is
		slightly different but not corrupt.  For example, upgrading to
		IE5.5 will install several files that show up as corrupt in SFC but
		are not--they are merely changed files.  If you blindly trust SFC,
		you will replace valid files with the original files and problems
		may ensue.  You also cannot overwhelm SFC with software
		installations and system updates and then expect it to be a useful
		tool.  Only apply one update at a time and then see what SFC shows
		as outlined below. 

	2.  Check your files with SFC before installing software or system
		updates.

	    a.  If no files are identified as being changed, proceed with the
			installation or update.

	   	b.  If files are identified as changed but your PC has been
			performing flawlessly, update the verification information and
			then proceed with the installation or update.

		c.  If files are identified as changed and your PC has not been
			performing well, do not update SFC and don't make an
			installation or update.  Instead troubleshoot the problem and
			at a minimum that will probably entail:

        (1) Searching at Deja.com for similar problems:
			http://www.deja.com/usenet/

        (2) Searching the MS Knowledge Base for symptoms of your problem or
			searching on any error message you might be getting:
			http://support.microsoft.com/support/search/c.asp

        (3) Using the MS DLL Help Database to identify where a particular
			version of a .dll file may have come from:
		http://support.microsoft.com/servicedesks/fileversion/dllinfo.asp

        (4) Posting your problem to the
		microsoft.public.win98.gen_discussion newsgroup and asking for
			help.

	If your problem is either resolved or appears to be unrelated to the
	"corrupt" files, update SFC's verification information and proceed with
	the update/installation.  If you must replace files, be sure to read
	the first article in para 4, below.

	3.  Once your update/installation is complete, run SFC to see if files
		have been identified as being changed.  If there are none, continue
		with your updates/installations.  If files have been identified, do
		not make additional changes until such time that you have
		ascertained that the machine is running properly.  Once that
		occurs, update the verification information and proceed with your
		updates.

	4.  Here are some articles about SFC:

	System File Checker Tool Extracts Incorrect File Versions 
	http://support.microsoft.com/support/kb/articles/q192/8/32.asp

	How the System File Checker Baseline Is Determined 
	http://support.microsoft.com/support/kb/articles/q188/1/86.asp

	Description of the System File Checker Tool
	http://support.microsoft.com/support/kb/articles/q185/8/36.asp

	System File Checker Detects Changes to Office Files
	http://support.microsoft.com/support/kb/articles/q189/2/92.asp

	Default.sfc File Is Not Restored By System File Checker Tool 
	http://support.microsoft.com/support/kb/articles/q187/5/43.asp

	System File Checker Detects Drwatson.vxd Has Been Deleted
	http://support.microsoft.com/support/kb/articles/q177/9/82.asp

	System File Checker Identified that the Following...
	http://support.microsoft.com/support/kb/articles/q264/8/65.asp

	System File Checker May Not Replace Older Files
	http://support.microsoft.com/support/kb/articles/q182/7/25.asp