>Hi Ed!
>
>Well, I coded this thing up and while my previous code always produced a "not connected" response, Using "InternetGetConnectedState" always produces a "connected" response!
>
>I am behind a Proxy, here, but the flag value returns "2" (LAN).
>After disconnecting the network cable, turning off the Proxy in Control Panel and rebooting the machine, the results were exactly the same - now I'm confused!
>
>Could this (and the previous error for that matter) bear any relation to the fact that IE is NOT my default browser (although it is installed)? Where could I find some more information on WININET.DLL and it's internals, including where it goes to look for the information before generating the response?
>
>Sorry to be such a bother, but I am under something of a deadline here.
>

I don't know what to tell you here; I just tried it on two of my systems here, with the following results:

Connected via modem to net - return 1, nFlags = 1
Connected via Proxy Server 2.0, ISP DNS - return 1, nFlags = 4
Connected via Proxy Server 2.0, Server DNS - return 1, nFlags = 2
Not connected, no dial in progress, no proxy - return 0, nFlags = 0
Not connected, dial in progress - return 1, nFlags = 1
Not connected, dial failed (5 busys) - return 1, nFlags = 8

I do run IE 4.0 as my default browser. I'm running Win98 4.10.1998, IE 4.01 SP1 (4.72.3110, SP1, 2636, 2375 patches applied). I also tried an NT box; NT Server 4.0 Build 1381 SP3, with the same IE4 revision. Tests were run under VFP 5.0a Build 415.