4.0Ghz P4 now officially cancelled

Page 5 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message news:a73fn0lfma9j4nfkvpkpmklvknmq4b4u1s@4ax.com...
> On Wed, 20 Oct 2004 19:56:33 GMT, "AJ" <ng@newsgroups.net> wrote:
>
>>
>>"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message
>>news:2ri8n0t5ol1naldood6ev0ddlqovdo9bk4@4ax.com...
>>> On Mon, 18 Oct 2004 19:30:03 GMT, "AJ" <ng@newsgroups.net> wrote:
>
>>>>The 3 motherboard temp sensors on my PC as I type this are 28, 26, 26 C.
>>>>(I plan on slowing down or replacing my case fans though. They are 92 mm
>>>>Zalmans that have the resistor inline causing them to turn at 1600 rpm, but
>>>>I can still hear them so I'm going to try to find even slower fans, perhaps
>>>>PWM ones and a controller). That's why I like Northwoods over Prescotts:
>>>>I can get much closer to silent computing.
>>>
>>> I think you're placing far too much faith in temp readings from your mbrd's
>>> BIOS.
>>
>>Why? I'm not doing a scientific comparison for a magazine.
>
> You're quoting temperature numbers as though they are actually accurate
> temperature readings - they're *not*.

No I wasn't. If you need more info on why mine runs at 28 C, my system specs
for example, fine. Of course there's a lot of variables. But the numbers pull off
of say Intel Active Monitor and the numbers someone else pulls off of Intel
Active Monitor with the same components, are going to be relatively comparable.

