Advertisements In fact, the basic code to make this happen has been in teh S3 software since it shipped. The reason that I (and others) know this for a fact is that for almost a year those of us in Austin TX had this feature active - our original S3 systems were able to get schedule data via our HDTivo interface w/o cablecards. It was great - no OTA hookup, no CCard costs, and I was only paying $13/month for cable and got all my locals in QAM HD with Tivo recording features. NOTE: This feature *started* after asked Tivo to tweak their lineup to recognize the 15xx series local channels as beings our local stations, and to map the Tivo data. Tivo complied. A year ago this suddenly stopped, and calls to Tivo and TimeWarner produced the following: TIVO: "We won't map data to QAM channels" TWC: "We have not changed anything in our setup/PSIP/etc to cause this change" Both of those were verified a number of ways (including checking out what changes (none) had occured to people using QAM to get guide data in non-Tivo appliances. So from this we can assert the following: #1. The solution (mapping OTA guide data to QAM) is a trivial act already, a capability already in Tivo software or in the Tivo headend datastream. #2. It requires no act by the Cable Co to enable (although it may require the Cable Co to consent). #3. It does not require Cable Cards to execute. Based on that data, it clearly is a Tivo issue to solve - they need to outline what is required, explain the downsides (items may remap) and allow for users to opt-in with full disclosure. *IF* Cable Co consent is needed then they need to let us (the users) know, so that we can bring pressure to bear.