Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!hubcap!ncrcae!ncr-sd!SanDiego.NCR.COM!tortuga!kshafer
From: kshafer@tortuga.SanDiego.NCR.COM (Keith Shafer)
Newsgroups: comp.windows.ms.programmer
Subject: Re: *HELP!* MS LINK errors!
Message-ID: <1991Jun8.154945.9258@donner.SanDiego.NCR.COM>
Date: 8 Jun 91 15:49:45 GMT
References: <1991Jun7.161503.11831@vaxa.strath.ac.uk>
Sender: news@donner.SanDiego.NCR.COM (News Owner)
Reply-To: kshafer@tortuga.SanDiego.NCR.COM (Keith Shafer)
Organization: NCR Corporation, Rancho Bernardo
Lines: 25

In article <1991Jun7.161503.11831@vaxa.strath.ac.uk> cihs08@vaxa.strath.ac.uk (Kenny Moriarty) writes:
>I'm using Microsnot C6.0 and SDK3.0 to write a major Windows3 application. I've
>got a 20Meg partition ('D' drive) which has WINDEV and my source code on it.
>There is 5Meg free disk space (unfragmented). My C compiler is on the 'C'
>drive. I've been using this setup for about 8 months. All of my environment
>variables are okay, nothing has changed.
>
>So why, all of a sudden, am I getting LINK (v5.10) errors 'L1085 : Cannot open
>temporary file'? My TMP variable is set up to point to D:\GARBAGE.TMP which
>exists.
>
>Any ideas? Please help?!
>

I had the same problem about six months ago.  If you are running your system
on a Novell lan then here is the solution.  Call Microsoft and request a
newer version of LINK (v5.13).  While you are waiting for the new linker, you
can fix the problem by not loading IPX.COM and [XMS]NET3.EXE. If you are not
on a Novell lan, you might try removing any memory resident programs from your
autoexec.bat.

Hope this helps...


- Keith.Shafer@SanDiego.NCR.COM