Subject: Re: Stripping the old go32?
To: sasbnb AT unx DOT sas DOT com
Date: Thu, 11 Aug 1994 21:50:10 -0600 (CDT)
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu, JMILLER AT chess DOT eisc DOT utoledo DOT edu
From: mcastle AT umr DOT edu (Mike Castle)

Amazingly enough sasbnb AT unx DOT sas DOT com said:
> 
> 
> Aloha,
> 
> pbmplus is my only program which requires empanded memory, and setting
> it up costs me 123k of lower memory (628k to 505k free). JMILLER
> suggested that there may be a way to "strip the old go32.exe and add the
> new go32 or stub".
> 
> Is this a possibility? If so, how can I pull it off?

Pbmplus was ported using 1.09.  I did not bind go32.exe to the
p?mmerge.exe.  All you *should* need to do is replace the
go32.exe that came with pbmplus with the most recent version of
go32.exe.

When you extract the pbmplus package, go32.exe is in the ./bin
directory.  Simply replace that version of go32.exe with the most
recent go32.exe from the latest djgpp distribution (make a backup
copy of the supplied go32.exe, of course).

You *may* have to run a fixup program against the stubbed
executables (p?mmerge.exe).  A program called "dpmifix" runs
through my mind, but as I'm a little behind the times wrt djgpp,
I'm unsure if this is necessary or not.  I hope someone more upto
date with the djgpp stuff will clarify on upgrading an excutable
from 1.09 to 1.11m5/1.12.

mrc
-- 
Mike Castle .-=NEXUS=-.  Life is like a clock:  You can work constantly
  mcastle AT cs DOT umr DOT edu     and be right all the time, or not work at all
   mcastle AT umr DOT edu       and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen