youxia Posted December 20, 2022 Share Posted December 20, 2022 I'm trying to update & expand my PC-XT dedicated software collection. This is primarily meant to run on MiSTer's new PCXT core (though it can be also ran on DOSbox/PCem) and for that I need to use hdd images. I've created a few using PCem, Win10 and also MiSTer's Linux, then have formated with MS-DOS 6.22. The size varies from ~500MB to 1.3GB. These images work as hard drives, and are bootable and can be filled with content. But one problem persists: there's a big loss of hdd space when filling them with my collection, which mostly consists of very small files. So, eg, for the initial release (v0.1) I've used a 487MB-sized hdd image and managed to only fill it with 334 MB of stuff (~30% space loss). A bigger one I need for the expaned collection, 1GB-size, only took 442MB of files, that's merely a 43% fill rate. After that the disks report running out of space (despite their original size being correctly reported in NC or fdisk). I've also tried filling the 1GB disk with big files (like 10x100MB) and in that case was able to fill it up to ~98%. I read a liitle bit about this whole topic, and how this quagmire might be related to old FAT16 (which I need to use for PCXT - I think, not sure it'd be compatible with MSDOS 7.1 which can offer FAT32 ?) cluster size limits and the resulting space loss - but even then my impression was that it should account for 20-30% max of space loss (and possibly only when going over 1GB). But ultimately this is all above my pay grade, and so I'm hoping maybe some of local MS-DOS experts might have simpler explanation, or perhaps even a solution. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.