CPM running under Symbos - Sounds like getting a Rolls Royce and fitting it with an engine from a go-kart

No, it's like getting a Rolls Royce and leave the engine (it's the symbos kernel / system processes still) but using the car to transfer dirty potato from the field at country side But seriously: it's not a bad idea, I think,
There are many CP/M softwares (well, not the ones like wordstar, seriously, GUI based better one can be written for SymbOS) which are basically command line based stuffs, which can be useful (I even used CP/M based compiler on Linux because there was no modern version, but who cares if you need to give a single command like it would be a native cli app). You can think running them as symshell apps with some CP/M CBIOS/BDOS "glue" or whatsoever

If you use emulator then please choose a config with EXOS 2.3, or with TASMON. The test will be much faster, and in EXOS 2.3 you can bypass memory test by a keyboard combination, unfortunately I do not remember for it, but booting screen shows it.

These means that unfortunately the original EXOS have no quick ram test feature or skip ram test feature (or we do not know about that). Probably they thought we would like to wait for booting this much ... And probably the warm reset will solve everything ... Or such ...

Some EP developers, especially Zozo created quick ram tests, but unfortunately that is tricky and difficult to integrate an already written ram test code to an extension ROM, and because of that, there is only a very limited number of extension ROMs containing a quick ram test part. Some ROM ASMON versions or ROM WP versions have that.

Or Zozosoft's enhanced EXOS ROMs have quick test, too. And Zozosoft's memory test have many functions as well, what other ram tests have not. Like faking 128K machine on a hardware extended memory configuration, and detailed test information, and such ones ...

Zozosoft modified EXOSes can be burned to an EPROM replacing the EXOS ROM on the motherboard, or other programs (like WP with Zozo's ram test, for example) can be burned to an EPROM to the cartridge.

Ok, I will update my EP128EMU with EXOS 2.3!

A few minutes ago I got SymbOS nearly fully running on the EP



They grey colours maybe a little bit sad, but it shows again, that this is an Enterprise and not a CPC (which only has 1 grey).
"Only" the sector read/write routines for the WD are missing now...

Thanks to all of you for your great support here!!

This thing will be cool ...

Is there a documentation for the settings and customization of the SymbOS ?

Can a user set the ICON captions (names) to transparent background ?

Can a user customize the colors ?

Till this point, what are the plans about EXOS compaibility ? Will SymbOS be a CAP to EXOS ? Will I be able to exit to EXOS ?

Transparent icons and captions are not possible yet.

Okay, maybe I can set the ICON caption background color to the color of the real background = transparent ICON caption ...

Colours can be customized. For all the settings please have a look at the screenshots of the control panel:
http://www.symbos.de/apps.htm?3#marke0

Maybe it would be the time for me to run SymbOS in an emulator or such ...

Regarding EXOS it seems, that it's quite easy to save its state during SymbOS is running, if your EP has enough RAM. So it will be possible to return to EXOS without a reset. As mentioned before SymbOS is not a cap of any existing OS, it has its complete own multitasking environment.

Okay, I probably think of the state saving/restoring calling it "CAP", because a CAP do not have to call EXOS ... so when SymbOS is saving/restoring EXOS, it's a "CAP" not making a single EXOS call ...

Maybe it would be the time for me to run SymbOS in an emulator or such ...

You can try it online here (and probably soon on LGBs emulator, too ):
http://symbos.cpc-live.com/
Use the Num-Pad (with "Num" switched off) to control the mouse.
There is a disc in drive A and drive B, for some apps you have to switch to drive B (Startmenu -> Run -> Browse).

Okay, I probably think of the state saving/restoring calling it "CAP", because a CAP do not have to call EXOS ... so when SymbOS is saving/restoring EXOS, it's a CAP not making a single EXOS call ...

In this case I agree