Hi All,
I’m developing NT class installer for whistler (build 2296) to install the device in the system.
In the next boot, as per the entry point defined in registry CurrentControlSet\control\class[guid] Installer32 , class installer gets called by “New Device wizard” . It calls installfunctions DIF_SELECTBESTCOMPATDRV and DIF_DIF_ALLOW_INSTALL., and class installer is returning them with NO_ERROR.
The problem happens, in next (and rest of the boots) when new hardware device is again getting detected by “New device found wizard” (newdev.dll and rundll32.exe).
I believe .pnf file is responsible for the new device detection decision making. It is properly generated during the boot.
Is some registry entry in control also responsible for this?
Any pointers would help greatly.
Thanx in advance,
Craig.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Some information’s what’s is going on with .inf, pnf files, and W2K hardware
locator after driver installation and reboot can be found in MSDN Library
(January 2001) under topic:
How to Force Windows 2000 to Use Standard VGA Compatible Driver
ID: Q268852
They are very problem specific, but it might help to bring some “more
light”.
Wbr Primoz
-----Original Message-----
From: Craig [mailto:xxxxx@hotmail.com]
Sent: Friday, March 16, 2001 4:10 AM
To: NT Developers Interest List
Subject: [ntdev] Class installer help
Hi All,
I’m developing NT class installer for whistler (build 2296) to install the
device in the system.
In the next boot, as per the entry point defined in registry
CurrentControlSet\control\class[guid] Installer32 , class installer gets
called by “New Device wizard” . It calls installfunctions
DIF_SELECTBESTCOMPATDRV and DIF_DIF_ALLOW_INSTALL., and class installer is
returning them with NO_ERROR.
The problem happens, in next (and rest of the boots) when new hardware
device is again getting detected by “New device found wizard” (newdev.dll
and rundll32.exe).
I believe .pnf file is responsible for the new device detection decision
making. It is properly generated during the boot.
Is some registry entry in control also responsible for this?
Any pointers would help greatly.
Thanx in advance,
Craig.
You are currently subscribed to ntdev as: xxxxx@hermes.si
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com