Thanks Scott, The error appears to be misleading, well perhaps. As you note, the patchstick is not getting executed, so that got me to wondering why. Interestingly enough when I went to do another boot with the USB connection, but this time with a hub (used so that I can access a keyboard), my ATV went right back into ATV. It did not boot into the atv-patchstick. This got me to wondering about my USB setup. As you point out, some USB devices can be a little slow and having a 1.1 version USB hub added to the mix dos not help. I also had some USB extender cables to make working with the setup more convenient.
In short, I cleaned up the USB cabling to eliminate possible losses and things appear to have moved along now. Well, I think they have. The screen appeared to be stuck on a command in the patchstick for the first mount but after a long time period t moved t the next step. This could be of my own doing since I modified the "sleep 1" values in the "Patchstick.sh" file to "sleep 1000". My expectation though was that the sleep increments are 1 millisecond (given the "sleep 10000" setting at the end of the file) so I simply made it wait 1 second. Apparently not, so now I have a longer wait (if "sleep 1" is 1 second then I have ~17 minutes for each of the three spots that I modified). -- To post to this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/atv-bootloader?hl=en
