Originally Posted by jraivala
My problem is I can't get one of my units to accept a firmware update.
Mfg. date of May 2010 and ReMfg date of 3/17/2011
It came with Ver. HD6A269718H1E
I have tried to update previously to Ver. HD6A26972AH1E with no success.
Yesterday I tried to update to Ver. HD6A269727V1E also wit no success.
I have been able to successfully update my other MDR513 as well as my older H2160A on both occasions.
All it does is loads then ejects the disc and says please insert disc at the point where the F-UP should begin counting the percent completed.
ANY help would be greatly appreciated.
i've got a thought or 2, here, that might apply, but it will be difficult to tell if i'm correct or not...
while this may not apply directly to our machines, when a firmware package is used to update a device, such as our machines, and the process stops like this, with the clue that the drive door opens and the thing asks for a disc, it could indicate a corrupt update file, a file of incorrect size, or an inability to actually locate the file...
think of it as the machine saying one of the following when the drive door suddenly opens up -
1 - hey, i can't find the update file
is it the correct name, including the .mot extension ?
2 - hey, i can't find the update file
is the file stored in the disc's ' root directory ' , as opposed to being stored in a sub-folder ?
3 - hey, i started loading the update file, but i didn't get ALL of it
is the file the correct exact file size ?
4 - hey, i started loading the update file, but it's too big
same as 3, is the file the correct exact file size ?
5 - hey, i started loading the update file, but its CRC does not match
hard one to confirm, but typically similar to 3 or 4 above...
my guess is that if the display makes it to F-UP, it has probably found the update file ( proper name and in root directory ) but there is something wrong with it; either size or 1 or more corrupt bytes, or a bad CRC check.
just a wild guess, here, but it might be good to verify the exact file size...
even if the size is correct, i might try downloading the file once again, to ensure that the download, itself, did not introduce some sort of gremlin in the mix.
I have successfully loaded HD6A269727V1E.mot using the download that i have... this file is exactly 12471283 bytes in size...
the size of this file on my computer hard disk is 12472320 ( slightly larger to allow for a cluster based byte boundary as stored on the disk )....
the size of HD6A269727H1E is the same ( as above )
you might want to confirm these sizes ( more important one is the exact size, rather than the ' size on disk ' ...
one last note. when a file is stored on a computer's hard disk, it is stored in chunks of 128 bytes ( or even larger, depending on your computer's disk cluster size ), making the file size a bit larger than the exact file size ( in our case, here ). the balance of the data that fills up the leftover bytes ( to make the cluster sized byte boundary ) is usually NOT initialized when the file is stored. this can result in some number of random bytes at the end of the update file.
this fact may play havoc with our machines, as we don't know exactly how the machines read the update file. could be in 128 byte chunks, 256 byte chunks, exact file byte count ( byte for byte ), etc...
it's easy for the software folks to make ' standard ' assumptions, sometimes, as to how the ends of files are treated and stored, but to not think about something that might, in their minds, be non-standard.
soooooooo ( sorry for lengthy exaplanations ) i would suggest the following -
1 - confirm the exact file size as stored on your computer hard disk...
2 - if possible, FORMAT a USB flash drive with a FULL FORMAT, to initialize all bytes on the flash drive... any old flash drive should work.
3 - copy the Funai update file over to the flash drive...
4 - burn your update CD-R using the file in the flash drive as the source...
this SHOULD guarantee that there is nothing at the tail end of the update file causing the Mag to get confused...