AmigaBlogs

  I got my AmigaOne motherboard in December of 2004. Wow, it seems so long ago! It came with the pre-release version of AmigaOS4 installed on the 80G hard drive. The motherboard and hard drive were tested and bought separately from the rest of the system. Here is what the motherboard looks like installed in my new case.

  Well, I've finally decided to do it!  Yes, it is a blog site dedicated to my favorite computer, the Amiga! But even more specifically, to the next generation of Amiga Computers, the AmigaOne.
  I hope to add new blog entries periodically that give information about the AmigaOne computers that run AmigaOS4 and beyond. Amiga OS4, for those who do not know, is the next generation PPC based Amiga OS operating system licensed from AmigaInc to Hyperion, and is the original Amiga 3.1 Source Code updated to run on PPC AmigaOne Machines.

Every time you cut a head of a new one grows back.

I try to keep this post short. New update is available:

• MacOSX Darwin PowerPC support is implemented.
• Fixed address distance calculation for the PowerPC native relative branch instructions.
• Refactored the boolean values to use TRUE/FALSE preprocessor defines.

Big thanks goes to Tobias Netzel, who implemented the MacOSX support for the JIT compiling and helped me chasing down one more sneaky bug.

How would recreate the "Amiga" "Workbench version 1.0" GUI if you created it today / 2012 ?

Every developer knows the feeling when finally he/she finds a bug and slaps to the forehead while mumbling: "How on earth was this thing ever been working?..."

Well, it just happened to me, I have fixed a bug that stopped the ROM from booting. It was a rather stupid mistake (as usually); for the details check out the update.
In this other minor update I have fixed one more nuance with the wrong addresses in the dumped PowerPC code log.

I am back from the holidays for sometime now, but I got swamped instantly by the work in my daytime job. I had very little energy on the project in the nights, which was spent on two things: chasing that #@!% bug which is killing me and implementing the data-flow optimization.

I have actually received a few donations! I'd like to start by saying thank you, you know who you are!

After a much needed vacation on the French Riviera, I still have a few days off work, and I can put a wee bit more effort into JAmiga/JamVM.

As an Amiga fan, many years ago I used Deluxe paint from Electronic Arts.

Today I still dream that one day, someone, somewhere will create Deluxe Paint for the Amiga.

In 2009 I had some attempts at JamVM. Now I have actually managed to get JamVM running on AmigaOS 4. You can read more on what was the turning point at amigans.net. So currently I'm going JamVM, all in!

What does this then mean, exactly?

After a long-long time we are going to go on holiday with my beloved wife.

While I am AFK (pick one) please just sit patient and try to find the bug that prevents the OS from booting, will ya?

Thanks. :)

See ya in August.

Although, it was just a small update, but highly important:

This is more of a mental note to self. But it gives a small insight to what I'm battling with.

I've just traced in which way VMNetChannel allocates its ByteBuffer (ByteBuffers are used for pretty much anything handling data, not only network stuff, so its a pretty crucial thing to have).
Starting in VMNetChannel, we find a ByteBuffer.allocate(int capacity). It goes something like this: