Morto

Don't know about that then. I'm using the Adaptec ASPI layer too.... How about trying this; Before I got WinDVD working, I used the Win2k DVD player. Just run "dvdplay" (it's in the path). Morto.

Try making sure that you have the correct ASPI layer installed. You'll find it somewhere around here, I'm sure. Morto.

I'd hazard a guess that it has something to do with the HPT/66 controller. My machine used to hang when running AudioCatalyst and as soon as I changed to using the standard ATA/33 controller (on my BP6) it fixed it! Give it a try - I've noticed that ATA/33 isn't that much slower than ATA/66 anyway. Morto.

AND THEN HIT THE CAPS LOCK KEY.... That's better. Morto.

Yeah, I've got the same problem. I'm using Win2k with a TNT and a BP6. It is a problem with the TNT drivers, because it doesn't happen for me with the ones supplied with win2k. Morto.

Ok, so the fact that Worms : Armageddon, GK3 and nfs4 etc. won't work properly is Nvidia's fault? Don't bull**** here SHS - they don't work. I'm not saying it's the fault of Win2k (and you don't have to get defensive just because your favourite OS has some incompatabilities with older software). All I'm saying is that he's probably better off using 98 if he does not want to use the extra features 2000 offers. And I don't know how the hell Ekstreme thought I was suggesting that 2 CPUs is a requirement. Here's the deal: if you wanna play games and don't need a larger, more feature packed OS use 98. Otherwise, knock yourself out with win2k. If win2k was so ****ing amazing, and perfect for everyone - why do you think Microsoft is making millenium? And don't tell me the win2k is faster - NTFS slows everything down by some factor just for a start. (Due to the security checking, etc.) So you don't have to bite my head off because I'm suggesting that win2k might not be perfect for everyone - different strokes make up the world. Morto.

May I ask why you're even using windows 2000? You only have one CPU, so stick to 98. And don't say you're using it because it's more stable - it obviously isn't because you're getting "spontaneous reboots". Add to that - 98 will run faster on your system. If I didn't have a dual system, I'd still be using 98 (I still do to play games, as win2k still won't play all my favourites). Besides that, try the 3.52 drivers (if they support GeForce) I found them to be the most stable. Morto.

I'm just waiting to see how long it takes for you to be flamed for not using the SEARCH FEATURE, as this question has been answered several times before. However, I'm feeling nice, so use the 3.52 drivers. That will fix everything. D3D will work fine and world hunger will be eliminated. Ok - I lied. (About the D3D working fine) Morto.

OK, I'll tell you EXACTLY how I fixed it. (I hope it works on your systems.) I did a fresh install of RC3 (I needed to upgrade from RC2 anyway). I then installed the 3.64 win2k drivers that were posted in this forum about a week ago. At this stage I loaded Q3 and had the problem that everyone above mentioned - the screen freezing with the small part around the head icon still moving. I then downloaded the 3.53 drivers from NVidia's web site and extracted ONLY the nvoglnt.dll to the WINNT\SYSTEM32 dir. I then rebooted and re-loaded Q3 and it all worked fine. NOTE: This is ALL that I did - I did not modify any configs, etc. Morto.

See my response to Ronin's post: http://cgi-bin.spaceports.com/~compatib/ubb/Forum6/HTML/000536.html Morto.

Well, IMHO, SMP does make a large difference to the OS as a whole. (Anyone that has studied Multiprocessor systems and Distributed systems in computer science should back me up on this). The main factors to consider are how much multi-tasking you will be doing, how many multi-threaded apps are you using, and you should realise that it will NOT be twice as fast (as Amdahls law suggests). The other factor to consider is whether your apps are CPU bound or I/O bound (do they spend most of their time computing, or is there a lot of HD access?) If the latter, SMP will make little difference, as even one CPU would be waiting on the I/O. However, in general use and when multi-tasking (given enough ram), an SMP system is wonderful. Especially if you have REAL multi-threaded apps (or run two copies of the same non-multi threaded apps at once) So, in answer to your question - it IS worth the trouble. Even if it's just for the EXPERIENCE. Morto.

Just download the newest Win NT drivers from NVidia's site, and extract ONLY the nvoglnt.dll to the WINNT\SYSTEM32 directory. That fixed the problems for me, hope it does the same for you guys.... Morto.

There is a known issue with the "lesser" version of this game. Try hitting the [enter] key or spacebar a few times when you think it's hung. Morto.

Just wondering if it helps the issue with SMP and the MX300. I hope so. (I want to use my MX300 again!!!!) Morto.

Has anyone had any success getting ASPI to work with this drive? I've tried LOTS of ASPI layers - Adaptec, Symbios, Pokiosoft (sp?) - none of them work. More specifically, they can't "see" the drive, and Pokiosoft's ASPI quits with: "ASPI Initialisation failed. Error code: F0000006h" Also, "Enable digital audio for this CD-ROM device" under device manager doesn't work - the drive just skips through the tracks when trying to play an Audio CD. I'm using a Pioneer 103s DVD drive on a BP6 motherboard with two celeron 400s. I'm running RC2 (although the same problem occured in build #2114). The drive is hooked up to the secondary IDE channel and is the master (and only) drive on that channel. I have not been able to find a cause for these problems (which DID NOT occur in Beta 3 on the same machine), so I thought I'd ask for some suggestions. Morto.

It turns out that the problems I'm suffering were caused by the HighPoint ATA/66 drivers not responding to ASPI requests properly. So I guess it's broken until HighPoint write better drivers.... Morto.

Just wondering if anyone has had success using a card based on the BT878 chipset in windows 2000? I've looked for some drivers but all I found were some obscure WDM drivers that don't work. Morto.

I have a TNT, RC2 and 3.53 drivers. It works okay, but is a little choppy. Morto.

WOW! I just want to check these few points, JimmyK. 1. These drivers enable D3D, direct draw and OpenGL. 2. The direct draw test actually draws something. 3. The D3D output is O.K (i.e not really slow or with poly errors). If this driver passes all these points, I'm there! (Now I've just gotta find decent drivers for my Sh*t MX300). Thanks, Morto.

Try WinDVD 1.284 (and newer) - it installs under w2k and works fine. If you can't get it to play DVDs, just use w2k's inbuilt player (C:\winnt\system32\dvdplay.exe), and it'll use the WinDVD decoders. Morto.

I installed WinDVD 2.184 (I think that's the version), and then used the built-in w2k player (c:\winnt\system32\dvdplay.exe). WinDVD USED to work under 2032 with the poikosoft wnaspi32, but the aspi does not work under my new build (2114). It doesn't really matter, because if you use the windows DVD player, it uses the WinDVD decoding engine, and works fine.... Morto.

Well, they work according to Dxdiag, but I didn't even leave them in long enough to run a game - no DirectDraw? I'm not going to give up my DVD / ASFs that quickly! Morto.

All I can say is that it works for me in BOTH 2031 and 2114. The only difference from an "out-of-the-box" BP6 and mine is that I've upgraded the BIOS to the newer version that (supposedly) supports ATA66. (The BIOS is available from firingsquad.) Morto.

This problem happened to me recently after a system crash - (the problem about not enough information.....). All I did was uninstall the device and W2k reinstalled it on reboot and it worked fine. You may also want to check your IRQ usage - w2k does some weird **** with the IRQs (I had USB, MX300 and NIC all sharing IRQ 10). Morto.

Hi. I had the same problem as this with a BP6 and 2 x 400 Mhz celerons. I tracked the problem down to the MX300 soundcard drivers supplied with 2114...... It would only freeze when I used anything that used the directsound component of the drivers. To fix it, go to adjust audio properties and set the acceleration level to emulation (as far left as the slider will go).