> From: Jonathan
> if someone wants to sticky this (here or in other forums), I think this
> would be a valuable resource for anyone wanting to use ImageDisk on
> non-PC formats.
How about someone doing an ImageDisk page on the Computer History Wiki; we
could include an 'External link' to the new registry (and also the original
one, etc).
Noel
Hello again, Folks!
I've listed yet another batch of S-100 goodies:
http://www.vcfed.org/forum/showthread.php?61192-Sellam-s-S-100-Hardware-Sof…
The latest batch includes a new Processor Technology kit, a BYT-8 front
panel, a Commodore PET to S-100 interface board, a couple Wameco
backplanes, a gaggle of Cromemco boards, and much more.
Thanks!
Sellam
I'd been trying to reach Dave Dunfield with new TestFDC results since
apparently August with no results. So, I wrote a new TestFDC registry into
my site:
https://services.theglitchworks.net/ng/testfdc_results
This registry currently includes Dave's last registry update from 2007.
There's now a form for entering your results, you can find it as a link
>from the registry, or here:
https://services.theglitchworks.net/ng/testfdc_results/new
Result submissions have to be manually approved currently so that the
registry doesn't get spammed. Text export forthcoming. Any suggestions
welcome!
Moderators, if someone wants to sticky this (here or in other forums), I
think this would be a valuable resource for anyone wanting to use ImageDisk
on non-PC formats.
Thanks,
Jonathan
> From: Warner Losh
> I'm curious: does it inter-operate with modern TCP/IP implementations?
This just a guess, but 'sort of'? It _is_ TCP/IPv4, so it's got compatible
headers, but I don't know if other parts have changed enough to make it not
work.
E.g. it probably only supports class A addresses, for instance, which is going
to influence the code for picking the first-hop router.
Also, the only driver is, IIRC, for an ARPANET interface.
Noel
On Thu, Jan 18, 2018 at 10:39 AM, Grant Taylor via cctalk <
cctalk at classiccmp.org> wrote:
> I was not aware that there was code that supported /only/ Class A (/8)
> addresses and /not/ Class B (/16) or Class C (/24) addresses.
>
> I /thought/ that everything was either classful (as in supports all three
> classes: A, B, and C) or classless (as in supports CIDR).
>
Years ago I added a configurable "bozo-arp" feature to the Telebit
NetBlazer router, which would respond to ARP requests for non-local
addresses and reply with the router's MAC address (on that interface),
specifically in order to make classful-only hosts work on a CIDR network.
Later someone paid me to write a NetBSD daemon ("anyipd") to do the same
thing, though for an entirely different reason. Recently I've needed that
functionality on Linux, as I have multiple old systems that only understand
classful, including the AT&T UnixPC (7300 or 3B1). I suppose I should
rewrite and open-source it.
> From: Grant Taylor
>> It is TCP/IPv4, so it's got compatible headers
> Are you referring to the 802.3 Ethernet (vs Ethernet II) frame type
No, I meant the IP and TCP headers. Those are end-end; the Ethernet stuff is
just a local wrapping, and can be substituted.
> I was not aware that there was code that supported /only/ Class A (/8)
> addresses and /not/ Class B (/16) or Class C (/24) addresses.
> I /thought/ that everything was either classful (as in supports all
> three classes: A, B, and C) or classless (as in supports CIDR).
> Is my networking history missing something else?
Yes. There was a stage before A/B/C. See RFC-760.
> Please clarify ... what you mean by ARPANET interface? Are you
> referring to host specific hardware that was used to communicate
> with an IMP?
Basically, yes.
The ARPANET supported several different kinds of interfaces between the IMPs
(the switching nodes in the ARPANET) and hosts, but the 'usual' one was
either 'Local Host' (LH) or 'Distant Host' (DH) which were _basically_
identical except at the very lowest level - LH was TTL, and DH was
differential pair.
Those interfaces were a custom bit-serial thing with a handshake (with
"there's-your-bit", "ready-for-next-bit" lines, etc); see BBN Report #1822:
http://www.bitsavers.org/pdf/bbn/imp/BBN1822_Jan1976.pdf
So the "ARPANET interface" in the host is a piece of custom hardware (some
were DMA; I also used one which was interrupt per byte) which went on the
host, which talked 1822 (as it was called), of either the DH or LH physical
form.
(There was also an Host/IMP interface called VDH, but that used a modem, and
a _lot_of software; see here:
https://en.wikipedia.org/wiki/Talk:Network_Control_Program#Layer_locations
for a bit more about it.)
> Do the necessary emulators support the ARPANET interface?
Dunno, but they shouldn't be too hard to add.
The real problem is going to be 'what do you hook the simulated ARPANET
interfaces up to, and how'? I know they have IMP code running in simulators:
http://mailman.trailing-edge.com/pipermail/simh/2013-November/007672.html
but I dunno how one would hook _that_ simulation up to a simulated host
running a simulated ARPANET interface.
Easier, to get this old TCP/IP running, might be to write a Unix V6 driver for
an Ethernet card (one the simulators do support - I know Ersatz-11 does the
Interlan NI1010A/2010A, which is nice and simple) and write an Ethernet
network interface module for that TCP, which talks to said driver; i.e. just
replace the ARPANET interface stuff completely.
Noel
> From: Lars Brinkhoff
> Richard Cornwell wants to implement DL10 for his KA10/KI10 simulator,
> but he doesn't have any documentation for it. Any leads?
Well.... The "decsystem10 System Reference Manual (DEC-10-XSRMA-A-D) -
available online:
http://bitsavers.org/www.computer.museum.uq.edu.au/pdf/DEC-10-XSRMA-A-D%20D…
has a definition for the -10 side of the interface on pages C-21 and
following (page 365 of the PDF). It just specifies the I/O instructions and
bits, there's no description of how it works.
Still, that will help understand code that uses it; the complete ITS code is
available.
I couldn't find anything on the PDP-11 side of the interface; ITS' IOELEV >
does define a "DLXCSR", and the bits in it, but ... it seems to be a memory
location, not a register?
The DL10 was used in two DEC system products, the DC76 Asynchronous
Communication System, and the DN87 and DN87S Universal Communication System
Front Ends. I couldn't find any documentation on the former, but complete
prints for the latter are available:
http://www.bitsavers.org/pdf/dec/pdp10/periph/MP00068_DN87_Universal_Comm_S…http://www.bitsavers.org/pdf/dec/pdp10/periph/MP00109_DN87S_Universal_Comm_…
It includes a complete set of prints for the DL10. From this, and also from:
http://pdp-10.trailing-edge.com/bb-d549g-sb/01/boot11.mem.html
it appears that the PDP-11's connected to the DL10 have a special console
which has a cable which goes to the DL10 which allows the PDP-10 to start and
stop the PDP-11; the PDP-11's UNIBUS runs into the DL10 and is plugged into
the DL10.
Anyway, it's going to be some hard work to create a DL10 programming manual
>from those dribs and drabs, but there is enough info there that it can be
done.
Noel