TiVo Community Forums Archives - n00b needs your help

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

n00b needs your help
(Click here to view the original thread with full colors/images)

Posted by: Adam_M

Trying to upgrade my TiVo by replacing the original 14 gig a: with an 80 gig drive. I burned the Kazymyr's Boot Cd v2.6i image to CD using Nero. Hooked up the original a: to the second ide channel with drive set as master. My CD drive is set to master on IDE 1, hooked upgrade drive to IDE 1, 2nd in chain and set to slave. Booted off CD, go to prompt and typed ‘noswap’ and get an error that says: kernal panic: attempted to kill init! . I have and use IDE raid but unplugged the array. The BIOS and POST recognize both HDs and the CDROM. Just out of curiosity I used the other options and get the same error. I’m a total newbie to this and have no idea what may be happening. Any help would be greatly appreciated

TiVo HDR110
Hard drive is quantum

Motherboard MSI K7T Turbo raid (KT133A) Athlon

Edit: tried buring image with CDRWIN 4 as well, same thing...

Posted by: bsnelson

Try using the default instead of noswap. Also, there should have been more than just that one error message.

(and, at the risk of sounding mean, it's better to use "real" English here, e.g. "newbie")

Brad

Posted by: Adam_M

I’m away from my system so I can’t get details on the error message. As I mentioned I tried other options and got the same result. I’ll try and adhere to standard English in the future. I’m new to the forum and did not mean to rub the denizens the wrong way.

Adam M

Posted by: noise

I have run into the same error, tried burning the cd at different speeds, and tried using the default option at well. Still getting the same error. Any suggestions?

Posted by: noise

ok for anyone that cares, I removed my scsi card from the computer and that removed the error, and am at this very minute in the process of copying drive a to a new drive. perhaps this will be helpful to someone else in the future.