VOGONS


First post, by Kahenraz

User metadata
Rank l33t
Rank
l33t

I'm trying to figure out exactly what I did and what's happening with this drive. I haven't dealt with it in a while, so this is somewhat of a surprising situation after working with it a few months later.

This is a 500GB SSD that has been partitioned to boot into DOS and Windows 98, with a shared logical partition at the end. There is also a 1GB partition at the beginning of the drive which does nothing other than run GRUB4DOS. The second DOS partition runs FreeDOS and the third is Windows 98. The partitions were configured using GParted. GRUB4DOS is booting from DOS 7.1.

The mystery is how drive letters appear at the command prompt, which files are visible, and the actual drive letters vs what shows in FDISK.

At the GRUB4DOS command prompt (DOS 7.1) I can see the DOS and WIN98 partitions as D and E. DIR on D shows and empty drive and E shows files for Windows 98. However, drive D (FreeDOS) is NOT empty, and I can boot to it and see it's files from its own command prompt, but not from DOS 7.1.

I also examined the drives using FDISK, which shows the DOS and WIN98 partitions as drive letters E and F... but there is no E and F. They are D and E.

I'm still trying to sort it out. It's all very bizarre.

The attachment 20221118_065319_resize_17.jpg is no longer available
The attachment 20221118_071404_resize_79.jpg is no longer available
The attachment 20221118_071445_resize_28.jpg is no longer available
The attachment 20221118_071420_resize_77.jpg is no longer available

Reply 1 of 1, by Kahenraz

User metadata
Rank l33t
Rank
l33t

This ended up being the same 48-bit LBA issue that I had encountered a few months ago. This is why I had installed FreeDOS on the DOS partition. I hadn't installed it on the BOOT partition as well, and had forgotten about it.

Trying to figure out the cause of data corruption in Windows 9x

I also had a problem with an unformatable drive letter appearing in Windows 98. This ended up being due to the extended partition type being set to 0x05 by fdisk in Linux by default. Changing it to 0x0f instead allowed it to be an extended partition type that Windows knew to ignore.