Scott, Thanks. I'll wait for the fix. I guess it is isolated to 0.99 because of no installer. Normally, I might have uninstalled, then reinstalled Kaboodle.
I will mention another *issue* I had. I was playing around in Kaboodle. I moved icons around, even moved groups around. I was trying to see if I could make a group and associate specific PCs to that group. I was thinking to make them visible/invisible to VPN Partners as I wished. I was also thinking that I could remove My MACs or My Printers, which I don't need at this point, and if needed could add them in the future. Once I pressed Refresh, all the icons I moved disappeared. I could not figure out what happened to them and could not find a way to detect them. I searched through the email archives. I found a post that stated to delete the Kaboodle registry key. I did that and all came back up the next time I loaded Kaboodle. I am still kind of confused on the functionality of making new groups if they can't be used. Unless, it is a place setting for a future release. Jim -----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 12:11 PM To: Jim McCabe Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Kaboodle-user] VNC Not Installed? 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: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
