porting XP hardware driver

  • Thread starter Thread starter FCBfreak
  • Start date Start date
F

FCBfreak

Hi,

I understand Windows XP Embedded is based on the same binaries as
Windows XP Professional.

And existing Win32®-based applications can be ported with little or no
modification.

Does this mean an external hardware driver (e.g. for webcam) that
originally was meant for Windows 2000/Win XP is runnable on a Windows
XP Embedded platform without modification?

Thanks in advance!
 
Hello FCB fan,
YES the XP PRO driver could be used on XPE without change, BUT you should
have provided in your image components to install new hardware AND
everything your device needs to work.
That's the hard part of the work, but no mods to the driver is needed.

Regards


"FCBfreak" <[email protected]> ha scritto nel messaggio
Hi,

I understand Windows XP Embedded is based on the same binaries as
Windows XP Professional.

And existing Win32®-based applications can be ported with little or no
modification.

Does this mean an external hardware driver (e.g. for webcam) that
originally was meant for Windows 2000/Win XP is runnable on a Windows
XP Embedded platform without modification?

Thanks in advance!
 
The answer to your question is Yes.
For an application, while porting to XPe, it is typically required to satisfy all dependencies in your image to get it working.
Tools are used from Dependency Explorer to Filemon/Regmon and Inctrl5/RegSnap.
Drivers typically are easier to port. If you have the driver INF you can just import it with Component Designer. You are still
responsible though to get all the drier dependencies in your image. Although for drivers the dependencies are typically very minimal
(kernel, ntdll, etc.) and usually are present in every image you create anyway.

You may want to read a general FAQ for the product:
http://msdn2.microsoft.com/en-US/library/ms838350.aspx

--
=========
Regards,
KM


Hi,

I understand Windows XP Embedded is based on the same binaries as
Windows XP Professional.

And existing Win32®-based applications can be ported with little or no
modification.

Does this mean an external hardware driver (e.g. for webcam) that
originally was meant for Windows 2000/Win XP is runnable on a Windows
XP Embedded platform without modification?

Thanks in advance!
 
The answer to your question is Yes.
For an application, while porting to XPe, it is typically required to satisfy all dependencies in your image to get it working.
Tools are used from Dependency Explorer to Filemon/Regmon and Inctrl5/RegSnap.
Drivers typically are easier to port. If you have the driver INF you can just import it with Component Designer. You are still
responsible though to get all the drier dependencies in your image. Although for drivers the dependencies are typically very minimal
(kernel, ntdll, etc.) and usually are present in every image you create anyway.

You may want to read a general FAQ for the product:http://msdn2.microsoft..com/en-US/library/ms838350.aspx

--
=========
Regards,
KM


Hi,

I understand Windows XP Embedded is based on the same binaries as
Windows XP Professional.

And existing Win32®-based applications can be ported with little or no
modification.

Does this mean an external hardware driver (e.g. for webcam) that
originally was meant for Windows 2000/Win XP is runnable on a Windows
XP Embedded platform without modification?

Thanks in advance!
Click to expand...

I did some research on the internet, but it isn't quite clear yet.

Before installing XPe on a platform with no image preinstalled, you
always have to start with a WinXP install to the target platform
because otherwise you won't be able to run the "tap.exe" analyzer
tool, right?

Furthermore I don't understand how the preinstallation of WinXP to the
target platform would have to be done, which tools would have to be
used etc.
On a desktop system you would install XP by running the installation
CD, but embedded boards don't support this feature.
 
I did some research on the internet, but it isn't quite clear yet.
Before installing XPe on a platform with no image preinstalled, you
always have to start with a WinXP install to the target platform
because otherwise you won't be able to run the "tap.exe" analyzer tool, right?
Click to expand...

Not necessarily. You can also start with:
- boot to DOS and execute TA.exe. THis will produce PMQ file with very small number of components enumeratied vs TAP
approach. It is also possible that you will have to add some hardware related components manually to your config to be abel to boot
it.

- boot to WInPE and execute TAP. This approach is similar to XP Pro install but saves you from isnatlling the entire OS. TAP
result here is probably the more efficient too if you think about minimizing your image footpint.
http://msdn2.microsoft.com/en-us/library/ms932909.aspx

All these approaches are described in the product documentations: http://msdn2.microsoft.com/en-us/library/ms940856.aspx
Furthermore I don't understand how the preinstallation of WinXP to the
target platform would have to be done, which tools would have to be
used etc.
On a desktop system you would install XP by running the installation
CD, but embedded boards don't support this feature.
Click to expand...

Each embedded board is unique so there is no common steps. But you may try to:
- connect external/internal CD-ROM drive (do you have IDE on the board?) and boot to PE or XP Pro install CD
- use floppy disk to boot to DOS
- boot from UFD (USB Flash Disk) to DOS/PE/another XPe image (assuming your board has USB 1.1 or 2.0 supported)
- prepare the target storage to boot to PE, for instance (WINPE 2.0 can perfectly boot off a HDD)
- etc.

