Background:  One day last November I tried to run McAfee Anti-Virus and it
would get an invalid page fault.  After looking for quite a while, I
discovered that the date on my PC was 11/27/2097 instead of 11/27/97.
Changing this "fixed" the problem.  It has not happened since and I have no
idea how this happened ...

More on this problem:

Last Friday I got a tape drive to replace a Zip drive I was using for
backups with Cheyenne Backup 2.0 for Windows 95.  The drive installed fine
with CB2.0 and I was able to switch to the tape instead of the Zip drive
with no problem ... until I tried to run the first full backup.  About half
way through a 1.5 hour backup, it died with the message "CBRUNJOB caused an
invalid page fault in module CSQIC113.DLL at ...".  After looking at this
and running several smaller backups, I narrowed it down to an RBK file
created by the Microsoft Registry Backup utility.  After filtering out this
file, the backup went further but then died again.  I checked the Cheyenne
Web site and discovered that they had seen this problem and it had been
corrected by changing "corrupt dates" on files.  I checked for bad dates
using Norton FileFind and found several files with 11/27/2097 creation
and/or modified dates.  After fixing these files with Borland's Touch, the
backup seemed to be running fine but then died with 2MB of 634MB remaining.
 The file it found this time had no creation or modified date at all.  The
reason why CB2.0 worked before but failed with the tape drive is that it
uses two different DLLs to drive the devices ... one had this problem, but
not the other.  There appears to be no fix on the Web site for this problem.

The files that had the bad date were files that I changed or created trying
to find out what was wrong with my PC that would be causing the invalid
page faults -- the registry backup program, various anti-virus files
(checking for a virus), etc.  There was something else though ... several
shortcut files associated with software I had installed shortly before that
came with my Sound Blaster 64 had a bad date in the 21st century so I
suspect that it might have happened when that stuff was installed.