This thread is becoming a mess.
Let's get a bit rational, please.
I gave those links to Lancelot, expecting he would EXPLAIN
the matter, instead of further confusing it:http://www.boot-land...?...=1662&st=59http://www.boot-land...?...1580&st=216http://www.911cd.net...o...21242&st=34
Since noone appears to actually follow links and READ them in their context
, let alone actually READing the VDK.EXE readme.txt, let's start from scratch.
Re-read psc's post above:
They do not fail!
They only are prohibited by the OS to free a driver service which is in use anywhere.
It should be in the responsibility of the Ghost 14 script's author to find, why a service remains in use after the script has been processed.
VDK commands are "telescopic" so:
INSTALL will install the driver.
START will INSTALL and START driver.
OPEN will INSTALL and START driver and OPEN given image.
CLOSE will close (unmount) the given image.
STOP will CLOSE all images and STOP the driver.
REMOVE will CLOSE all images and STOP the driver and REMOVE (uninstall) itIdeally
one could use ONLY the OPEN command (that will also INSTALL and START the driver) and the REMOVE command (that will also CLOSE the image and STOP the driver)BUT
- if anything "hooks" in ANY way the driver, the REMOVE command will fail.
- if anything "hooks" in ANY way the the mounted volume or the connected virtual \\.\PHYSICALDRIVEn, the STOP command will fail.
- if anything "hooks" in ANY way the the mounted volume the CLOSE command will fail.
- if EITHER the REMOVE or STOP or CLOSE commands failed, for ANY reason, NO subsequent INSTALL or START will work anymore
SO, in order to be "safe and "foolproof" (at least theoretically) :
- the INSTALL, START or OPEN commands should ONLY be executed at the beginning of a "session"
- the STOP and REMOVE commands should ONLY be executed at the end of a "session"
- ANY of the above commands and all the "intermediate" ones, LIMITED to CLOSE and OPEN, should ALWAYS be executed ONLY after having checked the status of the driver using VDK.EXE DRIVER command and parsing it's output.
I had guessed that the above was already solved at the time of this:http://www.boot-land...?...1580&st=216
I hope that this info helps.