Well, the beta application that I'm testing has evolved to a point where I can't use the mouse at all. I need some troubleshooting suggestions. I control PC2 remotely from PC1 via the beta application. PC1 runs powerpro my.pcf and PC2 runs powerpro empty.pcf or default.pcf or my.pcf. In all cases mouse clicks on PC2 -through the remote control application- don't work at all. The keyboard works normally. The reason I bring up default.pcf is because in a previous beta version I had the same problem with default.pcf but not with empty.pcf. I suspect that if/when I'll get around this mouse problem, powerpro will start crashing again, so I'll be able to test your suggestions below. BTW, what do the various hook code values mean?
--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], sgp <acs322000@> wrote: > > > > Bruce, PowerPro silently crashes each time a remote control > application (beta) connects to my PC. > > What can I do to help you debug this crash? > > > Try all of the following: > 1. empty configuration > 2. empty configuration with hook code on setup|advanced|limit set to 1 > 3. ditto with code set to 2 > 4. ditto with 4 > 5. ditto with 8 > > Are there any circumstances in which it does not crash? > > If not, I suspect there is not much I can do. If there are, try the > same hook code setting on your normal configuration to see if it still > does not crash. >
