Transparent Background Problem

[sbradford]

I recently upgraded my drive in my SAT-T60 from a 60GB to a 200GB drive and everything seemed to work fine. I had to shrink the image of the 60GB drive back to its original 40GB state while performing the backup. I used the following command.

mfsbackup -l 32 -6so /mnt/dos/tivo.bak /dev/hdb

This command worked fine. When I restored everything went smoothly, but when I put the drive in my TiVo my backgrounds were missing. So I tried the above command with a –l 64 instead of 32 but by changing that command my image does not get shrunken back to it’s original 40GB state so therefore I cant use it to upgrade to the 200gb because it will not expand.

So what am I doing wrong? Why will it shrink the image when I use 32 but not 64? Is there a fix for this background issue?

Thanks

[Jamie]

I recently upgraded my drive in my SAT-T60 from a 60GB to a 200GB drive and everything seemed to work fine. I had to shrink the image of the 60GB drive back to its original 40GB state while performing the backup. I used the following command.

mfsbackup -l 32 -6so /mnt/dos/tivo.bak /dev/hdb

This command worked fine. When I restored everything went smoothly, but when I put the drive in my TiVo my backgrounds were missing. So I tried the above command with a –l 64 instead of 32 but by changing that command my image does not get shrunken back to it’s original 40GB state so therefore I cant use it to upgrade to the 200gb because it will not expand.

So what am I doing wrong? Why will it shrink the image when I use 32 but not 64? Is there a fix for this background issue?

ThanksGet this (http://www.dealdatabase.com/forum/showthread.php?t=39487) package and run 'mfs_info -s' on the original drive 60GB drive. This will give you back something like:max stream fsid under /Resource: 2402
max stream size under /Resource: 16MBIn this case, it tells you'd need to use -f 2403 or -l 17 to preserve all the loopset tystreams under /Resource. Note that these values are one above the values reported by the mfs_info tool. This is the best way to find the minimal -f and -l values to use for a particular image. Try both and use whatever results in the smaller image.

If your image still doesn't "shrink" when used with either of these minimal values, it means you probably can't shrink using the existing tools without losing your background animations. Start over with a fresh image.

[Smee]

Get this (http://www.dealdatabase.com/forum/showthread.php?t=39487) package and run 'mfs_info -s' on the original drive 60GB drive. This will give you back something like:max stream fsid under /Resource: 2402
max stream size under /Resource: 16MBIn this case, it tells you'd need to use -f 2403 or -l 17 to preserve all the loopset tystreams under /Resource. Note that these values are one above the values reported by the mfs_info tool. This is the best way to find the minimal -f and -l values to use for a particular image.

Jamie,

Your a genious. I have had my Tivo hacked for a few months now and when I originally created the 4.01 image of my SD-DVR40, I made a backup following Hinsdale guide using the -f 9999 switch. Well, I bought another Tivo this past week and decided to restore that image and everthing looked like it was going well but almost toward the end when the "Your Almost There Screen" is about to switch to the aquiring sat screen, it would reboot. So I connected my laptop to the Tivo serial port and when it got to the "Starting Recorder" phase, it would get an error that said "Illegal read at 00000008". I assumed that it was a bad image I made, so again I ripped my drive out of my working Tivo and made a new image (Again using the -f 9999 as Hinsdale suggests) and restored it to the new drive. Same error. I then made a new image with -Tao. This time I got a message that the image could not fit on destination or some such. I was about to start from scratch when I got to this post.

I used the information provided by mfsinfo and added 1 to that number. I used the -f switch as that made the smaller image. I then restored it to the new Tivo drive and presto, system booted perfectly. It also backed up all the loopsets so I didn't suffer from the transparent background problem other have reported.

In short, thanks! :D

Take care...

Smee