Modem Fun!

So, unlike Mr. Spooner who was downing his first pint before midday I’ve made it to after 3pm before the first of a couple of cheeky glasses of port. Before starting on my RC fun I had setup the slow cooker for pulled pork, baked two lots of scones and cooked off some chicken and sausages. After the late night we’d had on New Year’s eve there was no stirring apart from myself in the household before 11.30!

I’ve not had any retrochallenge successes today. I have learnt some things however.

I started the day attempting to make a replacement direct-connection modem cable for the Tandy Model 102. Previously I’d bought some 8-pin DIN connectors. What I hadn’t realised is that the PHONE socket on the 102/200 is slightly different to the CASSETTE socket. They are both 8-pin DIN, but the PHONE socket pins are spaced closer to the casing. Obviously I found this out after spending an hour making a new cable. It makes perfect sense that you should be prevented from plugging cables in incorrectly given their proximity on the back of the computer, however it takes some close inspection to tell the difference!

I also found that the pin numbering of the PHONE connector in the Tandy 102 Users Guide is different to the numbering on the DIN connector. A lesson learnt (I made the classis mistake initially of forgetting to put the housing on the cable for the connector before soldering otherwise I might not have noticed this difference)!

I did get a modem cable with the 102 but it’s not in good condition. Having initially thought it was wired up wrong (due to the different numbering conventions) I then double checked and found it was wired up correctly. So I tried that cable but couldn’t get anywhere dialing up @retrocosm Nostromo BBS. I suspect it has something to do with the way in which I have the phone and modem connected to the phone line. I couldn’t get a connection established.

Having spoken to folks on the club100 mailing list I’ve also found that UK Model 100/102/200’s have different ROMS with the dialing facility removed. The PROHIBITED sticker on the bottom also indicates a difference.

The Model 100 I recently acquired (which has suffered from battery leakage corrosion) doesn’t even have a PHONE connector – there is a blanking plate and no DIN-8 socket on the motherboard.

I then resorted to the acoustic coupler that I had bought NOS from the USA a couple of months ago (in a whim, on my phone, waiting for the Windermere ferry whilst out on my bike).

In anticipation I had also bought one of these ‘retro’ bluetooth handset for use with a mobile phone with the correct profile for insertion in the coupler’s cups.

I tried this setup with various communication settings (7/8 bit, even/odd/none parity, 1/2 stop bits) and did at times get an occassional intelligible response but nothing remotely reliable.
The mobile phone signal here is very poor and I won’t write off this approach without having tried a connection near the local mobile phone mast (which is next to Booth’s supermarket – Model 200 in their Cafe I anticipate).

I am still to find a convenient method of attaching images to these posts. This time round I’m including a link to a google photo album. You’d think they would make it easy to embed an album on the page, but an internet search suggests otherwise. Like Star Trek the search continues…

Modem Photos

Introduction!

Since I entered RC2016/01 I’ve had a few more ideas about what I might get up to this time around.

The primary objective is to make blogging from a Tandy Model 100/102/200 as easy as possible. I intend to write all my blog posts on a Model M. To start with the process is as follows:

* Write a blog article on the Model 200.
* Connect the Model M to a Linux PC via a null modem DB25->DB9->Serial USB cable.
* Linux PC is running a console on the said serial port.
* I run the Terminal software on the Model M, and log in to the Linux box. * I use a $ cat >blogpost.txt command and use the upload facility of the terminal software on the Model M to upload the content of the blog post to a file on the Linux box.
* I run a custom bash function that takes the resulting text file and uses the email to wordpress facility on my blog site to upload the blog to my wordpress site.

There are a number of issues with this process which I will attempt to address. The first is images. I’m attempting to get my Android phone to upload photos automatically to my wickensonline.co.uk site in a specified folder. Doing this will allow me to reference the pictures as I write the blog post. This all needs sorting out. I am using Photo Resizer HD to resize the images before upload and using the Auto Uploader application to push the file via SFTP. However, this isn’t working – I’ve emailed the developer.

