WinEight Quick Start

Software Home Hardware Download


  1. Download the file, unzip it to a temporary directory, and run the SETUP.EXE program. Installation takes only a few seconds, doesn’t do anything nasty to your registry, and doesn’t require a reboot!

  2. There is a problem with the SETUP script that creates the OS8V3Q.RX1 bootable RX01 image as read-only. OS/8 is unable to run from a write protected disk, and WinEight will not allow booting from one. You need to turn off the read-only attribute on this file before proceeding. Note: WinEight does allow other, non-boot, devices to be attached to read-only files.

  3. There should be a WinEight item on your start menu. Run it, and select File >> Boot… and you should see an Open File common dialog. Select the file OS8V3Q.RX1 (be sure you’ve done step 2, above!), and click OPEN.

  4. You should see a ".", the OS/8 prompt, on your WinEight window. This window serves as a terminal emulator for the PDP-8 system. Type DIR and a carriage return and you should see an OS/8 directory. Remember – the OS/8 keyboard monitor does not understand lower case! DIR works, but dir gives the ubiquitous ? mark error message…

Booting FOCAL-69 from virtual paper tape is just as easy:

  1. Again run WinEight and select File >> Boot… Change "Files of type" drop down list to "Binary Loader Files (*.bin)", select FOCAL69.BIN and click OPEN. BTW, booting from a paper tape image assumes a program starting address of 00200. This works for most programs, including FOCAL, but certainly not all!

  2. This time nothing much will seem to happen, but if you look closely at the WinEight status bar you’ll see the message "Illegal IOT instruction 6142 executed at 04373." FOCAL attempts to initialize a number of peripherals at startup, most of which aren’t present in your WinEight emulated configuration, and WinEight is telling you what happened.

  3. You can select CPU >> Continue to keep going (there’s also a button for Continue on the tool bar), but it’ll just stop again when FOCAL executes a different IOT for another absent peripheral. To get around this, pick CPU >> Properties and uncheck the box which says "Halt emulation on unimplemented IOTs."

  4. Click Continue one more time and you’ll see




The wonderful ASR-33 Teletype font that you see in the screen shots was written by Mark Zanzig. To use it, you’ll need to visit Mark's home page and obtain your own copy, install it, and then use the WinEight Console >> Properties menu to select it. I find that it looks best if you select the bold version of the Teletype font rather than regular, but your taste may be different.

You can select any font you like for the console window. It even works correctly for variable pitch fonts (that took a lot of programming!), but you may not like the way variable pitch fonts look – the columns will not line up. If that bothers you, stay with fixed pitch fonts such as Terminal, FixedSys or Mark’s Teletype font.

By the way, the default background color of the WinEight console is supposed to approximate the parchment yellow color of an old roll of ASR-33 paper. You can change that too, if you like.

One final caution – the Teletype font has only upper case characters (so did a real Teletype, after all), and if you accidentally type in lower case, you’ll see upper case characters echoed in the console window. As a rule OS/8 era programs don’t understand lower case input, so if it seems like everything you type is just giving an error message and you can’t see anything wrong, you probably don’t have the CAPS LOCK turned on!


You can change the peripherals on your emulated PDP-8 by selecting View >> Devices (this is perhaps not the most intuitive menu choice – sorry!), which will show you a tree view of the devices currently emulated. You can add to this list by clicking the INSTALL button and then selecting from the list of devices WinEight knows how to emulate. You can connect emulated devices to external disk files by using the ATTACH and DETACH buttons on this same dialog. For some devices you can change emulation parameters (e.g. timing) by selecting the device and then clicking PROPERTIES.

For example, to add an RK05 disk to your OS/8 system, you would pick View >> Devices, then click INSTALL, select "RK8E DECpack Cartridge Disk" and click OK. Back in the Device View window, you would click the + sign to the left of the RK8E to see Unit 0, Unit 1, Unit 2 and Unit 3. Select one of those units (e.g. 0), click ATTACH, and get an Open File dialog to select the disk file. If you enter the name of a file that doesn’t exist, WinEight will ask if you want to create an empty image – simply click OK and you’re done.

Of course, you still have to build your OS/8 system to support RK05 disks, but that’s an exercise left to you!

If that seems like too much clicking, you could also simply select File >> Open…, change the "Files of Type" drop down list to "RK8E image files (*.rk5)" and then either select an existing file or enter a new name. WinEight will automatically add the RX8E/RK05 to the current configuration (if it doesn’t already exist) and then attach the file to the first free RK05 unit. In the same way you could boot from an RK05 image by selecting File >> Boot… instead.


You can see the internal registers of the emulated PDP-8 by selecting View >> Registers, which adds a register view to the tool bar. The register view is read/write, so you can stop the emulation, type some address into the PC, and click Continue and emulation will resume at the new location. In the same way you can change the AC, flags, fields, etc. The register bar is a standard Windows style docking tool bar, so you can move it around to suit your taste.

Unfortunately there’s currently no way to examine or change emulated memory. Sorry!


While I was writing WinEight, I made a conscious effort to avoid doing anything "stupid" which would ruin performance, but beyond that, no particular effort was put into tuning WinEight for maximum speed. Despite that I regularly run it on a K6/266 and I would guess that it’s about as fast as my real PDP-8/A.

WinEight is structured as two independent threads – an emulator thread, which actually executes the PDP-8 instructions, and a UI thread, which handles the menus, dialogs and the console window. Normally the emulator thread is run at a low, background, priority and the UI thread runs at the normal priority. This allows WinEight to soak up all the spare CPU cycles your system may have while still having a minimal impact on the performance of other Windows applications you may be running or on the responsiveness of its own UI.

Under Windows NT this works beautifully, however the thread scheduler on Windows 9x seems to be fairly lame and frequently the system will sit idle even though the WinEight emulator thread is runnable. This tends to kill the emulated PDP-8 speed! If this becomes objectionable you can go to the CPU >> Properties menu and uncheck the box which says "Run emulation as a background task." This will improve the emulation speed quite a bit at the cost of making the rest of your system, including the WinEight UI, somewhat spastic.

Again, this is only for 9x and ME systems. Under Windows NT/2000/XP the scheduling works perfectly and there’s never a need to disable background emulation.

Visit these Spare Time Gizmos

Calorie Record WinEight TU58 Driver OptaView Number Converter Call Review Mail Muncher Text Recorder

[logo: created and managed with Microsoft Front Page 2000]Click to join the Spare Time Gizmos Yahoo! Group.Copyright © 2000-2006 by Spare Time Gizmos.  All rights reserved.  Last modified July 31, 2006.
Send mail to with questions or comments about this web site.