#504 USABILITY: There should be a small message before the debugger's Bochs prompt that the c key must be pressed

[Oliver]

If Bochs was compiled with the --enable-debuggeroption and the debug GUI is not used, then after starting the simulation, Bochs should also inform the user and output a message before the <bochs:1> prompt that to continue the simulation, he should press the lower case "c" key for continue and lower case "q" key for quit.
The user should also be informed that he can get more information by entering "help" after the <bochs:1> prompt.

Example:

1. Restore factory default configuration
2. Read options from...
3. Edit options
4. Save options to...
5. Restore the Bochs state from...
6. Begin simulation
7. Quit now

Please choose one: [2] 6
00000000000i[      ] lt_dlhandle is 0x56128d890d60
00000000000i[PLUGIN] loaded plugin libbx_sdl2_gui.so
00000000000i[      ] installing sdl2 module as the Bochs GUI
00000000000i[SDL2  ] maximum host resolution: x=1920 y=1080
00000000000i[      ] using log file output.txt
Next at t=0
(0) [0x0000fffffff0] f000:fff0 (unk. ctxt): jmpf 0xf000:e05b          ; ea5be000f0
<bochs:1> 

<bochs:1> help
h|help - show list of debugger commands
h|help command - show short command description
-*- Debugger control -*-
    help, q|quit|exit, set, instrument, show, trace, trace-reg,
    trace-mem, u|disasm, ldsym, slist
-*- Execution control -*-
    c|cont|continue, s|step, p|n|next, modebp, vmexitbp
-*- Breakpoint management -*-
    vb|vbreak, lb|lbreak, pb|pbreak|b|break, sb, sba, blist,
    bpe, bpd, d|del|delete, watch, unwatch
-*- CPU and memory contents -*-
    x, xp, setpmem, writemem, crc, info,
    r|reg|regs|registers, fp|fpu, mmx, sse, sreg, dreg, creg,
    page, set, ptime, print-stack, ?|calc
-*- Working with bochs param tree -*-
    show "param", restore
<bochs:2> 

To continue the simulation, c must be entered:

<bochs:1> c

[Stanislav Shwartsman]

Done