Oleg:
Some updates. I started Kaboodle on a Win98 machine with
a fresh registry. Then I started Kaboodle on PSLEI. Everything
came up fine, except the weird two-icon thing for PSLEI, one of
which has a MAC address of all zeroes.
Then I did it the other way: started Kaboodle on PSLEI
first (with a fresh registry) and then started it on the Win98
machine. The one on PSLEI crashed. In the debugger, it took me
to CNIDNetwork::GetNetGwyID() where the 'this' pointer has a
value of 0xdddddddd.
Unfortunately...I've had no luck making it crash again,
though I tried at least 10 more times.
I've no idea what the root of the problem is, but I
believe that the all-zero MAC address on the WinNT machine is
a good place to start looking, as it's the basis of a device's
unique identifer in the NID. It's correct on a Win98 machine,
only on the WinNT machine is it broken.
Hope this helps.
-Scott
On Tue, 5 Feb 2002, Scott C. Best wrote:
> Oleg:
>
> > >2. The NID information is not being shared amoungst the
> > > multiple machines correctly anymore. Try starting up
> > > Kaboodle on two machines on your LAN after resetting
> > > the registry key. It looks like the second instance
> > > of Kaboodle gets the device name of the first one,
> > > and so things get terribly confused. It's more stable
> > > than it was, but it's confused and contradictory in
> > > places.
> >
> > Remains.
> > Could you provide us with more detail? Did you clear the
> > Kaboodle Registry and then start Kaboodle? What device
> > name did you observe? Thank you.
>
> I cleared the Kaboodle registry on two WinNT machines
> (a laptop with a 802.11 card and the PSLEI machine that you VNC
> into). If I start Kaboodle on the laptop, it starts up with two
> device icons (itself and one printer), naming the network icon
> after itself. Which it should do. After a 20 seconds or so, the
> "slow ping" process finds 5 other PC's on the LAN, one of them
> being the PSLEI machine. The PSLEI machine is show in all capital
> letters (this becomes relevant later). Only the laptop machine
> has the Kaboodle icon. So far so good.
> Now I go over to the PSLEI machine and startup Kaboodle.
> It *should* instantly detect that Kaboodle is already running on
> the LAN, and inherit the NID and the Network name. It doesn't. It
> displays itself (with a halo) and it's 3 printers (from installed
> driver detection). It then goes thru its own 20 second slow-ping
> process and then...breaks. That is, it looses PSLEI and its 3
> printers and instead displays the laptop machine with a Kaboodle
> halo and the laptop's 1 printer. It also displays the machines
> the slow-ping process found on the LAN: one of them the laptop.
> So, there are now two icons in PSLEI's GUI for the laptop.
>
> Back over on the laptop machine...the PSLEI devices have
> similarly over-taken this one. So, instead of showing itself and
> its one printer, its first position icon now reads "Pslei" with a
> Kaboodle halo, and PSLEI's 3 printers are here. It's own halo'd
> icon and the original printer are gone. It's as if Kaboodle
> confuses its own identity, and is displaying the network from
> the other Kaboodle machine's perspective.
>
> Here's the strange part. :) There are two icons on the
> laptop for PSLEI: one of them lowercase (Pslei), one of them
> uppercase (PSLEI). The lowercase one is in the first position with
> a Kaboodle halo. In its "system" tab, the IP address is the PSLEI
> machine, but the MAC address is all zeroes. The uppercase PSLEI
> has the correct IP address and MAC address, but has no Kaboodle
> halo. Similarly...on the PSLEI machine, there are two icons for
> the laptop, one lowercase and one uppercase. Also similarly, the
> one in the first position has the Kaboodle halo, and has a correct
> IP address but a MAC address of all zeroes. The uppercase one is
> correct in IP address and MAC address, but has no halo. You'll
> recall that the "slow ping" discovery is the one that displays
> the device with uppercase.
>
> Another strange part. One of the icons is drawn in the
> "off" state. If on PSLEI I select the icon and hit "connect",
> I get a popup *on the laptop* which reads "Remote network devices
> cannot be disconnected". I get the same popup box when I select
> an active printer icon and hit "disconnect". Although there's
> no reason I should get that popup, at least it comes up in the
> right window.
>
> Also...the Network icon (in the upper left) remains
> stuck for both machines. So, it says "Pslei's Network" on the
> PSLEI machine, and says "Laptop Network" on the Laptop machine.
> I got it to crash once by changing the name, but cannot get that
> to repeat. In any case, they should certainly be the same thing.
>
> Lastly, after many "refresh" clicks, I got a PSLEI icon
> to appear on the PSLEI machine. No halo, but the IP address and
> the MAC address are both correct. In this device's VNC setup
> PropertyTab, it does correct recognize that it's the "same
> machine": I can setup the VNC server settings as I should.
>
> Again, this is on two WinNT machines. A Win98 machine
> responds correctly when Kaboodle is already running on the LAN:
> it gets the NID from the "network master".
>
> Hope this helps! If I can get Kaboodle to crash while
> running the debugger, I'll send what info I can get.
>
> cheers,
> Scott
>
>
>
>
>
> _______________________________________________
> Kaboodle-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
>
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
