AbaloreOS [ wip ]

[XeNoMoRPH]

[Gryzor]

Wax on
Wax off

Following to see what it'll bring 🙂

[TotO]

The video link ask to enter a word to be watched. And it is not working at all.

[Gryzor]

The video link ask to enter a word to be watched. And it is not working at all.

Works fine for me, both embedded here and on YouTube. 

[BSC]

So you have an OS where you can toggle the split and change the vertical size of the screen?! ;-)

Seriously, this looks cool. Would code completion be possible? That's one of the nicest features
modern shells etc. introduced which I would not want to live without.

[Prodatron]

Looks interesting!
What is the intention/objective of this?

[asertus]

About to ask the same thing.., any special purpose? Gaming?

[GUNHED]

Well, what can be seen?

- Space for different programs (every one gets its own 64 KB bank) and they have their own screen each. Probably four programs + screen. Just guessing

- Nice format for anything 'machine monitor' alike. Yes, the DUMP inspires me here

Looks very interesting! Good luck and happy coding! 

@abalore : Let me know if I can support you in any way 

[abalore]

What you can see in the video is a command interpreter which runs as an app on top of the actual OS. The OS is a collection of firmware routines that replaces the lower ROM from cartridge.

It allows screen manipulation (also horizontal resizing and one pixel smooth scrolling in both split and non-split modes), and also compiled sprites designed with an external tool, sound FX and Music playing (based on Arkos Tracker).

It also handles a kind of cartridge based "file system". It can search and execute compatible programs in the cartridge, manage resources, etc. Also some debugging features are included as a external tool ROM, like memory inspection and disassembler (and maybe assembler at some point).

The purpose of this development is to put all the lessons learned with Alcon 2020 into a reusable engine that anybody can use to create their own games. My first goal is to be able to replicate Alcon using this engine, and in second place to add support for expanded hardware like the Play2CPC VROM and extra sound channels.

There is no BASIC interpreter or compiler of any kind. The firmware is meant to be accessed from assembler code just importing the routine definitions from a provided .asm file. I managed to create a fluid workflow with Visual Studio Code (for coding) + CPR Creator (own tool) + WinAPE (to test and debug). I don't consider a high level interpreter at this moment because the engine is aimed to maximise execution speed, only achievable in pure assembler.

About the schedule, it's a long term project, but I will keep publishing videos of the progress.

@GUNHED for sure I'll ask you in a later stage about the implementation of drivers and other stuff

[GUNHED]

Thanks for sharing your 'insider information' 

It reminds me a lot about some goals I had with FutureOS. Now you bring a fresh breeze in the OS circus for the CPC! That push will be very good for the scene - in may ways.

The two things I like the most about your concept are: You clearly state that it's made for Z80 assembler. Great so it's quick! And in addition it's cool to be able to adjust the screen features!

I'm really looking forward to the evolution of AbalOS. Please keep us updated.

[abalore]

[abalore]

Another video showing the screen size switch maintaining the text output compatibility with hardware scrolling in all sizes.

[GUNHED]

Very nice! For the split screen of smooth vertical scrolling do you select a height of 1 for the characters?

[abalore]

Very nice! For the split screen of smooth vertical scrolling do you select a height of 1 for the characters?

Do you mean setting R9? No, that requires too much CPU. I use R5 that is almost free.

[abalore]

50hz, double buffer, transparent, 1 pixel precision sprites

[abalore]

AbaloreOS can run from disc now, with all the features of the cartridge version available for disc games.

[zhulien]

Can it make an overscan sized screen?  Perhaps if all your code can run in the 64kb bank and not use firmware, then you can use a 32kb screen in overscan mode - multiple of them like you demonistrate with the screen command.  Also if you make some screens text screens, then they will take less RAM in thier buffers.