Igor:
Two more things from tonights debug session:
9. The "all zeroes" MAC address bug is back again. If I start
Kaboodle on PC1 and let it finish network discovery, then
start Kaboodle on PC2, the Kaboodle on PC2 displays two
icons for PC1 -- one with a MAC address of all zeroes,
the other with a correct MAC address but not Kaboodle halo.
10. When I start Kaboodle on PC2, it takes over the network
name. So if my LAN was "Scott's LAN" and I startup
Kaboodle on my laptop, the Network name becomes "Laptop
LAN everywhere. The existing Network Name in the NID
should have precedence.
Sorry for all the bugs all at once!
-Scott
On Tue, 22 Oct 2002, Scott C. Best wrote:
> Igor:
> Sorry, missed something:
>
> 7. When I select a new Master Node in the Network Icon dropdown
> and hit OKAY, it should be updated everywhere. It's not. If
> I change it, hit OK and immediately open the panel again, the
> same old data is there. Also, if I change the dropdown, click
> on the Remote Network tab, then back to the main tab, the
> dropdown should show the current Master, *not* my halfway
> made change.
>
> 8. In the main Prop Panel for a Kaboodle PC, there is a checkbox
> saying "Make this PC the Kaboodle Master Node" and it's always
> checked. Please change this so that it's always unchecked. If
> the user checks it, and hits Okay, it should update the Master
> Node status everywhere just like in #7.
>
> Thanks!
>
> -Scott
>
>
> On Tue, 22 Oct 2002, Scott C. Best wrote:
>
> > 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.
> >
> > > > 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...
> >
> > > > 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.
> >
> > > > 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
>
-------------------------------------------------------
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
