[Simh] Re: Simh Digest, Vol 5, Issue 3

Bob Supnik bob at supnik.org
Sun Apr 18 12:45:41 EDT 2004


Actually, it's a double bug.  The TQK70 not only has the wrong media ID, it 
has the wrong model byte.  It should be model = 14, and media ID = 
0x6d68b046, as you suggest.

Thanks for finding this.

/Bob Supnik

At 12:00 PM 4/18/2004 -0400, you wrote:
><snip>
>
>Message: 2
>Date: Sat, 17 Apr 2004 22:09:07 -0400
>From: "Robert G. Schaffrath" <robert at schaffrath.net>
>Subject: [Simh] Odd TK70 support
>To: <simh at trailing-edge.com>
>Message-ID: <001801c424ea$218aaca0$c50c2e18 at rgs>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Having worked with the VAX simulator for almost two months, I became 
>rather curious as to why setting TQ to TK50 created "MU" devices of type 
>"TK50" but setting it to TK70 resulted in "MI" devices with a device type 
>of "TF70".  Poking through the pdp11_tq.c source code I noticed that the 
>media ID, as defined by TQ7_MED, is set to 0x6A68B046.  As a test, I 
>changed the definition to 0x6D68B046 and now VMS running on my private 
>vax.exe build reports "MU" devices of type "TK70".  Is the "6A" a typo in 
>the source or is it a requirement for some other operating system?  One 
>week of testing with VMS has not turned up any problems.
>--
>Robert G. Schaffrath
>http://www.schaffrath.net
>+1.516.759.4314




More information about the Simh mailing list