Well, the QVSS device is monocolor, so you shouldn’t see any color. The QDSS 
device was multicolor.
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.
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.

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.

David


From: Simh <[email protected]> On Behalf Of Supratim Sanyal
Sent: Thursday, March 19, 2020 1:38 PM
To: [email protected]
Subject: EXT :Re: [Simh] EXT :Re: Mouse capture on VAXstation II/GPX (KA630) 
simulator V4.0-0 Current


Very interesting. With "qvss capture" below "cpu model", mouse now works 
(jumpy, but better than no mouse). Also, I am getting console replies at the 
top of the graphical desktop, and have lost color. Here's a screenshot.

[cid:[email protected]]
On 3/19/20 1:25 PM, Supratim Sanyal wrote:
On 3/19/20 11:09 AM, Hittner, David T [US] (MS) wrote:
et cpu model=vaxstationgpx
set qvss enable                        ; if required – I think ‘set cpu model = 
vaxstationgpx’ does this implicitly
set qvss capture

Tried this sequence:

set cpu model=vaxstationgpx
set qvss enable
set qvss capture

Trying to set capture after the CPU model produces this:

"Capture Mode Can't be changed with device enabled"

BTW, an explicit "set qvss enable" produces this twice, so I think your 
thoughts on implicit enable is correct ...

"QDSS Display Created.  Uncaptured Input Mode
QVSS Display Created.  Uncaptured Input Mode"



--

Supratim Sanyal, W1XMT

39.19151 N, 77.23432 W

QCOCAL::SANYAL via HECnet

--

Supratim Sanyal, W1XMT

39.19151 N, 77.23432 W

QCOCAL::SANYAL via HECnet
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh

Reply via email to