Telnet or SSH client?

Addison

I already have TinyFugue and some other goodies in the Ports folder.

Think your explanation is simple enough to follow.

Going to give this a try within the hour.

Thanks! :D

ts-x

FYI, there’s a MSDOS version that runs in DOSBox as well. Have it up and running on my Pi3 and can provide you with the start script and configs tomorrow if you’d like. It’s a really cool game!

Addison

@ts-x

I'd much prefer a cleaner looking font if I'm playing this on a big TV.

Thanks for the offer though. :)

Addison

@sleve_mcdichael

I tried launching in Emulation Station from the Ports folder.

Black screen for about 4 seconds then it returned back to menu.

What have I done so wrong? :P

alt text

Addison

You can click on those previous images to make them bigger by the way.

BennyProfane

@Addison I think you just missed the part where you get the ADOM archive from the website and unzip it in the ports folder. Also kudos for trying the ‘long’ version but if you are still stuck let’s go with the easier/first version the person earlier provided.

For what it’s worth I don’t even use it as a port - I have the desktop installed (which you can install through one of the menus if you got the stock image), boot into that and run from there (mainly because as a purist I like to track stuff on a notepad as I am running up/down dungeons). But the port is definitely a good touch.

Edit: so just to clarify there should be an extra ‘adom’ folder in the ports directory, alongside all the sh files (not just the adom.sh file)

Addison

@BennyProfane

Okay.

I used your initial link and downloaded the only one that had a fruit picture "Linux (Raspbian) ARM" to my Desktop Windows 11.

I then unzipped it using Winrar and it created an adom folder for me.

Transferred that folder to /opt/retropie/configs/ports/ with your suggestion using WinSCP.

Thought I followed your steps completely, but I must have went wrong somewhere.

I'm sure the problem is me and not you. :P

BennyProfane

@Addison you’re super close - think it went to the wrong ports folder using WinSCP - see how your first screenshot uses the /home/pi path -> needs to be there

sleve_mcdichael

@BennyProfane is exactly right, I can see from your screenshot @Addison that the adom executable (and the docs and licenses folders that come with it), are in the config folder at:

/opt/retropie/configs/ports/adom

...when it should be in the rom folder instead, at:

/home/pi/RetroPie/roms/ports/adom

You can either move the executable to the roms folder (and optionally the docs and licenses too, if you want, but leave emulators.cfg where it is) or, alter the emulators.cfg file to use the executable at its existing location: pushd /opt/retropie/configs/ports/adom; instead of starting with pushd ~/RetroPie... or pushd /home/pi....

It just comes down to where you want the game file to live, either in the "roms" area or "configs" area of your system -- but it's all your choice, the system itself doesn't really care either way, as long as it knows where to find it.

Addison

Moved the adom folder to what should be the correct place now.

/home/pi/RetroPie/roms/ports/adom
alt text

/opt/retropie/configs/ports/adom
alt text

Black screen again for 5 seconds then brings me back to the menu in Emulation Station.

Do I need to give something an executable permission?

mitu

@Addison said in Telnet or SSH client?:

Do I need to give something an executable permission?

Yes, of course - the main program (adom) needs to be executable. Is your roms folder on an external drive ?

Addison

@mitu

It's a 256 MB micro SD card.

Addison

So do this?

alt text

Addison

Don't think that worked.

Black screen now for about 10 minutes. :/

mitu

If you manually run the adom executable (exiting EmulationStation), does it work ?
Run the same commands as you have configured in the emulators.cfg entry for adom and see if it works.

Addison

@mitu

I feel like such a burden here at times.

Wish Linux would upgrade to Windows so I could just point and click on stuff to make things easy.

Obviously, I have no idea what I'm doing. :/

pi@retropie:~ $ cd /home/pi/RetroPie/roms/ports
pi@retropie:~/RetroPie/roms/ports $ ADOM - Ancient Domains Of Mystery.sh
-bash: ADOM: command not found
pi@retropie:~/RetroPie/roms/ports $ sudu ADOM - Ancient Domains Of Mystery.sh
-bash: sudu: command not found
pi@retropie:~/RetroPie/roms/ports $ cd adom
pi@retropie:~/RetroPie/roms/ports/adom $ adom
-bash: adom: command not found
pi@retropie:~/RetroPie/roms/ports/adom $ sudo adom
sudo: adom: command not found
pi@retropie:~/RetroPie/roms/ports/adom $ adom="pushd ~/RetroPie/roms/ports/adom; ./adom; popd"
pi@retropie:~/RetroPie/roms/ports/adom $ default="adom"

mitu

The commands are:

pushd ~/RetroPie/roms/ports/adom
./adom
popd

sleve_mcdichael

@mitu @Addison I've just had opportunity to test my own suggestions and it appears the command does work when ran from terminal, but not when from runcommand -- I too just get black screen that way. I suppose it's probably something to do with how runcommand handles video modes or something?

Additionally, it does not need to be ran from within the data dir, so we don't need to navigate there and back with pushd/popd; the emulators.cfg line can be shortened if desired to

adom="/home/pi/RetroPie/roms/ports/adom/adom"

...however that is secondary to the main issue that nothing is displayed on the screen.

Edit: runcommand.log looks like:

Parameters: 
Executing: /home/pi/temp/foo/adom/adom

Ancient Domains Of Mystery -- Version 3.3.3 
(C) Copyright 1994-2019 Thomas Biskup. 
All Rights Reserved. 

ESC)0ESC[1;24rESC[m^OESC[4lESC[?7hESC[HESC[JESC[1;9HESC[HESC[JESC[?25hESC[?0cESC[24;1H^M/* 
 * ADOM session aborted due to an external problem. 
 * Problem Description: ADOM requires at least a 25x80 screen to run on. 
 */ 


[Press ENTER to continue]

Edit edit: the "easy way" from my earlier post, bypassing runcommand and running the executable directly from the launch script, does work from EmulationStation.

sleve_mcdichael

A-ha! The error's happening here, specifically:

eval $COMMAND </dev/tty &>>"$LOG"

&> redirects both stdout and stderr; it is much the same as doing >>"$LOG" 2>&1. It's this redirection of stdout that's breaking it.

Running manually:

./adom 2>>log.file

...worked fine, but changing that to:

./adom &>>log.file

...had the error (black screen, log.file says needs 80x25 screen to run on.

So we cannot redirect the stdout (because that's how the game is shown at all.) And it turns out, runcommand already has a trick to handle this! Just preface the emulator command with CON: to set the CONSOLE_OUT parameter, which tells it to only redirect stderr and not stdout.

@Addison I think this should work, then, if you leave everything else the same and just change your emulators.cfg to:

adom="CON:/home/pi/RetroPie/roms/ports/adom/adom"
default="adom"

Addison

@sleve_mcdichael said in Telnet or SSH client?:

adom="CON:/home/pi/RetroPie/roms/ports/adom/adom"
default="adom"

It works!

Such joy!

This is so cool to finally have the game available on the Pi. :)

But hey, the resolution is about 3/7ths of the entire screen display (1920x1080 TV).

Any command that can be added to the config file for full screen resolution?