RJARRRPCGP

Slowness is USUALLY NOT A HARDWARE PROBLEM, *unless* it's a bad HDD, bad IDE cable or bad IDE controller. The first thing I would do, because it mentions I/O error, is to check the system event log for disk errors or IDE controller-related errors. You may have a bad HDD.

Those mega hdds you're referring to are the result of stiff competition and end-user demands for mega storage .... One basic reason why there's no longer 10/20GB hdds being produced is due to disk surface density ... I have not seen desktop drives with surface density lower than 80GB per platter in production (1 platter = 2 surface; each surface approx 40GB) in the last two years ... Newer drives are made using 200GB platters ... It is simply not cost effective to mass produce smaller drives where there is little demand ... If you really do feel strongly about monstrous mega hdds, then there is one alternative that I can think of ... get a new hdd make and model that you trust and perform LBA cut-down to the size that you like .... Perhaps making brand new 80GB hdd into a 10GB/20GB/30GB that you want ... There's several freeware tool that can do this ... This may be usefull on older systems with BIOS with certain usable hdd limits (ie. 32GB or 128GB) ... Rgds I have a Western Digital Caviar 40 GB laying around that was made in 2006!

You can get a brand new 40 GB (or fairly new at least 2006) and look for a jumper setting to limit the capacity to 32 GB. Also, even the bigger HDDs likely have a jumper to limit it to 32 GB. The pre-2001 motherboards likely are fine up to 32 GB. There's an issue where HDDs bigger than 32 GB cause a HDD detection failure or the OS gives you disk errors for the remainder of the HDD and ScanDisk reports bad clusters. If you always get disk errors after a certain cluster under Windows 95, it's a known issue, according to Microsoft. If you always get disk errors after a certain cluster under Windows 98, it's the BIOS' fault!

Copyrights expire in 95 years, or 125 years! That's great! I would be lucky to be alive and have Alzheimer's!

Is this a Firefox cookie handling bug?

I agree, otherwise it should give you an error message about the product key or CD drive being invalid. A lock up sounds like your system.

OK, I just installed Firefox 2.0.0.6 from scratch and despite I reformatted the HDD, after being logged into the message board, I'm always logged out on the front page and this causes the front page part to display "Sorry, you cannot comment to this news post because you do not have permission to do so.".

I dunno, but shouldn't the GRUB bootloader prevent that from occurring?

That message is known to occur if your processor core is OC'ed way too much or you have way too little Vcore. In those cases, Windows isn't corrupted and if you lower the processor clock or increase the Vcore, Windows will boot like nothing bad happened. Was that PC's processor OC'ed at all? It may be because of bad PSU a bad processor or bad RAM.

You must unregister the following DLLs then reboot: regsvr32 /u wintrust.dll regsvr32 /u initpki.dll regsvr32 /u dssenh.dll regsvr32 /u rsaenh.dll regsvr32 /u gpkcsp.dll regsvr32 /u slbcsp.dll regsvr32 /u cryptdlg.dll Warning, Windows File Protection will be triggered after you reboot. Windows File Protection will think that files were modified! They weren't modified! So just click "Cancel". Then re register the following DLLs: regsvr32 wintrust.dll regsvr32 initpki.dll regsvr32 dssenh.dll regsvr32 rsaenh.dll regsvr32 gpkcsp.dll regsvr32 slbcsp.dll regsvr32 cryptdlg.dll

The problem may be related to this: http://support.microsoft.com/kb/822798

The server is responding, but is messed up.

700?! I'm gonna get a heart attack! You might as well be thinking about a GeForce 8800 GTX! Also, BTW, you can get a better video card for less than $300! Think something like GeForce 7800 GS or a Radeon X1650 Pro. Spending $700 for a video card that's not pixel shader 4 or 3 compliant don't make sense!

I see a dot in the screenshot. Dots often are caused by the VRAM on the video card being OC'ed too much.

Sounds like anti-processor overheating protection being triggered! Especially if it wasn't cleaned by himself! Let me guess, possibly major dust.

But, with newer chips, they may actually be sold underclocked, for example, an Athlon 64 3700+ may be an underclocked Athlon 64 4000+! That may be why some people can raise the frequencies far beyond stock without any problems and not touching the Vcore! It's not like the 486 days, where the chips may get killed just from a 10 mhz raise!

I heard that usually isn't stable! Also, trying to use that shell can cause a BSOD!

Give me a break! Windows NT-based OSes are mostly impossible to break into! While it in most cases was a piece of cake to break into Windows 98 SE systems! All I needed was my Windows 98 SE CD-ROM and run the Poledit.exe utility!

Known issue, but it's only known to occur if you're installing non-Microsoft drivers. Have you tried a search for my posts?

Regedit search for SFCDisable and change the value to ffffff9d restart windows That method reportedly is obsolete! Because of Microsoft disabling it since Windows 2000!

improving the i810 drivers alone won't be good enough to add more color depth or resolutions. the i810 chipset hardware itself will also have to be modified to also support higher color depths and screen resolutions. Even the XP drivers for i810 hardware only support up to 24bit true color mode Unless it's older than 1999, then it likely supports 32-bit in 2D mode. It probably won't in 3D mode and the symptom of that being unsupported is you get a 3D init failure error message from a game and the game may accuse you of having a corrupted DirectX installation. That's at least the case with Voodoo 3s.

That sounds like wrong voltages. Also, some motherboards may do this if you're cranking up the Vcore! I have a MSI 845E Max that does similar if I try to max out the Vcore in the BIOS. Were you overclocking? Sounds like the crud I gotten when the BIOS don't have the right Vcore set. This may be because the BIOS was being stubborn by not returning the frequencies back to stock while returning the voltages back to stock. Either way, you're SOL, because even the jumpering and CMOS battery removal fails.

Reconnect the IDE cables, reconnect the HDD power connectors and try again.

Your problems may be because of DMA being disabled. With Windows 98, DMA is disabled by default!

Likely that the RAM is bad, incompatible RAM was installed or a bad RAM slot. I gotten STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA followed by REGISTRY_HIVE_FAILURE or REGISTRY_ERROR BSOD on an IBM PC300 GL before, because of a RAM issue.