Hello Scott. Thank you for the compiled binary.
>1. When I run Kaboodle on a Win98 box, and connect to a WinNT > box running Kaboodle using Kaboodle-startup of VNC, getting > the password wrong causes a problem. I reproduced that bug on my Win98. The registry structure is different. Trying to found out is that affects. >The WinNT Kaboodle >activates the VNC server, checks the password, and reports >back that it's wrong. However...it doesn't then *stop* the >server. You are right. Even in case the password is incorrect the service must be stopped. I have fixed that already. >2. >If I go to the WinNT machine and manually >shut down the VNC server (the icon is active, so the server >is connected to something), To the Win98, I think >a message appears on the Win98 >box saying something like "Partner Kaboodle has shut down >VNC". Is there something wrong about it? >than fail silently when a Kaboodle-initiated VNC session cannot >be started because the server is already active. Either a message >should be displayed to the user on the Viewer side, or the >Kaboodle instance on the server side should shut down the VNC >server and restart it. A message would be fine. If user choose "restart VNC", it will restart. I continue debugging the multy LAN messaging. I have some problems with my LAN connection so I have no access to CVS. Sys admin promised to make connection on Monday. When I merged the new piece of code with LAN detection I found that they bound to machine name, which may change. I suggest binding to MAK address. -Igor _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
