Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!batcomputer!riley
From: riley@batcomputer.tn.cornell.edu (Daniel S. Riley)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice 5.05 available
Message-ID: <9836@batcomputer.tn.cornell.edu>
Date: 4 Mar 90 22:39:13 GMT
References: <661@cameron.cs.duke.edu> <16457@well.sf.ca.us>
Reply-To: riley@tcgould.tn.cornell.edu (Daniel S. Riley)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 23

In article <16457@well.sf.ca.us> farren@well.sf.ca.us (Mike Farren) writes:
>A consumer warning: I got the same call, immediately downloaded the patch
>files, and found that they would not operate correctly.  I notified Lattice
>of the problem, and they are looking into it.  In the meantime, they are
>going to send me a complete 5.05 upgrade.

5.05 worked fine for me.  But not for several other people I've heard
from.  So...

After hearing this story n+1 times, I've come to the conclusion that
Lattice screwed up the 5.04 upgrade and sent out two different versions
(probably one a prerelease beta).  I've heard so many tales of people
having inexplicable upgrade problems that I never saw, that something
like this must be true.  If the 5.05 patch doesn't apply correctly,
or lmk stopped working after the 5.04 patch, or stdlib.h and string.h
have conflicting declarations after you applied the 5.04 patch, then
you may have the wrong version of the 5.04 patch.  Do the usual checks 
for operator error.  If you can't find any, call Lattice and ask them to 
ship you the complete 5.05 update.  They seem pretty nice about doing
this, and if enough people call they may figure out what went wrong.

-Dan Riley (riley@tcgould.tn.cornell.edu, cornell!batcomputer!riley)
-Wilson Lab, Cornell University