Hello Scott. This is our common message(from Oleg and Igor). Some words about usual Kaboodle messaging (below referred as UKM). UKM is implemented as separate thread. Current code posts messages to that thread and doesn't check result of really sending data via socket connection. If socket connection fail current code doesn't know about that. For really sending data Kaboodle use the function int CNetworkManager::SendRemoteMessage(const CGUID* pDestEFId,DWORD message,char* data,int datalen). If Kaboodle send data to one partner only, then SendRemoteMessage tries to find existing TCP connection. If SendRemoteMessage cannot find that connection, then it returns 1. This return code looks like "I sent 1 byte". We cannot use UKM for safe sending data. If Kaboodle needs notify partner that NID updates, it may be not too dangerous to lose that data. But for startup VNC of file transfer it is not so.
Now about a way general-purpose Kaboodle-to-Kaboodle messaging. Now we have class CServerPartnerRequest (see files EF\TCPRequestToPartner.h, EF\TCPRequestToPartner.cpp). Kaboodle creates object of this class at startup. That object listens all TCP/IP connections on the some port (now it is 7000). Each new connection is processed by the thread ThreadListenRequestConnection(). Thread ThreadListenRequestConnection() reads first data for new connection and checks the type of the *server applet* (see function GetTypeSession) and creates new thread depending on the type. For example, for the type of *server applet* "start up independent VNC session" that will create thread ThreadProcessRequestSIVS(). When some thrid developer needs to add new *server applet*, then he has to add new code in 4 places marked as // _ADD_NEXT_SERVICE_APPLET_HERE We have provided the room for error handling of socket data transfer. Each server applet has its own thread manager function like ThreadProcessRequestSIVS(). Unlike the UKM, with the new messaging system, the socket connection thread only exists when the server applet really needs it. After the applet is finished, the thread kills its own TCP socket and itself. -Igor,Oleg. ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> Sent: Wednesday, May 15, 2002 9:30 PM Subject: Re: VNC Server Status column > Igor: > You're right: the usual Kaboodle messaging doesn't have > any documentation. Right now, it's used for NID updates (ie, when > I change a device name in one Kaboodle window, all of the Kaboodle > instances on the LAN will get updated). Long term, I'll be changing > how Kaboodle sends these updates, so *not* using this messaging is > okay as long as you and Oleg can combine your messaging needs. That > is, he needs a way to send a Kaboodle-to-Kaboodle message for file > transfer, and you could use the same thing for VNC. I don't want to > create a new messaging system for every service applet, so please > build it to be general-purpose and not easily "crashable". So if I > netcat (http://freshmeat.net/projects/netcat/?topic_id=150) a > mega-byte of random data into the port Kaboodle is listening to, > it'd be best if it didn't crash the application or Windows. > > -Scott > > PS: Our ISP is down this AM, so the CVS server is not reachable. > They tell me they're working on it... > > On Wed, 15 May 2002, Igor Kotelevsky wrote: > > > Hello Scott. > > You wrote. > > > > > I was thinking this could fit into the usual Kaboodle messaging > > > going on, rather than require a dedicated TCP port listener. > > > > It seems to me that usual Kaboodle messaging doesn't have good > > documentation. > > That is more simply to write the new code. > > I have already write that new code. It is Win socket code. > > Please see the files EF\TCPRequestToPartner.cpp and > > EF\TCPRequestToPartner.h. > > Oleg said to me that he can use that code in hiz topic "File Transfer". > > Please let me know what do you think about. > > > > CVS server has some problems today. > > >In C:\PROJECTS\cvs_\Kaboodle: cvs -q -z6 commit -m "" EF.rc EF\EF.dsp > > EF\SynchrSocket.cpp EF\SynchrSocket.h >EF\VNCViewerSettingsPropPage.cpp > > EF\VNCViewerSettingsPropPage.h UI\MainFrame.cpp UI\MainFrame.h >resource.h > > >Unknown host cvs.echogent.com. > > > > > >Error, CVS operation failed > > I have cannot put my code in CVS server today. > > Please see my today code in attachment KABOODLE_15_MAY.zip > > -Igor > > > > ----- Original Message ----- > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > Sent: Tuesday, May 14, 2002 10:04 PM > > Subject: Re: VNC Server Status column > > > > > > > Igor: > > > Yes, Kaboodle needs to be able to send a special message > > > to another Kaboodle telling it to startup a regular VNC service. > > > I was thinking this could fit into the usual Kaboodle messaging > > > going on, rather than require a dedicated TCP port listener. > > > > > > -Scott > > > > > > On Tue, 14 May 2002, Igor Kotelevsky wrote: > > > > > > > Hello Scott. > > > > You wrote: > > > > > 2. If no independent VNC service is running and Kaboodle on PC1 > > > > > has "Kaboodle starts VNC" selected and the server field is > > > > > non-empty, then the the status column in Kaboodle on PC2 > > > > > should say "automatic". If the Kaboodle user on PC2 hits > > > > > Connect, then Kaboodle on PC1 starts up a VNC service for > > > > > a loopback connection if "Enable Kaboodle tunnels" is selected, > > > > > and it starts up a regular VNC service for a direct connection > > > > > if "Enable Kaboodle tunnels" is not selected. > > > > > > > > Dear Scott. As you know, > > > > ( see "VNC server" algorithm > > > > http://www.geocrawler.com/archives/3/16728/2002/4/0/8536833/ ) > > > > the current project version works as follows. > > > > If "Enable Kaboodle tunnels" is not selected for PC1, > > > > then Kaboodle on PC1 doesn't listen any VNC requests from other PCs. > > > > You wrote: > > > > >... it starts up a regular VNC service for a direct connection if > > "Enable > > > > Kaboodle tunnels" is not selected. > > > > This functionality is missing from the current project. > > > > It seems to me that I have to add this functionality. > > > > It can work as follows. > > > > Kaboodle always listens TCP connection on port number 7000. > > > > (The proper value of this number can differ.) > > > > If Kaboodle on PC2 needs to start up a regular VNC service on PC1, then > > > > Kaboodle on PC2 has to > > > > establish TCP connection with PC1 on port number 7000 and send a special > > > > message "please start up a regular VNC service". > > > > Then Kaboodle on PC1 starts up a regular VNC service. > > > > If that succeeded, then Kaboodle on PC1 sends a special message to > > Kaboodle > > > > on PC2 "a regular VNC service has started". If that failed, then > > Kaboodle on > > > > PC1 sends a special message to Kaboodle on PC2 "failed to start up a > > regular > > > > VNC service - system error code". > > > > > > > > -Igor > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > Sent: Tuesday, May 14, 2002 9:56 AM > > > > Subject: Re: VNC Server Status column > > > > > > > > > > > > > Igor: > > > > > Hello! Some feedback on your ideas: > > > > > > > > > > > > > Status column will be > > > > > > > > a) "active" when #2; > > > > > > > > b) "automatic" when no #2, simultaneously #1 with both options > > > > "Enable > > > > > > > > Kaboodle Tunnels for VNC" > > > > > > > > and "Let Kaboodle auto start and restart the VNC Server when it > > > > needs > > > > > > > > to"; > > > > > > > > c) "off" in other case. > > > > > > > > > > > > Scott wrote: > > > > > > > Sounds good, but I don't think "b" needs there to be "Enable > > > > > > > Kaboodle Tunnels" activated. As long as Kaboodle can start VNC > > when > > > > > > > it's needed, we can call it "automatic". > > > > > > > > > > > > About #b. > > > > > > As you know, if there is not active "Enable Kaboodle Tunnels" for a > > PCn > > > > > > then Kaboodle on the PCN doesn't listen VNC session via "Kaboodle > > > > > > Tunnels". > > > > > > > > > > But I can disable "Kaboodle tunnels" and enable "Kaboodle > > > > > starts VNC Service" at the same time. If no independent server is > > > > > running, then Kaboodle can start the independent server when a user > > > > > starts a VNC connection with Kaboodle. > > > > > > > > > > > > > > > > Therefore if status column for the PCn will be "automatic" when > > > > > > - PCn doesn't running independent VNC Server, > > > > > > - PCn have active option "Let Kaboodle auto start and restart the > > VNC > > > > > > Server when it needs to", > > > > > > - we do not take into account option "Enable Kaboodle Tunnels", > > > > > > it means that > > > > > > - we cannot connect to PCn directly, > > > > > > - we doesn't know can we connect to PCn through Kaboodle or no. > > > > > > > > > > No, that's not right. The "Enable Tunnels" button does > > > > > not affect the Status column. Lets go through an example: Kaboodle > > > > > on PC1 is managing a VNC server. I'm running Kaboodle on PC2. > > > > > > > > > > 1. If Kaboodle on PC1 has a VNC service running on PC1, then the > > > > > status column in Kaboodle on PC2 should say "active". It > > > > > doesn't matter what the "Enable Kaboodle Tunnels" button > > > > > in Kaboodle on PC1 is set to. It doesn't matter what the > > > > > "Kaboodle starts VNC" checkbox is set to. > > > > > > > > > > 2. If no independent VNC service is running and Kaboodle on PC1 > > > > > has "Kaboodle starts VNC" selected and the server field is > > > > > non-empty, then the the status column in Kaboodle on PC2 > > > > > should say "automatic". If the Kaboodle user on PC2 hits > > > > > Connect, then Kaboodle on PC1 starts up a VNC service for > > > > > a loopback connection if "Enable Kaboodle tunnels" is selected, > > > > > and it starts up a regular VNC service for a direct connection > > > > > if "Enable Kaboodle tunnels" is not selected. > > > > > > > > > > 3. If no independent VNC service is running and Kaboodle on PC1 > > > > > does not have "Kaboodle starts VNC" selected, then the the > > > > > status column in Kaboodle on PC2 should say "inactive". > > > > > > > > > > > > > > > > Second. About button "Connect". > > > > > > Igor wrote: > > > > > > > > What action has to do Kaboodle if user pushes the button > > "Connect"? > > > > > > > > May be it is > > > > > > > > - "Connect Directly (slightly faster)" for #a; > > > > > > > > - "Connect through Kaboodle (more secure)" for #b, > > > > > > > > - nothing (button is gray) for #c. > > > > > > Scott wrote: > > > > > > > I think we should add "I prefer to:" above the two Connect > > > > > > > choices. Then we should try to connect in that manner first, and > > > > > > > the other way second. The "more secure" should be the default > > > > > > > selected radio button. We shouldn't not try to connect in the > > > > > > > second way if the first, preferred way fails. > > > > > > > > > > > > Kaboodle can "Connect through Kaboodle (more secure)" only if > > partner > > > > has > > > > > > option > > > > > > "Enable Kaboodle Tunnels". Therefore when a user push button > > "Connect" > > > > > > Kaboodle can > > > > > > 1) - try to connect "more secure" ,if partner PC has option "Enable > > > > Kaboodle > > > > > > Tunnels", > > > > > > 2) - connect directly, if partner PC doesn't has option "Enable > > Kaboodle > > > > > > Tunnels" and > > > > > > has running independent VNC Server. > > > > > > Please let me know what do you think above "Second". > > > > > > > > > > That's correct, yes. The trick is: if the user on PC1 has > > > > > "connect more secure" chosen and the partner on PC2 doesn't have the > > > > > "Enable Kaboodle Tunnels" button chosen, then when the user of > > > > > Kaboodle on PC1 hits connect, it should try to connect securely > > > > > *first*, and then try to connect directly when the first one fails. > > > > > > > > > > > > > > > Lastly, there's a bug still with Kaboodle not remembering > > > > > the display/port value. I set it to port 80, then close the VNC > > > > > Service Icon panel, and when I open it again it's running on port > > > > > 5900 still. I think an independent VNC service is running when I > > > > > see this. > > > > > > > > > > Thanks! > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > Hello again. Some answer inline: > > > > > > > > > > > > > > > > 2. VNC Server Status column added into the list in the > > > > > > > > > VNC Service Icon. > > > > > > > > > > > > > > > [snip] > > > > > > > > > > > > > > > > What now will show ProperyTab "Viewer Settings"? > > > > > > > > May be it is list of all LAN PC which > > > > > > > > 1) running Kaboodle or > > > > > > > > 2) running independent VNC Server. > > > > > > > > Status column will be > > > > > > > > a) "active" when #2; > > > > > > > > b) "automatic" when no #2, simultaneously #1 with both options > > > > "Enable > > > > > > > > Kaboodle Tunnels for VNC" > > > > > > > > and "Let Kaboodle auto start and restart the VNC Server when it > > > > needs > > > > > > > > to"; > > > > > > > > c) "off" in other case. > > > > > > > > > > > > > > Sounds good, but I don't think "b" needs there to be "Enable > > > > > > > Kaboodle Tunnels" activated. As long as Kaboodle can start VNC > > when > > > > > > > it's needed, we can call it "automatic". > > > > > > > > > > > > > > > What action has to do Kaboodle if user pushes the button > > "Connect"? > > > > > > > > May be it is > > > > > > > > - "Connect Directly (slightly faster)" for #a; > > > > > > > > - "Connect through Kaboodle (more secure)" for #b, > > > > > > > > - nothing (button is gray) for #c. > > > > > > > > > > > > > > > > Please let me know what you think. > > > > > > > > > > > > > > I think we should add "I prefer to:" above the two Connect > > > > > > > choices. Then we should try to connect in that manner first, and > > > > > > > the other way second. The "more secure" should be the default > > > > > > > selected radio button. We shouldn't not try to connect in the > > > > > > > second way if the first, preferred way fails. > > > > > > > > > > > > > > > > > > > > > > > 3. The log file Checkbox I described last week. > > > > > > > > > > > > > > > > At 04/25/2002 08:49:28 your wrote (Message: 8495270): > > > > > > > > >Lastly...I think it would be useful for Kaboodle to help > > > > > > > > >log VNC server usage. So, at the bottom of the PropPanel, a > > > > checkbox > > > > > > > > >can say "Log VNC usage" with a "View Log..." button next to it > > > > > > > > >that's grayed out if the checkbox is off. If the user selects > > this > > > > > > > > >CheckBox, we activate set DebugMode and DebugLevel to 1, and > > then > > > > > > > > >show the Winvnc.log file in Notepad when "View Log..." is hit. > > > > > > > > > > > > > > > > There are some problems. > > > > > > > > First. > > > > > > > > A user tries to open a Winvnc.log file in Notepad. Notepad > > doesn't > > > > show > > > > > > > > the file properly. > > > > > > > > The reason is following. The Winvnc.log file has only one symbol > > for > > > > > > > > line break (0xA). > > > > > > > > Notepad wants two symbols for line break (0xD) (0xA). > > > > > > > > I can write a simple special viewer (KaboodlePad.exe) and > > include it > > > > in > > > > > > the > > > > > > > > Kaboodle project. > > > > > > > > It seems to me that will be no more then one day of my working. > > > > > > > > > > > > > > Okay, lets do that. Good idea. > > > > > > > > > > > > > > > Second. > > > > > > > > At the Win32 VNC Server documentation I have found > > > > > > > > *DebugMode 2 = Output to log file Winvnc.log in the WinVNC > > > > directory*. > > > > > > > > But on my PC I have found that above directory is "C:\". > > > > > > > > My suggestion is following. > > > > > > > > User push button "View Log...". > > > > > > > > Kaboodle check WinVNC directory and "C:\" directory. > > > > > > > > If it failed then Kaboodle prompt to user something MessageBox > > as > > > > > > > > "Please help to find file Winvnc.log". > > > > > > > > There are two buttons "YES", "NO". > > > > > > > > > > > > > > Sure. Maybe "Sorry...Kaboodle cannot find the WinVNC.log file > > > > > > > in the usual places." with "Browse..." and "Cancel" would be > > better. > > > > > > > > > > > > > > > Third. > > > > > > > > When user activate or deactivate check box *Log VNC usage*, then > > > > > > Kaboodle > > > > > > > > have to > > > > > > > > change VNC Server registry. If there is running independent VNC > > > > Server, > > > > > > then > > > > > > > > Kaboodle must > > > > > > > > prompt to user > > > > > > > > "Kaboodle needs to restart your VNC server for setting *Log VNC > > > > usage* > > > > > > to > > > > > > > > take effect." > > > > > > > > My suggestion is following. > > > > > > > > Kaboodle doesn't erase the change of VNC Server value *Log VNC > > > > usage* > > > > > > > > (remember value *AllowLoopback*). > > > > > > > > > > > > > > > > Please let me know what you think. > > > > > > > > > > > > > > If Kaboodle has already been given permission to restart > > > > > > > the server (ie, with the "Let Kaboodle re-start..." checkbox) then > > > > > > > we should just restart the server. If not, we should prompt the > > > > > > > user with the usual "Please restart the VNC Server for these > > > > > > > changes to take effect". > > > > > > > Besides that...treating the Log usage registry entry in > > > > > > > the same way that we treat AllowLoopback sounds fine. > > > > > > > > > > > > > > thanks, > > > > > > > Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ********************************************************************* > > > > > > > > - Igor > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > Sent: Tuesday, May 07, 2002 10:44 AM > > > > > > > > Subject: Re: Independent VNC server problem > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > I don't think this additional MessageBox is needed. > > > > > > > > > If Kaboodle on MyMachine is not running an independent VNC > > > > > > > > > server, and if I don't have that Checkbox selected, then we > > > > > > > > > should update the other Kaboodle instances on the LAN so > > > > > > > > > that they cannot initiate a VNC session to MyMachine. That > > > > > > > > > is, its status should change from active to inactive server, > > > > > > > > > so the Connect buttons won't work. > > > > > > > > > > > > > > > > > > That and one other VNC feature are still pending. > > > > > > > > > So, for this week, lets finish: > > > > > > > > > > > > > > > > > > 1. The VNC algorithm you described last week > > > > > > > > > 2. VNC Server Status column added into the list in the > > > > > > > > > VNC Service Icon. > > > > > > > > > 3. The log file Checkbox I described last week. > > > > > > > > > > > > > > > > > > Please confirm when you can. Thanks! > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, 6 May 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > We have to insert additional MessageBox when > > > > > > > > > > independent VNC server not running and user have not checked > > the > > > > > > > > Kaboodle > > > > > > > > > > option. > > > > > > > > > > <Let Kaboodle auto start and restart the VNC Server\nwhen it > > > > needs > > > > > > to> > > > > > > > > > > > > > > > > > > > > "A Kaboodle user on <IP address" > > > > > > > > > > "has tried to connect to this machine with VNC" > > > > > > > > > > "You have not checked the Kaboodle option" > > > > > > > > > > "<Let Kaboodle auto start and restart the VNC Server\nwhen > > it > > > > needs > > > > > > to>" > > > > > > > > > > There are two buttons "Let Kaboodle restart VNC Server now", > > > > "Cancel > > > > > > > > > > connection" > > > > > > > > > > > > > > > > > > > > -Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > > > Cc: <[EMAIL PROTECTED]> > > > > > > > > > > Sent: Saturday, May 04, 2002 12:31 AM > > > > > > > > > > Subject: Re: Independent VNC server problem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > Some thoughts on what you're seeing: > > > > > > > > > > > > > > > > > > > > > > 1. If PC1 is running an independent VNC server with > > Kaboodle, > > > > and > > > > > > > > > > > "Enable Kaboodle Tunnels for VNC" is set, then > > > > AllowLoopback > > > > > > > > > > > should be set. That's what "Enable Kaboodle Tunnels" is > > > > > > > > > > > supposed to do: set that registry key. Whenever > > Kaboodle is > > > > > > > > > > > running and this Checkbox is selected, that key should > > be > > > > set. > > > > > > > > > > > > > > > > > > > > > > 2. Let's change the Checkbox which reads "Use Kaboodle to > > > > startup > > > > > > > > > > > VNC Server only when it's needed" to read "Let Kaboodle > > > > auto > > > > > > > > > > > start and restart the VNC Server when it needs to". If > > this > > > > > > > > > > > box is selected, Kaboodle won't prompt the user when it > > > > makes > > > > > > > > > > > a change to the VNC registry and restarts the VNC > > service. > > > > > > > > > > > When the user first activates the "Enable Kaboodle > > Tunnels" > > > > > > > > > > > checkbox, we should activate this checkbox by default > > if > > > > > > > > > > > Kaboodle finds a WinVNC.exe server. > > > > > > > > > > > > > > > > > > > > > > 3. If Kaboodle makes any changes to the VNC registry, and > > the > > > > > > > > > > > user clicks "Okay", and the "Let Kaboodle..." checkbox > > from > > > > #2 > > > > > > > > > > > is not selected, it should prompt the user with "Your > > VNC > > > > > > > > > > > Server needs to be restarted for these Kaboodle > > settings to > > > > > > > > > > > take effect." We can have two buttons: "Let Kaboodle Do > > > > this > > > > > > > > > > > Now" and "I'll Do This Later". > > > > > > > > > > > > > > > > > > > > > > 4. If Kaboodle is started up with some VNC Server settings > > > > that > > > > > > > > > > > require changes to the VNC Registry, we'll need to > > prompt > > > > the > > > > > > > > > > > user in the same way as #3 if the "Let Kaboodle..." > > > > checkbox > > > > > > > > > > > of #2 is not selected. If it is selected, we can just > > make > > > > > > > > > > > the changes and quietly restart the VNC service. > > > > > > > > > > > > > > > > > > > > > > Sound good? > > > > > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 3 May 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > > > I have found a following problem of the independent VNC > > > > server. > > > > > > > > > > > > PC1 is running independent VNC server and Kaboodle. > > > > > > > > > > > > Kaboodle on PC1 is "Enable Kaboodle Tunnels for VNC". > > > > > > > > > > > > User on PC2 checks radio button "Connect through > > Kaboodle > > > > (more > > > > > > > > secure)" > > > > > > > > > > and > > > > > > > > > > > > push button "Connect". > > > > > > > > > > > > Then user on PC2 see MessageBox("Local loop-back > > connection > > > > are > > > > > > > > > > disabled"). > > > > > > > > > > > > The caption of this MessageBox is "VNC info". > > > > > > > > > > > > In this case Kaboodle on PC1 tries to connect with own > > VNC > > > > > > server on > > > > > > > > IP > > > > > > > > > > > > address of the LAN interface, > > > > > > > > > > > > and if it failed, then on loopback IP address... > > > > > > > > > > > > > > > > > > > > > > > > I have checked the source code of WinVNC server. > > > > > > > > > > > > I have found that in above case Kaboodle have to set VNC > > > > server > > > > > > > > registry > > > > > > > > > > key > > > > > > > > > > > > *AllowLoopback*. > > > > > > > > > > > > It is not difficult. But Kaboodle have to show > > > > MessageBox("The > > > > > > VNC > > > > > > > > > > Service > > > > > > > > > > > > needs to be restarted..."). > > > > > > > > > > > > > > > > > > > > > > > > I have following suggestion. > > > > > > > > > > > > - Kaboodle checks VNC server registry key > > *AllowLoopback*. > > > > > > > > > > > > - If there is not above key, then Kaboodle show next > > > > MessageBox > > > > > > > > > > > > "Kaboodle have to put VNC server registry key > > > > *AllowLoopback* > > > > > > and > > > > > > > > > > restart > > > > > > > > > > > > VNC server." > > > > > > > > > > > > "Kaboodle don't will restore above key at the finishing > > of > > > > the > > > > > > VNC > > > > > > > > > > session". > > > > > > > > > > > > There are two buttons: "Let Kaboodle do this now", > > "Cancel > > > > VNC > > > > > > > > session". > > > > > > > > > > > > > > > > > > > > > > > > -Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
