home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!wupost!psuvax1!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: PACKED FILE CORRUPT & DOS XMS settings
- Message-ID: <1993Jan5.202201.28015@njitgw.njit.edu>
- Date: 5 Jan 93 20:22:01 GMT
- References: <1992Dec31.102841.203438@uctvax.uct.ac.za>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 27
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Dec31.102841.203438@uctvax.uct.ac.za> bokkie@uctvax.uct.ac.za writes:
- >When I use a XMS_MEMORY_LIMIT setting greater than zero
- >in the DOS Settings, then one of my DOS applications fails
- >to start, and I get a message from DOS saying:
- >
- > Packed file is corrupt
- >
- >Any ideas why this is?
-
- This happens under DOS 5.0 if you put everything in UMB's and HMA.
- Packed executables (that had EXEPACK run on them) don't unpack if they
- load into the bottom 64K of memory. When you give yourself tons of
- free memory (putting everything in upper memory), the program dies
- this way.
-
- DOS 5.0 comes with a LOADFIX.EXE program which forces an app to load
- above the 64K line. Note that memory below 64K becomes useless, but
- the app will load. You'll probably do better with this than not using
- upper memory anyway, so go for it.
-
- Just prefix your usual command line with LOADFIX, and all will work
- fine.
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-