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

List:       ms-smartcardddk
Subject:    AW: Win98 PNP
From:       Stefan Swoboda <Stefan.Swoboda () ABG1 ! SIEMENS ! DE>
Date:       1999-12-15 8:19:30
[Download RAW message or body]


Hi Paul,
I had the same problem as you before
and Microsoft told me that there is a bug 
in the enumerator. The way to solve this problem is 
to connect later to the COM port as you did.


Mit freundlichen Grüßen/Best regards
Stefan Swoboda

Fujitsu Computers
        Siemens PC Systeme
Bgm-Ulrich-Str. 100
86199 Augsburg

Abt:            R&D SW 6
Tel:            +49 821 8043641
Fax:    +49 821 8042910
Email:  stefan.swoboda@abg1.siemens.de <mailto:stefan.swoboda@abg1.siemens.de> 

Besuchen Sie unsere Seite im Web http://www.siemens.de/pc/solution/de/sec.htm \
<http://www.siemens.de/pc/solution/de/sec.htm>  ! Visit our Web-site at \
http://www.siemens.com/pc/solution/us/sec.htm \
<http://www.siemens.com/pc/solution/us/sec.htm>  !



        -----Ursprüngliche Nachricht-----
        Von:    Paul Burkacki [SMTP:pburkacki@SPYRUS.COM]
        Gesendet am:    Dienstag, 14. Dezember 1999 22:36
        An:     SmartCardDDK@DISCUSS.MICROSOFT.COM
        Betreff:        Win98 PNP

        Hi all,

        I have a driver for a PnP-capable serial smart card.  The driver
        seems to work fine under Win95 but not under Win98.

        The problem occurs right after the OS is loaded and serenum is
        started to detect the reader.  Namely, serenum goes through the
        serial port PnP protocol, detects the reader and then loads my
        driver.  If I then try to open the COM port that the reader is
        connected to (as reported by the Configuration Manager), VCOMM
        returns an error that tells me that the COM port is already open.

        If I insert something like a 45 second delay right before I go
        to open the COM port, whoever owns the COM port in the beginning
        has a chance to stop talking to it and my driver is then able to
        open it and normally communicate with the reader.

        Are there any differences between Win95 and Win98 that would
        cause this to happen?  Does anyone know how I can find out who
        opens the COM port right before I open it?  In fact, why would
        any other module try to talk to the COM port when, clearly, my
        reader is the device that the Configuration Manager detects on
        it?

        Any comments are appreciated.

        Thanks,
        Paul Burkacki
        SPYRUS


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