Disk Error-Checking

[Warren]

WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re-boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?

 

[Wesley Vogel]

This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so early in the
boot-sequence, CHKDISK cannot run with the /F option at boot-time, because
it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.

 

[Warren]

This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so early in the
boot-sequence, CHKDISK cannot run with the /F option at boot-time, because
it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:

WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?

.

 

[Wesley Vogel]

Warren,

I honestly do not know how to get the fix. I only know that there is one.
It was posted by a fellow who works for a company that makes defragging
software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In

This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so early
in the boot-sequence, CHKDISK cannot run with the /F option at
boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:

WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?

.

 

[Rocket J. Squirrel]

Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite yet. For
now, the conventional wisdom is to revert back to v.4.5. To do this, users
need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before Zone Alarm
decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there is one.
It was posted by a fellow who works for a company that makes defragging
software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In

This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so early
in the boot-sequence, CHKDISK cannot run with the /F option at
boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

 

[Wesley Vogel]

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so chkdsk.exe
doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All one would have to do is
pull the plug on their modem, for safety. Schedule chkdsk to run, and set
the TrueVector Internet Monitor service to disabled, set Zonealarm not to
load at startup.

Reboot. Set TrueVector Internet Monitor service back to automatic and start
it. Set ZA to load at startup, start it. Plug the modem back in.

Nah. Someone's thought of that. The problem would be that a user would
forget to set things right again so ZA would run again correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In

Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5. To
do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before Zone
Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that makes
defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In

This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F option
at boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

 

[Rocket J. Squirrel]

Thanks for the info. I hope the new owner doesn't spoil what used to be a
beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so chkdsk.exe
doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All one would have to do is
pull the plug on their modem, for safety. Schedule chkdsk to run, and set
the TrueVector Internet Monitor service to disabled, set Zonealarm not to
load at startup.

Reboot. Set TrueVector Internet Monitor service back to automatic and start
it. Set ZA to load at startup, start it. Plug the modem back in.

Nah. Someone's thought of that. The problem would be that a user would
forget to set things right again so ZA would run again correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In

Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5. To
do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before Zone
Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that makes
defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F option
at boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

 

[Guest]

Actually, I tried disabling it at boot, but that didnt'
work. I wonder... is there a way to change the order of
bootup a la win.ini back in the old days of Windows?

-----Original Message-----
Thanks for the info. I hope the new owner doesn't spoil what used to be a
beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so chkdsk.exe
doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All

one would have to do
is

pull the plug on their modem, for safety. Schedule chkdsk to run, and set
the TrueVector Internet Monitor service to disabled, set Zonealarm not to
load at startup.

Reboot. Set TrueVector Internet Monitor service back

to automatic and
start

it. Set ZA to load at startup, start it. Plug the modem back in.

Nah. Someone's thought of that. The problem would be that a user would
forget to set things right again so ZA would run again correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In Rocket J. Squirrel <[email protected]> hunted and pecked:

Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5. To
do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before Zone
Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that makes
defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F option
at boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error- check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

.

 

[Wesley Vogel]

Either enable the XP firewall or don't forget to set the
TrueVector Internet Monitor service back to Automatic.

vsmon.exe is the culprit here.
vsmon.exe = TrueVector Internet Monitor service

Start | Run | Type: services.msc | OK |
Scroll down to and double click: TrueVector Internet Monitor |
General tab | Startup type: Set to disabled | Apply | OK | Close
Services.

Don't forget to set the TrueVector Internet Monitor service back to
Automatic!!!!

Don't forget to set ZA to load at startup!!!!

Configuring Service start up order in WinNT.
http://www.jsiinc.com/suba/tip0000/rh0069.htm

How can I delay services when Windows starts?
http://www.petri.co.il/delay_services_in_windows_2000_xp_2003.htm

How to Delay Loading of Specific Services
http://support.microsoft.com/?kbid=193888

--
Hope this helps. Let us know.
Wes

In

Actually, I tried disabling it at boot, but that didnt'
work. I wonder... is there a way to change the order of
bootup a la win.ini back in the old days of Windows?

