HR10 won't record...

[ursa99]

Been away from this for awhile so please be kind....:)

I did a new installe of 6.3b-01-2-357 on my HR10-250 with a CD built using zipper_isomaker with all the hacks. All installed fine and I can telnet and connect via Tytool. All seemed well...except I"m unable to record anything. The HR10 won't record. Any ideas where I may have gone wrong?

[ursa99]

Upon further review...I also found an error 51 hardware prob. I think a clear and delete everything may fix it. Trying that now...

[litzdog911]

Yep, needs a "Clear and Delete Everything".

[dbaile]

I have the HR10-250 that I recently deactivated and am using only as an OTA receiver. Is there any way to return the RECORD function to the tuner without activating through DTV?

[ursa99]

Did a clear and delete and it no longer shows error 51 and it is now insisting on making a phone call to the DRV service before I can record. I have a legit sub and made the call but it continues to fail while negotiating. This recorder has made successful calls quite recently....

This HD is for testing purposes so I may just start over and rebuild it...during the last install it asks for the Service # which the instructions say are the first 3 numbers of the Serial #. My serial # starts with two letters and then a number. I also have a DVR service # which I used because the install S/W wouldn't accept letters and numbers....

Question: Should I use the first 3 real numbers in my serial #? The first 3 digits of my serial are KA5xxxxxx

Thanks for any help.

[temp357]

If you run CDE on a hacked drive it will most likely wipe out all of the networking as well. Did you run the tweak.sh on the drive?

[Da Goon]

If the drive is hacked, a clear and delete is unnecessary. Since you've already done it, run fakecall.tcl and reboot, and the phone nag screen should go away.

[ctbl44]

I also have this same problem on a new drive, I used Zipper 2.7a on a new drive at 6.3b, installation goes smoothly but before I can record any programs, the HR10 wants to make that initial call. There are no error #51 or any messages.

I have run Fakecall several times and each time it reports as being successful. It is also run on reboot as well. Looking at the System Information screen confirms that the Fakecall data is current and listed as successful. I have also manually run 51killer as well to no avail.

I finally decided to run through the entire installation program again to see if anything was missed, but I still get the same result. Any suggestion or help would be appreciated.......................