[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-smartcardddk
Subject:    Re: An interesting problem
From:       Klaus Schutz <kschutz () MICROSOFT ! COM>
Date:       1998-03-13 19:03:02
[Download RAW message or body]


Baiju,

what you describe is a 'bug' of the control panel application in NT4
When you change/add/delete the settings for a serial port
this application changes the object name for the device from
\Device\Serialx to \Device\Serial1000x.
All you can do is to manually delete the key
HKLM\System\CurrentControlSet\Services\Serial\Parameters
to reset it to the old settings

Klaus U. Schutz
Software Design Engineer
Microsoft Corporation



        -----Original Message-----
        From:   Baiju Nair [SMTP:bnair@OKI.COM]
        Sent:   Friday, March 13, 1998 10:40 AM
        To:     SmartCardDDK@DISCUSS.MICROSOFT.COM
        Subject:        An interesting problem
        Importance:     High

        Hi,
                I had an intersting experience while working on a serial
port
        smartcard driver
                on NT 4.0. This forum might not be the suitable place to
post
        it.

                I was testing my driver in a NT 4.0 machine. It had only one
com
        port enabled in bios (com1)
                My driver worked fine on com1.  Then tried to test in com2 I
        added (unaware that in bios it was disabled)
                com2 thru control panel port and it affected com1 and it got
        removed from the list. Then I understood my fault and
                set com1 again thru control panel port (Io port 3f8 irq 4,
bios
        also io port 3f8 irql 4). When I restarted the
                 machine my driver did not started, because it failed on
        IoGetDeviceObjectPointer where I am trying to attach to
                serial driver using device name \Device\Serial0. Error was
        Object_Name_not_found (c000034). On the event viewer
                serial device put an information telling user settings
overriden
        firmware settings. But serial device was running.

                The interesting thing was even in this situation I could use
        Createfile (Com1,..) and could communicate to
                the reader connected.

                Then I deleted com1 thru control panel port and restarted
the
        machine. Now system autoamtically added Com1
                again with default values to io port and irql and again my
        driver started working.

                Is it possible serial device can run without registering
        \Device\serial0 and COM1 available?

                Thanks,
                Baiju



[prev in list] [next in list] [prev in thread] [next in thread]