Phil Dibowitz wrote: > Hmm. What might be interesting is doing an upgrade with the official > software and then doing a dump of the 'scratch' space. I suspect *part* of > the transmogrification is happening in the software but part is happening on > the remote. If we can remove all of the noise from the changes the remote > makes when it copies it, that may make this vastly easier. > > Maybe I'll do that tonight if I get a chance.
WOO! I got it. Well, sorta. It's not nearly as bad as I thought it was - that was just the difference between the the firmware data in the file the site gave Stephen and the firmware in the file the site gave me. I don't understand why they're difference since both remotes end up the same, but whatever - they're not the same. I had assumed they were the same since the results were the same and thus had lots of diff that wasn't necessary. All it takes is updating the first 6 bytes. If I take a file from the website, update the first 6 bytes with the first 6 bytes of my firmware and then use it to update my remote, it works like a charm. That makes this pretty easy. I should have a patch whipped up shortly. -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
