Hi,
In winxp if a device fails for some reason I am able to disable and enable
it after fixing the problem and then pnp manager starts it again.
Sadly, my impression is that this is not the case in win2k. When I disable
and enable a failed device in win2k, SetupDi always says I must restart the
system for the change to take effect.
This is a very big problema for the design of my driver since my driver can
be configured to fail some device stacks, but when configuration changes, I
want to restart the device stack without having to restart the machine.
Is there a way to restart failed device stacks on win2k without having to
restart?
Thanks,
Shahar
The OS asks for restart if stopping the device stack failed, which usually
means a veto imposed by some user or kernel mode component.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Shahar Talmi”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Sunday, July 10, 2005 6:38 PM
Subject: [ntdev] Restarting of a failed device always requires a restart on
win2k
> Hi,
> In winxp if a device fails for some reason I am able to disable and enable
> it after fixing the problem and then pnp manager starts it again.
> Sadly, my impression is that this is not the case in win2k. When I disable
> and enable a failed device in win2k, SetupDi always says I must restart the
> system for the change to take effect.
>
> This is a very big problema for the design of my driver since my driver can
> be configured to fail some device stacks, but when configuration changes, I
> want to restart the device stack without having to restart the machine.
>
> Is there a way to restart failed device stacks on win2k without having to
> restart?
>
> Thanks,
> Shahar
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
I’m not sure if I made myself clear…
The problem is with disabling of a device that is *failed*, hence the device
is already stopped and pnp manager doesn’t even try to send
IRP_MN_QUERY_REMOVE to it.
Shahar
“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
> The OS asks for restart if stopping the device stack failed, which
> usually
> means a veto imposed by some user or kernel mode component.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> ----- Original Message -----
> From: “Shahar Talmi”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Sunday, July 10, 2005 6:38 PM
> Subject: [ntdev] Restarting of a failed device always requires a restart
> on
> win2k
>
>
>> Hi,
>> In winxp if a device fails for some reason I am able to disable and
>> enable
>> it after fixing the problem and then pnp manager starts it again.
>> Sadly, my impression is that this is not the case in win2k. When I
>> disable
>> and enable a failed device in win2k, SetupDi always says I must restart
>> the
>> system for the change to take effect.
>>
>> This is a very big problema for the design of my driver since my driver
>> can
>> be configured to fail some device stacks, but when configuration changes,
>> I
>> want to restart the device stack without having to restart the machine.
>>
>> Is there a way to restart failed device stacks on win2k without having to
>> restart?
>>
>> Thanks,
>> Shahar
>>
>>
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>>
>> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
Does this happen with all stacks or just stacks of certain device
classes?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Monday, July 11, 2005 11:14 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Restarting of a failed device always requires a
restart on win2k
I’m not sure if I made myself clear…
The problem is with disabling of a device that is *failed*, hence the
device
is already stopped and pnp manager doesn’t even try to send
IRP_MN_QUERY_REMOVE to it.
Shahar
“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
> The OS asks for restart if stopping the device stack failed, which
> usually
> means a veto imposed by some user or kernel mode component.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> ----- Original Message -----
> From: “Shahar Talmi”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Sunday, July 10, 2005 6:38 PM
> Subject: [ntdev] Restarting of a failed device always requires a
restart
> on
> win2k
>
>
>> Hi,
>> In winxp if a device fails for some reason I am able to disable and
>> enable
>> it after fixing the problem and then pnp manager starts it again.
>> Sadly, my impression is that this is not the case in win2k. When I
>> disable
>> and enable a failed device in win2k, SetupDi always says I must
restart
>> the
>> system for the change to take effect.
>>
>> This is a very big problema for the design of my driver since my
driver
>> can
>> be configured to fail some device stacks, but when configuration
changes,
>> I
>> want to restart the device stack without having to restart the
machine.
>>
>> Is there a way to restart failed device stacks on win2k without
having to
>> restart?
>>
>> Thanks,
>> Shahar
>>
>>
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>>
>> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I’ve seen it happen with every single class I tried (tested with about 5
classes).
Shahar
“Doron Holan” wrote in message
news:xxxxx@ntdev…
Does this happen with all stacks or just stacks of certain device
classes?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shahar Talmi
Sent: Monday, July 11, 2005 11:14 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Restarting of a failed device always requires a
restart on win2k
I’m not sure if I made myself clear…
The problem is with disabling of a device that is failed, hence the
device
is already stopped and pnp manager doesn’t even try to send
IRP_MN_QUERY_REMOVE to it.
Shahar
“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
> The OS asks for restart if stopping the device stack failed, which
> usually
> means a veto imposed by some user or kernel mode component.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> ----- Original Message -----
> From: “Shahar Talmi”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Sunday, July 10, 2005 6:38 PM
> Subject: [ntdev] Restarting of a failed device always requires a
restart
> on
> win2k
>
>
>> Hi,
>> In winxp if a device fails for some reason I am able to disable and
>> enable
>> it after fixing the problem and then pnp manager starts it again.
>> Sadly, my impression is that this is not the case in win2k. When I
>> disable
>> and enable a failed device in win2k, SetupDi always says I must
restart
>> the
>> system for the change to take effect.
>>
>> This is a very big problema for the design of my driver since my
driver
>> can
>> be configured to fail some device stacks, but when configuration
changes,
>> I
>> want to restart the device stack without having to restart the
machine.
>>
>> Is there a way to restart failed device stacks on win2k without
having to
>> restart?
>>
>> Thanks,
>> Shahar
>>
>>
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>>
>> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com