ASP.NET, SQL Server, WPF, C#, VB.NET

On Thu, 01 Sep 2005 11:41:41 GMT, spam@uce.gov (Bob) wrote:  
  
http://support.microsoft.com?kbid=156640 "How to Troubleshoot a Stop 0xC0000218 Error Message "  
  
http://support.microsoft.com?kbid=238359 "Differences Between Manual and Fast Repair in Windows "  
  
http://support.microsoft.com?kbid=822705 "How to troubleshoot registry corruption issues "

Every once in a while after I restart, Win2K runs CHKDSK on its own.  
  
It repairs something called the "Usn Journal". Then when it restarts I  
  
get a BSOD which states  
  
+++  
  
STOP C0000218 Registry File Failure. The Registry cannot load the hive  
  
(file):  
  
SystemRoot\System32\Config\SECURITY  
  
or its log or alternate. It is corrupt, absent or not wittable.  
  
+++  
  
After I power off and back on, the system boots into Win2K without any  
  
problems.  
  
What does this all mean and what could be causing it?  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

Repeated hard drive corruption messages are a reliable sign that a drive  
  
is failing; it's most likely not a software problem. Get and run the  
  
drive manufacturer's bootable drive diagnostic from their website.  
  
Discuss its results with their tech support.  
  
And don't keep using that drive. That will likely propagate the  
  
corruption, eventually making it impossible to easily/cheaply recover  
  
its contents. Install another drive and clone that one while you can.  
  
Bob wrote:

In microsoft.public.win2000.registry Bob wrote:  
  
Here is some information on the $USNjrnl  
  
http://www.microsoft.com/msj/0999/journal/journal.aspx  
  
[ ]  
  
But I concur that imminent drive failure is the most likely cause of  
  
your observed behavior there.  After you have made a complete backup  
  
you should run diagnostics as suggested by Dan.  Possibly any SMART  
  
reporting utility would also show problems with the drive.  
  
Other causes are less likely in my opinion that disk drive problems.  
  
PS  If using NTFS on-disk encrytion, be certain you have exported the  
  
key!

On Thu, 01 Sep 2005 10:49:54 -0400, Jerold Schulman <Jerry@jsiinc.com>  
  
wrote:  
  
What is the "Usn Journal" and what would corrupt it enough to cause  
  
Win2K to schedule CHKDSK?  
  
"The registry files may have been corrupted because of hard disk  
  
corruption"  
  
I know it's HD corruption - there is a message sometimes in Event  
  
Viewer saying that the NTFS partition is corrupt and I need to run  
  
CHKDSK.  
  
The question is what is causing this corruption.  
  
If I do a repair, it's an IPU. Since this problem cures itself, I have  
  
not done that.  
  
I have 3 identical 80GB WD drives which I swap around using Kingwin  
  
KF-23 removable drive bays. I use official ATA133 ribbon cables. I do  
  
not believe it's a hardware problem. And it's not a power failure  
  
problem because the computer is on a UPS.  
  
That leaves:  
  
"The Registry Is Written to at Shutdown"  
  
"If one or two registry hives consistently become corrupted for no  
  
reason, the problem probably occurs at shutdown and is not discovered  
  
until you try to load the registry hive at the next restart. In this  
  
scenario, the registry hive is written to disk when you shut down the  
  
computer, and this process may stop the computer or a component in the  
  
computer before the writing is completed."  
  
If that were the case, then Windows would not load, in which case it  
  
would not get the opportunity to schedule CHKDSK on the next startup.  
  
Whatever is corrupting the registry is happening before shutdown.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

On Thu, 01 Sep 2005 12:08:49 -0400, Dan Seur <click@casta.net> wrote:  
  
If it is a hardware probkem, then why do I keep getting the sa,e kind  
  
of error? What is the "Usm Journal"?  
  
I have run the diagnostics and there is nothing wrong with any of the  
  
drives. Here is the Everest report of SMART:  
  
[ WDC WD800JB-00JJA0 (WD-WCAM91841493) ]  
  
01  Raw Read Error Rate     51   200  200  1  OK: Value is normal  
  
03  Spin Up Time       21   163  162    2850  OK: Value is normal  
  
