@Joe: The reason we're looking at tru2way is for the deployment of advanced applications. I can't speak specifically for the other cable companies, but I have heard their upper management speak at conferences and this isn't something they've touched on as being the primary reason for tru2wayt. Most of the cable companies are looking to deploy tru2way on set top boxes that are already owned by the company and deployed to the customers. This is approx. 40% of the set tops in our system. Unsure about the other companies.

As for whether they're in a rush to implement or not that's hard to say. It's going to be years before we see large numbers of tru2way consumer devices on our system. We've supported cable cards for a while. But we have less than a hundred on our system and they are a pain to get working. Each different model of TV had different issues to overcome and required a lot of hand holding by our staff. tru2way "should" (hopefully) be better.

I work at a small mid-sized independently owned cable company and we have deployed Moxi to our customers.

@Joe Maki: tru2way does much more than that. tru2way is basically a Java stack on the set top box. What it allows, in addition to what you mentioned, is for 3rd party applications to be easily run on the set top box. Right now it's all proprietary code, difficult and expensive to develop for and limited in scope. tru2way allows the writing of more advanced applications and television guides and only having to write them once instead of a proprietary port for each manufacturer and each model in that manufacturer's line.

@Eric: I work for a cable company that has some of the older Moxi boxes. They don't run Windows, they run Linux. They've made some improvements with their newest code that is faster and much less buggier than the original.