Windows Live Essentials 2011

[tkout]

Still breaking sharing with WD Live TV Plus for anyone else??  I tried the beta and it broke it, seems like the full release does the same still.

[TonyPh12345]

I'll be surprised to see a fix for that at all.

The "Fix" requires a completely new build of the Samba library and all of its dependencies and interfaces to the core code.

SAMBA.ORG only fixed this back in August; a complete re-build of the WDTV code to incorporate it probably will take longer than this box has left.  

Not saying it won't happen, I just kinda doubt it.   We'll see.  

[morrallas]

Is this the fix??

https://bugzilla.samba.org/show_bug.cgi?id=7577

[Dr-haraldsen]

It has to be somthing to do with Windows Live Essentials 2011.. when i install it, nothing works and i get "invalid username..." .. but if i unninstall it, everything works again.. tell me if you find somthing.. I have serched the the internett all morning and yesturday.. nothing works.. 

[mkelley]

Did you not read what Tony posted?  He explained *exactly* what the issue is, and why it's unlikely the Live will ever be fixed for this.

The bottom line -- don't install it ("Doc, it hurts when I do this".  "Don't do that!")

[Dr-haraldsen]

I did.. But I don't know what he is talking about.. Samba what? 

Not installing it is easy enough.. But I still don't understand how Live essentials and only installing live messenger can mess up everything so fast.. Can Windows Live really be that complicated?

Give the Doc a bone!

[TonyPh12345]

---

Dr-haraldsen wrote:

,,, Can Windows Live really be that complicated?

---

Yes, it can.   With certain live components installed, Microsoft removed "Legacy" authentication methods; the ones that have worked since Windows for Workgroups a LONG time ago up until now.  

The Live/Live+ depend on those authentication methods, and without them, it won't be able to log in.

Only new versions of the SAMBA code (the code inside the WDTV that allows it to connect to Windows computers) can use the newer authentication methods.

Furthermore, With those same components installed, Microsoft introduced the usage of Tokens inside the authentication protocol that were never seen before, and even the NEWEST versions of Samba choke on those tokens, hence the need for the patch that was posted a few posts up.

As I was saying, it will take WD a lot of work to change all that out, and it just may not happen before these boxes go end of support.

This development affected MANY third-party products, not just WDTV...  Pretty much anything that used SAMBA code older than about 1 year.

[jimpalompa]

Yay! This is absolutely fkn great!

So know everyone has to choose between WDTV or  Windows Live Essentials 2011 when using network share, can't use both...

Of course, everyone can still use the old Windows Live Essentials, but who really wants to do that, now with all the social stuff implemented into Live Essentials. I was really giving my thumbs up for the new WLE 2001, and already I'm very disappointed. But who is to blame really?

Superb having a piece of hardware which developers doesn't seem to update enough (still no fkn support for the 'old' matroska header compression) along with a piece of software, that to me is one of the best updates microsoft has delivered in years.

Yay.

PS. I was being very, very ironic with the first line (if you haven't already figured that one out)

[richUK]

---

jimpalompa wrote:

Yay! This is absolutely fkn great!

So know everyone has to choose between WDTV or  Windows Live Essentials 2011 when using network share, can't use both...

Of course, everyone can still use the old Windows Live Essentials, but who really wants to do that, now with all the social stuff implemented into Live Essentials. I was really giving my thumbs up for the new WLE 2001, and already I'm very disappointed. But who is to blame really?

Superb having a piece of hardware which developers doesn't seem to update enough (still no fkn support for the 'old' matroska header compression) along with a piece of software, that to me is one of the best updates microsoft has delivered in years.

Yay.

PS. I was being very, very ironic with the first line (if you haven't already figured that one out)

---

The 'old ' matroska header compression problem is actually very new. It only happened because the developer of MKVmerge decided to implement it after all these years. I believe that the latest beta firmware implements the solution to this 'problem'.

[jimpalompa]

As I understand, the Matroska header compression has been around for years, only difference is that the new MKVmerge program has it set to default nowadays.

And who cares about the betas, why isn't WD releasing a proper firmware update already? It's been several months without a firmware fix for those MKVs