Fairchild Channel F

edmaul69

@Pyjamarama just add the advmess file. the files that advmame uses in bin works with advmess.

Pyjamarama

@edmaul69 Will they affect the AdvMame 1.4 emuator? I run all my MAME vector game throught it. Thank you

edmaul69

@Pyjamarama as long as you dont overwrite any of the files already on there then no. Overwriting them im not sure.

TPR

@OneSwitch as long as you copied the folders
/opt/retropie/configs/channelf/
/opt/retropie/configs/mame-advmame/ &
/opt/retropie/emulators/advmame/
And gave full permissions to all files and folders in
/opt/retropie/configs/mame-advmame/image/
/opt/retropie/configs/mame-advmame/roms/ &
/opt/retropie/emulators/advmame/
It will work.

So this does not seem to work anymore with the most recent version of RetroPie (I'm using 4.1) It did get me very CLOSE but it took some tweaking. For the longest time I couldn't get it to work like others had stated. Everything was in the correct folders, es_config was properly edited, all files had correct permissions.

There was an update to retropie setup that when it did the update, it mentioned changes to advmame. At that point I could get the system to work, but I couldn't get specific roms to work (the system comes pre-loaded with a couple of games.)

I replaced the newer version of advmess with the older version in this folder: /opt/retropie/emulators/advmame/bin and all of a sudden it worked.

Unfortunately, I did not document everything I did, but it would seem that RetroPie needed to make some sort of an update, but the new executable of advmess wasn't compatible with Channel F, but the old version was.

End of the day, those instructions didn't work with 4.1 but it got me to the point of being close enough to where a few tweaks made it work.

edmaul69

@TPR the advmame shouldnt affect advmess. Advmess isnt even available through the retropie setup. I have updated to 4.1.18 and all is working fine for me. Not sure what happened in your case. Are you by chance tpr from atariage?

herb_fargus

@edmaul69 AdvMESS is now part of advmame 3.0 as far as I understand it.

edmaul69

@herb_fargus alrighty. So @tpr @herb_fargus in my case it did not delete the old advmess or the emulators.cfg files for each seperate system using advmess. Absolutely no system works with the new advmame 3.1 advmess

edmaul69

@herb_fargus @tpr so i figured out the issue. the emulators.cfg file for each individual system needs the correct config. so astrocade would need this:

advmame-3.1 = "/opt/retropie/emulators/advmame/3.1/bin/advmess astrocde -cart %BASENAME%"

and the channel f emulators.cfg would need this:

advmame-3.1 = "/opt/retropie/emulators/advmame/3.1/bin/advmess channelf -cart %BASENAME%"

you would have to have these for each specific system that advmess plays as they do not work without specifying the correct system that matches the roms. also the -cart needs to be set in it as i have done. Then you need to change the default emulator to advmame-3.1

herb_fargus

@edmaul69 mess is... A mess :p we may eventually get to including the configs in a module. Down the road...

It's the longest standing issue on the issue tracker.

https://github.com/RetroPie/RetroPie-Setup/issues/210

edmaul69

@herb_fargus i would like to see it set up at least for astrocade and channel f as those are systems that only work in advmess at the moment. I would like to know which all systems advmess 3.1 actually supports as i cant find any info on it. I assume it is nowhere as many as standard mame/mess

herb_fargus

@edmaul69 I'd imagine it's actually pretty close to parity with mame/mess

This is the list I found of some stuff.

http://www.progettoemma.net/mess/sysset.php

Don't know til you try I guess

edmaul69

@herb_fargus i have had a 50% fail rate so far. Using the correct mess rom files and images i have gotten atari 7800, channel f, and astrocade working, but i have failed trying to get all apple ii systems to work. A couple others as well but i dont remember which ones.

TPR

@edmaul69 I am TPR from AtariAge. Like I said, I did get it all working again, but with some trial and error (kicking myself for not writing it all down!) All I know is that the old setup didn't work with the newer version of RetroPie until I updated the Retropie setup scripts. Then the "system" would work, but not the ROMs. So I copied over the old version of Advmess into the directory and it worked.

mediamogul

@edmaul69

I got Channel F working last night as well and was surprised to find that there's a theme for it in Carbon. Very keen!

edmaul69

@TPR so if you want it to work with the new one just edit your emulators.cfg in the channel f config folder and add the info i posted. Doing that you can switch back and forth between them since both will be in the config file.

mediamogul

@edmaul69

You might want to consider changing advmame-3.1 to advmame in your instructions above, as the latest version from the setup script is already up to advmame 3.3. Also, I couldn't get %BASENAME% to work, so i switched to %ROM% and it booted right up.

edmaul69

@mediamogul strange. BASENAME works for me and it is what all the advmame configs use as well. Now the issue with advance mame being at 3.3 it means everytime you update advance mame and it changes number, you have to manually change what folder advmess is in in the config file. So if i point to /3.1/bin/advmess you are saying i will have to change the config to look in /3.3/bin/advmess if i update advmame? Ugh. At least my original advmess wont change so i will just stick to that for the 2 systems i use it for at the moment.

mediamogul

@edmaul69 said in Fairchild Channel F:

So if i point to /3.1/bin/advmess you are saying i will have to change the config to look in /3.3/bin/advmess if i update advmame? Ugh.

The path must have been altered to something more neutral. I have /opt/retropie/emulators/advmame/bin/advmess.

edmaul69

@mediamogul that is where i had my original one before the update added 3.1. But i have 3.1 as well. Is there any way to check what version is running?

mediamogul

@edmaul69

/opt/retropie/emulators/advmame/bin/advmess -version

Edit: of course your path is currently different.