Igor:

> > 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*.

        Same results: it works about once every 5 times. Logs
attached.

> > 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.

        This works well now.

> > 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.

        This works well now too.

        The all-zero MAC id bug is still there. I also noticed
that passive sniffing doesn't seem to be as reliable as it
once was. Perhaps the two are related?

-Scott

Attachment: Logs.zip
Description: Zip archive

Reply via email to