slkh

My respond to BladeRunner, Yes, you install the ASPI layer 4.57 first. Then reboot, then install the ASPI layer 4.60 then reboot. Then install ECDC 4.0. I think ECDC 4.0 overwrite the ASPI layer with its older version (Just guessing). For me, I would make sure the problem is dead, I reapply ASPI layer 4.60 before I reboot my comp again. That is my sequence of doing it. By the way, please don't install DirectCD. (Actually you can't get DirectCD to install anyway). It cause a lot of Kernel mode exception error (Blue Screen).

Update your ASPI layer before you install ECDC. It is a must! Alternatively, download the patch for ECDC for Windows 2000 from Adaptec. Basically doing the same thing, the small patch program install the latest ASPI layer. Latest ASPI layer can be downloaded from http://win2kbox.cjb.net/

Your system seems a little below the spec. (Actually to run smooth, you need PII 400 or equalvalent). Unfortunately again, your Voodoo does not support Moment Conpensation. These might explain why you get bad performance. Try lowering your resolution and see if it works? One more thing, you need to update the IDE ATA/ATAPI controller with the one that provided by the CD that came with your mainboard in order to enable the UDMA mode (IINM). Or better still, go and download the newest version from your motherboard manufacturer. Good luck

I experience a lot of random lockup. Eg: while railing someone, it just suddenly hang the system and continuos railing sound goes on and on and on when I set /r_smp 1. It does run and noticable improvement over /r_smp 0 mode. But it is just not stable enough for me to play. I rather sacrify the performance in exchange of stability.

Depends a lot on your resolution and depth of colour. I get approximately 42 fps for 1024x768 (trilinear + 32 bit colour) on my 2 x Cel300A@450 Mhz But experience random lockup more often. If I run on /r_smp 0, it rarely (can almost say never) lockup my system. -- My Configuration P6DGU, 2x Cel 300A@450 Geforce DDR 32 Mb 1024x768 32 bit colour Trilinear mode.

2D works well, but straight I launch Quake 3 Arena, it hang my system. 5.06 for NT4.0 give garbage screen on win2k

Plustek Driver for NT4.0 works for me. Alternatively, look around http://www.plustek.de/drivers/2000USB.exe

It looks like a very good defragmenter. It defrag rather slowly. When it start to defrag my MFT, there is no disk activity for more than 15 min, I decided to CTRL-ALT-DEL my system to shut down the process. But it doesn't listen to my command, I press the HW Reset, and my partition can no longer be found. And there goes a few Gb of my data.

>New copies of Office2k, however, which >incorporate the SR-1 patch already, will be >required to register within 50 occasions of >opening the program, after those 50 times >the program will cease to work. You mean electronic registration? What happen I do not have internet connection or BBS or modem connection but I register through the card that include in the package? Will Office 2000 automatically update its code so that it will continue to work after 50 times?

What is the "THIS" game?

I don't have AIM installed but have the page locked program.

I have Annihilator Pro. It used to be quite dark. But after I totally remove the Creative driver and install Nvidia driver and it is okay.

AT motherboard support ACPI? I haven't known that actually, but as far as I know AT motherboard can't switch off itself because of its power supply.

I think I am going back to 3.78 again. 3.81 although the benchmark looks great but often hang my system when I play Quake 3 after a few games (usually 5 to 8). When I force Win2K to shut down the quake 3 process when it hang, it gives me blue screen. Page locked or something like this.. Never happen to me in 3.78.

I usually get a hang sometimes in the game, and when I shut down the quake3 process, it turn blue screen. "Page locked" or something like this. For your case, I have this problem before and it has something to do with my ASPI Layer for my CD Writer. After I update my ASPI Layer and apply the patch for my DirectCD 3.0 (85), it finally went off.. The newer patch for DirectCD 3.0 doesn't solve my IRQ less or equal problem.

My flatmate have this problem too while I don't have this problem. It quit into the desktop with a message saying something like insufficient memory to load xxxx..... The difference between two system is that I have 256 Mb of SDRAM while he has 64 Mb of SDRAM. I think this could be the reason. Not sure about your case.

Yes I have a Supermicro P6DGU with dual processor capability. Both Slot 1 is installed with Celeron 300A in it. I can't go into suspend/hibernation mode because they are simply not available in the selection. However, if i press on the power switch, it will say my writer is preventing my system to go into hybernation mode which I believe it should be because the proper patch for the directcd that i am using is not out yet. Anyway, the hibernation/suspend features isn't important for me. Shut Down is especially when i need to shut down the system remotely.

SMP system P6DGU Dual Celeron 300@504 Mhz Geforce DDR 32 Mb 256 Mb SDRAM Nvidia Reference Driver 3.78 It works fine on my system. Quake 3 running smoothly, occasional lock up when starting the game (probably Nvidia driver not fully optimized for SMP). Unreal ran fine on my system, and infact it flies. MS Flight simulatro works fine.

Alright guys. I have narrowed the problem down to just three possibilities. 1. I have this problem only when I hyperclocked my processor. 2. When I burn my CD (solved when I update my ASPI layer to the latest version) 3. When I get a lockup and manually end task on some program (particularly Quake3). My solution:- 1. I don't hyperclock my processor but overclock to some stable speed instead. It is better to sacrify a few Mhz than to get an unstable system. 2. As said, get the latest ASPI for my CDR. Sometimes it reboot when I don't burn CDR at all. It restart when I click My computer.. Problem solved when update ASPI. 3. Can't do anything yet. I think it is my Nvidia Reference driver 3.78 which is not mature enough for my SMP system.

Takes a little bit of time for the drivers to mature. I do agree some games doesnt work on Windows 2000. But it has nothing to do with Windows 2000, it is because the games are not written specifically for Windows 2000. Can't blame Windows 2000. Neither can blame the games developers because when they release the product, Windows 2000 isn't born yet. Well, so far, most of my crucial applications does work on my Windows 2000. Occasional lock up with some of my games, I suspect my drivers or the games need patches. But will eagerly wait for its update or patches for Windows 2000. For those who wants everything to work fine? Go for Windows 98. For those diehard fans of Windows 2000 that wants things getting running, you are in the right forum

Hibernation is just a feature. I do not find it useful at all. Copying everything into the RAM takes time, copying from the hardisk to the RAM takes time again. If suppose you have lots of RAM, say 256 Mb or 512 Mb (which is quite common), it would take longer than a fresh booting up.

Everytime such a things happen when a new OS is introduced. Remember when switching from Windows 3.11 to Windows 95? No driver, no support, very slow, games don't run as smooth, cannot run PCTools, cannot run Norton Utilities, etc, etc... At the end, everyone adopt it. I think the same thing happen again in Windows 2000. Everyone complaining slow, bad drivers support, etc, etc.. In a few months time, you will never want to switch back to 9X again.

Hibernation? I don't think it is a cool features at all. It store everything in the memory into your hard disk. Say if I have 256 Mb of RAM or 512 Mb of RAM, the copying to the disk process + the copying from disk to RAM process would already take more time than a fresh reboot. Useful for those who have small amount of RAM, but again, with small amount of RAM, everything run so slow, except your hibernation.

Maybe some kind of auto-defragmenting mechanism going on? I do realize this as well. But the disk activity wasn't very heavy, it blinks from time to time (approx 3 sec one blink). But doesn't quite bother me.

I have P6DGU, your mainboard's brother, and UWSCSI is natively supported by Windows 2000.