Re: Problems importing .PMQ file

From: Brad Combs (brad_at_imagotechnologies.no.spam.com)
Date: 03/30/04


Date: Tue, 30 Mar 2004 16:08:11 -0500

Stephen,

There are a couple of things here....

1) Your right, the drivers are not being found because they do not exist in
the XPe Database. You need to either follow the steps to componentize the
drivers, obtain componentized versions from the manufacturer, or check
www.xpefiles.com for the drivers in question.

2) The errors on import are due to keys that the importer can't handle. This
could happen for a number of reasons. One way to fix this is to do a custom
import, choose the key type, and type the name of the key (ex CopyINF) into
the text box. Then import the driver from there.

3) The documentation sometimes assumes that you have followed a few of the
tutorials, or understand some of the XPe specific terminology. Post as many
questions as you want here in the NG and we will try to help. Be as specific
as possible.

HTH,

-- 
Brad Combs
Imago Technologies, LLC
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Steven Gildart" <steven.gildart@alphameric.com> wrote in message
news:A7F5B3A8-73C1-4B91-BB7B-A672FA753921@microsoft.com...
> When I try to import (using Component Designer) the .PMQ file generated by
TAP.EXE, I get a number of warnings;
>
>           Warning: Could not find a driver for Intel(R) Graphics Chipset
etc.
>
> I have run TAP on the hardware platform I am attempting to build an image
for, loaded the drivers for the chipset, graphics, sound and network devices
(under XP Pro, so all the devices are recognised and work). How do I resolve
this issue? I guess that the drivers are not in the driver database (it says
I have 9469 drivers), but I do not see how I add them in?
>
> I have tried to take the .INF files for each of the devices and import
them into the Component Database but get errors due to it not understanding
keyword (CopyINF) or properties.
>
> Is it me or is the documentation unrealistically sparse?
>
> Help!
>


Relevant Pages

  • Re: back to business.... (database technology)
    ... Exposes any DBX4-compliant database as an ADO.NET 2.0 data source. ... Unified metadata used for both DBX4 and ADO.NET drivers. ... SQLDatastore is a simple to deploy, fully managed, ... DbExpress Server ...
    (borland.public.delphi.non-technical)
  • Re: back to business.... (database technology)
    ... Exposes any DBX4-compliant database as an ADO.NET 2.0 data source. ... Unified metadata used for both DBX4 and ADO.NET drivers. ... SQLDatastore is a simple to deploy, fully managed, ... DbExpress Server ...
    (borland.public.delphi.non-technical)
  • Re: back to business.... (database technology)
    ... Exposes any DBX4-compliant database as an ADO.NET 2.0 data source. ... Unified metadata used for both DBX4 and ADO.NET drivers. ... SQLDatastore is a simple to deploy, fully managed, ... DbExpress Server ...
    (borland.public.delphi.non-technical)
  • dlopen(), atexit() crash on FreeBSD (testcase included)
    ... libdbi is a library for programs which are supposed to be able to ... access different database engines with a unified API. ... loads available database drivers at runtime via dlopencalls. ... FreeBSD invariably causes a segfault when the application linked ...
    (freebsd-hackers)
  • Re: dlopen(), atexit() crash on FreeBSD (testcase included)
    ... libdbi is a library for programs which are supposed to be able to ... access different database engines with a unified API. ... loads available database drivers at runtime via dlopencalls. ... FreeBSD invariably causes a segfault when the application linked ...
    (freebsd-hackers)