Unable to scan disk

[°¤Hedwig¤°]

Hi I am unable to run scan disk, everytime I try I get the message

Can't open volume for direct access.

I am up to date with virus software and have run several spyware programs,
can anyone tell me how to get it to run?

Thanks

 

[LVTravel]

First, you should be running Check Disk "CHKDSK" from either the command
prompt or the tools menu from Windows Explorer. If you are trying to run it
on a drive that is shared or the boot drive you can't get direct access to
it. The program should give the option of checking the disk on the next
reboot. Select that option and then reboot the machine to have it check the
drive.

 

[°¤Hedwig¤°]

First, you should be running Check Disk "CHKDSK" from either the command
prompt or the tools menu from Windows Explorer. If you are trying to run it
on a drive that is shared or the boot drive you can't get direct access to
it. The program should give the option of checking the disk on the next
reboot. Select that option and then reboot the machine to have it check the
drive.

I have tried to do it from the command prompt and it completes stage one of
three then just stops. The error message I get is what happens when I try to
run on reboot.

 

[Guest]

I feel your pain, I am getting the same darn thing! I look forward to getting an answer as well...gl
jade

 

[Don MI]

Hi I am unable to run scan disk, everytime I try I get the message

Can't open volume for direct access.

I am up to date with virus software and have run several spyware programs,
can anyone tell me how to get it to run?

Thanks

If you have Zone Alarm 5 installed, then your problem is that a Zone Alarm 5
driver is loading and preventing chkdsk and other applications from running.

Option:
Uninstall Zone Alarm 5 and go back to Zone Alarm 4.5 or another firewall.

Option:
Do not run chkdsk until Zone Alarm fixes the problem.

Work around:

Disable the Zone Alarm driver {VSDATANT} that is causing the problem. Then
enable the driver after chkdsk runs. Summary procedure:

Go to Device Manager and from the View menu select show hidden driver.
Right click on VSDATANT and select disable. Reboot.
Chkdsk should now run. Ignore any Zone Alarm error messages that may
occur as Windows XP loads.
Go back to Device Manager and right click on VSDATANT and select enable.
Reboot.

Don

 

[°¤Hedwig¤°]

If you have Zone Alarm 5 installed, then your problem is that a Zone Alarm 5
driver is loading and preventing chkdsk and other applications from running.

Option:
Uninstall Zone Alarm 5 and go back to Zone Alarm 4.5 or another firewall.

Option:
Do not run chkdsk until Zone Alarm fixes the problem.

Work around:

Disable the Zone Alarm driver {VSDATANT} that is causing the problem. Then
enable the driver after chkdsk runs. Summary procedure:

Go to Device Manager and from the View menu select show hidden driver.
Right click on VSDATANT and select disable. Reboot.
Chkdsk should now run. Ignore any Zone Alarm error messages that may
occur as Windows XP loads.
Go back to Device Manager and right click on VSDATANT and select enable.
Reboot.

Don

Thank you It was zone alarm I've gone back to 4.5 and everything is
working fine now.

 

[°¤Hedwig¤°]

I feel your pain, I am getting the same darn thing! I look forward to getting an answer as well...gl
jade

"°¤Hedwig¤°" wrote:

I followed Don's advice and everything is working fine now, hope you get
yours sorted.

 

[Don MI]

Glad you got it sorted.

Don

 

[Guest]

If you have Zone Alarm 5 installed, then your problem is that a Zone Alarm 5
driver is loading and preventing chkdsk and other applications from running.

Option:
Uninstall Zone Alarm 5 and go back to Zone Alarm 4.5 or another firewall.

Option:
Do not run chkdsk until Zone Alarm fixes the problem.

Work around:

Disable the Zone Alarm driver {VSDATANT} that is causing the problem. Then
enable the driver after chkdsk runs. Summary procedure:

Go to Device Manager and from the View menu select show hidden driver.
Right click on VSDATANT and select disable. Reboot.
Chkdsk should now run. Ignore any Zone Alarm error messages that may
occur as Windows XP loads.
Go back to Device Manager and right click on VSDATANT and select enable.
Reboot.

Don

Thank you -- this was a big help to me, even though I was not the original poster. I had the exact same problem, and was running into all kinds of problems, to the point that I ended up having to use Norton GoBack and lost a day's worth of e-mail. I started out by running Norton DiskDoctor, and kept getting the message that it couldn't fix any errors while XP had locked the hard drive. So it advised rebooting, at which point the chkdsk would run and fix the errors. But I too kept getting that same error message during chkdsk (about inability to get direct access.)

