To post new answers or open threads, you need to log in. The registration is closed now, sorry. If you are not a member, you are welcome to read the posted content without any limitations. If you have any DAEMON Tools related question, contact our support team.
If a main idea using DT is plaing the game witouth disk (because of scratching disk,etc.).... of course I agree.
But I don't think that I'll play it so long.
If another..... it also has a "right for life")
hey niko, i read this thread n followed ur suggestion, though i know you wouldn't like to talk about other software in the forum, but just a quick question if you don't mind, so i just burn the image with RMPS option enabled then just run it with physical drive n it should work?
...then just run it with physical drive n it should work?
At least there is no blacklisting of RMPS emulation, but still such copy can fail
as some drives "like" to start such copies better than others.
Also it's a good idea to use a MDS file verified working, e.g. this one.
Back on topic
@All getting the "conflict with emulation software" error when using YASU - regardless of OS & chipset:
There are no workarounds or special hints to make it work.
You have to wait for an updated version of YASU or DAEMON Tools.
I'm not employed by Disc Soft and my views do not necessarily reflect the ones of the company.
I'm running XP x86 and have a P965 using onboard RAID10 and one Plextor SATA Drive. My workaround to "Conflict with Disc Emulator Software detected" is the following:
First of all, I'am not using yasu or any other anti-blacklisting tool. Just Daemon Tools Lite.
I perform the following two registry operations to avoid blacklisting:
1. HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1 <- deny read or full access for administrators. (It's the Daemon Tools SCSI-Adapter)
2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Cdrom\Enum <- decrease "Count"-Value from 2 to 1.
After those two steps I can play every Securom game with a mounted Backup except ArmA2 and FUEL.
But however I found out that after some reboots, both games start just fine. It's kind of random. I reboot my machine, perform both steps described above and try to start the game. Mostly I get the error, but after ~5 reboots the game starts and will do every time until I reboot again.
I don't know why but, its the same for ArmA2 and FUEL. If I reboot often enough, both games work.
I noticed excactly the same behavior running XP in VMWare and using Daemon Tools.
The only thing that obviously changes every reboot is the random SCSI-Adapter name. At the moment it's AW3SP2X8 and the games are running fine. Maybe those names are somehow blacklisted with a formula.
Ok, so I realise that number is dependant on the number of virtual drives I have. I turned off my MagicISO and PowerISO drives, leaving only 1 - my Daemon Tools virtual drive.
I am still getting the "Conflict with emulation software detected' message.
Just be patient and wait for an updated YASU or the new ◙men.
What about making a sticky out of this, headlining "SecuRom Vx.xxx.xx - Solutions here"
And then list the ways to cheat the different versions.
Maybe there will be less hours wasted for those who are looking for solutions - and a couple of the allmighty "when itґs done" answers can be reduced to a minimum maybe.
I'm running XP x86 and have a P965 using onboard RAID10 and one Plextor SATA Drive. My workaround to "Conflict with Disc Emulator Software detected" is the following:
First of all, I'am not using yasu or any other anti-blacklisting tool. Just Daemon Tools Lite.
I perform the following two registry operations to avoid blacklisting:
1. HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1 <- deny read or full access for administrators. (It's the Daemon Tools SCSI-Adapter)
2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Cdrom\Enum <- decrease "Count"-Value from 2 to 1.
After those two steps I can play every Securom game with a mounted Backup except ArmA2 and FUEL.
But however I found out that after some reboots, both games start just fine. It's kind of random. I reboot my machine, perform both steps described above and try to start the game. Mostly I get the error, but after ~5 reboots the game starts and will do every time until I reboot again.
I don't know why but, its the same for ArmA2 and FUEL. If I reboot often enough, both games work.
I noticed excactly the same behavior running XP in VMWare and using Daemon Tools.
The only thing that obviously changes every reboot is the random SCSI-Adapter name. At the moment it's AW3SP2X8 and the games are running fine. Maybe those names are somehow blacklisted with a formula.
so long,
hackzero
Hello everybody, this is my first message on DT forums :-)
I can give my contribution to the discussion
I followed the standard instructions to get ArmaII to work (using YASU and DT) but it didnt work.
So I tried your suggestions and finally i got ArmaII to start!
Thank you!
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
)
Comment