6.3e / 6.4a problems on SD DirecTV TiVo systems - suggested workarounds

[dannchurch]

Originally Posted by Lou Jacob

Please see the first post of this thread; those are the options we are recommending.

I am in this boat too. I have an existing DVR40 which I've previously used MFSTools on to replace the original hard drive with a 120GB drive. This DVR is running 6.3f currently. I just got another DVR40 which I'm planning to upgrade to a 250GB drive with PTVNet and InstantCake.

I really want to have both systems at 6.2a so I can use MRV but don't see how to downgrade my existing system without losing all my current recordings. Any way to use the InstantCake 6.2a version to downgrade my existing system without wiping the drive?

	MFStools MFStools is a linux utility developed by "Tiger" many years ago. It is a command line tool often run from a linux boot CD and it can be used to backup and restore a TiVo image, as well as manipulate the partition system of drives during the upgrade process.

[Lou Jacob]

Originally Posted by dannchurch

I really want to have both systems at 6.2a so I can use MRV but don't see how to downgrade my existing system without losing all my current recordings. Any way to use the InstantCake 6.2a version to downgrade my existing system without wiping the drive?

Unfortunately, you can't downgrade the OS (in place). And the use of InstantCake will, by definition, erase anything on the hard drive.

[dannchurch]

Thanks for your prompt reply Lou. I think I'll have to do in a "phased" approach then. Let me know if any of these steps don't seem right:

1. Install PTVNet progs on my existing DVR40.
2. Install MFS_FTP on this box
3. Backup my current recording to my PC in .tmf format
4. Install 6.2a/PTVNet progs on that box using the PTVNet/InstantCake method
5. Re-install MFS_FTP on the box
6. Record a show (in order to have a copy of the "old" schema in case the schema changed)
6a. If the schema has changed, insert the old schema/xml into my existing recordings (as I've seen documented elsewhere)
7. Restore my recordings onto the box using MFS_FTP

I realize that I won't have any of my wishlists/settings/etc transfered over in the process but at least I should be able to keep the recordings.

--Dann

[Lou Jacob]

It is still not clear to me whether the currently rolling out 6.4a offers the stability and functionality we consider before doing any development that fundamentally relies on it. Until I see more evidence to support the notion that 6.4a offers compelling functionality or stability over 6.2a, we are going to stick with 6.2a as our recommended platform for the SD (and 6.3f for the HD) platforms for three reasons:

1) 6.2a is stable
2) 6.2a contains embedded functionality for support of MRV which is of interest to people who want to make additional modifications beyond what we currently offer with PTVnet
3) we do not consider the additional functionality offered by 6.4a to be compelling - although a recently deleted folder is a nice feature, it is simply that.. nice. as for remote scheduling, that can currently be done using GoToMyDVR if you've chosen to network your unit.

This is not to say that we won't eventually migrate our products to 6.4a, or a later version of 6.4 at some other time, however we are currently waiting to see if the quality is truly there before we put any major efforts into this.

Thanks,

Lou

[Rick Travis]

What if any problems have you encountered with 6.4a. I have a friend who told me 90% of all TiVo problems were hard disk related. I am only interested in SD Directv TiVo Series 2 which I believe you are neglecting. We would like to see an update or the reasons you are ignoring us.

[Lou Jacob]

Originally Posted by Rick Travis

What if any problems have you encountered with 6.4a. I have a friend who told me 90% of all TiVo problems were hard disk related. I am only interested in SD Directv TiVo Series 2 which I believe you are neglecting. We would like to see an update or the reasons you are ignoring us.

I have seen no problems, personally.

You are not being ignored, and even if we had the resources allocated to begin development of products based upon 6.4a, we have not yet received the updates; so its a moot point.

I do stand by my previous assessment and recommendation; 6.2a works fine, and offers more value and stability for the time being; once we have a better understanding of 6.4a, we'll certainly look at it more closely.

Lou

[Rick Travis]

Thanks, some of us are not hackers and only want a correctly working current unit. Instantcake is a great product and you are to be congradulated for the high level of support you give it.

[Lou Jacob]

Originally Posted by Rick Travis

Thanks, some of us are not hackers and only want a correctly working current unit. Instantcake is a great product and you are to be congratulated for the high level of support you give it.

Thx. Remember, there is no reason you cannot use the current version of InstantCake (or a replacement drive kit) to repair a failed unit. Even though it is based upon 6.2a, if your unit is authorized for the update to 6.4a from DIRECTV, it will simply update within a few days of being put into service.

[sgtmaj27]

I purchased the InstantCake and companion PTVnet for an SD-DVR40 (6.4a). Both installed OK and the unit runs fine with the exception of some the PTVnet changes. I did purchase the proper software, SW-ICAKE-S2DT-DL-351 and SW-PTVNET-DL-351. However, the software version last three digits in the menu is 151. The Service number in menu is 351 which matches the service number on the unit. According to available info all of these numbers should match.

Additionally, (and maybe related to the above) I have a problem in the rc.sysinit.author file. Although all of the flags are properly present in the /init folder (CALL_OFF etc), nothing loads from rc.sysinit.author except dhcp_enable and dhclient. A PS command does not show any of the other services from rc.sysinit.author running.

To get crond to load and run the fakecall at startup, I edited the rc.sysinit.author file to include those commands and placed it right after the set Path command. At least now the fakecall resets at reboot and runs each day at the time set in the /var/spool/con/contabs/root file.

Don't know if my problems are related to the Software version not matching the Service number. Any thoughts on the wrong SW version/Service number and problems running the rc.sysinit.author

Thanks for any help/suggestions

[Lou Jacob]

Originally Posted by sgtmaj27

I purchased the InstantCake and companion PTVnet for an SD-DVR40 (6.4a). Both installed OK and the unit runs fine with the exception of some the PTVnet changes. I did purchase the proper software, SW-ICAKE-S2DT-DL-351 and SW-PTVNET-DL-351. However, the software version last three digits in the menu is 151. The Service number in menu is 351 which matches the service number on the unit. According to available info all of these numbers should match.

Things changed with 6.4a, but you are fine. Basically, there was a code merge so the last three digits for HDVR2 / SDDVR will now match (and so will DSR7000 / DSR704, and RCA DVR39 / DVR40)

Additionally, (and maybe related to the above) I have a problem in the rc.sysinit.author file. Although all of the flags are properly present in the /init folder (CALL_OFF etc), nothing loads from rc.sysinit.author except dhcp_enable and dhclient. A PS command does not show any of the other services from rc.sysinit.author running.

To get crond to load and run the fakecall at startup, I edited the rc.sysinit.author file to include those commands and placed it right after the set Path command. At least now the fakecall resets at reboot and runs each day at the time set in the /var/spool/con/contabs/root file.

Don't know if my problems are related to the Software version not matching the Service number. Any thoughts on the wrong SW version/Service number and problems running the rc.sysinit.author

Thanks for any help/suggestions

Unrelated. From what I can recall, those services do not run constantly, so a PS isn't going to show them. Fakecall will run at startup, but it just runs every now and again in a loop with a long interval between runs; I don't recall using cron for that. Not exactly sure what problems you are having, though.