There was a small bug within the latest version that prevented the tool from exporting any driver. Please download the new fixed version.
I have added a new feature to Driver Extractor that allows you to export the device information of your current device to a PMQ file. The file format is identical to the TAP (Target Analyzer Probe) output.
Additionally I have added command line arguments so you can easily export all drivers from the command line.
These two features allow you to export the drivers for a specific system automatically so you can import them either into your Target Designer Component Database or Windows Embedded Standard 8 Catalog and use the exported PMQ file to automatically add the drivers to your image.
DriverExtractor.exe [tap] [export] [wes8|xp|copy] [path <path>]
export – will export all drivers in the format specified (wes8/xp/copy)
wes8 – Windows Embedded Standard 8 CTP1 Module
xp – XP Embedded / Windows Embedded Standard 2009 Component
copy – copy drivers only
path – specifies the output path
I have created a new version of my tool Driver Extractor which is now capable of creating Modules for Windows Embedded Standard 8 CTP1. The tool allows you to extract already installed drivers from your system with just a few clicks.
For the export you can also choose to package the driver into a Module (EMD) for Windows Embedded Standard 8 CTP1, a Component (SLD) for Windows XP Embedded & Windows Embedded Standard 2009 or you can just export the files.
The tool can be very helpful if you just have a system that has all the drivers pre-installed and you don’t have the driver CD at hand. It also saves you a lot of time because you don’t need to work with Module Designer or Component Designer to create your packages.
With the new version you can also import an INF file to create a component out of it – so the driver must not be installed on the system to extract it.
Also there are enhancements and bugfixes for the extraction routine.
Run the tool and select the devices of which you want to extract the drivers from.
Double-click a device to see which files are installed for the current device.
In the toolbar you can select the output format:
Click the Export button and select an output directory.
This will export all drivers to the selected format in the specified output folder.
If you want to convert a driver to a module or component you can select File / Import INF and select the INF file of the driver.
Then again select an output folder. Driver Extractor will create the package there.
The new Windows Embedded Device Manager 2011 enables you to manage all your embedded devices with a single tool.
This new tool integrates into Microsoft System Center Configuration Manager 2007 and it not only allows you to deploy and update images – you can differentiate between device types. This way updates can be deployed, e.g. only to Thin Clients but not to kiosks however both device types run Windows Embedded Standard 7.
Another great feature is that Windows Embedded Device Manager 2011 is able to control the write filters which might be enabled on your devices. Normally when a system has a write filter enabled and updates are applied the updates are gone again after a reboot – this is because the filter drivers redirect all changes made to the disk into a RAM overlay which gets reset on reboot.
When deploying updates via the Device Manager the system will handle this case properly by deactivating and reactivating the filter drivers automatically.
The tool works with all Windows Embedded Standard and Ready operating systems such as:
and because it is based on System Center Configuration Manager 2007 it can handle all Windows Embedded Enterprise systems as well.
More information about the tool can be found here:
The Driver Injector tool allows you to find suitable drivers for your target device automatically. The tool can be a great help if you have previously extracted all driver with Driver Extractor and want to inject them again automatically. Or if you have a driver CD/DVD and want to inject all drivers automatically to the image without having to install every device manually. Driver Injector needs a Target Analyzer Output file which contains all the device information from the target device and a driver search path. Then the tool will find all matches and allows to inject them with one click.
You have a bunch of drivers on the driver CD and need to install every driver one by one. In this case just run TAP to get the device information.
Then specify the driver search path – which is your driver CD. And click Next. Driver Injector will find the matching drivers and inject them to the image.
Sometimes there are missing files but Windows will not tell you why.
When this happens you just open the INF file with the tool and it will show you all missing files.
Driver Injector also allows to explore the content of an INF file. This feature will also display all missing files which are needed to install the driver properly. Missing files can happen on a Windows Embedded system in case not all components are installed but the driver depends on them. Missing files are being highlighted automatically by the tool.
How it works
Add additional information during driver selection
During the driver selection screen you can also add additional information to the selected device.
For this just select the device and click “Load Details”. Drive Injector will then add information about files, registry entries and services that are installed by the device. It will also highlight missing files.
To explore the whole INF file of an selected device driver just click “Explore INF”. Driver Injector will the open a new window displaying the whole content of an inf file. For more information read the “Explore INF File” section.
Driver Injector can run unattended with the following parameters:
DriverInjector.exe <devices.pmq> <DriverSearchPath> [OfflineImagePath]
If the [OfflineImagePath] is omitted then the current running OS will be modified.
Driver Injector can also be started to explore an INF file by using the following parameter:
The free Microsoft utility Windows SteadyState can be used on Windows XP Professional for Embedded Systems to prevent the OS from any changes.
It offers a write filter which will redirect all writes to a cache file which can be reset on a reboot. This will generate a fresh system on every boot.
Windows Updates can be installed even when the write protection is on. Additional security policies can be applied on the system using SteadyState.
This video demonstrates you the usage of imagex together with either Windows Vista AIK or Windows 7 AIK.
A detailed command description can be found here.
The video shows the capturing of an installed “ready-to-clone” image where it will be saved to an external harddrive.
The second part will show the deployment to a fresh system where the target disk still needs to be prepared.
Driver Extractor is a tool which makes creating SLD components for drivers very easy.
All you need to do is to run the tool on the target machine with XP, Vista or Windows 7 and all device drivers installed.
Then you just need to select the devices for which the drivers should be exported into an SLD file and click export.
Driver Extractor will then copy all the needed files and creates a component for XPe/WES with Repository for you.
After importing the component to the database you can easily create your image.
|File / End||Ends the program|
|Actions / Export Selected||Exports the drivers for the selected devices|
|Actions / Select All||Selects all devices|
|Actions / Deselect All||Deselects all devices|
|Actions / Refresh||Refreshes the device list|
|View / Files of selected device |
Contextmenu / Show Driver Files
|Shows the needed driver files for the current selected device|
|View / Properties |
Contextmenu / Properties
|Opens the Windows properties for the current selected device|
|? / About||Displays information about the tool|
There are two ways how you can remove these messages in Windows.
1. Use Minlogon
Minlogon will remove all the status messages and the logon window and logs the system on using the SYSTEM account.
Normally this works fine but if you need to access domains this solution will not work for you.
Also there are some other things (Cardspace,..) which will not work with Minlogon as it’s a minimum implementation of Windows Logon.
If you cannot use Minlogon you can go with the default Windows Logon and set the following Registry Key:
2. Windows Logon with hidden status windows
Create the following registry entry in the runtime image or add the following key to your Target Designer Image Configuration:
After this key has been set all the status windows will disappear.