sotti

I never had problems with crackling with the win2k driver release, or the lw2 release. Only the new liveware 3.0 drivers cause the crackling on my system, loading old drivers, disabling the second cpu, or turning hardware acceleration off, fixes the problem. it IS a driver issue oh yeah, and everything works fine if I boot to 98 [This message has been edited by sotti (edited 26 July 2000).]

I never had the pc speaker enabled, and never had problems until the liveware3 drivers came out. now I have crackling and pc speaker is muted

This was also a common theory back when Nvidia did the first detonator release for the TnT. Remember their was even an unofficial rumor that the reason STB(newly purchased by 3dfx at the time) was not releaseing detonator drivers because they caused basically overclocked the hardware and were unstable(wich is false), and sited examples very simialar to the ones you mentioned. The truth was that they didn't support the Detonator drivers was because they made the TnT look alot faster than a Voodoo2 in D3D. Anyway the bottom line is Nvidia refrence drivers will never overclock hardware by default, because they need to know the hardware is stable when they are working with beta drivers. They use the scientific method you know, they are scientists. Anyway they totally restructured their texture management structure to be able to handle anti-aliasing and this is a beta so they're are natuarally gonna be show stopping bugs

hmmm, the first install on these drivers didn't go well for me, I've been having a difficult time getting any driver other than the original shipping(read no 3d support) to load back up correctly. I can't say the problem wasn't my fault. But I've had issues with it so far.

Okay I've got one for all those people that run around sayin win2k is not a gamers os. And yes I have seen the offical statements sayin for gaming use 98/me, for apps use 2k. With that said why would microsoft choose to put the win2k kernel as the os for their newly announced(longtimed rumored) x-box? because it's stability and functionality are clearly the best choice for gaming. Everything else is driver problems. proceed to flame away. [This message has been edited by sotti (edited 26 March 2000).]

when I try and run the install it hangs, if I manually load just the driver I get a blue screen of death just before the login prompt. Still waiting for creative, although I appreciate the availabity of the betas

nope no hacked drivers at any point.

tried the universal inf, no luck just thought I'd mention I'm using the acpi multiproc hal, w/ mps 1.4 in bios

Okay the system is an abit bp6 running the qq bios, TNT2U running the 3.78 drivers, also have an old isa adaptec scsi, netgear fa310tx, and a ltwin modem(my dsl due date is in 3 days), The sound blaster is one of the original live value boxed retail version, and win2k ver 2195. So first I did it incorrectly and ran the setup first. Then after I installed the inf windows would crash out after the windows 2000 built on NT screen, but before I get my login prompt. So I booted to safe mode, removed the sound blaster from device manager, and ran the uninstall on liveware apps from add/remove programs. rebooted, it redetected my sblive and loaded the basic wdm drivers, I get sound and everything appears as it was. then I re-installed the updated drivers, I rebooted so that I could install the software and bam it crashed again right before the login prompt. if anyone can see a fault in the way I'm loading drivers or has a workaround for this problem please let me know. The only other odd thing I saw was after the new drivers were installed I got a device driver called "winmm wdm audio compatability driver", has anyone else seen this being loaded. [This message has been edited by sotti (edited 20 February 2000).]

Hey Mr. Marbles I don't want to call u an idiot, but UT shipped on DX7, it's on the friggin disk. It uses D3D 7.0, the original demo was on d3d 6.0 and hell the original unreal was on dx5(although it had no D3D support). Anyway the 3.69 drivers are buggy because they are buggy, I get texture curruption in Freespace2(written for dx6), and 3dmark2k(written for dx7). Anyway, time to start lookin for the 3.70 drivers.

Has anybody played this game successfully? The ingame is fine, but when it goes to load the next mission it gets about 4/5ths thru loading then lock up. system is NT 5.00.2915 abit bh6 w/ 450 sblive using default drivers TNT2U w/ 3.66(gonna dl 3.69 tonite when I get home) I'd love to hear from anybody who has played successfuly or not

I do tech support on the 2100 modems, the line is no one has gotten one to work on 2k, we take the calls when they don't, not that we support it yet, but we get alot of calls for 2k and neither of the internal modems work on 2k yet. And there hasn't been an annoucement of 2k training yet either.

I have .2195 and the 3.65 drivers from nvidia. The gamma seems exceptionally low in q3. Im wondering if there is a good console command or anything in the OS that can be tweaked to make it look like 98, or NT4.0