Hi

we developing a driver for a USB GSM modem on Windows XP and 2000. The Pnp inf file initialise the unimodem driver. To have different configurations we use the following entries in the INF file
HKR, Protocol\GSM\GPRS, 1,, "AT<cr>
HKR, Protocol\GSM\ANALOG_RLP,1,, "AT+CBST=7,,1<cr>" ; or ATB1
HKR, Protocol\GSM\ANALOG_RLP_14DOT4K,1,, "AT+CBST=14,,1<cr>" ; or ATB1
HKR, Protocol\GSM\V110_4DOT8K,1,, "AT+CBST=70,,1<cr>" ; or ATB2
HKR, Protocol\GSM\V110_9DOT6K,1,, "AT+CBST=71,,1<cr>" ; or ATB2
HKR, Protocol\GSM\V110_14DOT4K,1,, "AT+CBST=75,,1<cr>" ; or ATB3

The installation works fine. I see the selection "GPRS","ANALOG_RLP", ... on two places
1.) ControlPanel->Phone and Modem Options ->Modems->Properties->Advanced->Change Default Preferences->DataProtoco

and on
Dialup Connection->Properties->General->Configure->Modem Protoco

If both setting does not point to the same protocol the default setting is used. I think this is a bad solution for the user. It could prepare two or more dial up solution to connect to several providers or servers. Maybe each provider server needs a different protocol. So the user must change the default settings under the control panel to activate a different connection

Do I anything wrong? Can I get a hint to improve my driver? Or can anybody confirm this behaviour of Windows

Thank you

Guenter Hildebrandt

RE: GSM Modem by johnei

johnei
Tue May 04 18:34:31 CDT 2004

------=_NextPart_0001_1F1F8647
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi, Guenter

We are very short handed this week due to the WinHEC conference this week.
I will see what I can do to get you a response.

Thank you for your patience,

John Eikanger
Microsoft Developer Support

This posting is provided ?AS IS? with no warranties, and confers no rights.
--------------------
From: "=?Utf-8?B?R3VlbnRlcg==?=" <udo@t-h-e-s-y-c-o-n.de>
Subject: GSM Modem
Date: Tue, 4 May 2004 00:31:04 -0700
X-Tomcat-NG: microsoft.public.development.device.drivers

Hi,

we developing a driver for a USB GSM modem on Windows XP and 2000. The Pnp
inf file initialise the unimodem driver. To have different configurations
we use the following entries in the INF file:
HKR, Protocol\GSM\GPRS, 1,, "AT<cr>"
HKR, Protocol\GSM\ANALOG_RLP,1,, "AT+CBST=7,,1<cr>" ; or ATB13
HKR, Protocol\GSM\ANALOG_RLP_14DOT4K,1,, "AT+CBST=14,,1<cr>" ; or ATB15
HKR, Protocol\GSM\V110_4DOT8K,1,, "AT+CBST=70,,1<cr>" ; or ATB27
HKR, Protocol\GSM\V110_9DOT6K,1,, "AT+CBST=71,,1<cr>" ; or ATB29
HKR, Protocol\GSM\V110_14DOT4K,1,, "AT+CBST=75,,1<cr>" ; or ATB31

The installation works fine. I see the selection "GPRS","ANALOG_RLP", ...
on two places:
1.) ControlPanel->Phone and Modem Options
->Modems->Properties->Advanced->Change Default Preferences->DataProtocol

and on
Dialup Connection->Properties->General->Configure->Modem Protocol

If both setting does not point to the same protocol the default setting is
used. I think this is a bad solution for the user. It could prepare two or
more dial up solution to connect to several providers or servers. Maybe
each provider server needs a different protocol. So the user must change
the default settings under the control panel to activate a different
connection.

Do I anything wrong? Can I get a hint to improve my driver? Or can anybody
confirm this behaviour of Windows?


Thank you,

Guenter Hildebrandt