-----Original Message-----
Thanks for the info. I hope the new owner doesn't spoil what used to
be a beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so
chkdsk.exe doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All one would have
to do is pull the plug on their modem, for safety. Schedule chkdsk
to run, and set the TrueVector Internet Monitor service to
disabled, set Zonealarm not to load at startup.

Reboot. Set TrueVector Internet Monitor service back to automatic
and start it. Set ZA to load at startup, start it. Plug the modem
back in.

Nah. Someone's thought of that. The problem would be that a user
would forget to set things right again so ZA would run again
correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In Rocket J. Squirrel <[email protected]> hunted and pecked:
Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5.
To do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before
Zone Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that
makes defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F
option at boot-time, because it needs to access the disk
directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error- check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

.

 

[Wesley Vogel]

Dare to dream! ;-)

--
Hope this helps. Let us know.
Wes

In

Thanks for the info. I hope the new owner doesn't spoil what used to
be a beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so
chkdsk.exe doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All one would have
to do is pull the plug on their modem, for safety. Schedule chkdsk
to run, and set the TrueVector Internet Monitor service to disabled,
set Zonealarm not to load at startup.

Reboot. Set TrueVector Internet Monitor service back to automatic
and start it. Set ZA to load at startup, start it. Plug the modem
back in.

Nah. Someone's thought of that. The problem would be that a user
would forget to set things right again so ZA would run again
correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In

Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5. To
do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before
Zone Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that
makes defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F option
at boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error-check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

 

[Wesley Vogel]

Either enable the XP firewall or don't forget to set the
TrueVector Internet Monitor service back to Automatic.

vsmon.exe is the culprit here.
vsmon.exe = TrueVector Internet Monitor service

Start | Run | Type: services.msc | OK |
Scroll down to and double click: TrueVector Internet Monitor |
General tab | Startup type: Set to disabled | Apply | OK | Close
Services.

Don't forget to set the TrueVector Internet Monitor service back to
Automatic!!!!

Don't forget to set ZA to load at startup!!!!

Configuring Service start up order in WinNT.
http://www.jsiinc.com/suba/tip0000/rh0069.htm

How can I delay services when Windows starts?
http://www.petri.co.il/delay_services_in_windows_2000_xp_2003.htm

How to Delay Loading of Specific Services
http://support.microsoft.com/?kbid=193888


--
Hope this helps. Let us know.
Wes

In

Actually, I tried disabling it at boot, but that didnt'
work. I wonder... is there a way to change the order of
bootup a la win.ini back in the old days of Windows?

-----Original Message-----
Thanks for the info. I hope the new owner doesn't spoil what used to
be a beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so
chkdsk.exe doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All one would have
to do is pull the plug on their modem, for safety. Schedule chkdsk
to run, and set the TrueVector Internet Monitor service to
disabled, set Zonealarm not to load at startup.

Reboot. Set TrueVector Internet Monitor service back to automatic
and start it. Set ZA to load at startup, start it. Plug the modem
back in.

Nah. Someone's thought of that. The problem would be that a user
would forget to set things right again so ZA would run again
correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In Rocket J. Squirrel <[email protected]> hunted and pecked:
Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5.
To do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before
Zone Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that
makes defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F
option at boot-time, because it needs to access the disk
directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error- check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

.

 

[elgato]

I was experiencing the same problems and after some investigation I came
across this article which solved my problems.
Ignore the references to Diskeeper and follow the ZA disable process. Works
perefctly.

Boot-Time Defragmentation issues while running ZoneAlarm®

When you update your ZoneAlarm software to the latest build as of June 2004,
you may encounter an issue which, in some cases, prevents Diskeeper from
performing a boot-time defragmentation. The boot-time operation will not run
because it cannot gain direct access to the disk. In these cases, a message
is displayed stating that the boot-time operation cannot run due to
restricted access. (This situation can also occur when simply running the
Windows CHKDSK disk checking utility when your computer boots.)

