Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!ucsfcgl!cgl.ucsf.edu!kneller From: kneller@cgl.ucsf.edu (Don Kneller%Langridge) Newsgroups: comp.sys.ibm.pc Subject: Re: reducing size of exe files Message-ID: <10234@cgl.ucsf.EDU> Date: Tue, 9-Jun-87 16:08:36 EDT Article-I.D.: cgl.10234 Posted: Tue Jun 9 16:08:36 1987 Date-Received: Fri, 12-Jun-87 04:33:17 EDT References: <4044@amd.UUCP> <3320018@hpsrlc.HP.COM> <2723@mtgzz.UUCP> <1314@dataio.Data-IO.COM> Sender: daemon@cgl.ucsf.edu Reply-To: kneller@socrates.ucsf.edu.UUCP (Don Kneller) Organization: UCSF Computer Graphics Lab Lines: 29 In article <1314@dataio.Data-IO.COM> bright@dataio.UUCP (Walter Bright) writes: >In article <2723@mtgzz.UUCP> rosen@mtgzz.UUCP (t.rosenfeld) 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). I don't know if my previous posting got out about problems with EXEPACK. 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. This can cause your system to hang when allocating memory or trying to exec() a subprocess. The solution to the problem is to use EXEMOD to fix the maximum number. "exemod foo.exe /max 1" will reset the maximum number to be the equal to the minimum number again. ----- Don Kneller UUCP: ...ucbvax!ucsfcgl!kneller ARPA: kneller@cgl.ucsf.edu BITNET: kneller@ucsfcgl.BITNET