RJARRRPCGP

If it was because of the product key, it probably will be straight. It probably would complain about the product key in the error message. Instead, you got a generic error, thus probably not product key-related. A generic error probably means a corrupted Windows installation or a hardware malfunction.

With the filename mentioned in the error message, there appears to be junkware on your PC. If that's the firewall you're using, I majorly recommend that you uninstall it. Looks like the crap that's bundled with HP PCs. This is common with HP, Compaq and Dell PCs.

Just worried, because of more hotfixes after August 10. My CD from August 18 isn't good anymore, because I appeared to probably have missed at least one hotfix, then I saw another kernel hotfix!

This may be a sign of the motherboard giving the wrong default Vcore. You may be required to set the Vcore manually.

If you check the HDD speeds with HDTach. Or MHDD, which is a low level diagnostic utility, which is available at hddguru.com. If you choose the scan function or watch the KB/s when wiping a hard disk drive. It appears that no matter what, it's never as fast on the other end of the platter. But they can vary. It seems that all the HDD manufacturers can do is to reduce the speed drop when going to the other end of the platter.

Unfortunately, that isn't true. The beginning of the HDD is faster than the end. All disk utilities that measure the MB/s shows that. Most HDDs have a major speed drop when at the end.

I already have the rollup. I probably would be missing a major amount of hotfixes if I didn't!

But, if it gets terminated without an error message, it suddenly disappears, please check your video card driver settings. This problem can be caused by an unstable GPU OC. If OC'ing your video card, try again after lowering the core clock.

Is a version of HFSLIP later than 60810 required for later August Windows 2000 SP4 hotfixes? This is critical, because there's more hotfixes reguarding the kernel! Also, there's more hotfixes reguarding the shell! Thus even with the FDV fileset, I'm affected! I appeared to have missed some hotfixes and there's no September final.

The IDE driver that's part of the Hyperion 4 in 1 package should work fine. Otherwise, you must go to Device Manager to enable UDMA! Look for the "DMA" check box in the entry of your HDD in Device Manager.

About Page Defrag, it appeared that Windows 2000 accepted the pagefile when Page Defrag was done defragmenting then when at the login screen, used the shutdown menu to reboot Windows 2000. If I log in right after it was done defragmenting, then Windows 2000 will complain about the pagefile being corrupted and disable it! In short, if I don't reboot again before logging in, the error message saying that the pagefile is corrupted pops up and Windows 2000 disables the pagefile.

I agree. Also, can be caused by an unstable processor OC.

Sometimes, like a Pentium 1!

1. The boot sector, possibly the partition was wiped out or corrupted by malware. 2. Bad HDD.

That's less likely to do with SATA. Sounds like the other HDD just wasn't as fast.

I'm talking about if Chkdsk automatically runs.

I don't think that Windows Update deleted Windows. If the copy of Windows isn't 100 percent legit, it probably would just display the following message: Cannot Validate The Product Key The product key used to install Windows is invalid. (or similar)

That's because you're required to defrag yourself before reimaging. The imaging software don't defrag for you, AFAIK.

You shan't have any problem with Nvidia. i tried 3 different linux's and all said that my vid card was unsupported and it wouldnt install. Then you're required to wait. It's probably because the current Linux binaries don't support the latest GeForces.

It's probably because Windows got corrupted. The file system probably got corrupted. Sorry. You must make sure that the PC is shut down properly.

Wow! Sounds like Microsoft majorly messed up!

A new PC, then it's likely a buggy BIOS or insufficient power supply. You may be required to set the Vcore and/or VDIMM manually! But, also, if you have a socket A Epox, then it's likely because of bad caps!

I have been wondering, too, when testing nLite for Windows 2000, for slipstreaming DirectX 9.0c. It appears that you can't.

Yes, you shall have told us the motherboard before. Now, enter the BIOS setup and go to the hardware monitoring section. What are the voltages being reported?

Your processor may be faulty. There have been reports of some people's processor failing before. More likely with BSODs.