Protection Matrix Path of Neo?

[vedderx]

Found this posted on another forum

------
To get this to work with the patch using only the game mounted in Daemon Tools and some registry modifications:

1. Find the 'Scsi Port #' key under HKLM\HARDWARE\DEVICEMAP\SCSI\ that corresponds with Daemon Tools (look at the Driver key for the Daemon tools driver name.) Either change the permissions to Deny everything for your user or group, or change the Driver value here to anything else. (Securom will look up the driver in another part of the registry so it doesn't fool it if you're not using the default Daemon Tools driver name.)

2. Find HKLM\System\MountedDevices and locate the registry key that corresponds with your virtual drive. For example: \DosDevices\G: is mine. Rename this key to anything else such as \DosDevices\G:.backup. Make sure that you do not deny any permissions to MountedDevices, otherwise Securom will indicate that a security module couldn't be activated.

3. Find HKLM\SOFTWARE\D-Tools and change the permissions to Deny everything.

If you still get the message about a security module that couldn't be activated, either you are denying permissions to something in the registry that you shouldn't be, you have another virtual drive program that it is detected whose presence you'll need to hide, or it's complaining about some other active program. For instance, if I have Regmon or NewsLeecher open, Securom complains. Why Securom would blacklist a Newsreader I don't know.

By the way, this worked for the latest FEAR patch as well. Some of these registry changes are reverted when you reboot and need to be reapplied. The change that hides D-Tools will prevent Daemon Tools from loading so make sure it's already running and change it back as necessary.

UPDATE: If, when you installed Alcohol or Daemon Tools, you kept the default names for the drivers, you'll need to uninstall and reinstall the software. This time, choose your own names for those drivers, because Securom is hard-coded to look for the default names. I uninstalled Alcohol and reinstalled it in expert mode (minus the StarWind iScsi service), choosing some random names for the drivers. Then I took the same steps I did for Daemon Tools (this time denying permissions on HKLM/Software/Alcohol Soft instead of HKLM/Software/D-Tools) and it worked.