If someone says their P4C runs at 38 C at idle and I say mine runs at 28 C, then
it begs the question what is different between the systems. I don't reject those
relative numbers just because they weren't measured with a highly accurate
thermocouple and data acquisition equipment in a controlled environment. It's
not necessary and the info IS useful. That starts the dialog and further info is
gathered as need (what's the ambient temp.. etc).

And just FYI, my system is running at 28 C right now (as taken from Active
Monitor). If you wanted further qualification of where that number came from
originally, all you had to do is ask me. If you don't ask, then I'll assume
you were fine with the limited info.

>
>>> The mbrd mfrs can calibrate them to read anything you want
>>
>>They seem to be consistent across different boards.
>
> They're not necessarily so - they can vary across different BIOS versions.

So what? If you need that info, you'll get it upon further investigation and ask for
it. Some things can be assumed or derived you know: like I just built MY system,
so it's probably got a fairly recent BIOS. Every unlikely detail is not likely to be
encountered all of the time. No one was trying to make an absolutely irrefutable
statement. Take it with a grain of salt and not so absolutely literally. If you need
more info, ask for it.

>
>>>- there
>>> have been several cases where they have responded to user concerns of high
>>> reported CPU temps by lowering them, in a later BIOS, to the point they
>>> read lower than the mbrd "system temp".
>>
>>As long as they are measured the same way, it's fine. The readings are
>>hardly useless. Quite useful actually.
>
> I did *not* say they are useless... I hope you're not suggesting such!

I thought you were trying make such or similar a point. Mine was that most
times you don't need to be so diligent/scientific to arrive at conclusion from
info/data even if it is "fuzzy" info/data.

>
>>> The fact is that such readings are not useful as an absolute measure of
>>> temperature - the only use they really have is for detecting changes in
>>> general system/CPU thermal behavior.
>>
>>I think most people report those readings here though. Most people don't
>>have scientifically thermocoupled systems! The relative readings were
>>relevant for this thread (pretty much measured the same way and are
>>probably fairly consistent from board to board. I've built a few (5) of them
>>and they all turn out the same (except for the +10C Prescott).
>
> As I said, they are useful as relative changes for any given mbrd+CPU... to
> detect, e.g., loss of cooling efficiency or a failing fan... for that
> system.

Well as long as you mean for any same PN and not just any given standalone
system. If you and me buy the same model Dell PC configured the same, the
temps are gonna read pretty much the same in the same conditions. Unless
something is different. It's not like there's a 5 or 10 degree reporting difference.
When a 10 degree idle difference between systems has been noted, then one
can investigate further if there is cause for concern or if they wanna do anything
about it. It goes without saying that there are a number of variables, but I know
relative accuracy is not one of them (based upon the ones I just built. And I
know I just didn't get lucky with the consistency of parts over the last few months
in that they all operate pretty much the same). (The Dell example is of course
one of the special cases because they use their own proprietary cooling. They
run hot to keep fan noise down in at least some of their systems. They accept
that trade off.)

Even outside of specific PNs and brands, one could use one's own judgement
with a little bit of fact gathering and determine with good probability of correct
analysis. I've seen many sources give the 30-ish C number for the 2.X GHz P4Cs.
And I have no reason to doubt it. Similarly, I can count on a Prescott being almost
10 C hotter (40-ish). Just loosely given numbers meant to be taken as useful where
appropriate.

AJ
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

"keith" <krw@att.bizzzz> wrote in message news😛an.2004.10.21.02.18.23.406018@att.bizzzz...
> On Wed, 20 Oct 2004 19:56:33 +0000, AJ wrote:
>
>>
>> "Bruce Mckown" <no@email.here> wrote in message news:ds7bn0p8hbmtf7qpli2iupt4qnvc8leaen@4ax.com...
>>> On Mon, 18 Oct 2004 19:35:06 -0400, George Macdonald
>>> <fammacd=!SPAM^nothanks@tellurian.com> wrote:
>>>
>>>
>>>>I think you're placing far too much faith in temp readings from your mbrd's
>>>>BIOS. The mbrd mfrs can calibrate them to read anything you want - there
>>>>have been several cases where they have responded to user concerns of high
>>>>reported CPU temps by lowering them, in a later BIOS, to the point they
>>>>read lower than the mbrd "system temp".
>>>>
>>>>The fact is that such readings are not useful as an absolute measure of
>>>>temperature - the only use they really have is for detecting changes in
>>>>general system/CPU thermal behavior.
>>>>
>>>>Rgds, George Macdonald
>>>
>>> Yea, I read a test report on one website where they attached their own
>>> thermistor and compared Abit IC7 to an Asus mb (can't remember model)
>>> and the Abit mb always read higher and the Asus always read lower.
>>
>> I think a lot of you are trying to be too scientific
>
> Oh, now *THAT'S* a serious fault! Science means nothing? Good grief
> Gert!

You just don't get it! Why do you manipulate everything toward your goal
of being on the rampage and personal attack?

>
>> and missing the point of
>> the value of the *relative* readings and that some level of comparison
>> can be done with those and the info is still useful.
>
> Relative to *what*, exactly?

Comparable systems of various origins. Like saying my my Mercedes gets
29 MPG on the highway. It has validity. If someone said they only get 21 MPG
with their's, that MAY be a reason to take some kind of action. It's not like the
the performance variance amongst the same model parts (CPUs) is so high that
the info isn't useful. Indeed it is useful, and that's why Intel ships Active Monitor
with their boards: because it has relevance.

So try to keep things in perspective and in the context in which they were
presented instead of trying to make everything fit your paradigms. And try
not to be so volatile.

AJ
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

Bruce Mckown wrote:
> On Thu, 21 Oct 2004 22:35:12 -0400, keith <krw@att.bizzzz> wrote:
>
>
>> Sure, given that we have something upwards of a decade of interaction
>> with Mr. Hill, I'd have to agree. ...even though he is Canuckistani.
>> ;-)
>
> If Mr. Hill is so trusted in here then one would think he would use
> the latest drivers, drivers that completely destoy his brand of
> hogwash.

You must have some comprehension problem. Tony did say that the latest
drivers /didn't/ work on his system. That means he tried them and backed out
of them.

Look, you're going to have to accept that your own experiences aren't
necessarily the only way things can be. Hardware and software interactions
are complex enough that something that works out for one person may not work
on somebody else's system.

As for running the latest of something, that's usually a good recipe for
system instability. A lot of us in these newsgroups have been around since
PC's were first invented, in the early 80's. Some of us are even older than
that and have been using computers since before PC's were invented as a
product or even as a category. I used to be like you at one time, always
searched out and installed the latest of everything, whether I needed it or
not. Then I'd wonder why all of a sudden my previously stable system is now
crashing. After a few bad incidences, you quickly learn that upgrading is
something you should do only with the utmost care. So when everybody else
goes around getting excited that the latest version of something is coming
out, I get into the "ohmygod, is another upgrade coming soon?" mode. I
upgraded to Windows 2000 in 2002, a full two years after it was first
introduced. And I just upgraded to Windows XP this year, a full three years
after that one was introduced. And I waited a month and half before
installing SP2 on XP. For me, I have to wait and listen for problems before
I will bother to upgrade.

Yousuf Khan
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

In comp.sys.ibm.pc.hardware.chips AJ <ng@newsgroups.net> wrote:
> I have better things to do (like USING my computer)
> rather than worring about techinical details that simply
> don't matter to me. I don't want to deal with more vendors
> unnecessarily (KISS principle). Almost any current computer
> would be adequate for what I do with it.

A perfectly reasonable approach. But why then waste any time
here arguing about it? At least in csiphc, we _love_ looking
at low-level details, and you can hardly expect us to accept
_any_ undetailed look at things.

-- Robert
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

"Bruce Mckown" <no@email.here> wrote in message
news:h83gn05v0b65mvuqho74trm304akc2gd2m@4ax.com...
> On Wed, 20 Oct 2004 19:57:30 -0400, George Macdonald
> <fammacd=!SPAM^nothanks@tellurian.com> wrote:
>
>>Tony's experiences do
>>not inspire confidence in them.
>>
>>Rgds, George Macdonald
>
> As I said, Tony is FOS. I tested this supposed 100% cpu usage when
> moving the mouse and on my system it never went above 7%. Do some
> homework, the truth is out there, and Tony ain't God.

I have a ATI 9800 pro and I tried opening windows and resizing them
maximizing them and the highest cpu usage was 14%. The average was 8% to
12%. I am using the newest 4.10 drivers just released this week.

toony must be an nvidiot to have that much trouble with his ati card.
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

In comp.sys.ibm.pc.hardware.chips Bruce Mckown <no@email.here> wrote:
> On Thu, 21 Oct 2004 20:38:53 GMT, Robert Redelmeier
>>No one said he is. But personally, I find him more
>>believeable than you. By a long shot.

> More the fool you then.

Thank you for demonstrating my point.

-- Robert
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Thu, 21 Oct 2004 22:10:23 -0400, "Yousuf Khan" <bbbl67@ezrs.com> wrote:

>George Macdonald wrote:
>> Well no, I was just asking about specific differences which would,
>> e.g., make common code in OS & driver writing or compiler code
>> generation err, difficult. It had been my impression so far that
>> this would not be the case. E.g. though the 36-bit limitation is a
>> difference, it is not a significant one in terms of addressable
>> physical memory within the next few years, IMO.
>
>No, I don't think there's all that much difference that a few minor
>if...then statements can't take care of. Now that is if we're assuming that
>the Intel parts are acting exactly as their own documentation suggests that
>they will work.
>
>As for the 36-bit limitation, that's not any kind of instruction set problem
>either. That's just a processor external feature. It's no different than in
>the olden days when we had 386SX and 386DX, with the SX supporting only upto
>24-bit physical memory, while the DX did the full 32-bits. The OS simply
>polled the appropriate memory-size parameters found out how much physical
>memory was actually installed on each machine and used whatever amount was
>reported back.

Well of course it's not an ISA issue. If M$ and other OS mfrs had thought
to use it as a processor ID artifice though and Intel "corrects" it to
36-bits instead of 40, then things could get messy... especially if Intel
markets the EM64T into the i915/925 chipset space which brings things to a
36-bit CPU masquerading as a 40-bit CPU but in fact it only really has 32
address lines available for use.

The 32-bit DMA thing would appear to be really the most bothersome... and I
suspect has something to do with the delays in WinXP-64. Given the way
WinXX uses its swapfile, double buffering could be a real PITA.

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 01:07:17 -0700, Bruce Mckown <no@email.here> wrote:

>On Thu, 21 Oct 2004 17:32:58 -0400, George Macdonald
><fammacd=!SPAM^nothanks@tellurian.com> wrote:
>
>
>>
>>In at least one of the NGs crossposted to, Tony has established credibility
>>- you don't... remarks like FOS do not enhance your err, reputation.<shrug>
>
>What credibility? The man was using agent drivers.

"Agent drivers" you say?? Is that a secret code word/term for ATi experts?

> You consider that
>credibility? You lot are a bit dim and it's a good thing I don't waste
>too much time with this news group.

Just go away then. A smart move, given that the conversation appears to
have exceeded your perceptual capabilities.

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 04:19:06 GMT, "AJ" <ng@newsgroups.net> wrote:

>
>"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message news:a73fn0lfma9j4nfkvpkpmklvknmq4b4u1s@4ax.com...
>> On Wed, 20 Oct 2004 19:56:33 GMT, "AJ" <ng@newsgroups.net> wrote:
>>
>>>
>>>"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message
>>>news:2ri8n0t5ol1naldood6ev0ddlqovdo9bk4@4ax.com...
>>>> On Mon, 18 Oct 2004 19:30:03 GMT, "AJ" <ng@newsgroups.net> wrote:
>>
>>>>>The 3 motherboard temp sensors on my PC as I type this are 28, 26, 26 C.
>>>>>(I plan on slowing down or replacing my case fans though. They are 92 mm
>>>>>Zalmans that have the resistor inline causing them to turn at 1600 rpm, but
>>>>>I can still hear them so I'm going to try to find even slower fans, perhaps
>>>>>PWM ones and a controller). That's why I like Northwoods over Prescotts:
>>>>>I can get much closer to silent computing.
>>>>
>>>> I think you're placing far too much faith in temp readings from your mbrd's
>>>> BIOS.
>>>
>>>Why? I'm not doing a scientific comparison for a magazine.
>>
>> You're quoting temperature numbers as though they are actually accurate
>> temperature readings - they're *not*.
>
>No I wasn't. If you need more info on why mine runs at 28 C, my system specs
>for example, fine. Of course there's a lot of variables. But the numbers pull off
>of say Intel Active Monitor and the numbers someone else pulls off of Intel
>Active Monitor with the same components, are going to be relatively comparable.
>
>If someone says their P4C runs at 38 C at idle and I say mine runs at 28 C, then
>it begs the question what is different between the systems. I don't reject those
>relative numbers just because they weren't measured with a highly accurate
>thermocouple and data acquisition equipment in a controlled environment. It's
>not necessary and the info IS useful. That starts the dialog and further info is
>gathered as need (what's the ambient temp.. etc).

There're just too many things which *could* be different to be worrying
about actual readings.

>And just FYI, my system is running at 28 C right now (as taken from Active
>Monitor). If you wanted further qualification of where that number came from
>originally, all you had to do is ask me. If you don't ask, then I'll assume
>you were fine with the limited info.

The fact is neither you nor I knows much about where that number came from,
nor how meaningful it is as a measure of potential CPU thermal distress.
The only indication I get from it is that you might be living in a bloody
igloo... or that Intel or whoever made your mbrd would rather that you do
*not* pester them with "worried" Qs.

>>>I think most people report those readings here though. Most people don't
>>>have scientifically thermocoupled systems! The relative readings were
>>>relevant for this thread (pretty much measured the same way and are
>>>probably fairly consistent from board to board. I've built a few (5) of them
>>>and they all turn out the same (except for the +10C Prescott).
>>
>> As I said, they are useful as relative changes for any given mbrd+CPU... to
>> detect, e.g., loss of cooling efficiency or a failing fan... for that
>> system.
>
>Well as long as you mean for any same PN and not just any given standalone
>system. If you and me buy the same model Dell PC configured the same, the
>temps are gonna read pretty much the same in the same conditions. Unless
>something is different. It's not like there's a 5 or 10 degree reporting difference.
>When a 10 degree idle difference between systems has been noted, then one
>can investigate further if there is cause for concern or if they wanna do anything
>about it. It goes without saying that there are a number of variables, but I know
>relative accuracy is not one of them (based upon the ones I just built. And I
>know I just didn't get lucky with the consistency of parts over the last few months
>in that they all operate pretty much the same). (The Dell example is of course
>one of the special cases because they use their own proprietary cooling. They
>run hot to keep fan noise down in at least some of their systems. They accept
>that trade off.)
>
>Even outside of specific PNs and brands, one could use one's own judgement
>with a little bit of fact gathering and determine with good probability of correct
>analysis. I've seen many sources give the 30-ish C number for the 2.X GHz P4Cs.
>And I have no reason to doubt it. Similarly, I can count on a Prescott being almost
>10 C hotter (40-ish). Just loosely given numbers meant to be taken as useful where
>appropriate.

I have a PIII/500 here which has been reporting 58-65C temps for 5 years -
it's fine... I don't care... it's err, normal!!

How about starting a new NG on this?... along the lines
alt.cpu.temps.worryworts?

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 02:44:01 +0000, Robert Redelmeier wrote:

> In comp.sys.ibm.pc.hardware.chips keith <krw@att.bizzzz> wrote:
>> Sure, given that we have something upwards of a decade
>> of interaction with Mr. Hill, I'd have to agree. ...even
>> though he is Canuckistani. ;-)
>
> Better the Devil you know ? :)

Sure, but particularly when the little devil's experiences correlate well
with mine.

> Look carefully -- he may live further South than you!

Oh, my! That fact was decided here some years ago (pre Canuckistan),
when I made some comments about visiting "down" there (much to his
amazement). Mr. H does indeed live well below my latitude, as do
the upwards of 80% of Canuckistanis. ;-)

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 01:04:34 -0700, Bruce Mckown wrote:

> On Thu, 21 Oct 2004 22:35:12 -0400, keith <krw@att.bizzzz> wrote:
>
>
>>Sure, given that we have something upwards of a decade of interaction
>>with Mr. Hill, I'd have to agree. ...even though he is Canuckistani. ;-)
>
> If Mr. Hill is so trusted in here then one would think he would use
> the latest drivers, drivers that completely destoy his brand of
> hogwash.

Smart people don't walk into strange places with guns blazing either.
Those of us that have been 'round a while certainly trust Mr. Hill's
"hogwash", before the newb who can't keep a civil tongue.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 18:50:34 -0400, George Macdonald wrote:

> On Fri, 22 Oct 2004 01:07:17 -0700, Bruce Mckown <no@email.here> wrote:
>
>>On Thu, 21 Oct 2004 17:32:58 -0400, George Macdonald
>><fammacd=!SPAM^nothanks@tellurian.com> wrote:
>>
>>
>>>
>>>In at least one of the NGs crossposted to, Tony has established credibility
>>>- you don't... remarks like FOS do not enhance your err, reputation.<shrug>
>>
>>What credibility? The man was using agent drivers.
>
> "Agent drivers" you say?? Is that a secret code word/term for ATi experts?

George, George, george... I use some heavy Gravity drivers on my Win2K
systems, and Pan my Linux. Agent is fairly good, but it is ancient. ;-)

