CPCWiki forum

CPCEmu v3.0 (April 2025) (https://www.cpc-emu.org/) is out.

Hybrid SymbOS DSK not load all....

The V9990 emulation is a fantastic news! I have to try it ASAP!

Quote from: Prodatron on 20:58, 16 April 25The V9990 emulation is a fantastic news! I have to try it ASAP!

Doh I didn't check the new features...

I will add them to the news after my WoW raid.

22:18 : done during the pause

Emulation doesn't start (Win11 both portable and installation). Dobbertin HD file is also missing.?

Quote from: McArti0 on 20:51, 16 April 25Hybrid SymbOS DSK not load all....

Hi, all. I had intended to prepare all operating systems before announcing the release officially. But it's fine this way.

I tested the SymbOS version for M4 mass storage only. Anyway, you need to increase RAM size. Have you done that?

Quote from: HAL6128 on 21:52, 16 April 25Emulation doesn't start (Win11 both portable and installation). Dobbertin HD file is also missing.?

Thanks for the report. It's a mess with Win11. On my Win11 machines, v3.0 starts flawlessly. But I have already received a single report where it doesn't. The problem is, I can hardly find a solution as I cannot reproduce the crash. I'm trying to approach the culprit slowly. Please be patient.

And, I probably forgot to include the HD20 file, sorry. That's particularly annoying because I will have to submit another update to Google Play and the Apple app store (I'm still hoping the latter accepts CPCemu at all).

I also forgot to include index.html and favicon.ico in the Windows release. At least, this I can update without much effort.

Quote from: McArti0 on 20:51, 16 April 25Hybrid SymbOS DSK not load all....

I tried both 720k and 1200k versions as well as the regular disk version. All of them do boot until the start menu is visible. The screen background is black, but the start menu can be operated. However, no application can be started. Looks like a configuration issue to me.

Interestingly, if I boot from either hybrid DSK while the M4 board with the SymbOS mass storage version is enabled, the usual background image and the clock are shown and I can start applications with the mouse. However, once I open the start menu, SymbOS crashes.

It's good to see that the emulator is being developed. I'm also curious and heavily invested in the V9990 emulation.

Android set to const 60Hz refresh.

PPI 60Hz

SPEED INK 1,1
INK 0,22,17

Perfect fliker color.

Quote from: Prodatron on 20:58, 16 April 25The V9990 emulation is a fantastic news! I have to try it ASAP!

yeah, that's a great feature for sure!
cant' wait the Linux version :P

BTW Rainer, to answer your email no I have not yet tested the V9990 emulation, time constraint.

Anyway 2 questions with the android version :

- when the phone is in landscape mode and if the V9990 is being used, would it be possible to print the CPC screen to the left, the V9990 screen to the right ?

- lacking time to check with my phone, but if a real keyboard is connected to the phone and detected, can the the virtual keyboard stay hidden ?

Quote from: Emu on 22:56, 16 April 25

Quote from: HAL6128 on 21:52, 16 April 25Emulation doesn't start (Win11 both portable and installation). Dobbertin HD file is also missing.?

Thanks for the report. It's a mess with Win11. On my Win11 machines, v3.0 starts flawlessly. But I have already received a single report where it doesn't. The problem is, I can hardly find a solution as I cannot reproduce the crash. I'm trying to approach the culprit slowly. Please be patient.

And, I probably forgot to include the HD20 file, sorry. That's particularly annoying because I will have to submit another update to Google Play and the Apple app store (I'm still hoping the latter accepts CPCemu at all).

I also forgot to include index.html and favicon.ico in the Windows release. At least, this I can update without much effort.

Maybe you can add an option for creating a log file during boot/driving the emulator?

Quote from: genesis8 on 14:35, 17 April 25- when the phone is in landscape mode and if the V9990 is being used, would it be possible to print the CPC screen to the left, the V9990 screen to the right ?

Interesting idea for people having large phones (=phablets?). At least, it should be possible to switch between the screens. On the other hand: Is there any software known for the CPC using both screens at all? Perhaps this feature can wait until somebody creates such software.

Quote from: genesis8 on 14:35, 17 April 25- lacking time to check with my phone, but if a real keyboard is connected to the phone and detected, can the the virtual keyboard stay hidden ?

You can always hide the virtual keyboard, independent of a hardware keyboard with a two-finger tap on the virtual keyboard holders (yellow and cyan areas that are highlighted if you tap outside of the keyboard).

Quote from: HAL6128 on 15:41, 17 April 25Maybe you can add an option for creating a log file during boot/driving the emulator?

There are already two logs. One is stdout, the other one is stderr. The latter is shown in the message box if an exception occurs. Of course, you don't see that in case of a crash. So, capture both of them from the command prompt (cmd) like this (cd into the cpcemu directory first):

cpcemu.exe > log.txt 2>&1


Thanks for the hint.

This is the output of the logfile (Win11_64bit, Installation in C:\Program Files (x86)\CPCEmu3.0)

CPCemu (v3.0)  -  The CPC Emulator

   (c) Marco Vieth & Rainer Loritz
             2002-2025
      -- all rights reserved --

D-DPI: 96.000000 => display size is 16.022747 in.
Display resolution: a) 768/542  b) 768/542 c) 768/542 d) 768/542
CONFIG: Using cpcemu0.cfg
DATA: Using ./cpcemu.dat
MEM: 491520 Bytes ok.
ROM: CPC 6128 detected. (c) Amstrad and Locomotive 1984, 1985
ROM: TAPE bypass installed.
ROM: AMSDOS speedup installed.
Audio@44100 Hz (1024 Bytes).
IO_PORT: Cannot open printer file PRN

Another Log Error:

Windows 10 works fine, by the way, but only with the standard config. If additional config added it crashes....

It seems all about permissions?

I try GNU/Linux versions when they will be avalaible.

Maybe you have too high/low permissions for this folder?

I wouldn't expect a permissions problem on an App data folder, that's typically writable by the current user. The username does appear to have a hyphen in it, which is unusual and might be an issue, but should be okay.

More likely it's a crash in something the additional config you're adding has enabled.

Quote from: andycadley on 12:03, 18 April 25I wouldn't expect a permissions problem on an App data folder, that's typically writable by the current user. 

SugarBox 0.28-0.3 has permission problems on win10

I've tried today the Win-Version (3.0) with Linux & Wine. It seems to work fine, also the V9990 emulation works great. I've also realized that the sdcard "live" emulation is better than under Windows. I never got access to that folder (under Win, but Linux). Transfered data from my real CPC to that folder and run it.
Nice! First emulator with V9990 support. Now a cool programming environment is available.
Next check is SymbOS with V9990.

Quote from: McArti0 on 13:42, 18 April 25

