Problem with virtual memory

[justanotherfan]

Cool. Do you still have the original files undeleted? The broken settings may be of interest to TNM.

[Servalan]

That's where it gets weird again.

Just for the heck of it I moved the three files back again and they made no difference whatsoever. After backing up the originals I moved them into TNM's system folder...and when I started TNM, DX started. So I opened the .ini files and there are no references to TNM in them whatsoever - they look more like a DX.ini. Yet moving them fixed the game. So I'm not sure if you could learn anything from them or not.

[justanotherfan]

That's the kind of thing Yardbomb could help with.

Still, if you HAVE a spare goat, it could be worth the sacrifice. Just paint "VMM" on the side before setting it on fire. This may also please the llamas.

[Servalan]

Well, I'll be passing through Goat City in a while (I didn't mention that all my saved games were stuffed after I moved them back, so I had to start from scratch). I'll set fire to someone on the way.

[Hassat Hunter]

and when I started TNM, DX started.

That's what happens when using the TNM.exe in System, who doesn't have all the extra's to the shortcut to launch TNM (which basically is the DX launcher with added parameters), so it launches DX (you aren't the first one who, after installing TNM is fooled by that one ). Try it again; now with the proper TNM launcher. Does it crash or not?

[Servalan]

Yeah, the problem appears to have been solved by removing three "stray" TNM files from my DX system folder. The DX-launching thing was caused by my experimenting with those files to see if I could replicate the problem (which I couldn't). All seems to be well now.