Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
trouble after installing MS critical updates
I applied the 6 latest ones - one at a time, and rebooted after each. I noted after one or more reboots I got this "DOS" message:
Checking file system on C:\
The type of the file system is NTFS. Cannot open volume for direct access. Windows has finished checking the desk".
This appears after the usual boot, Dell logo, etc. and I get in but slows tings down. I didn't didn't do anything to the box.
These are the hotfixes: 831167 (for IE6 SP1) 840374 837001 828741 835732 837009 (cumulative security update for IE6 SP1).
I did a search here but nothing seems to apply here given the proximity to the updates. Hope someone has the silver bullet.
Thanks!
Checking file system on C:\
The type of the file system is NTFS. Cannot open volume for direct access. Windows has finished checking the desk".
This appears after the usual boot, Dell logo, etc. and I get in but slows tings down. I didn't didn't do anything to the box.
These are the hotfixes: 831167 (for IE6 SP1) 840374 837001 828741 835732 837009 (cumulative security update for IE6 SP1).
I did a search here but nothing seems to apply here given the proximity to the updates. Hope someone has the silver bullet.
Thanks!
- Hi Dukie,
I'm sorry to have stepped on your post, it looks like it's being ignored. I've done some searching and found a posting on the Zone Alarm Pro forum and it is a known ZA 5.0 problem and they are supposedly working on a fix. In the meantime you can revert back to 4.5 or just wait it out. (I don't know if you have ZA installed) They had a workaround posted there and that was to use a command prompt to set up chkdsk but I tried it and it didn't work for me, although the guy that posted said it works for him. - Bob,
Thanks for the posts. I fixed it and you were a help. Your mention of Norton reminded me of one of the time-tested axioms in the computer world: to wit "it's ALWAYS Norton :)
The language of the chdsk is very similar to Disk Doctor. Since I bought SystemWorks 2003 I could never tic the "fix problems" because "DiskDoctor cannot fix problems as another program has control of the disk and DiskDoctor must have exclusive...yada yada."
So: 1) I uninstalled SystemWorks seamlessly.
2) Re-booted and same thing occurred. Bummer.
3) Then, I reinstalled SystemWorks. Then after reinstalling the same Chdsk box but it appeared that Chdsk was now allowed to check the disk. This process took exactly 1 hour and 15" mostly because it also checked for free space. Then Norton folded its tent and skulked off. I haven't have any trouble all day. Go figure.
I still don't know what caused it, but I'm not ready to apologize to Microsoft. And I'm never using Disk Doctor again. BTW I'm using ZA.
I love computers!
Mike Hi Mike,
I'm glad to see your problem is resolved and your system is humming along, but it kind of goes against what I thought was causing my problem. As I mentioned above according to the ZA forum there is a known glitch in ZA 5 that causes this problem. I think NSW does use chkdsk to do it's disk doctoring.
rjmat
225 Posts
387
0
Posted June 1st, 2004 21:00
Dukie,
I don't have a solution to your problem, however, in another thread I listed a problem I am having with 840734, and one of the things I notice we have in common is the "Checking file system on C:\ etc.
In an attempt to determine if I incurred any damages from the three BSOD's, I ran the Norton Disk Doctor (chkdsk) portion of Norton System Works and that is the response I got for my 'C' drive. All other drives checked okay. I have no idea what this means for either of us.