Ok, I'm going to reply to my own post here. :-) I figured out what the problem was. On the Setup | Communications | Windows Socket setup screen Telnet tab there's a "Break Signal" and that was set to "Break". After changing this setting to "Interrupt", my defined break key is working fine.
On 6/13/07, Andy Pflueger <[EMAIL PROTECTED]> wrote:
Hello, Recently, I have installed wIntegrate Version 6.0.4 on my WinXP Pro machine for evaluation use. So far, I really like its enhanced features but have noticed one difference between the previous version which I had loaded. My defined break key is reacting differently. Always before I could use Ctrl-Pause/Break to break a program to the debugger. Now, with the new 6.0.4 version, neither Ctrl-C or Ctrl-Pause/Break will break a program to invoke the debugger. Moreover, the Ctrl-Pause/Break will abort the connection with the server altogether. Has anybody seen or encountered this issue before and how can I change the behavior of the Ctrl-Pause/Break to NOT close the host connection but instead just break the program for the debugger?
------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
