Date: Tue, 7 Oct 1997 14:45:31 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bill_HellGateS <eng60667 AT leonis DOT nus DOT sg>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP Question
In-Reply-To: <Pine.OSF.3.95.971007081054.19645C-100000@leonis.nus.sg>
Message-ID: <Pine.SUN.3.91.971007144450.25685M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 7 Oct 1997, Bill_HellGateS wrote:

> What is Go32-V2? What is it exactly used for? Forgive my ignorance.

Please make a habit of looking into the DJGPP FAQ list (available as
v2/faq210b.zip from the same place you get DJGPP) before posting
questions.  Then you will never need to apologize for ignorance.

The following excerpt from the FAQ answers this:


22.12 What is that `go32-v2.exe' program?
=========================================

**Q*: What is go32-v2 for?*

*A* :  The `go32-v2' program does the following:

   * With no command-line arguments, it prints the available physical and
     virtual memory, much like `go32' did in v1.x.

   * It can run unstubified v2 COFF images, like this:

           go32-v2 myprog

   * If you rename it to `go32.exe' and put on your `PATH' before the v1.x
     `go32.exe', it can also run a v1 COFF images, by loading the v1.x `go32'
     and letting it do the job.  With this setup, you can run v2 programs
     from v1.x programs, because the v1.x program will load `go32-v2' (since
     it found it first on the PATH) which knows how to run v2 images, instead
     the original `go32' which cannot.