No problem. The length of the bootloader wait is set by the MAX_TIME_COUNT constant which is defined in the Makefile (in the ng: or diecimila: targets). In both cases it's based on the F_CPU constant that corresponds to the clock speed of the microcontroller (16 MHz in the case of Arduino). The code that uses the MAX_TIME_COUNT constant is the getch() function, which waits for character input from the computer. If it doesn't receive a character in the right amount of time, it calls app_start() which jumps to the beginning of the sketch on the chip. There's also a "timeout" after receiving a certain number of errors, or data that doesn't fit the bootloader protocol (stk500). The error count is incremented anywhere the bootloader receives a byte that doesn't conform to the protocol.
So, if I understand correctly, and don't want to get too involved, I take the statetment
and vary the ">>1" so I have the option of altering it by powers of 2, so
F_CPU>>0 - doubles the timeout
F_CPU>>2 - cuts the timeout in half
and so on ... I did actually try it and it does indeed seem to work that way, I used
F_CPU>>3 - and the timeout did seem to be about a quarter of what it had been
... once again, thanks ... cheers ... BBR