did the people who built the boxee device even test it?

[jasonjm]

I mean you would think the first thing they would test is linking the system to media sources, isn't that the purpose of the device?

EPIC failure of management.

[Prospero424]

I know you're frustrated, but you have to understand the absolutely MASSIVE number of variables involved in Windows file sharing due to the way Windows handles not just SMB/CIFS, but user accounts and permissions.

I know a lot of people seem to be having problems with share access, but remember: you'll never hear from the vast majority of those for whom it IS working properly.

I'm also willing to bet that 99% of the problems being had turn out to be Windows- and permissions-related rather than due to an actual flaw with the Boxee Box's SMB client. It may take a while for some people to realize what is actually causing the problem, but more often than not, it's not what they expected it to be.

Boxee has been THOROUGHLY tested with SMB access over the past two years. The hardware may have changed, but the SMB client in the software is actually quite mature.

These problems with share access were inevitable, and it was also inevitable that Boxee would be blamed for problems that actually originate with Windows and/or user error because it's all part of the overall experience with the product.

So yeah, I really, really do understand the frustration. All I can do is urge patience and hope that this raises awareness of problems inherent in the current Windows CIFS file sharing system. To put it mildly: consistency is NOT its strong suit.

[jasonjm]

I know you're frustrated, but you have to understand the absolutely MASSIVE number of variables involved in Windows file sharing due to the way Windows handles not just SMB/CIFS, but user accounts and permissions.

I know a lot of people seem to be having problems with share access, but remember: you'll never hear from the vast majority of those for whom it IS working properly.

I'm also willing to bet that 99% of the problems being had turn out to be Windows- and permissions-related rather than due to an actual flaw with the Boxee Box's SMB client. It may take a while for some people to realize what is actually causing the problem, but more often than not, it's not what they expected it to be.

Boxee has been THOROUGHLY tested with SMB access over the past two years. The hardware may have changed, but the SMB client in the software is actually quite mature.

These problems with share access were inevitable, and it was also inevitable that Boxee would be blamed for problems that actually originate with Windows and/or user error because it's all part of the overall experience with the product.

So yeah, I really, really do understand the frustration. All I can do is urge patience and hope that this raises awareness of problems inherent in the current Windows CIFS file sharing system. To put it mildly: consistency is NOT its strong suit.


I guarantee you that with the current boxee firmware, less than 5% of users with this device and windows 7 will be able to set it up without referencing a forum like this

and I bet a large chunk of windows 7 users who manage to get to this forum will still not manage to get it working

[Prospero424]

I guarantee you that with the current boxee firmware, less than 5% of users with this device and windows 7 will be able to set it up without referencing a forum like this

and I bet a large chunk of windows 7 users who manage to get to this forum will still not manage to get it working

If we're talking about users who are already familiar with how to access a network share and therefore would be interested in setting up access to one in the first place, I think that 5% number is downright silly.

Some problems are inevitable, but like I said: we'll never hear from the people for whom it's working properly.

Windows has, over two decades, stacked layers and layers of cruft on top of what should be a straightforward interconnect process. CIFS under Win 7 is basically an open wound bandaged with bandaid layered on top of bandaid. The problem is that the additional layers are NOT transparent to everyday users, so they don't even see that they're there.

Oh well, neither of us has any way of even making a semi-accurate guess as to the percentage of end users having this problem with currently available data, so speculation is useless.

I'm glad you at least got your access working.

[brianXQ3]

not to start an OS war or anything :) but no problems with SMB and Mac OS X 10.6.4 over here. happily streaming my content and enjoying the 1080p goodness

[Prospero424]

It undoubtedly works fine for a lot of people with a wide array of OS environments. Obviously not everybody, but a lot.

Just for reference, here's a succinct rant on the problems OSX has with SMB sharing: http://arstechnica.com/apple/guides/2010/10/the-21st-century-guide-to-platform-trolling-apple-edition.ars/3

Love the title of the article, heh.

[melll]

I love my Boxee Box, and let me say that, since everyone is entitled to their opinion. :)

[jasonjm]

now that my box is working, it seems pretty good, so I am keeping mine.

but there was no legitimate reason for me to have gone through one hour of research to join a windows 7 share.....
other than lazy coding and poor testing before release.

And I mention windows 7 because I would think the largest group of users are going to be windows 7 users, so you would think that would be their number one test base.

[slimon007]

Mine connected and was indexing shares before I even got the picture on my tv.

[pcm2a]

It would be nice to know if Boxee was reading this forum and were planning on resolving any of these issues in short order.

[jasonjm]

Mine connected and was indexing shares before I even got the picture on my tv.


was your version of windows 7 home edition? 32 bit?

mine was windows 7 ultimate 64 bit, set up for corporate environment.

wonder if the part boxee did not like was the

64bit
or ultimate edition
or the part where its setup for corporate (on domain, with advanced shares)