I have a customer who needs to force use of a new INF
file. They have customers who have installed their
driver, now need to upgrade, problem is to accommodate
new devices there have been changes to the registry settings
and the property page that require a new INF file.
The problem comes as:
Customer gets new CD, and goes into the mmc to update
the driver. The system sees it knows about the device and
the device class, so uses the OLD INF file and property
page provider. New driver gets installed with incorrect
registry settings, so crashes.
Note even if we have the customer install with our own program
we use SetupCopyOEMInf and it creates a new inf/pnf pair
and leaves the other there causing the same problem.
It appears if the driver was signed that system might take care
of this, but since the device does not fit any of the Microsoft
classes (it is a semi-custom card for telecom), it cannot be
signed.
Is there any way to get around this?
Don Burn
Windows 2000 Device Driver and Filesystem consulting.
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
I would delete the older INF/PNF files and then do the install. The problem
may be in determining which files to delete since the INF file is normally
copied to OEM?.INF during the install process. I have an identifying header
in my INF files that allow me to identify my INF files and then delete them
manually. I have found, however, that using a global “del
\winnt\inf\oem?.?nf” will work. Note: I’m not recommending it, just noting
that you can do that. However, you may/will delete ALL INF/PNF files in the
range OEM0 to OEM9.
Gary
-----Original Message-----
From: Don Burn [mailto:xxxxx@acm.org]
Sent: Monday, January 08, 2001 8:09 AM
To: NT Developers Interest List
Subject: [ntdev] Is there a way to force use of a new INF file
I have a customer who needs to force use of a new INF
file. They have customers who have installed their
driver, now need to upgrade, problem is to accommodate
new devices there have been changes to the registry settings
and the property page that require a new INF file.
The problem comes as:
Customer gets new CD, and goes into the mmc to update
the driver. The system sees it knows about the device and
the device class, so uses the OLD INF file and property
page provider. New driver gets installed with incorrect
registry settings, so crashes.
Note even if we have the customer install with our own program
we use SetupCopyOEMInf and it creates a new inf/pnf pair
and leaves the other there causing the same problem.
It appears if the driver was signed that system might take care
of this, but since the device does not fit any of the Microsoft
classes (it is a semi-custom card for telecom), it cannot be
signed.
Is there any way to get around this?
Don Burn
Windows 2000 Device Driver and Filesystem consulting.
You are currently subscribed to ntdev as: xxxxx@delphieng.com
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
The problem with the search and destroy method is that it
is a custom installer, there are too many ways that the
customer can messup and cause a BSOD. This appears
to be a case where Microsoft designed for drivers that
can be signed and said fuck the rest of the customers.
I can see why the vendor has a large contingent of folks
saying dump Win2k and move to Linux.
Don Burn
Windows 2000 Device Driver and Filesystem consulting
----- Original Message -----
From: “Gary Little”
To: “NT Developers Interest List”
Sent: Monday, January 08, 2001 12:09 PM
Subject: [ntdev] RE: Is there a way to force use of a new INF file
> I would delete the older INF/PNF files and then do the install. The
problem
> may be in determining which files to delete since the INF file is normally
> copied to OEM?.INF during the install process. I have an identifying
header
> in my INF files that allow me to identify my INF files and then delete
them
> manually. I have found, however, that using a global “del
> \winnt\inf\oem?.?nf” will work. Note: I’m not recommending it, just noting
> that you can do that. However, you may/will delete ALL INF/PNF files in
the
> range OEM0 to OEM9.
>
> Gary
>
> > -----Original Message-----
> > From: Don Burn [mailto:xxxxx@acm.org]
> > Sent: Monday, January 08, 2001 8:09 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] Is there a way to force use of a new INF file
> >
> >
> > I have a customer who needs to force use of a new INF
> > file. They have customers who have installed their
> > driver, now need to upgrade, problem is to accommodate
> > new devices there have been changes to the registry settings
> > and the property page that require a new INF file.
> >
> > The problem comes as:
> >
> > Customer gets new CD, and goes into the mmc to update
> > the driver. The system sees it knows about the device and
> > the device class, so uses the OLD INF file and property
> > page provider. New driver gets installed with incorrect
> > registry settings, so crashes.
> >
> > Note even if we have the customer install with our own program
> > we use SetupCopyOEMInf and it creates a new inf/pnf pair
> > and leaves the other there causing the same problem.
> >
> > It appears if the driver was signed that system might take care
> > of this, but since the device does not fit any of the Microsoft
> > classes (it is a semi-custom card for telecom), it cannot be
> > signed.
> >
> > Is there any way to get around this?
> >
> >
> > Don Burn
> > Windows 2000 Device Driver and Filesystem consulting.
> >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@delphieng.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
> —
> You are currently subscribed to ntdev as: xxxxx@acm.org
> 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
Can you not TAG your INF file, look for that tag in your Co-installer and
then delete any instance of a found INF/PNF file?
-----Original Message-----
From: Don Burn [mailto:xxxxx@acm.org]
Sent: Monday, January 08, 2001 3:06 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Is there a way to force use of a new INF file
The problem with the search and destroy method is that it
is a custom installer, there are too many ways that the
customer can messup and cause a BSOD. This appears
to be a case where Microsoft designed for drivers that
can be signed and said fuck the rest of the customers.
I can see why the vendor has a large contingent of folks
saying dump Win2k and move to Linux.
Don Burn
Windows 2000 Device Driver and Filesystem consulting
----- Original Message -----
From: “Gary Little”
> To: “NT Developers Interest List”
> Sent: Monday, January 08, 2001 12:09 PM
> Subject: [ntdev] RE: Is there a way to force use of a new INF file
>
>
> > I would delete the older INF/PNF files and then do the install. The
> problem
> > may be in determining which files to delete since the INF
> file is normally
> > copied to OEM?.INF during the install process. I have an identifying
> header
> > in my INF files that allow me to identify my INF files and
> then delete
> them
> > manually. I have found, however, that using a global “del
> > \winnt\inf\oem?.?nf” will work. Note: I’m not recommending
> it, just noting
> > that you can do that. However, you may/will delete ALL
> INF/PNF files in
> the
> > range OEM0 to OEM9.
> >
> > Gary
> >
> > > -----Original Message-----
> > > From: Don Burn [mailto:xxxxx@acm.org]
> > > Sent: Monday, January 08, 2001 8:09 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Is there a way to force use of a new INF file
> > >
> > >
> > > I have a customer who needs to force use of a new INF
> > > file. They have customers who have installed their
> > > driver, now need to upgrade, problem is to accommodate
> > > new devices there have been changes to the registry settings
> > > and the property page that require a new INF file.
> > >
> > > The problem comes as:
> > >
> > > Customer gets new CD, and goes into the mmc to update
> > > the driver. The system sees it knows about the device and
> > > the device class, so uses the OLD INF file and property
> > > page provider. New driver gets installed with incorrect
> > > registry settings, so crashes.
> > >
> > > Note even if we have the customer install with our own program
> > > we use SetupCopyOEMInf and it creates a new inf/pnf pair
> > > and leaves the other there causing the same problem.
> > >
> > > It appears if the driver was signed that system might take care
> > > of this, but since the device does not fit any of the Microsoft
> > > classes (it is a semi-custom card for telecom), it cannot be
> > > signed.
> > >
> > > Is there any way to get around this?
> > >
> > >
> > > Don Burn
> > > Windows 2000 Device Driver and Filesystem consulting.
> > >
> > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@delphieng.com
> > > To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@acm.org
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@delphieng.com
> 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