Quote from: andycadley on 12:03, 18 April 25I wouldn't expect a permissions problem on an App data folder, that's typically writable by the current user.

SugarBox 0.28-0.3 has permission problems on win10

Sure, there are plenty of ways you can run into permissions problems (typically assuming you can write to files under Program Files) but the App Data folder is specifically where applications are supposed to store configuration data and is writable by default for the current user. So unless something very weird has been done during installation I'd not expect it to be the issue.

This was my intention. Normally the "CPCEmu Installer" installs the application right into the "program(x86)" folder. But permission in such folder isn't always clear for the application if changes are necessary because you need admin-rights to do that. So I changed the folder during installation process into my user folder where everything should be set to my user-permission (allowed to do everything).
But CPCEmu always wants to create a mirrored folders system into the root drive (I don't know what the purpose of that is). And this might be the drawback??

Within the Wine environment you can see the folders which have been created / double in the C:\. But why??

The keyboard layout is also weird. I can't use the bar "|" and I have to use the virtual keyboard.

I like the performance on Android tv (slow soc) with the android version however:
1. I still need a way to use my bluetooth controllers in stead of composite keyboard as a joystick, how to map the keys is key :D
2. The new setup menu is very difficult to read on tv, font size should scale a bit more to make it readable again.
3. Support for cpc plus models would be nice ;D

Because of the consistent speed on low spec android devices this is certainly one of my favorite cpc emulators on Android.

Quote from: HAL6128 on 15:13, 18 April 25I've tried today the Win-Version (3.0) with Linux & Wine. It seems to work fine, also the V9990 emulation works great. I've also realized that the sdcard "live" emulation is better than under Windows. I never got access to that folder (under Win, but Linux). Transfered data from my real CPC to that folder and run it.
Nice! First emulator with V9990 support. Now a cool programming environment is available.
Next check is SymbOS with V9990.

Even P-modes are emulated, that is really cool!

Quote from: Prodatron on 22:53, 18 April 25Even P-modes are emulated, that is really cool!

Thanks! Of course, I wanted to see Flappy Birds running on CPCemu...

I don't remember at the moment, but some features are missing. Wasn't there a second P-Mode? I think that's missing.

Quote from: HAL6128 on 23:39, 17 April 25Thanks for the hint.

This is the output of the logfile (Win11_64bit, Installation in C:\Program Files (x86)\CPCEmu3.0)

I have released v3.0.1 for Mac and Windows. It should work in Windows 11 now. It was a DLL linkage problem. I had inadvertently imported the Winsock functions by ordinals (which changed between Windows 10 and 11). So, all of my network code called the wrong functions in Windows 11, but nodody told me.

The Dobbertin HD20 should work now, too. The file was not missing, but is created automatically (but in v3.0 the wrong folder was used, so probably it failed). Of course, you need to install the X-DDOS ROM (included) first.

Quote from: diesoft on 19:32, 18 April 251. I still need a way to use my bluetooth controllers in stead of composite keyboard as a joystick, how to map the keys is key :D

At least the left stick and the buttons should work in Android out of the box. A hardware keyboard works, too, but currently some keys are wrong or don't work at all.

Quote from: HAL6128 on 16:30, 18 April 25But CPCEmu always wants to create a mirrored folders system into the root drive (I don't know what the purpose of that is). And this might be the drawback??

Because this way CPCemu can be installed to a read-only location for multiple users (such as Program Files in Windows or /usr/local/bin or whatever in Linux) without interference between the users. It copies all files to a user-specific folder when this user starts it for the first time. The executable stays the same for all users (in the read-only location).

Quote from: HAL6128 on 16:30, 18 April 25The keyboard layout is also weird. I can't use the bar "|" and I have to use the virtual keyboard.

This is strange and not intended. Which layout have you chosen in CPCemu and which is your hardware keyboard layout? Using a German keyboard and "German" in CPCemu's keyboard layout, AltGr+< should yield the bar. In MacOS with a German keyboard it's alt+7.

Quote from: HAL6128 on 11:14, 18 April 25Windows 10 works fine, by the way, but only with the standard config. If additional config added it crashes....

Can you send me this cpcemu_V9990.cfg? I assume it has a syntax problem. But of course, a bug is more probable.

Thank you for the update!!!! :)
Installation and starting on Win11 works now. Great. Changing config is also now working.

Still some troubleshooting... hopefully you can fix or give me a hint? Maybe I do something wrong?

My aime is having a (experimental) live M4 folder and a V9990 environment working.

Creating a folder works, but not deleting it (permission issue??).
Also digging into that folder works, but not going back.

Quote from: HAL6128 on 15:13, 18 April 25I've also realized that the sdcard "live" emulation is better than under Windows. I never got access to that folder (under Win, but Linux).

Which folder? You mean "%APPDATA%\CPCemu\SDCARD"?

Quote from: HAL6128 on 15:13, 18 April 25Next check is SymbOS with V9990.

As I wrote above, the M4 mass storage version works out of the box. I have no clue why the disk versions (not even the 178 k version) stop at the start menu with the remaining screen being black (but load further if the M4 board is enabled and has SymbOS installed).

Perhaps anybody can give me a hint why SymbOS stops booting there.

Quote from: Emu on 15:49, 19 April 25This is strange and not intended. Which layout have you chosen in CPCemu and which is your hardware keyboard layout? Using a German keyboard and "German" in CPCemu's keyboard layout, AltGr+< should yield the bar. In MacOS with a German keyboard it's alt+7.

I had suspected it, now I see it from your screenshot. You chose "1:1" layout. Please choose "DE" instead. "1:1" tries to provide the original CPC layout. There, the bar should be reachable by SHIFT+Ü on the German keyboard.

Quote from: Emu on 15:56, 19 April 25

Quote from: HAL6128 on 15:13, 18 April 25I've also realized that the sdcard "live" emulation is better than under Windows. I never got access to that folder (under Win, but Linux).

Which folder? You mean "%APPDATA%\CPCemu\SDCARD"?

Yesss, thanks. This is the folder I was looking for. Didn't know that %APPDATA% is used (and of course it's obvious for windows :D ).

Quote from: Emu on 16:00, 19 April 25

Quote from: Emu on 15:49, 19 April 25This is strange and not intended. Which layout have you chosen in CPCemu and which is your hardware keyboard layout? Using a German keyboard and "German" in CPCemu's keyboard layout, AltGr+< should yield the bar. In MacOS with a German keyboard it's alt+7.

I had suspected it, now I see it from your screenshot. You chose "1:1" layout. Please choose "DE" instead. "1:1" tries to provide the original CPC layout. There, the bar should be reachable by SHIFT+Ü on the German keyboard.

No, that's the reason why I had to choose 1:1 layout because with the German layout I'm not able to use the bar. With the 1:1 layout I'm able to do that.

