From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: tuhs-bounces@minnie.tuhs.org X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.1 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 09103f30 for ; Wed, 29 Aug 2018 20:17:28 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 32072A1F58; Thu, 30 Aug 2018 06:17:27 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id F294CA1A22; Thu, 30 Aug 2018 06:17:16 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 33F9FA1A22; Thu, 30 Aug 2018 06:17:15 +1000 (AEST) X-Greylist: delayed 438 seconds by postgrey-1.35 at minnie.tuhs.org; Thu, 30 Aug 2018 06:17:14 AEST Received: from p3plsmtpa07-08.prod.phx3.secureserver.net (p3plsmtpa07-08.prod.phx3.secureserver.net [173.201.192.237]) by minnie.tuhs.org (Postfix) with ESMTPS id 2DA43A1A21 for ; Thu, 30 Aug 2018 06:17:14 +1000 (AEST) Received: from medusa.kilonet.net ([72.69.214.193]) by :SMTPAUTH: with ESMTPA id v6mpfQ8p69tq5v6mqfmMIe; Wed, 29 Aug 2018 13:09:56 -0700 Received: from [199.89.231.101] (ender.kilonet.net [199.89.231.101]) by medusa.kilonet.net (8.14.8/8.15.1) with ESMTP id w7TK9tWq025801 for ; Wed, 29 Aug 2018 16:09:55 -0400 (EDT) To: TUHS main list References: <1F62F4D0-7AD1-43C2-A9B7-CF9DF239C3D9@berlan.de> <02ee9a61-2920-40e0-bfa4-feb8b3d38c73@gmail.com> <30f470e7-12cb-00ac-6461-35ce8dfb425d@kilonet.net> From: Arthur Krewat Message-ID: <0cfe9e5b-6a34-cea0-3639-4bdfea039cab@kilonet.net> Date: Wed, 29 Aug 2018 16:09:49 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------5741B6756D3AB0DBFFAEE702" Content-Language: en-US X-CMAE-Envelope: MS4wfKal0tYMJ04pfv4wSGtaja26EM8BXK+6ex0TXUao7kaj9vvzEWmfruxKye1AdWs7SJ6fTxxKUtQZ33hS197g6tVYXDSWW6gjjSi/hoXOHOazFyYx/RV+ BXMMTPhDcdCFaIY6onX5MVKxJXMVb5ZlCFrknnWL+ztOEGvM74QBwX9zDCuyBvbpWXID8xYkQCQIaA== Subject: Re: [TUHS] =?utf-8?b?UmV0cm9OZXTigKY=?= X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" This is a multi-part message in MIME format. --------------5741B6756D3AB0DBFFAEE702 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit LOL - very true, Clem. That was a shameless bit of self-promotion. From what I can tell, SIMH does not support a DH11. Yet. But when is an emulated interrupt a bad thing? Except for the idle loop that may or may not be optimized, the rest is balls-to-the-wall CPU bound anyway. And these days, even emulated, we're orders of magnitude faster than the original hardware. http://simh.trailing-edge.narkive.com/Sc9HBFZU/multiple-telnet-ports-in-simh-to-rsts-e-9-6 I recognize a familiar name in there ;) But yeah, when a DZ11 was blazing away at 19200 baud (I hacked the TOPS-10 6.03A we had at LIRICS to support it), it made the system crawl. Back to our regularly scheduled programming... On 8/29/2018 3:30 PM, Clem Cole wrote: > Right but for goodness sake, try to make a DH11 work; not a DZ11!!!  >  Real DZ11'S were SW pigs and consumed a measurable percentage of a > vax, particularly when running uucico(8) (they are interrupt crazy).  >  It is one of the reasons why the Unix community in those days always > recommended Able DH/DMs on Vaxen. > > Clem > ᐧ > > On Wed, Aug 29, 2018 at 2:57 PM Arthur Krewat > wrote: > > Ala DZ11 support in the KS10 emulator of SIMH ;) > > > > On 8/29/2018 2:50 PM, Clem Cole wrote: >> >> >> We can take this off line.   As I said, it been done a numberof >> times with simh and the like.   The key is that simh creates a >> 'serial line' on a TCP port. You tell UNIX to hang a login off it >> and then you telnet or whatever to that port.    The older system >> running in simh, thinks it has a serial line.   It pretty much >> just works; al biet is slow as hell and chews up a ton of resources. > --------------5741B6756D3AB0DBFFAEE702 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit LOL - very true, Clem. That was a shameless bit of self-promotion. From what I can tell, SIMH does not support a DH11. Yet.

But when is an emulated interrupt a bad thing? Except for the idle loop that may or may not be optimized, the rest is balls-to-the-wall CPU bound anyway. And these days, even emulated, we're orders of magnitude faster than the original hardware.

http://simh.trailing-edge.narkive.com/Sc9HBFZU/multiple-telnet-ports-in-simh-to-rsts-e-9-6

I recognize a familiar name in there ;)

But yeah, when a DZ11 was blazing away at 19200 baud (I hacked the TOPS-10 6.03A we had at LIRICS to support it), it made the system crawl.

Back to our regularly scheduled programming...

On 8/29/2018 3:30 PM, Clem Cole wrote:
Right but for goodness sake, try to make a DH11 work; not a DZ11!!!   Real DZ11'S were SW pigs and consumed a measurable percentage of a vax, particularly when running uucico(8) (they are interrupt crazy).   It is one of the reasons why the Unix community in those days always recommended Able DH/DMs on Vaxen.

Clem 
ᐧ

On Wed, Aug 29, 2018 at 2:57 PM Arthur Krewat <krewat@kilonet.net> wrote:
Ala DZ11 support in the KS10 emulator of SIMH ;)



On 8/29/2018 2:50 PM, Clem Cole wrote:

We can take this off line.   As I said, it been done a numberof times with simh and the like.   The key is that simh creates a 'serial line' on a TCP port.    You tell UNIX to hang a login off it and then you telnet or whatever to that port.    The older system running in simh, thinks it has a serial line.   It pretty much just works; al biet is slow as hell and chews up a ton of resources.


--------------5741B6756D3AB0DBFFAEE702--