After a year of being puzzled, we've finally got the WLM 2009 problem solved!


So it appears that the rudimentary MPoP system that was already coded into Escargot somewhat works with WLM 2009. I just need to tweak it so that endpoint data is updated in a timely fashion, along with the ability for the endpoint updates to be sent when other endpoints go offline. But for now, here’s a screenshot of my endeavors:


Do WLM 8.5 and older groups work on WLM 2009?


They’re named categories starting with WLM 2009, but yes.


I was talking about chat groups. Not about categories.


Ah. Yes those still existed in 2009. :stuck_out_tongue:


Sooo… WLM 2009 (without circles and etc) is almost done?


Yes! :smile:


Time to bring out my Vista VM.


What about patching?


Holy shit! Time to grab a WLM 2009 QFE2 MSI from @TReKiE!

since he has the MSI for it on the MG blog


That’s still an issue, especially since the reverse-engineer we had on board has awfully been inactive in recent months. :confused:


Also what about WLM 9.0?


I’ll look into that right after I get all the WLM 2009 stuff tested and finalized. :stuck_out_tongue:

[Edit: working from now after being overloaded]Can't connect, This time error 81000306 and sometime 800701f6

A bit off-topic but… Why haven’t you implemented 8.x’s Sharing Folders?


What if we grab another program that uses the same circle software


If the official client doesn’t like how we handle Circles, then what’s the point of relying on third-party software? Also it was getting too complex for my taste anyway.


Yeah, i don’t know who used circles back when Microsoft supported WLM.

I’m guessing that WLM 2009 will be released earlier.

I predict that during the first week of WLM 2009 being released, 75-90% of users currently using WLM 8.5 will switch to WLM 2009.


MPoP support is going well, and almost everything is in fine condition. However, there’s an odd bug where an account’s endpoint in a switchboard session might be added to a chat roster two more times. It’s not a program-breaking bug, but it’s annoying and might cause other complications, and I hope to get it fixed ASAP. After some review of the other Messenger features, support might be considered done. :slight_smile:

[Edit: working from now after being overloaded]Can't connect, This time error 81000306 and sometime 800701f6



He will go out when ?