CursorXP not always on top??

It's weird, I always thought my cursor disappear but it's actually just underneath the window....I tried to turn on and off but it didn't work. When I'm not using cursorXP, the cursor is always on top but once I started CursorXP, the cursor went under the window....







8,094 views 14 replies
Reply #1 Top
From GreenReaper: It's a Windows layering bug and it's been marked as 'not going to fix.' I've had that problem a few times, a reboot always fixed it.
Reply #2 Top
not going to fix...!?! I noticed that every time after I reboot the problem fixed but after every thing loaded, the same problem occur again...

Reply #3 Top
It's a shame there are no plans to overcome this bug, although I've not tried CursorXP under Vista yet, maybe MS will have addressed the layering bug, but I found it inconvenient to keep rebooting my PC when the cursor started disappearing under an icon or time an entire window, and stopped using it, and I'm registered user of CursorXP Plus too!
Reply #4 Top
It seems to happen more frequently to some users and hardly at all to others. I've had it happen only a handful of times and I can't even remember the last time it happened.
Reply #5 Top
It is a more bad drivers for the graphics card problem being not loaded correctly. This is common with XP a lot and ya a restart will fix it for a while. But a good fix is not to restart. But to defrag and then logoff and back in. If that fails then the only fix is to restart after a good defrag and hope it holds. If it does hold then logoff while it is fixed and log back in.
The usual cause for bad loading is a quick login, after a restart. If you take good notice of XP loading before you login. You will see it is still running before you try to login. [That is if you have a hard drive light to see if the hard drive is running or not?]

Even with Vista - there is a loading time for the restart. This is always present with any high graphics type of a system. That and espically one that also use a domain type of login. Domains are usually only used tho with business systems.

Just give it a few mins to load after the restart and then login. Then if it is working at the time. Do a logoff to clear the system cache for the load. Thus after you login again the system should be stable enough to run clean and clear graphics. Good luck and hope this helps!

Oh buy the way - the no fix thing is because there is none at all except this here. This due to the fact that it is more a hardware problem with loading the drivers correctly. Than that of a faulty program design. Which it is not and truely no fix is being worked on at this time.

But a newer 64bit windows OS is being designed as I write this to completely address the graphics issues. With a complete fix - but even now we predict a login and restart process time procedure.

Good luck and keep skinning happy!

SGT  
Reply #6 Top
only happens to me after a resolution change
Reply #7 Top
only happens to me after a resolution change
So only in the first week after the New Year?
Reply #8 Top
    
Reply #9 Top
I was just going to ask about this. Here is an example.



I had an even better one, but it stopped working. It was with the Onix skin such that the cursor was under Rainlendar (at desktop level) and over the window but under the window frame. I think Bill Gates had a thing for optical illusions in his youth.
Reply #10 Top
  




  
Reply #11 Top
Lets face it cursorxp is a flawed product. I had the same problem when cursorxp first came out a few years ago. I have a much better computer now built with excellent video cards ( yes cards ) I decided to try cursorxp again. Same problem as before. Cursorxp is a flawed product. I am going to uninstall the piece of crap and move on.
Reply #12 Top
Or MS is  a flawed app. 
Uninstall windows.
Reply #13 Top
this happens a lot, and there isn't really much you can do. i found the easiest way to solve this is to change your screen ressolution then change it back again, it's a lot less hassle than re-booting your system.
Reply #14 Top
not going to fix...!?! I noticed that every time after I reboot the problem fixed but after every thing loaded, the same problem occur again...


Just for reference sake.

MS is not going to fix this. Stardock isn't the one not fixing in this instance.