Hello Scott.
I implemented what you asked.
- Igor
----- Original Message -----
From: "Scott C. Best" <[EMAIL PROTECTED]>
To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
Sent: Sunday, September 01, 2002 8:58 PM
Subject: Re: [Kaboodle-devel] Re: A "Web Config" property tab
> Igor:
>
> The Web-Config tab looks good. I'd like to change two
> things:
>
> 1. If no server type can be detected, I'd like the "detected
> type" to say "unknown".
>
> 2. Similar to my suggestion for the Components tab, I'd like to
> change the layout so it looks like the Main tab of the VNC
> Service icon. That is, explanation text on the left, and
> then the information and buttons on the right. For this
> tab, the explanation text should say: "Kaboodle has detected
> that this device is accepting connections from web-browsers,
> probably so that you can configure its settings. Click the
> "Connect" button and Kaboodle will automatically make the
> connection".
>
> Thanks!
>
> -Scott
>
>
> On Wed, 28 Aug 2002, Scott C. Best wrote:
>
> > Igor:
> > Perfect, thanks! Will test it out shortly.
> >
> > -Scott
> >
> > On Wed, 28 Aug 2002, Igor Kotelevsky wrote:
> >
> > > Hello Scott.
> > > Now above tab searches the strings "Server:" and "realm=" only.
> > > If searching is successful, then tab removes the first and latest
> > > symbol quote (") from found name.
> > > If modem says
> > > - WWW-Authenticate Basic realm="Cayman DSL",
> > > then tab shows
> > > - Cayman DSL.
> > >
> > > - Igor
> > >
> > > ----- Original Message -----
> > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > > Sent: Wednesday, August 28, 2002 8:50 AM
> > > Subject: Re: A "Web Config" property tab
> > >
> > >
> > > > Igor:
> > > > Yes, sorry: "realm=" is correct. My modem says:
> > > >
> > > > WWW-Authenticate Basic realm="Cayman DSL"
> > > >
> > > > That's the exact string.
> > > >
> > > > -Scott
> > > >
> > > > On Tue, 27 Aug 2002, Igor Kotelevsky wrote:
> > > >
> > > > > Hello Scott.
> > > > > I updated latest version of project at the morning.
> > > > > But now I see the CVS error again
> > > > > - cvs [update aborted]: connect to cvs.echogent.com:2401 failed:
> > > > > Connection timed out
> > > > >
> > > > > About modification the "Server:" match to look for.
> > > > > You asked to add searching an additional string.
> > > > > At the beginning of email you said *Ream=*,
> > > > > at the end of email you said *realm=*.
> > > > > Please let me know the exact additional string.
> > > > > Now I added both of them.
> > > > > I'll commit CVS server when it will be successful.
> > > > >
> > > > > - Igor
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > > > > Sent: Monday, August 26, 2002 6:56 PM
> > > > > Subject: Re: A "Web Config" property tab
> > > > >
> > > > >
> > > > > > Igor:
> > > > > > You didn't need to re-add those files back into the
> > > > > > server, you just needed to use the latest version of "EF.rc"
> > > > > > which I commited to the database on Sunday afternoon.
> > > > > >
> > > > > > Also, please mod the "Server:" match to look for
> > > > > > "Ream="..." as well. My appliance doesn't respond with Server,
> > > > > > but it does respond with:
> > > > > >
> > > > > > WWW-Authenticate Basic realm="Cayman DSL"
> > > > > >
> > > > > > If we don't match "Server:" we should grep for the
> > > > > > data after realm="".
> > > > > >
> > > > > > -Scott
> > > > > >
> > > > > > On Mon, 26 Aug 2002, Igor Kotelevsky wrote:
> > > > > >
> > > > > > > Hello Scott.
> > > > > > > The "Web Config" property tab implemented as you asked.
> > > > > > > The top half of tab called "Type of Web server" and it works
like
> > > you
> > > > > wrote:
> > > > > > > - "GET / HTTP/1.0\n\n",
> > > > > > > - looking for "Server:".
> > > > > > > I received
> > > > > > > "Apache/1.3.23 (Unix) (Red-Hat/Linux) PHP/4.0.6"
> > > > > > > for my "appliance" device.
> > > > > > > I didn't test that for "printer" device because I didn't have
such
> > > > > "printer"
> > > > > > > device.
> > > > > > >
> > > > > > > I updated CVS server and found that following files doesn't
exist in
> > > > > > > project:
> > > > > > > res\bitmap2.bmp, res\bmp00005.bmp, res\bmp00003.bmp,
> > > res\bmp00004.bmp,
> > > > > > > res\bmp00002.bmp, res\bmp00001.bmp, res\applianc2_off.bmp,
> > > > > res\bmp00006.bmp.
> > > > > > > Without these files we have next errors:
> > > > > > > Compiling resources...
> > > > > > > C:\PROJECTS\cvs_\Kaboodle\EF.rc (993): error RC2135 : file not
> > > found:
> > > > > > > res\bitmap2.bmp.
> > > > > > > I inserted these files from my latest copy of project.
> > > > > > >
> > > > > > > - Igor
> > > > > > >
> > > > > > >
> > > > > > > ----- Original Message -----
> > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > > > > > > Sent: Saturday, August 24, 2002 3:26 AM
> > > > > > > Subject: Re: A "Web Config" property tab
> > > > > > >
> > > > > > >
> > > > > > > > Igor:
> > > > > > > > What you wrote sounds good. I'd like to change one thing
> > > > > > > > though: lets divide the window into two regions (like we do
for
> > > > > > > > the VPN Status Property Tab). The top half can show server
> > > > > > > > information, and the bottom half can show browser info. In
the
> > > > > > > > bottom half, put what you have done for the default browser
> > > > > > > > selection.
> > > > > > > > In the top half...lets do something like what this project
> > > > > > > > does: "httptype.sf.net". Essentially, it queries the web
server
> > > > > > > > looking for "^Server:". For instance, from a unix command
line,
> > > > > > > > I can "echo 'GET / HTTP/1.0\n' | nc www.kaboodle.org 80" and
then
> > > > > > > > grep for "^Server:". This results in:
> > > > > > > >
> > > > > > > > Server: FrontPage/5.0.2.2510 Signature/2.0 Apache/1.3.26
(Unix)
> > > > > > > >
> > > > > > > > Given that, we can put something into the top half of
> > > > > > > > this panel which shows what sort of http server we've
detected.
> > > > > > > > I'm going to run this httptype perl script against a LinkSys
> > > > > > > > appliance and an HP printer to see what they say.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > > -Scott
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, 22 Aug 2002, Igor Kotelevsky wrote:
> > > > > > > >
> > > > > > > > > Hello Scott.
> > > > > > > > > A "Web Config" property tab implemented.
> > > > > > > > > There is a button "Connect" as you asked.
> > > > > > > > > Also that tab has a group box "Use this Web browser" with
2
> > > > > controls:
> > > > > > > > > 1 - the read-only field, which shows "the full path of the
Web
> > > > > browser",
> > > > > > > > > 2 - the button "Browse...", which allows to change above
path.
> > > > > > > > > The default value of field #1 is "default web browser".
> > > > > > > > > A user can change that browser.
> > > > > > > > > The Kaboodle determines default web browser like next.
> > > > > > > > > It try to find in system registry if there is any
application,
> > > > > > > > > which associated with ".html" file.
> > > > > > > > > If field #1 is empty, then the button "Connect" is grayed
out.
> > > > > > > > >
> > > > > > > > > An "appliance" device always has the property tab "Web
Config".
> > > > > > > > > If a user opens "printer" device icon,
> > > > > > > > > then Kaboodle checks if that device listens the port
number 80.
> > > > > > > > > If that check is successful,
> > > > > > > > > then "printer" device has the property tab "Web Config"
also.
> > > > > > > > >
> > > > > > > > > The CVS server didn't works now
> > > > > > > > > - cvs [update aborted]: connect to cvs.echogent.com:2401
failed:
> > > > > > > Connection
> > > > > > > > > timed out
> > > > > > > > > Therefore I didn't committed my changes.
> > > > > > > > >
> > > > > > > > > - Igor
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > > Cc: "Kaboodle-devel"
<[EMAIL PROTECTED]>
> > > > > > > > > Sent: Thursday, August 22, 2002 4:55 AM
> > > > > > > > > Subject: Re: WinVNC log file
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Igor:
> > > > > > > > > > Sorry for the delay in replying. Here's what I was
hoping
> > > > > > > > > > you could work on while VK works on the ZeBeDee
integration:
> > > > > > > > > >
> > > > > > > > > > For devices discovered to be of type "appliance" I want
> > > > > > > > > > to add a new Property Tab called "Web Config". In that
> > > property
> > > > > > > > > > panel tab, I want there to be a "Connect" button which
> > > activates
> > > > > > > > > > the default browser to connect to the detected HTTP
server's
> > > IP
> > > > > > > > > > address.
> > > > > > > > > >
> > > > > > > > > > I also want to add port-80 detection to printers. That
> > > > > > > > > > is, once a device is discovered to be a printer, I want
to
> > > further
> > > > > > > > > > detect if its listening on port-80 (most new ones are).
If it
> > > is,
> > > > > > > > > > then this printer should also get a "Web Config"
PropPanel
> > > that
> > > > > > > > > > acts in the same way as above.
> > > > > > > > > >
> > > > > > > > > > Thanks!
> > > > > > > > > >
> > > > > > > > > > -Scott
> > > > > > > > > >
> > > > > > > > > > On Mon, 19 Aug 2002, Igor Kotelevsky wrote:
> > > > > > > > > >
> > > > > > > > > > > Hello Scott.
> > > > > > > > > > > I found 2 problems of WinVNC log file.
> > > > > > > > > > >
> > > > > > > > > > > 1. If VNC server starts and finds that WinVNC.log file
> > > already
> > > > > > > exists,
> > > > > > > > > > > then VNC server renames current WinVNC.log file into
> > > > > WinVNC.log.bak
> > > > > > > > > file.
> > > > > > > > > > > If WinVNC.log.bak already exists, then VNC server
removes
> > > > > current
> > > > > > > > > > > WinVNC.log.bak file.
> > > > > > > > > > >
> > > > > > > > > > > 2. I found that only debug level = 9 provides data
about
> > > > > > > unsuccessful
> > > > > > > > > > > connections.
> > > > > > > > > > > But that data isn't sufficient.
> > > > > > > > > > > There absent information about *IP address* of
unsuccessful
> > > > > > > connection -
> > > > > > > > > > > D:\ORL\vss\winvnc\vncServer.cpp : removing
unauthorised
> > > client.
> > > > > > > > > > > I can guess that it was last attempt of connection
only.
> > > > > > > > > > > But that not safely.
> > > > > > > > > > >
> > > > > > > > > > > You can see my changes of in the CVS server.
> > > > > > > > > > > KaboodlePad now shows data like next
> > > > > > > > > > > - Connection Start Time: Mon Aug 19 16:59:46 2002
> > > > > > > > > > > - Connection Success: YES
> > > > > > > > > > > - Connection Source: 127.0.0.1
> > > > > > > > > > > - Connection End Time: Mon Aug 19 16:59:57 2002
> > > > > > > > > > >
> > > > > > > > > > > - Igor
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > > > > > > > > > Cc: "Kaboodle-devel"
<[EMAIL PROTECTED]>
> > > > > > > > > > > Sent: Monday, August 19, 2002 9:43 AM
> > > > > > > > > > > Subject: Re: WinVNC log file
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > Igor:
> > > > > > > > > > > > I hope another debug level gives you what we need: a
> > > > > > > > > > > > timstamp, a viewer IP address, success status.
> > > > > > > > > > > >
> > > > > > > > > > > > On another note, I found a new bug. I installed
Kaboodle
> > > > > > > > > > > > on a machine that has a VNC viewer installed, but
not a
> > > VNC
> > > > > > > > > > > > server. Kaboodle wouldn't let me even "browse" for
the
> > > viewer.
> > > > > > > > > > > > It probably just didn't find VNC in the registry and
so
> > > greys
> > > > > > > > > > > > out every option.
> > > > > > > > > > > >
> > > > > > > > > > > > -Scott
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, 16 Aug 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > You wrote:
> > > > > > > > > > > > > > what they *want*
> > > > > > > > > > > > > > to see in a "VNC log" is one entry per
connection:
> > > > > > > > > > > > > I found that WinVNC.log file doesn't provide
necessary
> > > data
> > > > > > > always.
> > > > > > > > > > > > >
> > > > > > > > > > > > > For example, I made only VNC scan port number.
> > > > > > > > > > > > > I found in the log file only 2 strings:
> > > > > > > > > > > > > - D:\ORL\vss\winvnc\vncSockConnect.cpp : accepted
> > > connection
> > > > > > > from
> > > > > > > > > > > > > 192.168.1.225
> > > > > > > > > > > > > - D:\ORL\vss\winvnc\vncClient.cpp : client
connected :
> > > > > > > 192.168.1.225
> > > > > > > > > (1)
> > > > > > > > > > > > > I can't understand that above connection wasn't
success.
> > > > > > > > > > > > > I can think that above connection continue.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I'll research that problem.
> > > > > > > > > > > > > I'll try to use another *debug level* of WinVnc
registry
> > > > > > > settings.
> > > > > > > > > > > > > (But as result of big debug level, WinVnc log file
will
> > > be
> > > > > very
> > > > > > > > > big).
> > > > > > > > > > > > >
> > > > > > > > > > > > > - Igor
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > To: "Igor Kotelevsky"
<[EMAIL PROTECTED]>
> > > > > > > > > > > > > Cc: "Kaboodle-devel"
> > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > Sent: Thursday, August 15, 2002 9:31 PM
> > > > > > > > > > > > > Subject: Re: WinVNC log file
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > if we stay with #1, then I think we should
modify
> > > > > > > > > > > > > > KaboodlePad.exe. I've asked many users, and what
they
> > > > > *want*
> > > > > > > > > > > > > > to see in a "VNC log" is one entry per
connection:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > ---------------
> > > > > > > > > > > > > > Connection Start Time: 15 Aug 2002, xx:yy:zz
> > > > > > > > > > > > > > Connection Success: YES/NO
> > > > > > > > > > > > > > Connection Source: 192.168.1.12
> > > > > > > > > > > > > > Connection End Time: 15 Aug 2002, xx:yy:zz
> > > > > > > > > > > > > > ---------------
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > So if we stay with #1, we should change how
> > > KaboodlePad
> > > > > > > > > > > > > > "parses" the information that WinVNC writes into
the
> > > log
> > > > > file.
> > > > > > > > > > > > > > There's a lot of gunk in there.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Your modifications to the "current working
directory"
> > > > > > > > > > > > > > are good -- now Kaboodle at least knows where
the file
> > > is
> > > > > > > > > > > > > > reliably. If it can't find the file, please
change the
> > > > > > > messageBox
> > > > > > > > > > > > > > that comes up to read: "Please help Kaboodle
find the
> > > file
> > > > > > > > > > > > > > "WinVNC.log". Right now, it doesn't say what
filename
> > > the
> > > > > user
> > > > > > > > > > > > > > is supposed to browse for.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Thanks!
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Thu, 15 Aug 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > I prefer thing #1 for WinVNC log file.
> > > > > > > > > > > > > > > Real WinVNC log file describes connections
more
> > > fully.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I looked into the source code of WinVnc and
found
> > > > > following.
> > > > > > > > > > > > > > > WinVnc creates log file as "WinVNC.log"
without any
> > > > > path.
> > > > > > > > > > > > > > > Therefore that file creates into the current
working
> > > > > > > directory.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Now before starting WinVnc Kaboodle
> > > > > > > > > > > > > > > - saves current working directory,
> > > > > > > > > > > > > > > - changes current working directory as WinVNC
> > > > > installation
> > > > > > > > > > > directory.
> > > > > > > > > > > > > > > After starting WinVnc Kaboodle restores
previous
> > > working
> > > > > > > > > directory.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > To: "Igor Kotelevsky"
<[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > Cc: "Kaboodle-devel"
> > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > Sent: Thursday, August 15, 2002 9:33 AM
> > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release build
problem
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > You're right that VNC server discovery,
> > > particularly
> > > > > > > > > > > > > > > > in Win98, has become less reliable. As Jeff
> > > suggested,
> > > > > it
> > > > > > > may
> > > > > > > > > > > > > > > > be interesting to try a heap walker or bound
> > > checker
> > > > > to
> > > > > > > see if
> > > > > > > > > > > > > > > > we can isolate the cause.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On a related subject, I was hoping you could
> > > modify
> > > > > > > > > > > > > > > > the behavior of the "log VNC usage" button.
Right
> > > now
> > > > > all
> > > > > > > it
> > > > > > > > > > > > > > > > does is set the registry entry for WinVNC.
Problem
> > > is,
> > > > > > > when
> > > > > > > > > > > > > > > > I hit "View Log" it never finds the file, I
always
> > > > > have to
> > > > > > > > > > > > > > > > browse for it. I was hoping you could do one
of
> > > two
> > > > > > > things:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 1. Have the WinVNC log be written into the
> > > > > installation
> > > > > > > dir,
> > > > > > > > > > > > > > > > and have ViewLog always look there first.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > 2. Alternatively, don't use WinVNC log at
all.
> > > > > Kaboodle
> > > > > > > has
> > > > > > > > > > > > > > > > its own debug info now that's written to
> > > > > > > > > VncServerSessionLog
> > > > > > > > > > > > > > > > when built in Debug mode. Perhaps we
could
> > > output
> > > > > some
> > > > > > > (not
> > > > > > > > > > > > > > > > all) of that info into a .txt file.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > The intent with logging was for the user to
be
> > > able to
> > > > > > > > > > > > > > > > find out who connected, or tried and failed
to
> > > > > connect, to
> > > > > > > > > their
> > > > > > > > > > > > > > > > VNC server. All it needs to show are
timestamps,
> > > IP
> > > > > > > address of
> > > > > > > > > > > > > > > > the Viewer, and connection status (failed,
> > > connected,
> > > > > > > > > > > disconnected,
> > > > > > > > > > > > > > > > etc). Unfortunately, the debug info shows a
whole
> > > lot
> > > > > more
> > > > > > > > > than
> > > > > > > > > > > > > > > > just that.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Perhaps we could combine both: if the user
has
> > > "Log
> > > > > > > > > > > > > > > > VNC usage" we could both set the debug flag
in the
> > > VNC
> > > > > > > > > registry,
> > > > > > > > > > > > > > > > *and* record Kaboodle-detected info. So if
someone
> > > > > > > connected
> > > > > > > > > > > > > > > > directly, we could show that from grep'ing
the VNC
> > > log
> > > > > > > file.
> > > > > > > > > > > > > > > > If someone connected via Kaboodle, we could
show
> > > that
> > > > > > > > > directly.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Eager for your thoughts. I suppose getting
#1 to
> > > work
> > > > > > > > > > > > > > > > above would be sufficient for the needs of
0.90.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Wed, 14 Aug 2002, Igor Kotelevsky wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > > I see that VNC server discovery has become
less
> > > > > > > reliable.
> > > > > > > > > > > > > > > > > That unreliability shows itself in release
> > > build,
> > > > > > > > > particularly
> > > > > > > > > > > in
> > > > > > > > > > > > > Win98
> > > > > > > > > > > > > > > OS.
> > > > > > > > > > > > > > > > > It isn't possible that one of my recent
updates
> > > > > broke
> > > > > > > > > > > something -
> > > > > > > > > > > > > > > > > I didn't changed something pertaining to
that
> > > part.
> > > > > > > > > > > > > > > > > Here is what I have found.
> > > > > > > > > > > > > > > > > Now VNC discovery sometimes cannot create
a
> > > client
> > > > > > > socket
> > > > > > > > > for
> > > > > > > > > > > scan
> > > > > > > > > > > > > port.
> > > > > > > > > > > > > > > > > I see the system error's code 10055.
> > > > > > > > > > > > > > > > > That error has following text
> > > > > > > > > > > > > > > > > "An operation on a socket could not be
performed
> > > > > because
> > > > > > > > > > > > > > > > > the system lacked sufficient buffer space
or
> > > because
> > > > > a
> > > > > > > queue
> > > > > > > > > was
> > > > > > > > > > > > > full".
> > > > > > > > > > > > > > > > > It looks like another thread
simultaneously
> > > makes
> > > > > big
> > > > > > > lot of
> > > > > > > > > > > socket
> > > > > > > > > > > > > > > work.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Here is what I can implement for the
button
> > > "Check
> > > > > > > Again"
> > > > > > > > > only.
> > > > > > > > > > > > > > > > > If VNC server discovery receives above
error
> > > code
> > > > > 10055,
> > > > > > > > > > > > > > > > > then it waits 0.3 second and repeats the
> > > operation
> > > > > one
> > > > > > > more
> > > > > > > > > > > time.
> > > > > > > > > > > > > > > > > It seems to me that the button "Check
Again"
> > > will be
> > > > > > > more
> > > > > > > > > > > reliable.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > I cannot implement above check error code
10055
> > > for
> > > > > VNC
> > > > > > > > > server
> > > > > > > > > > > > > discovery
> > > > > > > > > > > > > > > > > at the first start Kaboodle (empty
registry
> > > > > setting).
> > > > > > > > > > > > > > > > > It seems to me that it is uselessly in
that
> > > case.
> > > > > > > > > > > > > > > > > We have to find and fix the reason of
error code
> > > > > 10055.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > To: "Igor Kotelevsky"
> > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > Cc: "Kaboodle-devel"
> > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > Sent: Wednesday, August 14, 2002 8:37 AM
> > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release
build
> > > problem
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > > > Your changes look good. I noticed one
thing
> > > > > though: it
> > > > > > > > > > > > > > > > > > seems as if the VNC server discovery has
> > > become
> > > > > less
> > > > > > > > > reliable
> > > > > > > > > > > > > > > > > > since you made these changes. Sometimes
it
> > > takes
> > > > > two
> > > > > > > or
> > > > > > > > > three
> > > > > > > > > > > > > > > > > > "Check Again" tries for it to find the
VNC
> > > server
> > > > > one
> > > > > > > one
> > > > > > > > > of
> > > > > > > > > > > > > > > > > > my machines. It used to catch it right
away.
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > This is in release build, latest stuff.
Is it
> > > > > possible
> > > > > > > > > > > > > > > > > > that one of the recent updates broke
> > > something?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Tue, 13 Aug 2002, Igor Kotelevsky
wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > I inserted exact your texts
> > > > > > > > > > > > > > > > > > > into the top of "VNC setup" tab in the
> > > device
> > > > > icon.
> > > > > > > > > > > > > > > > > > > Now only the "Check Again" button is
active
> > > > > > > > > > > > > > > > > > > if VNC connection is not possible.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Also I found that Kaboodle saves
special
> > > debug
> > > > > data
> > > > > > > into
> > > > > > > > > the
> > > > > > > > > > > log
> > > > > > > > > > > > > > > files
> > > > > > > > > > > > > > > > > > > - KaboodleNIDPreAlpha.xml,
> > > > > > > > > > > > > > > > > > > - Kaboodle_Dbg.htm,
> > > > > > > > > > > > > > > > > > > - Gnutella.log.
> > > > > > > > > > > > > > > > > > > That files appeared both in debug and
> > > release
> > > > > > > builds.
> > > > > > > > > > > > > > > > > > > Now that files appear in debug build
only.
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > To: "Igor Kotelevsky"
> > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > Cc: "Kaboodle-devel"
> > > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > Sent: Tuesday, August 13, 2002 8:28 AM
> > > > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release
build
> > > > > problem
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > > > > > Good, thanks; VNC tunneling is
working
> > > again
> > > > > > > nicely.
> > > > > > > > > > > > > > > > > > > > Only bug I can find right now: when
I'm on
> > > PC1
> > > > > and
> > > > > > > I
> > > > > > > > > open
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > device icon for PC2 (which is not
running
> > > a
> > > > > VNC
> > > > > > > > > service)
> > > > > > > > > > > it
> > > > > > > > > > > > > > > > > > > > says at the top "when connecting to
> > > <b>PC2</b>
> > > > > > > from
> > > > > > > > > > > > > <b>PC1></b>
> > > > > > > > > > > > > > > > > > > > use these settings". It *used* to
say "PC2
> > > is
> > > > > not
> > > > > > > > > running
> > > > > > > > > > > a
> > > > > > > > > > > > > > > > > > > > VNC Service" and only the "Check
Again"
> > > button
> > > > > was
> > > > > > > > > active.
> > > > > > > > > > > > > > > > > > > > Did that get changed somehow?
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Mon, 12 Aug 2002, Igor Kotelevsky
> > > wrote:
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > > > > > > I found next VNC problem:
> > > > > > > > > > > > > > > > > > > > > - PC1 run independent VNC service;
> > > > > > > > > > > > > > > > > > > > > - PC1 run Kaboodle with option
"Enable
> > > > > Kaboodle
> > > > > > > > > Tunnels
> > > > > > > > > > > for
> > > > > > > > > > > > > > > VNC";
> > > > > > > > > > > > > > > > > > > > > - I open PC1 device icon on PC2
machine
> > > and
> > > > > > > > > > > > > > > > > > > > > try to start up "Connect through
> > > Kaboodle".
> > > > > That
> > > > > > > > > > > connection
> > > > > > > > > > > > > > > failed.
> > > > > > > > > > > > > > > > > > > > > I found conflict in port number:
> > > > > > > > > > > > > > > > > > > > > - independent VNC service on PC1
listen
> > > some
> > > > > > > port
> > > > > > > > > > > number.
> > > > > > > > > > > > > > > > > > > > > That number by default is 5900.
> > > > > > > > > > > > > > > > > > > > > (it is number by default);
> > > > > > > > > > > > > > > > > > > > > - Kaboodle on PC1 reads port
number of
> > > VNC
> > > > > > > viewer
> > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > uses it for start up VNC
viewer,...
> > > > > > > > > > > > > > > > > > > > > That number by default is 5900
also.
> > > > > > > > > > > > > > > > > > > > > Now that bug fixed.
> > > > > > > > > > > > > > > > > > > > > Before start "Connection through
> > > Kaboodle"
> > > > > > > > > > > > > > > > > > > > > Kaboodle on the viewer side make
check:
> > > > > > > > > > > > > > > > > > > > > if there is running independent
VNC
> > > server
> > > > > on
> > > > > > > the
> > > > > > > > > port
> > > > > > > > > > > > > number
> > > > > > > > > > > > > > > > > > > N_VNC_SERVER,
> > > > > > > > > > > > > > > > > > > > > then port for start VNC viewer
cannot be
> > > > > same as
> > > > > > > > > > > > > N_VNC_SERVER
> > > > > > > > > > > > > > > > > > > > > and same as port, which use for
tunnel.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > I continue test Kaboodle in
release and
> > > > > debug
> > > > > > > mode.
> > > > > > > > > > > > > > > > > > > > > I see that Kaboodle works both in
> > > release
> > > > > and
> > > > > > > debug
> > > > > > > > > > > mode.
> > > > > > > > > > > > > > > > > > > > > If you will find any VNC bug,
please
> > > send me
> > > > > > > next
> > > > > > > > > log
> > > > > > > > > > > files
> > > > > > > > > > > > > > > > > > > > > - SessionVncServerLog.txt,
> > > > > > > > > > > > > > > > > > > > > - SessionVncViewerLog.txt,
> > > > > > > > > > > > > > > > > > > > > - ViewerThreadLog.txt
> > > > > > > > > > > > > > > > > > > > > for both Kaboodles.
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > About port number 7000.
> > > > > > > > > > > > > > > > > > > > > Kaboodle always listens TCP
connection
> > > on
> > > > > port
> > > > > > > > > number
> > > > > > > > > > > 7000.
> > > > > > > > > > > > > > > > > > > > > Please see
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > >
http://www.geocrawler.com/archives/3/16728/2002/5/0/8657977/
> > > > > > > > > > > > > > > > > > > > > If PC1 need to start independent
VNC
> > > server
> > > > > on
> > > > > > > PC2,
> > > > > > > > > > > > > > > > > > > > > then PC1 send special message to
the PC2
> > > on
> > > > > port
> > > > > > > > > number
> > > > > > > > > > > > > 7000.
> > > > > > > > > > > > > > > > > > > > > Also that port used for
initialization
> > > "File
> > > > > > > > > Transfer".
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > > > > > From: "Scott C. Best"
<[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > > > To: "Igor Kotelevsky"
> > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > > > Cc: "Kaboodle-devel"
> > > > > > > > > > > <[EMAIL PROTECTED]>;
> > > > > > > > > > > > > > > > > "mailbox"
> > > > > > > > > > > > > > > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > > > > > > > > > > > > > Sent: Sunday, August 11, 2002 9:17
PM
> > > > > > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel]
Release
> > > build
> > > > > > > problem
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Igor:
> > > > > > > > > > > > > > > > > > > > > > I agree that the Release builds
are
> > > not
> > > > > > > working
> > > > > > > > > right
> > > > > > > > > > > > > > > > > > > > > > now. However, even in Debug
mode, I
> > > cannot
> > > > > get
> > > > > > > VNC
> > > > > > > > > > > > > tunneling
> > > > > > > > > > > > > > > > > > > > > > to work anymore. So I used
WinCVS to
> > > get a
> > > > > > > code
> > > > > > > > > > > snapshot
> > > > > > > > > > > > > from
> > > > > > > > > > > > > > > > > > > > > > August-8, so that VK's NID-synch
bugs
> > > were
> > > > > not
> > > > > > > > > > > involved.
> > > > > > > > > > > > > Still
> > > > > > > > > > > > > > > > > > > > > > doesn't work. Details:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > 1. I'm running the VNC server on
PC1,
> > > > > WinNT,
> > > > > > > debug
> > > > > > > > > > > build.
> > > > > > > > > > > > > > > > > > > > > > No VNC service is active,
Kaboodle is
> > > > > setup to
> > > > > > > > > > > "autostart
> > > > > > > > > > > > > if
> > > > > > > > > > > > > > > > > > > > > > needed". On PC2, running Win2k,
in the
> > > > > Device
> > > > > > > Icon
> > > > > > > > > for
> > > > > > > > > > > > > PC1, in
> > > > > > > > > > > > > > > > > > > > > > the VNC Setup tab, "Connect
Directly"
> > > is
> > > > > > > greyed
> > > > > > > > > out.
> > > > > > > > > > > Since
> > > > > > > > > > > > > > > > > > > > > > no server is running on PC1,
both
> > > choices
> > > > > > > should
> > > > > > > > > be
> > > > > > > > > > > > > active.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > 2. Then on PC2 I open the VNC
Service
> > > > > Icon,
> > > > > > > and go
> > > > > > > > > to
> > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > list of viewers. I enter the
password
> > > for
> > > > > PC1,
> > > > > > > hit
> > > > > > > > > > > > > connect. I
> > > > > > > > > > > > > > > > > > > > > > immediately get an error from
VNC
> > > "Cannot
> > > > > > > connect
> > > > > > > > > to
> > > > > > > > > > > > > server".
> > > > > > > > > > > > > > > > > > > > > > Over on PC1, the VNC server icon
is in
> > > my
> > > > > > > service
> > > > > > > > > > > tray,
> > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > it's lit-up, indicating it's
receiving
> > > a
> > > > > > > > > connection.
> > > > > > > > > > > The
> > > > > > > > > > > > > log
> > > > > > > > > > > > > > > > > > > > > > file on PC1 has just two lines:
> > > "BEGIN:
> > > > > > > > > > > StartVNCServer"
> > > > > > > > > > > > > and
> > > > > > > > > > > > > > > > > > > > > > "StartVNCServer: Ok start
Independent
> > > > > > > VNCserver
> > > > > > > > > port
> > > > > > > > > > > > > number
> > > > > > > > > > > > > > > > > > > > > > 5900". I look at the tcpdump
traffic
> > > on my
> > > > > > > LAN,
> > > > > > > > > and
> > > > > > > > > > > see
> > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > > > > > > > following. When I hit connect:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > 16:36:57.351343
192.168.123.134.1189 >
> > > > > > > > > > > > > 192.168.123.130.7000: S
> > > > > > > > > > > > > > > > > > > > > > 2008127198:2008127198(0) win
16384
> > > <mss
> > > > > > > > > > > > > 1460,nop,nop,sackOK>
> > > > > > > > > > > > > > > (DF)
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > In the above, PC1 is .130 and
PC2 is
> > > .134.
> > > > > Why
> > > > > > > > > would
> > > > > > > > > > > port
> > > > > > > > > > > > > > > > > > > > > > 7000 be involved in a VNC
tunnel? I
> > > wait a
> > > > > few
> > > > > > > > > seconds
> > > > > > > > > > > to
> > > > > > > > > > > > > see
> > > > > > > > > > > > > > > > > which
> > > > > > > > > > > > > > > > > > > > > > port the VNC viewer on PC2 is
trying
> > > to
> > > > > use.
> > > > > > > Keep
> > > > > > > > > in
> > > > > > > > > > > mind
> > > > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > "Connect Directly" was not a
valid
> > > choice:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > 16:36:57.807921
192.168.123.134.1190 >
> > > > > > > > > > > > > 192.168.123.130.5900: S
> > > > > > > > > > > > > > > > > > > > > > 2008283092:2008283092(0) win
16384
> > > <mss
> > > > > > > > > > > > > 1460,nop,nop,sackOK>
> > > > > > > > > > > > > > > (DF)
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > So PC2 has tried to connect
directly,
> > > even
> > > > > > > though
> > > > > > > > > > > > > > > > > > > > > > Kaboodle on PC1 has opened a
tunnel
> > > and
> > > > > > > connected
> > > > > > > > > > > > > successfully
> > > > > > > > > > > > > > > > > > > > > > with the VNC server (which is
why the
> > > VNC
> > > > > icon
> > > > > > > in
> > > > > > > > > the
> > > > > > > > > > > > > service
> > > > > > > > > > > > > > > > > > > > > > tray is lit-up bright white).
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > 3. I then try connecting again
from
> > > PC2. I
> > > > > get
> > > > > > > a
> > > > > > > > > > > Kaboodle
> > > > > > > > > > > > > > > error
> > > > > > > > > > > > > > > > > > > > > > saying "You already have a
VNC
> > > session
> > > > > > > > > connected
> > > > > > > > > > > with
> > > > > > > > > > > > > PC1".
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > Thanks for looking into this. I
was
> > > very
> > > > > > > surprised
> > > > > > > > > > > that
> > > > > > > > > > > > > > > > > > > > > > port-7000 got involved with this
> > > > > connection
> > > > > > > > > attempt.
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > -Scott
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > On Fri, 9 Aug 2002, Igor
Kotelevsky
> > > wrote:
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > Hello Scott.
> > > > > > > > > > > > > > > > > > > > > > > I have tested all my changes
in both
> > > > > debug
> > > > > > > and
> > > > > > > > > > > release
> > > > > > > > > > > > > > > builds.
> > > > > > > > > > > > > > > > > > > > > > > All worked.
> > > > > > > > > > > > > > > > > > > > > > > Then I merged my code with CVS
code.
> > > > > > > > > > > > > > > > > > > > > > > Now Kaboodle works in debug
builds
> > > only.
> > > > > > > > > > > > > > > > > > > > > > > There is a problem in realise
> > > build -
> > > > > > > > > > > > > > > > > > > > > > > Kaboodle starts, but a user
don't
> > > see
> > > > > GUI.
> > > > > > > > > > > > > > > > > > > > > > > I found a problem.
> > > > > > > > > > > > > > > > > > > > > > > Please look into the function
int
> > > > > > > > > > > > > CEFController::Start().
> > > > > > > > > > > > > > > > > > > > > > > There is a line
> > > > > > > > > > > > > > > > > > > > > > > while
> > > > > > > (!m_pNetworkManager->bStartUpFinished);
> > > > > > > > > > > > > > > > > > > > > > > It seems to me that there is
> > > infinite
> > > > > loop
> > > > > > > in
> > > > > > > > > > > realize
> > > > > > > > > > > > > build.
> > > > > > > > > > > > > > > > > > > > > > > The member
> > > > > > > m_pNetworkManager->bStartUpFinished
> > > > > > > > > > > > > > > > > > > > > > > sets as "TRUE" in the function
> > > > > > > > > > > > > > > > > > > > > > > int
CNetworkManager::OnStartup(DWORD
> > > > > > > > > nIDController,
> > > > > > > > > > > > > CGUID
> > > > > > > > > > > > > > > > > > > KaboodleID).
> > > > > > > > > > > > > > > > > > > > > > > It seems like that function
don't
> > > works
> > > > > > > > > correctly in
> > > > > > > > > > > > > release
> > > > > > > > > > > > > > > > > build.
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > > - Igor
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > >
> -------------------------------------------------------
> > > > > > > > > > > > > > > > > > > > > > > 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: Jabber - The world's fastest growing
> > real-time communications platform! Don't just IM. Build it in!
> > http://www.jabber.com/osdn/xim
> > _______________________________________________
> > Kaboodle-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> >
>
>
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
