[Simh] Mouse capture on VAXstation II/GPX (KA630) simulator V4.0-0 Current

[Supratim Sanyal]

On 3/19/20 5:24 PM, Hittner, David T [US] (MS) wrote:
>
> I see now; I just noticed that you were running the MicroVAX2 
> executable, not the VAX executable, which doesn’t currently have a 
> QDSS device (it could). The set cpu model command implicitly 
> enables/disables the correct device(s). Try doing a “show device” 
>  before and after the set cpu model command to see how the 
> enable/disable works.
>
> The correct configuration is:
>
> ; for multicolor vaxstation
>
> set qdss capture                            ; qdss is the color device
>
>  set cpu model=vaxstationgpx  ;vaxstationgpx is multicolor variant
>
There is something broken with QDSS device emulation - mouse capture 
does NOT work in QDSS emulation.

Mouse works fine in QVSS emulation.

So, currently, there is no way to have color graphics with mouse on SIMH 
microvax2.

I will continue to use QVSS - monochrome is charming in its own way. I 
am sure QDSS mouse capture will be fixed in the near future.

Thanks very much for your help, David.

Regards,

Supratim



> OR
>
> ; for monochrome vaxstation
>
> set qvss capture                             ;qvss is the monocolor device
>
> set cpu model=vaxstation          ;vaxstation is monocolor variant
>
> David
>
> *From:*Hittner, David T [US] (MS)
> *Sent:* Thursday, March 19, 2020 4:55 PM
> *To:* 'Supratim Sanyal' <supratim at riseup.net>; simh at trailing-edge.com
> *Subject:* RE: EXT :Re: [Simh] EXT :Re: Mouse capture on VAXstation 
> II/GPX (KA630) simulator V4.0-0 Current
>
> 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 <simh-bounces at trailing-edge.com 
> <mailto:simh-bounces at trailing-edge.com>> *On Behalf Of *Supratim Sanyal
> *Sent:* Thursday, March 19, 2020 1:38 PM
> *To:* simh at trailing-edge.com <mailto:simh at trailing-edge.com>
> *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.
>
> 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

-- 
Supratim Sanyal, W1XMT
39.19151 N, 77.23432 W
QCOCAL::SANYAL via HECnet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20200319/bf25040e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 96953 bytes
Desc: not available
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20200319/bf25040e/attachment-0001.png>