[Fox McFox]

When I try to play it, I get this pop-up error message... "Not Enough RAM - FreeSpace has detected that you only have 0MB of free memory.  FreeSpace requires at least 32 MB of memory to run.  If you think you have more than 0MB of physical memory, ensure that you aren't running SmartDrive (SMARTDRV.EXE).  Any memory allocated to SmartDrive is not usable by applications."

I have 8gigs of DDR2 memory and am running windows XP 64bit version. 

Anyone have any idea what is wrong?

[Jeff Vader]

Does this happen with retail FreeSpace 2? Try FreeSpace_Open.

[Fox McFox]

lemme try freespace open

[Jeff Vader]

You do that. Use Turey's FSO Installer (link in my signature) to get started. Point it at your \freespace2\ folder so that it won't unnecessarily download the retail files. Use it to download at least any FSO files and maybe the MediaVPs. After it has downloaded everything, install OpenAL (link also in my signature). Then, use Launcher.exe, found in your \freespace2\ folder.

[Fox McFox]

thanx...i got it to work

[Jeff Vader]

Glad to hear.

[colecampbell666]

FS2 is pretty much guaranteed to start showing it's age on the monster systems of today.

[taylor]

I have 8gigs of DDR2 memory and am running windows XP 64bit version. 

The retail code supported a max of 2gig of RAM before it started to wrap around.  So with 8gigs the code actually sees it as a negative value.  Even FSO only supports 4gig properly, but it can't be negative, which is why it is able to work for you.  Just so you know.

[haloboy100]

Let this be your

[jr2]

I thought memory was divided up into "pages" that apps requested?  So why doesn't it just see if the max is > than what it needs and SU about the rest??

[taylor]

So why doesn't it just see if the max is > than what it needs and SU about the rest??

That's what it does, but how it looks at the max value is the problem.  It comes down to the max value getting stored in an integer that it uses to evaluate the max value.  For retail its a signed integer, which has a max value of 2gig and a min value of -2gig.  For FSO this was changed to an unsigned value, which has a max of 4gig and a min of 0 (ie, no negative).  Any value going over the max will wrap around to the min side.  So, 8gig will look to the game as -2gig in retail, which is well below the required 20meg.  And even in current versions of FSO, if you had something like 4.001gig, the game would only see 1meg of memory and give you the same message.  But with FSO you are safe so long as any multiple of 4 avoids that magic 20meg whole (ie, 4gig or below and 4.04gig or above are perfectly safe; with the same problem affecting 8gig/12gig/16gig/etc.).

[jr2]

Sheesh.    Is that simple to change, or no?  IDK, it seems it would be relatively simple.  Which probably means it would be really hard.