04  Start/Stop Count    0    100  100         287  OK: Always passing  
  
05  Reallocated Sector Count  140  200  200    0  OK: Value is normal  
  
07  Seek Error Rate    51   200  200   0  OK: Value is normal  
  
09  Power-On Time Count   0    98   98    1481  OK: Always passing  
  
0A  Spin Retry Count    51   100  100   0  OK: Value is normal  
  
0B  Calibration Retry Count  51  100  100   0  OK: Value is normal  
  
0C  Power Cycle Count   0    100  100    266  OK: Always passing  
  
C2  Temperature       0    108  85   35  OK: Always passing  
  
C4  Reallocation Event Count   0   200  200  0  OK: Always passing  
  
C5  Current Pending Sector Count  0  200  200  0  OK: Always passing  
  
C6  Off-Line Uncorrectable Sector Count  0 200 200 0 OK: Always  
  
passing  
  
C7  Ultra ATA CRC Error Rate  0  200  199  2229398  OK: Always passing  
  
C8  Write Error Rate   51   200  200  0  OK: Value is normal  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

On Thu, 01 Sep 2005 14:56:19 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
Change Journal, eh. Then maybe the fact that I am cloning those disks  
  
has something to do with it. Now the question is what is corrupting  
  
this Usn Journal.  
  
I have 3 drives and it happens to all of them. I rule out h/w failure  
  
because I see no evidence for it. Anyway, why would h/w failure result  
  
in all 3 drives showing the Usn Journal corruption? Did all 3 drives  
  
fail at the place on disk where the Usn Jorunal is kept?  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

On Thu, 01 Sep 2005 14:56:19 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
That article is very informative. I think I now know what is going on.  
  
According to that article, the Usn Journal is used to keep track of  
  
changes in the filesystem. The default condition is OFF - some  
  
application has to turn it on.  
  
Therefore I would not even be seeing CHKDSK repairing the Usn Journal  
  
unless some application turned it on. I believe the culprit is Norton  
  
Utilities "Protect", which is a rather lame attempt at creating a  
  
second layer of recycle bin.  
  
Normally when you delete a file it is goes to the Recycle Bin from  
  
which you can recover it. If you hold down the Shift key when you  
  
delete a file it will not go to there.  
  
With Norton Protection, a file which has been deleted but is not in  
  
the recycle bin can nevertheless be recovered. This scheme takes up  
  
disk space so periodically you need to clear the Protect facility  
  
which then renders all files deleted for good.  
  
I have disabled Norton Protect so maybe now my disk won't become  
  
corrupted.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

Wish I'd known that earlier. Hope I didn't waste your time.  
  
Bob wrote:  
  
[SNIP]

In microsoft.public.win2000.registry Bob wrote:  
  
[ ]  
  
3 drives... Well, that's different then.  :)

In microsoft.public.win2000.registry Bob wrote:  
  
With the "3 drives" I would *not* say "failing disk drive", but  
  
might say "unknown software".  :)  
  
Please give us a follow-up on this.  I neither use nor recommend  
  
Symantec products (personal preference).  Have you tried new  
  
searches based on the new information ("Norton Protection")?  
  
Other musings:  
  
You might also try, if available, disabling "delayed write"?  
  
You might try manually stopping one or more Symantec services  
  
before shutdown?

On Fri, 02 Sep 2005 12:43:11 -0400, Dan Seur <click@casta.net> wrote:  
  
Thanks for your comments. Nothing is a waste of time when it comes to  
  
diagnosing computer problems.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

On Fri, 02 Sep 2005 12:57:51 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
Actually I have a 4th drive - an old 30GB WD. The same thing happens  
  
to it.  
  
Time will tell if it was Norton Protection that was causing the  
  
problem.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

On Fri, 02 Sep 2005 13:05:30 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I believe it is Norton Utilities "Unerade Protection". It is the only  
  
thing I can think of that would want to keep track of file revisions,  
  
which is what Usn Journal is for. The fact that Norton Utilities are  
  
from Symantec almost makes it a certainty it is the cause of disk  
  
corruption.  
  
OK, I will be glad to. Let's give it a week and see if I am having any  
  
problems.  
  
That's a nice way of describing crap. I only used it because I wanted  
  