Quote from: HAL6128 on 15:56, 19 April 25Creating a folder works, but not deleting it (permission issue??).
Also digging into that folder works, but not going back.

I can reproduce it, but only in Windows. On the Mac, these steps work. Probably, I did not manage to test all plaltform-specific code. Smells like a v3.0.2. If it's not that urgent (you could delete the folder from the Windows host) I would like to wait a few hours, because there will be further bug reports for sure, now that Windows 11 works.

Quote from: Emu on 15:56, 19 April 25

Quote from: HAL6128 on 15:13, 18 April 25Next check is SymbOS with V9990.

As I wrote above, the M4 mass storage version works out of the box. I have no clue why the disk versions (not even the 178 k version) stop at the start menu with the remaining screen being black (but load further if the M4 board is enabled and has SymbOS installed).

Perhaps anybody can give me a hint why SymbOS stops booting there.

Just an assumption, it's a memory emulation / config topic. 
If I choose different memory layout (e.g. dk'tronics) and 512kB than nothing happens (black screen) after booting SymbOS. If I choose 576 kB then I see at least one second, the boot screen then memory garbage. With the vortex memory expansion only black screen.

Quote from: HAL6128 on 16:11, 19 April 25different memory layout (e.g. dk'tronics) and 512kB than nothing happens (black screen) after booting SymbOS. If I choose 576 kB then I see at least one second, the boot screen then memory garbage. With the vortex memory expansion only black screen.

Which SymbOS version? M4 or disk?

By the way, I was _not_ able to reproduce the |CD problem. Can you try to CD into the M4 folder and back? Does "TEST" still exist on the Windows host?

Quote from: Emu on 16:20, 19 April 25Which SymbOS version? M4 or disk?

I can reproduce it with the M4 version. Strange, indeed. I would like to know how a real CPC behaves, e. g. with 384k RAM.

Quote from: Emu on 16:20, 19 April 25With the vortex memory expansion only black screen.

I assume this would effectively be 128k, because SymbOS cannot use Vortex expansions as far as I know.

Still, SymbOS 4.0 should run on 128k, right?

I tried SymbOS 3.1. It does not start with 128k or 512k, either. Sounds improbable that just 576k would work, doesn't it?

Quote from: Emu on 16:20, 19 April 25

Quote from: HAL6128 on 16:11, 19 April 25different memory layout (e.g. dk'tronics) and 512kB than nothing happens (black screen) after booting SymbOS. If I choose 576 kB then I see at least one second, the boot screen then memory garbage. With the vortex memory expansion only black screen.

Which SymbOS version? M4 or disk?

By the way, I was _not_ able to reproduce the |CD problem. Can you try to CD into the M4 folder and back? Does "TEST" still exist on the Windows host?

The M4 version.

Quote from: Emu on 16:20, 19 April 25

Quote from: HAL6128 on 16:11, 19 April 25different memory layout (e.g. dk'tronics) and 512kB than nothing happens (black screen) after booting SymbOS. If I choose 576 kB then I see at least one second, the boot screen then memory garbage. With the vortex memory expansion only black screen.

Which SymbOS version? M4 or disk?
By the way, I was _not_ able to reproduce the |CD problem. Can you try to CD into the M4 folder and back? Does "TEST" still exist on the Windows host?

The folder is also created on the real drive...
The same behaviour also with the M4 folder

Quote from: Emu on 16:35, 19 April 25

Quote from: Emu on 16:20, 19 April 25With the vortex memory expansion only black screen.

I assume this would effectively be 128k, because SymbOS cannot use Vortex expansions as far as I know.

Still, SymbOS 4.0 should run on 128k, right?

I tried SymbOS 3.1. It does not start with 128k or 512k, either. Sounds improbable that just 576k would work, doesn't it?

Yes, SymbOS runs with 128k (limited, but it runs).

By the way, the new GUI system is very handy (on PC), if you want to change the config.
Haven't used the Debugger Monitor yet.

I fixed the |ERA bug with directories. However, I still cannot reproduce the |CD,".." problem.

Regarding SymbOS: Have you tried it in Windows and Wine? How did you set it up? Did you use live or image mode? Are there many files (including those in subfolders) in your SDCARD folder?

Just as a motivation and to prove that it works fine for me I've included two screenshots.

Quote from: Emu on 15:43, 19 April 25

Quote from: diesoft on 19:32, 18 April 251. I still need a way to use my bluetooth controllers in stead of composite keyboard as a joystick, how to map the keys is key :D

At least the left stick and the buttons should work in Android out of the box. A hardware keyboard works, too, but currently some keys are wrong or don't work at all.

Ok, will retry. At the moment it only seems to have the fire button A (using 8bitdo controller) mapped to the <enter> key..

Quote from: Emu on 22:40, 19 April 25I fixed the |ERA bug with directories. However, I still cannot reproduce the |CD,".." problem.

Regarding SymbOS: Have you tried it in Windows and Wine? How did you set it up? Did you use live or image mode? Are there many files (including those in subfolders) in your SDCARD folder?

Just as a motivation and to prove that it works fine for me I've included two screenshots.

Looks great, thanks so much @Emu !
I have to wait until tomorrow until I am back home and can try it.

Happy Easter everyone!

Looking for the reason why SymbOS runs only with >=576k of RAM, I found a special egg. The bank switching of RAM pages/banks beyond the actual RAM size was wrong. Of course, this can be (and obviously by SymbOS _is_) used to recognize the RAM size.

I have fixed this. Now SymbOS runs with 128k and, e. g. 512k. This is also true for SymbOS 3 when started from disk (with M4 board disabled).

Unfortunately, SymbOS 4.0 still does not start from disk (stops at the basic start menu). And, still, if the M4 board is enabled, it does correctly start from disk (obviously loading some missing things from the M4 SD card).

Quote from: Emu on 23:13, 16 April 25

Quote from: McArti0 on 20:51, 16 April 25Hybrid SymbOS DSK not load all....

I tried both 720k and 1200k versions as well as the regular disk version. All of them do boot until the start menu is visible. The screen background is black, but the start menu can be operated. However, no application can be started. Looks like a configuration issue to me.
Interestingly, if I boot from either hybrid DSK while the M4 board with the SymbOS mass storage version is enabled, the usual background image and the clock are shown and I can start applications with the mouse. However, once I open the start menu, SymbOS crashes.

My suspicion is that this is related to the non-working option to disable AMSDOS speedup.

Quote from: McArti0 on 17:36, 21 April 25My suspicion is that this is related to the non-working option to disable AMSDOS speedup.

The option does work. It removes waiting times between disk sectors and tracks (by modifying the AMSDOS ROM and by not artificially waiting in the disk controller emulation). But, and this came to my attention only through your hint, it has an effect only once the emulation is restartet (by quitting or by selecting the corresponding menu item in the setup menu). This is because it modifies the AMSDOS ROM, which cannot simply be undone, but requires reloading the ROM. I might add a message box after this option has been toggled.

Anyway, it does not relate to SymbOS not booting from disk. Nevertheless, thank you for the hint.

Quote from: HAL6128 on 16:11, 19 April 25If I choose different memory layout (e.g. dk'tronics) and 512kB than nothing happens (black screen) after booting SymbOS. If I choose 576 kB then I see at least one second, the boot screen then memory garbage.

I suspect that the latter is an artifact of the SD card live mode. Please restore the SymbOS files (in particular the .INI files) and try it with image mode. It seems that they become garbled when written back in live mode.

As Duke wrote to me once, the live mode is an uphill battle. I spent lots of hours (no, rather of weeks) to it, but it still has flaws at many places.

Hi @Emu , I wrote you an e-mail with my problem, but I will explain it here in case anyone might be interested.
The Android version works fine on my Samsung Galaxy Tab S9, but the physical keyboard doesn't work properly; the movement is jerky and practically unplayable. Is there a solution? 
Thank you very much.

Quote from: ikerkaz on 10:03, 22 April 25The Android version works fine on my Samsung Galaxy Tab S9, but the physical keyboard doesn't work properly; the movement is jerky and practically unplayable. Is there a solution?

Thank you for the report. I checked with two different Android tablets and you are right. Interestingly, typing in BASIC at the command prompt works without problems. I have to look into the code, but I remember certain difficulties with Android keyboard input. I hope I can improve this behaviour.

Quote from: Emu on 08:45, 22 April 25

Quote from: HAL6128 on 16:11, 19 April 25If I choose different memory layout (e.g. dk'tronics) and 512kB than nothing happens (black screen) after booting SymbOS. If I choose 576 kB then I see at least one second, the boot screen then memory garbage.

I suspect that the latter is an artifact of the SD card live mode. Please restore the SymbOS files (in particular the .INI files) and try it with image mode. It seems that they become garbled when written back in live mode.

As Duke wrote to me once, the live mode is an uphill battle. I spent lots of hours (no, rather of weeks) to it, but it still has flaws at many places.

It doesn't boot complete through the whole process and stops. I used SymbOS 4.0. 576kB RAM and the image mode of the M4.
It's a complete fresh installation of CPCEmu 3.0 and SymbOS. I didn't get it work.

Also tried SymbOS 3.1 with the same result. Maybe something's weird with Windows 11.

Two not important points :

- M4 ROM is 2.0.6, latest is 2.0.8
- the emulator still shows v3.0 not v3.0.1

A dumb problem for a frog, even if for a 6128 I choose (portable version FYI) :

LANGUAGE = 2
KBD_LANGUAGE = 2
VKBD_LANGUAGE = 2

the keyboard will still be qwerty.

So I went to ROM manager and chose the CPC6128.ROM.FR for both 255 and 0 and got in cpcemu.cfg :

#IFCPC 2 ;CPC 6128
ROM_BLOCK = 7, "CPCADOS.ROM", 0
ROM_BLOCK = 0, "H:\D\amstrad\emulateurs\cpcemu-3.0.1\ROM\National\CPC6128.ROM.FR", 1
ROM_BLOCK = 255, "H:\D\amstrad\emulateurs\cpcemu-3.0.1\ROM\National\CPC6128.ROM.FR", 0

When launching the emulator, I got an error cant find the ROM in ROM/\my path starting with H:, of course if I put :

#IFCPC 2 ;CPC 6128
ROM_BLOCK = 7, "CPCADOS.ROM", 0
ROM_BLOCK = 0, "National\CPC6128.ROM.FR", 1
ROM_BLOCK = 255, "National\CPC6128.ROM.FR", 0

then it works in azerty, but still can't use the pipe (ù with the french keyboard) with the real keyboard to use M4 commands, no problem with the virtual keyboard though.

Or did I make something wrong ?

An idea, let the user choose the model AND national ROM at the first start, and set by default the virtual keyboard the same language ? Otherwise, I fear some french will try and go for another emulator it it doesnt work at once.

Good news, SymbOS starts but now, what mouse must I choose to use SymbOS ? On SymbOS I choose the first v4.0 version (31th January), but a little bit down there is another version 4th March, stated " most actual 4.0 (improved) preview for Amstrad CPC".

Quote from: genesis8 on 21:24, 22 April 25- M4 ROM is 2.0.6, latest is 2.0.8

I might update it in v3.0.2 ;-).

Quote from: genesis8 on 21:24, 22 April 25- the emulator still shows v3.0 not v3.0.1

Ouch, touché. Thanks for the hint, will be fixed in 3.0.2.

Quote from: genesis8 on 21:24, 22 April 25When launching the emulator, I got an error cant find the ROM in ROM/\my path starting with H:, of course if I put :

I would like to understand this better. In which folder is CPCEMU.EXE and in where is %APPDATA%?

Quote from: genesis8 on 21:24, 22 April 25then it works in azerty, but still can't use the pipe (ù with the french keyboard) with the real keyboard to use M4 commands, no problem with the virtual keyboard though.

Probably, the mapping of the hardware keys is not complete or faulty. I tried to check all keys, but the easiest way to use different layouts was in MacOS. So, perhaps, there is a difference in Windows or I missed one key. I will look after it.

Quote from: genesis8 on 21:24, 22 April 25An idea, let the user choose the model AND national ROM at the first start, and set by default the virtual keyboard the same language ? Otherwise, I fear some french will try and go for another emulator it it doesnt work at once.

Perhaps I should stay with the two current selections for the user, but select the national ROMS depending on the virtual keyboard layout?

Quote from: genesis8 on 21:24, 22 April 25Good news, SymbOS starts but now, what mouse must I choose to use SymbOS ?

That's good news. Best-suited for SymbOS is Symbiface. For me, it feels almost 1:1. As SymbOS accepts joystick input, you could also use the numeric keypad (without NUMLOCK) or the AMX mouse emulation.

Quote from: HAL6128 on 20:11, 22 April 25Also tried SymbOS 3.1 with the same result. Maybe something's weird with Windows 11.

Interesting, that's exactly the state I end up with when booting SymbOS from disk.

From the drive names I conclude that genesis8 made it work in WIndows. I think I did so, too (but will try again). There shouldn't be a difference in Windows versions (the problem in v3.0 was only related to network functions).

I found the exact reason for the crashes with live mode. SYMBOSXT.INI is truncated to its previous size when written during shutdown of SymbOS. This results in a damaged start-up sequence next time SymbOS boots. Unfortunately, I don't have a solution, yet. My problem is that my emulation of the SD card file system has to cope with different orders of information-writing by SymbOS (first the directory sector then the data sectors or the other way round, I remember both ways to occur; there we are in the uphill battle, again).

Quote from: HAL6128 on 20:11, 22 April 25Also tried SymbOS 3.1 with the same result. Maybe something's weird with Windows 11.

I just remembered your |CD issue. In which file system (FAT32, NTFS, ...) is your %APPDATA%? Are there any special characters in the path to it? I remember a hyphen in it, is there more to it?

Besides, please look into %APPDATA%\CPCemu. There should be a file VSD.IMG once you tried to start SymbOS in image mode. It is a FAT32 image file. Can you mount it and look into it? Does it contain a complete copy of your SDCARD directory structure?

Quote from: Emu on 23:32, 22 April 25I found the exact reason for the crashes with live mode. SYMBOSXT.INI is truncated to its previous size when written during shutdown of SymbOS. This results in a damaged start-up sequence next time SymbOS boots. Unfortunately, I don't have a solution, yet. My problem is that my emulation of the SD card file system has to cope with different orders of information-writing by SymbOS (first the directory sector then the data sectors or the other way round, I remember both ways to occur; there we are in the uphill battle, again).

The live mode is an impressive feature. I have no idea how you are able to convert low level sector access on an emulated FAT32 device in realtime to a Windows NTFS subdirectory...  :o Are you working with an internal temporary FAT32 image, which is then synchronized with the directory as soon as there are changes?

I am currently trying to get SymbOS working with this, but currently without success. SymbOS boots fine from disc, when there is nothing on the SD card. I will continue with testing. Currently CPCEmu is installed in the x86-program folder (Windows 10; it seems, that the installer found this old location and updated it to 3.0.1), and the folders are in users/appdata/roaming/cpcemu . Is that a good place, or should it be somewhere else?

Quote from: Prodatron on 09:52, 23 April 25The live mode is an impressive feature. I have no idea how you are able to convert low level sector access on an emulated FAT32 device in realtime to a Windows NTFS subdirectory...  :o Are you working with an internal temporary FAT32 image, which is then synchronized with the directory as soon as there are changes?

Thanks, that's high praise coming from you! No, it's not exactly an image, but a huge linked-list structure of directories, files and their clusters. The directory sectors are filled on-the-fly from the structure when they are read (and converted to the structure when written).

Quote from: Prodatron on 09:52, 23 April 25SymbOS boots fine from disc, when there is nothing on the SD card.

Now, that's really interesting. I will try that immediately.

Quote from: Prodatron on 09:52, 23 April 25I am currently trying to get SymbOS working with this, but currently without success. ... I will continue with testing. Currently CPCEmu is installed in the x86-program folder (Windows 10; it seems, that the installer found this old location and updated it to 3.0.1), and the folders are in users/appdata/roaming/cpcemu . Is that a good place, or should it be somewhere else?

These places are fine.

I've just tried v3.0.1 in Windows 10 and installed the contents of the two SymbOS mass storage packages into the SDCARD folder. It boots completely without complaint. What I noticed for the first time is an exception when shutting down SymbOS. Bug removed.

Have you set RAM size to 576k and restartet the emulator via the setup menu item "restart emulation"? Otherwise, v3.0.1 will not be able run SymbOS.

Please do not use live mode for the time being. Try image mode and restore all SymbOS files, in particular SYMBOSXT.INI, after you used live mode. I would be interested to see if the SD card image VSD.IMG has the correct contents (i. e., a complete deep copy of the SDCARD directory).

Quote from: Emu on 13:46, 23 April 25No, it's not exactly an image, but a huge linked-list structure of directories, files and their clusters. The directory sectors are filled on-the-fly from the structure when they are read (and converted to the structure when written).

I forgot to mention that the data sectors are read and written immediately from and to the host file system (the clusters stored in the linked lists are only number ranges).

Quote from: Prodatron on 09:52, 23 April 25SymbOS boots fine from disc, when there is nothing on the SD card.

I tried, and indeed, all disk versions, even the BootHybrid versions 720k and 1200k, boot and work fine if the SD card is empty.

After that, I looked for any SymbOS-related code in CPCemu. Almost everything was already disabled when the M4 board was disabled.... besides of the Symbiface mouse and RTC ports at 0xFDxx. SymbOS reads from 0xFD4F, 0xFD41, 0xFD42, 0xFD0F (IDE status) and 0xFD14 (RTC), and CPCemu returned 0 as a default in these cases (apart from the RTC). In particular, SymbOS repeats 0xFD0F very often, so that's probably where booting visually stops. It seems that an available M4 board keeps SymbOS from probing Symbiface. Correct conclusion?

Anyway, returning 0 is wrong, I will change that. If I remove it SymbOS boots from all disk versions correctly.

I'm curious, what are 0xFD4F, 0xFD41, 0xFD42 for? I have not found any documentation on these.

Those are ports used by SF3/RSF (https://www.cpcwiki.eu/index.php/RSF3#SF3_I.2FO_Ports)3

d_kef

Ahaaa. Thank you.

Quote- M4 ROM is 2.0.6, latest is 2.0.8

I might update it in v3.0.2 ;-)

Not necessary... just invoke "|upgrade" and you'll get the 2.0.8 version immediately. :)

Quote from: Emu on 15:41, 19 April 25The Dobbertin HD20 should work now, too. The file was not missing, but is created automatically (but in v3.0 the wrong folder was used, so probably it failed). Of course, you need to install the X-DDOS ROM (included) first.

That's a great new feature!  :) :) :)
Did you try is with FutureOS?

Quote from: GUNHED on 23:07, 23 April 25Did you try is with FutureOS?

Yes, but I did only a basic check if FutureOS can read the contents of the HD20. It does display the directory and also starts files (even without the X-DDOS ROM).

Quote from: Emu on 23:05, 22 April 25

Quote from: genesis8 on 21:24, 22 April 25When launching the emulator, I got an error cant find the ROM in ROM/\my path starting with H:, of course if I put :

I would like to understand this better. In which folder is CPCEMU.EXE and in where is %APPDATA%?

As stated portable version so H:\DL\AMSTRAD\EMULATEUR\name of zip file, and the subfolders of "name of zip file" not %APPDATA%.

So if I go to ROM manager instead of using the absolute path, it is adding my absolute path to a relative path "ROM" : if I edit the CFG file with the relative path "National/good rom name" it works as it adds "ROM/" + "National/.ROM"

For the pipe character not working, on an PC Azerty keyboard, the key is for the two french accents : circumflex ^(lower) and trema like the E in Noël (upper), so it's considered a dead key doing nothing till you type another character being a vowel.

Quote from: genesis8 on 08:55, 24 April 25For the pipe character not working, on an PC Azerty keyboard, the key is for the two french accents : circumflex ^(lower) and trema like the E in Noël (upper), so it's considered a dead key doing nothing till you type another character being a vowel.

There are indeed two key mappings missing. Please try the following in cpcemu.dat in section KEYTAB_FR:

a) modify line 286:

47, 0x23, 0x23, 0xff,

b) insert a line, e. g. after line 290:

53, 0x10062, 0xff, 0xff,

c) save the file

Quote from: Emu on 15:35, 24 April 25

Quote from: genesis8 on 08:55, 24 April 25For the pipe character not working, on an PC Azerty keyboard, the key is for the two french accents : circumflex ^(lower) and trema like the E in Noël (upper), so it's considered a dead key doing nothing till you type another character being a vowel.

There are indeed two key mappings missing. Please try the following in cpcemu.dat in section KEYTAB_FR:

a) modify line 286:

47, 0x23, 0x23, 0xff,

b) insert a line, e. g. after line 290:

