Tweet
Operating System: Windows XP Pro
Burning Software: Blindwrite 5, Nero 6, CloneCD 4, Alcohol 120% 1.4.7
Anti-virus Software: NOD32 v2
DAEMON Tools Version: 3.41
Today I burnt a blindwrite image from the new game I bought (Broken Sword 3) so I could mount it from hd instead of the CD like I always do and I encountered the locked drive issue when unmounting. I know what's wrong and I was trying to post this at the Common Problems and Solutions Forum but I didn't have access to reply to that thread so here it goes.
The game is locked with SecuROM 4.85.07.0015 and apparently Daemon Tools can not mount it properly from a 1:1 blindwrite image cause probably this new wrapper has the stealth drive blacklisted as I have been able to mount images of previous 4.85 builds. When I run the game it does nothing at all. Checking the task manager I saw the process was a zombie eating 47-50% of cpu resources. I killed the process and when I tried to unmount the image the drive reported as locked which is quite reasonable since the process was killed and did not send an unlock command. I believe similar cases are what cause the reported "drive locked" issue (those that are not a corruption of the .inf file).
The workaround to this is quite easy. You just set the number of devices to disable and then back to what you were using. The stealth drive resets and you can mount a new image.
I was also wondering how the blacklisting of the drive is done. It's not the drive identifier because I have it custom for that reason. I am guessing it's using the driver name or inquiry data. Is it not possible to implement an engine that randomizes that data upon installation (and via the settings for whenever else it's needed) so that each installation would be unique and the drive non-detectable? :twisted:
PS I was also wondering if I could join the beta team :wink: And sorry for being a bit off topic.
Burning Software: Blindwrite 5, Nero 6, CloneCD 4, Alcohol 120% 1.4.7
Anti-virus Software: NOD32 v2
DAEMON Tools Version: 3.41
Today I burnt a blindwrite image from the new game I bought (Broken Sword 3) so I could mount it from hd instead of the CD like I always do and I encountered the locked drive issue when unmounting. I know what's wrong and I was trying to post this at the Common Problems and Solutions Forum but I didn't have access to reply to that thread so here it goes.
The game is locked with SecuROM 4.85.07.0015 and apparently Daemon Tools can not mount it properly from a 1:1 blindwrite image cause probably this new wrapper has the stealth drive blacklisted as I have been able to mount images of previous 4.85 builds. When I run the game it does nothing at all. Checking the task manager I saw the process was a zombie eating 47-50% of cpu resources. I killed the process and when I tried to unmount the image the drive reported as locked which is quite reasonable since the process was killed and did not send an unlock command. I believe similar cases are what cause the reported "drive locked" issue (those that are not a corruption of the .inf file).
The workaround to this is quite easy. You just set the number of devices to disable and then back to what you were using. The stealth drive resets and you can mount a new image.
I was also wondering how the blacklisting of the drive is done. It's not the drive identifier because I have it custom for that reason. I am guessing it's using the driver name or inquiry data. Is it not possible to implement an engine that randomizes that data upon installation (and via the settings for whenever else it's needed) so that each installation would be unique and the drive non-detectable? :twisted:
PS I was also wondering if I could join the beta team :wink: And sorry for being a bit off topic.
Comment