Quick Roku vs Ubuntu Rygel DLNA Note

(from the Okaaaay department)

Trying to get media streaming working between Ubuntu using the default Rygel DLNA server in Gnome and the Roku Media Player.

For some reason, Roku wants Rygel to transcode all MP4/H.264 videos to MPEG.  Rygel goes "OK - I can do that" then errors out.

Other DLNA clients work fine.

So - as a Hail Mary - in ~/.config/rygel.conf - I disabled transcoding.

# Set it to 'false' if you want to disable transcoding support.

enable-transcoding=false

Now - Roku accepts the videos as MP4 and plays them back great.

Hmm - not quite sure where's the breakdown here.  Why didn't Roku ask for MP4 in the first place, since that's the file encoding?  Why did transcoding break anyway?  

Weird.

Cheers,

Paul

Fix for Tomb Raider (2013) on Arch Linux

(from the Gaming On Modern Linux department)

Hi everyone,

Quick post here - I've been trying to run the original Feral Interactive port of Tomb Raider on Arch Linux.  It starts - then stops immediately.  

Looking at the Arch Gaming troubleshooting guide here: https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting#Tomb_Raider_(2013) they mention trying to see if there are missing libraries.  The output of that command is:

$ ldd steamapps/common/Tomb\ Raider/bin/TombRaider | grep found
       libssl.so.1.0.0 => not found
       libicui18n.so.51 => not found
       libicuuc.so.51 => not found
       libicudata.so.51 => not found
       libCoreFoundation.so.476 => not found
       libvorbis.so.0 => not found
       libSDL2_image-2.0.so.0 => not found
       libcrypto.so.1.0.0 => not found
       libcef.so => not found
       libpdf.so => not found
       libfmodex.so => not found

The weird part?  All of these libraries are already present in .steam/steam/steamapps/common/Tomb Raider/lib/i686

I thought "That's weird". I looked at the debug output in Steam - and yes - it can't find those libs.  I messed around with a few different approaches - adding LD_LIBRARY_PATH to the startup options, etc. - but nothing seemed to work.  

In desperation - and just because I like to be weird - I tried this:  

