mr_yellow

Oh poopy in my pants! ... hmm wtf have i recently changed on my system??? hmmm...... thanks for your replies.. mr_yellow

Ummm.. Did anyone else's system get fubar'ed by the 5.25 install? I installed/updated just like always, but the last install screen said "An error has occured: The specified file could not be found" That file is not listed anywhere. Anyways, I tried reverting back to my 5.22's and i get the SAME error message! I tried any of the earlier driver releases which I've installed before. the SAME error message.. So now i'm stuck with VGA mode and a big yellow exclamation mark beside my TNT2 Ultra card in the device manager. Does anyone know or have experience with this problem? In dire need for help. thanks. mr_yellow

I'd like to be the smart-ass who says(sorry): "Use the search button". You can not only find which file to edit but exactly what the other instructions involved are. and since I'm not the total sh*t-head i will outline the proceedure from what i have left in my memory. nv4_disp.inf: yes,that's the file you edit. You can find it packaged with the drivers BEFORE you install.. so unzip it from your archive. find the resolution and refresh rates for you card. Mine's a tnt2 ultra, so I look under: NV5ULTRA you'll see the listings grouped by colour depth and on each line a resolution and it's valid refresh rates. etc, etc, etc... there's also a way to directly edit the registry so you don't have to reinstall drivers. So go use the search button already!! you think my memory is that good?? mr_yellow

