Re: Cellcard (modem) dial-up issues - general solutions?
- From: "KM" <konstmor@xxxxxxxxxxxxxxxx>
- Date: Tue, 24 Apr 2007 15:39:26 -0700
Adam,
RasDial.exe does use RAS APIs the same way you'd use it in your own Win32 app that has to deal with enumerating and calling out a
RAS connection. Rasdial doesn't have its own UI but uses dialogs that are built in the TAPI library(ies).
RasPhone is a different story. It actually has its own UI and only calls in the RAS Manager APIs and reads the ras book. While
Rasdial provides unattended dialing, the RasPhone supports more features through its richer UI.
However the mentioned ShowDialingProgress flag in my earlier post, applies to both application as well as any other RAS client. You
are not supposed to see the progress dialog while dialing out a RAS (dial-up) connection. You will however see UI dialogs if an
error occurred while establishing the dial-up connection.
Due to old age and legacy support the RAS stack on NT and CE is over complicated nowadays. Call traces for simple user actions are
very long there and hard to track.
On Windows CE there is a feature (driver) implemented that is responsible for auto-dial. That driver basically launches
RasDial.exe - the default auto-dial handler - when requested. Even though the rasdail.exe name is hardcoded there in some Windows
components (WinInet and etc.) it is still possible to change the default handler and provide your own UI or modify system UI on CE.
On XP however it all stays in user mode. When an Internet connection is requested WinInet library will check the flag (Internet
Options settings you mentioned) and will show the dial-up dialog(s) if a dial-up connection needs to be established. I believe this
is being done via TAPI calls directly.
Basically on NT (XP) the Rasdial.exe is not for automating the connection process for any application client (e.g., starting
connection by a shortcut on the desktop, etc.).
Since your own application doesn't use TAPI directly (does it?) but calls into RAS API (RasDial function, etc.) you will see the
same UI the rasdial.exe shows. The ShowDialingProgress flag should hp you to get rid of the annoying dialog, though. (again, it
doesn't safe you from Microsoft UI completely - on error handling and such you will still see Microsoft TAPI UI there).
--
=========
Regards,
KM
Very interesting response KM - Thank you very much.
I wonder, do you think that when (and if) I switch our xpe image to using our custom application for the shell, that this will
conceal or not show the "Connectin to..." dialog if we stick to using the Control Panel -> Internet Options
Another question - do the rasphone.exe and rasdial.exe programs in XP simply use the RAS/TAPI API just like our custom application
does? That is to say, by using the RAS.h (actually Ras.pas since it was a Delphi port) to access functions like RasDial and
RasHangup, are we skipping around rasphone.exe and rasdial.exe? Does the auto-dialer that comes up when using the Control
Panel -> Internet Options -> Connections settings actually use rasdial.exe or rasphone.exe? The dialog I get when I rasphone.exe
from a cmd prompt looks totally different then the one that is popping up occasionally.
Thanks again KM. You're a real asset to this group.
.
- References:
- Cellcard (modem) dial-up issues - general solutions?
- From: Adam Nofsinger
- Re: Cellcard (modem) dial-up issues - general solutions?
- From: KM
- Re: Cellcard (modem) dial-up issues - general solutions?
- From: Adam Nofsinger
- Cellcard (modem) dial-up issues - general solutions?
- Prev by Date: Re: MSDN EWFAPI Sample Logic Error.
- Next by Date: Re: MSDN EWFAPI Sample Logic Error.
- Previous by thread: Re: Cellcard (modem) dial-up issues - general solutions?
- Next by thread: Component Upgrade Warnings?
- Index(es):
Relevant Pages
|
|