>> You consider that
>>credibility? You lot are a bit dim and it's a good thing I don't waste
>>too much time with this news group.
>
> Just go away then. A smart move, given that the conversation appears to
> have exceeded your perceptual capabilities.

Appears? Truth be told, if he weren't such a little prick, I'd appreciate
an education here. I don't know graphics cards for squat these days, not
that my needs would match his.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Thu, 21 Oct 2004 23:17:04 -0400, Carlo Razzeto wrote:

>
> "keith" <krw@att.bizzzz> wrote in message
> news😛an.2004.10.22.02.42.45.161604@att.bizzzz...
>> On Thu, 21 Oct 2004 22:10:23 -0400, Yousuf Khan wrote:
>>
>> Again, I have no first-hand information here, but it's my understanding
>> that Intel only supports a 36b hardware address, (xeon compatability), but
>> *reports* a full AMD64 (K8) 40b space. This screws the OS.
>>
>> --
>> Keith
>>
>>
>
> This is what I heard, in which case I guess the only fix would be to find
> out if the chip is Intel or AMD and switch the address size based on that.
> That would be a really ugly hack, but what else can you do if your CPU isn't
> going to play nice and tell you how big it's address space really is?

Sure, that's possible. Then you're left testing every possible stepping
to find when they've corrected the problem. There is good reason why
such things are reported by the hardware, and not just model/stepping.

