Rise And Fall: CaW - Starforce 3.7

[Morglum007]

Originally Posted by neptun

Maybe.I have nforce4 motherboard ( ASUs A8N-SLI Deluxe ) and in the past the strange controller helped me very much because i didn't need to unplug the drives physically when using image mounted in virtual drive but just disable the ide controller in device manager worked ( my harddisks are sata ).Toca race driver 3 worked for me with this method but Rise and Fall CaW doesn't work.I hope that new daemon tools pro which maybe will be released soon will fix the things by using virtual ide drive.

EDIT: Have you tried both with the nvidia ide drivers and with the standart MS drivers?In the past it did matter if you use the nvidia drivers or the standard ms drivers.

We did, and no way. Still refuses to launch.

For the next question, we discovered long ago, that SF access in SMM mode for a while before launching ( SMM: Super Memory Mode aka BIOS level for most people (even a "higher" level that ring0)[suposelly to be imposible under windows running, but SF does using special micro flags]) and here SF detects HDs, drives, and so on. We also know SF "blacklisted" some RAID controllers long ago, by modifying some windows entries to take data from those "virtual raid". Thats maybe the reason SF detects both ATAPI/ATIP check (when available, not applyable to +R format in theory) under such controllers.
We was known some RAID SiS controllers were "sniffed" but we didnt suppose it did the same with nforce ones, but who knows.... Nforce chipset specs are not public, so, maybe SF found something we didnt yet to get full access as an IDE under RAID (overriding RAID advantages).

Up to day, we are still in the "testing ands supposing phase".
We cant be more accurate with this nforce related issue yet, as stated before.

CdSTeam