From: "Tony O'Bryan" <aho450s AT nic DOT smsu DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: LD looks at zip drive
Date: Wed, 31 Dec 1997 08:41:52 -0600
Organization: Southwest Missouri State University
Lines: 13
Message-ID: <34AA59B0.5481@nic.smsu.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 971229133224 DOT 28272C-100000 AT is> <6883ah$9ld AT freenet-news DOT carleton DOT ca> <34A7CB4B DOT 74C6 AT nic DOT smsu DOT edu> <68d6uq$3c4 AT freenet-news DOT carleton DOT ca>
Reply-To: aho450s AT nic DOT smsu DOT edu
NNTP-Posting-Host: sara.a18.smsu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Paul Derbyshire wrote:
> 
> Tony O'Bryan (aho450s AT nic DOT smsu DOT edu) writes:
> > So, to summarize, perhaps he has some type of partitioning problem.
> 
> No, because then, as you observe, he'd have the behavior long before the
> linker ran.

Yep.  I was, of course, aghast to hear that a DJGPP base utility had a
hard-coded path in it (read that last line with a health dose of
tongue-in-cheek).  I had automatically eliminated that as a possibility
without a second thought.  As a result, I was starting to grasp for
solutions at the fringe of likeliness.