@sleve_mcdichael I'm not selling anything, it's your decision to use it or not. I'm not benefited in any way.
I'm just talking about my personal experience with it. And that, once everything is set up, it stops being a problem.
For what it's worth, I was able to fix the issue. Pretty basic fix: uninstalled the lr-rpboom package from the retroarch config menu, restarted the system and then reinstalled it. Poof! Everything works fine now. Not sure how or why, but I'll take it. B-)
@mitu All right, I'll try it and update. Thank you for your patience.
Edit : Looks like it works. Four reloads without a crash. Thank you so much!
Incidentally, I've found this on the github wiki :
'NAM however will run and continue to run everytime you start it up but it changes the eduke32.cfg file located in .etc/eduke32 on its own and breaks duke3d and all expansion packs till you manually modify eduke32.cfg selectedgrp field back to duke3d.grp. I've tried multiple times and nam breaks duke 3d and any expansion packs every single time. To avoid this change the permissions on the eduke3d.cfg file so no one can change it. And then you can run duke 3d the expansion packs and nam without anything breaking or having to modify anything after running nam.'
It's not only RetroPie that changed over the years, but also prboom. There's now a core option for the FPS (I think the original Doom ran at 30 or 35FPS), check if yours is set to 60 FPS.
Also, when opening a help topic, please add more info about your system and setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.
@BuZz , well I did not succeed installing lr-prboom or zdoom using the retropie-setup. Debugging was a bit hard, because I could not see the error message: after failure the retropie-setup reappears. So I suppose the error in the retropie-setup was the same as in my first command line attempt.
Are there any known issues regarding the install of these ports via retropie-setup anyway?