>
>
>yep.  I had 1.3.2 on my 5000/200 and got those same errors.  

I believe that I 1st encountered this error (and discovered that the 1.2G
drivers did not have it) with 1.3.  mhitch has done quite a bit of
investigation into this problem, so check with him.


					--Greg

>
>-Dan
>
>On Wed, 3 Feb 1999, Simon Burge wrote:
>
>> Hi chaps,
>> 
>> Did anyone test 1.3.2 on a 5000/200?  We know it works with 1.2G drivers
>> and doesn't on 1.3.3...  I'm trying to narrow down exactly where the
>> problem is and get it fixed for 1.3.4 (which will freeze in approx. one
>> week).
>> 
>> Simon.
>> 
>