Tried this in the OpenGlide forum, no responses. Now I see that it's a general Windows problem not related to OpenGlide, so I'm reposting it here.

I'm trying to get my old copy of Myth: The Fallen Lords running on my Windows 2000 box, using OpenGlide to get its Glide rendering working on my Nvidia card. I have applied the 1.3 patch to Myth, which I believe is the last patch they made.

When I run it, Myth puts up an error message saying that there's not enough memory or swap space. Yet there's gigs of both.

I'm aware that an application showing a "not enough memory" error usually has nothing to do with memory. Most likely, it's because the program made an API call which returned a failure, and they just put up a generic "out of memory" box because they have no way of knowing what caused the function to fail.

Others on this forum have reported Myth running fine (I did a search), so I'm curious if anyone was using Windows 2000 when they did it? Or if anyone has any other tips?

Note: I tried the Microsoft Application Compatibility toolkit 3.0, the one that was release April 2003. That ragtag collection of tools was a bit hard to understand, but I finally got to a screen that gave me a list of about 130 different "shims" that it could wrap an application with. Shims like "win98 version lie" and even shims that would emulate a different way of reporting disk space or heap space. I was sure that one of those would work, but no dice. I even tried checking all 130 shims and test-running Myth, and I got the same error.

Help?