- SET_LINE_CODING and usbser.sys
- Posted by John Davies on January 29th, 2008
I'm trying to write a USB to serial device (and who isn't<g>?)
Right now I'm using usbser.sys. I've read all the warnings but a custom
driver is currently out of the question.
I don't understand why I'm not getting SET_LINE_CODING messages. When I go
into Device Manager and change the baud rate, I would think that would be the
time to call into usbser.sys and pass on a SET_LINE_CODING.
My ultimate goal is to have the converter get the baud rate, etc on startup
from Windows.
- Posted by Doron Holan [MSFT] on January 30th, 2008
the property page just stores teh settings as defaults, it does not actively
set them. remember these are defaults which the application may apply, the
driver itself has no way of knowing what the defaults are. it is up to the
app to setup the port as it sees fit
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Davies" <JohnDavies@discussions.microsoft.com> wrote in message
news:5F51C9CC-3770-4EAC-94DE-BBBE277BAD7C@microsoft.com...
- Posted by Walter Oney on January 30th, 2008
"Doron Holan [MSFT]" wrote:
IIRC, however, SERIAL.SYS interrogates the registry to retrieve these
default settings. The OP was probably hoping that USBSER would do that
too.
--
Walter Oney, Consulting and Training
http://www.oneysoft.com
- Posted by chris.aseltine@gmail.com on January 31st, 2008
Also, don't forget that if you want to modify the behavior of
usbser.sys, you don't necessarily need to rewrite the entire thing.
You could write your own upper filter driver (in KMDF, to make it even
easier) that pulls the default baud rate, etc. settings itself.
Then in the start or create path of the filter, you could submit your
own serial IOCTLs to usbser.sys, which would then convert them into
SET_LINE_CODING control requests.
On Jan 29, 7:15 pm, "Doron Holan [MSFT]" <dor...@online.microsoft.com>
wrote:
