Re: componentized drivers
- From: "dferencz@xxxxxxxxx" <dferencz@xxxxxxxxx>
- Date: 30 Jan 2006 11:38:56 -0800
Sorry, I misunderstood your problem with INF files. It sounds like
your INF is either poorly constructed.
I have sometimes had success in parsing each section of the INF file
separately. In CD, when you select an INF for importing, choose
"Custom" rather than "Automatic" and add each section individually.
You can even import each section into a different component, then you
can tell which section is causing the problem.
Of course, if the component is fairly simple, you can just learn to
"speak" INF and construct the component manually. (This is usually
easier for me than trying to decode the output of InCtrl5). You can
find a reference to INF files in the MS DDK Documentation (go to
msdn.microsoft.com, open the "Library", then look for "Driver
Development"). Sometimes you can "tweak" an INF so that it can be
successfully imported.
I'm not familiar with Ashampoo, but if you are able to get a list of
added files and registry entries, then it's basically the same function
as InCtrl5.
-- Don
.
- References:
- componentized drivers
- From: Chris
- Re: componentized drivers
- From: dferencz@xxxxxxxxx
- Re: componentized drivers
- From: Adora Belle Dearheart
- Re: componentized drivers
- From: Chris
- componentized drivers
- Prev by Date: Re: stop error
- Next by Date: Re: Partition Magic and the image files
- Previous by thread: Re: componentized drivers
- Next by thread: Clone CF card... does not boot
- Index(es):
Relevant Pages
|
|
