Whether I click ADD or drag a video file into Toast 8.0.3 I get this message:
Couldn't complete the last command because there is a problem decrypting the file. In order to use TIVO files, you need to first enter your Media Access Key in the preferences dialog of the TIVO TO Go application.
Result code = -20000
I recently upgraded to Mac OS x 10.5.2; the MAK is properly entered in Tivo Transfer; Tivo transfers are enabled.
Is there separate software for TIVO to go? Does it require separate activation? Is it different from Tivo Desktop 1.9.3.008, or Toast 8.0.3?
Previously, things had been functioning fairly successfully.
Advice? Suggestions?
Many thanks!
Toast 8.0.3 Doesn't Work With Tivo Transfer
Started by
toasty8
, Feb 23 2008 11:38 PM
3 replies to this topic
#1
Posted 23 February 2008 - 11:38 PM
#2
Posted 25 February 2008 - 11:57 AM
trash TiVo transfer then run Toast Setup Assistant. Run TiVo Transfer again to enter you MAK and see if it works for you.
#3
Posted 02 March 2008 - 09:22 PM
QUOTE (gaper1 @ Feb 25 2008, 11:57 AM) <{POST_SNAPBACK}>
trash TiVo transfer then run Toast Setup Assistant. Run TiVo Transfer again to enter you MAK and see if it works for you.
This had no effect on my setup. I had been using TiVo transfer just fine previously. But now in Mac OS X 10.5.2, I am being told my MAK is wrong. It is correct. It worked before. Deleting and reinstalling TiVo Transfer did not help.
This is the only reason I bought Toast. Roxio, please make this work reliably, very soon, and keep up with system updates from now on!
#4
Posted 02 March 2008 - 09:31 PM
QUOTE (Jim Elliott @ Mar 2 2008, 09:22 PM) <{POST_SNAPBACK}>
This had no effect on my setup. I had been using TiVo transfer just fine previously. But now in Mac OS X 10.5.2, I am being told my MAK is wrong. It is correct. It worked before. Deleting and reinstalling TiVo Transfer did not help.
I spoke too soon. It seems that the shows I transfered after upgrading are problematic, but if I delete them and transfer them again after reinstalling TiVo Transfer, it is working again for now. Still, I have little confidence in the stability of the product.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users





