🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.comp.hardware.homebuilt
Article #391

Re: Bad Pc133 RAM?

#391
From: Rod Speed
Date: Thu, 04 Jan 2001 10:04
44 lines
3346 bytes
Guy Barwood - Dilithium Computing <dilithium@dilithium.com.au> wrote in
message news:4MU46.4940$l02.11018@news1.sunsh1.vic.optushome.com.au...
> Rod Speed <rod_speed@yahoo.com> wrote
>> Guy Barwood - Dilithium Computing <dilithium@dilithium.com.au> wrote

>>> We do not have enough info to say for certain that the Kingmax RAM is faulty.

>> Duh.

> So how can he then (in your words)

>     "Just force the original dealer to give your money back.
>     He legally has to do that when they clearly wont work
>     in that motherboard which obviously isn't defective when
>     the 64MB dimm from the other supplier works fine."

> You have just indicated that quite obviously
> (read "Duh") the RAM is not necessarily faulty.

It isnt yet clear just whats going on on that stuff.

> Later

> PS It is as simple as I said in respect to the banks/sides,

Wrong.

> as number of devices determines the number of banks (max 9 devices per bank).

Wrong again. And there are plenty of chipsets that dont have a limit of 4 banks too.

> Aside:
> Quote from Intel (note I was wrong on board max which is actually 512Mb):
> System Memory
> The D815EEA desktop board supports up to 512 MB of dynamic memory. The three
> 168-pin Dual Inline Memory Module (DIMM) sockets support 3.3V unbuffered 100
> MHz, or 133 MHz, Synchronous Dynamic Random Access Memory (SDRAM) DIMMs. If
> PC133 memory is going to be run at the full 133 MHz, only four of the six
> DIMM sides can be used (two double-sided DIMMs, or one double-sided DIMM
> plus two single-sided DIMMs).
> http://developer.intel.com/design/motherbd/ea/ea_mem.htm for more info

All completely and utterly irrelevant, it aint his motherboard.
Technical Details
Message-ID: <3a544a8d@news.iprimus.com.au>
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!newsfeed.online.be!sunqbc.risq.qc.ca!news.maxwell.syr.edu!intgwpad.nntp.telstra.net!news1.optus.net.au!optus!news0.optus.net.au!news.iprimus.com.au!203.134.92.116
References: <3a52273d@grissom> <3a525eaf$1@news.iprimus.com.au> <Nvt46.36195$1t.1905477@typhoon.ne.mediaone.net> <3a52762f@news.iprimus.com.au> <Z3F46.4916$l02.10938@news1.sunsh1.vic.optushome.com.au> <3a538d0e@news.iprimus.com.au> <4MU46.4940$l02.11018@news1.sunsh1.vic.optushome.com.au>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10d683,16a6ca033992abf1
X-Google-Attributes: gid10d683,public
X-Google-Thread: f70d1,16a6ca033992abf1
X-Google-Attributes: gidf70d1,public
X-Google-Thread: 10a2ed,16a6ca033992abf1
X-Google-Attributes: gid10a2ed,public
X-Google-ArrivalTime: 2001-01-04 02:11:04 PST
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!newsfeed.online.be!sunqbc.risq.qc.ca!news.maxwell.syr.edu!intgwpad.nntp.telstra.net!news1.optus.net.au!optus!news0.optus.net.au!news.iprimus.com.au!203.134.92.116
From: "Rod Speed" <rod_speed@yahoo.com>
Newsgroups: alt.comp.hardware.homebuilt,alt.comp.hardware.pc-homebuilt,aus.computers.ibm-pc
References: <3a52273d@grissom> <3a525eaf$1@news.iprimus.com.au> <Nvt46.36195$1t.1905477@typhoon.ne.mediaone.net> <3a52762f@news.iprimus.com.au> <Z3F46.4916$l02.10938@news1.sunsh1.vic.optushome.com.au> <3a538d0e@news.iprimus.com.au> <4MU46.4940$l02.11018@news1.sunsh1.vic.optushome.com.au>
Subject: Re: Bad Pc133 RAM?
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Original-NNTP-Posting-Host: 203.134.92.116
Message-ID: <3a544a8d@news.iprimus.com.au>
X-Original-Trace: 4 Jan 2001 21:03:57 +1100, 203.134.92.116
Date: Thu, 4 Jan 2001 21:04:04 +1100
NNTP-Posting-Host: 203.134.64.67
X-Trace: news0.optus.net.au 978602637 203.134.64.67 (Thu, 04 Jan 2001 21:03:57 EST)
NNTP-Posting-Date: Thu, 04 Jan 2001 21:03:57 EST
Organization: CWO Customer - reports relating to abuse should be sent to abuse@cwo.net.au