[Selectah]

Hey WMCoolMon,

This might be an afterthought or summit, but do you have the source code for the VPMage somewhere? If that's the case, perhaps you could look into the code a bit? I believe the posted VPMage version doesn't terminate properly on a Windows XP system. I haven't checked on Windows 2K, though. On a WinXP system, the VPMage leaves processes in memory, even after terminating the main executable. It's really a quickie to recompile the proggy and post an update, but it'd be a more than welcome one.

Thank you for your anticipated co-operation.

[WMCoolmon]

Hmm, yeah, it's floating around somewhere on here so it shouldn't be too much trouble. I actually can test on XP too, altho debugging will be much more difficult.

[Selectah]

Hey WMCoolMon, I dunno what you've coded it w/, but p'raps it's just a case of exit, instead of atexit or _c_exit or something.

[Selectah]

So, I take it that the VPMage will stay forever in its' perpetual memory hogging state?

[WMCoolmon]

It should be actually leaving the "WinMain" function that causes VPMage to exit.

Last time I spent time on this, I used it to get Polonius working under Windows. I love VPMage's interface dearly (Well...in a platonic sense), but most people seem to find it confusing.

Your best bet is to regularly bug me until I get some time to look over the source, and maybe put it into some kind of releasable form. It's probably using an older version of vplib, and I don't want too many versions of that drifting around.

Maybe I should start myself up a sourceforge project...

Oh and some mod can split this part of the thread and move it to SCP or something similar.

[jr2]

Maybe I should start myself up a sourceforge project...

  

I'm no coder, but I'd love that, 'cause then I'd be able to sit back and d'l new versions that are better and more stable.