Given the past few years I was speculating that Intel had lost their
collective minds. Over the past few weeks, I've become *sure* of it. AMD
is leading them by the nose, and I do believe people are starting to
notice.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 03:31:29 -0400, Yousuf Khan wrote:

> keith wrote:
>>> As for the 36-bit limitation, that's not any kind of instruction set
>>> problem either. That's just a processor external feature. It's no
>>> different than in the olden days when we had 386SX and 386DX, with
>>> the SX supporting only upto 24-bit physical memory, while the DX did
>>> the full 32-bits. The OS simply polled the appropriate memory-size
>>> parameters found out how much physical memory was actually installed
>>> on each machine and used whatever amount was reported back.
>>
>> Again, I have no first-hand information here, but it's my
>> understanding that Intel only supports a 36b hardware address, (xeon
>> compatability), but *reports* a full AMD64 (K8) 40b space. This
>> screws the OS.
>
> Yeah, reporting 40-bits when you should only report 36-bits *is* a bug. But
> it's a bug that I can only assume is easily correctible with a microcode
> update. Besides, even if the processor reports 40-bits are addressable, the
> OS works only with what is /actually installed/. Most systems would probably
> only come with 36-bits of addressable memory installed.

I'm no OS type, but it's my understanding that it's far worse than not
just not beiong able to "fully" populate the memory space. From what I've
read it totally confuses the OS, even with less than 36b physical memory.
People also don't believe you need 64b addressing until you go above
4GB physical.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 02:43:48 +0000, AJ wrote:

