Well I just attempted to perform this upgrade on my stock HDVR2. The HDVR2 has been in the system for some time and has not been modded.

Peformed dd to image onto a new WD160gig drive and tested the image (after the first attempt to use the upgrade disk) in the HDVR2. It works fine.

First I installed the drive as secondary master and had my CDROM as Primary slave, nothing else. I did this because the source drive was Primary master during the dd.

I got an odd message about "too many mount points (ff)", or some such, in the boot log. And the tivo drive would not mount at all. I even attempted the mfs_ls and got a message about unknown filesystem etc.

This is where I tested the drive in the HDVR2 for the first time, and it worked fine.

I decided to play it safe and place the hd as primary master and the cdrom as primary slave, and your boot disk saw it just fine this time. I ran the install script as configured above (no cake etc.) and got the bad flags messages.

I performed:
/#mfs_ls /SwSystem
1914649 tyDb 3.1.1e-01-2-151
2377966 tyDb 6.2-01-2-101
....
1914649 tyDb ACTIVE

Summary:
Another instance of a half installed 6.2 is also broken, and you should look at your scripts when cdrom is hdb and TivoA is hdc (single drive install). Hmm what now...

--tensor

Moving the private messages into public thread to continue conversation
=====================================================

I have already done the mfsbackup, and did a restore to another drive as a test. The script ran fine. I can still give you a mfsbackup if you need.

Now the new drive appears to work, but no internet dhcp request on my wg111 netgear usb wireless. Also, the script did not run mfsadd so I pulled the drive back out, used your mfsadd (ctrl-c out of script) and it is just reporting 120 hours in tivo menus (147 hours from mfs add). I'm looking for some indicators the script actually did something :-)

--tensor

ok - so wait, you did a backup and a restore to anther drive, and then there were no errors when the PTVnet scripts ran without errors?

As for the wireless issue - you need a USB 2.0 adapater, like the Linksys USB200M. There are no native wireless drivers (see product notes for more information on wireless stuff).

If you want to verify that the script DID do something, do a bootpage -p /dev/hdc to see what your active partition is (eg /dev/hdc4 or /dev/hdc7) then do a:

mount /dev/hdc4 (or /dev/hdc7) /mnt/tivo

and take a look for these directories and files:

test.conf
/ptvupgrade
/init

Then you'll know that things got installed (and all you need is the right network adapter...).

The thing that stinks about this (although its good to know) is that the script aren't working on an ORIGINAL drive - or a literal copy of one. An mfsbackup/restore does appear to work, even with a half-breed system; that isn't necessarily bad, but I'd like to be able to replicate the situation.

What I hate to say is that I might have to put my marketing hat on here and say that this is a GOOD thing, because it will prevent folks from potentially botching their original drives (less of a chance of folks doing a DD like you and more of a chance of them just using their original drive, right?).

We should really take this part of the conversation public, so others can see and chime in...

--tivoupgrade

All in all, this is a strange (and hopefully rare) situation. Note that TWO people have had this problem, and its been for the same reasons -- a half-breed system where the original drive (or a LITERAL DD COPY) is being used.

One thing I will do, for sure, is add some information to the product overview to indicate that its likely that the PTVnet scripts will NOT work on an original drive (or a DD copy). Perhaps that can be spun into more of a theme of "you wouldn't want to use your original drive anyway..."

For answers to commonly asked questions, please refer to the
InstantCake Instructions and Release Notes,
Official InstantCake Discussion Thread, and the
Official PTVnet Discussion Thread

tensor said:

I have confirmed the files exist on the upgraded drive. I will head out to buy a usb wired ethernet device.

Should tivo be reporting more than 120 hours on a 160 gig drive?

--tensor

For answers to commonly asked questions, please refer to the
InstantCake Instructions and Release Notes,
Official InstantCake Discussion Thread, and the
Official PTVnet Discussion Thread

Okay, so the 3.1.1e related version of PTVNet is availble as a general release. I've found it works perfectly with your InstantCakes on the 'select' models, but I had that same problem where the script cannot find files with my previously 'virgin' image. My virgin image is one of those that has the 6.2 (call it dormant) with 3.1.1.e still active.

The reference page found here says that a 6.2 supported version of PTVNet will be available soon.

" PTVnet Software CD for Select DVR systems running 6.2 (coming soon) "

Will there be an opportunity to beta test this version? I'd like to be on that list too!

FYI, per D*, the 6.2 has already been distributed to the LA area, the rest of the country is slated for April 7th. Guess that's when a lot of people will be busy. :)

OK, so I ran the above commands & it listed all 6 of the download versions, with the 3.3.1e still active. I then tried the phone connection many times, still no update.

1. Is there any available info on 6.2? Any new features? There does not seem to be any info on this or other forums.

Edit: I found the 6.2 info, so forget #1.....

2. Is there an ETA for the new PTV upgrade disk yet? (Edit) I just bought the 3.1.1e disk on the 19th, but since it looks like it won't work, can I get the new 6.2 disk when it is released?

What if 6.2 is installed

I'm having the abort problem, however, my unit says that 6.2 is installed and running. I did a MFStools copy to keep my programming and it won't take the PTVupgrade.