After all, you don't necessarily have to go by TAP/PMQ approach. You can add platform components to your image manually if you know
your hardware and the drivers required (read the board manual and specs).
 
Not necessarily. You can also start with:
- boot to DOS and execute TA.exe. THis will produce PMQ file with very small number of components enumeratied vs TAP
approach. It is also possible that you will have to add some hardware related components manually to your config to be abel to boot
it.

- boot to WInPE and execute TAP. This approach is similar to XP Pro install but saves you from isnatlling the entire OS. TAP
result here is probably the more efficient too if you think about minimizing your image footpint.
http://msdn2.microsoft.com/en-us/library/ms932909.aspx

All these approaches are described in the product documentations:http://msdn2.microsoft.com/en-us/library/ms940856.aspx


Each embedded board is unique so there is no common steps. But you may try to:
- connect external/internal CD-ROM drive (do you have IDE on the board?) and boot to PE or XP Pro install CD
- use floppy disk to boot to DOS
- boot from UFD (USB Flash Disk) to DOS/PE/another XPe image (assuming your board has USB 1.1 or 2.0 supported)
- prepare the target storage to boot to PE, for instance (WINPE 2.0 can perfectly boot off a HDD)
- etc.

After all, you don't necessarily have to go by TAP/PMQ approach. You can add platform components to your image manually if you know
your hardware and the drivers required (read the board manual and specs).
Click to expand...

Thanks for helping!

I think I will install WinXP first (CD-ROM drive) & then XP Embedded.

The embedded board indeed has an IDE-connector.
See: http://www.win-ent.com/IP-06058.htm
But what about the power cable and jumper settings then?

I guess the following book could be of great use:
http://www.amazon.com/Windows-Embedded-Advanced-Sean-Liming/dp/0929392779
 
Thanks for helping!

I think I will install WinXP first (CD-ROM drive) & then XP Embedded.

The embedded board indeed has an IDE-connector.
See:http://www.win-ent.com/IP-06058.htm
But what about the power cable and jumper settings then?

I guess the following book could be of great use:http://www.amazon.com/Windows-Embedded-Advanced-Sean-Liming/dp/092939...- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -
Click to expand...

And after 120 days the installed image on the board expires? Or is
this only the case for the development tools which are used to create
the XP Embedded image for the target board?
 
I think I will install WinXP first (CD-ROM drive) & then XP Embedded.

If you got CD-ROM working on the target, perhaps WINPE would be a faster
approach.
The embedded board indeed has an IDE-connector.
See: http://www.win-ent.com/IP-06058.htm
But what about the power cable and jumper settings then?
Click to expand...

If you don't have spare power cables on the device you could always use
another power supply, or, easier, just use a power cable from another open
PC that you turn on around the same time as the device.
Jumper settings should be documented in the board manual.

Regards,
KM
 
And after 120 days the installed image on the board expires? Or is
this only the case for the development tools which are used to create
the XP Embedded image for the target board?
Click to expand...

Development tool expiration is independent of the image expiration.
If you got eval toolkit it will expire in 120 days (I believe 120 days you
mentioned applies here).
With eval toolkit you won't be able to build production images either.

When you got full version of the tools and trying to build an image. If you
don't type the right PID in TD config settings your runtime will expire in
90 days.

Regards,
KM

PS. I never remember which is which when it comes to the XPe expiration day
limits. It may be vise versa - 120 days for runtime, 90 days for the
toolkit.
 
Development tool expiration is independent of the image expiration.
If you got eval toolkit it will expire in 120 days (I believe 120 days you
mentioned applies here).
With eval toolkit you won't be able to build production images either.

When you got full version of the tools and trying to build an image. If you
don't type the right PID in TD config settings your runtime will expire in
90 days.

Regards,
KM

PS. I never remember which is which when it comes to the XPe expiration day
limits. It may be vise versa - 120 days for runtime, 90 days for the
toolkit.
Click to expand...

A runtime operating system license (which includes the PID) can be
purchased in order to build a full-fuctioning run-time image.
http://msdn2.microsoft.com/en-us/library/ms940172.aspx

So a distributable image can be build by using the eval toolkit
(restricted time use of development tools) or is this only possible
with the full "Windows XP Embedded" product?
 
A distributable XPe image must be built with the full version of the toolkit.

In fact, with eval toolkit you will NOT have a way to type in PID in TD.
 
A distributable XPe image must be built with the full version of the toolkit.

In fact, with eval toolkit you will NOT have a way to type in PID in TD.

--
=========
Regards,
KM






- Tekst uit oorspronkelijk bericht weergeven -
Click to expand...

That makes Windows XP Embedded a pretty expensive solution!

It also makes sense now why the evaluation toolkit is completely free.
-)
 
Back
Top