Another goal is to convert Model M specific characters (other than straight ASCII) into their Unicode equivalent. I’ve done the ground work for this so it should be fairly straightforward to include as an additional step before upload.

Then I want to try and make this process as easy as possible. One goal is to remove the need for a hardwire. I would like to attempt a WIFI link up via a ESP8266 module. I then want to see how I could make blogging remotely with an upload possible.

Before Christmas I bought an acoustic coupler. It would be great to provide the ability to post blogs via a modem dial-up connection.

Happy New Year to all my fellow Retrochallengers – let the games commence!

20151231_171617

RC2016/01: The Tandy Years (1983)

I’m not setting any fixed goals this time round as that appears to be the kiss of death. I’m hoping to use the Tandy 102 or 200 as one of my blogging devices. I hope to blog a little, frequently. I may attempt to acoustically couple. Maybe blog from random places. That kind of thing. Entertaining with no focus…

tandy-model-100

The Thinking Man – Tandy Style!

You talking to me?

You talking to me?

Phreaking amazing!

Phreaking amazing!

 

A week in, really, already?

Introduction

I’ve been completely enamoured with my Tandy 102 Portable Computer since receiving it about a month ago. I can’t believe I’ve gone for so long without picking one up.

The machine itself is great – a nice readable display, excellent keyboard, great battery life, comprehensive BASIC implementation, accurate emulator ( VirtualT) and enthusiastic following. There are a number of after-market solutions for data transfer and storage, and documentation covers all aspects of the machine.

In preparation for my Retrochallenge entry I’ve ordered several books on both the Tandy model and 8085 machine language programming. The 8085 was Intel’s solution to provide a low-power and more tightly integrated version of the 8080. At around the same time the Z80 was released separately by Zilog, so both the 8085 and Z80 share a common ancestor and instruction set in the 8080, but Z80 programs won’t run on the 8085 unless they are written to only use the 8080 instruction set.

General Use

As a text editor (and I’m writing this on the Tandy 102 now) I can’t fault the hardware/software combination. It is responsive to both text entry and editing and unlike other comparable tools (such as the Cambridge Z88) the interface and keyboard shortcuts are very intuitive. For example you can use Shift-Left and Shift-Right to move backwards and forwards a word at a time, and Shift-Down and Shift-Up move you a page of text at a time.

As it is summer here one of the truly wonderful benefits is being able to ‘compute’ outside without the problems of screen visibility. I know I’ve harped on about that before with the Z88 and the HX20, but it’s worth re-iterating – the technology used in these early laptops often means they are the only viable outdoor computing options, regardless of age.

  1. Tandy 200 converted to a Rasperry Pi or other Linux based PC. LiPo based power, Teensy 2++ keyboard to USB converter, custom graphic to LCD driver (possibly).
  2. VT420 terminal with a Raspberry Pi built in, LiPo powered with DC->DC converter, keyboard shelf, possibly WiFi connectivity.
  3. Bluetooth serial module for the Tandy 102.
  4. Arduino built into Tandy 102 with Wifi shield for connectivity? Is this possible?

Introduction to the Model 102

Typed on the Tandy 102 itself…

20150627_124027

Tandy 102, Supercade, Programming Books, Fruit Tea and Space Invader’s notepad! Oh, outside, in the Sun!

This is the Tandy 102 Portable Computer. There were three variants of the Tandy Portable computer. The original model 100, the 102 (slightly thinner) and the 200 which had a flip up screen displaying more lines of thext. In order to print from the Tandy 102 you need a cable that has a 26 pin ribbon connector and a standard centronics connector. The cable I am using is for a BBC Micro and is compatible.

The operating system for the 102 was written by Microsoft and is well integrated with the excellent BASIC software. Portions of the code were written by Bill Gates and this software is credited with being the last piece of software that Bill had direct hands on involvement with.