>
> "George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message news:0uudn010fpt7imulqbkg7354t7et32if69@4ax.com...
>> On Wed, 20 Oct 2004 19:26:05 GMT, "AJ" <ng@newsgroups.net> wrote:
>>
>>>
>>>"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message
>>>news:fkh8n0p69hjrjvohh8tcjgpt70me4s53nj@4ax.com...
>>>> On Mon, 18 Oct 2004 19:05:50 GMT, "AJ" <ng@newsgroups.net> wrote:
>>
>>>> There is nothing about an AMD system which is frightening - maybe you
>>>> should try it. As for Intel mbrds, there's no such thing any longer on the
>>>> desktop... sub-contracted for even workstation class. From experience,
>>>> your "compelling" solution buys you nothing really: with a recent chipset
>>>> from any vendor, including Intel, you're going to have driver .INF files to
>>>> load for Windows of any flavor or vintage.
>>>>
>>>> Hmm, you spout this religious dogma and then accuse people who suggest AMD
>>>> of being zealots???õ_õ
>>>
>>>See, you're an AMD zealot because you (like that keith ranter) are trying to
>>>pursuade me to try/buy AMD. All I did was tell you why I'm currently using
>>>Intel and you both go off in a huff and try to impose your own personalities
>>>on me. I don't give a sh@! what you use. I'm not trying to convince anyone,
>>>but you zealots are. Get a grip and see yourselves!
>>
>> I dunno what it is with you iZombies - you miss what is being said and
>> twist what people say to find non existent accusations and quarrels; you
>> find anything non-Intel "frightening"; and you don't even have a clue about
>> the origin of the parts you are buying... and so conjure up reasons for
>> buying them.
>>
>> No, I know you are beyond persuading and when I said "maybe you should try
>> it", what I was suggesting is that you have never in fact tried it and
>> therefore have no reason for your irrational prejudices. I, OTOH, have
>> tried both and make my *choice* accordingly - I came close to doing a P4
>> system with Northwood, just so I'd have a direct, personal comparison, but
>> no way will I be tempted to Prescott.
>>
>> To tell the truth, I don't give a wet fart what CPU, mbrd or whatever that
>> *you* use but when you stick your head in the sand and spout your spurious
>> dogma, people here will correct you. We'd hate for some poor lurker to get
>> the impression that you actually know anything.
>>
>> Rgds, George Macdonald
>>
>> "Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
>
> Trying to turn the table huh. Sad. Why bother spouting YOUR AMD DOGMA in an
> Intel group anyway?

