Problems with VD10...
!HaGar! again bumpinī this thread...
As I posted above I had the problem, that VD10 (trial-version) doesnīt recognize itīs own virtual drive as a virtuall, so it doesnīt allow to mount anything in it.
As john486496 mentioned that the image-engine of VD10 should be able to create working starforce-images, i decided to investigate more time in VD10...
First off, I imaged my Worms 4 Mayhem disc with the VD10 ripping function, but, as already said, I couldnīt mount the image because of the missing vdrive.
So I tried to add another virtual drive. Rebooted. Nothing happened! No new drive were added. Well... Doesnīt really know why... Tried the procedere once more... But again: Nothing. Just the "first" "physical vdrive" stayed alive in my explorer.
Then I swapped the discs in my DVD-Burner because I need to copy a file... And then it happened... My system screwed up and died with a bluescreen!
This was the first bsod I met EVER on this machine!
Well, was pissed and slammed the reset. Windows came up with checkdisk on drive D: (ntfs!)... Okay, let windows run through it... Welcome screen appears, tray proggies cominīup... and BOOM! System blowed again...
Next try... Checkdisk coming up again, traytools loading... BSOD. Different reason this time as the errorcode that something about calling a bad block...
Okay... Tried secure mode... Whouw! Checkdisk again... Welcome-Screen... Wham! System rebooted without any report...
Ok... So what to do... First off: Disconnected "faulty" harddisk. System boots up without checkdisc (sure!), but bsod returns again...
Disconnected DVD-Burner this time... Reboot. System runs without any problems now... Connected my burner again... BSOD returns also...
Ok, to sum the story up: Rebooted again without my burner to let windows stay alive... Deinstalled VD10 and (nearly) all problems disappeared...
Burner works again, all harddrives are fine... But I had to force chkdsc via registry to not check d: at each reboot - donīt know what happened during the first crash at all...
But it seems the buggy VD10-driver (didnīt work properly on my system from the beginning) screwed something up here.
So just use this software on your own risk!
HaGaR out
|