When you get the Emulator problem, Just Unmount the Star Wars game from drive. I got the same mix up, then I realized the K drive had Star Wars mounted, unmounted and it worked.
Announcement
Collapse
No announcement yet.
CureROM & Star Wars: Empire at War...
Collapse
X
-
Wtf?
OK... i have the same problems... if i don't load the image it tells me to insrt disk, if i mount it in DT 4.0.3 : emulation software detected... and if i try to open the game .exe not the luncher, with CureROM_131 it asks for the original CD... i have no clue on how to solve this... Any Bright Ideeas?
Comment
-
Originally Posted by masteryoda34@Lord_Anubis
Was this with the 1.03 patch? Or before?
Works on both pre-1.03 and with 1.03 (thankfully)If the minimum wasn't acceptable it wouldn't be called the minimum.
Comment
-
Originally Posted by masteryoda34I still can't get mine working even with compatibility set to Windows 2000. I wonder if Home/Pro versions of windows makes a difference. I'm running Home SP2. Are you people who have it working using Home or Pro?
Comment
-
Great News!
Empire at War v1.03 is working with CureRom v2.0 (Beta) and Daemon Tools. I have tried this myself and it works, here's the method.
1. Get the CureRom 2.0 Beta and install it. http://www.curerom.net
2. Go to create a new profile.
3. On the first page use these settings. http://img126.imageshack.us/img126/8991/curerom12mb.jpg
4. And on the second page use these settings.
5. On the shortcut page choose whatever you want.
6. Click Finish.
Now use the shortcut that CureRom created and play the game.
Other: Do NOT check either "Unmount when finished." or the "Force Compatibility".
Comment
Comment