Jim:
Heya. Yes, you're right: something gets confused in
Kaboodle when WinVNC is uninstalled after Kaboodle is installed.
I just tested it here, and it does what you describe. Nuts.
I've contacted the developer who worked on that part,
but he's down with the flu. I'm hopeful that bug will be fixed
this month. For now, you'll have to start the VNC Server
"manually" on your Kaboodle PC's -- Kaboodle should still be
able to securely wrap the VNC connection.
I'll post an email once the bug is fixed.
-Scott
On Tue, 18 Feb 2003, Jim McCabe wrote:
> Well, I don't know why it happened but I can't seem to fix it. I am
> running version 0.99.
>
> I am having trouble with the VNC component for one of my PCs. On that
> PC, I was running WinVNC and TightVNC. I uninstalled WinVNC to just use
> TightVNC.
>
> After that point, Kaboodle stated the VNC Component as 'Not Installed'
> on the properties page. I was able to get the viewer running by
> browsing to the proper path, but I couldn't get the server running even
> with the proper path. I tried reinstalling WinVNC to try to correct the
> detection process but had no luck. When I click 'Autostart Now', if I
> have a server running, it closes but, a new instance doesn't appear. I
> then receive two errors: Failed to find path of the VNC and Failed to
> Restart VNC.
>
> I am able to use VNC successfully in both directions without Kaboodle.
> Do I need to reset one of the registry settings?
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
