[pups] A bootable disk image for a PDP-11/34?

[Ian King]

After seeing all the mail of success with the Supnik emulator, I found a
compiled copy and tried that -- and got to a login: prompt!  That's with the
image you sent me -- many thanks.  I'm going to have to learn more about the
Supnik emulator now; in particular, I need to understand how to set it for a
given processor emulation, so that once I rebuild the system to run on a '34
(which is supposed to be feasible), I can be reasonably sure it will work
once it's ported over to the real machine. 

NOTE: neither simulator will run in a DOS box on Windows 2000.  E11 starts
up, but has problem accessing files (you can't MOUNT a file as a device).
Supnik just won't go at all.  I've been running my emulator on a DOS machine
(actually, an old 486 laptop; hey guys, I have a laptop PDP-11!).  

Cheers -- Ian 

-----Original Message-----
From: Ken Wellsch [mailto:kwellsch at tampabay.rr.com]
Sent: Wednesday, January 31, 2001 5:20 AM
To: pups at minnie.cs.adfa.edu.au
Subject: Re: [pups] A bootable disk image for a PDP-11/34?


Ian King wrote:
> 
> Ken, I tried using that image and gunzip told me there was a crc error; it
> wouldn't unzip it.  (I downloaded it three times, just in case there was a
> transmission error -- twice by ftp, once by http.)

So going over all the things I can easily do data integrity checks on, I've
run 'gzip -tv' on all the GZip'ed things and found three that are apparently
damaged:

gzip: ./PDP-11/Distributions/dec/Ultrix-3.1/ultrix-3.1-bootape.tar.gz:
              invalid compressed data--crc error
gzip: ./PDP-11/Distributions/research/Ken_Wellsch_v6/v6.tape.gz:
              invalid compressed data--crc error
gzip: ./PDP-11/Distributions/unsw/90/record0.gz:
              invalid compressed data--crc error

I can't comment on the *.Z compressed archives as they do not do any crc.

I will have to peruse my stack of archive CD's made at various stages of
the archive to see if I have the other two (I have a good 'v6.tape.gz'
file).

I did not try and run the MD5 list yet.  But this is an example of why I
had been pushing for the use of MD5 for all items in the archive...  B^)

-- Ken