------=_NextPart_0001_1F1F8647
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi, Guenter
\par
\par We are very short handed this week due to the WinHEC conference this week. I will see what I can do to get you a response.
\par
\par Thank you for your patience,
\par
\par John Eikanger
\par Microsoft Developer Support
\par
\par This posting is provided \ldblquote AS IS\rdblquote with no warranties, and confers no rights.
\par \pard\li720 --------------------
\par From: "=?Utf-8?B?R3VlbnRlcg==?=" <udo@t-h-e-s-y-c-o-n.de>
\par Subject: GSM Modem
\par Date: Tue, 4 May 2004 00:31:04 -0700
\par X-Tomcat-NG: microsoft.public.development.device.drivers
\par
\par Hi,
\par
\par we developing a driver for a USB GSM modem on Windows XP and 2000. The Pnp inf file initialise the unimodem driver. To have different configurations we use the following entries in the INF file:
\par HKR, Protocol\\GSM\\GPRS, 1,, "AT<cr>"
\par HKR, Protocol\\GSM\\ANALOG_RLP,1,, "AT+CBST=7,,1<cr>" ; or ATB13
\par HKR, Protocol\\GSM\\ANALOG_RLP_14DOT4K,1,, "AT+CBST=14,,1<cr>" ; or ATB15
\par HKR, Protocol\\GSM\\V110_4DOT8K,1,, "AT+CBST=70,,1<cr>" ; or ATB27
\par HKR, Protocol\\GSM\\V110_9DOT6K,1,, "AT+CBST=71,,1<cr>" ; or ATB29
\par HKR, Protocol\\GSM\\V110_14DOT4K,1,, "AT+CBST=75,,1<cr>" ; or ATB31
\par
\par The installation works fine. I see the selection "GPRS","ANALOG_RLP", ... on two places:
\par 1.) ControlPanel->Phone and Modem Options ->Modems->Properties->Advanced->Change Default Preferences->DataProtocol
\par
\par and on
\par Dialup Connection->Properties->General->Configure->Modem Protocol
\par
\par If both setting does not point to the same protocol the default setting is used. I think this is a bad solution for the user. It could prepare two or more dial up solution to connect to several providers or servers. Maybe each provider server needs a different protocol. So the user must change the default settings under the control panel to activate a different connection.
\par
\par Do I anything wrong? Can I get a hint to improve my driver? Or can anybody confirm this behaviour of Windows?
\par
\par
\par Thank you,
\par \pard
\par Guenter Hildebrandt
\par
\par
\par }
------=_NextPart_0001_1F1F8647--


RE: GSM Modem by dmaddy

dmaddy
Thu May 06 16:31:28 CDT 2004

------=_NextPart_0001_28FBF066
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi, Guenter

Sorry for the late response. I am still researching the issue but I have a
question I was hoping you could answer for me:

>HKR, Protocol\GSM\ANALOG_RLP_14DOT4K,1,, "AT+CBST=14,,1<cr>" ; or ATB15

I could not find a <protocol_type> of ANALOG_RLP_14DOT4K in the DDK. Where
did you get this value?

Best regards,

Dan Maddy
DDK Support

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_28FBF066
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi, Guenter
\par
\par Sorry for the late response. I am still researching the issue but I have a question I was hoping you could answer for me:
\par
\par >HKR, Protocol\\GSM\\ANALOG_RLP_14DOT4K,1,, "AT+CBST=14,,1<cr>" ; or ATB15
\par
\par I could not find a <protocol_type> of ANALOG_RLP_14DOT4K in the DDK. Where did you get this value?
\par
\par Best regards,
\par
\par Dan Maddy
\par DDK Support
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }
------=_NextPart_0001_28FBF066--


RE: GSM Modem by udo

udo
Mon May 10 02:46:01 CDT 2004

Hi Dan

I see we have an additional problem: The modem supports two analog modes
Mode A: Analog 9600 bp
Mode B: Analog 14400 bp
You are right, the DDK does not have a second entry for analog connections. The string
;HKR, Protocol\GSM\ANALOG_RLP_14DOT4K,1,, "AT+CBST=14,,1<cr>" ; or ATB1
is not visible in the select box

Can you give me hint, how the user can select between the modes Analog 9600 and Analog 14400

