[DOSBox] official thread

mitu

@jamrom2 Do you have enough free space on your sdcard to install new packages ?
Run the installation again, then look in $HOME/RetroPie-Setup/logs and open the latest log, which should have the installation log with any errors.

jamrom2

@mitu

found it in there...

meson.build:1:0: ERROR: Meson version is 0.52.1 but project requires >= 0.54.2

I don't get this. I just did an OS update. Not sure why it says I'm at 52.1. I type in "meson -v" in my putty session and I get 0.56.1

mitu

@jamrom2 What are you installation details ? Is this a PI3/4 ? Which RetroPie version ? If you don't get a binary install, then your OS is too old.

jamrom2

@mitu
Pi3b+
4.7.11 Retropie-Setup Script

I did the OS rebuild via this from nemo93
Retropie menu > Configuration / tools (C) > raspbiantools (215) > Upgrade all packages (1)
or
from the terminal type the following: sudo apt update && sudo apt full -upgrade -y

Then I did a core package update via the Retropie menu because after doing the above, I was getting the volume mixer int error message which is now cleared.

mitu

@jamrom2 said in [DOSbox] official thread:

from the terminal type the following: sudo apt update && sudo apt full -upgrade -y

This will not upgrade your OS, if you're on Raspbian Stretch or older, you won't get upgraded to Buster.

jamrom2

@mitu I'm definitely on buster... at least that's what it shows on the RetroPie-Setup Script header.

mitu

@jamrom2 said in [DOSbox] official thread:

@mitu I'm definitely on buster... at least that's what it shows on the RetroPie-Setup Script header.

In this case you should have the binary install option - doesn't that work ?

jamrom2

@mitu I have the binary option but when I try to load it, it gives me that error at the end. Claims I don't have the correct version of meson, which makes no sense.

I also tried the source version, but it crashed as well.

Strange because I had already loaded the source version a while back without issue.

mitu

@jamrom2 said in [DOSbox] official thread:

I have the binary option but when I try to load it, it gives me that error at the end.

Please post the binary install log (from $HOME/RetroPie-Setup/logs) on pastebin.com.

jamrom2

@mitu said in [DOSbox] official thread:

@jamrom2 said in [DOSbox] official thread:

I have the binary option but when I try to load it, it gives me that error at the end.

Please post the binary install log (from $HOME/RetroPie-Setup/logs) on pastebin.com.

all set

https://pastebin.com/DvRGiKgC

mitu

@jamrom2 said in [DOSbox] official thread:

all set
https://pastebin.com/DvRGiKgC

Not quite, this is not a binary installation, it's a source installation.

For some reason though, your version of meson is not the one from the RPI repos - did you remove the RPI repos from your apt sources list ? Otherwise, apt update && apt full-upgrade should install version 0.56.1.

jamrom2

@mitu said in [DOSbox] official thread:

@jamrom2 said in [DOSbox] official thread:

all set
https://pastebin.com/DvRGiKgC

Not quite, this is not a binary installation, it's a source installation.

For some reason though, your version of meson is not the one from the RPI repos - did you remove the RPI repos from your apt sources list ? Otherwise, apt update && apt full-upgrade should install version 0.56.1.

Sorry... I took from the top of the log list thinking first last, when it's last first.

Here is the correct binary install I just did now.

https://pastebin.com/xf6KgvN6

No, I didn't remove anything manually, but that's not to say something else I've loaded did. I have a few emus that may have twisted my install a little. The Atari800 video script, MESS and Daphne/Singe installs I did I think somehow changed things a little.

I'll try what you posted and see if it works.

jamrom2

@mitu just tried

sudo apt update && apt full-upgrade

it came back with an error:

E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?

I'm logged in as pi what does it mean by root?

mitu

@jamrom2 said in [DOSbox] official thread:

Here is the correct binary install I just did now.
https://pastebin.com/xf6KgvN6

Seems to me you're using an older version of the Dosbox-Staging setup script, that you copied manually ? As @nemo93 mentioned at some point, it's now part of the RetroPie-Setup script, so you should remove the install script you copied manually and update your RetroPie-Setup script to the latest version. Afterwards, you can install the binary without issues.

I'm logged in as pi what does it mean by root?

The correct command is

sudo apt update && sudo apt full-upgrade

jamrom2

@mitu that might have happened while I was helping to test the newer versions of Staging a few months ago.

Where do I find that script to delete? Is it here?

/home/pi/RetroPie-Setup/scriptmodules/emulators

yeah... that extra "sudo" was missing. It's running the RPI repos update now.

also.. is 4.7.11 the latest RetroPie-Setup script version? If not... then I'm definitely having larger issues.

mitu

Where do I find that script to delete? Is it here?
/home/pi/RetroPie-Setup/scriptmodules/emulators

Yes.

also.. is 4.7.11 the latest RetroPie-Setup script version? If not... then I'm definitely having larger issues.

No, that's not the current RetroPie-Setup script version. If you have trouble updating to the current version, you should open a separate topic.

jamrom2

@mitu ok. I will. At this point, I think that's what's happening here. I'm not getting the current setup script.

@nemo93 I'll be back to help once I get this issue sorted. Not sure how this happened, but it seems to be the cause of all the headaches I'm having.

nemo93

@mitu much appreciated the time you spent here to assist @jamrom2. Thank you.
@jamrom2 I did check your other thread and I'm glad you get it sorted. Next time please be sure to rely on an official image :-) This is really the only way for all of us to ensure things will work as intended. I've started (and not finished) an article to guide users to setup a clean and easy-to-maintain DOS environment. Feel free to have a look.

jamrom2

@nemo93 All set. Long story short... when I loaded in the MESS build, I switched repositories from the true RetroPie set to the fork that the MESS build was based on. I never realized this, even though I did do it, I had no idea what it would do to my build. All is as it should be...

DosBox-Staging 77.1 is now loaded from the binary and working ... WOW! Amazingly fast.

For testing I chose:
NASCAR Racing
INDYcar Racing II
Aces Over Europe

All are running smoothly other than what I pointed out in an earlier post with A10 Tank Killer in regards to music slowing down when text boxes are posted.

NASCAR and INDYcar are very smooth and fluid. Considering these are mid-90s games with a lot of 3d polys and textures, that says a lot for Staging running on a Pi3b+.

What else do you need me to test? Can I now run any shaders on Staging? I'd like to try that.

nemo93

@jamrom2 glad you have everything back in a stable state. Regarding your game slowing down, as stated earlier this is likely related to the cycles count. Try setting a fixed cycles count for that game (eg. cycles = 15000 to start with).

For now testing is focused on the ARM64 dynarec. It's a kind of priority for the time being given everything else is stable. There might be updates to the controller-side. Shaders is something being looked at but it's really tricky to implement given the current codebase (details there). This would require quite heavy code change hence not sure when (and if) it will be implemented.

I'd say just enjoy your good old gems and report back should you hit any issue(s).