bootldr performed erase/write after aborted transfer (!)

I just experienced the following:

        load root
        # navigate painful minicom file selection dialogs
        # see a bunch of timeout message since I'm too slow

At this point I expected to see the customary "..." sequence which I
could then interrupt and redo the "load root", but instead I got:

        boot> load root
        loading flash region root
        using xmodem
        ready for xmodem download..
        Erasing sector 00140000
        Erasing sector 00180000
        Erasing sector 001C0000
        ...

Of course, no harm done to my system in this case, but I was quite
surprised to see it flash something after the file transfer was
unsuccessful. Is this a new bug?

I would hope that the "load bootldr" command has enough extra tricks
so that if this were a new bug it still wouldn't cause problems there.

-Carl

-- 
Carl Worth                                        
USC Information Sciences Institute                 cworth_at_east.isi.edu
3811 N. Fairfax Dr. #200, Arlington VA 22203		  703-812-3725