avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Sunday June 4, 2023, 1:21 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - TichGirl [ switch to compact view ]

Pages: [1]
Thank you @IainB, for the pointers.  :) I'm thinking it's not a mouse issue at the root cause for some reason, since when it is changing to the Wait cursor I'm unable to click anything (often-times even with a Wait cursor, Windows will still let me click something). Just a hunch, though I could be wrong.

@SkyWire, I was thinking the same about it possibly not being possible, but thought I'd ask anyway in case anyone else knew something that I don't. Maybe a Super-Mega-Grand-Poobah-Guru would've known some super sneaky and clever way to do this, lol.

I did have this problem for a while now; but, I recently upgraded my motherboard, ram and cpu, and it seems to be even more so than when it was happening on my last mobo/ram/cpu. I have just been watching my processes with taskmanager, and noticed a dllhost.exe constantly opening and closing, which made me raise an eyebrow. I looked at it's command-line and it's to C:\Windows\system32\DllHost.exe /Processid:{AB8902B4-09CA-4BB6-B78D-A8F59079A8D5}.

Looking in the registry at that CLSID it points to thumbcache.dll. I'm wondering if this could be the root cause?

I'm having a strange issue where my mouse cursor keeps showing the Wait/Working cursor, and while it does, I'm unable to click to perform whatever action. Especially in Explorer. It'll show the Wait cursor for a second then the normal cursor, then wait cursor, over and over with varying timespans when the Wait cursor shows. This is on a very fast system, so I'm thinking it's not due to something like maxed out CPU, etc.

I watch the RAM, and CPU while it's happening and there's plenty of RAM, and The CPU is nowhere near maxed. I'm wondering if there's some way to log/display EXACTLY which program just triggered the wait cursor. For example, if I write a VB program (let's call it "MyApp.exe") I can manually set the cursor to the Wait cursor like this: Me.Cursor = Cursors.WaitCursor, in which case, I'd like to see "MyApp.exe" show up "live" as it happens, in maybe a floating window(?) or even just a .txt log.

Then I could narrow down or eliminate this tricky, and maddening problem easily. :(

Pages: [1]