Re: Tame: I spoke too soon

[Harry Binswanger hb@xxxxxxxx]

Carl,
My problem is that the version of Tame that works with my customization of
XyWrite *always* produces a NTVDM crash (anywhere from 5 minutes to an hour
after launching). And the later version of Tame that doesn't crash NTVDM
doesn't work *at all* with my XyWrite. Is there some way to use a different
version/flavor/implementation of NTVDM that wouldn't crash? This didn't
prevent NTVDM from crashing:
c:\xy\kmd.exe /c c:\xy\editor.exe

David Thomas doesn't respond to repeated emails.
Regards,
Harry


You have no choice but to shell if you want to run an external
> command from XyWrite. (Many U2 routines do so, of course.) KMD.EXE
> doesn't necessarily open a separate VDM -- although you can use it
> to do so with the START command that's built into KMD.EXE and
> CMD.EXE, the Win32 command interpreter (see below). The point of
> KMD.EXE is that it provides an NT-level command processor that works
> consistently in 9x and every other Win32 OS. That's the key virtue
> of KMD.EXE: consistent results under any Win32 OS.
>
> As for same VDM vs. new VDM, consider the following commands:
>
> dos/nv/z
> (Shell to COMMAND.COM -- i.e., open a DOS command-line session -- in
> the same VDM as EDITOR.EXE)
>
> dos/nv/z /c MY.BAT
> (Shell to COMMAND.COM and run MY.BAT in Editor's VDM)
>
> dos/nv/z /c kmd.exe
> (Shell to COMMAND.COM, then launch KMD.EXE in Editor's VDM)
>
> dos/nv/z /c kmd.exe /c MY.BAT
> (Shell to COMMAND.COM, launch KMD.EXE, then run MY.BAT -- KMD.EXE
> interprets the BATch commands -- in Editor's VDM)
>
> dos/nv/z /c kmd.exe /c start
> (Shell to COMMAND.COM, launch KMD.EXE, then START a new CMD.EXE (not
> KMD.EXE) session in a separate VDM)
>
> dos/nv/z /c kmd.exe /c start MY.BAT
> (Shell to COMMAND.COM, launch KMD.EXE, then START a new CMD.EXE
> session and run MY.BAT -- CMD.EXE interprets the BATch commands --
> in a separate VDM)
>
> dos/nv/z /c kmd.exe /c start kmd.exe /c MY.BAT
> (Shell to COMMAND.COM, launch KMD.EXE, then START a new KMD.EXE
> session and run MY.BAT -- KMD.EXE interprets the BATch commands --
> in a separate VDM)
>
> Note that to run any of these commands you must, at a minimum, load
> a second instance of COMMAND.COM on top of Editor to get things
> rolling. In other words, you've got to shell.
>
> --
> Carl Distefano
> cld@xxxxxxxx


Harry Binswanger
hb@xxxxxxxx