captainsniz
Distinguished
It's never personal...thanks for enlightening all of us with your superior wisdom...Thanks for not attacking me (LOL).
What flame? I joked using sarcasm. You flipped out. There was no flame. You're just too thin skinned to realize that. Which means you might as well leave then because if you take everything that everyone says here personally you're not going to last long at all.Explain to me and the rest on this forum how my comments warrented that flame???
Now you're really losing me. What dogma? I don't see any dogma here. You're in a world of your own on that one. Nor, for that matter, is there any pushing. Dude, you can only be pushed around if you let yourself be pushed. If you feel you're being pushed, then stand tall. Hell, push back. You still have yet to debate a single thing. You do know that debating is a two way process, right?At any rate, why would ANYONE want to stick around on a forum that forces their Dogma upon its members...Not exactly constructive dialog from my perspective.
Did I ever say that it wasn't personal? Serously. If you're going to stay here, then you're going to need to start standing up for yourself better than that. This isn't Fluffy Bunny Land where everyone shares lollipops and sunshine. Here people actually hold discourse. They throw things back and forth. Hard things. We don't hold your hand.Then the backbone thing...Please anyone can see who is making this an issue. And we should take that one also as NOT PERSONAL. Of course it was intended as personal.
1) It's only slander if it isn't true.I have not slandered you in any way, nor do I plan on going down to that level over something as silly as a USB / battery issue.
If I had that kind of cash, and it came with a great GPU as well, I sure as hell would buy it in a heartbeat. I could use a new computer.Since we mostly agree that we cannot point the finger to Intel or MS until the alternative OS tests are performed, lets turn this into an extension of the original question.
_____________________________________________________________
Would you spend your own cash and pay a premium right now (with our limited knowledge of the problem) on a Core Duo based solution? <OR> Would you wait a few days / weeks / months to see how the issue plays out?
slvr_phoenix, Do yourself a small favor. Unplug for a little while. Go socialize with some humans in person. Force some of your Dogma on them and see how they react to it, then slander them because they don't take you ideas as law. I can see you have much to learn about this world...grasshopper.
Damn straight. Opinions are like arseholes. Everyone has one. That's what makes THGC fun. We've been doing too much tech support lately. We've grown weak and flabby. There hasn't been a good flame war in ages. :lol: :lol: :lol:Silver's right, thats kinda how things go here. You don't take anything personally, everyone has their opinions and usually no one likes anyone elses.
Now that wouldn't surprise me. Intel has always enjoyed paper launches. Besides, Intel has been screwing up their supply lately. First northbridges, now this. :lol: It's not a year with Intel if they don't screw something up. At least they recall what they can't otherwise fix. It may be a nuicance some times, but in the end you still get what you pay for, which is more than can be said for a number of other companies.And Silver, the Core Duo is still a better product than whats out there, though I saw on anandtech (GASP! I said the bad word), that Intel is having supply chain problems with it that may make it obselete by the time it is readily available.
I agree. There hasn't been anything to prove that there isn't a fault with Intel's design. Whether Linux, MacOS, whatever, someone really needs to verify that.By the way Silver, Though it may be M$s fault, I also haven't seen anything to prove that it isn't a fault with Intels design either. They have both screwed up in the past. We'll have to wait and see what the Linux tests show.
He he he he he. Aww. You shouldn't have. 😳 I love you too. :mrgreen:Most of us here know not to take Silver personally.
And don't think that I don't appreciate it. :mrgreen: This is an awesome thread.Thats exactly why I started this thread in the first place. To give us something to talk about and debate that isn't Tech Support related.
Darn tootin'. :lol: Especially when, at the end of the day, we can all laugh about it and have a beer. (Or whatever.)Besides, a good ole argueent is fun once in a while :lol:
We're good at that here. Topics rarely stay on topic the whole way through.Wow. Sounded like a pretty intereseting topic and turned into a discussion on whether somebody got flamed and why.
:lol: :lol: :lol: I hadn't even thought of that angle, but you're right. I can totally see M$ doing that. I can even see them whining about it and purposefully dragging their heels, like they did when they had to support x86-64.1) we all know that MS is an evil empire, let's face it, so I could easily see them know about the bug and not be overly concerned with it. But
Maybe. Maybe not. Maybe they figure that a registry change is something that doesn't even need a fix because anyone can go in and make that change. Maybe they figured that without a platform out there to support yet, there was no reason to make a fix. Or maybe they even have made the patch but are still testing it to make sure that it doesn't adversely affect other platforms. This is M$. They do take their sweet time on just about everything, especially patches.2) the fact that they've known for a while about it, and if it's just a registry fix, would indicate that it would have been likely they would have fixed it, 'cause really not much is involved, and
Except that there is a leak on other platforms. The existing PM platforms showed a leak as well, just not nearly as pronounced.3) the fact that there is no leak on other platforms could indicate that it is not all that simple.
Unless they either knew that a software patch would fix it, or just don't consider it a big deal. Even with the loss of battery life, it's still top-notch battery performance that can't be beat. And there are no stability or performance problems to worry about. It's just battery life.What amazes me the most is that Intel would rush a "big deal" product like that without addressing the issues.
That could very well be. Which is why it'd be nice to know if Apple's laptops are experiencing the same thing. That'd say for certain whether or not it was software.So was it some kind of commitment to Apple?!
Here I think you've got a lot of facts wrong. I believe that you're talking about the i820 chipset, which was a P3 chipset.Then again, it would not be the first time Intel released a buggy chipset. What was that P4 chipset called a while back (3-4 years, was it?). Most mobo's were DOA, and I was one of those unlucky early adopters. They quickly released another chipset and forgot about the issue...
Admit it. That felt good, didn't it? :twisted:Get your facts straight...biatch.
Yes, the MTH involved was an Intel part. The problem however was not with the part itself, but that some 3rd party motherboard manufacturers were putting the MTH on too long of a path. Had they followed Intel's instructions it wouldn't have been a problem. The part failed not through a flaw in the part itself, but in the failure to adhere to the specifications that the part required. Still, Intel recalled it anyway, because they had a reputation to uphold.Still an Intel part, if I remember correctly.
I don't argue with either point there. Though there were non-reference mobos that ran the MTH without flaw, because they at least followed the MTH's specs.Regardless, I remember the recall, and you would agree it was kind of a fiasco. (and let's face it, reference mobo's have very little to offer to enthusiasts).
Actually, it wasn't when RDRAM was dead at all. It was at the very beginning of the use of RDRAM. That was the first motherboard to use RDRAM. So Intel giving a replacement mobo with RDRAM (that performed significantly better than the cheaper SDRAM version that had the problems) was a huge benefit. It was a free major upgrade. Well, free in cost anyway. Obviously frustration and downtime was the price to pay. True, RDRAM was more expensive, but Intel had nothing to do with that. And it did perform better than SDRAM. But this was also nearly six years ago now.And if I recall correctly, even if it was indeed post RDRAM then it was already when RDRAM was dead (which Intel tried to shove down our throats at prices that just did not make sense), so no I can not let them slide on that one.
Failing? That's highly debatable. You'd have to be talking about the Prescott core specifically, as the Northwood (especially the NorthwoodC) was quite an excellent core, and gave AMD a lot to worry about.And last but not least, their arrogance in the past couple years with a failing [desktop] design is appaling
No, I'm being fair. There's a difference. When people have their facts wrong, and pass unfair judgement, I provide the correct facts. I'd do it equally for any company. It's only because most enthusiasts have a grudge against Intel and put AMD on some pedestal that I often end up defending wrongful accusations against Intel. Were the tables turned I would not hesitate to do the same for AMD. And, in fact, there have been many the occasion in which I have lauded AMD.I am not about to call you an Intel fan-boy, but I sense you are being protective of the giant.
Looking at the errata for any processor is always a scary endeavor.Link to Intel's current pdf outlining the 34 known errata (problems) and their plans to address these problems. Very interesting for those considering Core Duo...
Looking]http://download.intel.com/design/mobile/SPECUPDT/30922201.pdf