[TippeX]

1. Alcohol at it's setup installs an SCSI driver which is nothing other than the virtual device driver. In many of mine cases deleting it helped getting SR7 games to work. It has nothing to do with the program itself - burning, reading, DPM work just fine.

alcohol installs as a scsi driver and a pnp extender...perhaps what you might be talking about is just letting sptd.sys install... ?

2. That's just bloat talk - you can do either, as I mentioned DT will auto set itself anyways.

Hardly bloat when it comes from their own beta team

3. Write to VSO then if you don't believe me. If it's just an autoplay driver, why it would generate a random device name & even a device category? Please take a closer look. Extract from the guide about EZ-Play (it's a bit outdated but the main idea is the same): http://www.portmac.com/modules.php?n...de&file=EzPlay

it is autoplay, albeit as mentioned its new, the driver renaming (and/or hiding) is just an attempt by them to avoid blacklisting of their components..

4. All of those anti-blacklisters aren't harmful for the system so you can use them safely (Pr0t.St0p + SecuROM v7.26 Loader OR CureROM only).

nah, remember antiblaxx? it was pretty damned harmful, using 2 or more anti blacklisters could counteract the other blacklisters effectiveness.. if one works on your system stick with it.. using more is for sure a recipe for disaster..

Another point for CIV - if using SecuROM v7.26 Loader you must rather point CaesarIV.exe than civexec.exe (of course you can try both).

yep, pointing the anti blacklisting tool at the proper exe and not a launcher does increase the potential for it working...

Concluding, when it comes to SecuROM, you must work your own method. If you need future help, consult this thread at NFOrce:

agreed, each pc is different, so people must find their own solution, which is why i commented on your 'throw everything including the kitchen sink at the program to get it working' post.


and its not an 'art-for-art' reply... its active criticism