Dragon-Lord

I posted this as a new topic in the hopes that some of you who are super-frustrated with W2K (as I was) might find an answer or two within. :} I am one of the people who has been having problems (no eax, crackling, etc.), and I now have some concrete info to provide based on months of testing, and especially the last few days (success!). As part of my upgrade to Win2K, I added a second P3 processor to my dual mobo (SuperMicro P6DBS rev 1.02, bios 3.0). The two processors were bought at the same time and at the same place (450mhz PIII, first generation). I enabled MPS first, then ACPI, and was running SMP. I have had constant IRQL crashes, and seemingly random BSODs (kmode, irql, ntfs, you name it) ever since. Geforce freezes, IE freezes...and on and on. I have a hurricane of wind blowing across every component and nothing is overclocked, still no luck. No bios change made a difference, and no driver updates stopped the overall problem. Since I know the system was stable under win98se (single processor), or at least as stable as Win98 can be, I finally started downgrading the system to see results. MPS1.4, dual processor, no APM...no change, but confirmed that only my USB and Ethernet are sharing IRQs. Standard PC, single processor...solid as a rock. EAX works on my SBLive. BSOD and crashes have stopped, etc. Now, even though I suspect the mobo at this point - Supermicro support is non-existant and their bios manual is nearly useless (I got more useful info from the Abit Be6-II manual for the machine I built for my wife!) - I have just installed the new LiveWare drivers and will begin upgrading the machine to first, single-processor ACPI, then, if that works well, dual processor ACPI again. I am hoping the new LiveWare drivers stop the crashes at SMP/ACPI, but somehow I doubt it. If it doesn't, then I assume the mobo just can't handle everything I am throwing at it. I find it hard to believe that there are remaining issues at the OS level with W2K Pro(Purchased Retail, beta SP1 1.59RC) with SMP/ACPI (both?), so the LiveWare or Geforce drivers failing under SMP/ACPI(both?) are the next most likely suspects. Now that I *can* get my system to be rock solid, I thought I would share the details of my journey in the hopes that it might help others who are at their wits end. Most likely, I will be replacing this mobo in the near future for another dual PIII ready one, hopefully overclockable. Any recommendations (supermicro loses because of the lack of support issue)? :} ------------------ W2K Pro(Purchased Retail, beta SP1 1.59RC) Supermicro SBDBS r1.02, Bios 3.0 (dead on-board SCSI chip) 2xPIII @450mhz (not o/c) 256mb PC100 Ram in 2 sticks 3xIDE HDs (50gb total, all NTFS) and 1 Pioneer IDE DVD-ROM (all UDMA) Geforce 256 DDR (32mb), CL AnnPro (DET v5.32) SBLive! Platinum with digital breakout card (LW3.0) 3COM 3C905B-TX 100-base ethernet (newest driver release on 3COM site) SIIG AP-40 UWide SCSI PCI (W2K CD drivers) Nikon LS-2000 SCSI film scanner (drivers now released) Sony SDT-9000 SCSI 4mm DAT (W2K) SAF 4012 SCSI CD-Write (W2K) Iomega Zip 100 SCSI Drive (IO 2.2.1a) MS Natural Keyboard Pro USB MS Intellimouse Optical USB HP Laserjet 6L via USB printing (newest drivers on HP site) Epson Stylus Photo 700 via parallel Rainbow Sentinel Parallel Dongle for LightWave6

