It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi,
I tried submitting this to support, but haven't heard back so I figured I'd post it here. Freespace installs with no problems, but when I try to run it, I get an error saying that FreeSpace has detected that you only have 0MB of free memory. I'm running XP x64, so my first thought was some sort of conflict there. Is anyone running FreeSpace on XP x64? Has anyone had a problem like this?
This question / problem has been solved by imswellthanksimage
avatar
TheIDave: Hi,
I tried submitting this to support, but haven't heard back so I figured I'd post it here. Freespace installs with no problems, but when I try to run it, I get an error saying that FreeSpace has detected that you only have 0MB of free memory. I'm running XP x64, so my first thought was some sort of conflict there. Is anyone running FreeSpace on XP x64? Has anyone had a problem like this?

It runs for me in XP64, without any such error message.
I am getting an identical problem with x64 and am in the process of hunting down a solution. Compatability mode does not help.
avatar
TheIDave: Hi,
I tried submitting this to support, but haven't heard back so I figured I'd post it here. Freespace installs with no problems, but when I try to run it, I get an error saying that FreeSpace has detected that you only have 0MB of free memory. I'm running XP x64, so my first thought was some sort of conflict there. Is anyone running FreeSpace on XP x64? Has anyone had a problem like this?

Runs fine in Windows Vista Ultimate SP1 (x64) here.
Have you maybe tried using the Open Source Freespace version? That may (or may not) work.
As an added bonus you get some nice nifty graphic-upgrades :)
edit:
Err, just noticed you were referring to FreeSpace and not FreeSpace 2.
Any chance of you maybe checking your Windows Event log and seeing what else is (potentially) logged in there?
Post edited November 12, 2008 by Aprazeth
I have similar issues on my xp 64bit with some other old games. The weird thing is, it only cropped up whenever I upgraded from 2gb to 4gb ram. I haven't tried Freespace in it yet (I've been playing my games in Linux) but I'll let you know if I can get it running!
I'm pretty sure that setting the compatibility mode to Windows 98 will limit the amount of RAM the program can see to something like 256MB. That is what I used to get Total Annihilation to say I didn't have 0MB of RAM. Just try different compatibility modes (right click the .exe, choose properties, and click the Compatibility tab.)
EDIT: I just saw that supertzar2069 said that compatibility mode doesn't work. Oh well. Can't delete posts. =/
Post edited November 12, 2008 by Nalin
Ok, I experienced the same memory problem in my XP 64bit. I also found a fix!
I added a new boot option in my boot.ini. Here's what I ended up with in the important section (bolded being the new one):
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Windows XP Professional x64 Edition" /NOEXECUTE=OPTIN /FASTDETECT /USEPMTIMER
multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Windows XP Professional x64 Edition - 2GB Limit" /NOEXECUTE=OPTIN /FASTDETECT /USEPMTIMER /BURNMEMORY=2048
The important option here is /BURNMEMORY=2048. This will keep programs from using memory outside the limit. See the MSDN for more details on this.
Now, booting this special option I can play all the great old games that broke when I upgraded to 4GB. It's a heck of a lot better than unplugging memory!
I also had the same problem on my 4GB XP64 machine, but I got it working using Microsoft's Application Compatibility Toolkit to lie to FS.exe about total memory size. I searched around a bit but couldn't find any similar posts, so my apologies for resurrecting an old thread if this is somehow common knowledge already.
Here are the basic steps:
Install the Application Compatibility Toolkit and run Compatibility Administrator
Make a new custom database
Create a new Application Fix and point it at FS.exe
Select None for Compatibility Modes
Select GlobalMemoryStatusTrim in Compatibility Fixes
Pick out the important fields in Matching Information (probably at least PRODUCT_NAME and COMPANY_NAME)
Save the custom database somewhere (freespace.sdb for example)
Open a command prompt and run "sdbinst freespace.sdb" (substitute the path to the database file from the previous step)
If that works, try running Freespace to see how far it gets
The same process should work for other games with this problem, although it's probably easier just to stuff them all in the same custom database instead of making a new .sdb for each game.