beautify an error message

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@14101 f5534014-38df-0310-8fa8-9805f1628bb7

1 files changed, 11 insertions, 7 deletions

diff --git a/capture_loop.c b/capture_loop.c
index dda243f68c..dbe9a7e87b 100644
--- a/capture_loop.c
+++ b/capture_loop.c
@@ -607,18 +607,22 @@ static int capture_loop_open_input(capture_options *capture_opts, loop_data *ld,
 
        Do, however, warn that WAN devices aren't supported. */
     g_snprintf(errmsg, errmsg_len,
-"The capture session could not be initiated (%s).\n"
+"%sThe capture session could not be initiated!%s\n"
+"\n"
+"(%s)\n"
+"\n"
 "Please check that you have the proper interface specified.\n"
 "\n"
 "Note that version 3.0 of WinPcap, and earlier versions of WinPcap, don't\n"
-"support capturing on PPP/WAN interfaces in Windows NT 4.0, Windows 2000,\n"
-"Windows XP, or Windows Server 2003.  WinPcap 3.1 has experimental support\n"
-"for it on Windows 2000, Windows XP, and Windows Server 2003, but has no\n"
-"support for it on Windows NT 4.0.  WinPcap 3.1 is currently in beta, so\n"
-"using it might introduce bugs not present in WinPcap 3.0; you should report\n"
+"support capturing on PPP/WAN interfaces in Windows NT 4.0 / 2000 / XP / Server 2003.\n"
+"\n"
+"WinPcap 3.1 has experimental support for it on Windows 2000 / XP / Server 2003,\n"
+"but has no support for it on Windows NT 4.0.  WinPcap 3.1 is currently in beta,\n"
+"so using it might introduce bugs not present in WinPcap 3.0; you should report\n"
 "all problems you see to the WinPcap developers, so they can try to fix\n"
 "them before the final WinPcap 3.1 release.",
-	open_err_str);
+	simple_dialog_primary_start(), simple_dialog_primary_end(),
+    open_err_str);
     return FALSE;
 #else
     /* try to open iface as a pipe */