Oleg:
        Heya. There is a "halfway done" enhancement for the
network-discovery portion of Kaboodle. However, I don't think
it's causing the unhandled exception your seeing. All of my
run-time errors went away when I applied the latest service-pack
to my VC++ installtion.
        Which one are you using?

-Scott

---------- Forwarded message ----------
Date: Thu, 8 Nov 2001 20:24:40 +0300
From: Oleg Lyapin <[EMAIL PROTECTED]>
To: kaboodle-user <[EMAIL PROTECTED]>
Subject: [Kaboodle-user] 8 nov 2001 VPN Status report

8 nov 2001 VPN Status report
-----------------------------

    While wrestling with the bug described above, I found out some
inconsistence
between the source code supplied and workable installation. It looks like an
attempt has been made to enhance the code but the enhancement has not been
completed. The code was left in an unstable state. I need either the stable
code or some help to put it right.
    1. When I launch the compiled exe file an unhandled exception message
appears against the background of the application window. If left as is for
some seconds, the application window begins to display the computer icons.
Displayed are not only the Kaboodle computers, as it occurs with the
installed stable version, but all the LAN computers, and those running
Kaboodle are marked with the EchoFree icon (a small blue rectangle with a
white letter "e"). I suppose this was part of the developers' enhancement
plan.
    2. I traced the error of an unhandled exception. Here is a call stack
for file VPNModule\VPNSocket.cpp :

    CVPNSocket::CreateListener()

    CAsyncSocket::Create(unsigned int 4182, int 1, long 63, const char *
        0x00000000)

    CAsyncSocket::AttachHandle(unsigned int 500, CAsyncSocket *
        0x00b82af0 {CVPNSocket}, int 0)

    CAsyncSocket::LookupHandle(unsigned int 500, int 0)

    pSocket =(CAsyncSocket*)pState->m_pmapSocketHandle->
            GetValueAt((void*)hSocket),
    (!!!!) where (CAsyncSocket*)pState->m_pmapSocketHandle == NULL

    Unhandled exception in EF.exe: 0xC0000005: Access Violation.

    3. One more error. Inside InitInstance(), a special thread is created
obviously to register the EchoFree service. It is done by a call to
AfxBeginThread() supplied with the pointer to the thread function
ServiceThreadProc. The function tries to create a service by a call to
StartServiceCtrlDispatcher and fails. If we inspect the error with
GetLastError() we would get error 1063: "The service process could not
connect to the service controller"

Oleg.


_______________________________________________
Kaboodle-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-user
To UNSUBSCRIBE, click on the above link.


_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to