This issue is due to a conflict between the Diskeeper boot-time mechanism
and ZoneAlarm¹s VSDATANT component. VSDATANT resides on computers running
ZoneAlarm as a hidden, non-PnP (Plug and Play) device. Temporarily disabling
this device allows the Diskeeper boot-time defragmentation (or similar
processes such as a boot-time CHKDSK) to run properly.

The problem can be solved by temporarily disabling the VSDATANT device by
following these steps:

1) Configure ZoneAlarm preferences so that ZoneAlarm does not load at system
startup. This can be done by running the ZoneAlarm Control Center and
clearing the Load at Startup check box. This step is optional, but doing
this prevents ZoneAlarm from unnecessarily alerting you to a system change.
(Since you are performing a boot-time operation, you already are aware of
this system change.) Keep in mind this setting will only be temporary.

2) Set Diskeeper to do a boot-time defragmentation.

3) Start the Computer Management applet by right-clicking My Computer then
selecting Manage.

4) Click Device Manager in the left-hand pane.

5) On the Computer Management menu bar, click View, and ensure that Show
hidden devices is checked.

6) Click the ?+¹ sign beside the Non-Plug and Play Drivers entry in the
right-hand pane of the Computer Management applet to expand these devices.

7) Scroll down to the entry for VSDATANT, right-click it, and select
Disable.

8) Reboot your computer. The Diskeeper boot-time defragmentation operation
will then run.

9) After the boot-time defragmentation is complete and your computer
reboots, return to the Computer Management applet and re-enable the VSDATANT
device.

10) Return to the ZoneAlarm Control Center, re-enable the Load at Startup
option, and reboot the computer.

Your computer has now received the benefit of a boot-time defragmentation,
and your ZoneAlarm security has been re-established.


http://www.executive.com/support/support.asp


elgato-

Actually, I tried disabling it at boot, but that didnt'
work. I wonder... is there a way to change the order of
bootup a la win.ini back in the old days of Windows?

-----Original Message-----
Thanks for the info. I hope the new owner doesn't spoil what used to be a
beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so chkdsk.exe
doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All

one would have to do
is

pull the plug on their modem, for safety. Schedule chkdsk to run, and set
the TrueVector Internet Monitor service to disabled, set Zonealarm not to
load at startup.

Reboot. Set TrueVector Internet Monitor service back

to automatic and
start

it. Set ZA to load at startup, start it. Plug the modem back in.

Nah. Someone's thought of that. The problem would be that a user would
forget to set things right again so ZA would run again correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In Rocket J. Squirrel <[email protected]> hunted and pecked:
Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5. To
do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before Zone
Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that makes
defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F option
at boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error- check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.

.

 

[Wesley Vogel]

Veddy interesting.

--
Hope this helps. Let us know.
Wes

In

I was experiencing the same problems and after some investigation I
came across this article which solved my problems.
Ignore the references to Diskeeper and follow the ZA disable process.
Works perefctly.

Boot-Time Defragmentation issues while running ZoneAlarm®

When you update your ZoneAlarm software to the latest build as of
June 2004, you may encounter an issue which, in some cases, prevents
Diskeeper from performing a boot-time defragmentation. The boot-time
operation will not run because it cannot gain direct access to the
disk. In these cases, a message is displayed stating that the
boot-time operation cannot run due to restricted access. (This
situation can also occur when simply running the Windows CHKDSK disk
checking utility when your computer boots.)

This issue is due to a conflict between the Diskeeper boot-time
mechanism and ZoneAlarm¹s VSDATANT component. VSDATANT resides on
computers running ZoneAlarm as a hidden, non-PnP (Plug and Play)
device. Temporarily disabling this device allows the Diskeeper
boot-time defragmentation (or similar processes such as a boot-time
CHKDSK) to run properly.

The problem can be solved by temporarily disabling the VSDATANT
device by following these steps:

1) Configure ZoneAlarm preferences so that ZoneAlarm does not load at
system startup. This can be done by running the ZoneAlarm Control
Center and clearing the Load at Startup check box. This step is
optional, but doing this prevents ZoneAlarm from unnecessarily
alerting you to a system change. (Since you are performing a
boot-time operation, you already are aware of this system change.)
Keep in mind this setting will only be temporary.

