Acorn BBC Micro Emulator (current?)

Folly

As far as I can tell they both should work, but It has been a while.

I just installed b-em-allegro4 with succes on my Debian 11 / Pi4 setup.
I tested both, running a game, in my Desktop environment.

My guess is that they both should work on your installation.

Folly

@smartgenes

Just tried @valerino 's beebem script and I got it working now.
Have to do some more investigation though.

smartgenes

@Folly Getting a lot of errors from the Valerino fork, e..g. script module was skipped as wifi is already used by retropie-setup/scriptmodules/supplementary/wifi.sh and so on, what's the best way to purge it/remove the error messages?

Folly

@smartgenes

You probably have a duplicate error.
Just remove that one of Valerino and you should be fine.

Any progress on running these b-em's ?

smartgenes

@Folly Rather than remove I saw there was an option in Retropie Setup under Valerino's BeebEm to 'clean'and that worked.

I fired up Countdown to Doom and Axe of Kolt and both appear to be working great :-)

One question though, after I updated RetroPie, many emulators, e.g. ZX Spectrum and this BBC Micro emu aren't opening in a full-screen which fills the page but in a window, any idea why?

I also have an error which I haven't been able to get rid of for a while 'xrandr: Failed to get size of gamma for output default'.

Folly

@smartgenes said in Acorn BBC Micro Emulator (current?):

BBC Micro emu aren't opening in a full-screen which fills the page but in a window, any idea why?

If you are talking about b-em-allegro4 then that is correct.
You have to go to the menu and select fullscreen each time.
There is no way around that, only if the emulator is patched somehow to open in fullscreen at start.
But that is something we only managed with elkulator, sadly not b-em.
The xbeeb and xmaster work in a matchbox and should start fullscreen if you do not run it in the Desktop environment.

Folly

@smartgenes said in Acorn BBC Micro Emulator (current?):

xrandr: Failed to get size of gamma for output default

Try to do the same command like this :

sam@trinity: xrandr
xrandr: failed to get size of gamma for output default
Screen 0: minimum 1024x768+0+0 0mm x 0mm
  1024x768     76.00*

If you have somewhat the same output, with only one resolution, then your video driver doesn't work properly or your monitor/TV can't do many resolutions.
Are you using a regular PC, not an RPI ?

xrandr is used in X11/Desktop environment or when using XINIT.
So when a program tries to get supported resolution through xrandr it will fail with : xrandr: failed to get size of gamma for output default

A good output should be something like this :

Screen 0: minimum 320 x 200, current 1600 x 900, maximum 7680 x 7680
HDMI-1 connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 440mm x 250mm
   1600x900      60.00*+
   1920x1080     60.00    59.94  
   1440x900      59.90  
   1280x800      59.91  
   1152x864      75.00  
   1280x720      60.00    59.94  
   1024x768      75.03    60.00  
   832x624       74.55  
   800x600       75.00    60.32    56.25  
   720x480       60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08

smartgenes

@Folly When I type xrandr I get
Failed to get size of gamma for output default Screen 0: minimum 592x448 maximum 592x448 etc,
just one measurement.

I have LXDE - Lightweight X11 Desktop Environment, this was a pre-made image which was useful to me as it has the desktop environment on top of Retropie, which is great for building gamelists. I'm not sure how exactly it was built. (It's Pi not PC)

I've had the xrandr error message a while, what can I do to get rid of it?

The ZX Spectrum emulators changed from full screen to an inset box with a large black border after update and also some other emus seemed to open differently to before. So I thought it might be a similar issue with the BBC emulator (b-em-allegro4) but I guess in this case it's just a limitation.

Any idea what could cause the change in the Spectrum emus? I've been hunting about but don't know where this type of setting would be amended.

smartgenes

@smartgenes Actually the Valerino scriptmodules messages still appeared when I was in a music app. I went to home/pi/retropie-setup/ext and deleted the Valerino folder, hopefully that takes care of that.

Folly

@smartgenes

The questions you are asking are a bit off topic.
For you I think it better to re-start creating your own image.
I suggest you start with a fresh Buster with Desktop and install RetroPie-Setup on top of it.
Would be good to open a whole new thread regarding using RetroPie on a distribution with Desktop environment.

Btw.
I will go on vacation tomorrow so I will probably not reply for 2 or 3 weeks.

Lord Vek

@Folly said in Acorn BBC Micro Emulator (current?):

So add add-ext-repos.sh it with these commands :

cd
mkdir -p RetroPie-Setup/ext/RetroPie-Share/scriptmodules/supplementary
cd RetroPie-Setup/ext/RetroPie-Share/scriptmodules/supplementary
wget https://raw.githubusercontent.com/FollyMaddy/RetroPie-Share/main/00-scriptmodules-00/supplementary/add-ext-repos.sh
cd
Then start Retropie-Setup and goto config/tools and find add-ext-repos.
Select the repo you want and it will download the files to the RetroPie-Setup/ext/<repository>/ directory.
For adding my scripts choose FollyMaddy/RetroPie-Share .
When you go back, you will go to manage packages and select experimental packages.
Here you will find the b-em packages that you can install.

@Folly
Hello,

I found this answer you gave to Retro-Arcade-Fan. I did all the above, but I don't see B-Em (or anything new for that matter) inside the experimental packages. Please help.
I have a Raspberry Pi 400 running version 4.8.4 of setup script.

Folly

@Lord-Vek

Do you have this folder now ? :
/home/pi/RetroPie-Setup/ext/RetroPie-Share/scriptmodules