The Model 102 comes with a 32K ROM and 24K RAM as standard. An access panel on the bottom of the machine allows the installation of a custom 32K ROM and an additional 8K of RAM.

This particular example was purchased off eBay recently for #26. My Retrochallenge entry this year features the 102 – I plan on writing several pieces of software, hopefully culminating in a machine code program burnt to an EPROM.

The text has been reformatted from the original 40 columns as was transferred to my laptop via the Linux minicom program.

EPROM woes

OK, so I’ve not got off to the best of starts here. My first week, where technology has been involved, has mostly been either repairing self-inflicted damage, fixing other people’s stuff or failing at retrochallenge.

I’ll spare you the details of my dd raid drive saga, or the restoration of my wife’s ageing windows install but will concentrate on what I’ve been trying to achieve.

When I received my Tandy Model 102 recently I was curious about burning an EPROM for it. There are quite a few images available and I like to keep it old school if possible. I had an eraser, burner and EPROMS of the right size 27C256 and felt confident once I’d order the adapter PCB that life would be sweet. I failed to get my existing EPROM burner working, or at least talking to, one of my laptops. In a act of despair I ordered a WILLEM programmer on the basis that the software was more likely to be compatible with more recent machines – certainly it couldn’t be any worse than the poorly translated Chinese software that came with my original burner. All this was around two weeks before RC2015/07 and I had the new programmer and the PCB adapter boards in plenty of time.

20150629_231719

Willem Programmer

20150629_230423

Freshly burnt Model 100 Option EPROMS

 

 

 

 

 

 

In order to construct the adapter PCB I had to find some pins that were long enough to reach into the weird PLCC like but DIP shaped receptacle that is the option ROM socket in the bottom of the Model 102. I found that IDC pins worked just fine, so soldered a load of those into the PCB and then an EPROM.

20150702_213540

First two pins of four in each corner to make fitting the rest as easy as dropping them in and soldering them!

20150702_213559

Item on the right goes into item on the left

20150702_213756

Swiss army knife with one more trick up its’ sleeve!

20150702_213808

Strip of pins. In two rows. Would have been better in one row. Ho hum.

20150702_215747

Adapter PCB will all pins fitted

20150702_220445

Another shot before the EPROM was soldered in

I have no idea what these images are doing BTW – you spend so much time using these WYSIWIG editors (didn’t that mean something once) only to find when you publish that everything has moved around.

Anyway, long story short all this was for night. I should have read the documentation more carefully, but responses to my post on the Tandy Club 100 Mailing List indicated that I was wrong to try this and that it wouldn’t work. The PCB is primarily for replacing the main ROM in a Model 100 (which is deeper) than the option ROM in a Model 102. When I inserted the adapter into the PCB I could no longer close the trapdoor – I am guessing that the model 100’s deeper housing doesn’t suffer from this failing. And so I moved on…

Game Programming

One of my thoughts was to write a game for the Tandy 102 in assembler. I’d toyed with the idea of targeting a C-compiler, but the more I looked into the Tandy’s ROM and RAM map the more I decided that it was probably going to be a hard thing to achieve. I’d done this previously with my Motorola 68000 SBC, but clearly that is more capable than the rather limited 8085.

20150620_131806

Brooke with some Ghostbusters

20150620_124442

My attempt at a Samuel Jackson selfie!

At the time I was thinking ‘game’ I both went to the North East Retrogamer (think room full of arcade cabs, pinball tables and consoles/old computers) and also rediscovered my book Supercade. Whilst perusing the book I came across a maze game for a system I’d never heard of, the Channel F. Looked like the right sort of complexity for a first stab.

Here’s the blurb (courtesy of Supercade):

Channel F Fairchild Camera and Instrument

The Channel F Video Entertainment System (VES) was introduced just following the debut of the Coleco Telstar in August 1976. Released by Fairchild and designed by Jerry Lawson, it ws the first home videogame system to use a “Videocat” game cartridge (a plug-in programmable ROM cartridge) in order to play additional
games on the system.

