NetNews Usenet Archive 1992 #18/NN_1992_18.iso/spool/comp/os/mswindo/programm/misc/1395

Internet Message Format | 1992-08-19 | 1.8 KB

Path: sparky!uunet!snorkelwacker.mit.edu!ai-lab!zurich.ai.mit.edu!pshuang
From: [e-mail] (Ping Huang)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: WinExec and TSRs
Message-ID: <[e-mail]>
Date: 19 Aug 92 14:58:15 GMT
References: <[e-mail]>
Sender: [e-mail]
Organization: M.I.T. Artificial Intelligence Lab.
Lines: 25
In-reply-to: [e-mail]'s message of 18 Aug 92 16:17:01 GMT

In article <[e-mail]> [e-mail] (Tom Deneau) writes:

 > Can one use WinExec to invoke a non-Windows TSR application and then
 > have that TSR affect the parent window application's virtual machine?
 > (or is there some other way to do this?).  When I tried this, the TSR
 > was invoked, it hooked an interrupt vector, but the parent's view of
 > that interrupt vector remained unchanged.

The reason this is happening is that when you try to WinExec the TSR,
Windows detects that it is a DOS program and not a Windows program (by
looking for the New Executable header present on Windows executables)
and automatically starts up a new DOS box to run the TSR in, separate
from the system virtual machine where all Windows applications are
running (this sequence of events should be readily apparent visually).
You may be able to achieve the effect you want by putting a line to
start the TSR in the file WINSTART.BAT, which Windows will execute
before loading itself completely if in 386 Enhanced Mode. TSR's loaded
there will be visible to Windows applications, as documented in the
User's Manual.

--
| Ping Huang (INTERNET: [e-mail]) speaking for himself.
| "One Thing to name them all, One Thing to define them,
|  One Thing to place them in environments and bind them..."