I read lots of information on Symantec's website, but none if it helped. And then my computer insisted on running chkdsk every time it rebooted. And then, I decided to try starting in Safe Mode and discovered that that didn't work at all-- it froze up in a DOS screen listing files. I had to power off several times.

Anyway, now that I've finally been able to run chkdsk (I disabled the VSDATANT entry in Device Manager, per your suggestion), I still am find some errors that are not getting fixed, specifically: (from NDD)

"The 'Fix Errors' checkbox was not checked. Corrective actions indicated below were not written to the disk:
-- Deleting index entry INDEX.MAP in index $I30 of file 13945
-- Deleting index entery OBJECTS.MAP in index $I30 of file 13945

Since I didn't get any error messages from chkdsk, I'm wondering if this is a new error that's being created when I boot up each time? Any ideas?

Thanks again for your help! (Somehow or other during this proces I seem to have also fried my USB hub (to which I had three printers connected.)

 

[Don MI]

Thank you -- this was a big help to me, even though I was not the original

poster. I had the exact same problem, and was running into all kinds of
problems, to the point that I ended up having to use Norton GoBack and lost
a day's worth of e-mail. I started out by running Norton DiskDoctor, and
kept getting the message that it couldn't fix any errors while XP had locked
the hard drive. So it advised rebooting, at which point the chkdsk would
run and fix the errors. But I too kept getting that same error message
during chkdsk (about inability to get direct access.)

I read lots of information on Symantec's website, but none if it helped.

And then my computer insisted on running chkdsk every time it rebooted. And
then, I decided to try starting in Safe Mode and discovered that that didn't
work at all-- it froze up in a DOS screen listing files. I had to power off
several times.

Anyway, now that I've finally been able to run chkdsk (I disabled the

VSDATANT entry in Device Manager, per your suggestion), I still am find some
errors that are not getting fixed, specifically: (from NDD)

"The 'Fix Errors' checkbox was not checked. Corrective actions indicated

below were not written to the disk:

-- Deleting index entry INDEX.MAP in index $I30 of file 13945
-- Deleting index entery OBJECTS.MAP in index $I30 of file 13945

Since I didn't get any error messages from chkdsk, I'm wondering if this

is a new error that's being created when I boot up each time? Any ideas?

Thanks again for your help! (Somehow or other during this proces I seem

to have also fried my USB hub (to which I had three printers connected.)

It is not unusual for utilities such as chkdsk and Norton Disk Doctor to
find errors that the other does not. Nothing in the disable of the Zone
Alarm driver should cause the other problem you mention.

I do not use the current version of Norton Disk Doctor. However, the error
message you received indicates that there is some box you need to check in
Norton Disk Doctor to cause errors found to be fixed.

I have another problem with Zone Alarm 5 with a HP 7550 series printer. If
I allow Zone Alarm Security to load during Windows startup, not all of the
HP drivers are loaded. Suggest you try the following:

Right click on the Zone Alarm icon in the taskbar and open the Zone
Alarm Control Center.
In Overview Preferences, clear the box to load Zone Alarm at startup.
Accept any error messages.
In Start, All Program, Zone Alarm right click on Zone Alarm Security and
in Send to select shortcut to desktop.
Reboot.

If your printer hub now works. Leave the configuration as above. After
Windows completes loading, click/double click on the Zone Alarm Security to
start the program. If there is no difference, undo the above. Other than
the above, I have not idea.

Don

 

[Don MI]

Thank you -- this was a big help to me, even though I was not the original

poster. I had the exact same problem, and was running into all kinds of
problems, to the point that I ended up having to use Norton GoBack and lost
a day's worth of e-mail. I started out by running Norton DiskDoctor, and
kept getting the message that it couldn't fix any errors while XP had locked
the hard drive. So it advised rebooting, at which point the chkdsk would
run and fix the errors. But I too kept getting that same error message
during chkdsk (about inability to get direct access.)

I read lots of information on Symantec's website, but none if it helped.

And then my computer insisted on running chkdsk every time it rebooted. And
then, I decided to try starting in Safe Mode and discovered that that didn't
work at all-- it froze up in a DOS screen listing files. I had to power off
several times.

Anyway, now that I've finally been able to run chkdsk (I disabled the

VSDATANT entry in Device Manager, per your suggestion), I still am find some
errors that are not getting fixed, specifically: (from NDD)

