PeterH:
I guess that what you're really hoping for is some way for the sketch to work out where the bootloader code is stored and read the code to work out which bootloader it is. I'm not sure, but I suspect that the sketch doesn't have access to program memory containing the bootloader. Even if it did have access, finding and analysing the bootloader would be an extremely difficult task and I doubt that it would be practical to do this generically i.e. supporting different chip types and bootloader section sizes.
Hello, Thank you. Yes, that is my goal - to be able to ID the bootloader installed w/o doing any further modifications. My thinking is: I have an OK workaround in the code for people who just use the out-of-the-box Arduino IDE install, but really do want to be able to fully use the Watchdogs properly - which the out-of-the-box bootloader will not do. (This is a 3.3v only statement, the Uno bootloader works fine. But then, it is already an Optiboot version in the as-shipped Arduino IDE - more here: VSR Alternator Regulator: Solving watchdog non-support in 3.3v Arduinos with optiBoot).
Of course, I could simply REQUIRE people always install the Optiboot bootloader for the 3.3v version before using my sketch, but wanted to make it more user flexible and user friendly...
-al-