mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Software

Reply
 
Thread Tools
Old 2016-02-05, 14:19   #1
Dionysus
 
Feb 2016

210 Posts
Unhappy Suspect Software Incompatibility

Since installing VMWare Horizon client to access workplace server, my Dell system loses keyboard and mouse access after Prime95 has been running a while, forcing a hard reboot and disabling of the Prime client to regain access. Any ideas besides disabling the VMWare client?
Dionysus is offline   Reply With Quote
Old 2016-02-05, 18:48   #2
VBCurtis
 
VBCurtis's Avatar
 
"Curtis"
Feb 2005
Riverside, CA

10010010001102 Posts
Default

"losing kb/mouse access" sounds more like a hard lockup- does the screen indicate computations are running normally after kb/mouse fail?

It might just be overheating?
VBCurtis is online now   Reply With Quote
Old 2016-02-06, 02:18   #3
LaurV
Romulan Interpreter
 
LaurV's Avatar
 
Jun 2011
Thailand

52×7×53 Posts
Default

Not related to p95, but a win7 issue. We use synergy to access different machines around, and have the same problem with other tasks. Especially what bother us most is that we can not login next morning, if after logout in the evening, we (or a colleague) moved the mouse out of screen (to another computer's screen which is not logged out). We can use the other computer, but it is no way to come back to this computer and click the box where we have to type the login password. Neither local kbd (tab, alt-space, F6, etc, other meanings to "switch tasks") do not work. Hard reboot.

We now close synergy before logout, and since a while we discovered a better way, we take the (wireless) mouse from the table and hide it in the drawer (turning it off from the switch under its belly doesn't help, we tried)

Also, opening any system/console/[on screen keyboard*] on the guest machine (not the one where the mouse is physically connected) during normal work, loses the synergy access. We have to lift our bottom and use the local kbd on that machine to terminate the window (that computer has no mouse connected, but it has a local kbd laying somewhere around, out of our reach)

[edit: * also opening the "on screen kbd" on the target computer, we can click the keys with the remote mouse, but we ca not close it anymore, from the red X. By some magic we can't understand - and we were a "windows programmer" for 30 years! I mean system programmer, not applications, we ported winCE to embedded systems, etc. - the red X is totally insensitive to the remote mouse working over synergy (wired net) - none of these thingies ever happened with win XP in the past, before we migrated to 7]

So, losing kbg and mouse access may not be related to "running P95 for a while" but to levels of priorities for those windows that you open and close.

Last fiddled with by LaurV on 2016-02-06 at 02:33
LaurV is offline   Reply With Quote
Old 2016-02-07, 13:49   #4
Dionysus
 
Feb 2016

2 Posts
Smile Problem solved

Tnx for "housekeeping" suggestion. Some dust in CPU/FPU fan - sprayed that and air movement fans clean - so far after 24 hrs no more KB/mouse freeze!
Dionysus is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Suspect results koekie Data 7 2018-02-17 00:06
Suspect results bgbeuning PrimeNet 7 2017-07-20 16:18
Two very suspect results tha Data 6 2015-05-22 16:46
CUDA-gcc incompatibility workaround Dubslow GPU Computing 5 2013-01-26 17:18
suspect LL assigned again to me rudi_m PrimeNet 10 2009-02-12 09:56

All times are UTC. The time now is 22:55.

Mon Mar 8 22:55:17 UTC 2021 up 95 days, 19:06, 0 users, load averages: 1.22, 1.52, 1.73

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.