Hi Scott No problem, I have just joined a few open source community projects and some are clearly forgotten about, I have some posts several months old never answered either way. I can certainly sympathize with having a busy week ATM :) My original email had the MS debug report it sends to Microsoft attached, can reattach if it is any help. I am very willing to run a debug-build. Do I need to download this, or is it an install option ? BTW - the install went OK, and the first 2 runs. After that, the program crashes straight after startup.
Cheers Andy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott C. Best Sent: Friday, 9 September 2005 9:19 AM To: Andrew Kozak Cc: kaboodle-user@lists.sourceforge.net Subject: Re: [Kaboodle-user] Win XP Problem Andrew: Sorry for missing your post; it's been a busy week. There is a bug in Kaboodle with some user's WinXP platforms. It has to do with the WinPcap packet sniffer we use for passive network population detection. On WinXP, some interfaces (eg, the IEEE-1394 interface) are identified as network interfaces, but WinPcap throws an error when Kaboodle tries to attach to it. By disabling that network interface, or by de-installing the WinPcap DLL, some users have gotten Kaboodle working on otherwise-failing WinXP systems. But clearly, that's not a good longterm solution. We haven't isolated the problem here yet -- all of our development WinXP systems don't display the bug. If you'd be willing to run a "debug" build and email the resulting log files, that'd help us a lot. cheers, Scott On Tue, 23 Aug 2005, Andrew Kozak wrote: > Hi All > > > > I installed Kaboodle on my AMD64 Laptop with Windows XP on it this morning, > and get the MS error reporting service every time I attempt to start the > program. The gui fires up, but then the LAN picture flickers a couple of > times and the error report comes up and shuts Kaboodle down. It did work the > second time I started it though, and discovered the LAN nicely, however, > every attempt since has been a failure. Is there any issues using a wireless > nic? Is there any other information I can include to make tracking the > problem easier? > > I have attached the MS error report. > > Cheers > > Andy Kozak > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Kaboodle-user mailing list Kaboodle-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kaboodle-user To UNSUBSCRIBE, click on the above link. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Kaboodle-user mailing list Kaboodle-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kaboodle-user To UNSUBSCRIBE, click on the above link.
