YuppieScum

Hey - it gives us something to talk about...

OK, so you've done a clean install. Now, what errors do you actually get, and in what versions of the software?

Did you re-install W2K after swapping your mobo? W2K is like Win9x in this regard - during setup, drivers specific to the components comprising the mobo are installed, and that varies mobo to mobo. Not doing a re-install will seriously compromise stability... ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

Run DXDIAG, and hit the Display tab - there are buttons to disable several video card driver features, including AGP...

FWIW, I get the same problem on my BX chipset mobo...

Yeah, there is. Tools, Internet Options, Advanced. About 1/2 way down is the option "Use inline AutoComplete" - select it. You can also turn off smooth scrolling just below. Also, about 2/3rds of the way down is a heading "Search from the address bar" - select the "Do not search from the address bar" option to stop MSN loading if you get an address wrong. This is the first thing I do with a new install of W2K ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

This happens for me occasionally with the TNT 3.75 and 3.69 drivers. It may be because my current install of 2195 went over 2194, which went over 2183, which went over 2176, etc...

I sounds like you've installed a dodgy Win9x driver somewhere along the line - certainly the W2K kernel doesn't export a funcion called "SMaplS". Also, you don't mention where the driver says PCI instead of AGP, or where GLide 2.56 is reported. I have a CL TNT1 card (similar in all but name to the Viper550) and a Voodoo2 SLI, and both perform flawlessly. I recommend uninstalling both of your devices, downloading the drivers once more, and installing them one at a time (TNT first) to determine exactly what is causing the error. It may turn out to be neither of the vid cards... ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

That really sounds like a refresh rate problem. Did you edit the vid card INF file to remove slow refresh rates? Does your monitor have an on-screen display - does it show the current refresh rate?

Well, I can only run at 1280*1024 because that's the max resolution of my 18" LCD flat panel Rig Sig follows... ------------------ SuperMicro P6DBS (dual UW-SCSI) BIOS 2.2, 2*Celery 300a @ 450Mhz, 384MB PC100 RAM SCSI-A=4.3Gb+9Gb, SCSI-B=Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100, IDE1=4.3Gb IBM EtherJet 10/100 NIC PCI + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI PCI SoundBlaster Live PCI (not Value) Win2K build 2195 120-day eval

You don't say if this just happens in UT or in other games too, so try changing the "audio hardware acceleration" setting in UT. You could also run DXDIAG and use the h/w accel slider in the sound tab until things work...

Any game will benefit for the presence of a second CPU, 'cos the "game thread" won't keep getting stopped while the OS does I/O and things...

If the camera is working - try MS NetMeeting, which has the advantage of being free... Failing that, there are several other packages around - you might want to look in the "app compatability" list elsewhere on this forum...

Dunno man. I'm in favour of as much info as possible (but on as few rows as poss for a couple of reasons. 1. It'll encourage the newbies to give COMPLETE info about their kit when they ask questions. 2. It might give them confidence we know what we're talking about - 'cos we have experience of the kit, and it works for us The fact you've got ATA66 and striped drives is worth mentioning...

Sounds like a plan. I also think some kind of request to search the forum before posting, and include actual details in questions sould be made during forum membership signup. Maybe we need a forum FAQ...not that anyone would read it. ------------------ SuperMicro P6DBS (dual UW-SCSI) - 2 * Celery 300a @ 450Mhz and 384MB PC100 RAM 4.3Gb + 9Gb on SCSI-A, Tosh32x CD-ROM, Yamaha4416 CD-RW, Iomega ZIP100 on SCSI-B, 4.3Gb master on IDE-1 IBM EtherJet 10/100 + Nortel ADSL "modem" CL TNT1 AGP + Quantum3D Voodoo2 SLI SoundBlaster Live (not Value) Win2K 2195 120-day eval

Sorry if I ffended anybody with my use of the word "dweeb" - not being an American I may have an improper understanding of it's meaning... Two questions though... 1. What was the solution to the crashing problem - dodgy cable, dead fan, Win9x/NT4 driver? 2. SHS, when people sign up for the forum, can we ask them to give a bit of detail in their help requests?

Either Write your driver to the WDM (Windows Driver Model) spec, or You've missed changing a compiler flag - IIRC the OSVER flag, but don't quote me.

The last thing Q3A tried to do is Loading dll file ui. and the error is User Interface is version 4, expected 3 This implies that the prob is not with the drivers, but with the install of Q3A. Perhaps you've installed a mod thats not happy with the ver you're running, or maybe an update of Q3A didn't "take" properly. Try a clean install of Q3A.

I've been using my SideWinder FF Pro plugged into both my SB AWE64 and SB Live under Beta3, RC1, RC2, RC3 and gold, with my FSB at 100mhz. It works. No special drivers required. Just use "Game Controllers" in Control Panel and let it find the OS-provided native driver.

Several things. 1. You don't mention BIOS revisions or driver versions. 2. The error you see is usually due to either driver or hardware unhappiness. 3. W2K is more sensitive to overclocking than Win98. 4. There are some issues reported with VIA chipsets and AGP vid cards, resolved with BIOS updates. and finally 5. All the above can be found by searching this fourm...

Ah... Use CDRWIN to make the bootable CD. Also, don't worry about it only being a small boot block - the boot block for NT on the HD is tiny but it fills 100Mb after it loads...

RC1, RC2, RC3 and gold have all worked fine with my dual CPU and SBLive - 24*7...

First you might give us a little more info. What hardware, Os version, driver versions? Run MBM and get an idea of CPU temps. Are you overclocking your CPU or vid card? For fscks sake, give us something to work with, you dweeb!

now that you've given a bit more info, we'll try and help. Is it D3D or OpenGL (or both) that demonstrate this? What does DXDIAG say about your setup and refresh rates?

There are no overclocking features in the drivers, and almost certainly never will be, as they would compromise the stability of W2K - which after all is what W2K/NT is all about. Get hold of PowerStrip or equivalent for your vid card o/c needs...