a Registry fixer. Now that I have several, I really don't need Norton  
  
anymore. Good riddance to bad rubbish.  
  
No, because once I learned what the Usn Journal was for, the likely  
  
culprit is Norton Protection.  
  
How would I do that?  
  
I have all of them shut off.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv

On Fri, 02 Sep 2005 13:05:30 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
Apparently it is not Norton Protect. However I did not completely  
  
remove the Norton Utilities so there may still be something going on.  
  
The disk was corrupted again. Everything was fine until I rebooted.  
  
IOW, there was no hint of trouble until I used Start -> Shut Down ->  
  
Restart to reboot. It made it just to the point where it would run  
  
CHKDSK but I got a BSOD instead. That's the point just before where  
  
the keyboard lights flash.  
  
The BSOD read "STOP 9x0...7B INACCESSIBLE BOOT DEVICE"  
  
I tried "FDISK /MBR" using a Win98 boot disk but it did not work. It  
  
was not the MBR that was corrupted.  
  
I mounted the drive as D: and Windows did not fully recognize it. But  
  
it did enough for me to spawn a DVM and run "CHKDSK D: /F /V".  
  
CHKDSK fortunately recognized the NTFS volume on D: and repaired all  
  
sorts of stuff, including "corrupt attribute records" and "invalid  
  
security IDs". There were literally thousands of the latter that  
  
scrolled past the screen.  
  
That fixed the disk and I was able to boot the system using it.  
  
The Norton Utilities uninstall is broken so I am going to have to  
  
remove it by hacking the Registry. The instructions from Symantec warn  
  
that it will take an hour. Dontcha just luv Unka Peter's crap. Maybe  
  
if I reinstall it, the uninstaller will work.  
  
I have no clue what is doing this. Maybe it's time for an IPU.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson

On Fri, 02 Sep 2005 13:05:30 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I am still in the process of ridding my system of all Symantec crap. I  
  
swear I will never again install anything from Symantec. It is pure  
  
crap from Hell.  
  
In the meantime here's what I got when I ran CHKDSK on D:, which is  
  
the corrupted drive.  
  
+++  
  
Checking file system on D:  
  
The type of the file system is NTFS.  
  
Volume label is System Disk.  
  
The attribute of type 0x80 and instance tag 0x0 in file 0x9  
  
has allocated length of 0x40400 instead of 0x40600.  
  
Deleted corrupt attribute list entry  
  
with type code 128 in file 9.  
  
Unable to locate attribute with instance tag 0x0 and segment  
  
reference 0x14000000000014.  The expected attribute type is 0x80.  
  
Deleting corrupt attribute record (128, $SDS)  
  
from file record segment 20.  
  
Deleting orphan file record segment 20.  
  
The security data stream is missing from file 0x9.  
  
The security data stream size 0x0 should not be less than 0x40000.  
  
Repairing the security file record segment.  
  
Deleting an index entry with Id 256 from index $SII of file 9.  
  
Deleting an index entry with Id 257 from index $SII of file 9.  
  
Deleting an index entry with Id 258 from index $SII of file 9.  
  
Deleting an index entry with Id 259 from index $SII of file 9.  
  
Deleting an index entry with Id 260 from index $SII of file 9.  
  
Deleting an index entry with Id 261 from index $SII of file 9.  
  
Deleting an index entry with Id 262 from index $SII of file 9.  
  
Deleting an index entry with Id 263 from index $SII of file 9.  
  
Deleting an index entry with Id 264 from index $SII of file 9.  
  
Deleting an index entry with Id 256 from index $SDH of file 9.  
  
Deleting an index entry with Id 261 from index $SDH of file 9.  
  
Deleting an index entry with Id 264 from index $SDH of file 9.  
  
Deleting an index entry with Id 260 from index $SDH of file 9.  
  
Deleting an index entry with Id 258 from index $SDH of file 9.  
  
Deleting an index entry with Id 263 from index $SDH of file 9.  
  
Deleting an index entry with Id 259 from index $SDH of file 9.  
  
Deleting an index entry with Id 257 from index $SDH of file 9.  
  
Deleting an index entry with Id 262 from index $SDH of file 9.  
  
