Hello Scott,

I have added code in wincvs for the all-remaining points except UI refresh
problem on WinNT machine.



  1.. Zebedee port and zebedee exe path are now part of registry settings.
  2.. VPN log functionality is added for all services. The only VNC message
that I cannot add into log is of closing the VNC session that is established
in PC2 and PC3 (i.e. two VPNed machines), since the VNCviewer is directly
connected to zebedee client and not through kaboodle tunnel. So cannot get
the notification for it. Please let me know if VPN "View log" needs any
additional information to go in.
  3.. VNC setup dialog and the background GUI will now get updated with the
result of  Vnc port scan on the device's LAN side.
  4.. I have also increased the length and width of the device name display
field in file transfer status dialog.
  5.. I could not replicate the crash you mention in point#3 below. I have
tested it the way you mentioned in the mail. Please forward the crash
details (debug mode ) if you get the crash in the debug mode. I tried to
replicate the same in the debug but couldnot replicate the same.
Regards,
Varsha



----- Original Message -----
From: "Scott C. Best" <[EMAIL PROTECTED]>
To: "mailbox" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, October 04, 2002 10:22 PM
Subject: Re: Queries (waiting for reply)


> 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

Reply via email to