Initial "help" command in network control fails

[Robert Kulagowski]

mythfrontend --version
Library API version: 0.19.20060121-2
Source code version: 8808M
Options compiled in:
 linux release using_v4l using_oss using_alsa using_arts using_ivtv using_lirc using_joystick_menu using_dvb using_dvb_eit using_x11 using_xv using_xrandr using_xvmc using_opengl_vsync using_frontend using_backend


MythFrontend Network Control
Type 'help' for usage information
---------------------------------
# help
INVALID usage, try 'help' for more info
# help
Valid Commands:
---------------
jump               - Jump to a specified location in Myth
key                - Send a keypress to the program
play               - Playback related commands
query              - Queries
exit               - Exit NetworkControl

Type 'help COMMANDNAME' for help on any specific command.

[cpinkham]

(In [8811]) Print out a little more verbose error message when NetworkControl? receives an invalid command. References #1176.

RE: 1176, I think there may be garbage in the input buffer that isn't purged before reading the first command. This patch should help identify the problem.

[Robert Kulagowski]

I'm compiling now.

To reproduce, I was using putty on Windows XP in telnet mode, and connecting to the IP address and the port.

Is telnet / putty sending cruft as a part of the initial handshake to negotiate window size, etc, which is being interpreted by network control as a command?

[Robert Kulagowski]

Yep, just as I thought:

MythFrontend Network Control
Type 'help' for usage information
---------------------------------
# help
INVALID command 'ÿûÿû', try 'help' for more info
# help
Valid Commands:
---------------
jump               - Jump to a specified location in Myth
key                - Send a keypress to the program
play               - Playback related commands
query              - Queries
exit               - Exit NetworkControl

Type 'help COMMANDNAME' for help on any specific command.

#

[cpinkham]

(In [8825]) A tested fix for #1176. Tested using Putty in 'Active' mode which was the original problem case reported. Closes #1176.