From: cwalsh AT nf DOT sympatico DOT ca (Colin Walsh)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: LD looks at zip drive
Date: 30 Dec 97 04:05:43 GMT
Organization: Colossal Software
Lines: 26
Approved: By the Department of Silly Walks
Distribution: world
Message-ID: <34a87317.0@204.101.95.15>
References: <3481D587 DOT 5A03 AT netunlimited DOT net> <19971229043201 DOT XAA20808 AT ladder01 DOT news DOT aol DOT com> <687t62$7h2 AT freenet-news DOT carleton DOT ca>
Reply-To: cwalsh AT nf DOT sympatico DOT ca
NNTP-Posting-Host: 204.101.95.15
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <687t62$7h2 AT freenet-news DOT carleton DOT ca>
ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) wrote:

> 
> Myknees (myknees AT aol DOT com) writes:
> 
>>My zip drive has nothing to do with the process, as far as I know.  The zip
>>drive is not the tmpdir or anything.  It does take a while for the zip drive
>>to wake up, and it would be very nice to be able to make LD stop whatever it
>>is doing.
> 
> The linker does this with zips, cdroms, and tape drives if the drive is in
> the PATH. Make sure the drive is not in your PATH nor any directories on it.
> 

My zip drive (which I've only had for a few days) does the same exact thing
when I compile (and I'm not using RHIDE). I put the -v switch in and it occurs
when ld is running. In the command line used to invoke ld there is no reference
to any files being accessed on drive d:, also, there is no reference to anything
on the drive in my path. I'm guessing tho' that no harm is being done and its
just some sort of quirk of ld.

Happy Holidays,
Colin Walsh
cwalsh AT nf DOT sympatico DOT ca