I´m unable to run any copy of it through the known starforce workarounds. Emulation-Software is always detected. Don´t know if it recognizes the image (maybe DPM to bad?) or the emulation-tools itself.

Is there any virtual drive software that supports the image format of blindwrite 6 yet?

Cu & n8

It's the emulation tool, so the updated bw5mount.dll for DT4 won't help anyway

The only method for the moment seems to be mounting a full image under Windows Vista Beta 2; so if you have Vista installed give it a try.

but how do i install daemon tools under win vista? the installation of scsi doesn't work so d-tools cant be installed :(

When using DT 4.03 you have to install SPTD driver 1.25 first

well i did and it worked but i still cant play flat out 2, the protection system says "cant validate disk..." i've made an image using blindwrite 6 and autosettings, got the blindwrite 6 image plugin for d-tools, and mounted it with it. so what should i do to get it run?

(Wrong forum, moved; the Protection List subforum is NOT for discussion!)

You try it under Windows Vista Beta 2? If yes then I'm worried :(

@Homer Jay
 

Where did you get the plugin from?

Thx in advance.

@!HaGaR!
Haven't you noticed i linked the plugin in Post#2 ?
Or did i get your question wrong ? :o

@Homer Jay Simpson
A mounted Blindwrite 6 image won't run the game because Blindwrite does only measure a small part of media topology (which is okay for Securom, but not for Starforce DVD *). You have to use an Alcohol Image (an mds file contains full topology).

A Blindwrite 6 image creation/burn may run in opt. USB drives (Starforce claims even the original doesn't run in USB drives LINK, maybe the reason why my EZ-Play copy doesn't run in my drives attached to RAID controller). Starforce topologies will be ignored and not embedded in EZ-Play when burning with BW6, so only the second option of EZ-Play will be used, namely the ATIP/ADIP hiding.

* it's said there are rare exceptions

thx so i will try an alcohol image.

Sorry Zulu, just overlooked that there was a link behind the dll-name :rolleyes:

Will grab it now :)