I like XPE it is much easies to test drivers.
If you are writing device driver then you only need to include your driver
files in their folders, and also you will need inf file to be in inf folder.
If you are writing pure software driver then you will need to populate
registry from TD (some your component perhaps).
For more info use google to read old archives.
My proffered configuration is small XPE test image (less than 60 MB) with
network support.
And one batch file that uses devcon for stopping driver copying binaries and
enabling driver.
My target device is connected trough RS232 to dev machine (I had some
problems with firewire).
Besides standard switches in boot.ini for debugger setup at some point you
might find interesting
/BREAK switch.
If you need to write and install some video drivers or disk drivers I would
use for this purpose second OS on your disk for copying files from network.
Only thing you will need to do is to. Reboot to Windows with net support
copy files using the batch and reboot your device to XPE.
Very easy for testing driver changes, especially in the beginning, when you
unload still have problems.
Also if you are writing drivers especially for XPE only. And you know
specific purpose of this XPE device, you can skip many steps required for
normal XP drivers. (Although I do not recommend it) If you are limited with
time then this XPE specifics can reduce dev time.
Regards,
Slobodan
kathy said:
I know the setup for writing driver for Windows XP.
My question is:
what is the setup for writing driver for Windows XP Embedded using DDK?
Host is Windows XP professional and target is Windows XP Embedded and
everything else is same as desktop setup?