53, 0x10062, 0xff, 0xff,

c) save the file

And it works ! Thanks a lot.

It will make things so much easier with any ROMs commands.

Quote from: genesis8 on 19:10, 24 April 25It will make things so much easier with any ROMs commands.

You're welcome. I've also fixed the portable ROM paths. I'm currently working on the automatic selection of national ROMs during the installation.

I have released v3.0.2. Several bugs have been fixed in this release:

• Android: Lagging hardware keyboard input.
• Missing or wrong mapping of some hardware-keyboard keys.
• Selection of keyboard layout during setup sets hardware keyboard layout now, too, and configures national ROMs where appropriate.
• SymbOS 4.0 boots from disks now.
• Fixed bank-switching bug: SymbOS boots with RAM sizes between 128k and 576k now.
• M4 board (Windows version): Folders can now be deleted, |CD,".." works now.
• M4 board/SymbOS: SD card live mode significantly improved, but still not reliable enough for production use. Caveat emptor! If you have used live mode before please make sure to
  restore all SymbOS files, they might have become damaged.
• Portable version (Windows): ROM paths are relative now.

Thanks to all bug reporters!

Hi, just tried the new version today (Win11 / Installer version 3.0.2. ).
Can confirm that M4 board emulation works now (means creating & deleting or diving into folders) in "image mode".