What sniveling whiner you are! Take a look at the "newsgroups" list.
You're also posting to comp.sys.ibm.pc.hardware.chips. If you don't want
to learn anythign, why don't you just jack-off in the corner. No one will
bother you, promise!

> I'm just here trying to get info about the products I use and NOT
> to get caught in your silly games. Just drop it already, seesh.

If you don't like the heat, then get out of the Usenet! ...or try to be a
little less obnoxious.

To quote .chips' mascot, "what a maroon!".

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 04:19:05 +0000, AJ wrote:

>
> "keith" <krw@att.bizzzz> wrote in message news😛an.2004.10.21.02.16.40.204336@att.bizzzz...
>> On Wed, 20 Oct 2004 19:41:56 +0000, AJ wrote:
>>
>>>
>>> "Tony Hill" <hilla_nospam_20@yahoo.ca> wrote in message news😱ol8n01joe7ibirjoebnfcajo61o9dufor@4ax.com...
>>>> On Mon, 18 Oct 2004 19:05:50 GMT, "AJ" <ng@newsgroups.net> wrote:
>>>>> So now I know Intel and have no reason
>>>>>to look elsewhere. If I was considering building an AMD system, I wouldn't
>>>>>look at any other vendor for a motherboard than ASUS though. As far as I'm
>>>>>concerned, AMD+ASUS is the platform there and there's no need to
>>>>>evaluate the also-rans. Intel solution: CPU, chipset, motherboard by one
>>>>>vendor. AMD solution: CPU, chipset, motherboard by two or three vendors.
>>>>>The former is compelling. The latter is frightening. (It works for me!).
>>>>
>>>
>>>> I've used both, and honestly the difference is pretty much nil.
>>>
>>> That statement has no value if you're trying to convince someone/anyone,
>>> realize. (I've used both too).
>>
>> Gee, AJ. Wanna pissss offf any more of the knowledgeable in the group
>> with your asinine comments. Hint: Tony's been around the block a few
>> times. You *might* try learning, rather than bing a little prick.
>
> Oh I'm so sorry I didn't realize that he was one of your gods (you little prick).

Gods? Hardly, rather a well known net-friend. ...and one that has more
credibility with people he's never met than you will ever have with your
mommy.

> I'll make sure I bow next time (lol, not). You obviously think he needs you
> to protect him, funny.

Tony? ...need me? Maybe at one time... ;-))

>>>> About
>>>> the only bet is that you've got one number to call if a part dies
>>>> instead of two, but I've never actually had a CPU die on me, and I know
>>>> from my work that CPUs only die at a rate of about 1 for every 100
>>>> motherboards that blow (interesting bit of trivia, roughly 95% of all
>>>> CPUs that are returned as defective are 100% functional), so this isn't
>>>> really a big worry. Otherwise you've got one set of drivers to load
>>>> and that's about it.
>>>
>>> I look at the MB/CPU (and chipset of course) as a unit. I wouldn't care
>>> if the CPU was soldered on the board (it would probably cheaper).
>>
>> ...which shows that you haven't a *clue* about the PC market. What a
>> maroon!
>
> Kids! Can you even write one little sentence without personal attack in it?

Kid? Well, I just turned "34" last month. ;-) I have been around for a
while though.

