Windows Live Messenger 9.0 beta already over?


Recommended Posts

I found the following email in my inbox today:

Hello Windows Live Messenger beta testers!

Thank you for all of your efforts to help us test the latest version of Windows Live Messenger. You are some of our most engaged and passionate customers and over the last several months you've shown us just how much you care. You've sent us more than 1000 bugs and suggestions, provided valuable feedback on Windows Live Messenger v9.0 beta in three different surveys, and posted nearly 5000 messages in the newsgroup. We value your feedback - the good and the bad - and we are ready to begin using that feedback to enhance Windows Live Messenger.

For the past several months we've been gathering feedback from not only you, but also from past beta testers' comments, other external Windows Live Messenger customers, and Microsoft employees. We've compiled a thorough list of feedback, and it's now time to shift our focus to building the new version of Windows Live Messenger. Therefore, on June 24, we will close the official beta testing program.

Before the program closes we want to make sure we've reviewed and responded to all of the bugs and suggestions you sent in. The bug form will remain open through the end of this week. The newsgroup and Connect site will remain open after the bug and suggestion forms close so you can see our responses to your bugs and discuss them with other beta testers. This is a lengthy process, so we appreciate your patience as we respond to the remaining bugs and suggestions.

The good news is that even after the beta program closes you will still be

able to use the v9.0 Beta build. Please note, since the Connect site will be closed, there will be no way to download the bits from Microsoft should you want to install the build on a new or rebuilt machine. Installations you already have will continue to work.

If you have any last suggestions or bugs you want to send us, get them in by June 6 when the bug and suggestion forms will close.

Thank you again for your enthusiasm for Windows Live Messenger and all of your efforts during this beta program. There will be another beta later this year that includes the changes we're working on now, and we hope you'll participate in that and continue to send us your thoughts!

The Windows Live Messenger Team

Receiving e-mail messages from programs in which you are a participant is a mandatory part of your participation on Microsoft Connect. You can end your participation in a program at any time by visiting Your Dashboard (http://connect.microsoft.com/dashboard/) page and choosing "End Your Participation" for that program. If you do not wish to receive non-program related e-mails from Microsoft Connect, change the contact preference you have set on Your Profile (http://connect.microsoft.com/profile.aspx). This is an unmonitored e-mail address, so do not reply to this message.

Weird - they only released one beta back in November 2007, and that's it? Hm.

I don't think it's "over" but rather they are closing it for now. the beta came out VERY early and basically right after 8.5 finished. It seems to me they are getting feedback and now will be implementing the changes needed ect and working towards a more complete build and in the future may reopen it. Probably closed the beta to prevent any swaping with request durring the actual development phase.

Thats how I read the email anyway but I admittedly don't frequent the newsgroups so it's possibly I'm right off the money.

Yeah, they have closed this beta. But in the email it stated that they were just going to be working on adding features from the feedback & fixing certain bugs from the bug reports; before releasing another beta (beta 2) later in the year. Thus, it will be a while before the final version of WLMessenger 9 & there will definately be at least another beta.

Edited by cJr.
to be honest.. there isn't anything wrong with WML 8.5... I don't see the need for WLM 2008 aka 9.0

Speak for yourself. :(

Windows Live Messenger 8.5 constantly reports that I have a new email (or several) when I don't. I'll go to check my Hotmail Inbox and it will be empty. When that issue is also occurring, it does not show when I receive a new email, it just will continue to say 2 emails in my inbox (even if they're none).

to be honest.. there isn't anything wrong with WML 8.5... I don't see the need for WLM 2008 aka 9.0

Actually, WLMessenger 8.5 is Windows Live Messenger 2008 (look at the 'About' option); therefore, WLMessenger 9.0 will probably be Windows Live Messenger 2009.

I do see a point in a newer version, although maybe not too many new core features or much of a new user interface - I hear they are allowing developers to create 3rd party applications for it (without the need for MsgPlus), so if that is right, then I do see a point in it :)

I do like some of the new features announced for it - especially the option to be able to have animated GIF images as your display pic :p

  • 5 weeks later...

Actually cJr, the "Windows Live Messenger 2008" was a one time deal, according to a few developers. And for those who're wondering what this beta (Actually the correct term would be Alpha) was all about, here's a semi-in-depth artcile :).

  • 2 weeks later...

I also don't see a point for a new IM version. The functionality of WLM 8.5 works fine. How much more work can MS possibly put on WLM? I think they should release a new version with some user interface improvements and then, optimize WLM (it's kind of a memory hog), and call it a day.

The main issues with WLM is the unstable backend. Random errors where people can't sign on, or messages can't be sent etc. Awful performance when playing with appear offline. Sharing folders are just glitchy at best, although that may have improved now.

From what I understood bugs in the beta marked as Postponed were going to be added or atleast considered for WLM9...

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!