SymbOS still doesn't work. Either the mass storage or the disc version (I created a freshly installation) nor the discs (small boot disc or hybrid). And it doesn't matter which RAM config I have chosen (128k, 512k or 576k)

Out of curiosity I installed a new Windows 11 (AND a Window 7 version) in VirtualBox with a different username (because of the assumption of the hyphen in the username). But still the same behaviour as in my original Win11.

SymbOS boots up to the desktop and then crashes...

By the way: would it be possible to expand the Debugger Monitor to an external window?

Quote from: HAL6128 on 09:58, 25 April 25Can confirm that M4 board emulation works now (means creating & deleting or diving into folders) in "image mode".

Thank you for being perseverant! Just for clarity: Using AMSDOS, the M4 SD card is always emulated "live". The distinction between "image" and "live" mode is only related to SymbOS, the latter directly accessing the FAT file system on the SD card by reading and writing its sectors.

In image mode, the host SDCARD folder ist compiled into an image file called VSD.IMG. All sectors are read from and written into this file. At the end (reset, exit) all files from the image file that are newer than in the host SDCARD folder are extracted into the latter.

In live mode, all sectors are translated to and from host files on-the-fly. I'm afraid that this is impossible without collisions. In this particular case, one practical problem is that SymbOS appears to keep a certain amount of directory sectors in a cache. Therefore, the translation by CPCemu needs to be consistent between subsequent reads and writes. Which is a bit difficult if, on the other hand, modified and new files in the host file system should be visible within SymbOS as soon as possible. Because of the caching it can become necessary to overflow the cache (e. g., looking into a folder with many files in it, the folder being different from the one where the modified/new host files are) to see host-side modifications from within SymbOS. Bad things happen if SymbOS is writing a file of the same name as a new host file before SymbOS has refreshed its cache.

