Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!uw-beaver!uw-june!uw-entropy!dataio!bright
From: bright@dataio.Data-IO.COM (Walter Bright)
Newsgroups: comp.sys.ibm.pc
Subject: Re: reducing size of exe files
Message-ID: <1316@dataio.Data-IO.COM>
Date: Wed, 10-Jun-87 13:46:01 EDT
Article-I.D.: dataio.1316
Posted: Wed Jun 10 13:46:01 1987
Date-Received: Sat, 20-Jun-87 04:18:57 EDT
References: <4044@amd.UUCP> <3320018@hpsrlc.HP.COM> <2723@mtgzz.UUCP> <1314@dataio.Data-IO.COM> <10234@cgl.ucsf.EDU>
Reply-To: bright@dataio.UUCP (Walter Bright)
Organization: Data I/O - FutureNet Corp., Redmond, WA
Lines: 13

In article <10234@cgl.ucsf.EDU> kneller@socrates.ucsf.edu.UUCP (Don Kneller) writes:
<In article <1314@dataio.Data-IO.COM< bright@dataio.UUCP (Walter Bright) writes:
<<I have trouble with EXEPACK now and then. It occasionally produces an
<<EXE file that promptly crashes. Adding or removing a few bytes of code
<<from an object module causes it to start working again. Using the linker
<<with the /E switch exhibits the same results (must use the same code).
<
<One thing I've noticed is EXEPACK can reduce the maximum number of
<paragraphs (of memory) below the minimum number.  This happens when
<you've linked with linker flag /CP:1 (which sets the maximum number of
<paragraphs equal to the minimum number), then EXEPACKed.

I am not using the linker flag /CP:1