while driving, the new 765T decided that it would be a good time for it to "update its firmware." So, it says "updating firmware 1%" ... it says this a few times. I turned it off (I'm DRIVING and I need it to navigate...) and it seemed to be back to normal. A while later it happens again, and then I get the
"Update Complete - OK" dialog. clicked OK, and it turns itself off. Never to be heard from again. Dark. Nothing. Lifeless BRICK. I can't believe it BRICKED ITSELF WHILE DRIVING and ON THE ROAD. Spent 55 minutes on the phone (mostly waiting for a human) for them to tell me "uh, yeah its one of many reports we started receiving today." So Joy.

Garmin in their infinite wisdom decided it might *NOT* be a good idea to ship me another identical unit... so it looks like I will be getting an upgrade to a 800 series. Will see how well THIS brick works when it arrives next week...

Garmin Firmware Programmers: You're FIRED.

Messenger Chat Conversation
A: Bye
B: OK, c ya
A: L8r
B: G8r
A: lol
B:
A: ok bye
B: k, c ya
A: i'm going now
B: ok
A: bye
A: ok i really got to go.
B: ok.
<disconnected>

Chat Goodbye: FAIL.

PEOPLE. messenger is a tool for communication. Sometimes real life gets in the way of messenger time. I know, that is hard to take, but it IS reality. When it's time to go, GO. Say "bye" and then log out. Why we got to "bye" each other 7 times? Come on, we don't really have to be THAT polite, it's MESSENGER... it is a secondary form of communication... nobody is going to be insulted if you just say "bye" and log off. REALLY.

So, let me propose a new internet standard...

Messenger Sign-Off Protocol [MSOP] RFC8172
1. Protocol Semantics
    1.1 Announcement of Intent to Disconnect [AID]
        The Disconnecting Party [DP] announces that they intend to terminate the conversation and disconnect.
        Example. "I got to go. See you later..."
        Timeframe: Disconnect Timer [DT] Initiated (10 seconds)
    1.2 Confirmation of AID
        The Receiving Party [RP] must acknowledge the receipt of AID, and confirm the imminent termination of the conversation.
        Example. "OK, thanks. See you later."
    1.3 Final Intent to Disconnect [FID] (optional)
        Either party DP or RP may enter a final optional message, ONLY if possible within the DT interval.
        Example. "By the way I might be on later."
    1.4 Confirmation of FID (optional)
        Other party may enter a final optional acknowledgement ONLY if possible within the DT interval.
        Example. "OK, bye for now."
    1.5 Disconnect (EOM)
        Actually disconnect from the conversation. It's over. Go on with life now.
    1.6 Disconnect (DT expiry)
        When DT expires, disconnection is in effect, and termination occurs. Now go do something useful.
2. Disconnection
    2.1 Log-off
    2.2 Closure of chat window
    2.3 Locking of workstation
    2.4 Minimizing of chat window

Please support RFC8172 and follow the protocol for MSOP, and tell your friends.

PS Don't TXT while driving. Seriously. Or I will have to come over there and kill you.

"The connection to the Exchange server has been lost."
I am heartbroken.

"The connection to the Exchange server has been restored."
uh.. OK thanks... should I feel better now?

Up, down, back and forth... each time a new notification balloon appears above the system tray icon for Outlook. Since I positioned my command window just above the system tray, these little things cover the text I am trying to type... OK, I get that there are some problems with connectivity to my Exchange 14 dogfood server... FINE. I accepted that risk when I agreed to sign up for dogfood. The on and off again notifications are KILLING ME though and interrupting my work on the command line...

I have found a way to turn these off!
First for some flavorful keywords so your favorite search engine picks up this article...

outlook 2007 notification balloon system tray icon exchange server connection lost restored
also outlook 2003 in case you haven't joined the last half of this decade yet.

In the registry there are some keys to create that will disable these notification balloons for this specific problem of connectivity to the Exchange server.

Open registry editor and find this path:

2007: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
2003: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0

under this path, find this sub key:
\Outlook\Display Types\Balloons

there, create three DWORD values:
Exchange: DWORD (0)
NetConn: DWORD (0)
NetWarn: DWORD (0)

that's it! restart Outlook and you're FREE from the nuisance of notifications!
there are other notifications you can turn off as well, perhaps someday I will research them and post the list (don't hold your breath.)

Peace!