Quote from: HAL6128 on 09:58, 25 April 25SymbOS still doesn't work. Either the mass storage or the disc version (I created a freshly installation) nor the discs (small boot disc or hybrid). And it doesn't matter which RAM config I have chosen (128k, 512k or 576k)
Out of curiosity I installed a new Windows 11 (AND a Window 7 version) in VirtualBox with a different username (because of the assumption of the hyphen in the username). But still the same behaviour as in my original Win11.
SymbOS boots up to the desktop and then crashes...

I just tried it in Windows 7, too, 5 Minutes ago. It did work, both from disk and from SD card.

Have you used fresh SymbOS downloads? My only idea is that you used "used" files (that had been subject to the "live" mode at least once).
 

Quote from: HAL6128 on 12:24, 25 April 25By the way: would it be possible to expand the Debugger Monitor to an external window?

For the desktop versions, yes, I think so. Might be a good idea.

Quote from: Emu on 13:02, 25 April 25I just tried it in Windows 7, too, 5 Minutes ago. It did work, both from disk and from SD card.

Have you used fresh SymbOS downloads? My only idea is that you used "used" files (that had been subject to the "live" mode at least once).
 

I always downloaded a fresh version from internet and extracted it into directly the folder of the %APPDATA%\ROAMING\CPCEMU\SDCARD 

Quote from: HAL6128 on 09:58, 25 April 25SymbOS boots up to the desktop and then crashes...

