Ok, As some of you may know, I've been doing some digging into the R15 just cuz I want to know. For those of you that are as curious as I am as to how things "might" work, the following is what I may or may not have found. It has been reported here and referenced over at DealDatabase.com that another user had performed a Unix "dd" copy of a drive from an R15 to a blank drive, inserted it into the R15 and it booted and ran without any noticed problems. I have tried the same and can verify this. I did not run into any problems with a new copy of the original drive in the R15. Maybe at least a backup method for those that don’t want to loose their MYVOD. Keep in mind this does involved pulling the drive from your R15, placing it in a PC, booting a version of Linux and performing a dd copy. I have been looking at the filesystem utilized by the R15 and it is tagged as a FAT32 partition. Mounting that partition on a Linux system works and one can browse through the drive seeing all files and directories. Appears to at least be FAT32 compatible. The "files" under the root directory of the drive are few and most are coded as "system" files. They are as follows: Code: -rwxr-xr-x 1 root root 3130196 Mar 24 2034 jopa* -rwxr-xr-x 1 root root 1816 Feb 17 18:47 pcredit.dbf* -rwxr-xr-x 1 root root 4976 Mar 24 2034 pman.dbf* -rwxr-xr-x 1 root root 239202 Feb 17 16:25 signup.dbf* -rwxr-xr-x 1 root root 16104 Mar 24 2034 supp.dbf* -rwxr-xr-x 1 root root 52292 Mar 24 2034 xcatgry.dbf* -rwxr-xr-x 1 root root 4346 Mar 24 2034 xclient.dbf* -rwxr-xr-x 1 root root 532 Feb 18 15:51 xsetup.dbf* As shows are recorded a set of files, associated with each show are stored in a directory under the root directory. So each show that you may have in your MYVOD equates to a directory under the root directory. This concerned me as to the known limitations with a FAT32 filesystems. The files within this directory are all named the same and the directory name is meaningless. For example: Code: 12: total 747776 -rwxr-xr-x 1 root root 8928 Feb 18 00:00 meta_man.xm\001* -rwxr-xr-x 1 root root 705 Feb 18 00:00 meta_man.xmd* -rwxr-xr-x 1 root root 20170 Feb 18 00:00 meta_man.xmi* -rwxr-xr-x 1 root root 11993 Feb 18 00:00 meta_man.xmv* -rwxr-xr-x 1 root root 0 Feb 18 00:00 stream.ext* -rwxr-xr-x 1 root root 765591552 Feb 18 00:00 stream.str* In this example the directory name is 12. As in c:12. From the file sizes the “stream.str*” would seem to contain the video stream. On the backup drive I created I tried the DOWN ARROW/RECORD method. The R15 did come back quickly with a drive minus all shows and SLs. I'm working further on the filesystem as there can be no way DTV would have used a FAT32 filesystem for this product. I have some clues it may be more a FAT64 file system with compatibility backward to FAT32. Allowing file sizes > 4GB and partition sizes up to 2TB. Very interesting stuff. But this is all just me being curious. If any of you are also curious, jump in. I would love to hear your observations.