Merge remote-tracking branch 'origin/GP-4617_Dan_debugLauncherImprovements--SQUASHED' into Ghidra_11.1

Ghidra/Debug/Debugger-agent-dbgeng/data/debugger-launchers/local-dbgeng.bat

@@ -1,21 +1,20 @@
 ::@title dbgeng
 ::@desc <html><body width="300px">
 ::@desc   <h3>Launch with <tt>dbgeng</tt> (in a Python interpreter)</h3>
-::@desc   <p>This will launch the target on the local machine using <tt>dbgeng.dll</tt>. Typically,
-::@desc   Windows systems have this library pre-installed, but it may have limitations, e.g., you
-::@desc   cannot use <tt>.server</tt>. For the full capabilities, you must install WinDbg.</p>
-::@desc   <p>Furthermore, you must have Python 3 installed on your system, and it must have the
-::@desc   <tt>pybag</tt> and <tt>protobuf</tt> packages installed.</p>
+::@desc   <p>
+::@desc     This will launch the target on the local machine using <tt>dbgeng.dll</tt>.
+::@desc     For setup instructions, press <b>F1</b>.
+::@desc   </p>
 ::@desc </body></html>
 ::@menu-group local
 ::@icon icon.debugger
 ::@help TraceRmiLauncherServicePlugin#dbgeng
-::@env OPT_PYTHON_EXE:str="python" "Path to python" "The path to the Python 3 interpreter. Omit the full path to resolve using the system PATH."
+::@env OPT_PYTHON_EXE:str="python" "Python command" "The path to the Python 3 interpreter. Omit the full path to resolve using the system PATH."
 :: Use env instead of args, because "all args except first" is terrible to implement in batch
 ::@env OPT_TARGET_IMG:str="" "Image" "The target binary executable image"
 ::@env OPT_TARGET_ARGS:str="" "Arguments" "Command-line arguments to pass to the target"
 ::@env OPT_USE_DBGMODEL:bool=true "Use dbgmodel" "Load and use dbgmodel.dll if it is available."
-::@env WINDBG_DIR:str="" "Path to dbgeng" "Path to dbgeng and associated DLLS (if not Windows Kits)."
+::@env WINDBG_DIR:str="" "Path to dbgeng.dll directory" "Path containing dbgeng and associated DLLS (if not Windows Kits)."
 
 @echo off
 

Ghidra/Debug/Debugger-agent-dbgeng/data/debugger-launchers/local-ttd.bat

@@ -1,21 +1,20 @@
 ::@title ttd
 ::@desc <html><body width="300px">
 ::@desc   <h3>Launch with <tt>ttd</tt> (in a Python interpreter)</h3>
-::@desc   <p>This will launch the target on the local machine using <tt>dbgeng.dll</tt>. Typically,
-::@desc   Windows systems have this library pre-installed, but it may have limitations, e.g., you
-::@desc   cannot use <tt>.server</tt>. For the full capabilities, you must install WinDbg.</p>
-::@desc   <p>Furthermore, you must have Python 3 installed on your system, and it must have the
-::@desc   <tt>pybag</tt> and <tt>protobuf</tt> packages installed.</p>
+::@desc   <p>
+::@desc     This will launch the target on the local machine for time-travel debugging.
+::@desc     For setup instructions, press <b>F1</b>.
+::@desc   </p>
 ::@desc </body></html>
 ::@menu-group local
 ::@icon icon.debugger
 ::@help TraceRmiLauncherServicePlugin#dbgeng_ttd
-::@env OPT_PYTHON_EXE:str="python" "Path to python" "The path to the Python 3 interpreter. Omit the full path to resolve using the system PATH."
+::@env OPT_PYTHON_EXE:str="python" "Python command" "The path to the Python 3 interpreter. Omit the full path to resolve using the system PATH."
 :: Use env instead of args, because "all args except first" is terrible to implement in batch
 ::@env OPT_TARGET_IMG:str="" "Trace (.run)" "A trace associated with the target binary executable"
 ::@env OPT_TARGET_ARGS:str="" "Arguments" "Command-line arguments to pass to the target"
 ::@env OPT_USE_DBGMODEL:bool=true "Use dbgmodel" "Load and use dbgmodel.dll if it is available."
-::@env OPT_DBGMODEL_PATH:str="" "Path to dbgeng & \\ttd" "Path to dbgeng and associated DLLS (if not Windows Kits)."
+::@env OPT_DBGMODEL_PATH:str="" "Path to dbgeng.dll & \\ttd" "Path containing dbgeng and associated DLLS (if not Windows Kits)."
 
 @echo off