Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: yourmumman on August 27, 2008, 09:45:37 am

Title: Freespace 2 can't see my RAM..?!?
Post by: yourmumman on August 27, 2008, 09:45:37 am
Just installed the Open Source version, but the game will not start. I've gone through the Setup just fine, but auto-detecting the settings shows 0 RAM; I get the following message when I try to start the game:

"Freespace has detected that you only have -1MB of free memory.

Freespace requires at least 32MB of memory to run. If you think you have more than -1MB of physical memory, ensure that you aren't running SmartDrive (SMARTDRV.EXE). Any memory allocated to SmartDrive is not usable by applications."

I'm running 64-bit XP, so I know I have 4GB sat in my machine. I'm assuming that this is a standard message as I don't have (or need) SmartDrive.

Any ideas? Trawled the web for answers but seem to be the only one posting this problem...rubbish :(
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: karajorma on August 27, 2008, 10:00:38 am
It's a known issue with 3.6.9. If I remember correctly it's fixed in 3.6.10.

Anything fairly modern from the recent builds forum should fix this. A lot of people seem to suggest using this build (http://www.hard-light.net/forums/index.php/topic,54952.0.html)
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: Jeff Vader on August 27, 2008, 10:15:12 am
Wasn't this more of a retail issue? I'm not claiming or denying anything, but it is possible that... yourmumman, has still run the retail executables, which are notorious for not liking too much RAM.
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: karajorma on August 27, 2008, 10:42:04 am
IIRC 3.6.9 also suffered from it. Either way you are right that this could be a retail user though. Which means I've just pushed him into some very deep water without checking if he can swim. :p

@yourmumman : Did you install the game using the online installer from this forum or do you have the CDs? The solution is the same either way (FS2_Open 3.6.10) but the amount of help you need will depend on what you have at the moment.
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: yourmumman on August 27, 2008, 01:42:12 pm
I picked up the retail version, ran into this error and then found out about the Open Source version (d'oh!).

Downloaded from the main site and ran the installer (version FS2_Open 3.6.9); both executables gave the same error. That's where I'm at now :)

Is this URL for the .10 build? http://www.freespacefaq.com/Misc-Downloads/Builds/StandaloneFixes-1.7z

Thanks for your help so far, guys :)
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: Jeff Vader on August 27, 2008, 01:46:05 pm
Strange. I could've sworn that someone with an awful lot of memory got his FreeSpace working with 3.6.9. Oh well.

Yes. That's the build, packed into a .7z archive. Extract the contents to your \freespace2\ folder, then select fs2_open_3_6_10.exe as your build from the Launcher.
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: karajorma on August 27, 2008, 02:04:08 pm
Strange. I could've sworn that someone with an awful lot of memory got his FreeSpace working with 3.6.9. Oh well.

8GB will work.

It's all to do with how the memory is allocated. Taylor explained it once and I grasped enough of it to understand the effects if not the cause.
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: Jeff Vader on August 27, 2008, 02:13:19 pm
Ah. Right, there was that math thingy involved.
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: karajorma on August 27, 2008, 02:18:15 pm
http://www.hard-light.net/forums/index.php/topic,54735.msg1107002.html#msg1107002

Actually it's simpler than I remembered :)
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: yourmumman on August 28, 2008, 09:58:07 am
Thanks for the help, guys, I'm up and running now :)

Forgotton how excellent  this game is!
Title: Re: Freespace 2 can't see my RAM..?!?
Post by: phreak on September 03, 2008, 09:59:56 pm
There is a way to fix this, I can look at it tomorrow afternoon.