Volume Shadow Copy Service - problems with Drive Image XML Application

  • Thread starter Thread starter admiral_victory
  • Start date Start date
A

admiral_victory

I have successfully produced a Drive Image XML Image File on my XP
Pro SP2 desktop but am having a problem with attempting the same on my
XP Pro-SP2 laptop .

If I understand D.I.XML correctly , the difference between this
Imaging software and the similarly named Drive Image is that the XML
software attempts to create Image Files from within Windows whereas
Drive Image does this by moving the PC into an " XP DOS" situation
where Windows is not running.

I presume this is why Drive Image XML requires the Volume Shadow Copy
Service to be running so that any files " in use " in Windows are "
locked ".

The problem now described below would seem to indicate that the Volume
Shadow Copy Service is working on the desktop but not on the laptop.


On the laptop I get the message :-


" ...Could not intiate Windows Volume Shadow Service (VSS) .Make sure
VSSVC.exe is running in Task Manager....."


On both machines vssvc.exe appears under PROCESSES in Task Manager
with CPU showing "00" and MEM USAGE showing 9248k on the desktop and
CPU showing "00" and MEM USAGE showing 5484k on the laptop.


On the desktop and on the laptop , in Admin Tools>Services the vssvc
shows "STARTED" and "Manual"


I have also tried switching the vssvc to "AUTOMATIC" on the laptop but
this does not remove the message above.


Why is there this difference in two apparently similar situations with
Drive Image XML operation here ?


Also how do I "...make sure VSSVC.exe is running ...."


B.N.
 
I have successfully produced a Drive Image XML Image File on my XP
Pro SP2 desktop but am having a problem with attempting the same on my
XP Pro-SP2 laptop .

If I understand D.I.XML correctly , the difference between this
Imaging software and the similarly named Drive Image is that the XML
software attempts to create Image Files from within Windows whereas
Drive Image does this by moving the PC into an " XP DOS" situation
where Windows is not running.
Click to expand...

I don't know the answer to your question, but FYI the last version of
Drive Image, version 7, works from within the windows environment.
The makers, Powerquest, have since been taken over by Symantec - ughhh.
 
I don't know the answer to your question, but FYI the last version of
Drive Image, version 7, works from within the windows environment.
The makers, Powerquest, have since been taken over by Symantec - ughhh.
Click to expand...

Yes thank you I am aware of that .

However Drive Image XML is a completely different App from Drive
Image by Powerquest. It was because I was having other problems with
the Powerquest App that decided to use Drive Image XML!!

B.N.
 
Back
Top