CONFIRMED - Race Driver 2 workaround guide.

[The Gauge]

I've no idea why this only works over a network install.

I've tried creating a shared folder on the local computer and mounting the image through Network Neighbourhood just as I did from the remote computer. It still doesn't work.

I can only assume it's something to do with the file transport system for Microsoft Networking. Something subtle must get lost during the transfer that still remains when the image is mounted locally. It's most bizarre, though. I'd understand if you could install locally and just mount remotely to boot the game, but it doesn't work unless you INSTALL remotely as well.

I'd be most interested to know why, though.

[Morglum007]

Why SF only works with tricks like that is because its special drivers. SF hides and modifies the Windows IDE accesing in order to control the whole operation. Every way that hides GENUINE IDE conected to optical drives ( where the alcohol image is) will result in an image launching. This is why alcohol needs not to have IDE conected to a drive in order to work, or why by networking it works. (SF compares "spin" test on every drive in order to "know" if a drive is virtual or not, so no optical must be present in order to fool that test)

good luck!

[The Gauge]

Originally Posted by Morglum007

Why SF only works with tricks like that is because its special drivers. SF hides and modifies the Windows IDE accesing in order to control the whole operation. Every way that hides GENUINE IDE conected to optical drives ( where the alcohol image is) will result in an image launching. This is why alcohol needs not to have IDE conected to a drive in order to work, or why by networking it works. (SF compares "spin" test on every drive in order to "know" if a drive is virtual or not, so no optical must be present in order to fool that test)

good luck!

Hmmm... could you explain that last bit again, please? Are you saying that the SF protection modifies ALL your IDE drivers so, aside from controlling the access method on optical drives, it also knows if the "image" that's being run is coming off one of the other IDE devices, i.e. your harddrives? Presumably then, the SF protection runs, sees no optical drives, sees that it's not being accessed from one of the other IDE devices (harddrive), and proceeds as there are no other IDE devices to check? Hence the network image working?

This is very interesting stuff.

[t.foster73]

For all you electronics guys out there a question. Is it safe to wire an on/off switch into the 12v input of the IDE drive? Would this fool the Starforce drivers? (The drive will not appear in windows without 12 power).

[RincewindTheWiz]

Yes, it would fool the drivers, NO, I wouldn't recommend this. IDE devices are not hot pluggable, you might destroy the drives by doing it too much.

[KingPickle]

For all you electronics guys out there a question. Is it safe to wire an on/off switch into the 12v input of the IDE drive? Would this fool the Starforce drivers? (The drive will not appear in windows without 12 power).

You can test that out quickly. Just leave the side of your case open with the 12v unpluged. When you boot to windows, try puttin that molex back on the drive

[The Gauge]

Originally Posted by KingPickle

You can test that out quickly. Just leave the side of your case open with the 12v unpluged. When you boot to windows, try puttin that molex back on the drive

Heh... I'd seriously avoid doing something like this unless you're prepared to power-down the PC before you flick the switch.