Can you set CPCemu to 128k RAM (don't forget to restart), boot from "SymbOS-CPC40-Boot.dsk" with the M4 board disabled and make a 128k snapshot to post it here?

I have attached such a snapshot. What happens if you open it?

Ok, deactivating M4, setting to 128k RAM and booting from the disc works fine!

Quote from: HAL6128 on 13:38, 25 April 25Ok, deactivating M4, setting to 128k RAM and booting from the disc works fine!

That's a 64k snapshot only.

So, if you enable M4 (the rest staying the same), the disk does not boot anymore? What if you make the SD card empty?

Or, if you set RAM size to 576k (the rest staying the same), the disk does not boot?

Funnily it worked after enabled the M4 option. SymbOS booted correctly into main desktop.

Setting the RAM size to 576k afterwards leads to a crash.

Second test with SDCARD empty... and 576k RAM size leads to a proper booting of SYMBOS into the enhanced Desktop.

Your snapshot above works fine.

Quote from: HAL6128 on 18:33, 25 April 25Setting the RAM size to 576k afterwards leads to a crash.

When did you change the RAM size? Did you restart emulation after that? If so, when did it crash? After the splash screen? Only when booting SymbOS?

So, summarizing the current situation, booting SymbOS from disk works now both with and without M4 (with M4 only if SDCARD is empty) and both with 128k and 576k. Correct?

On the other hand, if you copy the contents of "SymbOS-CPC40-MassStorage" into "SDCARD", SymbOS still crashes after the start menu appears. Correct? If so, can you post a 128k (if 128k RAM size) or otherwise a 128k+ snapshot of the crashed system?

I changed the RAM size after booting 128k test and restarted the Emulator. The booting process stops always when the desktop taskbar on the bottom appears and then stops (no desktop symbols are loaded).

Quote from: Emu on 18:57, 25 April 25So, summarizing the current situation, booting SymbOS from disk works now both with and without M4 (with M4 only if SDCARD is empty) and both with 128k and 576k. Correct?

Yes.

Quote from: Emu on 18:57, 25 April 25On the other hand, if you copy the contents of "SymbOS-CPC40-MassStorage" into "SDCARD", SymbOS still crashes after the start menu appears. Correct? If so, can you post a 128k (if 128k RAM size) or otherwise a 128k+ snapshot of the crashed system?

I copied a new downloaded "MassStorage" content into the SDCARD folder and it crashed with the same 128k configuration which worked before (the disc one).

Attached the 128k Snapshot of the crashed system.

Quote from: HAL6128 on 19:18, 25 April 25Attached the 128k Snapshot of the crashed system.

The first thing that struck my attention is that your CPC was freezed when executing instructions in ROM 48. Do you have any such ROM configured?

The memory seems to be garbled somehow. Many places (with typical text strings) are offset compared to my snapshot. There are some data tables in your video ram, where they obviously don't belong.

One other thing: When I asked for the point of time when the crashed happened after changing to 576k RAM size I meant the crash of CPCemu (not of SymbOS) of which you posted the message-box screenshot above. Do you remember when it did happen?

And, another question: You wrote the boot process always stops with the taskbar, but without desktop symbols. How do you get to the situation in your snapshot (garbled screen) then? Just wait? Or open the start menu?

Quote from: Emu on 23:53, 23 April 25

Quote from: GUNHED on 23:07, 23 April 25Did you try is with FutureOS?

Yes, but I did only a basic check if FutureOS can read the contents of the HD20. It does display the directory and also starts files (even without the X-DDOS ROM).

Thanks a lot for testing!  :) :) :) :) Great to see the HD20 being supported!  :) :) :)

btw: FutureOS does not need other ROMs / software to work, so it's a good test for the emulation to see how faithfully the hardware is emulated and not only the 'included' software of an expansion. 

Quote from: Emu on 22:00, 25 April 25The first thing that struck my attention is that your CPC was freezed when executing instructions in ROM 48. Do you have any such ROM configured?

No, I didn't change anything regarding ROMs after installation of CPCEmu (only activated M4 / config of RAM size)

Quote from: Emu on 22:00, 25 April 25One other thing: When I asked for the point of time when the crashed happened after changing to 576k RAM size I meant the crash of CPCemu (not of SymbOS) of which you posted the message-box screenshot above. Do you remember when it did happen?

Oh, sorry. CPCEmu didn't crashes, was always reactive. I've always meant SymbOS as system.

Quote from: Emu on 22:00, 25 April 25And, another question: You wrote the boot process always stops with the taskbar, but without desktop symbols. How do you get to the situation in your snapshot (garbled screen) then? Just wait? Or open the start menu?

Ok, let me explain:

• config = empty SDCARD folder & 128k RAM & M4 enabled & SymbOS-CPC40-Boot.dsk >> this config starts correctly into SymbOS (total of 128k RAM in SymbOS available)
• conifg = empty SDCARD folder & 512k RAM & M4 enabled & SymbOS-CPC40-Boot.dsk >> this config starts correctly into SymbOS with e.g. background and sound daemon enabled (total of 448k RAM in SymbOS available)
• config = same config as 1. but with a filled SCDARD (unzipped fresh SymbOS masstorage files into that folder) >> this config creates a garbled screen (SymbOS crashed)
• config = same config as 2. but with a filled SDCARD (as 3.) >> this config creates a SymbOS-Desktop with a taskbar and then stops / freezes then. I can't do anything.

Quote from: HAL6128 on 09:46, 29 April 253. config = same config as 1. but with a filled SCDARD (unzipped fresh SymbOS masstorage files into that folder) >> this config creates a garbled screen (SymbOS crashed)
4. config = same config as 2. but with a filled SDCARD (as 3.) >> this config creates a SymbOS-Desktop with a taskbar and then stops / freezes then. I can't do anything.

I'm reluctant to ask, but I need to check: Are you sure you have copied all files extracted from "SymbOS-40-MassStorageCompletion.zip" into the symbos folder? I can only reproduce your crash/freeze of SymbOS if I solely copy the files from "SymbOS-CPC40.zip" into the SDCARD folder (but not the mass-storage completion files).

I also unzipped the "SymbOS-CPC40-MassStorage.zip" content into the SDCARD folder.
It should work.

It has definitely something to do with the SymbOS.INI file.
After deleting the file SymbOS boots correctly (and keep it deleted from the SDCARD folder). A freshly unzipped file produces the same troubleshooting as before.

Quote from: HAL6128 on 20:29, 30 April 25I also unzipped the "SymbOS-CPC40-MassStorage.zip" content into the SDCARD folder.
It should work.

I think we have found the problem. You have to extract a second ZIP archive called "SymbOS-40-MassStorageCompletion.zip (https://symbos.org/download/20250131-V40/SymbOS-40-MassStorageCompletion.zip)" and copy its contents into the symbos folder. Afterwards, it should look like this (please check for the APPS folder, in particular):

I forgot: You need to restore SYMBOS.INI. Otherwise you will still end up with an empty desktop.

Ok, you are right. It seems I totally missed the files from that "Completion" ZIP-container, which differs from the previous SymbOS versions. That was easy (...hm, not so for me  :laugh:).
Now, each version works perfectly (also the V9990 supported one). 
Again, very cool and thanks that you enhanced this emulator. 

Thanks a lot to @Emu for all the crazy hard work and @HAL6128 for all the testing! I am currently very occupied with another project, but it's really good to see, that everything is working!

Quote from: Emu on 22:37, 24 April 25I have released v3.0.2. Several bugs have been fixed in this release:

• Android: Lagging hardware keyboard input.
• Missing or wrong mapping of some hardware-keyboard keys.
• Selection of keyboard layout during setup sets hardware keyboard layout now, too, and configures national ROMs where appropriate.
• SymbOS 4.0 boots from disks now.
• Fixed bank-switching bug: SymbOS boots with RAM sizes between 128k and 576k now.
• M4 board (Windows version): Folders can now be deleted, |CD,".." works now.
• M4 board/SymbOS: SD card live mode significantly improved, but still not reliable enough for production use. Caveat emptor! If you have used live mode before please make sure to
  restore all SymbOS files, they might have become damaged.
