VK: Sorry for the delay: 1. It's not just the UI of Kaboodle that gets slow: it starts pulling 100% CPU time, so everything on the machine gets slow. I'm running the performance meter now to see what's going on, whether it's gradual or sudden.
2. Both the PropPanel GUI and background GUI should update when a VNC service is detected. 3. I experimented with the FTP'ing while VNC'ing and I got it to crash in Release mode. Here's how I did it: started Kaboodle on PC1, a Win98 machine. Started Kaboodle on PC2, a WinNT machine. From PC2, I initiated a VPN to PC1. Then on PC1, I start a VNC session to a peer with PC2. Then on PC1, I start a file-transfer directly to PC2. Then on PC2, I start using VNC, and Kaboodle crashes in the background. Mercifully...the VNC and Zebedee processes keep working. 4. I also noticed when FTP'ing across a LAN that there's not enough room for the machine names in the FTP status screen. I'll see if I can repeat #3 in Debug build. -Scott On Fri, 4 Oct 2002, mailbox wrote: > Hello Scott, > > I have tried to find out the problem of getting UI very slow on NT machines, > but I could not get the actual reason behind it. I will again try to get > into the problem. > > I have done VPN messaging to do the port scanning on the VPN Partner's node > and exchanged the VNC port information with the VPN node from where the > request for port scan was initiated. Do you want the VNC Setup GUI to be > updated with the port scan results or just updating the background GUI > (Device Icon) with vnc icon is sufficient? > > Please correct me if I am going wrong in any sense. > Did you get a chance to test the FTP with VNC on your side? > > Regards, > Varsha > > ------------------------------------------------------- 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