Vince:
I've not been able to update Kaboodle for WinXP SP2; I think
it will require some adjustments to the builtin firewall on SP2.
But to start...are you running it as an Admin user, or as a
regular user?
-Scott
On Sep 24, 2004, at 10:27 AM, Vince L wrote:
Hello!
I
Ken:
Sorry for the very late reply: Kaboodle 0.99c didn't come with
an installer, so it didn't install itself into your Windows system in
the
same way that most commercial Windows applications do (ie, no
DLL's, no Start Menu entries, no Desktop icons, etc.). You can
simply delete the Kaboodle
Dave;
Cool, thanks for the bug report: exactly which version of WinPCap
did you install? I'll try to reproduce the bug here.
Also, which service pack of XP: SP1 or SP2?
-Scott
On Dec 9, 2004, at 7:58 AM, Dave Dyment wrote:
I've installed Kaboodle under Win XP. Initially I had not
to connect, get engaged says it can't find my partner.
I've installed the debug version. What files can I send you which
would help in understanding what I am doing wrong?
Thank you
Dave Dyment
- Original Message - From: Scott Best [EMAIL PROTECTED]
To: Dave Dyment [EMAIL PROTECTED]
Cc
Barrie:
Heya. To connect more than one LAN together using Kaboodle,
you want to utilize the GetEngaged capability of it. Details here:
http://www.kaboodle.org/GetEngaged_setup.html
Hope that helps!
-Scott
We have installed Kaboodle and it is working well. But we have
servers on
David:
Heya. Yes, Kaboodle will default to calling a device a PC
if it can't figure out what else to do with it (e.g., my TiVo).
Any idea what TCP port your vonnage voip adapter uses?
thanks,
Scott
On Mar 3, 2005, at 6:51 PM, David Schlesinger wrote:
Scott and all. I just realized,
David:
Heya. Yes, that's what the make this group private radio
button is for. I don't believe it's been QA'd with the new 1.0 beta's,
but it should work as you describe in 0.99e.
cheers,
Scott
On Mar 4, 2005, at 8:29 PM, David Schlesinger wrote:
Scott and all,
In a previous email to
Heya. The remote install feature of Kaboodle is
still broken; you'd best best off still using FastPush for
that, for now.
sorry,
Scott
I cant get Kaboodle to install to remote pc. I have
admin on it, and have vnc installed locally. I also
have FastPush on here too.
Any ideas? The button
Jeff:
Heya. Which version of Kaboodle were you using? If
using 0.99e, please try our 1.0 pre-release beta:
ftp://ftp.echogent.com/Kaboodle/beta/Kaboodle_BETA_21Mar05.zip
That version will become the 1.0 release, just as soon
as some last minute flyers are nailed down.
-Scott
On Apr
:[EMAIL PROTECTED] Behalf Of Scott
Best
Sent: Tuesday, April 05, 2005 12:06 PM
To: Jeff Reach
Cc: Kaboodle-user@lists.sourceforge.net
Subject: Re: [Kaboodle-user] Fresh Install - Memory Problems.
Jeff:
Heya. Which version of Kaboodle were you using? If
using 0.99e, please try our 1.0 pre
Yucko. Please don't post stuff like this to the list.
thanks,
Scott
On Apr 14, 2005, at 5:59 AM, Vikas Goyal wrote:
Come join my network at hi5!
snip
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds
Sagi:
Heya. So when you try to connect, what error are you seeing?
-Scott
On Apr 29, 2005, at 7:47 PM, Sagi Ronen wrote:
This is not excepting my connection for VPN in Kaboodle:
Internet Address:
demo.kaboodleproxy.com
Password:
demo2005
Sagi
Bill:
Heya. I haven't updated the pictures yet (these were drawn up
using the older version, not the 1.0 release), but please try following
the directions here:
http://www.kaboodle.org/GetEngaged_setup.html
It sounds like you haven't yet registered for GetEngaged. Once
you install
Gary:
Heya. As a workaround to this problem, you can edit
the Kaboodle registry key here:
HKCU/Software/Echogent/Kaboodle:ZebedeePort
It should be set to 11965; just change it to whatever
you want, and Zebedee will be started there.
-Scott
-Scott
On Wed, 11 May 2005, Scott C. Best
Tyler:
Let me look thru the logs...exactly what email address are you
using on both sides of the connection?
The usual reasons for seeing the error you're seeing:
1. The Zebedee server is not running for some reason. If you
go to Setup - GetEngaged, the main screen will show
Tyler:
Also..be sure you're running version 1.01, with the 1.53
version of echoWare. The 1.0 release didn't work correctly
with 1.52 of echoWare (which is used for proxied connections).
cheers,
Scott
On May 26, 2005, at 7:29 PM, Scott Best wrote:
Tyler:
Let me look thru
Jeff:
Nope, doesn't sound like you're doing anything wrong. :)
Let me see if I can reproduce that error here (all of my GetEngaged
connections have been proxied ones, since the 1.01 release).
cheers,
Scott
On Jun 11, 2005, at 3:19 PM, Jeff Cole wrote:
Hi
What a great program -
Wow, that doesn't look good. Exactly what version of
WinPcap do you have installed? You can find the very latest
one here:
http://www.winpcap.org/install/default.htm
That screenshot looks like Kaboodle crashed when
loading the WinPcap DLL. We had a problem with one of
the
Heyaz. Just a quick email that we released the 1.4 version
of echoServer for Windows today (the Linux version should also
be ready before the end of June). It's not yet on most of the
mirrors, but you can get it here:
ftp://ftp.echogent.com/EchoWare/echoServer_1.40_Setup.exe
In
Heyaz. Thanks to Dmitri Popov for the recent NewsForge article
on Kaboodle:
http://software.newsforge.com/article.pl?sid=05/06/23/1843215tid=91
Here's hoping he finds EchoVNC as interesting. ;)
-Scott
---
SF.Net email is
I'm sorry, I thought I wrote back. I'm not seeing exactly
what you're seeing, but I did find something wrong with
direct mode connections that needs to be fixed in the 1.03
release. I'm hoping to get that release out in July.
Sorry for the hassle.
-Scott
On Jun 28, 2005, at
Bill:
Heya. There's a known bug in Kaboodle in that an IEEE-1394 device
in the networking interface list causes a crash. If you can open the
device
manager for your PC and temporarily disable that device, it should then
work correctly.
cheers,
Scott
On Jul 15, 2005, at 9:33
Pietro:
Hello! Sorry for the late reply. Unfortunately, no, there is no easy
way to remove an old entry without resetting the whole list (which can
be done by restarting Kaboodle with the SHIFT key held down).
I'll try to add this very useful feature request to the 1.03 release.
Mathias:
Heya. Here's an installer with no version check:
ftp://ftp.echogent.com/Kaboodle/beta/Kaboodle_27Aug05.exe
Please let me know if it works for you!
cheers,
Scott
On Aug 24, 2005, at 4:02 AM, Mathias Mildenberger wrote:
Hello Kaboodle Developers Helpers,
it seems
Sorry, proxy server was down. Back up now...
-Scott
On Sep 9, 2005, at 3:54 PM, ex qui wrote:
hello
i am running win2k. installed winpcap 3.1, the kaboodle 1.02
1. winpcap is inactive.
2. adding proxy does not work, i am getting sorry... proxy not found
message
here is the
Ted:
Yes, since you're using the demo proxy, the router/firewall settings
won't matter, they all get bypassed easily enough. The times I've seen
Kaboodle not work was because the Partnership files were not installed
on the current Master Node, but rather on another PC that was the
Master
Pete:
Heya. Does it help at all to startup Kaboodle with
the SHIFT key held down?
-Scott
On Oct 4, 2005, at 1:12 PM, Pete Sciacchetano wrote:
I installed kaboodle 1.02 over my .99 on Windows XP.
Now I get the following error when it tries to scan the network.
Instruction 0x01ffa3ab
Warwick:
Heya. Yes, that's a popular request. The problem is, if Kaboodle
allowed
the end user to specify a network range to scan, a lot of user would
set it up
(probably accidently) to scan large parts of the Internet. :) I could
try to limit
the scan range, by requiring users to pick
.
Useful ideas? Keep up the good work! Thanks! Warwick. PS BTW have you
seen
www.networkview.com?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Best
Sent: 23 October 2005 19:03
To: Warwick Grigg
Cc: kaboodle-user@lists.sourceforge.net
Subject
Jeff:
Heya; sorry for the very late replies to your detailed messages.
Yes, there is a bug in Kaboodle's GetEngaged connection that can
cause the connection to be unreliable, especially in direct mode.
If you can connect using KaboodleProxy via a common echoServer,
the overall connection
I've seen this before when printing to an old printer. Do
you have more than one you can try to print to?
-Scott
On Nov 25, 2005, at 2:51 AM, Gordon Clarke wrote:
When I try to print my network diagram, Kaboodle produces a blank
page. Any ideas?
Thanks
Sébastien:
Hello! I am honestly unsure how Kaboodle would run under WinNT 4.0.
If you'd like to try it out for me, try this installer:
ftp://ftp.echogent.com/Kaboodle/beta/Kaboodle_27Aug05.exe
That's the same as 1.02, I just removed the installer restriction.
cheers,
Scott
On
Mr.Disher:
Hello! Try running Kaboodle with WinPCap deinstalled. There's
an incompatibility between the two that we'll fix in the 2.0 release.
cheers,
Scott
On Dec 19, 2005, at 8:42 AM, Mike Disher wrote:
Problems with Kaboodle crashing just after completing the network
discovery on
Mike, Dave:
Sorry for the late reply. Yes, there is a problem with Kaboodle and
WinPcap that causes instability on some systems, especially with 1394
ports. It's not yet resolved. The easiest fix is to deinstall WinPcap
globally,
and move it instead to the installation folder of the
Peter:
First I've heard of this one. :) Have you tried (sorry), downloading
the .ecf file again, in case it got corrupted somehow?
-Scott
PS: We'll be nix'ing this authentication scheme in the 2.0 release.
Turns out, it's not nearly as easy to use as was originally imagined.
On Feb 3,
Jeff:
Good call, thanks. I usually assume things like that will work
correctly,
but it never hurts to be explicit.
If you have any other suggestions/requirements for Kaboodle 2.0,
please let me know. We'll be assigning resources to it in the April
timeframe.
cheers,
Scott
PS:
Valeriy:
Hello! Yes, Kaboodle does it that way intentionally: in the
current release, only one PC can be a Master Node and make
GetEngaged connections. We'll be changing that in 2.0 most
likely.
cheers,
Scott
On Mar 29, 2006, at 10:00 PM, Valeriy Krizhevich wrote:
Hello, all!
John:
Heya. Yes, we turned off the GetEngaged service, as it started to
receive a lot of DoS traffic. We're reworking Kaboodle so that it no
longer requires this.
Kaboodle is still useful for intra-LAN command and control. But for
remote-desktoping across the Internet that
Dr.Jogi:
Hello! We discontinued the GetEngaged site sometime early last year.
It was the recipient of too much malicious traffic, proving (to me)
that such
as system for cryptographic distribution is inherently flawed. :)
When we get around to updating Kaboodle, we will repair
Jan:
Hello! We discontinued the GetEngaged service, at it was attracting
far too much unwanted attention. As most people used Kaboodle's
GetEngaged service for remote support, we focussed instead on getting
EchoVNC working:
http://www.echogent.com/download_echovnc.htm
I hope it
Terry:
Hello! Nope, I never did figure out that error. You're right, some
users worked around it by disabling the 1394 interface completely
from the list of network interfaces (it's not as if 1394 is, really, a
network interface to begin with). But that workaround isn't 100%, and
Kaboodle
Heyaz. As most of you probably know, Kaboodle has been mothballed.
I've updated the main webpage to explain this:
After many years of effort, and through no fault of your own,
Kaboodle has been mothballed. :-( Please feel free to try it out and
suggest improvements, but our
42 matches
Mail list logo
