Hello Chris Wiles ([EMAIL PROTECTED]),
You wrote about "[netconnect] Re: Hypercom & Voyager",
on Fri, 9 Jul 1999 22:08:07 +0100.
>
> > It seems there's a lot of bad air being produced over Hypercoms and
> > Voyager. I have had a Hypercom 3Z in my A4000 for over a year without
> > problem.
>
> There's no bad air from me, I had to point out the work for 99% of people,
> well, everyone except Jason Watson ;)
OK then Chris no problems exists on the older cards. I mean the fact
that VMC have recognised ta hardware problem on the older Hypercom1
and 3Z don't effect anyone but me.
I may be the only person who has this problem on this list but if I am
the only one in the world how come VMC have addmitted and are working
on a solution?
For those interested check:
http://www.vmc.de/ger_vmc_bfix.html
Details for a fix on older hypercom1 cards is already there with the
one for the 3Z in the pipline.
I have no bad opinions on my 3Z only facts:
Fact 1. This hypercom card is one that has the same problems as
detailed in the abouve URL.
Fact 2. The latest 2.88beta, 2.88beta2 and 2.89 drivers do not work
on this card. I am currently using 2.85 which is the most
recent working versions VMC supplied.
Beyond that I don't think I have to waste any further bandwidth on
any comments aimed at Chris. VMC's website and other peoples postings
to this list seem to make may point for me.
--
Jason Watson.
====================================================
Towerised A4K, WB3.1, CS-PPC 060-60 604-200 2+64MB,
CV-643D 4MB (CGfx4.1), 2.1GB IDE (PFS2), Atapi ZIP,
6x2x2 CD-RW (IDEFix97 3.4). Dynalink 33.6 Modem (NC v 2.3)
====================================================
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