Prior to the release of the Channel F, videogames were selected by a series of switches or dials to toggle between various built-in games. Although the original Magnavox Odyssey did include plug-in cards, they functioned in a similar manner to the switches in that they acted as a circuit “key” to switch between pre-programmed games and didn’t contain any actual game programming. But the Channel F Videocart, with its bright yellow plastic outer casing and bold game label graphics, actually contained program ROM and is now considered the first videogame cartridge.

20150627_124302

Supercade on the ‘Channel F’

20150627_124034

Transcribing into the Model 100 from the book

Designed around the Fairchild F8 8-bit microchip and four RAM chips, the architecture of the Channel F system was revolutionary in that it was the first home videogame system to use a programmable microprocessor with a screen bitmap – basically a scaled down implementation of the technology now being used in coin-op arcade videogames.

The Channel F shipped with the main system console, two game controllers, AC adaptor, and RF box. Two “console” games – Hockey and Tennis – were pre-programmed into the system. The console itself contained a slot for inserting the optional spring-loaded cartridges ( about the size of an 8-track tape), a compartment to store the game controls, and numerous control switches including an innovative “Hold” button for freezing the action on-screen.

The Channel F was also the first home system to include a directional joystick. Videogame controllers – even the control boxes of the Odyssey – usually consisted of knobs to control the horizontal/vertical direction of active objects on-screen, or a light gun attachment for target games. However, the Channel F’s plunger style game controls – hard-wired to the console – contained a knob on top that could be moved in eight directions: forward, backward, left, right, twisted left or right, pulled up, or pushed down. With this configuration it was now possible to control any number of on-screen actions.
The Channel F was incredibly popular following its release in 1976, and by 1977 the system was on back-order for nearly six months. Fairchild released a total of 21 games for the Videocart library throughout the life of the system including Space War, Memory Match, Quadradoodle, Math Quiz, Shooting Gallery, Tic-Tac-Toe, Blackjack, Pinball Challenge and more. Zircon International (the makers of the handy “StudSensor” pocket tool) purchased the videogame division from Fairchild in 1979 and released the Channel F System 2 along with five additional game cartridges.

Unfortunately the revolutionary Channel F was swiftly eclipsed following the release of the technologically superior Atari VCS – and was discontinued in 1980.

It’s in the Game!

So I printed out a screenshot of the maze shown in the youtube video with a view to encoding it as a bit pattern:

Hand coding the maze into eight-bit bytes

Hand coding the maze into eight-bit bytes

I then wrote a quick BASIC programming to check the data was correct (there were a couple of mistakes) before moving into the murky world of 8085 assembler!

and the resulting display on the Model 102:

The maze generated via simple BASIC program, scaled to 3x original size

The maze generated via simple BASIC program, scaled to 3x original size

Tandy Model 200

I also received a Tandy Model 200 recently, with half an idea to try and replace the internals with something modern whilst keeping the same keyboard and case. Unfortunately there are three keys that don’t work on the keyboard. I originally assumed that this might be down to a connection issue and they were on the same scan row, but I discovered following disassembly that it is the individual key switches themselves that are faulty. Somewhat disappointing! So I’m going to have to look out for a donor machine.

20150703_195737

Model 200 PCB after the keyboard and screen are removed

20150703_195730

Screen and top housing

20150703_195716

The key caps take some force to remove – I highly recommend a key puller for this job.

20150703_195711

Key switches after all key caps have been removed. Notice the smaller function key switches.

20150703_194622

Always good to take a reference image of the keyboard before removing caps in anger!

Next up… programming the Virtual Model T in assembler!

Urbancamo’s RC2015/07 Entry

I recently aquired a Tandy TRS-80 Model 102. I’ve been looking for a while and finally managed to bag one in remarkable condition.

Tandy TRS-80 Model 102Tandy TRS-80 Model 102

