Programming

When I was trying to fully understand the image files, I had to dive into the binary code for the game. Which meant that I had to reference online documentation a lot, utilize a bunch of different tools and also build my own tool to help with the reverse engineering.

Finally, we have reached the last part of the image files, the animation instructions. This post assumes you have read the earlier ones, and if you haven’t, links to them can be found on this page.

At the start of this year I was introduced to Wordle and took to it imminently. It is a simple word game where you try to guess a 5 letter word.

When I started with reversing Dune I felt that I needed to code my own Assembler programs and run them DOSBox. Simply to make sure that I understood the code and logic I was studying.

This is my third post about the image files of the computer game Dune. All the previous posts can be found on this new summery page.

This is part two of my walkthrough of the Dune image files. (Part one can be found here). This part focuses on the color definitions, palettes, that can be found in almost all the images files.

This year I have decided that my next big LEGO project will be to build a Middle Earth map. A map of the world from the Lord of the Rings and the Hobbit books/movie.

I have not been able to keep myself from JavaScript and general web development. I have taken a dive into learning more about CSS, and this lead to an explosion of hearts - A simple web page for viewing and creating messages written over a heart with more hearts flying out of it.

After I figured out the HSQ compression, I started to look into the image files. Something I thought would be relative easy as there was, as with the HSQ compression, code to study.

I have recently begun the journey of learning to code old DOS assembly and how to debug it in the debug version of DOSBox. And when being new to both, the debug screen in DOSBox is a bit overwhelming.