Naturally SourceForge would change their URL mappings so soon after my posts.
Here are some link updates (for the original README, almost all were within the
RTVpatch project):
The
ISO referred to is now here.
extract_rtv can now be found here:
extract_rtv5 (new version)
PC /
Mac
extract_rtv (old version)
PC /
Mac
-------------------------------------------------------
Also, HTTPFS is part of the ReplayPC program suite.
-------------------------------------------------------
As the DVArchive method of getting files into your RTV 4K/5K has been discussed extensively in many other threads I'll focus on httpfs and extract_rtv for the 1-file installation method.
These instructions are not 'fool-proof' (nothing is - bigger, better, far more astounding fools come along every day). If words and phrases like 'upload', 'IP address', or 'command line' cause dizziness, uncontrollable sweating, and/or nausea then find someone else to perform this upgrade for you. (You would probably refer to such a person as 'geek', 'dork', 'nerd', or the occasional 'gimpy douchebag' - and possibly some even more colorful attributions.)Installing files with HTTPFS:
The RID file itself is VERY small (2276 bytes), but it will still occupy an entire cluster when the RTV writes it to your HDD (probably 32kb or more depending on the size of your HDD). The Photo partition (even if you never configured one) often will have at least 1 cluster allocated, and sometimes even more. This should be enough room to perform the 1-file upgrade. HTTPFS should be able to send a file to your RTV's Photo partition, even if DVArchive refuses to cooperate (this worked for my other 5K). I suppose you can even go through the post(HTTPFS)/copy(WiRNS) process 2 or 3 times if you really want to perform the 3-file upgrade with such seriously limited space considerations, just remember you may need to delete the previous file(s) before uploading more (or use '
mv -f' instead of '
cp -f' in your shellcmds). Given my sample cluster/filesize (see below) I should be able to get 2 small files (up to 196608 bytes each) at a time into my 'unallocated' Photo partition.
[
Step 1: Get the RID file into your RTV (on it's HDD) by uploading the file.]
So, for the 1-file install on a 5K (assuming "httpfs.exe" and "C0237fi.rid" are in the current directory):
--------------------------------------------------------------------------------
httpfs -a -s 520411140 writefile -f C0237fi.rid /Photo/C0237fi.rid
--------------------------------------------------------------------------------
(The -s version string may need to be changed for 4K's.)
[
Step 2: Get the RID file into your RTV's (normally inaccessible) system directory with a copy shellcmd via WiRNS or PTVIO.]
--------------------------------------------------------------------------
cp -f /name/storage/Photo/C0237fi.rid /name/system/user/mirror/sys-setup-gaea/data/irCodeset/C0237fi.rid
--------------------------------------------------------------------------
(Notice I made no 'install' directory in the first step (to preserve 1 cluster) and adjusted the final shellcmd accordingly.)
FYI, my never-configured, empty, Photo partition (in response to
http:///httpfs-volinfo?name=photo):
Quote:
0
cap=1048576
inuse=589824
and after sending only the RID file with HTTPFS:
Quote:
0
cap=1048576
inuse=786432
It appears (on my 40GB factory HDD, re-imaged once) the 2276 byte RID file consumed 196608 bytes worth of cluster(s). (I am reasonably certain it only occupies 1 cluster, but thats huge - 6 times larger than your maximum FAT32 cluster!)
Installing files with EXTRACT_RTV:[If you've ever touched the command-line, and installed or replaced/upgraded an IDE HDD in someone's computer then extract_rtv should be well within your capabilities. You may need to change the Master/Slave/Cable-Select jumper for your PC to detect the RTV HDD (don't forget to change it back!). Older machines running 2K/XP (or better) can still use extract_rtv even if the old BIOS fails to detect the RTV HDD on boot, as long as XP's 'Disk Management' snap-in (right-click 'My Computer', Manage, Storage) can properly detect the HDD within Windows then it should work. (I have one old PC that behaves this way.) Most modern OS HDD drivers will almost completely circumvent BIOS routines because they are notoriously untrustworthy.]
If I had insufficient room on my Photo partition and wanted to maintain my recordings, and given that I have a RTV 5K and use a PC, I would download the PC version of extract_rtv5.
According to its README:Quote:
USAGE: extract_rtv
...
-e extract all files
-e filename extract single file or subdirectory
...
-w filename localfile overwrite filename with localfile
...
In Windows2000 or WinXP use:
\\\\.\\PhysicalDrive0 First hard drive
\\\\.\\PhysicalDrive1 Second hard drive
\\\\.\\PhysicalDrive2 Third hard drive
\\\\.\\PhysicalDrive3 Fourth hard drive
Be
CERTAIN of your RTV HDD's
devicename when plugged into your PC! Because the RID file will be (over-)written directly onto a file within the RTV HDD's system folder you do not need to issue any shellcmds (WiRNS/PTVIO) to complete the installation.
To make a backup copy of the sacrificial target RID (assuming 1-file install)
AND to verify the correct
devicename of your RTV HDD (optional, but
highly recommended):
------------------------------------------------------
extract_rtv5 -p1 -e /user/mirror/sys-setup-gaea/data/irCodeset/C0237fi.rid
------------------------------------------------------
(It's been so long since I've used this program that I cannot recall if it accepts a target filename, or simply assumes the same filename as the source and writes it to the current directory.)
Place your RTV's original "C0237fi.rid" in a safe place, then unzip a copy of my
new "C0237fi.rid"
(DC50X).
For the 1-file install on a 5K (assuming "extract_rtv5.exe" and "C0237fi.rid" are in the current directory):
-------------------------------------------------------------------------------
extract_rtv5 -p1 -w /user/mirror/sys-setup-gaea/data/irCodeset/C0237fi.rid C0237fi.rid
-------------------------------------------------------------------------------
*OR*, depend on extract_rtv's ability to auto-detect your RTV HDD (
risky in my opinion):
----------------------------------------------------------------
extract_rtv5 -p1 -w /user/mirror/sys-setup-gaea/data/irCodeset/C0237fi.rid C0237fi.rid
----------------------------------------------------------------
(Your target RID must be at least 2276 bytes for extract_rtv to successfully replace it with with my new RID. This works fine for C0237, but you should check twice if you have changed the new RID's internal identity and filename.)This concludes today's RTFM seminar. 
Quote:
Originally Posted by
sean6484 
but you can only select two digit channels on this box even thou it goes up way above that.
sean6484,
Either you've 'fine-tuned' your IR-blaster settings to a maximum of 2 digits, or there are no clear channels above 100 in your area. Try the DTA's remote control, and remember you can't really "surf" (CH+/CH-) with that remote through all channel ranges - you need to KNOW the (clear) channel number or it will stay on the last channel tuned (clear channels are not always contiguous in the line-up).
-eslave
P.S.: Don't worry about code C0237 being replaced during a 'phone-home' connection. No new software has been produced for the RTVs in a very long time. Now, after the remnants of ReplayTV.com have been sold/acquired twice since its initial spin-off I strongly doubt that anyone within the company retains the knowledge-base or skill-set required to implement any genuine software upgrades. The last ReplayTV update was the new DST adjustment, but that was simply a registry change as I recall. There is a 'newer than factory' 5K image (for very late refurbs), but it lacks the 'Only record new episodes' option. The current owners of ReplayTV.com are only interested in guide subscriptions, viewing habits (which they likely sell), selling the PC (software) version of ReplayTV, and possibly thinking of re-implementing that blissful PAUSE screen advertising (remember?).
However, pdellera's concern has had me thinking lately that the ultimate 1-step RID upgrade option for 4K/5K users would be a tweaked, globally accessible WiRNS server that could somehow send only the new RID file as part of a 'software update', and the shellcmds would then finish the job at the end. Then only a small configuration-free WiRNS-proxy would need to run on the LAN (or even an extremely dumbed-down pseudo-WiRNS server instead of a proxy). The end-user would still need to make the RTV network adjustments (gateway/DNS) required to point at the WiRNS proxy, but all the other WiRNS configuration confusion could be left behind (like waiting 30+ minutes for it to notice your RTV before you can add it to the list.) Also, the end-user would need a mechanism (either through a remote webpage or within the LAN proxy) for identifying which RID they wanted, the desired code number, and likely their IP address so the remote WiRNS server would know which RID to send to which IP. This and many other pipe-dreams will likely be available the day after you unplug your RTV for the last time. 