OpenGl - Zonealarm problem

Hi,

I have a strange problem which occur when I call opengl with the following function,

void EnableOpenGL(HWND hwnd_gl, HDC *hDC, HGLRC *hrc)
{
PIXELFORMATDESCRIPTOR pfd;
int format;

*hDC = GetDC(hwnd_gl);

ZeroMemory(&pfd, sizeof(pfd));
pfd.nSize = sizeof(pfd);
pfd.nVersion = 1;
pfd.dwFlags = PFD_DRAW_TO_WINDOW | PFD_SUPPORT_OPENGL | PFD_DOUBLEBUFFER;
pfd.iPixelType = PFD_TYPE_RGBA;
pfd.cColorBits = 24;
pfd.cDepthBits = 16;
pfd.iLayerType = PFD_MAIN_PLANE;
format = ChoosePixelFormat(*hDC, &pfd);
SetPixelFormat(*hDC, format, &pfd);

*hrc = wglCreateContext(*hDC);
wglMakeCurrent(*hDC, *hrc);
}

When calling EnableOpenGL in win xp everything works just fine, but when I tested in win me
zonealarm alarms about my program. I can’t see anything in the above code that could cause
this? Should add that the program don’t make any external calls at all.
I tried to get an answer from zonelabs without success, so
if someone have any experience from this problem I would appreciate some good pointers.

Not sure if it linked to OpenGL…
I have seen progs made with MS VC++ or .NET studio that connect to microsoft website whithout being asked to, probably to report some interesting facts back to Microsoft…
The MS XP built-in firewall surely let pass such connections.

I don’t think it has to do with the compiler. I first used Mingw, but I had the same result with Borland bcc55. I do belive it’s some reporting issue because it don’t affect the behaviour of the program when I don’t grant contact.

It may be the video driver ? A special reporting mode. What is the server it connects to ?

I can’t trace the connection longer than to my ISP. However, the problem was solved in a somewhat peculiar way. I installed MS Word and after that my program became “silent”? I guess I have to include Word in system requirements:). I don’t see any logic here except a corrupt OS or some adware messing things up.
I will reinstall win me and hopefully the problem will be gone.
Anyway, thanks for your input!

There is some process which ZoneAlerm detect such as virus or something like that, but in a lot of case there is an internal process !

Such as IDLE (IDE for Python programming language)

  • IDLE displays a new message upon startup: some “personal firewall”
    kinds of programs (for example, ZoneAlarm) open a dialog of their
    own when any program opens a socket. IDLE does use sockets, talking
    on the computer’s internal loopback interface. This connection is not
    visible on any external interface and no data is sent to or received
    from the Internet. So, if you get such a dialog when opening IDLE,
    asking whether to let pythonw.exe talk to address 127.0.0.1, say yes,
    and rest assured no communication external to your machine is taking
    place. If you don’t allow it, IDLE won’t be able to start.
    But it’s possible MS’s .NET compiler try to access on the web too :smiley:

This topic was automatically closed 183 days after the last reply. New replies are no longer allowed.