>>> I've never used a CPU from one system in another (I don't think most
>>> stand alone system users have/would/do, though the techies here probably
>>> do). Removability/replaceability is a good paradigm for video cards, but
>>> for a CPU the cost/benefit is probably not worth it (?).
>>
>> Again, you haven't a clue what you're talking about. The PC market
>> *demands* socketed motherboards, and not because of replacements. Think
>> about it. If you need a further clue, perhaps one of the nice people here
>> will fill you in. Though I have no idea why they would bother.
>
> I'm putting you in your bin (the bozo bin). Bye! (Where do these creeps come
> from?!).

Look under your bed. We're idiots worst nightmares!

Maroon!

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 05:21:18 +0000, Robert Redelmeier wrote:

> In comp.sys.ibm.pc.hardware.chips AJ <ng@newsgroups.net> wrote:
>> I have better things to do (like USING my computer)
>> rather than worring about techinical details that simply
>> don't matter to me. I don't want to deal with more vendors
>> unnecessarily (KISS principle). Almost any current computer
>> would be adequate for what I do with it.
>
> A perfectly reasonable approach. But why then waste any time
> here arguing about it? At least in csiphc, we _love_ looking
> at low-level details, and you can hardly expect us to accept
> _any_ undetailed look at things.

Robert, he's only interested in people who agree with him (his complaint
that *this* was an "intel" group. It's amazing truely amazing how people
can think they can learn anything from those who belive exactly as
they do. <shrug>

....may he forever be happy in his own little world.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

"Robert Redelmeier" <redelm@ev1.net.invalid> wrote in message news:iN0ed.9244$Al3.8948@newssvr30.news.prodigy.com...
> In comp.sys.ibm.pc.hardware.chips AJ <ng@newsgroups.net> wrote:
>> I have better things to do (like USING my computer)
>> rather than worring about techinical details that simply
>> don't matter to me. I don't want to deal with more vendors
>> unnecessarily (KISS principle). Almost any current computer
>> would be adequate for what I do with it.
>
> A perfectly reasonable approach. But why then waste any time
> here arguing about it? At least in csiphc, we _love_ looking
> at low-level details, and you can hardly expect us to accept
> _any_ undetailed look at things.

Of course. But the apparent current "argument" is really about the
comparison details of the multitude of other things (AMD system
parts and there details) and moreso the constant response by some:
"just buy an AMD blah blah...". What relevance does that have in
comp.sys.intel? Shouldn't that be in alt.flame.wars? IOTW, I already
have an Intel system so I come here to stay up on the issues with
and info about these systems. Is it necessary to weed through all
the irrelevant posts?

The "details" I was avoiding was knowing all the details of the other
vendors' technologies. If I already bought and own a Corvette (already
made my choice), and I go to a Corvette show to participate in that
user group, I wouldn't expect to find people promoting Mustangs there!

I may build some AMD systems again someday. But then I'd go to the
AMD room to get those details and not comp.sys.intel.

AJ
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

"George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message news:3dshn0li504qvopv4ba5qjsvvvqrqp40q7@4ax.com...
> How about starting a new NG on this?... along the lines
> alt.cpu.temps.worryworts?

No one is worried about it except you (and you just have other motive
anyway).

AJ
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Sat, 23 Oct 2004 02:18:01 +0000, AJ wrote:

>
> "George Macdonald" <fammacd=!SPAM^nothanks@tellurian.com> wrote in message news:3dshn0li504qvopv4ba5qjsvvvqrqp40q7@4ax.com...
>> How about starting a new NG on this?... along the lines
>> alt.cpu.temps.worryworts?
>
> No one is worried about it except you

You seem to be totally consumed by your ignorance here.

>(and you just have other motive anyway).

....and what "motives" would "that" be.

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

In comp.sys.ibm.pc.hardware.chips AJ <ng@newsgroups.net> wrote:
> "Robert Redelmeier" <redelm@ev1.net.invalid> wrote in message
> news:iN0ed.9244$Al3.8948@newssvr30.news.prodigy.com...
>> In comp.sys.ibm.pc.hardware.chips AJ <ng@newsgroups.net> wrote:
>>> I have better things to do (like USING my computer)
>>> rather than worring about techinical details that simply
>>> don't matter to me. I don't want to deal with more vendors
>>> unnecessarily (KISS principle). Almost any current computer
>>> would be adequate for what I do with it.
>>
>> A perfectly reasonable approach. But why then waste any time
>> here arguing about it? At least in csiphc, we _love_ looking
>> at low-level details, and you can hardly expect us to accept
>> _any_ undetailed look at things.

> response by some: "just buy an AMD blah blah...". What
> relevance does that have in comp.sys.intel? Shouldn't

Ah, you are posting from csi -- I didn't know earlier.
My quote lines show everyone I'm posting from csiphc.

Discussing the merits of AMD may well be unwelcome or OT in csi.
It is far otherwise in csiphc where personal value statements like
"I think Intel is more stable" are treated with derision unless
accompanied by detailed data.

