NV30 to be launched at Fall 2002 Comdex
- Thread starter alexsok
- Start date
Doomtrooper
Veteran
MikeC said:
Well you had better start linking right here...
http://www.nvnews.net/vbulletin/forumdisplay.php?s=6c3b88adfca6a10979c4cf7d3e5246c7&forumid=26
Its probably wise to inform your user base of driver issues/hardware issues related to the hardware your site is built around before posting competitor links to issues alot of the people posting have no clue about..
Example:
http://www.nvnews.net/vbulletin/showthread.php?s=6c3b88adfca6a10979c4cf7d3e5246c7&threadid=1626
Tv-OUT don't work according to this thread with OEM Geforce 3 cards, which requires a bios flash of the card
Remember Mike you said
I would consider that pretty big news...and its on your own forums.
Typedef Enum
Regular
The reason why I posted that information is simple...
I guess I'm just smart enough to read market trends...I fully understand that ATI has a good product out right now AND I realize that a good number of _our_ readers will be buying a 9700. It's that simple..
And the guy who claimed that the essence of that post was, "ATI still has shit-ass drivers...blah blah blah...go to Rage3D and check it out..."
I very carefully stated that viewers of our site should go to Rage3D to check out the compatibility issues that actual users are experiencing to make sure they're hardware is OK. There was no other insinuation whatsoever.
The reason why you probably wouldn't see this on Rage3D is the fact that, for the first time, you will begin to see nVidia folks migrating to ATI for the simple and obvious reason that ATI was the first out the door with a DX9 part, and it clearly outperforms anything else on the market...The exact opposite situation has never happened, period. At no time in the past have you seen a wave of diehard ATI users flock to nVidia products, as nVidia has always been the performance leader in their respective market (though I'm sure there are those that will argue this point to no end).
I guess I'm just smart enough to read market trends...I fully understand that ATI has a good product out right now AND I realize that a good number of _our_ readers will be buying a 9700. It's that simple..
And the guy who claimed that the essence of that post was, "ATI still has shit-ass drivers...blah blah blah...go to Rage3D and check it out..."
I very carefully stated that viewers of our site should go to Rage3D to check out the compatibility issues that actual users are experiencing to make sure they're hardware is OK. There was no other insinuation whatsoever.
The reason why you probably wouldn't see this on Rage3D is the fact that, for the first time, you will begin to see nVidia folks migrating to ATI for the simple and obvious reason that ATI was the first out the door with a DX9 part, and it clearly outperforms anything else on the market...The exact opposite situation has never happened, period. At no time in the past have you seen a wave of diehard ATI users flock to nVidia products, as nVidia has always been the performance leader in their respective market (though I'm sure there are those that will argue this point to no end).
TheMightyPuck
Newcomer
is this what people mean when they talk about hijacking threads? 
Typedef Enum
Regular
DT, Seriously...
How many threads do you intend on just completely ruining while visiting this forum? I mean, do you get a kick out of flat out destroying those things that used to make this forum so great?
I hate to beat a dead horse here, but it's utterly clear as day that you, almost single handedly, have been responsible for the vast majority of mud-slinging, name-calling, and extreme zealotry/fanboyism that has ended up turning good threads into a big wad of crap.
How many threads do you intend on just completely ruining while visiting this forum? I mean, do you get a kick out of flat out destroying those things that used to make this forum so great?
I hate to beat a dead horse here, but it's utterly clear as day that you, almost single handedly, have been responsible for the vast majority of mud-slinging, name-calling, and extreme zealotry/fanboyism that has ended up turning good threads into a big wad of crap.
Sabastian said:
Yea, none of these NVIDIA fansites mentioned that MotoGP, a game developed on NVIDIA hardware, is broken with the latest Detontor 40 driver (which gets final after they get the WHQL certificate from MS) on NV20.
I also remember 3DGPU and PCRAVE never saying that the NV30 pictures they posted (and claimed that these are actual NV30 pics) have been rendered in software.
Mephisto said:
Let me just chime in and say that I seriously, seriously doubt that the 40.41 drivers will get WHQL certification. They're just too buggy.
Granted, they still work on my system (for the most part...for some odd reason I'm having a hard time running 3DMark2k1...but I don't really care about that...), but that doesn't mean I haven't seen bugs, such as the aniso selection bug in Direct3D and the flashing screen bug, also in Direct3D.
MikeC:
"What exacty is it that you find offensive with Scott's post?"
That it keeps perpetuating that impression that ATI has bad drivers.
As soon as an issue is discovered with ATI, it's immediately , 'oh we knew that would happen, they have shitty drivers after all'. If something breaks with Nvidia, it's just a bug. Or some may claim it's the OSes fault, not the drivers at all...
It's simply bad news reporting to keep doing this OVER AND OVER. If you guys checked the Nvidia newsgroup, you'd seen the enormous flood of posts reporting basically unfixable instances of that infinite loop crash with W2k/XP. Only thing that helped for many people was to go back to the 21.83 driver. I think the issue is finally fixed now, but I'm not sure.
Or what about all the bugs in Nview? Also tons of posts about various problems. I've personally had the thing crash each and every process in my system ("seti@home has performed an illegal operation in nview.dll and will be shut down", etc), things that has absolutely NOTHING to do with Nview, until it hit something critical that simply made my box die and I had to switch it off (no reset button unfortunately).
I don't see anyone trying to create an impression of Nvidia having bad drivers despite there definitely being severe issues with them for a great number of people! However, ATI is not given the same courtesy, and that includes Scott at NVNews.
Testiculus:
"is DOS still a supported OS?"
Not by Microsoft, hasn't been for years I think. DOS programs work in a window, but not fullscreen. Hell, even a simple DOS prompt doesn't work full-screen, monitor switches itself off. Problem is, you can't run VESA apps in a window...
Anyway, that doesn't really matter since fullscreen DOS apps worked great with the 21.83 driver and now they don't. I can't see why anyone would intentionally break the thing just because it's not supported by microsoft anymore. It's a bug and they should fix it. End of story.
"WindowsME doesn`t even include DOS"
Yes it does. On every ME system you'll find command.com, io.sys... Dude, that *is* DOS!
"Now that we`ve cleared that, I was wondering which of the rather recent( say 2 years or so) game titles have been built for DOS?"
What relevance is this? I like playing OLD games, so sue me.
"I`m not defending nVidia`s drivers"
Hm, you could have fooled me dude because it sure sounds like you are! You're making excuses for them by saying DOS isn't supported anymore and there's no new games for it anyway. You're in damage-control mode, and that's the same as defending.
*G*
"What exacty is it that you find offensive with Scott's post?"
That it keeps perpetuating that impression that ATI has bad drivers.
As soon as an issue is discovered with ATI, it's immediately , 'oh we knew that would happen, they have shitty drivers after all'. If something breaks with Nvidia, it's just a bug. Or some may claim it's the OSes fault, not the drivers at all...
It's simply bad news reporting to keep doing this OVER AND OVER. If you guys checked the Nvidia newsgroup, you'd seen the enormous flood of posts reporting basically unfixable instances of that infinite loop crash with W2k/XP. Only thing that helped for many people was to go back to the 21.83 driver. I think the issue is finally fixed now, but I'm not sure.
Or what about all the bugs in Nview? Also tons of posts about various problems. I've personally had the thing crash each and every process in my system ("seti@home has performed an illegal operation in nview.dll and will be shut down", etc), things that has absolutely NOTHING to do with Nview, until it hit something critical that simply made my box die and I had to switch it off (no reset button unfortunately).
I don't see anyone trying to create an impression of Nvidia having bad drivers despite there definitely being severe issues with them for a great number of people! However, ATI is not given the same courtesy, and that includes Scott at NVNews.
Testiculus:
"is DOS still a supported OS?"
Not by Microsoft, hasn't been for years I think. DOS programs work in a window, but not fullscreen. Hell, even a simple DOS prompt doesn't work full-screen, monitor switches itself off. Problem is, you can't run VESA apps in a window...
Anyway, that doesn't really matter since fullscreen DOS apps worked great with the 21.83 driver and now they don't. I can't see why anyone would intentionally break the thing just because it's not supported by microsoft anymore. It's a bug and they should fix it. End of story.
"WindowsME doesn`t even include DOS"
Yes it does. On every ME system you'll find command.com, io.sys... Dude, that *is* DOS!
"Now that we`ve cleared that, I was wondering which of the rather recent( say 2 years or so) game titles have been built for DOS?"
What relevance is this? I like playing OLD games, so sue me.
"I`m not defending nVidia`s drivers"
Hm, you could have fooled me dude because it sure sounds like you are! You're making excuses for them by saying DOS isn't supported anymore and there's no new games for it anyway. You're in damage-control mode, and that's the same as defending.
*G*
Testiculus Giganticus
Newcomer
WinME does NOT include DOS. You could indeed hack support for it by copying msdos.sys, io.sys and command.com from the emergency repair disk. Prove me wrong. Because some files are there does not mean it is included by the maker, MS. The thing with SETI may be an issue. And trust me, on the TO DO list at NV, fixing old DOS games is not the top priority, even though it could be a deadly blow to the R9700 if a GF card could beat it in Alien Invaders or Commander Keen
Testiculus Giganticus said:WinME does NOT include DOS. You could indeed hack support for it by copying msdos.sys, io.sys and command.com from the emergency repair disk. Prove me wrong. Because some files are there does not mean it is included by the maker, MS. The thing with SETI may be an issue. And trust me, on the TO DO list at NV, fixing old DOS games is not the top priority, even though it could be a deadly blow to the R9700 if a GF card could beat it in Alien Invaders or Commander Keen
On a WinME system, go to 'Start;, 'Run', then type 'command', and tell us what appears...
Testiculus:
"WinME does NOT include DOS."
Rofl. Dude, that's just TOO funny! WinME is based on the win95 architecture, which in turn is heavily reliant on MSDOS. Only thing MS did with ME to "remove" DOS was to modify the boot files so you no longer have a boot-to-dos option after tapping F8 during startup.
Otherwise it's the same old shit. Try renaming (or deleting, if you're brave) the MSDOS core files from a WinME system, reboot the computer and check what happens.
"Prove me wrong."
I think you just proved yourself wrong. Claiming WinME doesn't support DOS is utterly prepostrous since it RELIES on it...
"And trust me, on the TO DO list at NV, fixing old DOS games is not the top priority, even though it could be a deadly blow to the R9700 if a GF card could beat it in Alien Invaders or Commander Keen"
Like I said. It's not just old DOS games that won't work; fullscreen dos prompts don't work EITHER, and that's actually something that people use, even today.
It's a bug, they should fix it. And you should stop making (bad, I might add) excuses for them.
*G*
"WinME does NOT include DOS."
Rofl. Dude, that's just TOO funny! WinME is based on the win95 architecture, which in turn is heavily reliant on MSDOS. Only thing MS did with ME to "remove" DOS was to modify the boot files so you no longer have a boot-to-dos option after tapping F8 during startup.
Otherwise it's the same old shit. Try renaming (or deleting, if you're brave) the MSDOS core files from a WinME system, reboot the computer and check what happens.
"Prove me wrong."
I think you just proved yourself wrong. Claiming WinME doesn't support DOS is utterly prepostrous since it RELIES on it...
"And trust me, on the TO DO list at NV, fixing old DOS games is not the top priority, even though it could be a deadly blow to the R9700 if a GF card could beat it in Alien Invaders or Commander Keen
"Like I said. It's not just old DOS games that won't work; fullscreen dos prompts don't work EITHER, and that's actually something that people use, even today.
It's a bug, they should fix it. And you should stop making (bad, I might add) excuses for them.
*G*