Flux Studio: all Vorpal blocks can now be decoded

I finally also finished implementing the decoder for custom Vorpal blocks on track 18. There are four of these in California Games, used to load the main drive code into the drive RAM.

Here’s the debug output from both Vorpal decoders:

Flux Studio: output from Vorpal decoders by Luigi Di Fraia
Flux Studio: output from Vorpal decoders

I shall do some restructuring of the code in line with the idea of letting users validate disk images, similarly to what TAPClean does for tape images.

Other than that, I shall work at the automated write splice discovery, which is way simpler to achieve now that Flux Studio knows everything about Vorpal šŸ™‚

Stay tuned for more!

About Luigi Di Fraia

I am a Senior DevOps Engineer so I get to work with the latest technologies and open-source software. However, in my private time I enjoy retro-computing.
This entry was posted in Retrocomputing, Reverse Engineering, Technical and tagged , , , , , . Bookmark the permalink.

7 Responses to Flux Studio: all Vorpal blocks can now be decoded

  1. Fritz Laufwerk says:

    No word about syncless tracks with 8-bit soft-syncs and random byte-framing instead, or how 80% of encoding efficiency is achieved with no more than 4 1-bits in a row? šŸ˜¦

    • The (very technical) details you mentioned will be in the documentation for Flux Studio once I release it. If you already know about them, would you consider sharing your notes so I can compare with mine? Perhaps you have a blog of your own where you did already post this information?

      • Heinz Lesekopf says:

        I only looked into this a few days ago, upon polite request by SLC. But i think that in the absence of any hardware sync, some details of the encoding scheme are precisely what is required to determine good write splice offsets in order to avoid chopping up data blocks when writing images back to physical disks. Just thought that a bit of info on this was missing in previous posts. =)

      • Hm. It’s a bit disheartening to know that, although many must have researched and reverse engineered these details before I did (in the 80′-90′ but also more recently, e.g. the work KryoFlux developers have done to verify disk images), the latter don’t seem to be publicly available?

  2. Shreckenninja says:

    Disheartening that the KryoFlux developers don’t publish their findings and keep brewing their commercial closed software? Yes, certainly. šŸ™‚

    I guess something must have gone wrong along the way for this particular encoding, otherwise you wouldn’t have to fix their broken write splice offsets in the first place.

  3. Pingback: Vorpal disks: perhaps the most reliable way to set write splice offsets | Luigi Di Fraia's e-Footsteps

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s