<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:x="urn:schemas-microsoft-com:office:excel" 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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Consolas;
panose-1:2 11 6 9 2 2 4 3 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Well, the QVSS device is monocolor, so you shouldn’t see any color. The QDSS device was multicolor.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If the “set cpu model= vaxstationgpx” seems to enable the qdss (multicolor) device instead of the qvss (monocolor) device, then you should be setting qdss (multicolor)
capture, not qvss.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Note that the QVSS and QDSS share the same IO space by default, and were [practically] mutually exclusive in a normal system, but could technically both exist
at the same time if the CSR and Vectors were set correctly in an extended backplane. If both are actually enabled and working, that could easily account for some mouse jumpiness as the software double-dispatches the mouse event.<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">The Operator console can be toggled on and off with one of the function keys or a control-key sequence. I can’t remember what the toggle sequence is off the top
of my head. Might be worth looking at one of the old Vaxstation manuals. Some of the odd console behavior might also be from setting the console parameter in your configuration file, or if you are using the wrong QxSS device.<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">David<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 #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 <simh-bounces@trailing-edge.com>
<b>On Behalf Of </b>Supratim Sanyal<br>
<b>Sent:</b> Thursday, March 19, 2020 1:38 PM<br>
<b>To:</b> simh@trailing-edge.com<br>
<b>Subject:</b> EXT :Re: [Simh] EXT :Re: Mouse capture on VAXstation II/GPX (KA630) simulator V4.0-0 Current<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-family:"Arial",sans-serif">Very interesting. With "qvss capture" below "cpu model", mouse now works (jumpy, but better than no mouse).</span> Also, I am getting console replies at the top of the graphical desktop, and have lost color. Here's
a screenshot.<o:p></o:p></p>
<p><img width="1048" height="905" style="width:10.9166in;height:9.427in" id="_x0000_i1025" src="cid:image001.png@01D5FE0D.37F12C40"><o:p></o:p></p>
<div>
<p class="MsoNormal">On 3/19/20 1:25 PM, Supratim Sanyal wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 3/19/20 11:09 AM, Hittner, David T [US] (MS) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
et cpu model=vaxstationgpx<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
set qvss enable ; if required – I think ‘set cpu model = vaxstationgpx’ does this implicitly<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
set qvss capture <o:p></o:p></p>
</blockquote>
<p>Tried this sequence:<o:p></o:p></p>
<p><tt><span style="font-size:10.0pt">set cpu model=vaxstationgpx</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>set qvss enable</tt><br>
<tt>set qvss capture</tt></span><o:p></o:p></p>
<p>Trying to set capture after the CPU model produces this:<o:p></o:p></p>
<p>"<tt><span style="font-size:10.0pt">Capture Mode Can't be changed with device enabled</span></tt>"<o:p></o:p></p>
<p>BTW, an explicit "set qvss enable" produces this twice, so I think your thoughts on implicit enable is correct ...<o:p></o:p></p>
<p>"<tt><span style="font-size:10.0pt">QDSS Display Created. Uncaptured Input Mode</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>QVSS Display Created. Uncaptured Input Mode</tt></span>"<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre>-- <o:p></o:p></pre>
<pre>Supratim Sanyal, W1XMT<o:p></o:p></pre>
<pre>39.19151 N, 77.23432 W<o:p></o:p></pre>
<pre>QCOCAL::SANYAL via HECnet<o:p></o:p></pre>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Supratim Sanyal, W1XMT<o:p></o:p></pre>
<pre>39.19151 N, 77.23432 W<o:p></o:p></pre>
<pre>QCOCAL::SANYAL via HECnet<o:p></o:p></pre>
</div>
</body>
</html>