I honestly can't say I am the most enthusiast about W7.
To me it looks like the least intuitive OS MS ever built. Difficult to explain, but things are just not in place. One example, and let's imagine you are a completely new Windows user (while at the background we sure know how things were) :
There you are. A new fresh system. Hey, that's nice, we can drag our IE icon to the taskbar, and now there it sits as a button. Great !
So, I use that button (click) ...
Allright. Let's start another instance of IE.
What the heck ... where is my button ?
You see ? this makes no sense.
We -who really know- know about the shortcut taskbar buttons (at the left). Well, MS thought to trade them for this new feature just described. I don't know, but the one who invented this should be hospitalized.
And you know, the old way of those buttons really is still there. But don't think you will be able to find out yourself how to do this.
Ok, somehow I heard only positives of you out there. It feels faster etc. Does it ? Well to me it does not. At all.
To me it looks like some technical MS nerd was set to tweak the lot without touching the real stuff. Backdoor solutions. Take for example this forum; Besides it seems impossible to type texts in an area like I'm typing in now (in some occasions), maybe you noticed the orange bar scrolling from top to bottom when a page is displayed. Well, if you know what I mean, you may have noticed that all is scattering and flickering. And no, this is not about a malfunctioning video driver (I think). This is about some opposite of Vista which virtually was slow but actually was smooth. Now it is virtually fast (flickering) but actually is slow.
All is slow, and all is less responsive. If you think otherwise ... don't believe it. Just watch carefully, and know what to watch for.
Internal priorities are hopelessly flawed !Who says ? me. And MS better listen to it.
I now know why many suddenly have problems with audio and hickups. Watch it : this is about those who started using W7.
One of the major flaws I discovered (but it's a general thing I think) is that "media" (hence audio) doesn't perceive the highest priority anymore. Thus, when a piece of kernel code is supposed to fill a buffer while another piece of user code is doing something else, that user code now has preference. STUPID ! This is just where Vista was good at, and now it is destroyed. I don't say this can't be solved, but in the mean time it now *has* to be solved, where Vista was ok with it. So thank you very much.
The sound ...
I don't know yet, but after two days of listening it seems that I hear what I see. At the rate I see "task switching" (take the orange bar as an example if you perceive that the same like I do) I hear a fake timbre in everything. More raw. This is a bit difficult because it could be real, but if that is real I don't like it much. Strangely enough this seems more apparent with WASAPI (Engine#3) than with Kernel Streaming. Or maybe it is logic ... (about task switching).
Take a look at the resource monitor; what the hell is all that network traffic doing there ? mind you, all to your own address. This wasn't before ...
Ah, my bloodily setup remote isn't working anymore. Why ? dunno yet. But I do know I don't like it.
Yes, XXEngine3 is a kind of demanding to the OS (about auto-shutdown services which I didn't see yet in W7) ... but what in heaven's name is happening with a window I cross away and which may take 30 seconds, in the mean time the red cross shivering and shivering again at that "task switching rate".
Funnily it now exhibits all the characteristics of using a wrong SSD like I did at first with Vista. Well, something *has* changed in that area for W7. Maybe it is related ?
Oh, just a minor thing : Vista already couldn't cope with WASAPI and hybernation (it just wouldn't after playing with Engine#3 for a while), but with W7 this is even more fun : Now it hybernates, but as soon as it is waked up, it shuts down. Hahaha.
Well, at least shutting off the hybernating now works, so problem solved.
That OSD time showing for a second only ... when the Wallpaper changes the handle to the screen is distroyed. A technical issue of course, and now solved by recreating that handle. In the mean time this means a "memory leak". No big deal (because it hardly takes memory) but in the mean time a major incompatibility. Or call it a bug.
Allright, if it weren't for you out there just using W7 which *thus* has to be supported, I would go back to Vista !!
But, when I can't get the sound right, I will anyway. If I can't get those priorities right, we better all go back. Keep in mind : "you" now (mostly) solved this by "tweaks" meant for changing SQ. So, your bandwidth for that has been taken away. This is not the intention of it all ...
Peter