RJARRRPCGP

Could you check your C:\MSDOS.SYS file? It must contain "SystemReg=0" line... I do know that a registry check can fail if you have a hardware RAM configuration problem. (such as too aggressive RAM timings defined in the BIOS or OC'ing it too much) Gape, why do you think this is occuring? I thought that the registry checker wouldn't report an error unless the HDD was corrupted. Is it actually rejecting the service pack files?

Cool. That's hosted by the same ISP I'm with!

Yep. In fact, 133 mhz is what Athlon XPs are supposed to be at for the FSB.

You're probably required to change a jumper. The FSB probably is controlled by a jumper. 100 mhz probably is the default and if you have an Athlon XP, change that to 133 mhz. Do you still have the motherboard manual?

Unfortunately, like with earlier versions of Windows, you're probably required to reformat the HDD then reinstall Windows. Because there's a good chance that the "repair" install feature won't work or work properly. It also may demand a password that you didn't put in, thus being locked out of the "repair" install feature. Sorry.

Actually, if it's unstable when using more than 1 RAM module, the RAM you inserted is incompatible with the motherboard, bad or you have a bad RAM slot. May also be because if an insufficient power supply. If you're overclocking, I heard that using more than 1 RAM module can cause your RAM to overclock crappily. If NT-based Windows versions give you file corrupted error messages and file not found error messages, I can guarantee that you have a RAM chip or RAM slot problem. Did you check your voltages? Also if you run Prime95 and Prime95 fails, your CPU likely isn't stable!

Your video drivers probably arn't installed or configured properly. You're required to install the drivers for your chipset before installing the video drivers!

Sorry about that. I was just saying that I decided to test 56.72 a while ago, because I switched back to a Nvidia from an ATI. Then I noticed that. Wonder if the 5xxx versions require a GeForce FX for good performance?

I don't like 56.72, because it causes 3D Mark 2001 SE to start stuttering!!

It's probably underclocked if it's at less than 1.60 ghz. Can you use 133 mhz FSB stably?

Lower the maximum simultaneous HTTP connections for the web browser.

This was when I decided to test 3D Mark 2001 SE based on the driver version number that had the best results. 44.03 is the version number of the Detonator drivers that gave me the best 3D Mark 2001 SE results with my eVGA GeForce 4 Ti 4200 64 MB video card. Thus I decided to try the Windows 9x version of 44.03 under Windows 98 SE then that's when I noticed this phenomenon.

Windows 98 SE for most of the time seems to give me better benchmarking results, especially with Nintendo 64 emulation, but 3D Mark 2001 SE always gave me a lower final score than when running under Windows 2000 and when running under Windows XP. I dunno why.

Cars and operating systems aren't the same thing. Firstly, you don't write software and drivers for a car. A car serves one purpose. To get you from point A to point B and so forth. Games and high end software are designed for high end good quality platforms. No game that requires a CPU of 1GHz or faster and 256MB or more RAM should EVER support junker Windows 9X. Applications designed to run as background tasks shouldn't support Windows 9X either primarily because performance is critical with background tasks as you want background tasks to take up the least resources as possible since they are running all the time. Only the most simple applications that don't run as background tasks maybe should still support Windows 9X. Applications like old school 2-D games and eductaional games for little kids that don't require many resources to run. Actually, you should have at least 1.2 ghz for Windows XP and Windows 2000.

I have 56k dial up and I still have dial up support after using the FDV file set and HFSLIP.

That's because you have have the 32 GB BIOS limitation (PCs older than 2001) or a WinME format utility bug. Windows NT 5.x bypass bios to access ide drives and others drive too, like sata, it's for that you need driver disk/splitstream drivers on cd. It still requires a later BIOS, AFAIK.

If it locks up at "Verifying DMI Pool", the problem likely is caused by just having the wrong HDD jumper settings. (if still using PATA) FYI, "Verifying DMI Pool" isn't an error message at all.

I suggest that you get a brand new 56k modem or use a later driver, if possible. Windows XP 64-bit Edition possibly installed the wrong modem driver and thinks it's the right modem driver! I had that problem before with a PC and Windows XP would keep on giving me a BSOD and rebooting until I rebooted in safe mode then install the driver that came with the modem.

You probably gotten an internet virus. You're required to have a firewall! You probably weren't running a firewall!

Probably the wrong IDE driver (not for your chipset) or the HDD isn't being detected at all, even by the BIOS.

Welp, the Windows 2000 Pro with the newest fileset from FDV, HFSLIP and the CD burn was successful. I was worried that I wasn't gonna make the CD right. Appears that the quick launch feature is back with this one. This was with an LG CD-RW drive and a Sony 700MB and 80 minute CD-R. I decided to burn it at 40x, because I was worried about the CD being corrupted.

Even when I'm using a GeForce 4 Ti, I use DirectX 9.0c, because some games still use DirectX 9, even when pixel shader 2 isn't being used. Mine don't support pixel shader 2, either. It's fine to install DirectX 9 on a "DirectX 8.1" (don't have pixel shader 2) video card.

That's because you have have the 32 GB BIOS limitation (PCs older than 2001) or a WinME format utility bug.

Warning, this link possibly bad. It redirected me to a site owned by Yahoo.

Can you stop the BS. I tried opening IE over and over and didnt get too far: Here a file box started opening........?????? Start menu gone Firewall frozen Icons a-bye-bye I had to kill a few windows before i could use printscreen it complained not enough memory, all in all i didnt like it but didnt have to reboot The symptoms you have are probably a sign of not having enough virtual memory.