AnsweredAssumed Answered

vrf DLVA Implementation in VEE?

Question asked by bill.ossmann on Jul 8, 2004
> Maybe this could be resolved another way.

Well the basic problem is that for any interpretive host process (such as
cmd, command, VEE or veerun) the process name gives you absolutely no
information about exactly what is being run. VEE's process name is always
vee and it's executable file is always vee.exe regardless if it's measuring
relay contact resistance or controlling a manufacturing process. It's the
same for .bat files and in fact everything of this nature.

The information that's necessary is contained in the command line used to
start the process and that information is private to the process. You can
look at running processes all you want, but you'll never know what any given
vee, cmd, gw-basic, wsh, asp or any other interpreter is doing unless you
know what interpreted program it's running.

In fact, it's not just the command line. Any information at all that might
give you a clue is private, such as the current directory.

The situation is even worse for virtual dos machines. And worse yet for WOW
VDMs. These subsystems create virtual environments in one and two layers
respectively that are impossible to penetrate without 32:16 bidirectional

The method I have in mind won't do for DOS programs or 16-bit Windows
programs. In fact my preferred 32-bit solution is proving very difficult to
get working and I'm just about to abandon it and try something else.

You are currently subscribed to vrf as:
To subscribe send a blank email to "".
To unsubscribe send a blank email to "".
To send messages to this mailing list,  email "". 
If you need help with the mailing list send a message to "".