Replacing invalid security id with default security id for file 11.  
  
Replacing invalid security id with default security id for file 29.  
  
Replacing invalid security id with default security id for file 43.  
  
Replacing invalid security id with default security id for file 88.  
  
Replacing invalid security id with default security id for file 118.  
  
Replacing invalid security id with default security id for file 189.  
  
Replacing invalid security id with default security id for file 194.  
  
Replacing invalid security id with default security id for file 290.  
  
Replacing invalid security id with default security id for file 298.  
  
Replacing invalid security id with default security id for file 301.  
  
Replacing invalid security id with default security id for file 335.  
  
Replacing invalid security id with default security id for file 490.  
  
Replacing invalid security id with default security id for file 759.  
  
Replacing invalid security id with default security id for file 856.  
  
Replacing invalid security id with default security id for file 865.  
  
Replacing invalid security id with default security id for file 958.  
  
Replacing invalid security id with default security id for file 1090.  
  
Replacing invalid security id with default security id for file 1153.  
  
Replacing invalid security id with default security id for file 1528.  
  
Replacing invalid security id with default security id for file 1531.  
  
Replacing invalid security id with default security id for file 1651.  
  
Replacing invalid security id with default security id for file 1653.  
  
Replacing invalid security id with default security id for file 1740.  
  
Replacing invalid security id with default security id for file 1769.  
  
Replacing invalid security id with default security id for file 1839.  
  
Replacing invalid security id with default security id for file 1845.  
  
Replacing invalid security id with default security id for file 2613.  
  
Replacing invalid security id with default security id for file 2655.  
  
Replacing invalid security id with default security id for file 2824.  
  
Replacing invalid security id with default security id for file 3017.  
  
Replacing invalid security id with default security id for file 3204.  
  
Replacing invalid security id with default security id for file 3736.  
  
Replacing invalid security id with default security id for file 3915.  
  
Replacing invalid security id with default security id for file 4045.  
  
Replacing invalid security id with default security id for file 4921.  
  
Replacing invalid security id with default security id for file 5304.  
  
Replacing invalid security id with default security id for file 7914.  
  
Replacing invalid security id with default security id for file 7945.  
  
Replacing invalid security id with default security id for file 8177.  
  
Replacing invalid security id with default security id for file 9171.  
  
Replacing invalid security id with default security id for file 11319.  
  
Replacing invalid security id with default security id for file 11324.  
  
Replacing invalid security id with default security id for file 11326.  
  
Replacing invalid security id with default security id for file 11342.  
  
Replacing invalid security id with default security id for file 11362.  
  
Replacing invalid security id with default security id for file 12210.  
  
Replacing invalid security id with default security id for file 12546.  
  
Replacing invalid security id with default security id for file 14167.  
  
Replacing invalid security id with default security id for file 14171.  
  
Replacing invalid security id with default security id for file 14178.  
  
Replacing invalid security id with default security id for file 14288.  
  
CHKDSK is verifying Usn Journal...  
  
The remaining of an USN page at offset 0x28b0a18c8 in file 0x86bd  
  
should be filled with zeros.  
  
Repairing Usn Journal file record segment.  
  
Usn Journal verification completed.  
  
CHKDSK discovered free space marked as allocated in the  
  
master file table (MFT) bitmap.  
  
CHKDSK discovered free space marked as allocated in the volume bitmap.  
  
Windows has made corrections to the file system.  
  
78148160 KB total disk space.  
  
18564705 KB in 30543 files.  
  
11192 KB in 2379 indexes.  
  
0 KB in bad sectors.  
  
172007 KB in use by the system.  
  
65536 KB occupied by the log file.  
  
59400255 KB available on disk.  
  
512 bytes in each allocation unit.  
  
156296321 total allocation units on disk.  
  
118800511 allocation units available on disk.  
  
+++  
  
Any comments about what this all means?  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson

On Fri, 02 Sep 2005 13:05:30 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I removed everything from the Registry that has to do with Symantec  
  
and Norton Utilities 2002 based on the instructions for manual  
  
uninstall from Symantec.  
  
Now I get the following error:  
  
+++  
  
Application popup: 16 bit Windows Subsystem :  
  
SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers. VDD. Virtual  
  