I am one of the people who has been having problems (no eax, crackling, etc.), and I now have some concrete info to provide based on months of testing, and especially the last few days (success!). As part of my upgrade to Win2K, I added a second P3 processor to my dual mobo (SuperMicro P6DBS rev 1.02, bios 3.0). The two processors were bought at the same time and at the same place (450mhz PIII, first generation). I enabled MPS first, then ACPI, and was running SMP. I have had constant IRQL crashes, and seemingly random BSODs (kmode, irql, ntfs, you name it) ever since. Geforce freezes, IE freezes...and on and on. I have a hurricane of wind blowing across every component and nothing is overclocked, still no luck. No bios change made a difference, and no driver updates stopped the overall problem. Since I know the system was stable under win98se (single processor), or at least as stable as Win98 can be, I finally started downgrading the system to see results. MPS1.4, dual processor, no APM...no change, but confirmed that only my USB and Ethernet are sharing IRQs. Standard PC, single processor...solid as a rock. EAX works on my SBLive. BSOD and crashes have stopped, etc. Now, even though I suspect the mobo at this point - Supermicro support is non-existant and their bios manual is nearly useless (I got more useful info from the Abit Be6-II manual for the machine I built for my wife!) - I have just installed the new LiveWare drivers and will begin upgrading the machine to first, single-processor ACPI, then, if that works well, dual processor ACPI again. I am hoping the new LiveWare drivers stop the crashes at SMP/ACPI, but somehow I doubt it. If it doesn't, then I assume the mobo just can't handle everything I am throwing at it. I find it hard to believe that there are remaining issues at the OS level with W2K Pro(Purchased Retail, beta SP1 1.59RC) with SMP/ACPI (both?), so the LiveWare or Geforce drivers failing under SMP/ACPI(both?) are the next most likely suspects. Now that I *can* get my system to be rock solid, I thought I would share the details of my journey in the hopes that it might help others who are at their wits end. Most likely, I will be replacing this mobo in the near future for another dual PIII ready one, hopefully overclockable. Any recommendations (supermicro loses because of the lack of support issue)? :} W2K Pro(Purchased Retail, beta SP1 1.59RC) Supermicro SBDBS r1.02, Bios 3.0 (dead on-board SCSI chip) 2xPIII @450mhz (not o/c) 256mb PC100 Ram in 2 sticks 3xIDE HDs (50gb total, all NTFS) and 1 Pioneer IDE DVD-ROM (all UDMA) Geforce 256 DDR (32mb), CL AnnPro (DET v5.32) SBLive! Platinum with digital breakout card (LW3.0) 3COM 3C905B-TX 100-base ethernet (newest driver release on 3COM site) SIIG AP-40 UWide SCSI PCI (W2K CD drivers) Nikon LS-2000 SCSI film scanner (drivers now released) Sony SDT-9000 SCSI 4mm DAT (W2K) SAF 4012 SCSI CD-Write (W2K) Iomega Zip 100 SCSI Drive (IO 2.2.1a) MS Natural Keyboard Pro USB MS Intellimouse Optical USB HP Laserjet 6L via USB printing (newest drivers on HP site) Epson Stylus Photo 700 via parallel Rainbow Sentinel Parallel Dongle for LightWave6

Thanks! I had heard the gf2 drivers were still unbaked. glad to see you found a solution. :}

Since D2 only runs in D2D mode, and a slightly enhanced D3D mode, what is the big difference? I have a geforce DDR and some v2 sli boards sitting on a shelf. Why would I want to run D2 in glide over my geforce? Enlighten me please? :}

even the d3d version is 640x480, so be prepared to be disappointed even when it is working. I have a 21" monitor too and such a low resolution does indeed suck. I like it better at the 2D version, though, and there are people pushing for a mip-mapped D3D version (it wouldn't change the art resolution, but such art would scale and smooth better in an upres). Honestly, the gameplay in Diablo 2 is great, but Darkstone (all d3d) with FSAA on (you can't change res in DS either, but you can put FSAA on!!) is gorgeous on my 21". I like the 3d nature of the game too. Diablo 2 is one view only...weak. :}

I just saw that a patch to Diablo 2 is already out. I didn't see this bug listed as fixed, so that may mean it is/was driver related. :}

this same bug was in the demo. The Direct3D accelerated version is the key here. If you run it in DirectX 2D view only, the game will run and close and run again without crashing. Now, this may be fixed in the v5.30 drivers, so try those as well. Future patches (of game and drivers) should alleviate this. :}

Have you re-installed the game compatibility updates for W2K? Also, this happened to me until I moved my SBLive to a different slot. So, you might try that. :}

your TNT2 is overheating. The symptoms you describe are classic failures due to overclocking. If you aren't overclocking your TNT2, you'll need more cooling for it (or return) or your system. If you are overclocking, stop it!, or reduce the amount a bit. Hope that helps, :}

Capt'n, we're gonna need mo' power!!! :} [This message has been edited by Dragon-Lord (edited 26 June 2000).]

No, but the Direct3D enhanced mode might respond to forced FSAA in the latest detonator2 driver set. For example, DarkStone (which is all D3D) also has a fixed resolution, but with FSAA on, it looks GORGEOUS!!! Let us know if Diablo2 (final, not beta) responds to FSAA. :}

