🚀 go-pugleaf

In article <22306@well.sf.ca.us> brent@well.sf.ca.us (Brent Southard) writes:
>In article <1990Dec20.202200.10633@naitc.naitc.com> gkrone@bbs.NAITC.COM (Gary Krone) writes:
>>We are having trouble with Microsoft Link 5.1 on a large Windows 
>>project ( 60+ source files ).  The problem didn't show up until 
>>we hit around 59 source files.  When linking this project while 
>>logged onto our Novell network we get an L1087 error: unexpected 
>>end-of-file on scratch file.  
>
>We had the same problem too, albeit with an even larger (@180 files)
>project.  The only solution for us was to buy OptiLink/Windows from SLR
>Systems.  This was perhaps the best purchase we ever made!  Links are MANY
>times faster, and never encounter the problems that Link did.  Not only
>that, but the program is half Link's size!  It seems Link has problems
>keeping files open when not necessary, hence you run out of file handles.
>Note that setting your FILES limit in config.sys won't help -- the limit
>is imposed on the Link executable itself.
>
>Buy OptiLink today.  You'll be glad you did!
>
>brent
>

Actually, the problem is not all that fatal.  The error L1087 occurs when
the device to which you have assigned your TMP directory runs out of space.
If your TMP is in the RAM drive (good idea for improving the link time), make
sure that whenever you have your network running that the drive letter
for RAM drive does not conflict with your network drives.

If you can afford the extra RAM, try to do your links IN RAM DRIVE.  The
improvement in speed can be dramatic.

Adam Rybicki
arybicki@dhw68k.cts.com