Development of module-script generator for lr-mess, lr-mame and mame standalone

Folly

remove our script
add-mamedev-systems-2v4.sh

and try to run the setup again without it.
You should use this :

sudo ./retropie_setup.sh

Could you check the permission of the files again for me ? :
I have :

pi@raspberrypi:~/RetroPie-Setup $ ls -l
total 76
-rw-r--r-- 1 pi pi   146 Oct 28 21:16 AUTHORS
-rw-r--r-- 1 pi pi   417 Oct 28 21:16 CONTRIBUTING.md
-rw-r--r-- 1 pi pi   635 Oct 28 21:16 COPYRIGHT.md
-rw-r--r-- 1 pi pi 32265 Oct 28 21:16 LICENSE.md
-rw-r--r-- 1 pi pi  2033 Oct 28 21:16 README.md
drwxr-xr-x 2 pi pi  4096 Oct 28 21:16 ext
drwxr-xr-x 2 pi pi  4096 Oct 28 21:53 logs
-rw-r--r-- 1 pi pi  6374 Oct 28 21:16 platforms.cfg
-rwxr-xr-x 1 pi pi  2314 Oct 28 21:16 retropie_packages.sh
-rwxr-xr-x 1 pi pi   520 Oct 28 21:16 retropie_setup.sh
drwxr-xr-x 7 pi pi  4096 Oct 28 21:16 scriptmodules

Folly

@dteam

Do you have these permissions for the file ? :

ls -l
-rw-r--r-- 1 pi pi   520 Oct 28 21:16 retropie_setup.sh

Then it's not executable, and you will get :

pi@raspberrypi:~/RetroPie-Setup $ sudo ./retropie_setup.sh 
sudo: ./retropie_setup.sh: command not found

DTEAM

@folly
The problems seems to be your script. I removed it and now it's fine.

Folly

@dteam

That sounds bad.
I don't have any problems over here.
I will pull it from github to see if I get any problems.

I assume it was the latest.

edit:
I installed everything fresh on my x86 laptop too.
I found some compatibility problems for the sorted lists, so I will look at that.
But no problems in crashing or recognising whatsoever.

Did you try to edit the script and perhaps made a mistake in doing so ?
Can you open the script into a text editor to check if it's a good file ?

Folly

@dteam

I don't expect it, but be sure you don't saving it as a html file :
(right-click on raw and download should download the correct file)

https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-and-mame-standalone/789

Folly

@dteam

Any luck yet ;-)

DTEAM

@folly

No, I followed the instruction from Post #1 and put add-mamedev-systems-2v4.sh

here
/home/pi/RetroPie-Setup/scriptmodules/supplementary

I did that a lot of times. I don't understand why it doesn't work now.

I'm gonna re-downloaded your file

Folly

@dteam

Yes indeed you did that a lot of times, so I was confident you had a correct file.

Not really sure either what the problem is but I am quite confident that the script should work.

Is your sd card still ok ?
No problems at boot ?
Do the older scripts that you tested earlier still work ?

How old is your retropie-image, is it based upon buster ?
Perhaps an idea to update.

Btw. I read that 0237 is out now.

DTEAM

@folly
It works !! I solved the problem . I don't know why, but i had problems to transfer my file. Now It's fine. The problem was on my side. It's not a general issue

Folly

@dteam

Aha you found the problem, great to hear it's working again.

jamrom2

@folly Hiya. Doing good here with the script. I've got all my handhelds working great and moved into the TRS-80 CoCo.

Ran into a question there.. I don't see a CoCo disk/flop1 option to add in to my list.

How do I use .dsk images with this system. I'd rahter not have both the TRS-80 and the Coco, just one works for me as I already have the Dragon32 running.

Thanks!

Folly

@jamrom2

The system coco has FDC support (floppy drive controller) as an external slot, reading from the mame output.

So by default it will not support a floppy drive controller out of the box and so my script will not detect support for floppy-drive media.
No detection means that no module-script for that media is created and installed.

To be able to do that a manual line should be created to be able to add FDC support.

