Path: utzoo!attcan!uunet!bfmny0!tneff
From: tneff@bfmny0.UUCP (Tom Neff)
Newsgroups: comp.unix.microport,comp.unix.i386
Subject: Re: new DOSMerge
Keywords: DOSMerge VP/ix scripts help
Message-ID: <14429@bfmny0.UUCP>
Date: 30 Jun 89 22:02:59 GMT
References: <51@calcite.UUCP>
Reply-To: tneff@bfmny0.UUCP (Tom Neff)
Followup-To: comp.unix.microport
Organization: ^
Lines: 27

In article <51@calcite.UUCP> vjs@calcite.UUCP (Vernon Schryver) writes:
>VP/ix is a pure DOS-in-a-window sort of thing.  Interactive tells me that I
>cannot run INTEL's PLM386 development stuff from a makefile, as I now do
>with DOSMerge.  DOSMerge allows a DOS program which does no more than
>character stuff to the console and keyboard to talk with UNIX standard
>I/O.

VP/ix absolutely allows this.  A command of the form

	dos -c "myprog" | nocr | less

works as intended.  VP/ix detects the pipe or redirection of stdout
and forces the DOS program output to handle 1.

>Another restriction of VP/ix is that DOS programs can only talk to devices
>that have drivers in the UNIX kernel.  

VP/ix doesn't care what devices are linked into the kernel.  It has a
special hook called the Virtual Device Interface (VDI) which allows
Direct Device Access (DDA).  There is a set of utilities (dda*) that let
you configure nonstandard devices into VP/ix without a kernel rebuild.
I have successfully used it to add things like a Scanjet interface card,
which then worked perfectly under Simul-Task (the name for VP/ix on this
AT&T 6386E system).
-- 
"My God, Thiokol, when do you     \\	Tom Neff
want me to launch -- next April?"  \\	uunet!bfmny0!tneff