Both of us have SMP systems, my guess is that the benchmark timing routine only sees 50% of the CPU (since the app would be split across two CPUs by NT), or something. I'll do a test with CPU Affinity on one processor and see if it makes a difference. As long as my Q3A plays well...the rest is just braggin' rights. ;}

I believe the problem is with 3DMark2000 itself. It crashes out many times while running, etc. My guess is that we should wait until they release an updated version. :}

I am using Quicken 99 (since a lot of people say Quicken 2000 is a nightmare) and doing exactly what you want to do with no problems. There is a new Iomegaware on the iomega site 2.2.1a or something, try that! :}

Another option: Make sure machine with two nics is running Win98SE. One NIC is connected to the cable modem with default settings. Check to make sure you can see the internet and everything is working fine. Talk to your ISP if it isn't. The other NIC connects directly to the hub (or connects directly to the other machine with a crossover cable). Under Add/Remove Programs, make sure Internet Connection Sharing is installed. Run the Internet Connection Wizard and answer simple questions, do what it says, reboot. Connect second machine to hub (network needs only default settings) if not using crossover cable mentioned above. Use floppy created by Internet Connection Wizard as previously instructed by Internet Connection Wizard, then reboot. Enjoy. :} PS Under W2K it is as easy as checking one box. Win98ME should be just as easy as W2K.

the last driver set passed WHQL compliance too, so I am not holding my breath. That one incident ended any hope I had that WHQL/WDM approval would actually mean something. fingers crossed (but turning blue by now), :}

From above: What are you doing with the geforce1 on a regular basis that I can't do with the TNT2(albeit slower)?). LightWave 3D 6 and Project:Messiah My Geforce DDR made a HUGE difference in these high end apps as compared with my TNT2Ultra. I can Q3A and LW3D on the same system...very nice. :}

I read somewhere that this is a known bug in the latest detonator drivers. Turning off the mouse shadow (of all things) is supposed to fix the problem until new drivers are released. I hope that helps, :}

SLKH, I was using an AGP aperture of 256, because I have 256mb of ram on my Supermicro mb. By dropping it down again to 32 or 64, the hiccups seem to have stopped with my system. Also, I had made some John Carmack-recommended geforce-related changes to my Q3A config file. By deleting that version and rebuilding it from the new version of Q3A v1.17, my performance has increased as well. I still get the SMP hit, but I am leaving SMP on for now. The saga continues, :}

You know what else is wierd? Now that I run the (oddly slower) SMP 1 mode under the realtime switch, I get the occasional quick sound/video "hiccup" when playing Q3, but no more freezes! Weird. The game actually behaves like it wants to freeze, but the system won't let it. Go figure. Also v5.25 has been MUCH better under Win2k. IRQL BSODs have seemingly disappeared. I still have a regular KMODE crash and an occasional BAP_POOL crash but things are getting more and more stable every release. I really have high hopes for new SBLive drivers, the final IE5.5, and final W2K SP1. I think that will make a HUGE difference. :} :}

Tried this and SMP works now!!! Thanks! However, I now get the same huge frame drop that was mentioned above, so back to SMP 0 for me...weird. I am using Geforce DDR on Nvidia 5.25 drivers. Which ones are you using? I have AGP 2X, SB enabled... :}

hibernation is spelled well...hibernation. try your search again. :}

nvstat.sys installs in the device manager under non-plug and play drivers as "Nvidia performance analysis tool"...hmmmm. :}

Yes, Ronin, the SBLive drivers suck....hard. Even the latest Creative FAQ states that EAX won't be implemented until the next driver release. Also, ACPI mode (combined with SMP?) really throws these drivers for a loop (IRQL, Kmode BSDOs). These are well-documented throughout these and the creative message boards. My board works fine as long as I am doing MIDI or it is just playing a default sound when I am clicking in IE, but try playing an AVI fullscreen with high quality audio, MP3s for a half hour or so, or any game with a lot of sound mixing (Q3A) etc. and these drivers will fail, crackle, freeze, crash, etc. on many systems. :}

none of the new Nvidia drivers support SMP (officially, according to their website!), so I wouldn't bother for now. I am sure that the hit you are seeing is a result of a bottleneck of some kind (FSAA code?) in those drivers. I too am looking forward to SMP support in the drivers (soon?). :}