Device Driver format in the registry is invalid. Choose 'Close' to  
  
terminate the application.  
  
+++  
  
When I closed the application I was trying to install, the system  
  
placed a RunOnce in the Registry. I know because I use RegMon to  
  
report all startup activity.  
  
I rebooted but the problem persists. What do I do to fix this?  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson

On Mon, 05 Sep 2005 15:43:01 GMT, spam@uce.gov (Bob) wrote:  
  
More information. I have backup disks so I ran one and looked at that  
  
part of the Registry. Sure enough there was a key having to do with  
  
Symantec, which I was told to remove by the uninstall instructions.  
  
The missing key is  
  
C:\Progra~1\Symantec\S32EVNT1.DLL  
  
There is no C:\Program Files\Symantec anymore - I deleted it in  
  
accordance with the uninstall instructions.  
  
What a farce this is turning out to be.  
  
Any suggestions on how to fix this.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson

In microsoft.public.win2000.registry Bob wrote:  
  
This seems that we may be back to hardware issues.  Possibly BIOS  
  
settings lost or altered.  New battery?  Review settings.  Flash  
  
the BIOS?  Disks/IDE controller/cables.  Other new hardware  
  
recently installed?  Just guesses at this point...  
  
I don't really know at this point, but suggest investigation by  
  
reducing the number of components.  Possibly remove all but one  
  
disk drive and doing a clean install of the OS.  Then adding  
  
software and/or hardware until the problem manifests itself?

In microsoft.public.win2000.registry Bob wrote:  
  
Well, there is alway "start over clean". <G>  
  
Then at least you can rule out third party software issues at the  
  
outset.  Should problems remain, it seems likely to me that  
  
hardware is at the heart of the problem.

In microsoft.public.win2000.registry Bob wrote:  
  
Not really.  Although "in-place upgrade" / "install over" /repair  
  
installation" do reset a lot to as-installed, I would not say they  
  
are essentially the same when used in a situation such as this.  
  
YMMV  
  
Perhaps.  But a test "clean" install could rule out a number of  
  
things while perhaps also indicating more definitely that software  
  
(of some sort) is indeed the culprit.  YMMV but it could be worth  
  
the time and might also give you some baseline data for the OS on  
  
this particular hardware.  If you go this route also apply (one-by-  
  
one) later SPs and device drivers to match the current config.  
  
Is there (yet) any evidence that is not?  :)  Another thing a clean  
  
installation might prove useful for.  Just thoughts...  Hopefully  
  
you will find the problem one way or another.

On Tue, 06 Sep 2005 13:15:08 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
That's what I am doing. I reinstalled SP4, turned off the write cache  
  
and told Shutdown to turn off the computer instead of rebooting (in  
  
the vague hopes that it will cause a complete flush to disk.)  
  
The problem is intermittant so I have to catch it at random.

On Tue, 06 Sep 2005 13:17:51 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I could do an "In-Place Upgrade" which is essentially the same as  
  
starting over. But I will wait until I am forced to because I want to  
  
find out what is causing this problem.  
  
I should be able to isolate this without having to revert to a  
  
complete reinstall.  
  
There is no evidence that it is hardware.

On Tue, 06 Sep 2005 18:20:30 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
If I have to reinstall Windows, I will install Linux instead. I've  
  
just about had it with this bug-ridden piece of crap.

On Tue, 06 Sep 2005 18:20:30 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I reinstalled a recent version of SP4 and now I can't do an IPU. The  
  
setup disk won't copy certain files with the extension ".icn", likely  
  
because they are not on the setup CD.  
  
I found out that Norton Protection was not the culprit, so I  
  
reinstalled it, because it is useful. The rest is crap.  
  
I also found out that disabling the Write Cache does not help. As  
  
those Microsoft articles pointed out, the write cache problem was  
  
fixed with SP3 and anyway it only applies to SCSI drives - I have IDE  
  
drives.  
  
As mentioned above I reinstalled a recent version of SP4 so maybe  
  
there was something in there that fixed the problem.  
  
I did one other thing that may have solved this problem. I have a spam  
  
filter that fetches the mail on startup. It does this when the system  
  
is still installing itself, which may have caused the corruption. I  
  
