Bug fix from Monday fixed, new software update, new features too

[oscarv]

All,

If you did a 'git pull' yesterday, and you run your PiDP-10 headless, my last update broke something. I am sorry!

Bug fix:

I just updated the PiDP-10 software. 

1. Update

Do 'git pull' on the /opt/pidp10 directory, 

then run /opt/pidp10/install/install.sh again. 

Say No to everything, except Y to these two questions:

- Automatically start the PiDP-10 ...?

- Do you wish to add a DEC flavour to the desktop?

2. In case of trouble, check this

I don't think it hurts, but if you have trouble: open the file ~/.config/wayfire.ini, and check if there is only one copy of 

[autostart]
pidp = pdpcontrol start

If you see that twice, remove one copy and save. I apologise for this!

New feature:

If you run from the Pi's GUI, you will see new icons on the desktop. These are the equivalent of the various commands like 'pdp tvcon' or 'pdp telcon'. Just quicker. 

Using the desktop icons, you don't necessarily have to use 'pdp view'.

Booting up ITS can also be done as follows:

• Press STOP, then READ IN switches (as always, if you have a physical PiDP-10)
• Double-click desktop icon TELCON (or CON)
• Type its<cr><esc><g> on the Teletype
• And once ITS is up, double-click the Knight (or IMLAC, VT-52, etc) desktop icon.

Annoyance:

Alas, the new Wayland GUI on the Pi cannot make me automate the following from the install script.

By default, if you double-click a desktop Icon, the Pi asks you to 'Execute, etc'. To get rid of this annoyance, launch the File Manager, go to the Edit-->Preferences menu item, and enable the "Don't ask options on launch executable file' item:

It seems there is no failsafe way to automate this for you in the install script (let me know if you have a way!).

Kind regards,

Oscar.

[oscarv]

And some more information for those who installed and run the PiDP-10 headless (that is, not on the HDMI monitor but through ssh connections):

I had not tested running the install script headless, and that caused a bug on Monday. Now fixed, but there are some things to know.

Issue:

The Pi started using Wayland instead of X11 for its GUI.

But Wayland wants GUI programs to autostart from its own wayfire.ini, instead of the normal .profile config file that, oh, everyone uses since about the seventies <grumble>.

So I need to support one method of autostarting the PiDP-10 for Wayland, and another way for X11. Brilliant.

Not an issue:

1. If you install the PiDP-10 using a HDMI monitor and USB keyboard, and don't want to switch the Pi back from "modern" Wayland to the previous X11 GUI, no need to read. You can always use headless too.

2. If you installed the PiDP-10 headless, but later on decide to use the HDMI monitor to view the graphics displays on the default Wayland setup:

- run the install script again and only say Yes to "Automatically start the PiDP-10 ...?". Now the script will know you are running Wayland and will adjust the autostart.

3. If you at some point decide to switch from Wayland to X11 because you hate Wayland,

- run the install script again and only say Yes to "Automatically start the PiDP-10 ...?". Now the script will know you are running X11 and will adjust the autostart.

Hopefully I got this right, this time! Please let me know.

Oscar.

[sunnyboy010101]

Stupid question I know, but could I please get the full command for the "git pull /opt/pidp10" because that alone doesn't work. I built this current system using the "git clone" from the draft PiDP10 manual, and I know about git and all that, but "git pull" needs somewhere to get the info from.

Thanks,

-R

[terry-...@glaver.org]

Just cd to /opt/pidp10 and do a "git pull". You do this as the regular user (normally "pi"), not root:

pi@PiDP10:~ $ cd /opt/pidp10
pi@PiDP10:/opt/pidp10 $ git pull
Already up to date.
pi@PiDP10:/opt/pidp10 $

[sunnyboy010101]

Thanks. I do notice that TOPS20 works fine, but now TOPS10 gives gibberish during the boot sequence and never finishes. It worked before I did "git pull" and followed the instructions.

-R

[sunnyboy010101]

In the above for TOPS10, I've started the system "pdpcontrol start 2" then telnet to localhost 1025 and then in telnet start the boot process as per the quick start up guide. I've done this a few times before the update tonight and it always booted just fine; I was able to log in and all that. 

Now, It seems to boot TOPS10 normally until here:

%DPB6 IS OFF-LINE

%DPB7 IS OFF-LINE

% INTFCR File command error

% INTFCR File command error

after that I see

KA603 12:25:18 CTY system 50
.LOGIN 1,2
.R OPSER
[OPRPAF Processing auto command file]
}12:25:27(M1)
        ?KILL?
        .?No start adr
        .

and then just gibberish (lots of *!) and it's locked into some kind of command error loop.

[terry-...@glaver.org]

If you haven't applied any customizations to the emulator or supplied operating systems, I'd say just delete (or rename if you want to be cautious) /opt/pidp10 and start over with the steps from the building instructions:

cd /opt

sudo git clone https://github.com/obsolescence/pidp10

/opt/pidp10/install/install.sh

[sunnyboy010101]

Thanks. That did it. TOPS10 now booting and running correctly.