• Portable version (Windows): ROM paths are relative now.

Thanks to all bug reporters!

On android version, I can see that some of the bluetooth controller buttons are now mapped to different keys, I would like to map them myself so I can use it in stead of on screen input. For instance select and fire B button are mapped to *break* and fire button A is mapped to the <enter> key. This is tested with 8bitdo bt controller.

Also the setup menu is cut of on tv screen when using android tv. Last visible line is 'start webserver'.

Quote from: diesoft on 06:15, 02 May 25I would like to map them myself so I can use it in stead of on screen input.

This is absolutely desirable. However, it requires an additional layer of indirection in my input code. Therefore, it will take time.

Quote from: diesoft on 06:15, 02 May 25Also the setup menu is cut of on tv screen when using android tv. Last visible line is 'start webserver'.

This is a bug I discovered only recently. Actually, the menu should scroll if you move through it. I remember that it had worked once. It should be easy to fix.

Hi again @Emu 

About the Android version... now it works perfectly with my Samsung Galaxy Tab S9 with its official keyboard and Dex mode active.

But when it is not in Dex mode, the "main" keys (all the letters and the space key) are not working, only the numeric keys and ENTER (even with the official keyboard).
I tried again with USB keyboard and another one with bluetooth (Logitech), and the problem is the same.

It is not a big problem for me, because I always use my tablet with its keyboard attached (and CPCEmu works well, as I said before), but I'm telling you about this problem for your information.

Best regards ;)

Quote from: ikerkaz on 11:01, 09 May 25but I'm telling you about this problem for your information.

Thank you. I will have to find out what the internal difference between Dex mode and normal mode is. Do you have another Android device to check if the keyboard doesn't work there in non-Dex mode, either? For me, it worked both on a Galaxy Tab with Android 5.0 and on a Nokia Phone with Android 10.

Quote from: Emu on 11:30, 09 May 25

Quote from: ikerkaz on 11:01, 09 May 25but I'm telling you about this problem for your information.

Thank you. I will have to find out what the internal difference between Dex mode and normal mode is. Do you have another Android device to check if the keyboard doesn't work there in non-Dex mode, either? For me, it worked both on a Galaxy Tab with Android 5.0 and on a Nokia Phone with Android 10.

I tried with my S23 Ultra and another bluetooth keyboard (normal mode, not Dex). The behavior is the same.
For your help, I tried with CPCEmu and with Azimuth (another emulator of the Play Store) and in both the result is the same, only the numeric keyboard and the enter key working... maybe some kind of bad configuration in my side?

Thank u very much ;)

Quote from: ikerkaz on 15:12, 09 May 25only the numeric keyboard and the enter key working... maybe some kind of bad configuration in my side?

Does the keyboard work correctly in other apps than emulators?

If not: I found hints on the web according to which NUMLOCK might be the culprit, e. g.: https://www.reddit.com/r/SamsungDex/comments/spj8yp/recent_weirdness_with_bluetooth_keyboard_s10/?rdt=51142

Quote from: Emu on 09:44, 12 May 25

Quote from: ikerkaz on 15:12, 09 May 25only the numeric keyboard and the enter key working... maybe some kind of bad configuration in my side?

Does the keyboard work correctly in other apps than emulators?

If not: I found hints on the web according to which NUMLOCK might be the culprit, e. g.: https://www.reddit.com/r/SamsungDex/comments/spj8yp/recent_weirdness_with_bluetooth_keyboard_s10/?rdt=51142

I tried with Samsung Notes and Whatsapp, both keyboards work correctly.

Inside your emulator, I pressed NUMLOCK in order to check the behaviour. The numeric keyboard works like a joystick or not, depending of the NUMLOCK status. This is the only difference; the letter keys don't show on screen with NUMLOCK pressed nor unpressed.

Quote from: ikerkaz on 12:03, 12 May 25The numeric keyboard works like a joystick or not, depending of the NUMLOCK status.

This is the way it should work.

What brand/type of keyboard do you have? Perhaps I find a similar one to test here.

Quote from: Emu on 20:17, 12 May 25

Quote from: ikerkaz on 12:03, 12 May 25The numeric keyboard works like a joystick or not, depending of the NUMLOCK status.

This is the way it should work.

What brand/type of keyboard do you have? Perhaps I find a similar one to test here.

Keyboard: Logitech K375s (bluetooth)
Mouse: Logitech M720 (bluetooth)

Also I tried with keyboard & mouse pack Logitech MK270 (separately keyboard is model K270 and mouse is M185) with an USB receiver (not bluetooth).

Quote from: ikerkaz on 21:05, 12 May 25Also I tried with keyboard & mouse pack Logitech MK270 (separately keyboard is model K270 and mouse is M185) with an USB receiver (not bluetooth).

I tried with a similar Logitech kbd (375? I don't remember exactly). It worked both in standard and desktop mode (not Samsung, however).

To understand better what happens: Does your keyboard have these issues only at the CPC command prompt (when typing BASIC commands) or only in the CPCemu menus or both?

Quote from: Emu on 23:59, 20 May 25

Quote from: ikerkaz on 21:05, 12 May 25Also I tried with keyboard & mouse pack Logitech MK270 (separately keyboard is model K270 and mouse is M185) with an USB receiver (not bluetooth).

I tried with a similar Logitech kbd (375? I don't remember exactly). It worked both in standard and desktop mode (not Samsung, however).

To understand better what happens: Does your keyboard have these issues only at the CPC command prompt (when typing BASIC commands) or only in the CPCemu menus or both?

It always happens at the prompt, and in the menus I don't have the option to write anything, but for example in the disk selection menu, if I press a letter the first DSK with that initial letter is selected, I don't know if I'm making myself clear.

Quote from: ikerkaz on 21:18, 21 May 25It always happens at the prompt, and in the menus I don't have the option to write anything

You can type filenames in the disk menu (to create an empty .DSK) and in the save-snapshot menu. It's the second-last violet input field in both menus. I think it is worth a try, see below!

Quote from: ikerkaz on 21:18, 21 May 25but for example in the disk selection menu, if I press a letter the first DSK with that initial letter is selected

So, if I understand you correctly, you can type letter keys in the menus and they make the menu jump to the respective letter - in standard mode (not DeX!). This means that the letter keys do work in the menus, but not at the prompt. You can only type numbers and Enter at the prompt. Correct?

@ikerkaz : I forgot to ask if the on-screen keyboard does work at the prompt. I assume so. Correct?