The RasDial function establishes a RAS connection between a RAS client and a RAS server. The connection data includes callback and user authentication information.
DWORD RasDial(
LPRASDIALEXTENSIONS lpRasDialExtensions, |
// pointer to function extensions data |
LPTSTR lpszPhonebook, |
// pointer to full path and filename of phone-book file |
LPRASDIALPARAMS lpRasDialParams, |
// pointer to calling parameters data |
DWORD dwNotifierType, |
// specifies type of RasDial event handler |
LPVOID lpvNotifier, |
// specifies a handler for RasDial events |
LPHRASCONN lphRasConn |
// pointer to variable to receive connection handle |
); |
Points to a RASDIALEXTENSIONS structure that specifies a set of RasDial extended features to enable. If you do not need to enable any of the extensions, set this parameter to NULL.
Windows 95: This parameter is ignored. Dial-up networking stores
phone-book entries in the registry rather than in a phone-book file.
The caller must set the RASDIALPARAMS structure’s dwSize member
to the sizeof(RASDIALPARAMS) to identify the version of the structure
being passed.
Value |
Meaning |
0xFFFFFFFF |
The lpvNotifier parameter is a handle to a window to receive progress notification messages. In a progress notification message, wParam is the equivalent of the rasconnstate parameter of RasDialFunc and RasDialFunc1, and lParam is the equivalent of the dwError parameter of RasDialFunc and RasDialFunc1. The progress notification message uses a system registered message code. You can obtain the value of this message code as follows: {UINT unMsg = RegisterWindowMessageA( RASDIALEVENT ); if (unMsg == 0) unMsg = WM_RASDIALEVENT; }
|
0 |
The lpvNotifier parameter points to a RasDialFunc callback function. |
1 |
The lpvNotifier parameter points to a RasDialFunc1 callback function. |
2 |
Windows NT: The lpvNotifier parameter points to a RasDialFunc2 callback function. |
If this parameter is not NULL, RasDial sends the window a message, or calls the callback function, for each RasDial event. Additionally, the RasDial call operates asynchronously: RasDial returns immediately, before the connection is established, and communicates its progress via the window or callback function.
If lpvNotifier is NULL, the RasDial call operates synchronously: RasDial does not return until the connection attempt has completed successfully or failed.
If lpvNotifier is not NULL, notifications to the window or callback function can occur at any time after the initial call to RasDial. Notifications end when one of the following events occurs:
The callback notifications are made in the context of a thread captured during
the initial call to RasDial.
If the function succeeds, the immediate return value is zero. In addition, the function stores a handle to the RAS connection into the variable pointed to by lphRasConn.
If the function fails, the immediate return value is a nonzero error value, either from the set listed in the RAS header file or ERROR_NOT_ENOUGH_MEMORY.
Errors that occur after the immediate return can be detected by RasGetConnectStatus. Data is available until an application calls RasHangUp to hang up the connection.
An application must eventually call RasHangUp whenever a non-NULL connection handle is stored into *lphRasConn. This applies even if RasDial returns a nonzero (error) value.
An application can safely call RasHangUp from a RasDial notifier callback function. If this is done, however, the hangup does not occur until the routine returns.
To specify that RasDial should enter a RASCS_CallbackSetByCaller state,
set lpRasDialParams->szCallbackNumber to "*" on the
initial call to RasDial. When your notification handler is called with
this state, you can set the the callback number to a number supplied by the
user.
RasDialDlg, RasDialFunc, RasDialFunc1, RasDialFunc2, RasGetConnectStatus, RasHangUp, RASDIALEXTENSIONS, RASDIALPARAMS, WM_RASDIALEVENT
file: /Techref/os/win/api/win32/func/src/f69_32.htm, 10KB, , updated: 2000/4/7 12:19, local time: 2024/9/2 03:09,
18.188.240.4:LOG IN
|
©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://massmind.org/techref/os/win/api/win32/func/src/f69_32.htm"> RasDial</A> |
Did you find what you needed? |
Welcome to massmind.org! |
Welcome to massmind.org! |
.