Apparent success with Type-4 P66 & Socket-4 Overdrive P133
Tim Clarke
without going into too much analysis as to WHY its working. I have this
up and running reliably, so far. Using a T4-P66 complex previously Flashed
to BIOS Level 10, an 897 cache controller from a T4 P90 complex and a stock
P120/133 Overdrive for Socket4 upgrade processor.
It threw the odd "1047000 221" error (cache/memory-related?) early in
the power-on, auto-reconfigure, set date&time, auto-reboot song and dance
but doesn't seem to do that anymore. Maybe there are some devious POS-stored
auto-tuned cache-control/memory-access related parameters, but hey, I'm not
complaining.
--
Regards,
Tim Clarke (Guildford, UK)
David L. Beem
Excellent. </Mr.Burns>
David
Da...@IBMMuseum.com
wm_w...@hotmail.com
> Hi All,
> without going into too much analysis as to WHY its working. I have this
> up and running reliably, so far. Using a T4-P66 complex previously Flashed
> to BIOS Level 10, an 897 cache controller from a T4 P90 complex and a stock
> P120/133 Overdrive for Socket4 upgrade processor.
So this begs the question...is the complex able to run "demanding"
software, like say Windows NT, OS/2 or Linux?
There are stories around that say others have gotten the complex to
start up, but that it is not reliable under any kind of load.
William
Tim Clarke
this
> > up and running reliably, so far. Using a T4-P66 complex previously
Flashed
> > to BIOS Level 10, an 897 cache controller from a T4 P90 complex and a
stock
> > P120/133 Overdrive for Socket4 upgrade processor.
>
> So this begs the question...is the complex able to run "demanding"
> software, like say Windows NT, OS/2 or Linux?
Well, I have it in my "development" workhorse running Warp 3 FixPak 40 with
Debug Kernel, bashing about on EPM and TEDIT, with CD-player going, plus MS
C 6.00A compiles of the OS2CDROM.DMD DASD Manager Driver with SCSI Changer
support addition that I'm developing. (Who needs 6 CD symbols for every
Pioneer DRM-6nnnX hooked-up, not to mention the 18 in a DRM-1804X, when
there's only one accessible at any one time), so it's not being
under-utilised I'd say.
I'll bet the next question is going to be "can you list all the chip
revisions etc.". I can just feel that pregnant pause ticking away.
--
Regards,
Tim Clarke (a.k.a. WBST)
wm_w...@hotmail.com
> I'll bet the next question is going to be "can you list all the chip
> revisions etc.". I can just feel that pregnant pause ticking away.
Not from me at least. :-)
I don't have a Type 4-P66 complex any longer. I've never even seen the
133MHz Pentium overdrive CPU. I suppose that if I ever do, I will put
that in my mother's aging Packard Bell P60 box. (No comments. It is the
only computer she has ever had, and it is still all she needs. Not bad,
considering that it has been in use since 1992.)
> (Who needs 6 CD symbols for every Pioneer DRM-6nnnX hooked-up,
> not to mention the 18 in a DRM-1804X, when there's only one accessible
> at any one time), so it's not being under-utilised I'd say.
Those are nice drives. I didn't know there was an 18-disc
version...will have to look for that one. The DRM-624X is very common
around these parts. A lot of them came with some early type of
electronic card catalog system and these are now being phased out.
Oftentimes I get the drives for nothing other than the time to haul
them away. Sad thing is that the NT 4.0 "Spock" driver seems too buggy
to handle the mutiple discs in the Pioneer unit correctly--Systems
Programs shows my setup properly but NT seems to give each disc slot in
the unit a separate SCSI ID as opposed to a logical unit number "under"
a device ID. This in turn pushes some devices "out of the picture" on a
fully loaded adapter. Fortunately I have an AHA-1640 that seems to
solve the problem nicely...the only downside is having four SCSI
adapters in one system (two Cheetahs, one Spock and the 1640.)
William
David L. Beem
>> I'll bet the next question is going to be "can you list all the chip
>> revisions etc.". I can just feel that pregnant pause ticking away.
> Not from me at least. :-) I don't have a Type 4-P66 complex
> any longer. I've never even seen the 133MHz Pentium overdrive
I have 'P's & 'Q's (just different by clocking) to test. Never got to
the point of grabbing a Socket 4 120/133POD off of eBay I think, but I can.
It should just be one version (a particular S-spec) for the CPU, which is
fine to list the other component (cache controller) too.
David
Da...@IBMMuseum.com
b_pa...@ccad.uiowa.edu
<SNIP>
> Those are nice drives. I didn't know there was an 18-disc
> version...will have to look for that one. The DRM-624X is very common
> around these parts. A lot of them came with some early type of
> electronic card catalog system and these are now being phased out.
> Oftentimes I get the drives for nothing other than the time to haul
> them away. Sad thing is that the NT 4.0 "Spock" driver seems too buggy
> to handle the mutiple discs in the Pioneer unit correctly--Systems
> Programs shows my setup properly but NT seems to give each disc slot in
> the unit a separate SCSI ID as opposed to a logical unit number "under"
> a device ID. This in turn pushes some devices "out of the picture" on a
> fully loaded adapter.
CMIIW but isn't there an updated .inf file for the 624 that corrects
that problem??
Maybe a special ASPI driver as well?
Or both?
It's been some time since I used my 624 with my NT 4.0 9595, but I
recall having that problem and having to download a couple files to fix
it.
I was using a later model Spock w/ cache in that box at that time.
Brad
Louis Ohland
William R. Walsh
> CMIIW
?
> but isn't there an updated .inf file for the 624 that corrects
> that problem??
The only drivers I ever knew of from Pioneer corrected an issue where
95/NT's Explorer would repeatedly seek through all the drives and lock up
until each one had been queried.
There might have been something on the CD audio front as well...but if there
was I never used it.
> I was using a later model Spock w/ cache in that box at that time.
Mine was a red termpack, "Card 3" variant with the 1993 ROM on it. Apart
from the red termpack it looked to be a very late model card. I used 2MB
cache. The card worked well to drive an IBM DDS-2, Panasonic 8X CD-R drive,
the IBM-provided slimline CD-ROM drive and the Pioneer changer, though NT's
driver couldn't seem to handle all of this on one adapter.
William
Louis Ohland
12902 Cache Error on IBM* ValuePoint Computers
http://support.intel.com/support/processors/overdrive/sb/CS-012623.htm
Symptom
12902 cache error is received on IBM* ValuePoint computers after
Pentium® OverDrive® Processor is installed.
Description
Internal cache needs to be reset.
> It threw the odd "1047000 221" error (cache/memory-related?)
--
Reply to ohl...@charter.net
Louis Ohland
0104 72XX
ESDI Controller wrap error
> > It threw the odd "1047000 221" error (cache/memory-related?)
>
> --
> Reply to ohl...@charter.net
--
Reply to ohl...@charter.net
Tim Clarke
Nope, an "n129 nnnn" I would have recognised, but is displayed as 0129 nnnn
on a Model 95.
The 221 qualifier looks like the 200-series memory type codes but I can't
find 1047 anywhere obvious.
Tim Clarke
> 0104 72XX
> ESDI Controller wrap error
>
> > > It threw the odd "1047000 221" error (cache/memory-related?)
Now you're ADDING a "0" in front of the PRECISE error code given. Stop
mucking about and find "1047000 221" for me, if you can.
David L. Beem
> ...Stop mucking about and find "1047000 221" for me, if you can.
You used a PS/2 keyboard ('M') where I wanted you to use an original AT
keyboard ('F') in this response to Louis... ;-)
David
Da...@IBMMuseum.com
Louis Ohland
I tried looking for a 1047, and the esdi thing was the closest.
Tim, you can choose betwixt a 000104XX or a 010472XX. Choose wisely.
0104 70XX / 0104 71XX 1. Run Advanced Diagnostics
0104 72XX
ESDI Controller wrap error
0001 02XX 1. System Board
0001 03XX 2. Processor Board
0001 04XX
0001 07XX
--
Reply to ohl...@charter.net
Louis Ohland
P133, or as close as you might get. Is the error code tucked away in the
stored error codes?
Has it gone away? In that case, it may be an artifact, where the system
knows that something is different, but what it is, it doesn't know...
> > This may not be the same Overdrive, yet it sounds similar.
> > 12902 cache error is received on IBM* ValuePoint computers after Pentium® OverDrive® Processor is installed.
> Description Internal cache needs to be reset.
--
Reply to ohl...@charter.net
William R. Walsh
> Now you're ADDING a "0" in front of the PRECISE error code given. Stop
> mucking about and find "1047000 221" for me, if you can.
"221" claims to be a ROM to RAM parity error...almost definitely cache or
memory related. Perhaps the copy of ROM that is cached in RAM got screwed
up. That's what I take "ROM to RAM" to mean...
William
Tim Clarke
> Tim, aren't zeros sometimes not shown?
>
> I tried looking for a 1047, and the esdi thing was the closest.
>
> Tim, you can choose betwixt a 000104XX or a 010472XX. Choose wisely.
>
> 0104 70XX / 0104 71XX 1. Run Advanced Diagnostics
> 0104 72XX
> ESDI Controller wrap error
>
> 0001 02XX 1. System Board
> 0001 03XX 2. Processor Board
> 0001 04XX
> 0001 07XX
Yes, on some systems, and depending upon whether you're looking at a System
Log entry or the POS/BIOS display of the code the code may be shown in a
nasty "abbreviated" form, leading to difficulty in interpretation and
discussion. You should know that I'm experienced enough to (ordinarily) NOT
mis-communicate critical problem determination information, however, typing
mistooks aside (the keyboard on this ThinkPad 760ED is on its last legs, or
wants a serious dishwasher cycle).
I couldn't find any clue to the "error locus" indicated by the 1047 prefix
anywhere either, and since it's gone I no longer care that much. I just
wanted to be complete in my post as to what to expect.
Dan O
OTTOMH ISTR a 'Q' complex sans CPU, and a couple of 'Y' wall-hangers
amongst my inventory. Hmmm...
Tim Clarke
news:LDeIe.9202$hc4....@newsfe6-win.ntli.net...
> <SNIP>
>
> It threw the odd "1047000 221" error...
I think I've found what this is related to:
1047 16-Bit AT Fast SCSI adapter (i.e. any Future Domain Chipset-based
adapter, IMHO) as there's one in the system in question. Also, the error has
started again, but has not effect on operation, so it's an *ignore*
side-effect.
Nicopoy
> >
> > It threw the odd "1047000 221" error...
>
> I think I've found what this is related to:
>
> 1047 16-Bit AT Fast SCSI adapter (i.e. any Future Domain Chipset-based
> adapter, IMHO) as there's one in the system in question. Also, the error has
> started again, but has not effect on operation, so it's an *ignore*
> side-effect.
Yes, that's it. IIRC, you get the error when there are no devices
connected to the FD adapter. And as you said, this doesn't prevent the
computer from booting, so it doesn't matter.
If I hadn't been on holiday on 4th August, I'd have answered sooner...
Nicolas
WBSTClarke
I typo-ed the incorrect Intel cache controller part, it's the Intel A82497-60 or -66, but I've only ever tried with the faster rated chips. My Type-4 P60 'P' complex is late enough to have -66 cache RAM chips etc., but I'm not sure if this is a relevant factor, I would doubt that, as most production chips are tolerant of +10% overclocking.
More details when I can find the time for more extensive testing and interpretation of the results.
Cheers,
WBST