View Single Post
  #221 (permalink)  
Old 08-19-2007, 10:39 PM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
 
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by Jeff Kirvin
Quote:
Originally Posted by gguruusa
Quote:
Originally Posted by Jeff Kirvin
Quote:
Originally Posted by luv2chill
The problem is that gx.dll is already in the kitchen by default and there cannot be duplicate files. What you should try to do is delete the gx.dll from your Atomic Cannon OEM, rebuild the dsm and then build the ROM. See if the game works with the existing gx.dll.
I've been trying for some time to get the Astraware Solitaire game to work with the gx.dll module but haven't been able to get it to work. I also can't get the ROM to build if I replace the module in the kitchen with Astraware's .dll file, so I'm stuck installing the cab to my ExtROM after a hard reset. It sucks, but I haven't found a way round it. Some games just can't be OEMed.
Nah, if it works as a seperate install, there is a way (maybe a really long, difficult, and totally purpose defeating way) to make it work as an OEM. Where does it put gx.dll when you install it to Ext Rom?
Same folder as the .exe, in my case ExtROM\Program Files\Astraware\Solitare\

Astraware's gx.dll is about 12k, the stock Windows version created by the kitchen module is about 6k. So there's extra calls in Astraware's version, but for some reason WM won't work right if I replace the stock module with the file. It's been a while since I tried, so I don't remember the exact error.
Hate to say it, but you're going to have to choose between a) using initflashfiles to copy the files around, or b) using a hex editor to change the dll name in the loading program. Option a) works because the current directory is searched for dlls before \windows is. Incompatible revisions just don't gain much from being OEMed unless you go the hex editor route.
__________________
Grammar: The difference between knowing your shit and knowing you're shit.
Reply With Quote