Good news! After a bit of a configuration nightmare (it is more complicated than Worldpay) I have got it working.
I will test a couple more times and then figure out what we need to do to make it live.
> Begin forwarded message:
> From: Vale Coaches - Office <office at valecoaches.com>
> Subject: Your Vale Coaches order has been received!
> Date: 31 December 2019 at 14:11:32 GMT
> To: mark.darvill at mac.com
> Reply-To: Vale Coaches <office at valecoaches.com>
> Thank you for your order
> Hi Mark,
> Just to let you know ? we've received your order #10075, and it is now being processed:
> [Order #10075] (31st December 2019)
> Product Quantity Price
> RHS Cardiff Flower Show - Saturday 18th April 2020
> Pickup Point:
> Sturminster Newton
> Packed Lunch Sandwich:
> Egg & cress on brown
> Packed Lunch Drink:
> Apple Juice
> 1 ?69.00
> Subtotal: ?69.00
> Payment method: Barclaycard
> Total: ?69.00
> Billing address
> Mark Darvill
> April Cotatge
> Sackmore Lane, Marnhull
> Sturminster Newton
> DT10 1PN
> 01258 820871
> mark.darvill at mac.com
> Thanks for using valecoaches.com!
> Vale Coaches
> Site built by Marnhull Computers Marnhull Computers <mailto:mark at marnhullcomputers.com>
On Mon, 2019-12-23 at 12:00 -0600, cctalk-request at classiccmp.org wrote:
> Re: First Internet message and ...
I read the caselaw in the GUI war cases of the 80's. Microsoft and
apple were battling over features and everyone else was being weighed.
There are nice comparative tables, TOS/GEM vs OS/2, vs Amiga, vs,
Windows..... Vs. Smalltalk.
The Xerox btw, comes out ahead of everyone.
Is there a way to get an HP-IB disk unit with an ST412 or ESDI type HDA inside to perform a low-level format?
I think this is what 'mediainit' is maybe supposed to do (based on being able to change the interleave) but I don't see any way to map bad blocks (etc.) using it. The -r 'recertify' option is apparently only valid for tape.
I have a 7946A with a Vertex V170 that needs some new blocks marked bad. There's nothing on it I need to keep, but if I use 'mediainit' on it, it fails pretty quick with an I/O error. From the sounds it makes, it's hitting the first defect (at block 64) and giving up.
# ioscan -f
Class H/W Path Driver H/W Status S/W Status
hpib 7 98624 ok(0x301) ok
disk 7.0 cs80 ok(0x220) ok
tape_drive 7.0 cs80 ok(0x220) ok
serial 9 98626 ok(0x10) ok
scsi 14 98265 ok(0x313) ok
disk 14.2 scsi ok(0x202) ok
lan 21 lla ok(0x30f) ok
# mediainit -v -i 1 /dev/rdsk/c7d0s0
mediainit: initialization process starting
mediainit: locking the volume
mediainit: performing a describe command
mediainit: running diagnostics
mediainit: initializing media
mediainit: initialize media command failed - I/O error
I know it's doing something to the disk because the data that was in the first 64 blocks is now zeroed out.
# dd if=/dev/dsk/c7d0s0 count=64 | od -x
0000000 0000 0000 0000 0000 0000 0000 0000 0000
64+0 records in
64+0 records out
# dd if=/users/bear/7946A.dd count=1 | od -x
0000000 0030 7375 2e72 0032 0000 0200 0000 0000
0000020 0000 0100 0000 0000 0000 0000 0000 0000
0000040 0000 0000 1190 1202 0644 0000 0000 0000
0000060 0000 0000 0000 0000 0000 0000 0000 0000
64+0 records in
64+0 records out
until further notice
Well, I've been working on all these RL02 drives and such in an effort
to repair the pdp11/73 that I used to bring to science fiction
conventions in the 1980's and 1990's. TALOS was the new system, BALCON
(after Balticon) was the older system that ran on RL01's and would
require me hauling a 6 foot rack of gear in a 1971 station wagon. Oh
those were the days, splitting power with the laser frobs and running
multi-player games back in the late 80's....
Anyway, Talos suffered a failure a long time ago and has been dead
since. Now that I have time and space I've been working on fixing it.
First step was to find out if anything worked, turned out one of my RL02
controllers was flakey and one of my RL02 drives had a very naughty head
that resulted in the destruction of my RSXM38 boot pack. And the memory
was unhappy. But the 11/73 CPU was sound.
After fixing that junk I was able to boot RT11 and install it on one of
the partitions of the Fujitsu ESDI disk (MTI controller, has two
partitions per disk each about 70mb in size). So finally the system and
drive logic was working but trying to boot the RSX11M image just gave me
a trap to zero fault.
First step was to fix a RSX11M 4.2 system disk. Did a quick sysgen on
SIMH, built to a RL02 pack image, then once that was up and working with
DU: driver support (the out of the box disks do not support DU:) I was
able to transfer the image over serial using pdp11GUI (great tool!) to
the RL02 drive. Now I could boot RSX11M on the RL02. However I knew that
I had only one shot to fix the Fuji drive, and I wished I had a backup.
Wait! I can make a backup of the Fuji drive using PDP11GUI! Upped the
baud rate on the 11/73 from 9600 to 38400, loaded the drivers, fired it
up, and let it run for 7 hours to copy the disk image. Really
interesting that there were no errors, meaning the disk image itself was
not the problem. Hm....
Then I made a copy on my laptop (took less than a second, sigh) and
realized I could boot the RSX11M image on SIMH *and* mount the Fuji
volume copy to find out what was up.
Booted the image, mounted the disk, and took a look. Found it pretty
quickly: Back in 1997 I was doing a cleanup of the system and did a
purge of old versions of files in [1,54]. I must have had a later
version of RSX11M there from a VMR operation that I never committed to
disk, and when I purged the older version it was the one that the boot
block was trying to reference. Thus the system ran fine but when I shut
it down and booted it a few years later it could not find the deleted
file and crashed out.
Simple. Solution was to set the default to DU2:[1,54], then boot
du2:rsx11m, hit G when the XDT debugger came up, then type SAV /WB to
re-write the boot block with the correct version of the RSX11m file.
Sure enough, the system booted up, complained about not finding the
DZV11 cards (I had removed them for testing) and was working. Shut down
the RL02 drive, did a cold restart, and TALOS came up and online :-)
Now I need to figure out what to do with it. I think it has DecNet 11/M
4.0 on it, so I could do a Phase II link with another system over serial
ports/tcpip to serial gateways. If I can find the later versions of
Decnet 11/M I could probably gen an Ethernet card and do a gateway to
TCP/IP systems. Anyone want to peer with this old system?
Overall this was an interesting little project: It required me to dust
off my hardware, software, and OS level troubleshooting skills. Now that
the system is up I can start working on hooking up the RX01 drives to
get the PDT11/150 some fixed disks, then start thinking about the 20/20
core in the shed.....
Never dull, and thank you everyone for the help and the tools.
On 12/30/19 12:47 PM, Eric Hernandez wrote:
> Hi ,
> My name is Eric (engr.eric at gmail.com), I'm from Long Beach, California,
> USA. I have an original PDP-11 Rack (just the one rack with the Digital
> logo and no other components). I absolutely love this Rack and the
> vintage logo/sign across the top, but I have to find a new home for
> it and I can't bring myself to just craigslist it for it's usage as
> a general equipment rack or to just ebay the logo at the top. I was
> wondering if anyone here knew where I can sell it to a good home or
> what a fair asking price would be for it? Thanks for any insight you
> could provide.
Cross posting to a wider audience.
Grant. . . .
unix || die
As I work to repair my RL02 collection I need to check and fix the files
on the five disks in the original boot collection. Question: Does anyone
know which directories/files went on which RL02 disk pack?
Goal is to get the packs back to the point where I can do a good old
fashioned sysgen again.
I was wondering if anyone knows what system either of these two keyboards
1) APL keyboard made by Maxi-switch, IC date codes in 1976, p/n 2129-009,
keyboard encoder has "NKBD-452 03-004-05":
2) Keyboard branded as Licon 55-500129, IC date codes in 1973 and '74. Has
three blank white keys, one blank gray key, and one blank black key, also
"home mem", "marg set" and "video rvs":
I picked up both hoping that at least one would be simple parallel output
and so useful for homebrew stuff, but I am curious about what they
originally came from.
I'm trying to find a way to get my DEC Rainbow's monochrome output onto a
newer monitor than my aging VR201 (especially since I zapped something in
it and my diagnostic efforts to date haven't fixed it).
So, I found the bit in the Rainbow docs that said the output was DC Coupled
RS-170 signals and to convert to RS-170 (NTSC black and white) I needed to
put a 10uF cap inline to make it RS-170. So I did this, and fed it into a
generic NTSC composite video to VGA thing, and got only a little joy. The
first few lines seem to be missing, then the next few are OK and then
I tried to google this, but found nothing. My google foo has failed me.
Does anybody else have a working setup?
I'm doing some work with my Pro 380 over the holidays, but have run into a snag because both my LK201 keyboards are dead. They fail poweron self test -- LEDs stay on and no response to any keypresses.
The odd thing is that the circuit board itself seems ok; I had a spare board that tests fine by itself, so I installed it as a replacement control board on one of those keyboards and now it fails. So that suggests there's something wrong with the key array that breaks selftest.
I don't understand that because the documentation says a stuck key would produce a selftest pass along with an indication reporting stuck key. And while I know LK201 keyboards don't like spilled liquids, one of those keyboards definitely hasn't been abused that way and I don't see signs the other one has, either. So having both fail the same way is puzzling.
I'm considering building a PC keyboard LK201 emulation, should be a fairly simple bit of Arduino code.