Stephen Warren wrote: > Stephen Warren wrote: >> See attached... >> >> I also just validated (with a clean CVS checkout/build) that starting >> with a working remote, forcing it into safe-mode, and updating with >> "--direct -F file" causes the same problem:-( >> >> I also captured the USB logs in Windows updating to the latest firmware. >> I'll analyze them and see if I can see anything weird. > > The USB logs from a Windows firmware upgrade don't look particularly > special; it seems to match the version Kevin previously captured, except > that the latest Windows code reads a bunch of flash/state before the > upgrade, which I don't imagine is relevant. > > Anyway, I've attached the decoded Windows upgrade USB log just in case > you can see anything I've missed.
I dropped you an email offline - I see exactly what's wrong. I'll get you a patch. If you're curious, dump the firmware using -f, and then compare that file to the file the site gave you and you'll see the difference in format. -- 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