Looking at the mame output for coco2 or coco3, they will have FDC support OOB.

Don't know for sure, but perhaps the easiest way is to install one of these :

Driver coco2 (Color Computer 2): *computer*non-arcade
Driver coco2b (Color Computer 2B): *computer*non-arcade
Driver coco2bh (Color Computer 2B (HD6309)): *computer*non-arcade
Driver coco2h (Color Computer 2 (HD6309)): *computer*non-arcade
Driver coco3 (Color Computer 3 (NTSC)): *computer*non-arcade
Driver coco3dw1 (Color Computer 3 (NTSC; HDB-DOS)): *computer*non-arcade
Driver coco3h (Color Computer 3 (NTSC; HD6309)): *computer*non-arcade
Driver coco3p (Color Computer 3 (PAL)): *computer*non-arcade
Driver cocoe (Color Computer (Extended BASIC 1.0)): *computer*non-arcade
Driver cocoeh (Color Computer (Extended BASIC 1.0; HD6309)): *computer*non-arcade

jamrom2

@folly I put those into \BIOS\mame as well as \roms\coco

what do I pick as far as an eumlator? the lr-mame-basename, lr-mess-cmd? or any other?

jamrom2

on top of this, a few games appear to be corrupt roms and do not work properly under MESS.

a lot of artifacting and lines all over stuff. Worse is Dungeons of Daggoorath, the only reason really for me to even have the TRS-80.

I was hoping to get Flight Simulator II working as well... but that's a .dsk image.

Controls for left, right, up and down not working either. Mapping is there, but doesn't look like the system is recognizing it.

Folly

@jamrom2 said in Development of module-script generator for lr-mess and mame standalone:

@folly I put those into \BIOS\mame as well as \roms\coco

what do I pick as far as an eumlator? the lr-mame-basename, lr-mess-cmd? or any other?

Explain better.

It seems you did not understand my post.
Adding the files to the directories doesn't do anything if you don't install, for example coco2, first.

If you do that a line with floppy will appear for booting a disk.
I suggest you use that.

The basename and cmd lines are only used if you want to :

make use of handmade .cmd files
if you want to run system-game bios files directly (as with classich)
if you want to run the software so mame or lr-mess will check the database, if in database, and try to boot it depending on that.
(we discovered that there are still issues using this and some combinations need fixing, but this is a difficult process, so still many combinations will not work)

jamrom2

@folly

Ok. how do I add coco2? Where does that come from?

Folly

@jamrom2

Select coco2 or coco3 in my script and it will be installed.
Select All systems > submenu.

etc. :

Rom directories become coco2 and/or coco3.
and make sure you have the bios files too.

jamrom2

@folly

well.. that's why... I don't have that list.

I must be behind a version in the script. Is that from a new version you created?

nevermind... I see you did. Let me update and see what I get.

Folly

@jamrom2

It should be in there.
All older versions have it.

If you want the latest.
Check here :
https://github.com/FollyMaddy/RetroPie-Share/blob/432d2c9db4b1497ba2da938cef1968621c5c2570/00-workdir-00/add-mamedev-systems-2v4.sh

Right-click RAW and save it where it has to be in :
/home/pi/RetroPie-Setup/scriptmodules/supplementary

Remove the old versions.

jamrom2

@folly I didn't realize it was "buried" in the massive list of systems.

That is some list, wow.

At any rate, I have it running and looked up some load commands to get it working. Works great.

This brings the question about systems. The idea of using Retropie is to sort of isolate or condense several systems under one umbrella. These old Computer systems kinds present their issues with the amount of variances to them, some with little change. Like the Apple, we saw it was best to go Apple IIe and Apple IIgs.

What about a Tandy package that covers the Coco, Coco2 and Coco 3 plus the TRS-80 16? Otherwise Emulationstation is going to require a lot more themes for each system and each of the variants.

Right now, I have Tandy Coco for carts and cass, Coco 3 for Disk and TRS-80 16 for really old stuff. I think this is overkill.

What are your thoughts on this?