VOGONS


First post, by theFiddler

User metadata

Hello All,

my system: Dell / Intel 2.6 GHz, Win XP Pro SP1.

Some time ago, I installed VDMSound 2.1.0 beta, in order to support the Aerowinx Precision Simulator 744 (PS1); and everything worked like a charm.

However, yesterday I installed a program "MA80.exe" (shareware math tutor) which has been around a while, and probably began its life under some much earlier Windows than XP is.

When I tried to start this program, it crashed with the message

"MA80 caused an access violation in MA80.exe at 0x00000022. Click on CLOSE to terminate the application Click on CANCEL to debug […]
Show full quote

"MA80 caused an access violation in MA80.exe at 0x00000022.
Click on CLOSE to terminate the application
Click on CANCEL to debug the application
Click on IGNORE to continue, you should save your work in a new file."

I then remembered that I had recently begun to see this same message (giving the same address, too) for another old program I often run (catfish.exe). This one worked normally, though -- the crash occurred only when exiting it. (!)

The DrWatson log indicates that the crashes actually occur in ntvdm.exe, which is (I think) the XP (NT) Virtual Machine for old 16-bit Windows app.s.

Just on a hunch (meaning without any evidence whatsoever...) I then de-installed VDMSound, and in both cases the error went away: the first app now started and ran, and the other one exited normally.

On another hunch I re-installed VDMSound, and sure enough, those two app.s now still ran normally.

But only until I re-booted (only then the VDMSound re-installation "took hold", I guess) -- now I get the error again, can't start the shareware, and can't cleanly exit the other old app.

Incidentally, both programs in question do not use sound, and their context menu does not include the "Run with VDMS" item.

And of course the point is not how to get VDMS to support these app.s, but rather the contrary, how to prevent any interference between VDMS and them (if that's what's happening).

Any ideas?

Thanks in advance for any pointers,
cheers,
Martin

Reply 1 of 2, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

Just a crazy idea - It seems like VDMSound adds a new variable (VDMSPath) to the environment. Could it simply be a case of the memory set aside for environment variables gets too small? If you create a short-cut to your application, you can adjust the size using the Memory tab.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 2 of 2, by vogonsmark

User metadata
Rank Newbie
Rank
Newbie

Hi All,
I have had the same problem.
Has anybody found a solution yet?
Thanks for any help.
Mark