Well it never matters how great something is: I'm never going to rush to upgrade until some other guinea pig has!
Especially for OS upgrades. Even if the vendor wanted to, there's no way they could test every possible configuration so my motto is let someone else encounter the early-adopters problems.
Mind you, this is fairly minor. The Win8.1 RT BSOD-type bootloader crash was far more serious.
Misleading performance charts? Hasn't AMD hired a bunch of marketing people who used to work for another graphic card making company who have an excellent history of such charts?
After upgrading from Windows 7 to Windows 8 the local and usb disk seemed faster and didn't freeze up the PC at all when copying data to usb disk.
Since upgrading from Windows 8 to Windows 8.1 disk performance has been reduced, WMP freezes up when starting or un-pausing a video from local or usb disk, copies have noticeable affect but still better then Windows 7.
Strange bug, Desktop shortcut files visible on desktop but not in Windows Explorer until I moved them away then back.
So it seems I'll better stick with my win 7. I will wait for a new windows to upgrade or if they fix the problems.
I upgraded 8 to 8.1 on Sunday evening, all seemed ok, until I booted up last night and all i get is a black screen and a mouse cursor. Cant be bothered to look at it at the minute, a job for the weekend. :-(
I'll most likely try a flat install.
Thanks for the clarification, as someone from an embedded & Unix background I had no idea what this was really about.
Still, If 20 years ago MS provided a shoddy broken way to read a mouse, a big part of me thinks it is their duty to maintain it for all time. That is kind of what system software is all about.
+1 for crap chart. They grind my gears
I had this problem every once in a while with 8. Can't remember the fix but you should be able to RDP into the machine and login remotely if that's enabled. It is one of the reasons why I downgraded to 7 at work. Tried really hard to find any benefits over 7 but couldn't.
No they didn't.
They provided a way to read the mouse related to what is rendered on screen. Now, guess what that means? Device Independent units!
Then the games developer doesn't use that rendering system.
This is where the problem comes from, the mouse input being in a different co-ordinate system than the rendering system.
This is why they specifically told people to use Direct Input.
The old API works exactly as it was supposed too, in fact the old bugs that allowed it to work at different DPIs were the issue.
throw new ArgumentException (String, String, Exception)
There are currently 1 users browsing this thread. (0 members and 1 guests)