I’ve had a play with the pretty good Microsoft BASIC implementation and would now like to explore alternative programming languages. Intel 8085 assembly language programming is well documented but there may be the possibility of targetting Small-C. I have previously been able to target a MC68000 single board computer with a C cross-compiler, although this is a trickier possibility based on the constraints of the machine.

Possible goals for this month include:

Raid Backup Battery Replacement

So I have been tinkering today with the simulated VMS set up on the server and also started making a stab at bringing up a VAX 11/780 simulator configured to run BSD Unix.

The DL380 has a backup battery attached to the internal HP Smart Array P400 controller. In this server there were two intelligent batteries – there are slots for two, presumably for if you have two controller installed (which may be a reality now that I have bought an external MSA50 drive enclosure). This system came with two batteries but alas the second battery was dead as a parrot.

There is a guide on line I’ve just found to replace the cells with an external AA four cell pack, but I went the whole hog and ordered the actual cells.

The battery compartment has a thin plastic bottom that can be sliced off revealing the four Vartar V500HT. These are available from CPC for £3.44 each. Each cell is 1.2 volt giving a total of 4.8 volts although when I measured the four new cells I got exactly 5 volts – presumably because there was no load. Anyway, the replacement process involves prizing off the crimped on connectors and repackaging the new batteries in the same order. I soldered each sandwich of batteries together at one edge. Once reinstalled I had to be careful to ensure the battery terminals were oriented correctly so the PCB pressed down on the terminals correctly.

Lunar Lander on the Kim Uno

So I finally braved the Kim Uno and typed in Lunar Lander – thanks Dale for encouraging me to do this – weird how you get so lazy with such good technology surrounding you these day. Sometimes it’s as much about the journey as the end goal.

I played a couple of games and of course turned it off without thinking. Like tears in the rain and all that. Anyway, here are a couple of photos:

Lunar Lander on the Kim Uno!

Lunar Lander on the Kim Uno!

Lunar Lander on the Kim Uno!

Had to print this out in a large font and spaced out!

Lunar Lander on the Kim Uno!

In the descent, picking up speed…

He's dead Jim!

He’s dead Jim!

Anyway, this has rekindled my interest in writing something on a (now simulated VAX) in 6502 assembler and getting it onto the Uno.

ORAC lives again!

Firstly, apologies for not taking more of an active part in the competition as an organiser. I know I’ve done half-time round ups and such in the past, but I’ve been in the unique position this month to have the time to be able to indulge myself in my own retro-tinkering, so I expect leniency from my peers! I promise to do an uber-roundup at the end. Honest.

ORAC is the first VAXstation 4000/90, and indeed the first VAX of any description, that I’ve ever owned. The name is derived from a computer appearing in the cult BBC television series Blakes 7 broadcast in the UK between 1978 and 1981. I pinched the name from a node in a VAX cluster I worked with whilst in my first job at Cyberscience Corporation around 1991.

The Perspex wonder that is ORAC

The Perspex wonder that is ORAC

I had a VMS saveset of the system disk (created in November) under Ubuntu on the HP microserver. In order to get a disk image created from it I had to load it into SIMVAX via ftp – SIMVAX is a SIMH instance running on the microserver so I was basically pulling the file from Linux into a VMS file system. This took a long time! I attached a new disk image to BUBBLE and extracted the image across DECNET. Then I stopped BUBBLE, detached the image, attached it to a new VAX MP instance (single processor only) and booted into ORAC.

Of all the VAXEN I’ve owned ORAC has had the most software thrown at it. Of note is that it runs ALLIN1 – and in fact I’ve used this to generate previous Retrochallenge entries. Besides a bit of reconfiguration still to do it looks like it’s hanging together.

I bought a quad ethernet PCI-E card off eBay to go in the DL380G5 for a very, very reasonable £7.99 which turned up yesterday. On closer inspection it looked like the connector had been hacked – part had been cut off and a notch created:

PCI-E connector - hacked!

