Click to See Complete Forum and Search --> : Modem Initialization W2K URGENT!!!


TheCPUWizard
October 23rd, 2002, 11:27 PM
I believe I have found a limitation on W2K with the length
of the HKR,,INIT,2 value with respect to its length.

I am behind deadline on a project to create a new modem.
(And having to pay daily penalty clauses) It is a clone
of the standard MDMGEN.INF file, but with a LONG built in
init string (up to 100 chars).

This appears to cause a corruption in the driver that
causes SVCHOST to trap an error. If I shorten the string,
the problem seems to go away.

If any body knows of a problem like this, please contact
me immediately, prefferablly by e-mail
dvcorbin@optonline.net

I am really desperate there.

Thanks in advance.
.

AnthonyMai
October 24th, 2002, 06:17 PM
Then shorten your modem INIT string.
Why would you need a 100 character long Init string?
"AT&F" will load the factory default, which in most cases will be sufficient and adequate (that's what factory default is for, right?) Any thing additional you can attach to the "AT&F" but I wouldn't think you need to be THAT MUCH deviated from the factory default.

TheCPUWizard
October 24th, 2002, 07:33 PM
Unfortunately that is not an option. The modem is a custom peice of hardware that "looks like a modem" to Windows, Unfortunately it needs about 100 characters to download specific configuration information for wireless connections, icncluding APN,QOS, ROUTING and other parameters, the device does NOT have the capability of storing this information between calls.

At this point I am simply trying to get a firm definition of the maximum length allowed. If I can pass this back to the hardware manufacturer (my client) I have some leverage for him to either change his hardware (e.g add nov-RAM), or conract me to develop a custom driver rather then gust using unimodem as if it was a 33.6K modem.

Someone/Somewhere (Any MSFT internals guys listening) must know the internal buffer size. The crazy thing is long strings do not get terminated (as would be expected from most registry read requests which take the size of the buffer as a parameter. Rather they tend to cause corruption of other functions. At about 80 characters (in the INIT string), the system starts to abort svcHOST.exe on a disconnect. Closer to 100 characters it starts to effect the connection speed (Serial port DCB settings), By 120 characters, the system (W2K pro (All SP levels from None to SP3) will crash and BSOD.