DOSContainer framework in Rust.
Go to file
Bas Wiel, van de 1f63d61aad Lots of breaking crap.. this is more of a backup than a commit. 2024-04-25 19:01:02 +02:00
.vscode Cleanupt settings.json 2024-02-23 18:33:00 +01:00
docs Clarify layered architecture. 2024-04-18 11:39:14 +02:00
src Lots of breaking crap.. this is more of a backup than a commit. 2024-04-25 19:01:02 +02:00
.gitignore Docs updates. 2024-04-14 19:02:22 +02:00
CONTRIBUTING.MD Docs before opening the source repo. 2024-02-23 18:31:33 +01:00
Cargo.lock Lots of breaking crap.. this is more of a backup than a commit. 2024-04-25 19:01:02 +02:00
Cargo.toml Support ZIP format properly. 2024-04-14 14:01:51 +02:00
Jenkinsfile Revert build plan. 2024-04-18 18:11:45 +02:00
LICENSE Docs before opening the source repo. 2024-02-23 18:31:33 +01:00
README.MD Docs before opening the source repo. 2024-02-23 18:31:33 +01:00
test.yaml Cleanups pre-alpha 2024-04-14 18:42:59 +02:00

README.MD

DOSContainer the framework

This repository houses the framework of DOSContainer. The DOSContainer project started out over a year ago in response to me becoming aware of community-created "packs" of games. These come in the form of large hard drive images with a menu system layered on top, allowing for an easy end-user experience in playing a large number of retro games in platforms like the IBM-compatible PC and Amiga. While I tip my hat to the creators of these packs in admiration of their skill and dedication, these were not what I was personally looking for. DOSContainer was born.

The version you see here is the newly imagined Rust version. It's mostly a rewrite of what is already there because Bash becomes very unwieldy.

So what is it?

DOSContainer aims to be a tool that sits in the middle between the retro purist who does everything by hand, and the casual gamer who enjoys playing from game-packs. Note that there is absolutely no value judgement in there on my part. Everything goes, I'm just scratching my own personal itch here. Now if I had to try and sell DOSContainer it'd be something along the lines of a declarative solution to generating MS-DOS compatible hard drive images in a reliable and repeatable way. You can very easily mix and match different versions of operating systems, drivers and utilities with your games to see which combination is optimal for you. Just write a configuration YAML, run the script, and there you are.

What is it not?

DOSContainer is not an emulator of any kind, nor is it intended to be usable by anyone besides myself. Yes, I'm selfish like that. I can write YAML and I consider it reasonable for a configuration format. So no graphical interface, or someone else should build that to spit out YAML's for them. I'm open to any suggestion in that regard.

How to use it

At this point? You don't. The core features are not complete yet. Check out the CONTRIBUTING.MD file in the root of the project to find out how you can help.

Yes.. but.. PIRACY!

Indeed. You're not supposed to pirate copyrighted works and all that. Yet I sourced every single file DOSContainer downloads from Archive.org, which offers them in the open and has been proudly doing so for years. Since I'm not really doing anything different, I'm assuming the rights holders don't mind or don't care enough. If you are a rights holder and you don't like what I'm doing, I will cooperate with any reasonable request sent to archive@area536.com to rectify any issues. If you're not a rights holder to any piece of software this project references, you're welcome to not use it but I'm not interested in hearing about it.