PCI-E connector – hacked!

Now the card was sold as seen – and I hadn’t picked up on this – and indeed would never have thought to look. I contacted the seller, in a non-confrontational manner, and got a reply detailed the fact that he had used the card, it worked, and that he had bought it in this condition and sold it on at a discount price. Fair enough I guess. So I put it in the DL380, and you know what – two of the ports work, and two of them don’t. How weird is that!

So BUBBLE and ORAC are now configured on these Ethernet ports. Here are a couple of screenshots of ORAC running under VAX MP:

Mosaic Web Browser rendering the Yahoo home page!

Mosaic Web Browser rendering the Yahoo search page!

Screenshot from 2015-01-26 23:39:07

 

Screenshot from 2015-01-26 23:40:20

Screenshot from 2015-01-26 23:40:33

Screenshot from 2015-01-26 23:40:52

 

Screenshot from 2015-01-26 23:41:50

 

Screenshot from 2015-01-26 23:42:16

 

Screenshot from 2015-01-26 23:42:47

 

Screenshot from 2015-01-26 23:44:51

 

Screenshot from 2015-01-26 23:45:00

 

Screenshot from 2015-01-26 23:45:29

 

Screenshot from 2015-01-26 23:45:47

 

Screenshot from 2015-01-26 23:46:22

 

Screenshot from 2015-01-26 23:46:54

 

Screenshot from 2015-01-26 23:47:15

 

Screenshot from 2015-01-26 23:47:40

That’s all for now!

A quick update…

So, so, so.

Got a little distracted.

To say the least.

Watched Elysium tonight which was very enjoyable. Some serious compute cycles went in to that film. Last night I was attempting, still, to get DCPS to work. Someone has now kindly provided me with Version 2.7 and it’s still not working. Might need to sack that one in.

Other things I’ve been up to:

  • accidentally creating a RAID 1+0 array by adding another drive to the boot array – in an attempt to give me a bit more breathing room. So after that completed I migrated the array to RAID 5. All this after copious backups of course.
  • My hecnet bridge link to Sweden has been notorious unreliable, some weird configuration issues, so I asked Steve Davidson to try and get the long lost link between BUBBLE (the VAX MP SIMH instance) and his machine on the Eastern Seaboard of the USA. So far I’m getting a lot of ‘Circuit TCP-0-19, Adjacent node address out of range’ messages.
  • I hooked up a VT520 to a DECserver 90M to see if the simulators BUBBLE and SLAVE serve connections up via LAT – they do.
  • The developer of AlphaVM sorted out why the SLAVE instance was crashing on boot – I had used the same VMS cluster password for both SLAVE and BUBBLE. That might be a good thing long term – but at the moment they are both designed to have their own clusters.
  • Browsing eBay for server bits. I bought a 4-port GB network card for less than a tenner – still a firm believer in one emulator <-> one port.
  • Trying to work out a back up strategy for the server that doesn’t cost an arm and a leg. Considered an external MSA50 or MSA60 Storageworks array, USB3 is a non-starter (no way to provide additional power to the card), eSATA is looking unlikely, GB networking to the HP Microserver seems to be the best way to go.
  • Looking at 24 port gigabit managed switches – will need a new one in the basement at the start of my plan to reduce daisy-chaining of switches and improve network performance. Plan is to trunk 2 x 1 gigabit lines between basement and attic.
  • Wired up the PP404 line printer to see if that was still talking, but previously I used a franken-connector using at least two adapters, and that has long since disintegrated into pieces and scattered to the four corners of the attic. The cable I tried didn’t work, so that’s still one to try.

That’s about it.

Oh, and I found MGBOOK – a DEC Bookreader application written in Bliss-32 for displaying Bookreader documentation in the terminal (the standard bookreader app is strictly X11 based). It looks rather hansome with it’s SMG rendered windows:

MGBOOK Bookreader Application

MGBOOK Bookreader Application

MGBOOK Bookreader Application

