In playing with DECnet I built a DDCMP implementation which deals with a byte stream, normally from a UART. So that works nicely with async link DDCMP as found in RSX and several other operating systems. But the speed is limited.
The other option would be synchronous links, which would enable connections to DMC11 or the like at speeds up to 1 Mb/s. But synchronous comm devices that connect to modern computers aren't so easy to find, though I have seen a few.
After playing with Arduino for LK201 keyboard emulation I started to wonder if one could be made to be a synchronous comm link with a USB back end, with low level things like byte framing and maybe DDCMP packet format handling in there, but the protocol state machine in the host behind the USB interface. For moderate speeds that seems entirely practical. For 1 Mb/s, probably not, though perhaps one of the fast ARM based units with its built-in SPI could be warped into that.
The alternative would be something like a BeagleBone Black (or Green) such as David Gesswein used as the engine for his MFM hard disk emulator. That clearly could do the job without any strain.
So I'm wondering: would there be interest in such a thing? If yes, should it be a modem-connected one (RS232 signaling, bit clock supplied externally by a modem or modem-eliminator)? Or should it be the "integral modem" short distance type, the ones that used a pair of coax with 4-pin AMP connectors like this https://www.digikey.com/en/products/detail/te-connectivity-amp-connectors/2… ?
So, DEC part numbers (xx-yyyyy-zz) have a system where the 'xx' says what
_kind_ of part it is; e.g. bootstrap PROMs are all 23-xxxxx-yy. I seem to
recall reading at some point something which listed all the xx- codes, and
what they meant - but now I can't find it. A Web search didn't turn it up, and
it's not in the 1974 'engineering handbook'?
Does anyone recall seeing it, and if so, where?
Obviously, I could look through a bunch of print sets, and reconstruct it
(e.g. 90- seems to mean mounting hardware - nuts and bolts, etc) but I'd
rather not put the time and energy into reconstructing the wheel, unless
there's no other way.
Looking for HP marketing posters, in English and other world laguages large systems like HP-3000 as well as HP-150 and other pc and workstations...?? urgent need for monarch butterfly HP-150 poster!!!? Will be part of smecc museum hp display. -? Thanks Ed#
Ok, with the RX02 running I see that 50 of these disks from Solarex were
formatted with the FD: driver which is probably the MXV21 controller.
Since I don't have a 5.4 version of this driver and to be honest will
not be putting the MXV11 controller online anytime soon I'm offering
these disks for free.
So if you need 50 disks with various versions of RT11 and god knows what
data on them or 50 frisbees let me know and they're yours for the cost
of shipping. I need to either pitch these things or give them away.
So I found an RXV21 board in the pile of stuff here and popped it into
my 83. Crashes the system. It's an M8029 D board, and I see from this
site that you have to add a few traces and cut a few others to make it
work on an 11/73 or better.
I'll pop in an 11/23+ CPU just to test it, but is it really just putting
in two wires on the top of the board and cutting a total of three
traces? Looks simple enough...
On Sun, 3 Jan 2021 at 03:53, Boris Gimbarzevsky <boris at summitclinic.com> wrote:
> Ran into 68000 processor for
> first time in 1986 when my father bought a 512 K
> Mac and couldn't believe performance of this CPU
It is odd. I had read of it, of course, but for me the revelation was
getting an Acorn Archimedes in 1989, with an 8MHz ARM2, and seeing it
blast past benchmarks of ~8MHz 68K machines such as the Amiga 500 or
Atari 512 ST. It was about 4x faster, I believe.
For me -- being a bit too young for the early days of the 68K family
-- it was not a performance chip, but more about its ability to have
lots of flat memory, unlike the crippled Intel chips that IBM used.
> Weird that Rod Coleman had 68000
> instruction set associated with IBM 370 whereas
> to me it was very PDP-11 like
I've heard that before, yes,. and never the IBM comparison.
I suppose it is a matter of what you're more familiar with.
> Thanks for the link as didn't realize 68000 was
> used for home systems before I ran into Mac.
Sinclair's QL used a 68008 and was launched some weeks before the Mac.
Of course Apple's own Lisa was before the Mac, too.
Very soon after came the Amiga and ST -- the "Jackintosh", "power
without the price."
Liam Proven ? Profile: https://about.me/liamproven
Email: lproven at cix.co.uk ? gMail/gTalk/gHangouts: lproven at gmail.com
Twitter/Facebook/LinkedIn/Flickr: lproven ? Skype: liamproven
UK: +44 7939-087884 ? ?R (+ WhatsApp/Telegram/Signal): +420 702 829 053
The question was asked (I misplaced the note) if the OS images that are on the Xhomer website work with David Gesswein's MFM emulator on real hardware.
You can turn these into emulator data files, provided you have the latest ext2emu tool that's part of David's software (as of 1/19/2021). The format needed is "Elektronika_85" which is the Pro format, called that because it was first added to the emulator as the format found on the Russian bootleg copy of the Pro of that name.
Results, on my Pro 380:
1. P/OS 3.2: works.
2. Venix: panic at boot, "Bad access number". That doesn't mean anything to me. I wonder if the issue is that Venix doesn't support the 380.
3. RT-11 5.3: works.
For grins I tried a smaller interleave factor than the default 5:1, since it seems reasonable that this should make things go faster on the Pro 380, given that its CPU is about 4x the speed of the one in the Pro 350. Somewhat to my surprise this isn't the case; the performance indicates that at 4:1 or smaller interleave the software misses the next sector and has to wait for another revolution.
As some people here are aware, I have spent probably too much time this summer
hacking on J. David Bryan's excellent Classic HP 3000 simulator and trying to
build up the ultimate classic 1980s HP 3000 system (virtually speaking).
I started with the MPE V/R KIT that's widely available and expanded that into a
5x120MB HP 7925 disc system and configured things like the system directory
size and all the system tables to make a fully functional multi-user server.
I then set about collecting as much old MPE software as I could find, which
included Keven Miller's collection of the old Contributed Software Library tapes
which were conveniently available in SIMH format. This is a huge trove of cool
stuff including most of the classic mini/mainframe games (Dungeon, Warp,
Advent, etc., etc.) and even a little game called DRAGONS that was written in
1980 by a guy named Bruce Nesmith when he was in college and he used it
to get a job at TSR and went on to write parts of many classic D&D products
and eventually landed at Bethesda where among other things he was the
lead designer for another little game called The Elder Scrolls V: Skyrim. I was
able to track Bruce down and give him a copy of the system with his 40 year
old game running on it. The CSL tapes also include other amazing goodies
that people developed and gave away over the years, including a FORTH and
LISP, as well as most of the system and utility programs that people used to
run their 3000 shops. It's quite fun to explore.
I was curious how far we could push the 3000 simulator, so I hacked all
the memory bank registers to be six bits instead of four bits, and we
now have a simulated HP 3000 Series III that supports 8MB of memory, 4x
more than any physical system ever did. I started trying to do the same thing
for giant disc drives, but MPE turned out to have too much knowledge of
what the supported disc models look like to make it practical. Bummer.
Since I met my first HP 3000 in 1980 (40 years ago this month), people would
talk about what was probably the most rare and exotic HP software subsystem
ever produced, APL\3000. APL on the 3000 was a project started at HP Labs
in Palo Alto in the early 1970s. They were likely motivated by the success IBM
was having with mainframe APL timesharing services. This would be the first
full APL implementation on a "small" (non-mainframe) computer. It would be the
first APL with a compiler (and a byte-code virtual machine to execute the
compiled code), it would include an additional new language APLGOL (APL
with ALGOL like structured control statements), and it managed to support
APL workspaces of unlimited size through a clever set of system CPU
microcode extensions that provided a flat 32-bit addressing capability (on
a 16-bit machine where every other language was limited to a 64KB data
Because APL required these extra special CPU instructions that you got as
a set of ROM chips when you bought the $15,000 APL\3000, and because
APL ultimately failed as a product (another story in itself) and thus HP never
implemented these instructions on their later HP 3000 models, I never saw
it run on a real HP 3000, but over the years we talked about wouldn't it be
cool to find a way to get APL running again.
With assistance and moral support from Stan Sieler and Frank McConnell
and others, I was ultimately able to reverse-engineer the behavior of the
undocumented ten magic APL CPU instructions needed to get it to run and
implement them as part of the MPE unimplemented instruction trap and now
APL\3000 runs again for the first time in ~35 years. Somewhat ironically, this
implementation method could have been used back in 1980 as I didn't
actually end up changing the hardware simulation code at all, and it should
also run (if a bit slowly) on any physical classic architecture 3000.
So that was cool and all, but what is APL without all the weird overstruck
characters and whatnot? APL\3000 supports the use of plain ASCII terminals
through blecherous trigraphs like "QD for the APL quad character, but this
is hardly satisfying. So the quest was on to find a solution. Back in 1976 when
APL\3000 was released, there was a companion HP terminal in the 264x line,
the HP 2641A APL Display Station, which was basically an HP 2645A with
special firmware and APL character set ROMs that supported all the APL
special characters as well as overstrikes (the terminal would take X<backspace>Y
and lookup to see if it had a character to represent Y overstriking X and if
so it would show that on the display, and if that got transmitted to the host it
would convert it back into the original three character overstriking sequence).
I briefly looked into the idea of hacking QCTerm or Putty or something, but
then I found out from Curious Chris that an HP 2645A emulator already existed
in the MAME emulator system! Since the '41 is basically just a '45 with modified
firmware, and Bitsavers had both the character set ROMs as well as the
firmware ROMs from a '41, this sounded like it might be easy! There was a snag
however in that the firmware ROM images that were allegedly from a '41 turned
out to actually be from an ordinary '45. But we did have the character sets and
one of the ROMs from the second CTL PCA. I put out a call on the Vintage HP
list to see if anyone might possibly have a lead on an actual HP 2641A, and
Kyle Owen responded that not only did he have one he could also dump the
ROMs for us. So a few days and a few hacks to F. Ulivi's MAME hp2645 driver
later we now have a functioning MAME HP 2641A terminal emulation, so you
can experience APL\3000 in all its original glory. I bundled up a somewhat
stripped down MAME along with my turnkey 3000 setup so both emulated HP
terminals are just a couple clicks away.
So that's how I spent my summer vacation (who am I kidding, it's pretty much all
vacation these days). It has been a lot of fun revisiting all this old
3000 stuff as
well as the numerous people I talked to along the way including some of those
who were around at APL\3000's birth (before my time). It was rather a lot of
work so I'd like to feel it might be useful to someone in the future
who is digging
into this part of history. Because of all the usual reasons, I don't
plan on hosting
it permanently until and unless we maybe someday get the licensing worked out
(the 50th anniversary of the HP 3000 will be in a couple years so maybe people
will get interested again then) but I will offer it up here to my
history nuts if you want to help ensure that it doesn't vanish if I
get run over by a
bus or something :)
This is a simulated HP 3000 Series III (circa 1980) running MPE V/R (circa 1986)
with 8MB of memory, all the language subsystems (APL, BASIC, BASICOMP, RPG,
FORTRAN (66), SPL, PASCAL, COBOL (68), COBOL II (74)), 20 years of users group
contributed software, many classic historical computer games, etc. Software
archaeologists can get lost in here for years. Oh, and thanks to Dave
HP 2000 Timesharing BASIC contributed library is even included (kinda sorta
converted to MPE BASIC) for good measure. This is a streamlined turnkey edition
that's ready to run out of the box with no assembly required (all
batteries are included).
Currently, I only provide executables for Windows (sorry) but am in
the process of
getting the 3000 simulator changes (for large memory support) and the new MAME
hp2641 driver back upstream. Instructions and further details can be
found in the
README.txt hint book for this adventure. 94MB Google Drive link:
P.S. I'm giving a talk on the history of APL\3000 and its resurrection
to the ACM APLBUG
group in a couple weeks. If anyone is interested I can provide more
details when I have