For the tests I have removed the entry ANALOG_RLP_14DOT4K from the INF and from the registry. I have found the same behaviour. If I select the protocol Analog in the default settings and at the same time protocol GPRS in the dial up connection properties, Windows set the analog protocol. Only if I select in both select boxes GPRS than GPRS is set

Thanks
Guente


RE: GSM Modem by dmaddy

dmaddy
Tue May 11 22:45:55 CDT 2004

------=_NextPart_0001_441259C0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi, Guenter

> Can you give me hint, how the user can select between the modes Analog
9600 and Analog 14400.

That does not seem possible because the DDK defines GSM Protocol registry
entries as having the following form:

"HKR, Protocol\GSM\<protocol_type>, 1,,"command string<cr>""

User defined values for <protocol_type> are not supported.

The best you can do is autobauding as per the DDK:

"It is also recommended that autobauding be enabled for RLP connections as
specified in ETSI/GSM 07.07."

Best regards,

Dan Maddy
DDK Support

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_441259C0
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi, Guenter
\par
\par > Can you give me hint, how the user can select between the modes Analog 9600 and Analog 14400.
\par
\par That does not seem possible because the DDK defines GSM Protocol registry entries as having the following form:
\par
\par "HKR, Protocol\\GSM\\<protocol_type>, 1,,"command string<cr>""
\par
\par User defined values for <protocol_type> are not supported.
\par
\par The best you can do is autobauding as per the DDK:
\par
\par "It is also recommended that autobauding be enabled for RLP connections as specified in ETSI/GSM 07.07."
\par
\par Best regards,
\par
\par Dan Maddy
\par DDK Support
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }
------=_NextPart_0001_441259C0--


RE: GSM Modem by udo

udo
Wed May 12 08:06:03 CDT 2004

Thank you Dan for this hint

I still have the problem with the settings between GPRS and Analog protocol. If I prepare a GPRS dialup connection and I set the protocol in the dialup connection to GPRS, the unimodem driver uses the setting for the analog protocol, if this is set under CPL->Modems->Default Settings. I would expect, that the setting in a dialup connection would overwrite the default settings! Why does it not work

Guente


----- Dan Maddy wrote: ----

Hi, Guente

> Can you give me hint, how the user can select between the modes Analog
9600 and Analog 14400

That does not seem possible because the DDK defines GSM Protocol registry
entries as having the following form

"HKR, Protocol\GSM\<protocol_type>, 1,,"command string<cr>"

User defined values for <protocol_type> are not supported

The best you can do is autobauding as per the DDK

"It is also recommended that autobauding be enabled for RLP connections as
specified in ETSI/GSM 07.07.

Best regards

Dan Madd
DDK Suppor

This posting is provided "AS IS" with no warranties, and confers no rights

RE: GSM Modem by dmaddy

dmaddy
Fri May 14 23:25:36 CDT 2004

------=_NextPart_0001_53A9DFC4
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi, Guenter

> I still have the problem with the settings between GPRS and Analog
protocol. If I prepare a GPRS dialup connection and
> I set the protocol in the dialup connection to GPRS, the unimodem driver
uses the setting for the analog protocol, if this is
> set under CPL->Modems->Default Settings. I would expect, that the setting
in a dialup connection would overwrite the
> default settings! Why does it not work?

This may work differently in Win 2K and Win XP. I am still researching
this issue.

Best regards,

Dan Maddy
DDK Support

This posting is provided "AS IS" with no warranties, and confers no rights
------=_NextPart_0001_53A9DFC4
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi, Guenter
\par
\par > I still have the problem with the settings between GPRS and Analog protocol. If I prepare a GPRS dialup connection and
\par > I set the protocol in the dialup connection to GPRS, the unimodem driver uses the setting for the analog protocol, if this is
\par > set under CPL->Modems->Default Settings. I would expect, that the setting in a dialup connection would overwrite the
\par > default settings! Why does it not work?
\par
\par This may work differently in Win 2K and Win XP. I am still researching this issue.
\par
\par Best regards,
\par
\par Dan Maddy
\par DDK Support
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights
\par }
------=_NextPart_0001_53A9DFC4--