Check if you can find, for example, these files :

/home/pi/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/emulators/b-em-allegro4.sh
/home/pi/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/emulators/b-em-pico-pi.sh
/home/pi/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/supplementary/add-mamedev-systems.sh
/home/pi/RetroPie-Setup/ext/RetroPie-Share/scriptmodules/supplementary/mamedev.sh

Check if above files have contain something.

Lord Vek

@Folly
Thanks for the answer.
The folder \home\pi\RetroPie-Setup\ext\RetroPie-Share\scriptmodules\emulators,contains only one path file.
The folder \home\pi\RetroPie-Setup\ext\RetroPie-Share\scriptmodules\supplementary, doesn't contain the files you mention above.

Folly

@Lord-Vek

Try to select my repository again from add-ext-repos in configs/tools and see if it will download the scripts (make sure you have a good connection).
Then check the folders again for files.
If this doesn't work then you can just download my repository and copy and paste the the ones you want in the appropriate directories.
You can see how it's done over here with this module-script :
https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-lr-mame-and-mame-standalone

Lord Vek

@Folly

I manually copied the files for which you asked me in your previous answer. Now, I can see the two instances of b-em: b-em_allegro and b-em-pico-pi. The question now is, which one should I install? What are their differences?

Folly

@Lord-Vek said in Acorn BBC Micro Emulator (current?):

@Folly

I manually copied the files for which you asked me in your previous answer. Now, I can see the two instances of b-em: b-em_allegro and b-em-pico-pi. The question now is, which one should I install? What are their differences?

I must say it's already a long time ago since I made these module-scripts and I am not really sure on which linux version they still work.
I did not implement flags for linux distributions that don't work.
So it can be that bullseye/debian 11 doesn't work.
I think however Buster/debain 10 should work.

As far as I can look up and can remember the info is as follows :

b-em-pico-pi is based on the b-em fork of kilograham :
https://github.com/kilograham/b-em
A b-em version adjusted to work on the rpi-pico.
In the readme you can read that the version can also work on a regular rpi or pc.
So my module-script is created for installing it like that.
The advantage is that this version works with the correct speed whereas the latest b-em, from that time, had issues running with the correct speed. It also has a different menu than the normal b-em.
It's basically a rpi-pico build running it on a normal rpi.
A loader script is also added which uses matchbox to get fullscreen and quit option and xdotool for autoloading software (disk only).

The other b-em-allegro one is a normal version but we picked it out of the b-em repository on very old commit which worked the best on the rpi.
Basically this means that it also works with the correct speed.
The advantage or disadvantage is (how you look at it) it has a normal menu like the normal b-em version.
A loader script is also added which uses matchbox to get fullscreen and quit and xdotool for autoloading software (tape or disk(.uef or .ssd)).

As far as I can remember :
The pico-pi version runs demos and games with advanced graphics pretty good, not really sure if the the allegro version does the same. However the allegro version can run tapes and more disk formats.

The basic difficulty is that when source code gets older it sometimes will not compile anymore when gcc upgrades to a newer version.
Tried to implement some fixes in the past but not sure anymore if this is still enough.
So we have to try.
I must say my knowledge, for adapting the source code, will probably not be enough to fix future problems if they occur.

If you are looking for the most robust way up till now then you can have a look at mame/lr-mess using my mamedev.sh or add-mamedev-systems.sh scripts. Mame/lr-mess will work but demos and games with advanced graphics will not correctly work and mame/lr-mess has steep a learning curve.
Sadly developing speed of mame/lr-mame/lr-mess has also it's disadvantages.
Compiling on rpi and on older linux distributions becomes more troublesome :

Also installing it from source on an rpi is not recommended as it takes too much time or will fail.
The proper way is to install it from a binary and accept the binary version that is the best way for now.

Btw.
You should read this topic also :
https://retropie.org.uk/forum/topic/29402/bbc-micro-acorn-electron-emu

Lord Vek

@Folly Thanks for the answers Folly. I will try them both then tomorrow. I will also read the topic you suggested.

Folly

@Lord-Vek

I checked if I they where installed on my rpi4 with RaspberryPiOS(Debian11/Bullseye 32 bit)* and they were installed and both are working.
So basically it should work on both Buster 32 bit and Bulleye 32 bit on a RPI.

*my /boot/config.txt contains :
arm_64bit=0
To force the kernel in 32 mode.
More info in this topic :
https://retropie.org.uk/forum/topic/34301/cross-compile-packages-for-rpi1/17
(not doing so can get you into trouble on Bullseye)

ps. if you peek into kilograhams fork you will find demo disc in the scr/pico folder.
Tested twiser and bs-party and they both work on both emulators but xmaster from b-em-pico-pi does the best job. The allegro version has some difficulty with the sound.

Lord Vek

@Folly Hello,

This is what I did. I installed b-em-pico-pi. It works fullscreen OK, but it doesn't recognize half the keyboard. It loads .ssd files without problem.
Then I installed b-em_allegro. This is works OK, loads .ssd files also, recognizes keyboard, but it is not running in fullscreen. I couldn't find any shortcuts to enter the menu (does it have a menu?), or make it run in fullscreen. I only discovered that with Ctrl + C it exits the emulator.
From what I could tell, both emulators seem to run at the correct speed. I run Chuckie Egg, Repton and Elite.
Any further help would be appreciated. Thanks for your support.

Lord Vek

@Folly
I discovered also that with Alt + Enter, b-em_allegro goes fullscreen but you have to switch it back in order to exit with Ctrl + C.