Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by comer, Sep 20, 2010.
Another old school question... does a 32bit copy of the MFSTools iso exist? I saved an old tower PC for just this reason - easy to open and attach both drives, etc., but it's apparently too old now. I downloaded the current version of MFSTools, burned it to a USB drive but I get an error since it's a 64bit program.
I tried booting it up on a current 64 bit all-in-one HP PC (set the BIOS to boot from a USB drive first, etc.) as well as new iMac and MacBook and was going to just use a dual HDD dock and let it run, but it's not recognized by any of those machines at all.
Also tried burning JMFS to a USB drive and none of my computers recognize it. So I'm stuck trying to upgrade my TiVo Premiere XL4.
How did you burn MFSTools to the USB drive
Sorry, I flipped the application names. I should have said that the 64bit/32bit error was with MFSTools, not JMFS and that I couldn't get JMFS to boot on any of my machines. I'll update my post.
I used Universal USB installer to create the MFSTools USB ISO.
Apologies for the confusion.
Download the HDD/USB version and unpack it. Then use a program like Etcher to write it to the USB drive.
I did download MFSTools and used balenaEtcher to burn it, but received the "no partition" error. I actually modified it in Terminal to create a DMG image file, but no love that way either.
I'll take a look for the HDD/USB version. I must have missed that.
Just make sure you unpack it before burning it.
The only downloadable file I can locate is this one which is the one I used (after unzipping it) to create the USB drive - which, again, booted in the old PC, but had the 64 bit error message. Is there a different USB file somewhere?
Normally the CD ISO would have been fine, but the CD/DVD drive in my old tower PC has apparently given up the ghost and why I'm trying to boot from a USB drive. I can pick up a cheap DVD drive if needed.
Thanks so much!
You did not download the one from my post in MFSTools 3.2 thread?
Still searching. Do you happen to have the link? Thanks!
In post 8 of the MFSTools 3.2 thread has a link
Ah, got it... ultimately this file - MFSTools 3.32-devel USB/HD from this thread?
If so, yes, I believe that was the first one I tried, but I'll give it another try.
Just tried that file and am getting the balenaEtcher "Missing Partition Table" error.
Can you use dd to copy it to the USB drive?
I will give that a try! Thanks!
Unfortunately I'm back to square one. Used dd to copy/create the iso on a USB drive. MFSTools will initially boot up on the old PC but gives me the "64 bit program vs 32 bit computer" error. It doesn't boot up at all on the newer PC or Macs.
Thanks so much for all of your time on this... far too much for what I'm trying to accomplish. But if you think of something else that I can try, let me know, I'm all ears. Otherwise, have a great weekend!
Can you disable EFI booting on your newer computer or enable legacy booting or compatibility mode?
Well, by gosh, that worked (on the newer PC of course)! Had to disable secure boot and enable legacy boot mode in the BIOS, and THEN get into the boot device menu to tell it to boot from the USB drive, but now it's sitting at the MFSTools login screen. So fingers crossed I should be good to go. I'll post back with the (hopefully) positive results.
Thanks again! I owe you big time!
Moved post about my Premiere HDD upgrade fail here since it was with MFSTools and not JMFS.
I recently had a Premiere drive GSOD on me and used JMFS to copy, expand, and super size a working Premiere 320 GB drive to a 2TB drive. I installed the new 2 TB drive after executing these three steps and booted up the Premiere. However, during the boot up, I got a message that the external disk drive was missing i.e. TiVo expected that there was an external drive linked to the internal. This obviously was not the case, so I followed the prompts to disassociate the nonexistant external drive and reboot. When it rebooted, TiVo booted into its OS, but it only showed 75 hours of HD recording space. It is as if the expand step did not take correctly.
I was just wondering if any of you have heard of or experienced this behavior previously and / or have any recommendations. I will try and expand it again this weekend, but if you have any advice or suggestions, I would appreciate any input you might have.
I had that happen. I just went back and expanded/supersized again and it worked properly the next time.