Is the Psion Series 3[x] supported?
-
@Folly Cheers, will try this later today.
-
@Folly said in
supported?:I tried with my script and I have an issue.
I cannot install the driver.Will have a look.
Edit :
Added media to the mediafilter so psions can be installed :
https://github.com/FollyMaddy/RetroPie-Share/commit/54c77fb977677a9738581d5656ba2ec71114b5f2Could not test the driver yet as I can't get the files at the moment.
I think I'm missing something about this. I updated your script and all the Series 3 machines appeared in the list. So I told it to install them and I didn't get any errors, but none of them have shown up - there's no entry in either version of ES_SYSTEMS.CFG and it hasn't created rom or config folders for them. Do I need to do something specific with the media filter?
-
You need to install my latest script !
265.14Changes for psion3/3a have been added in 265.13
See my commit link in your reply !You will be able to change the database version to an older version if needed.
-
@Folly How do I install the new one? I thought updating it would have been enough but I did notice the bit that said "This won't be updated any more."
-
You are using my deprecated script add-systems-mamedev.sh.
You need to delete that version and copy the newer mamedev.sh to it.
mamedev.sh works differently it doesn't generate module-scripts anymore it directly installs the systems without making module-scripts.
It also works much faster and has much more utils and fixes.Go to my first post and read : https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-lr-mame-and-mame-standalone
After that you can just update the script from within the script.
-
@Folly Ah yes, found that and installed it, but it's still complaining about the mediafilter. (I get the same message for all the Series 3 systems.)
-
-
@Folly Nope, they're all the same including the US one. Unknown system, mediafilter problem.
-
@JimmyFromTheBay Could this be anything to do with not having MAME/MESS 0265 installed?
-
Yes , that is the reason.
You need to have a mame binary where these drivers are in.
My script tries to get the media info from mame.
But if the driver doesn't exists in mame you get the errorunknown system.
The minimum version you need to have is 263, I think. -
@Folly Ah, so I'm back to the old problem of not being able to install the new MAME/MESS because it'll destroy all the old systems I installed with the previous script. Bah. Oh well, thanks for the help anyway. I'll add it to the list of "stuff to do when I get the Pi 5".
-
@Folly (I do have 0264 installed in a separate directory, is there any way I can tell the script to use that?)
-
You're welcome !
-
@JimmyFromTheBay said in
supported?:@JimmyFromTheBay (I do have 0264 installed in a separate directory, is there any way I can tell the script to use that?)
Yes, that should be possible.
Will have a look. -
@Folly If I changed the line in mamedev.sh from
local _mess_core=$rootdir/libretrocores/lr-mess/mamemess_libretro.so
to local _mess_core=$rootdir/home/pi/Downloads/lr-mess264/mamemess_libretro.so
would that solve it?
(And presumably all the other references to $rootdir/libretrocores/lr-mess/mamemess_libretro.so)
-
@JimmyFromTheBay said in
supported?:@Folly If I changed the line in mamedev.sh from
local _mess_core=$rootdir/libretrocores/lr-mess/mamemess_libretro.so
to local _mess_core=$rootdir/home/pi/Downloads/lr-mess264/mamemess_libretro.so
would that solve it?
(And presumably all the other references to $rootdir/libretrocores/lr-mess/mamemess_libretro.so)
No, it doesn't work that way.
My script uses standalone mame to get information.
That is the one you need to update. -
@Folly said in
supported?:$rootdir/libretrocores/lr-mess/mamemess_libretro.so
So I need to download the 0264 MAME files from your site, put them in the Downloads folder and then change every reference to $rootdir/libretrocores/lr-mame/mamemess_libretro.so to $rootdir/home/pi/Downloads/mame264/mamemess_libretro.so?
(Sorry, I'm very far out of my depth here :D)
-
If you could rename your /opt/retropie/emulators/mame folder by renaming it as root user.
Then you will have a backup.Then you are able to install a newer mame from my script using the lines to get binaries from my gdrive.
-
@JimmyFromTheBay said in
supported?:@Folly said in
supported?:$rootdir/libretrocores/lr-mess/mamemess_libretro.so
So I need to download the 0264 MAME files from your site, put them in the Downloads folder and then change every reference to $rootdir/libretrocores/lr-mame/mamemess_libretro.so to $rootdir/home/pi/Downloads/mame264/mamemess_libretro.so?
(Sorry, I'm very far out of my depth here :D)
No, every folder you mention is linked to libretro cores.
Standalone mame is in /opt/retropie/emulators/mame.In my script I use both ( means the same ):
/opt/retropie/emulators/mame/mame
$emudir/mame/mameI should make that a bit uniform.
But if you want you should edit these.
Though I think that isn't the route you should take.Edit :
I would take the risk.
First I would backup the old RetroPie scripts by renaming them and just clone RetroPie to the newest version like described over here :
https://github.com/RetroPie/RetroPie-Setup
Then I would update standalone mame to 264 from binary. -
@Folly Thanks, but I barely even understand what you just said, and it's a VERY big risk. I have a Pi 5 on order now, I'll do all that stuff on it when it arrives and just leave the 4 intact and safe.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.