home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uchinews!quads!pynq
- From: pynq@quads.uchicago.edu (Jeremy Mathers)
- Subject: Re: LOADFIX and low-memory EXE loading
- Message-ID: <1993Jan12.144008.5697@midway.uchicago.edu>
- Sender: news@uchinews.uchicago.edu (News System)
- Reply-To: pynq@midway.uchicago.edu
- Organization: D. J. Dougherty & Associates
- References: <C0ozzJ.DJA@csugrad.cs.vt.edu> <1993Jan12.005245.9608@rei.com>
- Date: Tue, 12 Jan 1993 14:40:08 GMT
- Lines: 30
-
- In article <1993Jan12.005245.9608@rei.com> fox@rei.com (Fuzzy Fox) writes:
- >jjarrett@csugrad.cs.vt.edu (James Jarrett) writes:
- >
- >>My DOS manual does not mention LOADFIX, so all I have is the HELP LOADFIX
- >>documentation. How does it work and why is it necessary?
- >
- >LOADFIX allocates memory up to the first 64K segment, then loads your
- >program at that point, avoiding the problems that occur when the code
- >segment is below the 64K boundary. Normally only DOS is below this
- >boundary, but DOS 5 can load high and thus allow programs to run there.
- >
- >>Next, how can I write a program so it doesn't need LOADFIX?
- >
- >You must be doing something strange to generate a program that fails.
-
- Yup. The poster mentions that he is not, as far as he knows, using
- EXEPACK, but it is possible that some compiler or linker is doing it or
- the equivalent behind his back. I would get LZEXE (from Simtel, et al),
- and try running UPACKEXE on the executable file. It might tell you
- something...
-
- ************************************************************************
- "The rich are different from you and me."
- - Fitzgerald -
- "Yes. They have more money."
- - Hemmingway -
-
- - pynq@quads.uchicago.edu, who is still costing the net
- hundreds, if not thousands, of dollars, every time he posts -
- ************************************************************************
-