I did read somewhere that enabling the W2K software RAID, like dynamic disks and striped disks makes your computer unbootdiskable(if that's such a word). I think the solution was to unplug the harddrives with the offending partition and then boot with the bootdisk. but then.. you didn't mention anything about dynamic or striped partitions. just a thought. mr_yellow

I'm not sure about the geforce users out there but My TNT2Ultra card has the intermittent black screen boot up bug with all the new 5.xx drivers, and the 3.81+ drivers. Does 5.22 suffer from the same ailment?? thanks mr_yellow

When you had RC3 installed, was it with Multiprocessor ACPI support? I too have sticky keys problem and have narrowed it down to when I flashed my bios from nj to qq AND clean installed with multiproc ACPI support(I did both in relatively short time). I'm thinking if I go back to NJ, the ACPI support will freak on me so I'm just sticking it out... I wonder how that new RU bp6 bios is.. But I'm running out and buying a USB mouse today so I won't have this problem anymore! yay.. dumb ps/2.. mr_yellow ------------------ -----mr_yellow Win2k build 2195, ACPI enabled. Celeron 366@550 on BP6 w/QQ, Xentor32 TNT2U(3.81), SB Live!(Liveware2k), IDE1=6G quantum(ata33), IDE2=CDROM, IDE3=13G quantum(ata66), Dualboot with win98.

What motherboard are you using? I have a feeling you're a bp6 user if you're asking a question like this.. mr_yellow

unchecking the box in tweakUI isn't enought to get rid of the version number on the desktop. The problem lies in the fact that if the KEY is there, no matter what it is, a 0 or a 1, it will still paint the version on the desktop. the solution is to DELETE the key from the registry.. and since I've already experienced this myself, I know first hand. BUT since the key has been removed from my registry, I can't look up what it is! hahahahahahah anyways.. look under HKEY_CurrentUser(or localmachine)/control panel/desktop/ in that folder you'll find something to the words of "PaintDesktopVersion" or "PaintVersionDesktop" or Paintversionondesktop or paintversionnumber or paint.. bah.. you get the idea.. if it's not in that folder do a brute force search for "paintversion" that should result in the key. anyways, happy hunting. Remember, Delete the key, even if it's turned off (0), it'll still put the version number on the desktop.

Complexity brings along incompatibilities and hardships. Dual Celerons will introduce a whole slew of problems and hiccups that, if one isn't prepared for, will frustrate even the most patient. SMP, Overclocking, Win2k, this is a recipe for disaster. Being a BP6 dually, I have to admit sometimes i wish i didn't have to deal with some of my probs. When i built my system I researched to hell. Went through the exact same questions you're going through. unfortunatly, when I did buy athlons wern't in full force and i didn't have the time to wait. If confronted with the decision now, I'd buy a higher speed athlon instead of a lower dual celeron.. But i love the fact that I have enough horsepower to last me a while. My system is highly upgradable(dual p3 via powerleap adapter). And the technology is very mature and reliable. Hope this helps.

Yep.. the new 5.13 detonators have gamma correction. i don't have the url but i'm sure it's all over the place. mr_yellow

Bah! Spoke too soon.. just lost my keyboard/mouse control a couple minutes ago.. ****ing hell.... Increasing the buffer helped but problem still occurs..

Another possible resolution or work around is to increase the input buffer from 100 to 300(max, at least for me). I usually get dead mouse/keyboard(sticky keys) 2-3 times a day. I've been running at 40Hz ps/2 rate and 300 buffer for like a week now and It's I've only gotten the sticky keys maybe once(I didn;t experience it, a friend did(using my comp) and told me afterwards. Not sure if he had a Hard crash or had sticky keys). Can anyone else comfirm this? mr_yellow

I'm running dual366@550 on BP6 and have had the sticky keys(loss of mouse and keyboard) with three logitech mice: PS/2 firstmouse wheel, ps/2 firstmouse threebutton, and ps/2 mouseman 95(old wedge design(aka gaming mouse)). My Story: I ran all the betas Plus the 2195 final with my threebutton firstmouse for months without problems, until I switched to the firstmouse wheel. That's when i started getting sticky keys. Unfortunately I also upgraded to Mouseawre 9.0 so all that time i thought it was that.. I uninstalled, reinstalled, everything(including win2k) but i still kept getting the sticky keys with the firstmouse wheel. Bah! sucks eh? I thought I had it figured out before where i had a week of no crashes with the ps/2 firstmouse *threebutton*(i finally switched back to see if it was the mouse). I also changed my MPS 1.4 to 1.1. I switched back to the firstmouse wheel and bam! sticky keys. For uncontrollable reasons i couldn't get the threebutton firstmouse back so i went out and bought the old mouseman95 mouse(i love the feel of it, also three buttons) and tried it out thinking it was a wheel problem, but i still get sticky keys in games AND in plain ol' desktop(was always like this). I'm desperately trying to get back my three button firstmouse... mr_yellow --------- Win2k build 2195, ACPI enabled. Celeron 366@550 on BP6 w/QQ, Xentor32 TNT2U(3.81), SB Live!(Liveware2k), IDE1=6G quantum(ata33), IDE2=CDROM, IDE3=13G quantum(ata66), Dualboot with win98. [This message has been edited by mr_yellow (edited 02 April 2000).]

The strange thing is is that, before I had installed liveware2k, i still got the DMA problem of permently stuttering sound and crashes etc with the WDM drivers.. weird eh? I guess it just sucks to be me..

This may apply to you, but it's never happened to me before... Try redownloading the update file MANY times until it gets through correct. I've had friends have to redownload the update patch like 5-10 times. probably the best way is to get it straight from the source from download.com or some public file archive. Update it and try running it after that..

Quote: Originally posted by Jabba: I thought the drivers OFFICIALLY supported SMP. Am I wrong? Well.. they DO work.. just not well... But i usually don't trust the PR people.. Are you running smp and EVERYTHING works fine for you?

rbarbier is partially correct. New/old dirvers probably do screw themselves over.. BUT the fact still remains that the drivers are NOT smp friendly(at least not BP6 smp friendly). I have a clean w2k install and virgin wdm sblive drivers before I upgraded to the w2k live drivers/package. My sound works but is ****ed. Sound from stuff(games, winamp, beeps, etc) eventually start stuttering and hangs shutdowns waiting for a certain process to die... Also eax is broken. tested with rally2k and HL.. sounds become lagged and repeat after a second or so.. hmm.. what else broken can i bring up? oh yeah.. mediaplayer will start skipping every couple seconds if you don't bump down the sound acceleration in the multimedia options.. My friend who has a 1 cpu bp6 setupwith the sblive and w2k doesn't have any of the above problems... (i'm not sure if his eax works though).. mr_yellow

hah.. sweet.. now that's being considerate..

Not to be a patronizing bastard but, check the microsoft knowledge base.. I had the same problem.. look for keywords winmgmt or WMI ADAP you have to reinit the winmgmt database or something to that effect...

Yay.. I get to be the guy who first posts it on the forum! Saw it on voodooextreme. I'm going to try it out later.

Liveware 2k sucks ASS on SMP systems just as much as the beta and hacked drivers before it. I installed liveware 2k on a perfectly clean, untouched win2k(been waiting for 'offical' drivers) and i get the same results from previous wek installations with the hacked drivers. HL, UT, Rally2k, etc. all have sound distortions and delays when eax is enabled. rally2k even has sound distortions when 3dsound is disabled. also, my multimedia video skips now!! I had this problem before on previous installed but never knew it was the sound drivers fault! I always thought it was the multitude of nvidia drivers i went through. So you smp users beware.. the only good thing that comes from this is quad speaker support. but you lose a lot more in my opinion. mr_yellow

goto www.friendtech.com look forthe pl-s370 or the neo-370(samething). it's a pin converter socket ~6mm thick so that you can stick a coppermine in a ppga-s370 socket. apparently it's very close to release. been tested with bp6's and other s370 boards. read teh forum. lots of info there..

Abit released the bp6 at the crappiest time possible. Right before the release of windows 2000. If you consider the timeframe in which the bp6 was announced, all we had was w98 and nt4. The bp6 works Great with these OS's. Let's not forget Linux. Other than some hpt366 foul-ups, it still was compatible. True they should have been more prepared for w2k, but then, EVERY HARDWARE MANUFACTURER has had w2k problems. Abit isn't the only one. Of course if you asked me about this before things such as the QQ bios and the 1.231 hpt drivers, I'd be just as pissed the worst of them... mr_yellow PS. The prospect of Dual Coppermines is too tempting for me to ditch the bp6...

As much as i anticipated them, I'm sticking with 3.81. Movies don't crash and opengl/d3d still work(tested with q3, HL, rally2k).. the only thing that bugs me is that i can't resume from hibernate with the 3.81 drivers.. but it worked with 3.78's.. Ah well.. EDIT: I've got the guillemot xentor32 TNT2Ultra [This message has been edited by mr_yellow (edited 22 March 2000).]

Quote: Originally posted by euankirkhope: blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen,blank screen Is all I ever see... Sigh... Still stuck with 3.66 I got the same blankscreen startup after i updated my 3.78 drivers to 3.81.. i booted to safe mode, rebooted into regular mode, and updated the wdm drivers to 3.81 and it worked. Maybe you can try that.. Or stickwiht 3.66 since everyone seems to like those. hope this helps. mr_yellow