Update a comment.

(Thanks for killing off a bunch of comment mechanisms, not saving the
old comments and placing them somewhere useful, and not even allowing
the Wayback Machine to archive at least some of those sites, Microsoft.)

Change-Id: Ie4258250a0176a56ee33be77604acf43c6886e0f
Reviewed-on: https://code.wireshark.org/review/31274
Reviewed-by: Guy Harris <guy@alum.mit.edu>

ui/win32/console_win32.c

@@ -139,7 +139,8 @@ create_console(void)
          * command prompt).
          */
         if (!AttachConsole(ATTACH_PARENT_PROCESS)) {
-            /* Probably not, as we couldn't attach to the parent process's console.
+            /* Probably not, as we couldn't attach to the parent process's
+               console.
                Try to create a console.
 
                According to a comment on
@@ -154,8 +155,9 @@ and
 
 http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/kb2567680-andor-kb2507938-breaks-attachconsole-api/e8191280-2d49-4be4-9918-18486fba0afa
 
-even a failed attempt to attach to another process's console
-will cause subsequent AllocConsole() calls to fail, possibly due
+(none of which are available any more, either at any obvious Microsoft site or
+on the Wayback Machine), even a failed attempt to attach to another process's
+console will cause subsequent AllocConsole() calls to fail, possibly due
 to bugs introduced by a security patch.  To work around this, we
 do a FreeConsole() first. */
             FreeConsole();