rloew

I have been seeing this intermittently with the regular 52.9.0 for months now. One Core appears to be maxed out. Sometimes killing the browser works, other times I may have to reboot.

What drivers, if any, are in your SYSTEM.INI? The SYSTEM.INI File is processed in the area that froze.

Does that work for Windows 98SE?

Of course.

I have similar problems with the Startech PEXUSB4DP PCI-E USB 2 Card. It typically disables the Video Driver and/or the Ethernet Driver. Once I saw it slow down DOS. Unfortunately, I could not reproduce the problem to debug it. The Card works in Windows 9x if I disable the other Drivers. I think it may be a PCI-E Interrupt sharing problem but I am not sure at this point. It works fine in Windows XP.

Going from 3.5GiB to 3GiB suggests a change of hardware. Did you add or change your Video card?

That is correct. This is not a reason to prefer SP1.

You mean the drivers weren't designed to handle physical addresses above 4GiB. The drivers obviously can handle PAE as the system is using PAE.

RFDISK can create Partitions with any geometry settings. Changing an existing Partition's geometry can be done but would be problematical. It would be easier to switch existing Partitions to LBA access.

I wouldn't count on it. I have seen Short Filename issues with files that are part of a fresh Install. It may depend upon what features you Install. I would have to do a fresh Install to find out which files are involved. Problems occur when the Short Filename is used in the Registry.

Copying the files would not work safely with Windows 9x unless you have a tool such as my XFILE that can preserve Short File Names. Standard copying can cause the Short File name for a given file to be changed on the destination.

Check the power supply.

To be sure, he would have to post the MBR of the original Hard Drive. A new Drive as well as a GPT MBR is blank. Simply partitioning a Drive without making it bootable might not initialize the MBR Code. Mine won't unless you tell it specifically to do so.

It doesn't matter how you run Windows 9x. When it enumerates the Hard Drives, it checks each MBR and puts a signature in any MBR that does not appear to have one.

The four bytes at 0xDC in the MBR is a signature that Windows 9x writes when there are only zeroes between 0xDA and 0xE0. Windows has big problems when the checksum of two MBRs are identical so it adds a signature to new MBRs or if blank. It corrupted one of my Amiga Hard Drives by doing that.