fdisk/mbr

This is a pretty serious error. It indicates that Windows
encountered a defect in your PC's memory, motherboard, or
a hardware device (serial port, parallel port, video card,
network card, and so on). The problems you're encountering
can occur with any version of Windows. Since Setup was able
to check components and disk space, the problem is most
likely in your memory or hardware, not your hard drive.
Here are some troubleshooting steps that may help you figure
out what's wrong. First,try a few software diagnostics.
Shut down the system and remove all nonessential plug-in
cards--modem, network and sound--leaving the video card
in place. This should leave you with just your hard drive,
memory, and motherboard devices. Run Setup again, and if it
fails the same way, you can suspect memory or the motherboard.
If you can, swap RAM with another system and rerun Setup.
If the system still fails, then your motherboard is bad
and needs to be replaced. If Setup proceeds successfully
without the expansion cards you removed, the motherboard
is probably OK, and it's time to identify which card is
causing the problem. Shut the system down and install
each card in turn, restart the system and run Setup again.
Repeat the process with each card. If installation fails,
the last card you installed is likely the culprit.

Fdisk is operating properly.

The MBR switch runs a special sub-routine in fdisk. After it runs, it returns to the DOS prompt.

As to the install error, I agree with the other responses, it looks like a hardware issue.

I have a couple of RAMmodules that pass the POST test at boot, but do not function in Windows, so that is a good place to start.

If you do have a virus concern, I would start with a known clean, and write protected startup disk.
Run fdisk/mbr
run fidisk and delete all logical drives and partitions.
re-boot.
Run fdisk again, and define partitions as desired.
Re-boot.
Format at least the C: drive.
Install Windows.

Chas

As mentioned this can be caused by bad or mismatched ram. If you have more than one dimm modules take out the first one and put the second one in the first slot.

Most of the time incorrect BIOS settings is the cause. Disable extra cache settings for things like video and especially if specific memory locations are cached or reserved. Hard drive/CD DMA mode settings and CPU over-clocking can all be a problem.

Strangly enough CDROM vibration can also cause this this exact same error. I usually copy the setup files to a folder on the hard drive and run the setup from there. Plus in the future anytime the win98 files are needed it will remember that location and you won't have to look for the disk since the files are already on the drive.

I agree with the idea to remove the extra cards from the system and install those one at a time after the windows is up and running correctly. There's sounblaster cards that cause a simular error with certain chipsets durring the installation process. After windows is installed the soundcard is no problem.

Computer has Creative Labs SBLive! and the Emu10k1.vxd has not been loaded.

Locate and rename the file Emu10k1.vxd file and rename it to Emu10k1.ch.

swapped the ram around and one was misbehaving.everything loaded ok after.
Thanks everyone but popeye doyle gets the points.
steve