Notice that articles are cross-posted, and learn how and when to
set the Followup-To: header.

> I may build some AMD systems again someday. But then I'd go
> to the AMD room to get those details and not comp.sys.intel.

Personally, I dislike the obvious partisanship of csi and the
various AMD groups. I prefer the open discussion in csiphc.

-- Robert
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

[FU2 set] In comp.sys.ibm.pc.hardware.chips keith <krw@att.bizzzz> wrote:
> Robert, he's only interested in people who agree with him
> (his complaint that *this* was an "intel" group. It's
> amazing truely amazing how people can think they can learn
> anything from those who belive exactly as they do. <shrug>

Well, yes.

Actually, I think AJs problem is different. He doesn't
realize he was cross-posting, let alone any idea about
Followups-To: Not that any of us should claim to be saints.
FU2 csiphc should have been set long ago.

> ...may he forever be happy in his own little world.

Well, perhaps. I always try to differentiate between ignorance
and stupidity. The former can be cured. Stupidity is forever.
"never attribute to malice that which incompetence explains." [Nap]

-- Robert
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 21:43:31 -0400, keith <krw@att.bizzzz> wrote:

>On Fri, 22 Oct 2004 18:50:34 -0400, George Macdonald wrote:
>
>> On Fri, 22 Oct 2004 01:07:17 -0700, Bruce Mckown <no@email.here> wrote:
>>
>>>On Thu, 21 Oct 2004 17:32:58 -0400, George Macdonald
>>><fammacd=!SPAM^nothanks@tellurian.com> wrote:
>>>
>>>
>>>>
>>>>In at least one of the NGs crossposted to, Tony has established credibility
>>>>- you don't... remarks like FOS do not enhance your err, reputation.<shrug>
>>>
>>>What credibility? The man was using agent drivers.
>>
>> "Agent drivers" you say?? Is that a secret code word/term for ATi experts?
>
>George, George, george... I use some heavy Gravity drivers on my Win2K
>systems, and Pan my Linux. Agent is fairly good, but it is ancient. ;-)

Ach, but I wanted *him* to look up the word himself. You've spoiled the
humiliation now and he'll claim it was his keyboard's fault... just like JC
did.;-)... Hey ya don't think... it might be......

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

On Fri, 22 Oct 2004 21:52:10 -0400, keith <krw@att.bizzzz> wrote:

>On Fri, 22 Oct 2004 03:31:29 -0400, Yousuf Khan wrote:
>
>> keith wrote:
>>>> As for the 36-bit limitation, that's not any kind of instruction set
>>>> problem either. That's just a processor external feature. It's no
>>>> different than in the olden days when we had 386SX and 386DX, with
>>>> the SX supporting only upto 24-bit physical memory, while the DX did
>>>> the full 32-bits. The OS simply polled the appropriate memory-size
>>>> parameters found out how much physical memory was actually installed
>>>> on each machine and used whatever amount was reported back.
>>>
>>> Again, I have no first-hand information here, but it's my
>>> understanding that Intel only supports a 36b hardware address, (xeon
>>> compatability), but *reports* a full AMD64 (K8) 40b space. This
>>> screws the OS.
>>
>> Yeah, reporting 40-bits when you should only report 36-bits *is* a bug. But
>> it's a bug that I can only assume is easily correctible with a microcode
>> update. Besides, even if the processor reports 40-bits are addressable, the
>> OS works only with what is /actually installed/. Most systems would probably
>> only come with 36-bits of addressable memory installed.
>
>I'm no OS type, but it's my understanding that it's far worse than not
>just not beiong able to "fully" populate the memory space. From what I've
>read it totally confuses the OS, even with less than 36b physical memory.
>People also don't believe you need 64b addressing until you go above
>4GB physical.

Surely it *could* cause problems with where to map the high reserved
address space - in 32-bit systems, the video memory and BIOS gets mapped to
just below the 4GB boundary.

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,comp.sys.intel (More info?)

"keith" <krw@att.bizzzz> wrote in message
news😛an.2004.10.23.01.34.19.337189@att.bizzzz...
> On Fri, 22 Oct 2004 02:44:01 +0000, Robert Redelmeier wrote:
>
> > Look carefully -- he may live further South than you!
>
> Oh, my! That fact was decided here some years ago (pre
Canuckistan),
> when I made some comments about visiting "down" there (much to his
> amazement). Mr. H does indeed live well below my latitude, as do
> the upwards of 80% of Canuckistanis. ;-)

Ahem. I recall the time I visited Detroit. Climbed into a boat, went
due _south_ to Windsor, Canuckistan. Yes, south. Check a map. So
there!

Felger Carbon
not longitudinally challenged
 
Status
Not open for further replies.