<Intel's XEON/Pentium II/Celeron designs do not have the problem - they are "better by design".>
Of course, pal, Intel is above any law of physics
and logic! Nonsense. Read this up:
------------------------ quote1
Subject: Re: Win95 bug with >=350MHz
Date: 27 Sep 1998 18:45:27 GMT
From: yanquidawg@aol.com (YanquiDawg)
Organization: AOL aol.com
Newsgroups: comp.sys.ibm.pc.hardware.chips
>>The first error is a result of a divide exception in IOS.VXD,
>>the second is due to a similar error within ESDI_506.PDR
>>or CSIPORT.PDR.
>
>Has anybody seen this error? It's also
>interesting that MS has not posted
>the fix and you have to telephone
>them and plead/beg for it. How
>embarrassing!
>
I've gotten these errors on Intel CPU's when Overclocking
past a certain point. Dawg
----end of quote1;
--- quote2:
Subject: Re: Win95 bug with >=350MHz
Date: Mon, 28 Sep 1998 16:42:54 GMT
From: clayn@NOSPAMbga.com (Clay)
Reply-To: clayn@NO_JUNKbga.com
Newsgroups: comp.sys.ibm.pc.hardware.chips
I've seen this error before, and not on systems 350 or faster. Last
week we went threw hell installing Win95 on a Compaq 100 mhz 486
laptop. Kept getting that error. Turned out to be funky drivers for
the docking bay interface. New drivers from Compaq fixed the problem.
We also got it on one of our fax servers (a K6200 w/ 4 modems and fax
routing software) and was the primary reason for upgrading to Win98 on
that box. Since then we haven't had any problems with it.
There are several issues like this one that MS is aware of, but are
not fixing in older product versions. In some cases the fix causes
more problems then it solves or are to complicated for general
release. I'm not defending them for this, but it is a bigger issue
than just posting a fix on their web site.
------ end of quote2;
------ quote3:
Re: K6-2 350 and Windows 95 timing bug
Author: Anthony Hill
Email: hilla@uoguelph.ca
Date: 1998/11/19
Forums: comp.sys.ibm.pc.hardware.chips
>Also, if this is a timing problem due to the
>processor speed, does a Pentium
>II have the same problem?
Apperently the PII 333MHz and above did have the same problem,
but Microsoft put a partial fix into the software before any PII
333MHz chips were released. Faster PIIs then are currently availible
probably could be affected in the same way that the K6-2 350+ chips
are affected, but for the timing loop in which the bug occurs, the
K6-2 350MHz chip is faster then any PIIs out there now (certain
instructions execute considerably faster on the K6, while other
execute considerably faster on the PII).
Anthony Hill
hilla@uoguelph.ca
------- end of quote3;
------- quote4:
Re: "Strange ERROR message when OVERCLOCKING ...read this!"
Author: fammacd=!SPAM^ (George Macdonald)
Email: fammacd=!SPAM^nothanks@garden.net
Date: 1998/11/01
Forums: comp.sys.ibm.pc.hardware.chips
On Fri, 30 Oct 1998 20:21:25 GMT, dpenkala@dc.net (Dave Penkala) wrote:
>The bug you refer to is only with Win95, only with AMD K6-2 CPUs and
>only with CPU speeds (overclocked or otherwise) of 350 and up.
>
>Not applicable to this problem.
But it *did* occur with the PII/333 until Intel "fixed" it - at least
according to a story at www.news.com. OTOH that bug typically gives probs with IOS.VXD and ESDI_506.PDR.
Rgds, George Macdonald
---------end of quote4;
--------quote5:
Re: "Strange ERROR message when OVERCLOCKING ...read this!"
Author: root
Email: root@bbs.fidonet.org
Date: 1998/11/02
Forums: comp.sys.ibm.pc.hardware.chips
I have the exct problem with yours, I'm using BH6+Celeron300A+IBM-UDMA
Harddisk. This happens even when I'm not overclocking the 300A. Any
solution??
Rico Laguna <brazil@tiac.net> wrote:
: I seem to be getting a STRANGE ERROR message
: when booting my P II 300
: overclocked to 450 <100x4.5> on my ABIT BH6
: right before Windows 98 boots it'll post
: a message saying "UNABLE to
: FIND/LOAD WINDOWS/SYSTEM/VMM32.SYS MISSING.
: ......PRESS ANY KEY TO RESTART"
: then my machine will automatically reboot
: The funny thing is, it wont happen every boot.
: It seems to only happen
: randomly every 4th or 5th boot until tonight...
: .it happened 3 STRAIGHT
: BOOTS and I have been noticing this
: message comming up more frequent
: now on boot ups recently.
-----------end of quote5. |
