mr_yellow

Quote: Originally posted by Shrink: How about you try it and let us know <g>? Hah.. well, I did try it. i uninstalled all traces of lw1(except those lovely wdm drivers), and started up the lw3 that's been sitting on my hd since forever. and bam! it stalled. I said before, i have a bp6.. BUT i could've sworn i was able to get the setup installed before with rc2 or 3. I even remember the problems with missing .dlls whenever the launcher or mixer tried to start. the same errors lw1 had when I installed it and forgot to install the wdm drivers included with the dell drivers. dammit. so what know? i just realized the wdm drivers have 4 speaker support, and i really only wanted eax support from lw, AND since eax is broken in lw1(was really screwed up in halflife), I've decided to forget lw1 and just used the wdm drivers. yay. quad speaker support with out the overhead of old lw programs... anyone else willing to give lw3 a shot?

Hmm.. this is off topic, but I wonder if liveware 3 will work with the drivers supplied with the dell oem drivers. I've got a bp6, and i'm very surprised everything(well almost everything) works. hmmm... It just seems strange since the installation of the oem liveware and liveware 3 are identical(even the error messages), and the magically oem driver update solved the liveware1 problems. maybe, just maybe, it'll solve the problems of liveware 3... any thoughts on this?

Thanks for the response.. I'll try setting my PSrate to 80 or back to 60.. it's at 100 at the moment. I still wonder as to the use of the logitech drivers. before i could get 100 Hz polling rate for my mouse using the windows drivers. the onlything lacking is the middle mousebutton /double click support. mr_yellow

Has anyone else had this occur to them with mouseware9.0??? complete input loss from Keyboard AND Mouse. Everything else is running and is just waiting input. of the day and a half i've had these installed, this has happened THREE times already.. I'm left staring at my halflife game as people run around me, or at my webbrowser as the stupid ads keep flashing. I end up forced to press the reset button to get back anysort of input. mr_yelloww

*ahem* we are all at the mercy of the software/hardware companys. If they want to delay release of some drivers, then too f'ing bad for us. ranting on this forum doesn't do jack squat either. Do you really think employees of these companies read these forums to 'get motivated' and write the drivers quicker??(if they do? the world really is a better place). I haven't heard anyone say that they've personally sent out a response directly to these companies complaining and voicing their opinions about these delays. Sure we may get a form response, but at least they'll realize the need out there and may actually be pressured to release the drivers quicker. If all of us here do send an email, that like what? 10-20 people? 30+ with all the lurkers out there? this isn't a flood of emails but i'm sure they'll get the picture. Also, you have to realize the market scope of their products. win9x users eclipses any nt or 2k numbers. when a company has limited resources and personel, they can only devote a certain percentage to certain OS's. Devoting the whole team to w2k support is expensive and time consuming, as well as a stupid decision(since w2k ISN'T going to be widely adopted(I expect flames for this remark)). Anyways, back to my original point. Send emails to creative or nvidia or whatever other company that's pissing you off. And FYI. I have an SBLive, and a TNT2Ultra card. BP6 too.. so i do have my own fair share of problems. I also run w2k as my primary OS. Flame away boys..

Reading all the posts of how screwed up logitech's mouseware 9.0 is, I'm kinda iffy about installing iomegaware 2.2 for my parallel zipdrive. Maybe it's the similarity in name, or maybe it's cause it's suppose to be "windows 2000" compatible. ANyways, anyone who's taken the plunge I'd like you hear back from you. mr_yellow

