During the working day some background process will start accessing my HD, and whilst active, this shuts down any other program I am running by perhaps 95%. This can last anywhere from 5 mins to 2 hrs. It appears to have no relation to anything I am working on and can happen at any time of the day. To find which background process out of over 100 is doing this, I tried loading Resource Monitor via resmon.exe at the Start Menu or via the button on the Performance tab in Task Manager. Both ways result in the same - the Resource Monitor starts loading its window but doesn't complete. So I am unable to access the Disk tab on it. There is an hourglass indicating it is still loading, but after 15 mins gets no further than the window frame and the top bar containing "File Monitor Help". Curiously all these three are active. Tried loading the RM whilst the HD is being accessed and whilst not. Makes no difference.
Unable to find any reference to this problem being reported anywhere.
Related
Good Morning
Hoping someone has some experience with this, when the power settings are set to set the monitors to go to sleep after x number of minutes, the monitors then refuse to wake back up. On laptops, this also stops the display on the laptop when opening the lid.
No amount of button presses or combination of buttons wakes the monitors up and has to be hard powered.
At the moment we have had to set VIDEOLOCK and VIDEOCONLOCK to ridiculous timeout settings to stop people losing their work when going on breaks etc but at a loss as to what is causing the displays to drop out completely - PCI Express power saving has also been turned off but made no impact.
Changed power settings and registries through Group Policies and through powercfg but nothing seems to stop the monitors from dropping out after the display goes to sleep.
Actually, I'm new to 'xamarin.mac' applications and I'm trying an application that takes screenshot frequently also captures system idle time on login.So far I've managed to capture screenshot but How to take system idle time?
I've gone through 'NSEvents'.But I cannot figure it out how to implement those
event against button click.
I just want the system idle time count that starts on login.
I have the following setup:
My application has a sticky button (i.e. clicking the button makes it stay down, until it's clicked again when it goes up).
Multiple instances of the application can run concurrently.
A "detector" application needs to be able to report whether or not at least one of the above buttons is currently down.
There can be a limit to how many instances are supported, but clicking the button once the limit is exceeded should gracefully fail.
How can I do this, using Windows API calls? So far I have used CreateSemaphore, however that has an insurmountable problem that if the application is killed, the semaphore count is not incremented (so the button is still reported as down even when all applications are closed).
Note: this is not a newbie question
Main window of my application occasionally "freezes" with symptoms listed below. The application continues to work properly as soon as main window resized.
Debuggers, Windows Application Verifier and other tools I used revealed no problems.
What could be a reason or how can I check why the window becomes blocked from updates?
Some details:
old 32-bits c++ MFC application, worked fine for many years on many Window XP installations in 24/7 mode
the app renders some simple 2D graphics with MFC/GDI functions
on several computers under 64-bits Windows 7, very rarely (~once per month) app's main window stops updating: it looks exactly as if the app took a screenshot of client area of its main window and shows this screenshot until mail window resized
my diagnostic logs and all kind tools indicate that once frozen, internally the app works normally: it still renders updates but because of some reason Windows ignores them
application main menu opens and works properly
all drawings are made in single thread
various modal dialogs called via main menu also work properly
Notepad brought on top on my app shows properly and leaves no traces behind
Windows itself and all other application always work properly
I would think this is something related to the video card/its driver we are using (3 monitors connected to two NVIDIA NVS 300) but I don't understand why only my application is affected. Also I would love to know with what magic the resizing removes the update lock.
Update 12/9/2015:
I'm sure the drawing thread is not blocked: it is application main thread that also always properly responds to mouse clicks, menu commands and keyboard
All counters (memory, processor, GDI/USER objects) indicate no problems
I'm trying to make an simple anti-idle script (that moves the mouse or whatever) to prevent an application from stopping.
How can I keep it running after screen lock ?
It seems like this is explained in the Autoit faq :
http://www.autoitscript.com/wiki/FAQ#Why_doesn.27t_my_script_work_on_a_locked_workstation.3F
On locked station any window will never be active (active is only dialog with text "Press Ctrl+Alt+Del") In Windows locked state applications runs hidden (behind that visible dialog) and haven't focus and active status.
So generally don't use Send() MouseClick() WinActivate() WinWaitActive() WinActive() etc.
Instead use ControlSend() ControlSetText() ControlClick() WinWait() WinExists() WinMenuSelectItem() etc. This way you may have your script resistive against another active windows. It's possible to run such script from scheduler on locked Windows station.
You can't automate anything after your screen is locked. User input is simply ignored. A much easier way would be to prevent your screen from locking, for example, by moving the mouse randomly every 30 seconds.