PiDP-8: Play spacewar!

Get spacewar! up and running quickly!!

  • Set the Instruction Field (Inst Field) switches to octal 4

  • Toggle the Single Step switch (Sing Step). This loads the spacewar program at 0200, and sets up the VC8-E interface.

Display on an external Windows/Mac/Linux Machine

You need Java installed http://www.java.com/en/download/windows_xpi.jsp

Check your control panel and see if you have 32-bit or 64-bit java installed

Install and run Processing  (32-bit Java use 32-bit Processing)

https://processing.org/download/

Find vc8e.pde — load that into Processing (I got mine here: https://groups.google.com/group/pidp-8/attach/73f045074bb8c/vc8e.pde?part=0.1&authuser=0 )

Change the client ip on line 18 to the address of your Pi and click the ‘play’ button

Capture

Use 1,2,3,4 on your keyboard as the player 1 controls, 9,0,-,= for the player 2 controls.

1/9 = Fire, 2/0 =  Counter Clockwise turn, 3/0 = Clockwise turn, 4/= = Thrust

 

 

 

PiDP-8/I Running Various Programs

Run Adventure

.RUN RKB0:ADVENT
to quit
SUSPEND
to save game
.SA SYS ADV
to re-run
.R ADV

Lunar Lander

.R BASIC
NEW OR OLD--OLD
FILE NAME--RKB0:ROCKT1
RUN

Star Trek

.R BASIC
NEW OR OLD--OLD
FILE NAME--RKB0:SPACWR
RUN

Golf

.R BASIC
NEW OR OLD--OLD
FILE NAME--RKB0:GOLF
RUN
Chess
.R CHESS
Wumpus
.R BASIC NEW OR OLD–OLD
FILE NAME--RKB0:WUMPUS
RUN
 http://obsolescence.wix.com/obsolescence#!how-to-use-the-pidp-8/c1vcd

PiDP8 – Setup with Wifi (pipaOS)

At the time of this post the latest SD Image for PiDP8 was 15-Dec-2015.  These instructions are not for the serial mod, but for using a USB Serial dongle

Create SD Card

Use SDFormatter with size adjustment on and quick format the SD Card

Use Win32 Disk Imager to write the image to the card

Get the basics going

Boot the new SD Card

  • Username: pdp
  • Password: pdp

Compile the source code:

  • cd /opt/pidp8/src
  • sudo make
  • cd scanswitch
  • sudo make
  • sudo reboot

Login again

  • cd /opt/pidp8/install
  • sudo pidp8-setup-default.sh

Setting up WiFi

  • sudo nano /etc/udev/rules.d/70-persistent-net.rules

Remove all the wlan devices except the last one

Rename the last device wlan0

Type CTRL-X, Y, ENTER to save your changes

  • sudo nano /etc/network/interfaces

Put in your SSID and password (wpa-psk)

Save your changes (in green above)

Custom Pre-Login screen

  • sudo nano /etc/issue

Save your changes (in green above)

 

/******** BELOW IS STILL WORK IN PROGRESS *******/

Setting up USB Serial ports (NOT TTL) FOR A VT420 TERMINAL

First, make sure your terminal works!

Second, we’ll see if you can send data to your terminal

Determine which USB port device name

  • ls /dev/ttyUSB*

add yourself to the dialout group

  • sudo usermod -a -G dialout pdp

Install minicom

  • apt-get install minicom
  • minicom -b 4800 -o -D /dev/ttyUSB0

 

Setting up Login

Install the VT420 emulation

  • apt-get install ncurses-term

 

With ports you find do the following:

  • sudo nano /etc/inittab

Search for ttyS1, put in a line (Assuming ttyUSB0, 4800 Baud, Terminal emulation VT420)

T0:23:respawn:/sbin/getty -L ttyUSB0 4800 vt420

 

 



			
					

Simply Accounting 2010 – MAPI Error

The people at Sage can’t do even the most simple of programming correctly.

As a result, using a 64-bit email program will fail.  If you upgraded to the latest office and uninstalled your older version, you’ll find you can’t send emails anymore.

The solution is to install a 32-bit email program such as Outlook 2010 — this will mess up Outlook 2016 and you’ll need to repair the PST file.  After you use ScanPST to repair the pst file, you’ll be able to use Simply again and use Outlook 2016.

 

 

 

Stuck at Windows 7 start screen

WARNING:  Do this at your own risk

The exact cause I haven’t been able to determine why the systems hangs HOWEVER removing the Sata cable to the SSD cache while the machine is on and plugging it back in allowed the boot to continue and didn’t have a problem until months later where I had to did this again.

NOTE:  removing the Sata connector and reinstalling it while the machine was off DID NOT resolve the boot issue.

 

VM Workstation 12 – Change Autostart Order

NOTE: Don’t use an xml editor, use notepad as some of the tags do not follow proper xml format.

 

All these files are in C:\ProgramData\VMware\hostd

vmInventory.xlm – Identifies each shared virtual machine

<ConfigRoot>
<ConfigEntry id=”0003″>
<objID>4</objID>
<vmxCfgPath>C:\Users\Public\Documents\Shared Virtual Machines\XPPro\Machine1.vmx</vmxCfgPath>
</ConfigEntry>

<ConfigEntry id=”0005″>
<objID>6</objID>
<vmxCfgPath>C:\Users\Public\Documents\Shared Virtual Machines\Ubuntu\Machine2.vmx</vmxCfgPath>
</ConfigEntry>

<ConfigEntry id=”0006″>
<objID>8</objID>
<vmxCfgPath>C:\Users\Public\Documents\Shared Virtual Machines\Windows10\Machine3.vmx</vmxCfgPath>
</ConfigEntry>

<ConfigEntry id=”0007″>
<objID>9</objID>
<vmxCfgPath>C:\Users\Public\Documents\Shared Virtual Machines\Demo Server 14.04.2 Ubuntu 64-bit\Demo Server 14.04.2 Ubuntu 64-bit.vmx</vmxCfgPath>
</ConfigEntry>
</ConfigRoot>

vmAutoStart.xml – details timing between starts and order

<ConfigRoot>
<AutoStartOrder>
<_length>3<_length>
<_type>vim.host.AutoStartManager.AutoPowerInfo[]<_type>
<e id=”0″>
<_type>vim.host.AutoStartManager.AutoPowerInfo<_type>
<key>
<_type>vim.VirtualMachine<_type>
<moid>4</moid>
</key>
<startAction>PowerOn</startAction>
<startDelay>-1</startDelay>
<startOrder>-1</startOrder>
<stopAction>GuestShutdown</stopAction>
<stopDelay>120</stopDelay>
<waitForHeartbeat>systemDefault</waitForHeartbeat>
</e>
<e id=”1″>
<_type>vim.host.AutoStartManager.AutoPowerInfo<_type>
<key>
<_type>vim.VirtualMachine<_type>
<moid>6</moid>
</key>
<startAction>PowerOn</startAction>
<startDelay>-1</startDelay>
<startOrder>-1</startOrder>
<stopAction>GuestShutdown</stopAction>
<stopDelay>120</stopDelay>
<waitForHeartbeat>systemDefault</waitForHeartbeat>
</e>
<e id=”2″>
<_type>vim.host.AutoStartManager.AutoPowerInfo<_type>
<key>
<_type>vim.VirtualMachine<_type>
<moid>9</moid>
</key>
<startAction>PowerOn</startAction>
<startDelay>-1</startDelay>
<startOrder>-1</startOrder>
<stopAction>GuestShutdown</stopAction>
<stopDelay>120</stopDelay>
<waitForHeartbeat>systemDefault</waitForHeartbeat>
</e>
</AutoStartOrder>
<SystemDefaults>
<_type>vim.host.AutoStartManager.SystemDefaults<_type>
<enabled>true</enabled>
<startDelay>120</startDelay>
<stopAction>PowerOff</stopAction>
<stopDelay>120</stopDelay>
<waitForHeartbeat>false</waitForHeartbeat>
</SystemDefaults>
</ConfigRoot>

Change the moid in the order sequence you want machines to start.  Don’t use an xml editor, use notepad as some of the tags do not follow proper xml format.