Right now, I can think of three potential categories of problems:
- I'm doing something boneheaded - like eating up memory in ways that I shouldn't be.
- You're doing something that seems benign, but is actually causing a problem - like running something else at the same time, which consumes memory that would otherwise be available.
- I'm overestimating the capabilities of your hardware - the perennial problem of PC development - you build on a fast machine, but need to support a range of consumer configurations.
The last one seems the most likely to me, but all I'm doing is drawing lines, so I'm a little stunned to run into machine limitations. I'm running on an nVidia 6200, and I've tested on an older nVidia card (4000 series, maybe?) and on a Mac (with maybe an ATI card?). I've had friends and other contestants test it, and at first, about 50% of people saw a blank screen (or occasionally fragments of color), which I took a guess, and found a solution to. So, now the only machine that's having problems (that I know about) is yours.
With the CustomConfigs thing we just tried, I wanted to use as small of a window as possible, guessing that OpenGL was running out of memory handling an 800x600 screen. You say you ran the 256x192 bat file, which uses around 1/10 the video memory of the 800x600 version.
I've got one other idea of a potential problem spot - I'm drawing fat antialiased lines, which use up a certain amount of memory. I could have an option to scale that back to drawing single-pixel lines. It won't look as pretty, but it may finally run. I'll post and or reply when that's in.
Other than that, I'm running out of ideas. Maybe you can help me out here. What version of windows are you running? What graphics card do you have in the machine? What kind of CPU is it? Do you know if the video drivers have been updated at all recently?
It may be that we can track this one down soon. If so, we both are happy. It may be that there's a solution that's going to take me more time to find than makes sense while the competition clock is running - in which case, I'll apologize and defer chasing down the solution until next week. Or, it may be that my game just isn't going to run on your machine. I'm not excited about that possibility, but it's something to consider.
And yeah, when you get a chance, do close as much as possible, including the stuff in the system tray next to the clock - random helper programs sometimes gobble up system resources in a surprising way.