Igor:
        Heya. Log file attached for the Win98 startup. The Win98
PC also has the following problems when I start up Kaboodle without
a LAN connection or modem connection:

1. When Kaboodle starts up, the "Detecting Network" MessageBox
   never goes away.

2. After the log file is generated and I quit, when I try to
   install the RegistrationFile, I get the warning "This PC IS
   Not the Kaboodle Master Node".

        I'll re-run it attached to the LAN to see what the
MasterNode.txt file produces.

thanks,
Scott

On Wed, 13 Nov 2002, Igor Kotelevsky wrote:

> Hello Scott.
> Sorry I don't see these bugs.
> I implemented additional log-file *MasterNode.txt*
> as I wrote in my previous e-mail.
> That file contains information about processing changing Master Node status
> and about GUI part of that changing.
> Please repeat bugs and send me log-files for each bug severally.
> Also I wait the log-file for the bug from your previous e-mail:
> > 2. When I start Kaboodle on a Win98 laptop with just a modem
> > and no network connection, it fails to set itself as the
> > Master.
>
> - Igor
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 12, 2002 11:40 PM
> Subject: Re: [Kaboodle-devel] Re: VPN bug
>
>
> > Igor:
> > Heya. Sorry forgot to mention these other two Master
> > Node bugs, which maybe are all part of the same bug:
> >
> > 3. When I start Kaboodle on PC1 on my LAN, it sets itself as
> >    the Master like it should. Then I start PC2 on my LAN. If
> >    I look in the Network Icon on PC1, it says that the Master
> >    node is PC2. If I look in the Network icon on PC2, it says
> >    that the Master Node is PC1.
> >
> > 4. If I open the PropPanel for PC1, it says that "This PC is
> >    the Master Node". But the checkbox is active. Same thing
> >    for PC2: "This PC is the Master Node" which an active
> >    checkbox. The checkbox should only be active if the PC is
> >    *not* currently the Master Node.
> >
> > Thanks!
> >
> > -Scott
> >
> > On Tue, 12 Nov 2002, Scott C. Best wrote:
> >
> > > Igor:
> > > Thanks for the update. Am testing it out now. Regarding
> > > #1 thru #5, how long would you estimate it would take you to
> > > clean up the code and document the functionality?
> > >
> > > Before that work, though, I'm hoping we can fix the
> > > Master Node functionality. Two known bugs:
> > >
> > > 1. All Kaboodle nodes ping the list of active devices. Only
> > >    the Master Node should do this. Everyone else should just
> > >    sniff. If I change the Master Node, the new Master should
> > >    start pinging.
> > >
> > > 2. When I start Kaboodle on a Win98 laptop with just a modem
> > >    and no network connection, it fails to set itself as the
> > >    Master. At least, when I install the RegistrationFile,
> > >    GetEngaged.exe warns me that "This PC is not the Master".
> > >
> > > thanks,
> > > Scott
> > >
> > > On Tue, 12 Nov 2002, Igor Kotelevsky wrote:
> > >
> > > > Hello Scott.
> > > > Your thing implemented:
> > > > Kaboodle saves the IP address after successful remote connection
> > > > in the registry. When it next try to connect with that partner,
> > > > it try that IP address *first*, on port 4182,
> > > > bypassing a Gnutella completely.
> > > > If it fails to connect, then it returns back to the Gnutella search.
> > > > All my changes are in the CVS server.
> > > >
> > > > Also I want to notice following my estimation:
> > > > 1. Current design of source code not very well to answer the purpose
> > > > of the current functionality of the application.
> > > > There are very many big functions, which has fuzzy functionality.
> > > > 2. Source code has very little documentation.
> > > > 3. There is a big part of code, which was written in style C language,
> > > > but not in style C++ language.
> > > > 4. Indications of many variables look as in "hungarian notation",
> > > > but these real types not conform to that notation.
> > > > 5. Indications of some variables written in MFC style,
> > > > others variables don't has that style,
> > > > even when both of them refer to one class.
> > > > Things #1 - #5 greatly obstruct further accompaniment and development
> > > > of the application.
> > > >
> > > > - Igor
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > Cc: <[EMAIL PROTECTED]>
> > > > Sent: Monday, November 11, 2002 10:35 PM
> > > > Subject: Re: [Kaboodle-devel] Re: VPN bug
> > > >
> > > >
> > > > > Igor:
> > > > > Sorry, didn't see this email until after I sent my
> > > > > email describing the LAN traffic. Am looking forward to you
> > > > > getting to work on this tomorrrow.
> > > > >
> > > > > -Scott
> > > > >
> > > > > On Mon, 11 Nov 2002, Igor Kotelevsky wrote:
> > > > >
> > > > > > Hello Scott.
> > > > > >
> > > > > > First.
> > > > > > The bug you wrote fixed:
> > > > > > > > Looking at my LAN traffic after I hit the "Connect"
> > > > > > > > button, I'm not sure that the discovery is working. I don't
> > > > > > > > see any traffic exchanged between the two endpoints.
> > > > > >
> > > > > > Second.
> > > > > > Now Kaboodle saves the IP address of the latest successful remote
> > > > connection
> > > > > > in the registry.
> > > > > > Please see the registry key
> > > > > > *SOFTWARE\Kaboodle\LatestRemoteConnections*.
> > > > > > It didn't tries that IP addresses *first*, on port 4182,
> > > > > > bypassing Gnutella completely.
> > > > > > I'll implement that later on (I hope this will tomorrow).
> > > > > >
> > > > > > - Igor
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > Cc: <[EMAIL PROTECTED]>
> > > > > > Sent: Monday, November 11, 2002 10:11 AM
> > > > > > Subject: Re: [Kaboodle-devel] Re: VPN bug
> > > > > >
> > > > > >
> > > > > > > Igor:
> > > > > > > Heya. Hope you had a good weekend. Quick questions:
> > > > > > >
> > > > > > > 1. Any progress on the update to Kaboodle to use Partner IP
> > > > > > >    addresses as described below?
> > > > > > >
> > > > > > > 2. Any progress on the Master Node ping problem?
> > > > > > >
> > > > > > > thanks,
> > > > > > > Scott
> > > > > > >
> > > > > > > On Wed, 6 Nov 2002, Scott C. Best wrote:
> > > > > > >
> > > > > > > > Igor:
> > > > > > > > Looking at my LAN traffic after I hit the "Connect"
> > > > > > > > button, I'm not sure that the discovery is working. I don't
> > > > > > > > see any traffic exchanged between the two endpoints. What I
> > > > > > > > *do* see is the request to Gnutella.GetEngaged.Net, and then
> > > > > > > > multiple requests to the IP address in the Partnership file.
> > > > > > > > Then, in my VPN status window, that IP address is now shown
> > > > > > > > as a Gnutella server with a "Handshake OK" status.
> > > > > > > >
> > > > > > > > Here's what I think: every time I successfully make
> > > > > > > > a connection to a VPN partner, I should put their IP address
> > > > > > > > into a file, or registry entry. When I next try to connect
> > > > > > > > with them, I should try those IP addresses *first*, on port
> > > > > > > > 4182, bypassing Gnutella completely. If they fail to connect,
> > > > > > > > I should fall back to a Gnutella search.
> > > > > > > >
> > > > > > > > Of course, the first time I connect with a Partner,
> > > > > > > > I won't have such a file or registry entry. In that case, I
> > > > > > > > should use the IP address in the Partnership file first. If
> > > > > > > > that fails, then fallback to Gnutella.
> > > > > > > >
> > > > > > > > Importantly: those IP address I try should *not* end
> > > > > > > > up in the list of Gnutella servers. I should not see any
> traffic
> > > > > > > > to port 4183 except to machines in the list of Gnutella
> servers.
> > > > > > > >
> > > > > > > > hope this helps,
> > > > > > > >
> > > > > > > > Scott
> > > > > > > >
> > > > > > > > On Wed, 6 Nov 2002, Igor Kotelevsky wrote:
> > > > > > > >
> > > > > > > > > Hello Scott.
> > > > > > > > > I continue VPN bug debugging process.
> > > > > > > > > I know that Kaboodle receives remote network data,
> > > > > > > > > which is *exactly* correct, but GUI 'don't want' to show
> that
> > > > data.
> > > > > > > > > - Igor
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > -------------------------------------------------------
> > > > > > > > This sf.net email is sponsored by: See the NEW Palm
> > > > > > > > Tungsten T handheld. Power & Color in a compact size!
> > > > > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> > > > > > > > _______________________________________________
> > > > > > > > Kaboodle-devel mailing list
> > > > > > > > [EMAIL PROTECTED]
> > > > > > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > 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
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:
> > > To learn the basics of securing your web site with SSL,
> > > click here to get a FREE TRIAL of a Thawte Server Certificate:
> > > http://www.gothawte.com/rd522.html
> > > _______________________________________________
> > > Kaboodle-devel mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> > >
> >
> >
>
>
>
>
Read from registry status of Master Node as *FALSE* and apply that to itself PC. 
CNIDPC::CreateLocal()

Reply via email to