Hi,
The issue with this title...both in crossover/wine and in the case of a real
Windows installation...is the game executable crashes if the machine it's being
run on has more than 2Gb of ram. In Windows, the only current solution known is to
physically remove the ram modules from your system (which would be hard to do for
the sake of one game, and what if you only had a single 4gb ramstick fitted? 8).
A similar method would also..in theory at least...work in the crossover/wine case,
but who wants to do that every time they want to play Juiced?
In linux, it is possible to use the mem=<value> kernel bootparam to limit the
amount of system memory the kernel uses, however that applies system wide, and
so you'd be rebooting with mem=2000 just to play Juiced, and then rebooting again
to use the 8gb of ram you actually have that makes everything else work properly,
so if you're into rebooting your penguin all the time, this might work for you...
I think the 'preferred' route, would be a hacked version of one of the older
wine-devel 1,1,xx trees.....this would be wine with a patch to limit the amount
of system ram it declares to any/all win32 processes it's running, so it would
only be useful for win32 apps that would cope with such limitation...
At the end of the day, even after doing all this, you're going to discover that
the DVD version has a disc based DRM system, and so this all goes to make this
a rather problematic target and which way you look at it....
One of our Great Ninjas drew my attention to the following WineHQ link;
http://appdb.winehq.org/objectManager.php?sClass=version&iId=3189
That should do the job for Juiced as well -- so if you're ever inclined to make
a 2gb limited wine, now you know what to do -- happy hacking!
Cheers!