Hello Scott. The log file WithAOL\NidLog.txt (connection via AOL and crash) shows following. The latest 3 strings are next: - StartOSDetection: BEGIN - AutoDetectDeviceType: BEGIN - AutoDetectDeviceType: 172.194.188.224 It seems to me that crash has occurred - inwardly to the function DWORD CSearchNetworkManager::AutoDetectDeviceType(...), or - inwardly to some function, which called from AutoDetectDeviceType(). (The log process is made so that if function ends then we see something like - AutoDetectDeviceType: BEGIN ... - AutoDetectDeviceType: END) I have added enhanced information into the file NidLog.txt. Please update latest CVS source and run Kaboodle in debug build. Please send to me NidLog.txt.
You wrote: > ...Perhaps the OS detection process is not being bypassed correctly? Yes. From above log file I see, that OS detection process starts in case of connection via AOL. I didn't found Kaboodle's source code, which detect a modem. Now I don't know as to detect a modem. I'll try to search that. - Igor ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]> Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel" <[EMAIL PROTECTED]> Sent: Tuesday, July 30, 2002 8:44 AM Subject: Re: Bug Report, 22 July > Igor: > Hello! I ran the latest CVS code in debug mode on my > Win98 laptop. It crashed whenever I ran it with AOL connected. > The attached zipfile has three log file sets in there. > One with no-AOL and no-LAN connection (no crash), one with > a LAN connection (no crash) and one with AOL (crash). The AOL > case looks like it does in fact start running OS detection. > I know we agreed that the network detection process > should be bypassed when Kaboodle connects to the Internet via > a modem. Perhaps the OS detection process is not being bypassed > correctly? > > -Scott > > On Mon, 29 Jul 2002, Igor Kotelevsky wrote: > > > Hello Scott. > > I don't found any information about error. > > Please update latest CVS source and run Kaboodle in debug build. > > You will find new log file - NidLog.txt. > > Please send that file to me. > > > > The log files vpnsocket1.txt, vpnsocket2.txt now generate in Kaboodle > > install directory. > > That files appeared in pre-Akmosoft period. > > > > - Igor > > > > > > ----- Original Message ----- > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel" > > <[EMAIL PROTECTED]> > > Sent: Friday, July 26, 2002 8:32 PM > > Subject: Re: Bug Report, 22 July > > > > > > > Igor: > > > The Kaboodle log files are attached. I didn't even > > > know Kaboodle was generating these. :) Can we write them > > > into the Kaboodle install directory instead of C:\.? > > > > > > Please let me know what progress you make on this > > > error source. It's holding up the public release of 0.90. > > > > > > -Scott > > > > > > On Fri, 26 Jul 2002, Igor Kotelevsky wrote: > > > > > > > Hello Scott. > > > > The output files you have attached were really short. > > > > Please attach the Kaboodle's log files vpnsocket1.txt, vpnsocket2.txt. > > > > You can find these files in the directory C:\. > > > > Please remove these files before your test. > > > > > > > > The description of "A fatal exception OE" can be finding on > > > > > > http://support.microsoft.com/default.aspx?scid=/support/windows/topics/error > > > > msg/kbfe0e.asp > > > > > > > > - Igor > > > > > > > > ----- Original Message ----- > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > To: "mailbox" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > Sent: Friday, July 26, 2002 10:57 AM > > > > Subject: Re: Bug Report, 22 July > > > > > > > > > > > > > VK, Igor: > > > > > > > > > > I tested this again tonight. I installed VC++ on my > > > > > poor little Win98 laptop, applied the latest SP5 service pack. > > > > > I compiled the latest source, connected to AOL, and started > > > > > the debug. Output attached (I don't know why it's so short, > > > > > but it is). > > > > > > > > > > Kaboodle starts, and the "Detecting Network" message > > > > > box comes up. At this point, in my opinion, it should detect > > > > > that it's on a modem and give up. It doesn't. About half a > > > > > minute later, "Classifying New Devices" comes up. About 10 > > > > > seconds later, Windows then blue screens with the message: > > > > > > > > > > "A fatal exception OE has occurred at 0028:C004A08B in VXD NDIS(01) + > > > > > 00002F1F. The current application will be terminated." > > > > > > > > > > The second time I tried this, the debug output looks > > > > > like it started the VNC auto-detection before it crashed. > > > > > > > > > > Any advice appreciated. > > > > > > > > > > -Scott > > > > > > > > > > > > > > > On Mon, 22 Jul 2002, Scott C. Best wrote: > > > > > > > > > > > > > > > > > I tested Kaboodle on a un-networked Win98 machine which > > > > > > uses AOL as the dialup ISP. I connected to AOL, then started > > > > > > Kaboodle, and it blue-screen'd the PC when it got to the > > > > > > "Classifying Devices" part of startup. > > > > > > Ouch. > > > > > > > > > > > > Is it possible to restrict network detection to use only > > > > > > LAN-based interfaces, as opposed to modem-interfaces? I can't > > > > > > imagine that we'd ever want to ping 255 devices on one of AOL's > > > > > > subnets... > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
