(Work with Assembler is going forward slowly but surely.)
Being plagued by another problem.
The "skeleton" program, as I call it, which serves to test functionality
of swapping the tsr to disk or EMS, is running fine in the VDM.
It installs itself properly in the background, hotkeys are working.
When called a 2nd time (from the same batch file) it show
the "Already installed." message as it should, and when called
with the "-u" parameter it successfully deinstalls itself.
The actual version I have produced meanwhile does show a different
behaviour. It will install alright, hotkeys working, windows are popping
up, but at the moment it is called a 2nd time from the VDM prompt,
regardless whether with or without parameter, it completely stalls
(crashes)
the VDM. Funny thing being that I didn't touch anything in the area
of the program which deals with module initialization, parameter scan,
or trying to unload. Sometimes, but not always, I will get a NT error
message "...VDM encountered an unvalid/illegal command..." together
with the frozen DOS box.
I'm really stuck here, since when the "skeleton" was running alright
I didn't test _every_ single step over there in the VDM but relied on
it being okay as long as it ran under pure DOS.
As always I will be obliged for receiving hints of any kind... Thanks.
Martin
in...@airkreuzer.com
Regards,
--
Andrew Denton [TPX]
Senior Software Engineer
Q-Systems (International) Ltd
"I want to move to Theory...Everything works in Theory"
Those of us with [TPX] after our names are not TurboPower employees but a
group of folks that have volunteered to assist TurboPower and help fellow
users who have questions about the operation of the products.
http://www.turbopower.com/pub/visualplanit/updates/Fixes.htm
http://www.turbopower.com/pub/orpheus/updates/Fixes.htm
"Martin Ph. Kreuzer" <in...@airkreuzer.com> wrote in message
news:3D6492C...@airkreuzer.com...
The reason for using the VDM is, that we're trying to run several modules
side by side (some DOS applics, some 16-bit Win, some 32-bit Win applics,
but all similar in what they do: retrieval software for bibliographic
databases).
The tsr in question is meant to be run alongside one of the DOS applications,
called in the same VDM as the main DOS applic itself, interacting with it (and
only with that module), and than disappear. May sound a bit strange, but worked
fine over the years: Evaluating and then modifying screen output supplying
different and additional information to the user.
The choice for WinNT was made because problems with the DOS box of
Win9x were much greater, because some of the programs in question would
simply refuse to run under Win2k, and WinNT was (looked at from that
perspective) the more stable platform, which proved true so far.
Martin
in...@airkreuzer.com