<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Yes, at least some versions of the original DDP516/H316 IMP code have been recovered; it is possible to run it on the simh H316 simulator, and I am at least partially to blame for that. See<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='text-indent:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://mailman.trailing-edge.com/pipermail/simh/2013-November/007672.html">http://mailman.trailing-edge.com/pipermail/simh/2013-November/007672.html</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Of course, this just gets you a network of IMPs. To do something useful you need a host that emulates the RFC1822 interface and talks to one of the IMPs. Not too long ago Charles Anthony did that for the DPS8 and Multics, and I believe he actually got that working. That was the first case of an actual host for the simulated IMP network. It’d be fun to have another one, and if you have enough details about how the original hardware worked it should be possible to add the AN22/RFC1822 interface to the KS10 emulation.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> But, be aware that all the IMP software we have is from the early 70s and predates TCP. I don’t know if there was ever any OS for the KS10 that supported NCP networking, but if there was then it’s possible you could get something running.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> Good luck!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bob Armstrong<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Simh [mailto:simh-bounces@trailing-edge.com] <b>On Behalf Of </b>Mark Pizzolato<br><b>Sent:</b> Monday, February 29, 2016 1:33 PM<br><b>To:</b> SPC; Clem Cole<br><b>Cc:</b> SIMH<br><b>Subject:</b> Re: [Simh] KS10 IMP documentation<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bob Armstrong did the work and it was merged into the master branch in the <a href="https://github.com/simh/simh">https://github.com/simh/simh</a> repo.<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Simh [<a href="mailto:simh-bounces@trailing-edge.com">mailto:simh-bounces@trailing-edge.com</a>] <b>On Behalf Of </b>SPC<br><b>Sent:</b> Monday, February 29, 2016 1:21 PM<br><b>To:</b> Clem Cole <<a href="mailto:clemc@ccc.com">clemc@ccc.com</a>><br><b>Cc:</b> SIMH <<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>><br><b>Subject:</b> Re: [Simh] KS10 IMP documentation<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hum... not sure about this, but someone talked here some years ago about a modification of the SIMH Honeywell simulator to convert it in one IMP. I assume that he had some kind of BBN IMP code. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'm not sure if this project would be limited to tray to simulate the original ARPANET token ring limited to the IMPs or there was some other goals to reach. An example: modify another simulator adding to it a simulation of one device like this one (AN22) making it to talk with the IMP. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As I said this was a post from years ago. Perhaps was Bob Armstrong who talked about it but I'm not sure at all.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kind Regards.<o:p></o:p></p></div><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><div><p class=MsoNormal><span style='font-size:10.0pt'>Gracias | Regards - </span>Saludos | Greetings |<span lang=DE> Freundliche Grüße</span> | Salutations<span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><o:p></o:p></p></div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>-- </span><o:p></o:p></p><div><p class=MsoNormal><b><u><span style='font-size:10.0pt'>Sergio Pedraja</span></u></b><span style='font-size:10.0pt'><br></span><span style='font-family:"Arial","sans-serif"'>-- <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt'>twitter: @sergio_pedraja | skype: Sergio Pedraja<o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>--</span><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt'><a href="http://plus.google.com/u/0/101292256663392735405" target="_blank"><span style='color:#1155CC'>http://plus.google.com/u/0/101292256663392735405</span></a></span><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><a href="http://www.linkedin.com/in/sergiopedraja" target="_blank"><span style='font-family:"Times New Roman","serif";color:#1155CC'>http://www.linkedin.com/in/sergiopedraja</span></a><o:p></o:p></span></p></div><div><p class=MsoNormal>-----<span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt'>No crea todo lo que ve, ni crea que está viéndolo todo</span><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>2016-02-29 21:48 GMT+01:00 Clem Cole <<a href="mailto:clemc@ccc.com" target="_blank">clemc@ccc.com</a>>:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>Tim I'm going to guess that the AN22 implements the PDP-10 side of the BBN 1822 IMP interface. Is that a correct belief?<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>Bit Savers has the BBN 1822 document from 1976 (the original I think was '72 - I had a xerox of that one). I think I saw it about a week ago at home, so I'm nearly 100% sure I have very clean copy of the actual published in it's Yellow Cover from BBN, the later edition - which would have been the one when the IP transition was taking place or at least planned (i.e. post Arpanet - when IP was being created). If so, I'll look into getting it scanned and send an update to Al. I'm pretty sure there was changes when BBN implemented their own mini for the IMP (the C30 - which later got re-microcoded to be general purpose computer - the C70 "C Machine").<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'>I do not remember how CMU interfaced the 10's and C.mmp to their (Honeywell) IMP. I suspect it was either something like the AN22 or be a Jim "Tetter Toy" that he cooked up (I never knew). However, IIRC @ UCB Ingres 11/70s a DR-11B with a little logic (??Bob Kriddle hack maybe?? - at one time I had my hand in it). That was the UCB Arpanet interface for many, many years --- until CSRG finally got a C30 IMP in Evans in the early 1980s. Ing70 had a "very long host" interface from a Honeywell IMP that was "up the hill" at LBL. Again, IIRC the C30 could do Ethernet to the Vaxen. Or maybe it was connected to the Ethernet via a C70 which was connected the C30 (I've forgotten). But until the C30 showed up, the UCB Arpanet/Internet connection was fairly shallow; unlike CMU, MIT or Stanford.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#888888'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:#888888'>Clem<o:p></o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>On Mon, Feb 29, 2016 at 12:33 PM, Timothe Litt <<a href="mailto:litt@ieee.org" target="_blank">litt@ieee.org</a>> wrote:<o:p></o:p></p></div></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>On 29-Feb-16 12:34, <a href="mailto:b4@gewt.net" target="_blank">b4@gewt.net</a> wrote:<o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>Hello,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Arial","sans-serif";color:black'>Can anyone point me at IMP documentation for the KS10? I'm only seeing AN10 maintenance printsets up on Bitsavers...I'd love documentation that isn't KLH10's KS10-ITS implementation!<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>Alternatively, were any of the experimental Ethernet interfaces ever supported in TOPS-10/20 on the KS10? (I don't have access to my SRI-NIC packs due to the VM being down at present)<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:black'>Alternatively too...the userland ANF-10 bridge could prove useful for this...<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></blockquote></div></div><p class=MsoNormal style='margin-bottom:12.0pt'>Not clear what you want to do.<br><br>The KS does have an ARPA interface, the AN22. I have not tracked down a spec for it. It is KMC-11 based, not simulated by SimH at present. The TOPS-20 monitor sources for 4.1 are a resource. One day I'll get access to my stuff at CHM and will look for a spec. It's on my list to see if it's worth emulating.<br><br>The DEUNA is simulated in SimH. Neither the released TOPS-10 nor TOPS-20 support it. There is some TCP code floating around that does.<br><br>If you're trying to move files in and out:<br> DECnet does work (phase II on TOPS-20, Phase III or IV on TOPS-20), and will talk to VAX/RSX. You can move files by stopping on or PMR thru) one of them.<br><br> ANF-10 on the KS does work, KS-KS. It should be possible to build the -11 nodes on the KS & boot them on a SimH -11. I've been meaning to get around to that, but haven't. With ANF, besides the peripherals and terminals, you get DCP.<br><br> Networking on the KS is supported on both OSs by the KDP emulator. The DMR should work, though I think there's a monitor bug in 7.04 where my colleagues changed AC definitions and didn't update the DMR driver. Also on my list.<br><br> You can also move files in and out with Kermit (serial lines), cards, magtape, printer.<br><br>I don't know what you mean by 'anf-10 userland bridge'. Of course, FAL on the -10 listens to both DECnet and ANF.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>Simh mailing list<br><a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br><a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br>_______________________________________________<br>Simh mailing list<br><a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br><a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></body></html>