[r2075+]Unable to allocate 217698 bytes

[Major Cooke]

Okay. I downloaded them and tried them, they behave the same way. I used Aeons of Death and Hell Revealed II map 32, still the same problem.

[randi]

And can you confirm that 2071 still works properly? That by just switching between 2071 and 2072 without rebooting or doing anything else, you can make the problem go away and come back?

[Major Cooke]

Yeah, except that I actually got a blue screen for the first time on 2071 while playing in game... I'm beginning to think that it indeed may be my system after all. I'll try it again to see if I get either bluescreen or the allocation failure message, again... It's the first time on 2071 that it's ever happened too, been using it for quite a while.

I didn't catch the file name of what was causing it to stop up, sadly.

*sigh* Whether a reformat would help or not, I'm considering sometime soon. I still have a bunch of junk on my hard drive, related to homework, other games, etc... And it's easy to back everything up on my external HD and wipe it out.

Oh, and would it be of any help for me to say I'm running windows 7 professional?

Edit: Okay, I put up the GZdoom version here, if this interests you at all Randy. I should tell you now that what I experience in the GZdoom software renderer I get the same with Zdoom (I used gzdoom 696 with 2071 as those two were compatible, or so I think) except for that blue screen... I don't really know what to say there, but I only experienced it in regular Zdoom.exe, not GZdoom with software renderer. But anyway, I tweaked some of the display cvars and reduced the usage of things like decals to nothing, and a few other things in the zdoom-name.ini file and it seemed to have helped a bit. I still get that occasional crash though.

[Graf Zahl]

See here:

http://forum.drdteam.org/viewtopic.php?p=43669#p43669


I consider any further investigation of a project that wastes so much memory for bad organization pointless.