PDA

View Full Version : Do's and Don'ts with HDVR2


nipquad
07-01-2003, 03:15 PM
Im starting this thread to copy the one thats on the Dtivo section. I think its a great idea to start posting little things that you should or shouldn't do when working with the HDVR2 or any series 2 for that matter. It would be nice if we could get this a sticky if it gets to be helpful. Im gonna start it with a few suggestions from my hacking expenience in the past week.

1. Always listen to Mr. Black and read his post FIRST! I can't stress enough about how helpful his thread was and it'll answer many questions you have! It's a sticky and it's not hard to find.

2. Always check the damn Null modem cable, this was kicking me in the butt over and over till I got a cable tester out and made sure it was right. It'll save you many headaches!

3. NEVER USE WINDOWS TEXT EDITORS FOR SCRIPTS. I learned this the hard way and it was the cause to most of the trouble I had with the fixsub and callsub scripts.

4. Give it some time to boot up. My HDVR2 took about 3-7 mins to boot. There were many times that when I thought it was messed up and was going to unplug it, it jumped to "almost there" and finished. Give it 10mins to be completely safe!

5. If you get "Welcome Powering Up" and then it reboots, this is normal as long as it doesn't reboot more than once. I though I had a bad image but if you let it go, after the first reboot, it may work!

Thats all I have for now, I haven't messed with locals (if possible), tivoweb, or extraction on my HDVR2. If you have, please share some tips that would help people out. It just kinda sucks when you have to have 5 threads and have to peice it together from everywhere! Thanx for all the help guys, without this forum, me and a lot of other people would be dead in the water! :D

Dr. Phil
07-01-2003, 04:01 PM
Originally posted by nipquad
4. Give it some time to boot up. My HDVR2 took about 3-7 mins to boot. There were many times that when I thought it was messed up and was going to unplug it, it jumped to "almost there" and finished. Give it 10mins to be completely safe!

Corollary: if at all possible, install a drive activity light or an ide drive cage with an activity light. With a very small amount of practice this will allow you to see how far along the boot process has gotten. Also watch the power light - it turns a funny amber-ish color for a second shortly after rc.sysinit starts.

gsxrpilot
07-01-2003, 04:20 PM
As far as rule #3, you can use texpad and save as a UNIX file, but one DO I learned the hard way was

gsxrpilot
07-01-2003, 04:21 PM
to continue...
ALWAYS DO A CHMOD 777 to your hackinit if you do modify it.

nipquad
07-01-2003, 04:47 PM
good one, just to take it a little further, ANY script that you edit to create, its always a great idea to "chmod 777 filenamehere" that script, it'll save you haveing to re-edit the rc.sysint cause of "permission denied"