Hello Scott. Please see my inline comments. - Igor ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, October 22, 2002 9:14 AM Subject: Re: Misc bugs, 18 Oct 02 > Igor: > > > > 1. CPU usage hits 100% again on my WinNT when I leave it > > > running for a long time. (VK: Please help Igor look > > > into this! It appeared around the time the last > > > Zebeedee code was added). > > I don't see that bug. > > I have inserted output some debug data into the file > > *NidLog.txt* in release build. > > Please repeat the bug and sent me that file from your PC. > > Kaboodle is running now along with the Performance meter. > I'll see what happens... > > > > 2. At startup, I can see from the network traffic that > > > Kaboodle check for VNC servers, and I can see an ACK > > > response from one when it finds one, but Kaboodle > > > doesn't seem to be able to detect it (ie, the icon is > > > not updated, the device is not added to the list of > > > known servers, etc). Also, if I use the "Check Again" > > > button it works but only half of the time. > > I don't see that bug. > > I have inserted output some debug data into the file > > *VncRunningAutoDetectLog.txt* in release build. > > Please repeat the bug and sent me that file from your PC. > > I worked the first time, failed the next 5 times. I've > attached the two logs, one from when it "worked" one when it > "broke". Please note: the machine the VNC server is running > on (.129) is a Mac. Unlike the other devices on my LAN, no > traffic is sent to the device during OS discovery. Not sure > if that matters.
The log file from "broke" shows that Kaboodle perform VNC scanning for the device with IP address <192.168.123.129> on the port range 5900-5909 and didn't found the VNC server. (There is next line in the log file: Finish ThreadScanVnc: 192.168.123.129, No VNC running detected) I inserted addition data in that file. Please repeat the bug and sent me log file *VncRunningAutoDetectLog.txt*. > > > 3. It used to be that when I opened the VNC Setup tab on > > > a PC device that was not a VNC server, Kaboodle would > > > quickly check the VNC ports 5900-5909 on that device. > > > I can see from the network traffic that it doesn't do > > > that anymore. > > In above case Kaboodle performs VNC scanning (5900-5909) on a PC > > device *only* if there wasn't such scanning on that PC. > > If a user pushes "Check Again", then it checks ports 5000-5999 > > always. In my tests all above work. > > Ah, okay. Maybe we should change that: if a device is > not running a VNC service and the user opens the "VNC Setup" > tab, we should quickly do a mini-scan (5900-5909) on that device. > After all, the user will probably only open that tab if the > device *should* be running a server... I made a modification: if a user opens the "VNC Setup" tab on the device, which doesn't run VNC server, then Kaboodle performs VNC scanning on the port range 5900-5909 on that device. > > > 4. The VERSION registry entry is not being set on initial > > > startup. So the second time I start Kaboodle, it puts > > > up the version warning popup. > > Yes, I saw that bug. The bug is fixed. > > Yup! > > > > 5. If I push "Cancel" on that popup, Kaboodle quits but > > > it leaves a renegade icon in the taskbar that cannot > > > be deleted without a restart. > > Yes, I saw that bug. The bug is fixed. > > Partly, yes. Try this: start Kaboodle, then quit. Change > the Version Registry entry from "5f" to "5e". Start Kaboodle, > choose "Cancel". Then start Kaboodle, choose "Okay". The two > icons in the task manager come back. I never seen two icons on my Win2000 box, but I saw that bug on my Win98 box. I debuged source code and found the strange thing on Win98 box: the WinApi function *BOOL Shell_NotifyIcon(...)* returns *FALSE*, though really a tray icon created. As result - there was more then one creation of that icon. I inserted some additional code. > > > 6. Please remove the text in the Network Icon which reads > > > "Status of the PC will be changed...". Also, please > > > remove the "+" and "-" signs from next to the Device > > > names in the dropdown. All I want in that dropdown list > > > are the Kaboodle PC's on my LAN, that's it. Whichever > > > one is selected when I hit "OK" becomes the Master. > > > > > > > > > Igor: > > > To clarify on #6: if the user selects a new Master > > > machine in the Network Icon, and then clicks Remote Networks > > > tab before hitting Okay...the Master Node status should *not* > > > change. Only if they change it *and* hit Okay should it be > > > updated. > > > > The text in the Network Icon which reads > > "Status of the PC will be changed..." removed. > > Signs "+" and "-" removed also. > > Only if a user change selected dropdown *and* hit Okay should it be > > updated. The user can set a PC as the Master Node from that tab. > > The user *cannot* set a PC as the "Non Master Node" from that tab. > > > Looks good now, thanks! I'll keep you posted about the > CPU bug. It can take an hour or so to appear. > > -Scott > > ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v? http://www.sun.com/javavote _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
