Working with Cadius

Tips welcome and strongly encouraged.

Based on tip from Quinn Dunki, I also wanted to explore Cadius as an alternative to AppleCommander.

Cadius is from BrutalDeluxe and is their ProDOS disk imaging utility, so I thought I’d get it installed and take it through it’s paces.

Manual install?  Umm, no thank you.

With as handy as HomeBrew is, not everything is in there.  As mentioned in the previous post, there is a set of formulae for Apple II utilities available here, which has a lot of great things in it.  One of the things NOT in there is Cadius.

I could have just installed Cadius using the instructions found on Cadius’ GitHib page, but what fun is there in that?  Time to learn to make a HomeBrew formula and make the (Apple II) world a little bit better.

I created the HomeBrew formula for it, which was very simple using the instructions found in the Formula Cookbook.  I have a pull request open against the HomeBrew Apple II repo to get it officially included.  If you want to use it before then, you can grab it from here.  One you have it you can install Cadius with:

Image in ProDOS’ self

Now that we have Cadius installed we need to create a disk image, that’s pretty easy:

Despite it being a valid ProDOS volume, it won’t boot like this. Similar to how DOS 3.3 disks, we need to do some extra things to this to make it bootable.  Namely, we need to put on BASIC.SYSTEM and PRODOS from another bootable ProDOS disk.

I was able to find the ProDOS system master on Call-A.P.P.L.E’s site here.  But, I realized it’s a .DSK in DOS order which Cadius will not read.  Fear not!  A quick search pointed me to a script by Paul Hagstrom called, oddly,  I downloaded that and fixed shebang line to use python and not python3 and converted the disk image (Thanks Paul!):

Now, I want as much space on my default ProDOS disk so I just want just the BASICs (see what I did there?) to get the disk bootable.  Let’s copy the needed files over to the new image that was just built:

And now for the boot:

So far, so good.

Back to the past

In the last post I added “helloworld” to a DOS 3.3 disk image with AppleCommander, booted it and ran the executable.  Let’s try that again, but using Cadius to put it on the new disk image and try the same thing.  This will prove that Cadius can be used in place of AppleCommander in my build pipeline.

And the pudding:



Cadius seems like a great alternative to AppleCommand IF you want to only work with ProDOS disks, but it was much more straightforward (detecting the AppleSingle format that we needed).

I think I’ll use it in my build pipeline going forward.  I guess I should stop playing around and should probably write some code for my game as well!

Leave a Reply

Your email address will not be published. Required fields are marked *