Alexander:
I believe that the data in the registry is taken into
account only when the Service or App is *initiated*. So even
if a VNC Service is running, and the Current_User registry is
modified, and then VNC in App mode is launched...only the App
will be affected by that registry change. The Service just
keeps running. On reboot, the Service starts up looking at
the Local_Machine Settings, so even then it won't be affected
by the changes Kaboodle made to the CurrentUser.
-Scott
On Thu, 13 Mar 2003, Kaboodle wrote:
> Today I worked on bug #3.
>
> 1)
> I investigated the possibility to determine from inside the Kaboodle what tcp ports
> are used at local machine, to provide the requirement:
> "Kaboodle should check active services running on the indicated port, and start
> the app on the requested port if nothing is there already."
> I have found the free application/source code that obtains the ist of used TCP
> ports. So now I can satisy this requirement.
>
> 2)
> According to the documentation on WinVNC server the used TCP port is defined in
> registry:
>
> --------------------------------------------------------------------------------
>
>
> PortNumber
> specifies the port number to be used for VNC. You will need to disable
> AutoPortSelect to use this.
> Local or Global per-user setting
>
> a.. Local per-user settings. These override the local default user settings. If
> there is no current user, the username SYSTEM will be used. Location:
> HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\<username>
> b.. Global per-user settings. These are only read if AllowProperties has not been
> set to zero (see below) Location:
> HKEY_CURRENT_USER\Software\ORL\WinVNC3
>
> --------------------------------------------------------------------------------
>
> So all WinVNC server instances shares the same port setting. Therefore the
> requirement:
> No, that is incorrect. It should be possible to start
> WinVNC as a app even if WinVNC is already running as a service,
> as long as they don't try to listen to the same port. So when
> Kaboodle autostarts, it should *look for conflicts on the chosen
> port* and report an error if there is one. Otherwise, it should
> start WinVNC as an app on the indicated port number.
>
> can't be satisfied as is. Insted, if WinVNC server is already running as a service
> we could try to stop it, change port number setting in registry and then restart it
> as service again.
> Is it OK?
>
> 3)
> I'll try to check in the revised version of EF.RC (bug #5) in CVS server tomorrow.
>
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
