31 May
2021
31 May
'21
8:08 p.m.
I now have my VAXstation 4000/vlc up and running OpenVMS 7.3, DECnet Phase IV, and part of
my cluster. It?s using a SCSI2SD v5.2 board for the hard drive. While have plenty of DEC
Hard Drives, I like the lower noise, power, and heat of the SCSI2SD?s, plus I can really
cram the disk space in there, this has a whopping 32GB. :-)
I?m using a VSXXX-AA mouse (Hocky Puck), and when I use the middle-button on the mouse, it
messes up DECwindows, and I?m no longer able to use the other buttons, which means I can?t
change to another window, or access menus. It remains like this until I either logout, or
reboot.
Does this sound familiar to anyone?
This is actually the first time I?ve used a VAXstation as a VAXstation, so I don?t know if
this is normal (though I can?t imagine it is).
Zane
1 Jun
1 Jun
3:37 a.m.
On Tue, 1 Jun 2021 at 05:08, Zane Healy via cctalk
<cctalk at classiccmp.org> wrote:
I now have my VAXstation 4000/vlc up and running OpenVMS 7.3, DECnet Phase IV, and part
of my cluster. It?s using a SCSI2SD v5.2 board for the hard drive. While have plenty of
DEC Hard Drives, I like the lower noise, power, and heat of the SCSI2SD?s, plus I can
really cram the disk space in there, this has a whopping 32GB. :-)
This is good news -- well done.
I have 3 of the things, with keyboards and mice, but only 1 DEC mono
monitor. Unfortunately my to-do list is so long that I've never even
tried them since I got them 8 years ago. :-( I don't know where to
begin testing, TBH...
--
Liam Proven ? Profile: https://about.me/liamproven
Email: lproven at cix.co.uk ? gMail/gTalk/gHangouts: lproven at gmail.com
Twitter/Facebook/LinkedIn/Flickr: lproven ? Skype: liamproven
UK: +44 7939-087884 ? ?R (+ WhatsApp/Telegram/Signal): +420 702 829 053
9:27 a.m.
On May 31, 2021, at 8:08 PM, Zane Healy via cctalk <cctalk at classiccmp.org>
wrote:
I?m using a VSXXX-AA mouse (Hocky Puck), and when I use the middle-button on the mouse,
it messes up DECwindows, and I?m no longer able to use the other buttons, which means I
can?t change to another window, or access menus. It remains like this until I either
logout, or reboot.
Does this sound familiar to anyone?
I?ll answer my own question. This morning I booted up using my other VSXXX-AA mouse. And
it works as expected, so the problem is the mouse. Of course the bad mouse is the nice
one, the good one is disgusting. :-( Time to shutdown and try and clean it up.
Zane
9:39 a.m.
The described behavior is what you'd get in X11 if the middle-button is "stuck
on" (autorepeating) after being pressed the first time, and you move the mouse. Not
sure if that helps, though.
9:47 a.m.
On Tuesday, June 1, 2021, 09:39:41 AM PDT, Jonathan Stone via cctalk <cctalk at
classiccmp.org> wrote:
The described behavior is what you'd get in X11 if
the middle-button is "stuck on" (autorepeating) after being pressed the first
time, >and you move the mouse. Not sure if that helps, though.
Supposedly there's an "xev" with Decwindows Motif. Do you have one in
DECW$UTILS: ? Try it (with good mouse first) and see what it reports when the bad mouse
goes bad.
?
9:41 a.m.
On Jun 1, 2021, at 12:27 PM, Zane Healy via cctalk
<cctalk at classiccmp.org> wrote:
On May 31, 2021, at 8:08 PM, Zane Healy via cctalk <cctalk at classiccmp.org>
wrote:
It would be interesting to attach a UART to the comm link (4800 bps, RS-232 signal levels)
and capture what happens. It's quite strange to see a system failure caused by
pressing a button. I suppose it could be a bug in the system software mishandling a
protocol error on the mouse to system link. Or perhaps the mouse embedded controller has
failed so that pressing the button in question crashes the controller and makes it stop
talking to the host. In that case you'd think that unplugging and replugging the
mouse would cure the issue, though.
paul
I?m using a VSXXX-AA mouse (Hocky Puck), and when I use the middle-button on the mouse,
it messes up DECwindows, and I?m no longer able to use the other buttons, which means I
can?t change to another window, or access menus. It remains like this until I either
logout, or reboot.
Does this sound familiar to anyone?
I?ll answer my own question. This morning I booted up using my other VSXXX-AA mouse.
And it works as expected, so the problem is the mouse. Of course the bad mouse is the
nice one, the good one is disgusting. :-( Time to shutdown and try and clean it up.
11:53 a.m.
On 01/06/2021 17:41, Paul Koning via cctalk wrote:
It would be interesting to attach a UART to the comm link (4800 bps, RS-232 signal
levels) and capture what happens. It's quite strange to see a system failure caused
by pressing a button. I suppose it could be a bug in the system software mishandling a
protocol error on the mouse to system link. Or perhaps the mouse embedded controller has
failed so that pressing the button in question crashes the controller and makes it stop
talking to the host. In that case you'd think that unplugging and replugging the
mouse would cure the issue, though.
Years ago I had a VSXXX-AA mouse that stopped a VS3100-76 from powering
up. Removed the mouse and it was fine. Tried another mouse and it was fine.
I recently re-tested my DEC mice and none exhibited that behaviour, so
I've no idea where that one has ended up. I couldn't remember whether
you could hot-swap mice or keyboards (I *think* you could, but I wasn't
*sure*) so I tested the slow way, with reboots and power-cycles (and a
long gap to give the VS4000-60 a breather in between!)
Antonio
--
Antonio Carlini
antonio at acarlini.com
1:42 p.m.
On Jun 1, 2021, at 9:41 AM, Paul Koning <paulkoning at comcast.net> wrote:
I?m effectively seeing a ?Stuck On? as Jonathan describes. Since it?s fine until I hit
the middle-button, I tend to suspect that the issue is the chip in the mouse. Things go
back to normal if I?m able to log out, or reboot.
On a positive note, the ?disgusting? mouse, is no longer disgusting, but rather simply
discoloured. The rodent was actually sticky, in addition to being filthy.
Zane
On Jun 1, 2021, at 12:27 PM, Zane Healy via
cctalk <cctalk at classiccmp.org> wrote:
On May 31, 2021, at 8:08 PM, Zane Healy via cctalk <cctalk at classiccmp.org>
wrote:
It would be interesting to attach a UART to the comm link (4800 bps, RS-232 signal
levels) and capture what happens. It's quite strange to see a system failure caused
by pressing a button. I suppose it could be a bug in the system software mishandling a
protocol error on the mouse to system link. Or perhaps the mouse embedded controller has
failed so that pressing the button in question crashes the controller and makes it stop
talking to the host. In that case you'd think that unplugging and replugging the
mouse would cure the issue, though.
paul
I?m using a VSXXX-AA mouse (Hocky Puck), and when I use the middle-button on the mouse,
it messes up DECwindows, and I?m no longer able to use the other buttons, which means I
can?t change to another window, or access menus. It remains like this until I either
logout, or reboot.
Does this sound familiar to anyone?
I?ll answer my own question. This morning I booted up using my other VSXXX-AA mouse.
And it works as expected, so the problem is the mouse. Of course the bad mouse is the
nice one, the good one is disgusting. :-( Time to shutdown and try and clean it up.
1299
days inactive
1299
days old
7 comments
5 participants
participants (5)
-
a.carlini＠ntlworld.com -
healyzh＠avanthar.com -
kiwi_jonathan＠yahoo.com -
lproven＠gmail.com -
paulkoning＠comcast.net