Aww... not ANOTHER tnt2 driver question?? nonono.. just a quick(maybe notso quick) survey. I've been tracking the w2k driver issue for the nvidia cards awhile now. I've noticed a very large difference in opinions for each and every driver release since the introduction of d3d enabled drivers. I have a xentor32 (tnt2ultra). My experiences with all the drivers differs from all of the other tnt2 owners that come onto this forum to spew their troubles. I was wondering if type of manufacturer of the card has any relavence on driver issues. (after writing about a couple paragraphs, I thought i'd delete it and shorten it up a bit. hope you can follow) prior to 3.36(2021-rc2): the most stable drivers i ever had..(albeit broken drivers) 3.36(rc2-rc3): also pretty good. opengl worked sometimes. d3d non-exsitent. 3.5x(rc3-RTM): after trying these, I stayed the hell away from them. ddraw froze my system, so did opengl and d3d. 3.6x(RTM): same thing with 3.5x except for 3.69(RTM): the one driver that everything worked and was (relatively) stable! (maybe you'll remember my rant about it in the past threads) 3.75(RTM): same as 3.69. stuff worked great. but I turned the ddraw and d3d acceleration off via the display properties slider to eliminate the case where playing videos sent my monitor into sleep mode forever. Unfortunately, switching vids to 'full screen' still sometimes results in system freezes. BUT opengl runs great. ya! so there you have it. the history of a xentor32ultra user. mr_yellow (of course all these won't matter two weeks from now when un-beta drivers are (hopefully) released that (hopefully) will work for all.)

Oooo ye ye yeaH!!!! hope these have been as good to me as they 3.69 were... brb with my trials..

Just wondering, but are all of you with problems "clean" installing the drivers? i mean, uninstalling the video card from the device manager, and redetecting the card and then up[censored] with the drivers, all in safe mode? thanks.

just finished with about an hour of q3 timedemoing... I timedemoed in fastest, fast, normal, highest, and custom settings. all in non-smp and smp mode. every mode worked. Switched back and forth resolutions with no problem(this was a guarenteed crash on my machine before on ALL previous drivers). this is sweet!

*big grin* i just played half-life, UT, some direct X winamp plugins, some winamp opengl plugins, and some movie files... all worked.. I know it's not an intensive testing, but in my case. this is a miracle. I just hope thisis still the case a couple hours from now. I uninstalled the nvidia drivers, and installed the 3.69 via safe mode, so no format.. Upgrade from 3.65, where 3.66, and 3.53 were tested. Best of luck to the rest of ya! I'm going to test quake3 smp soon..

The subject speaks for itself.. being in the brink of a clean w2k install, i'd like to know if these are 'working', as in quad speakers work/smp support, etc... Ofcourse I have a nagging feeling these are just the WDM sblive drivers from rc2.. duh.. makes sense right?

I actually had the same problem. although I never tested it with the full version of quake, i assume the demo is just as good. What I discovered is that the gamma slider only registers in the first third of the slider. so if you mouse click on the latter two thirds, the screen would get really dark. But if you click all the way to the left(the darkest) and use the keyboard to shift right, the gamma actually works and only works up to the first third(meaning it'll get brighter and brighter and stop getting brighter after it passes the first third of the bar). I'm not sure if this is so for other video cards or setups. I am running guillemot xentor32 ultra win2k rc3 2183 nvidia 3.64 drivers bp6 dual 366@561 does this work for anyone else or did i just luck out?

I'm listening to everyone talk about getting lw3 and sblive working in the newer revisions of w2k, but I was wondering if anyone has been successful with it on a SMP system?? Does it still crap out during the LW3 setup? Also, the instructions from antony toste is very weird. The original says to overwrite just the wdma10k1.inf, but the newer one overwrites a whole bunch of driver files but NOT the wdma10k1.inf. Also, should the newer instructions(liveware31) be run in safe mode? which parts? just the first? Very confused. mr_yellow

Ok.. I've read that some people can get Unreal Tournament working with the new nvidia drivers(3.53) on RC2. Am i doing something wrong? I have the latest drivers and UT still doesn't 'work'. I mean, it loads up but once the level gets started, everything seems to be un-lightmapped. no shadowy corners or dark rooms. Just plain ol' textures. has anyone else experienced this? I'm running 2128 on dual celeron@550 with a guillemot maxigamer32.

I don't want to sound like an idiot, but where in w2k is the distributed net client? I've tried looking under services but all i see is distributed link tracking client and dist. transaction coordinator(which isn't started). what am i not understanding here? thanks.

Has anyone tried the new drivers/software from logitech? Does anyone know if it's Windows 2000 compatible? I remember logitech's NT4 drivers(8.3) were very unstable and would sometimes even crash my system. thanks.