2) Set Diskeeper to do a boot-time defragmentation.

3) Start the Computer Management applet by right-clicking My Computer
then selecting Manage.

4) Click Device Manager in the left-hand pane.

5) On the Computer Management menu bar, click View, and ensure that
Show hidden devices is checked.

6) Click the ?+¹ sign beside the Non-Plug and Play Drivers entry in
the right-hand pane of the Computer Management applet to expand these
devices.

7) Scroll down to the entry for VSDATANT, right-click it, and select
Disable.

8) Reboot your computer. The Diskeeper boot-time defragmentation
operation will then run.

9) After the boot-time defragmentation is complete and your computer
reboots, return to the Computer Management applet and re-enable the
VSDATANT device.

10) Return to the ZoneAlarm Control Center, re-enable the Load at
Startup option, and reboot the computer.

Your computer has now received the benefit of a boot-time
defragmentation, and your ZoneAlarm security has been re-established.


http://www.executive.com/support/support.asp


elgato-

Actually, I tried disabling it at boot, but that didnt'
work. I wonder... is there a way to change the order of
bootup a la win.ini back in the old days of Windows?

-----Original Message-----
Thanks for the info. I hope the new owner doesn't spoil what used to be a
beautiful product.

Rocky

Howdy Rocky,

Somebody bought Zone Labs. And they are probably going to show the
world how they can mess up ZoneAlarm. ;-(

I had it on good authority that there was a fix.

Actually, the problem is that vsmon.exe starts too soon, so chkdsk.exe
doesn't have exclusive use of the volume.

I just now thought of this. (Light bulb here.) All one would
have to do is pull the plug on their modem, for safety. Schedule chkdsk to run, and set
the TrueVector Internet Monitor service to disabled, set Zonealarm not to
load at startup.

Reboot. Set TrueVector Internet Monitor service back to automatic
and start it. Set ZA to load at startup, start it. Plug the modem back in.

Nah. Someone's thought of that. The problem would be that a user would
forget to set things right again so ZA would run again correctly.

Thought I had a deal going there for about five minutes. Oh well.

--
Hope this helps. Let us know.
Wes

In Rocket J. Squirrel <[email protected]> hunted and pecked:
Hi Wesley:

I don't think that Zone Labs has fixed the problems with v.5 quite
yet. For now, the conventional wisdom is to revert back to v.4.5. To
do this, users need to completely uninstall v.5 first.

I use 4.5 myself but, like you, I long for the olden days before Zone
Alarm decided it needed to be security supermarket.

Rocky

Warren,

I honestly do not know how to get the fix. I only know that there
is one. It was posted by a fellow who works for a company that makes
defragging software.

I use ZA 3.7.211.0. I didn't even like ZA 4.0

--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and pecked:
This is in response to your suggestion regarding my
question on the
Microsoft Community Newsgroup Board.

Well, it worked. I disabled ZA from loading at bootup,
but that didn't work.
I checked ZA's website, and apparently I have the most
recent version of the
free version, so I uninstalled it and am in the process
right now of running
WINXP CHKDSK on re-boot. You indicated that ZA has a
*fix* for this. It must
be in the paid version of the software, huh?

THANK YOU VERY MUCH!

Warren

-----Original Message-----
This seems to be a very common problem recently.

Do you have ZoneAlarm 5 ??

[[Since the new version 5.0 of TrueVector accesses the disk so
early in the boot-sequence, CHKDISK cannot run with the /F option
at boot-time, because it needs to access the disk directly.]]

Uninstall ZA5 and install an earlier version.

Or get the ZA update that *fixes* this problem.


--
Hope this helps. Let us know.
Wes

In Warren <[email protected]> hunted and
pecked:
WINXP Pro; I'm able to run the very basic error- check on
the hard drive, but when I click on either one or both
options presented which schedule the check upon re- boot,
the scan does not run whether I restart or shut off and
reboot. Any hints?
.


.