After nearly four months of hard work, I'm back with a new version of CPCemu. I'm very proud to present an exclusive feature:
-
Complete Almost complete emulation of an M4 Board (http://www.spinpoint.org (http://www.spinpoint.org)) using a host directory as drive C: (i. e. SD card; even for SymbOS), including network/internet connections, dynamic ROM simulation and (replaceable) Hack ROM (lower ROM). The only thing missing is the web interface. Many, many thanks to Duke for providing all necessary information and staying patient!
Other new features are:
- CRTC emulation of type 0 (register 8 ) and type 1 (register 6) even better than before.
- HYSNC and VSYNC emulation still a bit improved.
- Online help updated.
- Mouse pointer visible on movements.
- Correction of many small and big errors (in particular, 576 KB RAM work correctly now for the first time after decades) and improved error reporting. Please check if your personal error has gone. If not please re-report it here. It is well possible that I missed some.
(https://cpc-emu.org/BASICnetstat320.png)(https://cpc-emu.org/CPChessNET320.png)(https://cpc-emu.org/SymbOS320.png)
You can download the new version here: https://cpc-emu.org/download.html (https://cpc-emu.org/download.html)
Versions 2.3.1 and 2.3.2 correct several problems:
- File handling on systems with a case-sensitive file system.
- Missing folder "m4" in some Linux packages.
- Outdated online help on Android.
- Sound volume very high.
Version 2.3.2.1 corrects directory path problems in Raspberry Pi OS (64-bit version only).
Version 2.3.3 provides:
- Snapshot sizes of up to 576 K (uncompressed only).
- Default snapshot size can be changed in configuration file.
- New option to use on-screen joystick as cursor keys.
- Several bug fixes, in particular in the context of ROM handling.
Nice one 8)
Will test this on my Pi400 this evening ....
Ok, did some quick testing while taking a break from work ... looks good, works good, only some minor things :
- Sound is still way too loud (Pi400), even if I turn the volume down in the system to LOWEST setting ! Would it be possible to include a % volume into menu so you may turn down the volume inside the emu ?
- why do you use two times the same directorys ? inside cpcemu/ there are all the dirs (DISK, ROM, etc.) and they are copied over to /.CPCEmu also (same files inside) which is a hidden folder on Raspberry Linux ...
- M4 emulation is really nice but how do I do a M4 Reset or entering Hack Menu ? Did not found a key for that ... EDIT : Ok, found at least SHIFT-F1 for the Hack Menu ;)
- also M4 emulation : the emulated M4 gets the same IP as the host machine, but how do I connect to it from browser ? Even from another machine it is not possible to get to the web interface.
Nice sounding update! Maybe I should bring my 400 to the office now that summer is here :D
Btw I tried to upload some roms on CPC itself with |ROMUP,"NAME.ROM"",5 (Example) but it won't show up ....
Thanks for the upgrade!
Two things...
- The M4 is 2.0.6, in real life it's already 2.0.7 (important update for some, also new hack menu)
- How can I install ROMs?
I try first the GNU/Linux version for x86-64 and I found a bug, the emulator stop working because $HOME/.CPCemu/cpcemu.cfg is a empty file (0 bytes).
I solved copying cpcemu0.cfg over $HOME/.CPCemu/cpcemu.cfg and make a SDCARD directory where I unzipped CPCEmu.
About M4 emulation:
- If I type |NETSTAT show the info of the host and I can't access via web.
- I try to change directory with the command:
|DIR,"MYDIR" but sometimes show "Unknowing directory" or can't see files in the directory.
Some answers:
- I wrote "complete", but that's not true. There is no web interface, because the host has direct access to all files anyway. The CPC uses the same IP address as the host, because an emulated WiFi network would be rather useless with only two participants (CPC and host).
- If desired, V2.0.7 of the M4 ROM can be copied into the ROM folder manually or by just calling |UPGRADE. The only downside I know is that it calls the SD card drive "A:", again. The letter "C" is my only modification to V2.0.6.
- ROMs can be installed with |ROMUP (apart from "mounting" them in cpcemu.cfg, of course). They are activated by |ROMUPD. Should this happen automatically at the next hard reset (F8)? I'm afraid I did not try this on my real M4 Board.
- I use (apparently redundant) read-only source directories (e. g. ROM and DISC) so that CPCemu can be installed at a central folder by an administrator where others only have read access (e. g. in Windows' "Programs (x86)" or in Mac's "Applications"). This way, every user can have his own configuration and files. Besides, this is mandatory for Android and iOS, even without an administrator.
- There is no separate M4 reset so far. Why would one be needed apart from F8?
- I really forgot the sound volume problem. And, I still don't understand where it comes from. I'm a bit afraid that an additional volume multiplication could further slow down the sound output on the Pi, for me it is already delayed by a few seconds.
@CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) : Is there any pattern for the situations where |DIR does not work? Does it help just to retry |DIR to make it work or does it reproducabily depend on the folder name (or a name in the full path)? Maybe something with wildcards? Have you tried if |CD works in cases where |DIR doesn't?
Quote
I wrote "complete", but that's not true. There is no web interface, because the host has direct access to all files anyway. The CPC uses the same IP address as the host, because an emulated WiFi network would be rather useless with only two participants (CPC and host).
but it would make things SOOO much easier, handling roms would be nice AND we could establich a CPCEMU <> CPC Network[QuoteIf desired, V2.0.7 of the M4 ROM can be copied into the ROM folder manually or by just calling |UPGRADE. The only downside I know is that it calls the SD card drive "A:", again. The letter "C" is my only modification to V2.0.6.
|UPGRADE isn't working (Download Error)
QuoteROMs can be installed with |ROMUP (apart from "mounting" them in cpcemu.cfg, of course). They are activated by |ROMUPD. Should this happen automatically at the next hard reset (F8)? I'm afraid I did not try this on my real M4 Board.
As I said above.... isn't working ... see this ....(https://i.ibb.co/xJsgzZh/IMG-20210708-232808.jpg)
P.S : regarding the sound .... no delay here on 64Bit Pi 400 .... everthing really fine and smooth .... but too loud ;)
Oh, and btw. this is the same PARADOS.ROM that works fine on my real M4 ...
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) :
The correct sound is interesting. Are you using Raspberry Pi OS? Sound output via HDMI?
Theoretically, a web interface would work even in the current setup. The only condition is if the TCP port is available on the host. By the way, network connections between CPC and host and between two CPCemus are possible already now, of course. For example, I can confirm that CPChessNet works between to CPCemus on the same host.
Regarding |UPGRADE: Is there a folder M4 in your SDCARD directory? I think so, because |ROMUP works for you. So, the error must have a different reason. Please start CPCemu from a terminal window, there should be an error message when executing |UPGRADE.
Regarding |ROMUPD: I've just tried doing the same you did and it worked. |M4HELP shows "5 PDOS" after |ROMUPD. Please post the files ROMCONFIG.BIN and ROMSLOTS.BIN in M4 both before and after |ROMUPD.
@CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) :
I think the reason for your problems with |DIR and probably also |CD might be Linux' case-sensitive file system. I have to check this on a Linux machine. I remember this problem was reported for file access via |TAPE. I have not solved this, yet.
|UPGRADE error in terminal : "fopen : No such file or directory" and yes, M4 folder is there but it's empty except the M4.DIR file
Regarding the |ROMUPD : I can post the files AFTER but before the first |ROMUPD the M4 folder is empty (see above)
Oh btw, using Raspbian OS 64Bit from official site :)
-> https://downloads.raspberrypi.org/raspios_arm64/images/raspios_arm64-2020-05-28/2020-05-27-raspios-buster-arm64.zip
Thank you. I had a Linux VM up and running just a few minutes ago and observed the same behaviour.
The reason is indeed the case sensitivity of Linux. As a first workaround, please rename your M4 folder to m4, this makes |UPGRADE work.
This will probably also make |ROMUPD work, because it uses the same hard-coded path to "m4".
As for some strange reason the SDCARD folder is missing from some packages (Intel 32-bit and 64-bit, Rasperry 32-bit package) I have to recreate these anyway and will recreate also the Raspberry 64-Bit package, because it's "M4" in there at the moment.
|UPGRADE now works (with "m4" in lowercase) but on |ROMUP I get a "Fire not found or other error."
Tried both lower and upper case letters for the parados.rom, same error msg...
(https://i.ibb.co/3dm2ZQG/2021-07-09-162814-1680x1050-scrot.png)
I'm looking into the code. I assume the problem is now that the path to ROMSLOTS.BIN (including "m4") is converted to upper case, which does not exist. I'm checking where to implement case insensitivity. It's not trivial.
For the time being, you could try to create a Symlink from M4 to m4.
Quote from: Emu on 21:56, 08 July 21
@CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) : Is there any pattern for the situations where |DIR does not work? Does it help just to retry |DIR to make it work or does it reproducabily depend on the folder name (or a name in the full path)? Maybe something with wildcards? Have you tried if |CD works in cases where |DIR doesn't?
I confirm than only find files and folders all in uppercase.
Tried symbolic Link already, same Error ... Waiting for your Investigation I guess :)
But the emu itself ist really good now :) keep it up
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) , @CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) :Please try v2.3.1 (https://cpc-emu.org/download.html). I don't claim my case-sensitivity solution to be perfect, but it appears to work.
Besides, I have reduced audio wave generation by a factor of 2. I think this should correspond to the other audio sources. Please report if this improves your situation. By the way, I tried the audio jack on Raspberry and found that there is no delay here. Obviously, HDMI audio is the problem.
Ok, |UPGRADE works fine, sound is good as is ....
But |ROMUP/|ROMUPD didn't work ... ROMCONFIG and ROMSLOTS were created but nothing else shows up in emulation .... I have attached those ....
Oh no, I missed two places where I should have inserted my case-insensitivity correction, too - one in the code for |ROMUPD, one in |DSKEXT.
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Please try v2.3.2 (https://cpc-emu.org/download.html). |ROMUPD should work now.
Quote from: Emu on 01:30, 12 July 21
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Please try v2.3.2 (https://cpc-emu.org/download.html). |ROMUPD should work now.
Still doesn't work .... It won't show up at all, I also tried the ROMUP464.BIN from spinpoint.org for installing basic 1.1 and modified lower rom for 464, also doesn't work !
Is there a way to log the actions (Terminal shows no output when performing ROMUP and ROMUPD) ??
Is there any interface to set the roms on M4 from CPC (not web interface) ?
thanks
Yes, the application ROManager of FutureOS.
Hello
I write |sd , save"hello" , cat and I can see the new file, but I can't see the new file on linux file system inside cpcemu-2.3/SDCARD or cpcemu-2.3/SDCARD/M4
Then, where is the file?
Quote from: Fran123 on 10:43, 13 July 21
Hello
I write |sd , save"hello" , cat and I can see the new file, but I can't see the new file on linux file system inside cpcemu-2.3/SDCARD or cpcemu-2.3/SDCARD/M4
Then, where is the file?
There's a hidden folder in your home dir called ".CPCemu" , inside you find SDCARD and your saved files ...
If you're using terminal just enter "cd ~/.CPCemu"
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) :
I found the problem. It was a newbie error, "strcpy" with overlapping strings, shame on me. It occurred only on 64-bit Raspberry Pi OS, the other OSes (including 32-bit Raspberry Pi OS) are more tolerant as it appears.
While looking for the bug, I've also found that the SDL message-box system does not work on 64-bit Raspberry Pi OS, either. So I reverted to printing status and error messages to the terminal window, but on all other operating systems it is possible to keep SHIFT pressed while exiting from CPCemu to bring up a log of the messages.
So, there is a v2.3.2.1 (https://cpc-emu.org/download.html) available now, but for the Raspberry Pi only. The other versions should still work as expected (including the SHIFT-on-exit option).
Quote from: ajcasado on 12:15, 12 July 21
Yes, the application ROManager 2.37 for FutureOS.
Oh, that works? Great! :) :) :)
And I can confirm that |romup and |romupd now works fine ;D
Great work @Emu (https://www.cpcwiki.eu/forum/index.php?action=profile;u=4040) ... This is absolutely my fav emu for Pi platform now for testing 8)
Quote from: GUNHED on 16:33, 14 July 21Oh, that works? Great!
Well, I have not tried it using CPCEmu. :-[
Quote from: ajcasado on 21:54, 14 July 21
Well, I have not tried it using CPCEmu. :-[
It's a good test for the emulator anyway. :) :) :)
Quote from: Emu on 19:09, 11 July 21
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) , @CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) :Please try v2.3.1 (https://cpc-emu.org/download.html). I don't claim my case-sensitivity solution to be perfect, but it appears to work.
I try 2.3.1 in my Ubuntu 20.04 and I have the same problem, only can change to dir or run files with all letters in uppercase.
I also try Android version but I still can't open external DSK (Android 10).
Quote from: CPCBEGIN on 15:33, 15 July 21
I try 2.3.1 in my Ubuntu 20.04 and I have the same problem, only can change to dir or run files with all letters in uppercase.
I also try Android version but I still can't open external DSK (Android 10).
AFAIK the final solution for upper/lower case was with 2.3.2 ....
Quote from: SkulleateR on 16:04, 15 July 21
AFAIK the final solution for upper/lower case was with 2.3.2 ....
Sorry, I said 2.3.1 but the Ubuntu version I probe was 2.3.2... by the way, the number of version doesn't show correct in wellcome screen.
It's a little bit pitty that there's no built in assembler with in the Emu. But with RASM you are able to code directly into the SD drive and makes an easy work flow.
The first Emu which supports working and developing for the M4 board. The webinterface is not necessary and the Emu has a built in hack possibilities.
Very nice, great work.
Quote from: GUNHED on 21:57, 14 July 21It's a good test for the emulator anyway. :) :) :)
Ok, I tested it and found several bugs, I'm using Manjaro Linux.
-Saving the config file causes sometimes that in the configuration file the path of the sdcard is erased (M4_SD_PATH = "). The final statement (end;) also.
-Restarting the emulator causes all roms (but the lowest one) flashed with |romup command (and ROManager tool) to be corrupted.
-Flashing several roms must be done from the highest numbered one to the lowest, if a higher numbered rom is flashed all the lower numbered roms are corrupted.
-Between |romup commands the command |romupd must be issued, otherwise only the last |romup command take effect.
-FutureOS installer fails to install its roms but ROM -D-. The roms must be flashed using the |romup command. I wrote a small basic program to do it (see attachment). Roms numbers must be configured with the FutureOS provided tool.
-When using the default rom numbers of FutureOS it cannot be booted. The numbers must be under 16 for FutureOS to start properly.
-In FutureOS runinng an application corrupts the date and time values when using the M4 as RTC.
-If ROManager is used in FutureOS all the roms with lower number than the modified one are corrupted, same behaviour as with the |update command.
Despite the bugs CPCemu is very handy, I think that emulating the M4 is a great and very useful achievement, congratulations. 8)
Thanks for all that testing.
So, it would be great to have 32 ROMs. :) :) :)
Quote from: GUNHED on 00:08, 17 July 21
So, it would be great to have 32 ROMs. :) :) :)
i do not understand why emulators are limited to 16 (wtf?) or 32 ROMs... => gogogo to the maximum => 256!
Quote from: GUNHED on 00:08, 17 July 21So, it would be great to have 32 ROMs. :) :)
The 32 roms works ok. I tested with booster rom in slot 15 and the bombjack 3 roms pack form the wiki roms list in slots 29, 30 and 31.
Bomb jack runs ok from this slots.
EDIT. It works, but the |m4help command doesn't show correctly the rom names in slots 30 and 31.
@GUNHED (https://www.cpcwiki.eu/forum/index.php?action=profile;u=2029) : What do you mean by "to have 32 ROMs"?
@roudoudou (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1714) : The M4 Board provides only 32 slots. I emulate an M4 Board. So, I provide 32 slots. I'm not even sure if the M4 ROM is able to handle more than 32 slots. If there is anybody really in need of more than 32 slots, he (or she) can mount them manually (and outside of CPCemu) in cpcemu.cfg. If you need more than 32 ROMS configurable from within the CPC I can discuss it with Duke.
@ajcasado (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1987) : Where can I find this booster rom? Are roms 30 and 31 listed with wrong names or as the usual "BASIC"?
@CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) : It appears that the bug with strcpy is present with Ubuntu's libc, too. So, I will release v2.3.2.1 for Intel Linux, too.
By the way, I have submitted CPCemu to the Google Play Store recently. Let's see if it complies with all their requirements. As I had already written earlier, I had to remove the permission to access other folders than those of CPCemu.
Quote from: Emu on 20:39, 17 July 21@ajcasado : Where can I find this booster rom? Are roms 30 and 31 listed with wrong names or as the usual "BASIC"?
You can download it from here: https://www.cpcwiki.eu/index.php/ROM_List (https://www.cpcwiki.eu/index.php/ROM_List)
This thread explains how it works: https://www.cpcwiki.eu/forum/programming/understanding-booster-rom/ (https://www.cpcwiki.eu/forum/programming/understanding-booster-rom/)
I put it in slot 15 using config.cfg.
You can get also 32 roms initialised using the firmware 3.1 lower rom from TotO, is also in the ROM list page of the wiki, but I cannot get it working in CPCEmu. When emulation starts the screen scrolls in a closed loop and no input is possible. I tried to use it changing the slot 255 configuration in config.cfg.
The names seems to come from a buffer where the file names used with |romup command are stored, see it in the attached screenshot.
Quote from: ajcasado on 21:13, 16 July 21-When using the default rom numbers of FutureOS it cannot be booted. The numbers must be under 16 for FutureOS to start properly.
Well, that is not true. I flashed them in roms 28, 29, 30 and 31 with the booster rom in slot 15 and it boots. But with no booster rom and the default rom numbers (10, 16, 17 and 18) it doesn't boot.
Another issue that I found is that you cannot navigate upwards in the directory tree using the M4 Frontend from Abalore.
Quote from: Emu on 20:39, 17 July 21
@GUNHED (https://www.cpcwiki.eu/forum/index.php?action=profile;u=2029) : What do you mean by "to have 32 ROMs"?
Upper ROM slots from &00 to &1F (0-31). :)
Quote from: Emu on 20:48, 17 July 21
By the way, I have submitted CPCemu to the Google Play Store recently.
I can't find CPCemu in Play Store, can you provide us a direct link to download the emulator from Google Play Store?
@Emu (https://www.cpcwiki.eu/forum/index.php?action=profile;u=4040)
Some really odd things happen ...
1. when disabling M4 in cpcemu.cfg the installed Roms will be still mounted
2. emulating CPC464 with M4 : inserting a DSK makes the emulation crash, parados rom works (|DRIVE)
3. emulating CPC6128 with M4 : inserting DSK works but parados rom won't work at all
4. disabling M4 in CFG, then emulating 6128 -> parados still mounted, DSK works and parados also works
Oh, wow, that sounds bad. I will look into all of these issues as soon as possible, but I have to travel from Wednesday to Friday of this week.
@CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) : The Play Store was only a teaser. I submitted CPCemu, but this means that Google has to check (review) it before it is published. Yes, and Google currently reports "We're experiencing longer than usual review times", so be patient, please.
@GUNHED (https://www.cpcwiki.eu/forum/index.php?action=profile;u=2029) : Why do you think that these slots don't work in the M4 emulation?
I'm still investigating the strange behaviour with some ROMs. Currently, I have not even a clue if the bug is in the M4 ROM or in the emulator.
Meanwhile, I have released v2.3.2.1 (https://cpc-emu.org/download.html) for Intel Linux, too. This should fix the directory problems.
Perhaps this would be worth a separate thread (@CPCBEGIN ): CPCemu for Android is now available (https://play.google.com/store/apps/details?id=com.loritznet.softwarecreations.cpcemu) in the Google Play Store for the first time!
I gave now the latest CPCEmu also a try (Linux version) and I am happy to see that the case-sensitivity issue with the TAPE emulation is now resolved. Thanks a lot for that.
One thing that I noticed (and which most likely was already present in earlier versions): I tried to make cpcemu available by just copying the executable "cpcemu" into /usr/local/bin and making sure that I have the paths in /.CPCemu/cpcemu.cfg. However, there seems to be no configuration for the path of the file cpcemu.msg. Seems this file always needs to be in the current working directory from which cpcemu is started. Otherwise it will give us segfault and this debug window says "MSG: Cannot open message file cpcemu.msg".
@ajcasado (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1987) :
Quote-Flashing several roms must be done from the highest numbered one to the lowest, if a higher numbered rom is flashed all the lower numbered roms are corrupted.
-Between |romup commands the command |romupd must be issued, otherwise only the last |romup command take effect.
Can you give an example for which ROMs this happens? I cannot reproduce it. Which system (CPC and host) are you using?
Quote-When using the default rom numbers of FutureOS it cannot be booted. The numbers must be under 16 for FutureOS to start properly.
Well, that is not true. I flashed them in roms 28, 29, 30 and 31 with the booster rom in slot 15 and it boots. But with no booster rom and the default rom numbers (10, 16, 17 and 18) it doesn't boot.
That's expected behaviour. Background ROMs (such as FutureOS) are detected only up to ROM 15. You can extend this range with said booster ROM mentioned above.
QuoteEDIT. It works, but the |m4help command doesn't show correctly the rom names in slots 30 and 31.
This is a problem of the M4 ROM. It reads the ROM name from the RSX table as if they were background ROMs (type 1), which is true for the first Bomb Jack ROM, but actually the others are of type 2 (extension-foreground), so they don't have an RSX table and thus no name. I will tell Duke so that he can consider improving the ROM code.
QuoteWhen emulation starts the screen scrolls in a closed loop and no input is possible.
I've found this behaviour in the 464 emulation. I think I've also found the bug causing it yesterday.
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) :
Quote1. when disabling M4 in cpcemu.cfg the installed Roms will be still mounted
4. disabling M4 in CFG, then emulating 6128 -> parados still mounted, DSK works and parados also works
Yep, correct. I've found the bug and removed it.
Quote2. emulating CPC464 with M4 : inserting a DSK makes the emulation crash, parados rom works (|DRIVE)
I think I've also found and fixed this one.
Quote3. emulating CPC6128 with M4 : inserting DSK works but parados rom won't work at all
This is correct behaviour, I verified it with my real M4 board. In |SD mode, |DRIVE returns immediately with "Ready". In |DISC mode it returns with "Bad command".
What helps is making ParaDOS ROM no. 7 (replacing AMSDOS), but I've not tried if the latter is possible with the M4 board at all (neither the real one nor the emulated one).
Quote from: Emu on 10:37, 26 July 21
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) :Yep, correct. I've found the bug and removed it.
I think I've also found and fixed this one.
Great news 8)
Quote from: Emu on 10:37, 26 July 21Can you give an example for which ROMs this happens? I cannot reproduce it. Which system (CPC and host) are you using?
Hi,
I'm not close to my PC now so I cannot send a capture. I'm using Manjaro Linux.
In about three weeks i'll post captures whith this behavior.
Thanks for checking.
Edit: This happens with all roms.
Quote from: Emu on 10:37, 26 July 21That's expected behaviour. Background ROMs (such as FutureOS) are detected only up to ROM 15. You can extend this range with said booster ROM mentioned above.
For FutureOS to boot only ROM A must be under slot 16, so using slots 10, 16, 17 and 18 should work.
Anyway this problem can be bypassed easily so I guess it is not very important to fix it.
Finally I get inject a DSK to CPCEmu for Android using Total Commander.
(https://i.ibb.co/sHB8v0r/IMG-20210727-184659-574.jpg) (https://ibb.co/3zJgyDH)
Only I can do this with play store version.
But now, I can't play games like Pinball Dreams, because the keys aren't mapped in Android keyboard.
(https://i.ibb.co/KVp7VHs/Screenshot-2021-07-27-21-14-16-161-com-loritznet-softwarecreations-cpcemu.jpg) (https://ibb.co/dkw6kyp)
I know. Android and keyboard input, in particular real-time input, is a pain in the *ss, even with a Bluetooth hardware keyboard connected. No cursor keys detectable, unbelievable.
One way I see would be an option to redefine the buttons of a Bluetooth game controller to produce the keys needed. But that's probably not what most people want - carrying a controller along with them in the subway.
Another way I came up with recently is to make the touch screen joystick result in cursor key strokes. There is already an option to use the cursor keys as a joystick, so this new thing would be just the other way round. Of course, this would only work where no joystick input is needed. What do you think? Would this be helpful?
For me old computer games are nearly unplayable on mobile devices, except for a few titles; see Baba's Palace (Android version) or Millie and Molly (https://play.google.com/store/apps/details?id=com.BelowTheTower.MillieandMolly&hl=en_US&gl=US) (really lovely little game!). But you can see that's a whole different direction.
However, a decent solution that works with controllers would provide a great option for my TV or Nvidia Shield TV!
I've just uploaded v2.3.3 that provides:
- Snapshot sizes of up to 576 K (uncompressed only).
- Default snapshot size can be changed in configuration file.
- New option to use on-screen joystick as cursor keys (fire button acts as COPY).
- Several bug fixes, in particular in the context of ROM handling.
@CPCBEGIN (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1472) : The joystick option might help you. Please report.
@ajcasado (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1987) : I hope most of your problems are solved now. Please report.
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Please try if all of the bugs you found are fixed.
@ajcasado (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1987) : I would like to explore this further.
QuoteFor FutureOS to boot only ROM A must be under slot 16, so using slots 10, 16, 17 and 18 should work.
As far as I understand, this configuration can only work if the ROMs are modified by the ROM number utility on the installation DSK. Is this correct?
@Gryzor (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1) : CPCemu is already able to use a game controller (if one is attached). What exactly are you missing? (No offense, I'm just asking to make CPCemu better.)
In general, I think retro gaming is exactly the only thing that really works on mobile devices (if and only if the game is controlled by a joystick). The on-screen joystick of CPCemu should be exactly what you need. And even if you have to press "1" for single player by using the on-screen keyboard, this should be acceptable.
I confirm that it is nearly impossible to play games (or use other software) that requires key strokes.
@sb1903 (https://www.cpcwiki.eu/forum/index.php?action=profile;u=4184) : Why not install the CPCemu folder to /usr/local/cpcemu-2.3 and create a script /usr/local/bin/cpcemu that calls /usr/local/cpcemu-2.3/cpcemu, but executes a "cd /usr/local/cpcemu-2.3" before?
I've installed CPCemu 2.3.3 Android multiarch in a Samsung Galaxy Tab A, Android 8.1.0, and having a problem: when I power off the virtual machine from the menu and start it again, the emulated CPC works fine, but the menus and the splash screen shows distorted, or blank, or with garbage. The same happened with the 2.2 version.
Other than that, the app works really good.
Quote from: Emu on 21:19, 30 July 21
@Gryzor (https://www.cpcwiki.eu/forum/index.php?action=profile;u=1) : CPCemu is already able to use a game controller (if one is attached). What exactly are you missing? (No offense, I'm just asking to make CPCemu better.)
In general, I think retro gaming is exactly the only thing that really works on mobile devices (if and only if the game is controlled by a joystick). The on-screen joystick of CPCemu should be exactly what you need. And even if you have to press "1" for single player by using the on-screen keyboard, this should be acceptable.
I confirm that it is nearly impossible to play games (or use other software) that requires key strokes.
Oh nothing missing, that was a general observation. Can't stand touch, on screen joysticks! If it runs on my Shield TV then it's all I need. Only device I managed to enjoy some Dreamcast titles on!
Quote from: Emu on 21:21, 30 July 21
@sb1903 (https://www.cpcwiki.eu/forum/index.php?action=profile;u=4184) : Why not install the CPCemu folder to /usr/local/cpcemu-2.3 and create a script /usr/local/bin/cpcemu that calls /usr/local/cpcemu-2.3/cpcemu, but executes a "cd /usr/local/cpcemu-2.3" before?
OK, that way it's working :) Thanks!
Quote from: Emu on 21:07, 30 July 21
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Please try if all of the bugs you found are fixed.
Oh great, will try as soon as I get home tomorrow 8)
Rom Handling seems fine now :)
But I came across another weird issue, as soon as I start the emu, the main system sound gets distorted and gets back to normal when quitting the program ...
Made a short clip so you can hear it (had webradio on, but it happens with all other sound sources as well) :
https://youtu.be/LyVSAWVxm5U (https://youtu.be/LyVSAWVxm5U)
Is it possible that the Pi is just overloaded with multimedia from different processes? Did this problem occur with v2.3.3 for the first time? I would assume it existed before...
Definitely not overloaded with only a web radio running besides the emulator, I could even play a youtube video, web radio and have Vice and other emulators running at the same time without getting this issue ...
And yes, it was there before but I simply did not check that before because I had the sound disabled or didn't have a second sound output enabled.
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Is there any special setup in your Pi? Would you be so kind and check when (in which version) this problem appeared for the first time? I'll try with my Pi 4 and the 400 as soon as I can, too.
Only "specal" Item is the USB sund card because my monitor got no HDMI audio so I needed a decent sound output but as I said, it works with all of the other sound sources like youtube, webradio, other emulators !
And I just downloaded 2.2 again (first ARM64 Version) and the problem is there too ...
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Thank you. Could you also try if the sound problems are present when using the analog audio jack of the Pi?
@Emu (https://www.cpcwiki.eu/forum/index.php?action=profile;u=4040) : Sorry, the Pi400 got no audio jack, only HDMI sound output (but my monitor got no speaker), so I got myself an USB sound card with audio jack ...
And just to add this : the sound itself seems to be "broken". Even if the CPC-EMU is the only sound source. Just played Gryzor and all of the FX is distorted, extremly noticable if you take the laser in level one (first extra item)
Oh no, I've never noticed that there is no audio jack, but it's true. Unbelievable.
Unfortunately, I don't have an USB sound card.
Would you be so kind to try the HDMI output on your television set? Just to check if the problem is USB-only.
The distortion really seems to be USB only !
There's a huge sound lag when using BT but I think that's BECAUSE of BT, so never mind that ;) HDMI sound output is ok !
1994 news from AA
(https://www.gavpugh.com/wp-content/uploads/2010/05/aa104-081.jpg)
@SkulleateR (https://www.cpcwiki.eu/forum/index.php?action=profile;u=3124) : Thank you very much! So, the next check would be a different USB sound adapter. Have you tried if the USB sound is better with a 32 bit OS?
@Emu (https://www.cpcwiki.eu/forum/index.php?action=profile;u=4040)
Tried with 32Bit (fresh Raspian OS install) -> same distortion
I also tried various other programs (like VICE 3.5, VLC, CPCEC, DosBOX, etc.), they all sound normal (on 64Bit this is)
Gemjam (https://www.cpcwiki.eu/forum/programming/my-lockdown-project-a-bejeweledcandycrush-clone/) doesn't show the screen in any of the checked systems: Ubuntu 20.04, Debian 10, Raspberry pi OS, Android 10.
I make a new thread to Android version problems (https://www.cpcwiki.eu/forum/emulators/cpcemu-for-android) for avoid mixing its specific problems.
Thank you for the report. I will look into the issue. I've also found a few bugs in the meantime. And I'm still thinking of a selfmade Android keyboard.
I've found the problem. The R register of the CPU was erroneously initialised with 0xff where it should have been 0x00. Gemjam was waiting for a value less than 0x7e, which did never happen as R changes only in its lower 7 bits, but its MSB was set all the time.
Just a feature suggestion.
As a debug feature, would it be hard to have a memory coverage view. It would comprise a reset coverage function which clears the memory coverage view.
Then, any executions beyond that track the coverage. Coverage tracked in 2 ways, you could represent it as squares in 2 charts, but would be better 2 colours within a square like a triangle (red & blue). One coverage is anything that goes through the PC, basically which code was executed. The other coverage is anything that goes through any other memory access instruction. In the case where there is both access & code executed in the same memory location - due to reallocations over time, self-modifying code or whatever else, it that is where the split square shows. So, basically show the coverage between a reset coverage and a pause. Perhaps you can re-reset during the pause if you are happy, and maybe you can save the coverage charts.
A future extension of this could be to allow that coverage chart to be marked (in mass) with breakpoints - like a memory protection when debugging, i.e. stop the code if it somehow jumps out of this memory space.
Not sure if anyone else thinks this is a useful feature.
The M4 support is superb!!
I miss a more flexible debugger, with the instructions flow showed and an easy method to put breakpoints, like put it with the mouse on the instructons flow like winape
It will be better for analyse code, especially for the M4 board code and behaviour.
The emulator is great, but with this... more great even :)
To verify how faithful the M4 emulation is, you can use FutureOS 2023 including ROM M for M4. Use the installation Disc and install to M4.
If problems occur, then the emulation probably can be improved.
Why do I mention this? Up to now, I wouldn't know a 100% faithful M4 emulation.