Property page causing reboot during update

NTDEV
1

Hi,

I have a device driver running in Windows 2000 that has a property page. I
can install the device driver fine by using infs but when I try to update it
afterwards using device manager the Windows requires me to reboot in order
to make update effective. Just to make note here; I don’t receive any PnP-
or Power-IRP so this doesn’t seem to be related with PnP-IRPs.

If I delete the property page dll manually from "…\System32"-directory,
the update works fine. Now I’m running out of clues how to get things
working without rebooting. Checked build has really given me any glues,
except the line:
InstallDev CM_Get_DevNode_Status()=0 DevNodeStatus=180610a Problem=e

Does anyone has any clues how to solve this problem. I’m wondering if this
is a inf problem but I’m not sure… Could the dll itself somehow cause this
kind of behaviour?

BR, Mikko

ps. Updating of the drivers work fine with Windows XP

2

Look in setupapi.log to see why the reboot is required. I amguessing it
is b/c the dll is already loaded and setup is trying to copy it, but
can’t.

D

This posting is provided “AS IS” with no warranties, and confers no
rights

-----Original Message-----
From: xxxxx@nokia.com [mailto:xxxxx@nokia.com]
Sent: Sunday, January 26, 2003 11:13 PM
To: NT Developers Interest List
Subject: [ntdev] Property page causing reboot during update

Hi,

I have a device driver running in Windows 2000 that has a property page.
I
can install the device driver fine by using infs but when I try to
update it
afterwards using device manager the Windows requires me to reboot in
order
to make update effective. Just to make note here; I don’t receive any
PnP-
or Power-IRP so this doesn’t seem to be related with PnP-IRPs.

If I delete the property page dll manually from
"…\System32"-directory,
the update works fine. Now I’m running out of clues how to get things
working without rebooting. Checked build has really given me any glues,
except the line:
InstallDev CM_Get_DevNode_Status()=0 DevNodeStatus=180610a Problem=e

Does anyone has any clues how to solve this problem. I’m wondering if
this
is a inf problem but I’m not sure… Could the dll itself somehow cause
this
kind of behaviour?

BR, Mikko

ps. Updating of the drivers work fine with Windows XP

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com