gsellis
Diamond Member
- Dec 4, 2003
- 6,061
- 0
- 0
No, the Pro was available in quantity about a month after street date. The PE was never in quantity, even though they said it was. I remember it as it was part of a project I was working on and was cancelled.Originally posted by: Genx87
Originally posted by: gsellis
And that is because nVidia never paper launches, right? Do remember that the 6800 launched about 3 weeks before the 800 (which was rushed because of that announcement) and hit the streets about 2 months later than the 800. I am glad they learned their lesson and did not paper launch this last time. And it was a stroke of genius because ATI assumed same old same ole and was caught completely flat-footed figuring they had the same lead time on a 'paper' launch.Originally posted by: Rollo
Originally posted by: M0RPH
Originally posted by: junkyardDawg
I don't think you can compare x1800xt to crossfire. crossfire in may was a true "paper launch". I think they've got working xt's now, just not enough to avoid a x850xtpe-type debacle.
Don't try to use logic on Rollo. That never works.
My point about X800 Crossfire and paper launches is valid- that did happen, twice, and some people have been waiting since May.
People who wanted a X800XT PE last year largely had to wait a long time as well.
Paper launches are a big concern and ATI excels in them.
Not really familiar with that. I remember both companies paper launching and the 6800GT\Ultrass showing up in quantity late June while it took ATI until Nov.
nVidia showed some cards at WinHEC, but it was late June before a sku showed up. It was about 3 weeks later that they were available in quantity.
I also got into the 6800 PVP debacle right off the bat because nVidia told me it could after I had dug around, and then found out it could not do WMV decode (part of that project.) BUT, ATI NEVER got back to me on what it could and could not do with WMV decode, even after talking to some higher ups in CA.
IOW, they both annoy me equally, but nVidia actually told me stuff that was not true (and I cannot fault the guy who did as it was their own documentation that said it and that is the only thing he had as a reference.)
Sorry, back to topic.