From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
After I installed Fisher, and mounted a (separate) disk with a FAT32
partition, I am unable to read the disk when I boot to DOS/Windows 98.
Reproducible: Couldn't Reproduce
Steps to Reproduce:
I installed Fisher using the feature that finds old Linux partitions and
uses them. The disk that is messed up should not be touched by this. It is
a 8GB disk, formatted in one partition as FAT32. After Fisher was
installed, I mounted it, and perhaps executed ls on it, but didn't write
anything. When I rebooted to Windows 98 the first time, it tried to run
SCANDISK on it, but it crashed totally, before it was able to start
checking it. I was unable to start Windows until I physically disconnected
the bad disk. When I boot to DOS and run DIR on it, the screen is filled
with mainly grabage, and a few entries that look like files with bad
names, but nothing of the original, and in the end it says there is a
partition error. Norton Disk Doctor was also unable to read it, and did
not want to try to fix it. I can still mount and read it in Fisher,
though, and I was able to copy out all the important files. When I try to
run the fsck for DOS, it does not find any errors. I mounted another 45GB
FAT32 disk without any problems, and I have also copied both to and from
it. I use a HPT370 controller. Linux was installed on the first disk on
the first port, the messed up disk is the second disk on the first port,
and the 45 GB disk is alone on the second port. If there is a program I
can run to get a copy of the partition table or anything else that might
help you, please let me know.

Just FYI, I've had the same problem with Fisher and Win98. The partition setup
I ended up with is as follows:
Disk /dev/hda: 255 heads, 63 sectors, 1027 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 16 128488+ 6 FAT16
/dev/hda2 17 19 24097+ 83 Linux
/dev/hda3 325 1027 5646847+ c Win95 FAT32 (LBA)
/dev/hda4 20 324 2449912+ 5 Extended
/dev/hda5 20 315 2377588+ 83 Linux
/dev/hda6 316 324 72261 82 Linux swap
Yes, the partitions were originally out of disk order.
Unfortunately, I didn't have the foresight to make a list of the original
partition boundaries. Although Windows (off /dev/hda1 or a boot floppy)
apparently has problems with the file allocation table on /dev/hda3 (namely, the
directory listing looks like the Matrix), Linux reads it just fine.
I haven't been able to reproduce this bug--for lack of trying. When I do the
ol' Windows format/reinstall on /dev/hda3, I'll try installing Wolverine, just
to see if the bug persists in the newest beta. However, I have a feeling that
the gremlin that popped up in the Fisher install has done its job and gone home
for a nice cuppa tea.

Partitioning seems to causes lots of problems on certain systems, I am sorry you
encountered these issues.
I am not sure what we can do at this point to help. I will close the bug as
NOTABUG (closest match to the situation we have) but please reopen if you have
new problems or information.