![]() So if you were to load V14 onto an original HW-150PVR, it'll detect the old chip and work OK, but won't act any different than with V13. ![]() V14 supports the new HW-150PVR with the new chip and remoteįeature-wise, they're all the same and there are QAM versions of each (except V3). V8 (no logo) and V13 (with logo) support the original HW-150PVR with the new remote V3 (buggy) and V10 (bugs fixed) support the original HW-150PVR with the old remote I'd try to make a venture to do this, but I'm not interested enough to devote the time (i.e., if I really cared so much for a better system, I'd just spend 10x and get a Tivo or perhaps the new ChannelMaster at 5-6x if it actually works unlike their most recent attempt.) Someone would release a device based on this mstar soc that's prettier, rear mounted usb port, better ir receiver or better yet RF, and, most importantly, open source firmware that enough people would be keen to develop on so we're not reliant on crap software written by crap developers (homeworx being, seemingly, only one of the less crappy firmwares for these devices compared at least to the iview.) I've ultimately just decided to use the 320gb drive - 40-50 hours of space is sufficient for me and has none of the headaches of troubleshooting the new drive I bought > partitioning the drive only makes a new problem I suspect -> would the homeworx automatically know where to record on the partitions? I suspect it has to do with the peculiarities of the drive/power consumption than anything else (perhaps if I bought a good powered hub that might help)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |