Hello Chris Wiles ([EMAIL PROTECTED]),
You wrote about "[netconnect] Re: Hypercom & Voyager",
on Sat, 10 Jul 1999 09:48:44 +0100.
>
> > 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.
>
> As I keep telling you over and over and over again, problems *may* exist on
> *some* cards, but the way you kept writing your replies indicated that *all*
> the cards had problems and/or the drivers were 'buggy'. Same with Voyager.
>
> This kind of generic 'everything has a problem as I have' put other people
> off. If we establish that your card has a problem, and this is rare, this is
> a different matter entirely.
Incidently if you actually read the whole message before before
"jumping up and down" like a mad man everytime some one disagrees with
you you would of noticed the URL.
Did you visit the site?
Did you read the info there?
VMC STATE THAT A CERTAIN UART CHIP REVISION ON OLDER HYPERCOM1 CARDS
HAS A PROBLEM. IT DESCRIBES THE SYMTOMS AND DETAILS A HARDWARE FIX
FOR IT. IT ALSO MENTIONS THAT THE SOME 3Z'S HAVE THE SAME PROBLEM BUT
AT THE MOMENT THEY HAVE NOT PINNED DOWN THE CAUSE AND SO DO NOT HAVE A
SOLUTION. WHEN ONE IS FOUND THEY WILL POST IT.
loud enough for you. "Jesus H Christ" if VMC have admitted a problem
with "SOME" of the older cards then why the hell can't you?
If it i a chip revison problem and they used various revisons and
manufactures then that explains why some cards had (have) problems and
not others. When you buy bulk IC's you go to a stockest and ask for a
1000 16c552 UARTS then that is what you will get. Unless you specify
then you will can end up with various revisions form various
manufacturers.
Hell do you still stock and sell the old revision "Hypercom1" and 3Z ?
If the answer is NO then stop bitching.
I have never said in any of these postings that the current range of
Hypercom range is hardware bugged. I have stated which models had the
problem, included a URL for the relevant info regarding the chip
revision from the MANUFACTURERS OWN website. I did not make any of
this up, if you have a problem with it then complain to VMC.
If you do still stock them have you checked the for chip revison
for the Hypercom1?
YES or NO?
Do not blame me for damaging your sales with what you term "generic"
responces when you obviosly don't read all the way through them.
Especially when the manufacturers of the card are aware of the
problem with the OLDER HC1 and 3Z cards.
Finnally concerning the drivers VMC have not replied to the repost I
have sent them detailing the driver problems I have here (but it has
not yet been 24hours). Additionally the original poster which
triggered this "shouting match" (Not his fault by the way) between
us has not yet replied as to if his problem is driver related after
checking. (If it turns out to be driver based then I expect you to
appolgise publically by the way). Either way we will have to wait.
You did say to me that you have the latest drivers working on your 3Z
so obviously it is a problem my end. However as you seem to of
declined my request to send me a copy of the drivers you are using I
cannot verify it can I?
--
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]>
