Date: Tue, 15 Oct 1996 13:34:03 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Cc: "John M. Aldrich" <fighteer AT cs DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: Install thingy
In-Reply-To: <Pine.NEB.3.95.961015130455.10709A-100000@ananke.amu.edu.pl>
Message-Id: <Pine.SUN.3.91.961015133109.19845E@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 15 Oct 1996, Mark Habersack wrote:

> easy. However to support this way of operation I'd have to further modify the
> stub code. If djverify fails to run for some reason (e.g. i cannot load DPMI
> host or anything else that prevents the COFF image from being run) I'd have to
> check the return code in RM stub to present the user some explicative error

Just use the batch file similar (or identical) to the one included in 
djverify.  Batch files can also sense the exit code, you know.

> >host.  So having a stand-alone image (with PMODE or Charles unreleased 
> >version which writes CWSDPMI image the first time it runs) is all you 
>
> What does it mean it 'write...'??? Is there any version of CWSDPMI that can be
> attached to COFF just like pmode can? I'd prefer it this way, certainly.

Charles wrote (an unpublished) version of the stub which would write an
image of CWSDPMI if it doesn't find one the first time it is run.