Hello,
We are having problems when we try and put 2 modem drivers
onto 1 COM port.

We need this in two cases: the user may need to attach
different external modems to the COM port (e.g. GSM or
satellitte phone), or he may be using a GSM phone with
GPRS, and because the modem handling for GPRS is different
a different driver needs to be installed. These are laptop
users who cannot add additional COM ports to their
machines.

The user has 2 dial-up networking (DUN) settings, one for
each modem driver. Windows selects the modem driver to use
seemingly at random. If logging is switched on, the log is
also placed in a modem's log file at random. However the
log entry shows which modem driver is being used, and this
is always correct, so we can see when Windows is using the
wrong driver.

Has anyone else experienced this? Anyone got a workaround?

FYI, Windows 98 handles this without any problem, but 2000
said this does not work by design on the MS support pages,
and there is nothing about it in XP. Also, according to
our software engineers, Windows guidelines now stop us
writing our own modem driver to circumvent this problem.

Regards,

Tim Thornton

"Tim Thornton" <(E-Mail Removed)> wrote in message
news:26c701c3fc89$5857bd10$(E-Mail Removed)...
| Hello,
| We are having problems when we try and put 2 modem drivers
| onto 1 COM port.
|
| We need this in two cases: the user may need to attach
| different external modems to the COM port (e.g. GSM or
| satellitte phone), or he may be using a GSM phone with
| GPRS, and because the modem handling for GPRS is different
| a different driver needs to be installed. These are laptop
| users who cannot add additional COM ports to their
| machines.
|
| The user has 2 dial-up networking (DUN) settings, one for
| each modem driver. Windows selects the modem driver to use
| seemingly at random. If logging is switched on, the log is
| also placed in a modem's log file at random. However the
| log entry shows which modem driver is being used, and this
| is always correct, so we can see when Windows is using the
| wrong driver.
|
| Has anyone else experienced this? Anyone got a workaround?
|
| FYI, Windows 98 handles this without any problem, but 2000
| said this does not work by design on the MS support pages,
| and there is nothing about it in XP. Also, according to
| our software engineers, Windows guidelines now stop us
| writing our own modem driver to circumvent this problem.
|
| Regards,
|
| Tim Thornton


Hi Tim -

This is by design in Windows XP, as in Windows 2000. They're both built on
the NT kernel.

External com port modems must be attached to the computer and turned on when
it is booted in order to be properly detected when the OS is started. Have
you tried this approach?

Jef

Or by refreashing the hardware in Device Manager.

"Jef Norton" <jefn_REMOVE_YOUR_SHORTS_@sbcglobal.net> wrote in message
news:05q%b.2851$(E-Mail Removed)...
> "Tim Thornton" <(E-Mail Removed)> wrote in message
> news:26c701c3fc89$5857bd10$(E-Mail Removed)...
> | Hello,
> | We are having problems when we try and put 2 modem drivers
> | onto 1 COM port.
> |
> | We need this in two cases: the user may need to attach
> | different external modems to the COM port (e.g. GSM or
> | satellitte phone), or he may be using a GSM phone with
> | GPRS, and because the modem handling for GPRS is different
> | a different driver needs to be installed. These are laptop
> | users who cannot add additional COM ports to their
> | machines.
> |
> | The user has 2 dial-up networking (DUN) settings, one for
> | each modem driver. Windows selects the modem driver to use
> | seemingly at random. If logging is switched on, the log is
> | also placed in a modem's log file at random. However the
> | log entry shows which modem driver is being used, and this
> | is always correct, so we can see when Windows is using the
> | wrong driver.
> |
> | Has anyone else experienced this? Anyone got a workaround?
> |
> | FYI, Windows 98 handles this without any problem, but 2000
> | said this does not work by design on the MS support pages,
> | and there is nothing about it in XP. Also, according to
> | our software engineers, Windows guidelines now stop us
> | writing our own modem driver to circumvent this problem.
> |
> | Regards,
> |
> | Tim Thornton
>
>
> Hi Tim -
>
> This is by design in Windows XP, as in Windows 2000. They're both built
on
> the NT kernel.
>
> External com port modems must be attached to the computer and turned on
when
> it is booted in order to be properly detected when the OS is started.
Have
> you tried this approach?
>
> Jef
>
>

On Thu, 26 Feb 2004 08:55:31 -0800, "Tim Thornton"
<(E-Mail Removed)> wrote:

>Hello,
>We are having problems when we try and put 2 modem drivers
>onto 1 COM port.
>
>We need this in two cases: the user may need to attach
>different external modems to the COM port (e.g. GSM or
>satellitte phone), or he may be using a GSM phone with
>GPRS, and because the modem handling for GPRS is different
>a different driver needs to be installed. These are laptop
>users who cannot add additional COM ports to their
>machines.
>
>The user has 2 dial-up networking (DUN) settings, one for
>each modem driver. Windows selects the modem driver to use
>seemingly at random. If logging is switched on, the log is
>also placed in a modem's log file at random. However the
>log entry shows which modem driver is being used, and this
>is always correct, so we can see when Windows is using the
>wrong driver.
>
>Has anyone else experienced this? Anyone got a workaround?

I'd have the same advice as Jef. If you have the modem connected and
turned on, doesn't it detect the proper modem?

Moreover, it would seem that no modem at all would be installed in
Device Manager if there was no modem connected to the com port. I
mean...you could have a mouse, etc. connected there.


Have a nice week...

Trent

What do you call a smart blonde?
A golden retriever.

The external modems are not plug and play, so they are
always there in device manager, rather than becoming
disabled if not connected at start-up.

Because of this, I do not think either of these solutions
will work.

Also, because of the non-technical nature of our end
users, I do not think that going into device manager and
enabling/disabling modems, and then rebooting, is really
an option.

In the long term we can get our SmartCom developers to
take over the modem drivers in Windows by having one
driver and writing the correct registry settings just
before using the modem (we have had to do similar things
with dial-up networking to make that more robust), but I
was just hoping that XP had improved on 2000.

Thanks anyway,

Tim


>-----Original Message-----
>On Thu, 26 Feb 2004 08:55:31 -0800, "Tim Thornton"
><(E-Mail Removed)> wrote:
>
>>Hello,
>>We are having problems when we try and put 2 modem
drivers
>>onto 1 COM port.
>>
>>We need this in two cases: the user may need to attach
>>different external modems to the COM port (e.g. GSM or
>>satellitte phone), or he may be using a GSM phone with
>>GPRS, and because the modem handling for GPRS is
different
>>a different driver needs to be installed. These are
laptop
>>users who cannot add additional COM ports to their
>>machines.
>>
>>The user has 2 dial-up networking (DUN) settings, one
for
>>each modem driver. Windows selects the modem driver to
use
>>seemingly at random. If logging is switched on, the log
is
>>also placed in a modem's log file at random. However the
>>log entry shows which modem driver is being used, and
this
>>is always correct, so we can see when Windows is using
the
>>wrong driver.
>>
>>Has anyone else experienced this? Anyone got a
workaround?
>
>I'd have the same advice as Jef. If you have the modem
connected and
>turned on, doesn't it detect the proper modem?
>
>Moreover, it would seem that no modem at all would be
installed in
>Device Manager if there was no modem connected to the com
port. I
>mean...you could have a mouse, etc. connected there.
>
>
>Have a nice week...
>
>Trent
>
>What do you call a smart blonde?
>A golden retriever.
>
>.
>