HoofedEar wrote on 2023-02-27, 21:46:
Any help is appreciated, thanks!
Think different.
Edit: Just kidding. 😜
I'm also half a mac user, so I can see the difference in approaching the situation here.
As Ryccardo said, DOS uses FAT/MBR. You have to take care of different drive geometry systems (CHS, Large, LBA 28,LBA 48 etc).
What Ryccardo says surely is right, but you can also try another approach.
You can make an 1:1 image copy of your old HDD and then write it onto your CF card.
Later on, you can use utilities to change size or add a second partition (recommend).
That way, you can make use of the extra capacity.
a) To make an 1:1 copy, you can use "Win32 Disk Imager" on any 32-Bit Windows.
Just save the device (drive letter) to an image file (say backup.img or backup.dmg).
Then, use that image as a source for your CF card. You can use same program or WinImage or macOS' Disk Utility.
The advantage is, that macOS has image file support since the 1980s.
You can easily mount the backup on macOS like and ordinary drive.
macOS can even read/write 1,44MB floppy disk images, once renamed from *.ima to *.dmg. 🙂👍
b) To make an 1:1 duplicate, you can use Disk Utility.
Simply use the original drive as source for restoration of the CF card.
I don't know the exact steps right now, but I used this method to copy the Mac OS X Leopard install CD to an USB pen drive.
That way, I could install Leopard on a Power Mac G4 without an DVD drive.
Yeah, it's been older Mac systems I did work with, hah. 😅
Edit: Speaking of maximum CF sizes.. Your worries are right.
The classic maximum of both Large (aka E-CHS) addressing and DOS 6.22/Windows 3.1 HDD drivers are 8 GB.
So if you can, please stay within the 8 GB limit. Windows 9x can handle more than this (see LBA-28 limits), but it causes unnecessary confusion between BIOS and Windows.
That's something to keep in mind, by the way.
Windows 95 and the underlying DOS 7 are two separate entities.
DOS asks mama BIOS about the HDD, while Windows uses its own HDD driver.
In some situations, however, the BIOS may be limited or just plainly outdated.
In such a situation DOS/BIOS and Windows will see the very same HDD with different capacity, cylinder numbers, etc.
In short, Windows gets a bit confused. If you then use that extra capacity, data corruption may occur.
Windows will write into areas of the HDD that the DOS part won't see/can't reach during boot.
Then, once ScanDisk runs during boot-up (still in DOS), it will try to correct what it thinks are errors.
That means that the file allocation table gets cleaned from all those entries that ate beyond the borders of what DOS/BIOS can see.
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//