"The 'Fix Errors' checkbox was not checked. Corrective actions indicated

below were not written to the disk:

-- Deleting index entry INDEX.MAP in index $I30 of file 13945
-- Deleting index entery OBJECTS.MAP in index $I30 of file 13945

Since I didn't get any error messages from chkdsk, I'm wondering if this

is a new error that's being created when I boot up each time? Any ideas?

Thanks again for your help! (Somehow or other during this proces I seem

to have also fried my USB hub (to which I had three printers connected.)

Addition.

Errors can be classified is several ways such as Critical, Major or Minor.
Most utilities such as chkdsk or Norton Disk Doctor will find the Critical
and Major errors. A utilities ability to find minor errors is a function of
the program criteria and the programmer.
I would expect a program like Norton Disk Doctor to find more minor errors
than a Windows utility like chkdsk. Minor errors are those that do not
effect system performance.

Don

 

[J-Man]

Errors can be classified is several ways such as Critical, Major or Minor.
Most utilities such as chkdsk or Norton Disk Doctor will find the Critical
and Major errors. A utilities ability to find minor errors is a function of
the program criteria and the programmer.
I would expect a program like Norton Disk Doctor to find more minor errors
than a Windows utility like chkdsk. Minor errors are those that do not
effect system performance.

Don

Thanks again for your help. I tried disabling ZoneAlarm to see if that
would help, but it did not. What I've discovered is that the printer will
print if it's directly connected to the USB port on the computer, rather
than through the USB hub. Here's the lowdown:

Epson CX5400 (inkjet)
Epson Photo Stylus 825
HP LaserJet 4L (connected using a parallel-to-USB converter cable)

If the three printers are connected through the USB hub, I always get a "The
document failed to print" error message, even if the document DID print
(although sometimes in only prints partway.) If I print a test page from
Windows XP, it usually goes through, although sometimes the LaserJet cuts
off before the last line or combines lines. All of these problems disappear
if I plug the printers directly in to a USB port. One more thing: the
printers all show as either "ready" or "online" when plugged into the hub.
I'm lost!

 

[Ricky]

Thanks again for your help. I tried disabling ZoneAlarm to see if
that
would help, but it did not. What I've discovered is that the
printer will
print if it's directly connected to the USB port on the computer,
rather
than through the USB hub. Here's the lowdown:

Epson CX5400 (inkjet)
Epson Photo Stylus 825
HP LaserJet 4L (connected using a parallel-to-USB converter cable)

If the three printers are connected through the USB hub, I always
get a "The
document failed to print" error message, even if the document DID
print
(although sometimes in only prints partway.) If I print a test page
from
Windows XP, it usually goes through, although sometimes the LaserJet
cuts
off before the last line or combines lines. All of these problems
disappear
if I plug the printers directly in to a USB port. One more thing:
the
printers all show as either "ready" or "online" when plugged into
the hub.
I'm lost!

Are you using a powered hub?

 

[J-Man]

Are you using a powered hub?

Not A/C powered, but bus-powered.

I think I've figured out the problem. I tried to download a driver for one
of my printers that I haven't yet connected (a fourth inkjet), but somehow
it installed the printer driver and the printer despite its not being
connected. I went through a couple of uninstall/delete processes for that
printer (which was always showing as "READY" even though it was never
connected), and now everything seems OK.

 

[J-Man]

Not A/C powered, but bus-powered.

I think I've figured out the problem. I tried to download a driver for one
of my printers that I haven't yet connected (a fourth inkjet), but somehow
it installed the printer driver and the printer despite its not being
connected. I went through a couple of uninstall/delete processes for that
printer (which was always showing as "READY" even though it was never
connected), and now everything seems OK.

I spoke too soon .... it stopped working again. Seems to be VERY erratic.
I can't figure out why devices that will work when plugged directly into the
USB port won't work when plugged into a hub-- I've tried A/C powered and
bus-powered, and nothing seems to work!

Tonight I tried using one of those hubs that lets you share four USB
printers between two computers and it seems to work (for now.) I also tried
disabling Zone Alarm again to see if that would help. It didn't help with
the old hub(s).