Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support compressed .boxer bundles or inner .harddisk containers. #106

Open
amcgregor opened this issue Apr 4, 2020 · 0 comments
Open

Support compressed .boxer bundles or inner .harddisk containers. #106

amcgregor opened this issue Apr 4, 2020 · 0 comments

Comments

@amcgregor
Copy link

amcgregor commented Apr 4, 2020

ZIP files are essentially a small single-file read/write filesystem, with NeXT (thus Cocoa, thus macOS) supporting use of ZIP archives as the container for "file bundles", not just unpacked directories. (Ex: iWork '07 files.) It would massively reduce the overhead of maintenance (offsite backup) and poor Spotlight metadata indexing to permit zipped bundle use. This would result in a single file per application or game, not potentially thousands.

Though, yes, this would be with the trade-off of modifying a small file within that DOS environment (e.g. creating a save game) invalidating the entire .boxer bundle, but that happens far more rarely than adding a new package to the archive. Even if the .boxer overall bundle can't be sourced from ZIP, could the .harddisk / .cdrom / .floppy inner bundles be?

My library is extensive—just under a terabyte of DOS software, alone, still to be processed. A small subset of 182 games from childhood totalling 16GB are actually comprised of 25,692 individual files, or an average of 141 files per game.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant