Re: driver
- From: vcnewbie <frares@xxxxxxxxx>
- Date: Mon, 3 Mar 2008 03:41:22 -0800 (PST)
Hi, All
I have a similar problem: the driver I need is deployed as an Install
Shield executable package. I got all the files when I just start the
package instalation and grab them from the temporary folder (then I
just cancel the instalation). There are some well known INF, SYS, DLL
and CAT files, as well as some CAB and EXE. Inside one of this CAB is
where I've got the INF and some others.
How do I get to know which files will I really need? Just the ones
mentioned by the "INF" file are enough? What about the others?
Should I pack them also?
Thanks
Francisco
On 27 fev, 02:22, "Sean Liming \(MVP\)" <sean_lim...@xxxxxxxxxxxx>
wrote:
Very simply just import the INF into Component Designer.
There are a number of websites and books with information on components:
http://msdn2.microsoft.com/en-us/library/ms838332.aspxhttp://msdn2.microsoft.com/en-us/embedded/aa731186.aspxwww.seanliming.comwww.xpefiles.com
Or are you having a specific problem with a driver?
--
Regards,
Sean Limingwww.sjjmicro.com/www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
"YULUNYEH" <yh1...@xxxxxxxxxxx> wrote in message
news:63B26096-95C7-429D-B42D-3A997C17AA43@xxxxxxxxxxxxxxxx
I am just beginner with XPE. Anyone has any tools or any suggestion to
packing driver, so it will not become blue-screen to FBA.
Mike
.
- Follow-Ups:
- Re: driver
- From: KM
- Re: driver
- From: Schockal
- Re: driver
- Prev by Date: Re: USB 2.0 boot problem
- Next by Date: Forgot my Admin password on an XPe device
- Previous by thread: Re: USB 2.0 boot problem
- Next by thread: Re: driver
- Index(es):
Relevant Pages
|