$ cd ~/.steam/steam/steamapps/common/Tomb\ Raider/lib
$ ls
i686
$ cp i686/* .
$ ls
i686       libCoreFoundation.so.476  libcurl.so.4  libicudata.so.51  libicuuc.so.51  libssl.so.1.0.0  libtcmalloc_minimal.so
libcef.so  libcrypto.so.1.0.0        libfmodex.so  libicui18n.so.51  libpdf.so       libsteam_api.so

And tried starting the game again.  It worked!

That wastes 152M of hard drive space though - so I deleted the files and decided to create a symbolic link to the files instead:

$ cd ~/.steam/steam/steamapps/common/Tomb\ Raider/lib

$ ls

i686

$ ln -s i686/* .

$ ls
i686       libCoreFoundation.so.476  libcurl.so.4  libicudata.so.51  libicuuc.so.51  libssl.so.1.0.0  libtcmalloc_minimal.so
libcef.so  libcrypto.so.1.0.0        libfmodex.so  libicui18n.so.51  libpdf.so       libsteam_api.so

Works just the same - and saves a ton of space!

So - the summary is - it should be loading the game libraries from the i686 subdirectory, but it doesn't seem to be able to find them.  Making them available one level up seems to solve the problem.

Cheers,

Paul

Switching Desktop Environments in Ubuntu 22.04

(from the Don't you have better things to do? department)

Introduction:

Hi everyone,

Much like many tech sector workers, I spend a lot of time on a Linux desktop lately.  I tend to prefer Enterprise or Long Term Support (LTS) editions of Linux - like Ubuntu 22.04 LTS - as opposed to the rolling update Linux versions like Arch.  They tend to be very stable, with most bugs ironed out so I can concentrate on the software being tested and not worry about tracking issues in the distribution. 

Now - I'm always in search of the perfect desktop experience.  I enjoy trying the latest Linux GUIs - Gnome, KDE, Xfce, etc.  Ubuntu allows you to install these simultaneously - switching between them when you login.  It used to work flawlessly - but since the desktops are becoming more customized - extra steps are needed to switch between them. 

This document will contain my notes for switching between Ubuntu Gnome/Gnome, Unity, and Xfce on Ubuntu 22.04 LTS.  I'll leave the installing of these into a stock Ubuntu installation as an exercise for the user. (Hint:  there are great online guides like this one: How to Switch from GNOME to Unity in Ubuntu 18.04 and 17.10).  I'll also assume this is a stock Ubuntu installation with Ubuntu Gnome as the default environment.

Xfce4:

• Switch the Display Manager from GDM to LightDM via the sudo dpkg-reconfigure gdm3 command, and selecting lightdm
• Change LightDM from the Unity greeter to lightdm-gtk greeter by editing /etc/lightdm/lightdm.conf and adding the line greeter-session=lightdm-gtk-greeter, commenting out the line greeter-session=unity-greeter
• If present, you'll have to uninstall gtk3-nocsd - it now interferes with Xfce4 menus, since they're starting to use client side decorations.  In Ubuntu the command is sudo apt remove gtk3-nocsd libgtk3-nocsd0
• If you have Unity installed - you may run into an issue where notifications are using the Unity handler instead of the Xfce handler.  The easiest way to make sure that Xfce notifications are used is to issue the following command, which just renames the Unity notifier and is easily undone: sudo mv /usr/share/dbus-1/services/org.freedesktop.Notifications.service /usr/share/dbus-1/services/org.freedesktop.Notifications.service.disabled
• You can test the default handler by using the notify-send command.  Xfce notifications should be clickable - they close you click on them.
• Once rebooted and logged into Xfce, you'll want to add an additional panel to the top bar - the "Indicator Plugin" - this will make sure Unity style notifications like Skype, Slack, etc. - are displayed in the top bar.  I put it next to the Status Tray Plugin for continuity.
• Don't forget to select Xfce Session from the LightDM login screen!
• UPDATE:  There may be an issue with XFCE panel notifications and something called ayatana-indicator-application.  Uninstalling this via apt made panel notifications work - however it looks like it's installed by default with Xubuntu.  Not sure what's going on - but I'm removing it for now.  See more information here: https://forum.xfce.org/viewtopic.php?id=16436

Unity:

• Switch the Display Manager from GDM to LightDM via the sudo dpkg-reconfigure gdm3 command, and selecting lightdm
• Make sure LightDM is set to the Unity greeter by editing /etc/lightdm/lightdm.conf and insuring that the line greeter-session=unity-greeter is set.
• Make sure gtk3-nocsd is installed via the command sudo apt install gtk3-nocsd
• Install additional yaru icons with the sudo apt install yaru-theme-unity
• If you have Xfce installed - you may run into an issue where notifications are using the Xfce handler instead of the Unity handler.  The easiest way to make sure that Unity notifications are used is to issue the following command, which just renames the Xfce notifier and is easily undone: sudo mv /usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service /usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service.disabled
• You can test the default handler by using the notify-send command.  Unity notifications should not be clickable - they should fade when you hover over them.
• Once rebooted and logged into Unity, you'll want to use Unity Tweak Tool to select the Yaru-dark Theme and Yaru-dark Icon to make it match the latest Unity builds.
• Don't forget to select Unity from the LightDM login screen!
• In addition, current Unity builds are using Nemo instead of Nautilus for default file handling. After locking Nemo to the Unity Launcher, you can switch to Nemo file handling by using the following command: xdg-mime default nemo.desktop inode/directory application/x-gnome-saved-search 
• You can revert back to Nautilus by using the following command: xdg-mime default nautilus.desktop inode/directory application/x-gnome-saved-search
• NOTE:  If you've been experimenting with KDE desktops, for some reason, this kind of trashes the ~/.config/gtk-3.0/settings.ini file.  This shows up as a messed-up right click Unity Desktop menu, among other things.  The quick fix is to edit the ~/.config/gtk-3.0/settings.ini file, and set gtk-menu-images=false.  Logging out and logging back in should now have fixed your right click Unity Desktop menu.
• NOTE:  Electron apps have issues with Ubuntu AppIndicator Tray Icons.  There's a fix here: https://askubuntu.com/questions/1469305/unity-desktop-tray-icons-of-some-apps-not-showing-anymore-ubuntu-22-04
• NOTE:  If Nemo menus no longer move to the top of the Unity desktop - but are stuck to the Nemo window - you may need to reload unity-gtk3-module.  I'm not sure what clobbers this.

Ubuntu Gnome/Gnome:

• Switch the Display Manager from LightDM to GDM via the sudo dpkg-reconfigure gdm3 command, and selecting gdm3
• Remove the additional yaru icons with the command sudo apt remove yaru-theme-unity
• If you switched to Nemo, be sure to switch back to Nautilus:  xdg-mime default nautilus.desktop inode/directory application/x-gnome-saved-search
• Once rebooted, and logged into Ubuntu Gnome or Gnome, you may need to reset your theme from Gnome Tweaks or the Settings control panel. 
• Don't forget to select Ubuntu or GNOME from the GDM login screen!
• I had an issue where GNOME was really slow after switching back - and the GTK windows ignored theme requests.  I fixed it by removing xdg-desktop-portal-gnome.  I don't think this is a good fix - but it got it working again.  Caveat emptor. 
  UPDATE: This was caused by potential bug fix for a Unity 90 second logout issue - as described here: Bug #2063383 “[SRU] Ubuntu Unity takes 90 seconds to log out” : Bugs : gnome-session package : Ubuntu Commenting out the line as indicated breaks xdg-desktop-portal-gnome. 

Cheers,

Paul

Xquartz, XDMCP & Xfce tips (aka restoring my sanity)

 (from the X11 is fun!! department)

Hi everyone,

This is a quick posting.  For various reasons too long to go into here, I've been trying to connect to a Ubuntu 18.04 LTS Linux box via XDMCP from a MacBook Pro using XQuartz (MacOS Catalina) or from a Microsoft Surface Pro using VcXsrv (Windows 10).

The key points for all operating systems - you must set up your Ubuntu Linux box to run XDMCP.  All of these commands need to be done from a terminal window on the Linux box you're connecting to:

• You have to install and select Xfce - it won't work with any of the other modern desktops, since Remote X11 is 2D only.  Try this to install it:

sudo apt-get install xfce4

• You have to use Lightdm - this doesn't seem to work right with GDM.  To install:

sudo apt-get install lightdm

• Make sure it's selected with:

sudo dpkg-reconfigure gdm3

• You have to turn on XDMCP in Lightdm by adding the following to /etc/lightdm/lightdm.conf:

[XDMCPServer]
enabled=true

• You have to install an additional Greeter with Lightdm.  I used lightdm-gtk-greeter which I installed with:

sudo apt install lightdm-gtk-greeter lightdm-gtk-greeter-settings

• Check firewalls, etc.

Okay, most likely, your Windows box will work at this point.  Set up a VcXsrv profile using XDMCP and point it at your Ubuntu Linux box.  The Mac - using XQuartz - needs additional steps:

• You have to manually start the session via command line - replacing the 192.168.0.71 with your Ubuntu XDMCP IP address:

X -query 192.168.0.71 -terminate

• It turns out the Mac doesn't define the "Super" key, so Xfce reacts unpredictably.  For me, it was a broken spacebar.  There was no way to enter a space - the cursor would just blink at you frustratingly. 
• To fix this, in Xfce, go to Applications --> Settings --> iBus Preferences and remove the "<super>Space" mapping from the Next input method field on the General tab.  Since I don't need iBus, I just deleted the mapping entirely.
• Additionally, starting Chrome would prevent any text from being entered.  This turned out to be a old Chrome App I had loaded by default.
• To fix this temporarily, I went into Chrome extensions (chrome://extensions/) and unchecked "Google Play Music".  You don't have to uninstall it - just disable it.

Good luck!!

Cheers,

Paul

Fixed: x2vnc not working with Mac OS X

(from the Wow - this was obscure department)

Hi everyone,

If you're trying to control your Mac OS X screen from your Linux box using x2vnc and the built-in Mac OS Screen Sharing server, and it's not working - or has stopped working - I finally figured out why.

It's because the Mac now adds a small security screen during an unencrypted VNC login.

To get around this, you need to bypass this screen so that VNC goes to the currently logged-in user.

This is done via this command:

sudo defaults write /Library/Preferences/com.apple.RemoteManagement VNCAlwaysStartOnConsole -bool true

Be aware that this bypasses some added security, so use this carefully.  

Cheers,

Paul

Setting up Oracle Java JRE 8 on Ubuntu

(from the Java - But Not Coffee department)

Hi everyone,

(This is a quick post - these instructions are necessarily terse and mainly serve as a reminder to myself. If you do try this - you do so at your own risk - I can't provide any help if you mess anything up.)

I needed to set up Oracle Java JRE 8 on my Ubuntu 12.04 LTS 64-bit system.

For previous versions of Oracle Java, I followed the steps in "6. Installation from RPM package" on the web page here:
http://how-to.linuxcareer.com/oracle-java-jdk-7-on-ubuntu-linux-installation

These instructions worked fine for previous versions of Java but broke with JRE 8.

When I analyzed the failure, I saw it was breaking with the alternatives command.  Ubuntu uses update-alternatives instead of alternatives.

So - I decided to try something bold.  I created a symbolic link to alternatives from update-alternatives:

cd /usr/sbin
sudo ln -s update-alternatives alternatives

Then, I followed the steps in "6. Installation from RPM package".  The package installed properly.  Just for reference, here's the commands I used for the JRE 8u77 I installed today:

sudo alien --scripts jre-8u77-linux-x64.rpm
sudo dpkg -i jre1.8.0-77_1.8.077-1_amd64.deb

That left connecting up the Firefox Java plugin.  There's many ways to do that, but I like using alternatives.. er... I mean update-alternatives:

sudo update-alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so libjavaplugin.so /usr/java/default/lib/amd64/libnpjp2.so 20

Obviously - these are for a 64 bit system.  These won't work as written for a 32 bit system or a mixed 64/32 bit system.

Good luck!

Cheers,
Paul 

Turn your Ubuntu 12.04 LTS into SteamOS (kinda)

(from the This is a cool trick department)

When I first heard about Steam for Linux, I immediately looked at their website and decided to try it.  Here's the specifications from the original page: https://github.com/ValveSoftware/steam-for-linux

Steam for Linux requires the following:

• 1 GHz Pentium 4 or AMD Opteron with 512 megabytes of RAM and 5 gigabytes of hard drive space, or better
• Internet connection (Cable/DSL speeds recommended)
• Ubuntu 12.04 LTS, fully updated
• Latest graphics driver
• NVidia driver support - For recent cards (e.g. series 8), you will need to install 310.x. For older cards, driver 304.x supports the NVidia 6 and 7 GPU series. To access these drivers, first update your cache and then install the specific driver you need from the list in Additional Drivers.
• AMD driver support - For recent cards (e.g. series 5 and above), we recommend installing the 12.11 driver. For older cards, Catalyst 13.1 Legacy supports the HD 2400 Pro card and is the latest for the 2 and 4 GPU series.
• Intel HD 3000/4000 driver support - you will need to use the latest Mesa drivers, Mesa 9 or later. For installation instructions, see here.

So -  I added a new hard disc to my Windows gaming system, and created a stand-alone Ubuntu 12.04 LTS installation.

Then - I heard about SteamOS.  It's built on Debian - like Ubuntu.  I was curious what it was like, but - hey - I'd already fine tuned my Ubuntu system - and I didn't feel like re-inventing the wheel.

That's where it stayed - until tonight.

I saw an article or two about Marc Deslauriers and a project he'd been working on: https://plus.google.com/103632865447092840471/posts/1nVUjx8WtWC

"I've rebuilt a couple of #SteamOS packages in a PPA for Ubuntu 12.04 LTS. They add a "SteamOS" session that runs Valve's compositor and starts Steam in big picture mode."

There was an explanation of what this means here:  http://www.webupd8.org/2013/12/install-steamos-session-in-ubuntu.html

This had instructions on how to install it:
http://askubuntu.com/questions/302488/can-i-run-steam-as-its-own-standalone-session

but they only work for Ubuntu 14.04, so here's the 12.04 instructions. 

NOTE:  Try this at your own risk.  It worked for me - but I can't guarantee it will work for you. Nor can I provide any tech support if your system is rendered unusable.

Enter these three commands in a terminal window - each sudo command should be one line - don't add any extra line breaks:

sudo add-apt-repository ppa:mdeslaur/steamos
sudo apt-get update
sudo apt-get install steamos-compositor steamos-modeswitch-inhibitor steamos-xpad-dkms

This will add a SteamOS login to the Ubuntu login screen.  Selecting it will launch Steam in Big Picture mode without the overhead of a normal Linux window manager.

I haven't fully tested this yet.  It seems to be behaving itself - I'll update this post as I find out more.  And - you can always remove it by

sudo apt-get remove steamos-compositor steamos-modeswitch-inhibitor steamos-xpad-dkms

and your system will be back to normal, pending a reboot.

UPDATE:  After running in SteamOS mode, then rebooting and starting Unity, my Ubuntu 12.04 LTS system lost the use of the Volume Up, Volume Down and Volume Mute keys on my multimedia keyboard.  This was a real head scratcher - none of the online guides seemed to work - and some of the fixes were downright dangerous.

I finally got my keys back by following the advice here: http://askubuntu.com/questions/387379/ubuntu-12-04-volume-up-down-mute-stopped-working and deleting my ~/.pulse directory.  You'll want to reboot immediately after doing this.

Apparently, running in SteamOS mode disables the volume keys.  Deleting the ~/.pulse folder and rebooting recovers it safely.  You'll just have to reset your audio output next time you log into Unity/Gnome.

UPDATE 2: I finally upgraded to 14.04 LTS.  There's an additional package you can add - plymouth-themes-steamos.  This is only available for 14.04 LTS and 16.04 LTS - I had to leave it out for 12.04 LTS.  So - the instructions would be the same as above but with the extra package.  e.g.:

sudo apt-get install steamos-compositor steamos-modeswitch-inhibitor steamos-xpad-dkms plymouth-themes-steamos

It doesn't change a lot - but there's an extra SteamOS splash screen.

Also - I haven't had to delete the ~/.pulse directory in 14.04 LTS - my keys have continued to work - so that's nice.  I don't know if it's the change in videocards since I wrote this originally - had AMD, now nVidia - but it does seem to set the sound to HDMI even if I had headphones or analog selected.  But - that's easy enough to set once you go back to the Ubuntu desktop.

Cheers,
Paul

If Video DownloadHelper in Ubuntu fails with a "Failed Aggregating" error message

(from the I Love Linux department)

Hi everyone,

I use Video DownloadHelper for Firefox in Ubuntu 12.04 LTS.

Sometimes, when trying to aggregate video, it fails with a "Failed Aggregating" message.

Specifically, you see this error:

ffmpeg version 0.8.17-4:0.8.17-0ubuntu0.12.04.1, Copyright (c) 2000-2014 the Libav developers
  built on Mar 16 2015 13:26:50 with gcc 4.6.3
The ffmpeg program is only provided for script compatibility and will be removed
in a future release. It has been deprecated in the Libav project to allow for
incompatible command line syntax improvements in its replacement called avconv
(see Changelog for details). Please use avconv instead.
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/tmp/media.tmp':
  Metadata:
    major_brand     : dash
    minor_version   : 0
    compatible_brands: iso6mp41
    creation_time   : 2015-04-22 12:53:09
  Duration: 00:07:02.96, start: 211.487256, bitrate: 64 kb/s
    Stream #0.0(und): Audio: aac, 44100 Hz, stereo, s16
    Metadata:
      creation_time   : 2015-04-22 12:53:09
Input #1, mov,mp4,m4a,3gp,3g2,mj2, from '/tmp/media.mp4':
  Metadata:
    major_brand     : dash
    minor_version   : 0
    compatible_brands: iso6avc1mp41
    creation_time   : 2015-04-22 13:13:56
  Duration: 00:07:02.83, start: 211.419544, bitrate: 1147 kb/s
    Stream #1.0(und): Video: h264 (High), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 tbr, 90k tbn, 47.95 tbc
    Metadata:
      creation_time   : 2015-04-22 13:13:56
Unrecognized option 'c:v'
Failed to set value 'libx264' for option 'c:v'

So - what happened?  Well - by default, Video DownloadHelper is installed to work with avconv.  But - if you reset Video DownloadHelper's settings, it falls back to an older conversion method based on ffmpeg.

This normally wouldn't be a problem, except that in Ubuntu 12.04 LTS, there is no ffmpeg.  It's actually a script front-end for avconv, and doesn't take ffmpeg's arguments.  This is the error you're seeing.

The fix is simple.  Go into Video DownloadHelper's settings, and go to the Conversion setting:

Note the Converter path - it's most likely set to /usr/bin/ffmpeg.  Change this to the location of avconv, usually /usr/bin/avconv:

Now - try your file again.  It should work.  Hope this helps!

Cheers,
Paul

tsclient for Fedora 15

(from the RPM department)

Hi everyone,

As most folks know, I do like to dabble in Linux. Lately, I've been trying Fedora 15 on a virtual machine - just to see what a cutting edge Linux is like.

One thing I miss from previous versions of Fedora is the old rdesktop GUI front-end called tsclient. That package has been deprecated in favor of newer RDP clients. But - I miss it anyway.

Well - I was able to take the SRPM for tsclient from Fedora 13, and add patches to get it to build in Fedora 15.

(Side note: Normally, I run Yellow Dog Linux on my PS3.)

I don't think this will build on YDL per se - since it's based on RedHat Enterprise Linux - but the patch system is interesting. You basically unpack the SRPM, add your patches in the form of diff files to the SOURCE directory, edit the spec file to include them, and re-package and re-build the RPM and SRPM.

No muss - no fuss.

Unfortunately, Blogger doesn't allow me to add attachments, so I've posted the files on the Yellow Dog board: tsclient for Fedora 15

Cheers,
Paul

Saying "farewell" to a part of Sony history....

(this is adapted from an entry I originally published on the Yellow Dog Linux community forums)


Hi everyone,

Well - it looks like one of PS3 Linux's ancestors is finally calling it a day. Sony is shutting down the PS2 Linux site: http://playstation2-linux.com/forum/forum.php?forum_id=1251

I'm fairly sad to see this go. I contributed many, many PS2 builds of Mozilla, Firefox & Thunderbird to this site. In fact, I attended the Mozilla 1.0 release celebrations, based on my membership there. See here: http://playstation2-linux.com/projects/mozilla-ps2

I learned much about the ways of the Sony from this site. In some ways, what we do with PS3 Linux is based on lessons learned (or unlearned) from PS2 Linux. Much like Yellow Dog Linux, PS2 Linux was also derived from Red Hat Linux, via Kondara Linux. It allowed full access to the PS2's Emotion Engine - including the twin Vector Unit processors. Only the cryptography functions were restricted so that you couldn't copy PS2 games directly.

That website was also the place I met some like-minded PS2 Linux enthusiasts. One of them is now a PS3 Linux moderator with me at the Yellow Dog Linux community forums. We met trying to compile the PS2 version of Firefox with gtk2 and freetype. Good times.

It's worth poking around the site a little bit before they shut it down for good. There's a lot of knowledge locked up in there.

Cheers,
Paul

P.S. For those of you who have never seen the PS2 Linux kit - it was quite impressive. It came with a keyboard, mouse, special network adaptor, hard drive, special VGA cable and two DVDs of source code & binary code. Here's the bundle:

Roll your own Linux!

(from the DIY department)

Hi everyone,

Found a "quick" guide to rolling your own Linux distro. I might have to give this a try....

How To Roll Your Own Linux Distro.

Cheers,
Paul

More about the Original Adventure source code

(from the YOU ARE STANDING AT THE END OF A ROAD department)

Hi everyone,

You might have seen this posting on Slashdot (or in my RSS headlines) about the original FORTRAN Adventure source code being found in an archive.

Originally written by Will Crowther, Adventure was the first text adventure game. Most people are familiar with a subsequent version that was expanded and edited by Don Woods.

Long thought lost, Crowther's original source code has been located in a backup of Don Woods' Standford student account from 1977.

Matthew T. Russotto has already translated the PDP FORTRAN to g77 (GNU FORTRAN 77) - which means that most modern gcc installations should be able to compile it.

He has a link here: http://www.russotto.net/~russotto/ADVENT/

I've gone ahead and compiled it on my PlayStation 2 Linux box (mips binary) - and on my laptop under Cygwin (x86 binary). I've never used GNU FORTRAN before - very interesting. I might have to peep the source code a bit - last time I used FORTRAN was in 1983 in college.

In the meantime,

$ ./advf4-11.exe
PAUSE  INIT DONE statement executed
To resume execution, type go.  Other input will terminate the job.
go
Execution resumes after PAUSE.
WELCOME TO ADVENTURE!!  WOULD YOU LIKE INSTRUCTIONS?

yes
SOMEWHERE NEARBY IS COLOSSAL CAVE, WHERE OTHERS HAVE FOUND
FORTUNES IN TREASURE AND GOLD, THOUGH IT IS RUMORED
THAT SOME WHO ENTER ARE NEVER SEEN AGAIN. MAGIC IS SAID
TO WORK IN THE CAVE.  I WILL BE YOUR EYES AND HANDS. DIRECT
ME WITH COMMANDS OF 1 OR 2 WORDS.
(ERRORS, SUGGESTIONS, COMPLAINTS TO CROWTHER)
(IF STUCK TYPE HELP FOR SOME HINTS)

YOU ARE STANDING AT THE END OF A ROAD BEFORE A SMALL BRICK
BUILDING . AROUND YOU IS A FOREST. A SMALL
STREAM FLOWS OUT OF THE BUILDING AND DOWN A GULLY.

go east
YOU ARE INSIDE A BUILDING, A WELL HOUSE FOR A LARGE SPRING.
THERE ARE SOME KEYS ON THE GROUND HERE.
THERE IS A SHINY BRASS LAMP NEARBY.
THERE IS FOOD HERE.
THERE IS A BOTTLE OF WATER HERE.

Cheers,
Paul