home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!hal.com!decwrl!bu.edu!cvbnet!rishikesh!jsingh
- From: jsingh@rishikesh.NoSubdomain.NoDomain (Jitendra Singh 5-2)
- Newsgroups: comp.sys.ibm.pc.misc
- Subject: Re: Changing the bus speed?
- Message-ID: <3610@cvbnetPrime.COM>
- Date: 27 Jul 92 18:09:55 GMT
- References: <24JUL199209035496@zeus.tamu.edu> <3939@cruzio.santa-cruz.ca.us>
- Sender: postnews@cvbnetPrime.COM
- Organization: Computervision Corp.
- Lines: 24
-
- In article <24JUL199209035496@zeus.tamu.edu>, rcg1597@zeus.tamu.edu (GUYNN, RICHARD CARL) writes:
- >
- > I have seen quite a few people talking about the fact that they have
- > upped the bus speed on their boards. I was just wondering, is this simply done
- > by replacing the oscillator crystal? Or is there something else that must be
- > done with the crystal changeout? Ids there an easy way to determine whether the
- > board will support the new speed?
-
- My Gateway 2000/386 has a little switch on the motherboard that can be set to
- `high speed' if the user wishes. I believe it changes the number of wait states
- in the bus protocol, or some such..
-
- Gateway sets it to `low speed' and inserts a sentence in the hardware manual
- that says `increase speed at your own risk'.
-
- I did. Then spent many frustrating hours trying to figure out why the file
- manager of MS-Windows 3.1 would freeze up when I touched drive a: or drive b:
- icon. It would operate just fine under DOS, which kept me from guessing that
- it might be the bus speed causing problems. I had to set the speed back in order
- to get Windows 3.1 file manager to work right again.
-
- So, try it. Change nothing else for some time and verify it all still works.
-
- js
-