MGBOOK Bookreader Application

and now the pub calls…

 

Clustering an AlphaVM node

Just a quick update before I hit the sack. I’ve been busy this evening on a number of Retrocomputing activities:

Fibre Broadband Arrived!

This morning a very nice engineer enabled and installed fibre broadband. A quick test revealed a download speed of around 80 Mbit/sec and an upload speed of around 20 Mbit/sec. Cushty. Unfortunately my somewhat esoteric network set up took a bit of licking into shape. I typically use the supplied ADSL modem as just a modem – in bridged mode – to a Mikrotik RouterBoard 2011UiAS-2HnD-IN:

MikroTik RouterBoard 2011UiAS-2HnD-IN

MikroTik RouterBoard 2011UiAS-2HnD-IN

Fortunately – and this could easily have taken all evening – a simple change in the TalkTalk supplied modem/router enabled bridged mode and I was able to set the connection via the Mikrotik RouterOS configuration page:

Mikrotik Bridging Configuration

Mikrotik Bridging Configuration

More problematic was the configuration of firewall filter and NAT rules. Whilst the Mikrotik is comprehensive it’s not always that intuitive. With power comes great responsibility. So I spent a couple of hours this evening sorting these out – I had a half arsed approach working previously which allowed routing through of an external port to an internal machine as long as the port numbers were the same. I also found that the external machine I was using to test the external connection back into my network wasn’t working with non-standard port numbers! I ended up resorting to a fellow-hecnetters VMS box to check SSH and TELNET connectivity.

Although the rules can be configured through a web-interface on the Mikrotik:

Web based NAT configuration

Web based NAT configuration

It is much easier to cut and paste scripts into the SSH command line interface, this way you can save off the configuration to a file and easily tweak, backup or recreate it.

Mikrotik SSH Access

Mikrotik SSH Access

Here’s a listing of the current NAT rules:

Mikrotik cmdline NAT configuration

Mikrotik cmdline NAT configuration

DCPS – DEC’s answer to Ghostscript

Attempting to get DCPS working on BUBBLE. DCPS was DEC’s answer to ghostscript bundled in a VMS queue symbiont format – basically it allowed you to print Postscript, ANSI encoded and TXT files (amongst others) to a postscript printer. This was working once-upon-a-time with the original BUBBLE hardware setup when configured to talk to a Kyocera FS-800 printer, but it broke at some point and I didn’t get it working again.

Now I have this fancy Brother MFC-9970CDW I was keen to get this working, but to no avail. I upgrade from Version 2.3 to Version 2.5 but I can’t persuade it to print more than the burst page. If I capture the output and copy to Linux and attempt to convert using ps2pdf ghostscript throws an error.

DCPS Burst Page

DCPS Burst Page

The postscript file does contain the text of the file that I’m attempting to print. I’ve put the feelers out for version 2.6 or the last version for the VAX 2.7 – hopefully I can persuade one of those versions to work.

AlphaVM Instance – SLAVE

I’ve previously tried to persuade AlphaVM to boot a snapshot of the important drives in my AlphaServer 1000A instance SLAVE.

SLAVE - an AlphaServer 1000A

SLAVE – an AlphaServer 1000A

Initially I tried this on the HP Microserver using AlphaVM 1.4-ish. This crashed on boot. I found the same issue with the latest test version of AlphaVM compiled for Windows.

So as an alternative I found an Alpha OpenVMS 7.3-2 installation CDROM image and created a new AlphaVM instance with a single DEC RZ59 8.5GB drive. This worked much better and I was able to configure this new instance VICTOR to cluster with BUBBLE the VAX MP instance:

Victor Clustering Request/Response

Victor Clustering Request/Response

Victor, AlphaVM 7.3-2 Boot

Victor, AlphaVM 7.3-2 Boot

With the resulting cluster, as seen from BUBBLE:

New VMS Cluster!

New VMS Cluster!

That’s enough for this evening!