Re: XXX_Init only being called once
- From: "Andy Shi" <yashi88@xxxxxxxxxxx>
- Date: Wed, 9 Nov 2005 09:02:03 +0800
You must know that XXX_Init only be called once when system load. You need
change your design.
Andy Shi
http://www.v-max.com.cn
"Thomas Magma" <somewhere@xxxxxxxxxxxxxxxxxx> дÈëÏûÏ¢ÐÂÎÅ:uvvpbeL5FHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
> We are rewriting our PCMCIA driver for WM 5.0. I am noticing some odd
> behavior I'm hoping someone can shed some light on it. The first time the
> card is inserted in the CF slot the device manager does everything as
> planned. Our driver dll is being loaded properly and sits next to
> pcmcia.dll when viewed with Remote Process Viewer. Oure XXX_Init function
> is being called in our driver and the active key with our prefix shows up.
> These are all expected behaviors, however, when I remove the card and
> insert it a second or third time none of these events occur. If I don't
> CardDeregisterClient on the first card removal I will still get call backs
> to the driver when the card is continually inserted and de-inserted. If I
> do CardDeregisterClient on the first card removal my driver is never
> called again. Even though my driver dll doesn't appear anywhere on Remote
> Process Viewer after the first card insertion a pop-up window is still
> telling me some process is holding on to it when I try to copy over top.
>
> How do I make sure XXX_Init is called each time our card is inserted?
>
> Thanks,
>
> Thomas
>
.
- Follow-Ups:
- Re: XXX_Init only being called once
- From: Steve Maillet \(eMVP\)
- Re: XXX_Init only being called once
- From: Thomas Magma
- Re: XXX_Init only being called once
- Prev by Date: WinCE 5.0 Update Instructions need Updating
- Next by Date: Re: XXX_Init only being called once
- Previous by thread: WinCE 5.0 Update Instructions need Updating
- Next by thread: Re: XXX_Init only being called once
- Index(es):
Relevant Pages
|
