Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!devildog!jdalin
From: jdalin@devildog.att.com (Jimmy Dalin)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Gateway 2000 486/33
Message-ID: <1991Jun26.124404.12758@devildog.att.com>
Date: 26 Jun 91 12:44:04 GMT
References: <44717@netnews.upenn.edu> <44736@netnews.upenn.edu> <1991Jun25.001427.17701@serval.net.wsu.edu>
Reply-To: jdalin@devildog.att.com (Jimmy Dalin)
Organization: AT&T IMS - Piscataway, NJ (USA)
Lines: 17

A friend of mine had exactly the same problem with a new Gateway 2000 
486/25 system.  (Actually, it was one of several problems, including a
months-long wait for the system to be shipped.)  Eventually, it turned out
that Gateway had shipped a brand-new confighuration for their 486's, and not
all of the cards worked well together. I suggest that you call Gateway,
explain the problem, and hope that you're talking to a technician who is
already familiar with the problem.  I believe they simply sent my friend a
new controller card (or was it the I/O board?). 

His experiences were, by the way, enough for me to question ever buying a
system from Gateway.  Good luck.

-- 
Jim Dalin            "No Salga Afuera"  
AT&T                    N.Y.C.T.A.
ATTMail id: !jdalin            
Compuserve: 72260,1573