turned that option off and now I am not experiencing any corruption  
  
whatsoever. I have rebooted at least 20 times since I made the  
  
changes, and not once did anything happen.  
  
I suppose I could turn the mail fetch back on at startup to see if  
  
that is really the cause, but I need to move on. I have spent far too  
  
much time chasing this problem.

In microsoft.public.win2000.registry Bob wrote:  
  
Good to hear that "bottom line" all is working now as designed and  
  
expected.

In microsoft.public.win2000.registry Bob wrote:  
  
[ ... ]  
  
[ ]  
  
Always best when the WHY is known of course.  :)  
  
[ ]  
  
They should exist on the W2K original installation disc in the  
  
\I386\ directory.  Compressed as *.IC_ files.  I don't know what  
  
your source medium is there though.

On Fri, 09 Sep 2005 01:31:33 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I would have liked to find out what it was that was causing the  
  
problem. I contacted the tech guys at the spam filter and they claim  
  
that running it at startup cannot possibly cause disk corruption. So  
  
maybe it's SP4 that fixed it.  
  
But now I have a different problem, which I suspect is caused by  
  
having installed a recent version of SP4. Now when I do an In-Place  
  
Upgrade, the setup application fusses about not being able to load  
  
*.icm files. Those files are color drivers which apparently are not  
  
available on the distribution disc.  
  
Windows reminds me of an old Three Stooges gag where one of them shuts  
  
the top drawer on a chest of drawers and the bottom drawer flies open  
  
wacking him on the shins.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson

In microsoft.public.win2000.registry Bob wrote:  
  
[ ]  
  
[ ]  
  
Well that is certainly unacceptable and the authors should being  
  
sitting bolt upright and listening (and fixing it)!  
  
How is it started?  Can you start it from batch instead and include  
  
a delay or start it from a later point such as User's Startup  
  
folder perhaps?

On Fri, 09 Sep 2005 08:14:01 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I used the same disc before and never had any problem. I burnt a copy  
  
and it also acts up.  
  
However I managed to get thru the IPU by ignoring those files. I had  
  
to use a CD-RW because my NEC 3540 would not restart. I got a clean  
  
repair so apparently those files are not critical to the IPU.  
  
However I have decided not to use the IPU disc because it has other  
  
problems with RAS and remote procedures that I do not care to sort out  
  
again. I figured out what the problem was before - it had to do with  
  
the fact that I had a modem installed long ago.  
  
Back to the problem at hand. I reimplemented the mail fetch at startup  
  
and sure enough the corruption occurred again. But it only happens  
  
when the program fetches mail that is not spam. The reason is because  
  
it then writes entries to its database. If it's spam it does nothing  
  
until I intervene. So apparently the corruption occurs when the  
  
program is accessing the disk while Win2K is trying to finish its  
  
startup procedure.  
  
The safest practice is to stay clear of Windows during startup - so I  
  
removed the fetch mail at startup because then I do not experience  
  
disk corruption.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson

On Fri, 09 Sep 2005 15:16:48 -0400, Mark V <notvalid@nul.invalid>  
  
wrote:  
  
I wrote them back suggesting that they take a close look at this  
  
matter.  
  
An entry in the user's Startup directory.  
  
I used to do that with Zone Alarm to get it to run. Then I got rid of  
  
ZA when I discovered is was really a virus. I got Kerio Personal  
  
Firewall and have never had any problems since.  
  
That's where it is starting from. Most startups are in the "All Users"  
  
Startup directory, but this one is special in that it will install the  
  
startup in the user's Startup directory if it is not there.  
  
It's easier just to tell it not to fetch during startup. If I want the  
  
mail that badly, I can fetch it manually. When I reboot it's because I  
  
am busy trying to diagnose some problem, and email is the last thing I  
  
want to be pestered with.  
  
--  
  
Greatest Movie Line Ever  
  
http://home.houston.rr.com/rkba/MovieLine.wmv  
  
"Rightful liberty is unobstructed action according to our will within  
  
limits drawn around us by the equal rights of others.  I do not add  
  
'within the limits of the law,' because law is often but the tyrant's  
  
will, and always so when it violates the rights of the individual."  
  
-- Thomas Jefferson