Well what do you know the leak is the RTM. Brandon LeBlanc confirmed the build number. MD5 stuff probably won't matter. I think we would have heard by now if it contained malware as some sort of fake. I'm pretty sure this is the first time the RTM has leaked well in advance of Brandon's blog.
You're very welcome Mike.I would like to thank all of you who had faith in this announcement from the start, and those who had the confidence to speak their opinion, irregardless of the outcome. Debate is at the heart of all good discussion. Sadly, I became a naysayer for a few hours, of files that even I originally announced must be the RTM bits. We know now, with 100% certainty, that this build is the RTM. This confirmation has come from Microsoft. I am glad we have been able to make these files available for such a long duration of time, wherefore, a great deal of analysis and resources went into checking authenticity.
Questioning the legitimacy of these files was acceptable, and for a short time, I did a complete 180 and became concerned these weren't the files. A quick examination of how the Service Pack functioned after the February Patch Tuesday releases created confidence between the admin team that this was the RTM once again. External forces had shaped differing opinions, but it is good that at the end of the day, we stuck to our principles.
The files will remain online so that members who desire the Service Pack can use them right now. Thanks to Microsoft, for giving out the build number details and confirmation of RTM status. We are excited to be able to provide these files for those who feel they absolutely need SP1 today.
No HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\CurrentMetadata key here either.Seems to me that Windows Media Player version 12.0.7601.17514 that comes with SP1 does not write the HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\CurrentMetadata key any more. I was using it to get the WMP track title and album art in a Rainmeter skin but the registry entry seems to have dissapeared.
Is it just me or do other people have that key and some info that gets updated in their registry?
It was a Rainmeter skin that was I was working on and it was working just fine until I installed SP1 with the newer (?) version of WMP 12. I can't see what WMP would have used the registry key for anyway so maybe they just decided it was a waste of time having it write the currentmetadata everytime a new track or movie was played.I also don't find the skin you mention in the list of "official" skins on the MS WMP skin site either.
Could be a bug with Rainmeter.
Ah it's kinda like Conky in Ubuntu but developed for Windows.It was a Rainmeter skin that was I was working on and it was working just fine until I installed SP1 with the newer (?) version of WMP 12. I can't see what WMP would have used the registry key for anyway so maybe they just decided it was a waste of time having it write the currentmetadata everytime a new track or movie was played.
I have no use for FRAPS but installed the free version to check this.
It seems to work fine for me.
I'm not a gamer hence my comment about having no use for FRAPS.What kind of video card are you using, and you have Aero enabled? After some extensive testing, here was what Josephur and I found:
"I have done further testing and it seems that the issue is the overall system hook that FRAPS uses to hook to the video source it wants to capture. If my screen contains any kind of overlay (such as a 3d game, screen saver preview window, or any other program that uses the OS's overlay function) then FRAPS attempts to use that overlay instead of the overall system overlay. I suspect that FRAPS will have to be updated to understand how 7 SP1 handles overlay. My guess is FRAPS sets a win32 API hook to capture Overlay 0, and Windows 7 has changed the Overlay to 1 (or whatever). So I suspect the issue is the new Service Pack's Direct3D stack, possibly this was changed because of the new RemoteFX features as well, as they need access to the overlay."
This information has been sent to Beepa Support for them to take a look at.
(Images of FRAPS overlay on applications, but not on appearing on the desktop itself)
This is regarding the inability to record DWM (Aero) workspace, including the entire desktop. It works fine pre-SP1
I guess I don' know what you want this program to do.We are specifically talking about the ability to record/screenshot/FPS the entire desktop itself and not just a game. We are almost 100% positive it is SP1