Xref: utzoo comp.sys.ibm.pc.hardware:3808 comp.os.msdos.misc:801 comp.sys.ibm.pc.misc:4705
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!mit-eddie!uw-beaver!cornell!vax5.cit.cornell.edu!hd7x
From: hd7x@vax5.cit.cornell.edu (Sanjay Aiyagari)
Newsgroups: comp.sys.ibm.pc.hardware,comp.os.msdos.misc,comp.sys.ibm.pc.misc
Subject: Re: Gateway 2000, Diamond SpeedStar, Pheonix Bios que
Message-ID: <1990Dec13.223116.1615@vax5.cit.cornell.edu>
Date: 14 Dec 90 02:31:16 GMT
References: <4148@cui.unige.ch>
Distribution: comp
Lines: 17

In article <4148@cui.unige.ch>,afzal@cui.unige.ch (Afzal Ballim) writes:
>
> The second problem is more bothersome.  I launch Windows 3.0 from my
> autoexec.bat file.  Sometimes (1 out of 8 or 10 times) when Windows comes up
> the monitor goes crazy (it can't seem to sync.).  [Note:  this is with the
> standard Gateway monitor.] By default, I star in 800x600x256 mode, although
> I have seen the same in 1024x768x256 mode.  When the machine arrived I did
> have a problem with the SpeedStar, in that there was no red.  On taking the
> board out, I saw that one of the chips was not seated properly in the
> socket, so I put it in and that cleared up that problem.  I don't know if
> this is a problem specific to Windows (I have not seen it exhibited by any
> other software I have) or if it is a hardware problem.  Any ideas anyone?

Have you tried turning on the monitor for a few seconds before you turn on the
system? Perhaps the monitor has to "warm up" in order to synchronize with the
card.
Sanjay Aiyagari (hd7x@vax5.cit.cornell.edu)