🚀 go-pugleaf

Ran wrote:

> Hello,
> 
> I am trying to find a way to execute a pif file within the context of
> my own application's console using AllocConsole.
> 
> My basic need is to have the console in my context so I can use the
> console API's AND I must use the pif parameters for EMS, XMS, and a
> few other parameters.
> 
> Is there a way to do this ? Is there a way around ?
> 
> For example, try running "start /b XX.pif" 
> 
> I am getting an error message
> 
> The NTVDM CPU has encountered an illegal instruction.
> and get the Close Ignore buttons.
> 
> This is not related to any problems in the DOS application.
> 
> If I use CREATE_NEW_CONSOLE in the creation flags, ofcourse everything
> works,
> but it is open in a new window. in the allocated console window I
> always get this GPF.
> 
> Is there a way to get the console window in my context after the OS
> created it ?
> 
> I can change _default.pif and just execute cmd.exe but I do not want
> to be dependant on _default.pif because of multiple executions issue.
> _default.pif is is hardcoded into ntvdm.exe.
> How can I allocconsole, run CMD with PIF settings ? and no
> _default.pif?

After AllocConsole() you need to get the handles to the console I/O and 
set them as standard input/output/error so that the new process can 
inherit the console I/O handles.

Use CreateFile("conin$", ...) and CreateFile("conout$", ...) as 
described in CreateFile() documentation. Make sure the handles get 
inheritable. Then pass the handles you get to SetStdHandle().

As an alternative you can skip the three SetStdHandle() calls and 
instead pass the handles to the new process in the STARTUPINFO structure 
passed to CreateProcess().

-- 
Olof Lagerkvist
ICQ: 724451
Web page: http://here.is/olof