Just for test, and advised by Zozo, Hans has enabled the 60-6F segment zone for Rom, and 70-7F for Ram.

The system has found correctly the added Ram, from 1088KB to 1344KB(1376256 bytes in system)

The SF3 manages a SF3.INI batch file that, if found on the SF3 card's SD slot, is executed just before the EP starts. If a modified EXOS has been installed, a 16KB Rom can be put on any of the segments, including on the Ram zone, and it will be found and added to the Rom list, just like EPDOS does. On the non modified EXOS, the Rom will be only found on 60, and maybe on 70(?).

The test file is the Cyrus.rom. This picture is when I have loaded it to the 60(Rom) segment.

Then I have loaded it to 70(Ram). I have loaded EPDOS, but as an extension to call its useful commands, like HROM:

Observe that Cyrus is on 70, but I have loaded it there with SF3, not with EPDOS.

This is the CPC rom that is executed when the SF3 starts. It would be great if Geco converts it to Enterprise, to put it on the 60 segment.It has to take total control, print the SymbiFace 3 screen and then release control to system.

Today, at lunch time, I have tried the Wifi capabilities of SF3. I have sent the Cyrus.Rom to Hans, and he has put it on his Web page as downloadable.

Then I have put the SSID and password of my Wifi Router on the SF3.INI script:

"WIFI_PASS =XXXXXXXXXXXXXXXXWIFI_SSID =ZZZZZZZZZ

WIFI_CONNECT"

And the following Rom loading command:

"ROM[96] =HTTP:www.tmtlogic.com/cyrus.rom"

And then, at the booting, it has connected to TMTLogic and has downloaded the Rom on the segment 60.... Perfect, on only a little more time than loading from the SD or USB....

I have also tried to share Wifi from my phone, and it did the same flawlessly.

By now the internal software of the SF3 only manages 16KB Roms because is how was planned for the CPC. This probably will change, but I have cut the Pasziansz 32KB version on two, then I have put the first halve on segment 61 and the second on segment 62. Of course all has worked.

This has surprised Hans a lot, because he says that CPC roms need to have an external header, sometimes as long as 128 bytes...

when I have the second batch of SF3s ready I will continue with the firmware.-enlarge the roms 32 48 and 64kb-hexadecimal rom number-Enterprise,CPC,MSX or PCW name on the oled display. -continu with the wifi stuff

SF3 has the powerful option of being able to inject Roms or enable or disable Ram/Rom zones on the 4MB EP addressable space. This can be done by means of a script that is executed every switch-on by the Arm processor that manages the SF3, but the card can also be configured while the computer is running(after that, a hard reset is needed for the system to recognize the changes).

Zozo proposes to create a new SF3.Rom to configure the EP at start and to add SF3 drivers. It will be placed on a X0h segment, so every kind of EXOS can find it at switch on.

Then, depending of the EXOS version and the internally installed Ram/Rom, several configurations of Ram/Rom will be allowed, some Roms injected, and a hard reset executed.

The process will last only a little more than a normal boot, and only at the start of the session, all the changes will survive hard resets but not a switch off/on.

The best is that we will be able to easily test a lot of configurations like we do with the emulator, putting Ram or Roms where we would want.