Target Analyzer Probe (TAP) Technical Reference (Standard 8)
7/8/2014
Review the use, syntax, options, and parameters of Target Analyzer Probe (TAP) for Windows Embedded 8 Standard (Standard 8).
Target Analyzer Probe (TAP) is a command-line tool that you can use to produce a comprehensive listing of hardware on your device. There are different versions of TAP based on the device architecture it is being run on. Windows Embedded 8 Standard Toolkit (Standard 8 Toolkit) includes both a 32-bit (tap_x86.exe) and a 64-bit (tap_amd64) version of TAP but each bootable Image Builder Wizard (IBW) disk includes a TAP executable (tap.exe) that is architecture-specific.
TAP runs on Windows XP, Windows 2000 Service Pack 2, Windows Preinstallation Environment (Windows PE) 4.0, Windows Vista, Windows 7, and Windows 8.
Note
If you run TAP from Windows PE 4.0, it’s possible that some devices may not be detected. If you run TAP from Windows 8, Windows 7, Windows Vista, or Windows XP, TAP will detect all devices, but it may also detect devices, such as USB drives, that do not need drivers.
Syntax
tap.exe | tap_x86.exe | tap_amd64.exe
[/o <file_name>]
[/r]
[/i]
[/q]
[/?]
Where to Find TAP
The executable file for TAP and in a typical installation of Windows Embedded 8 Standard (Standard 8), this file can can be found at one of the following locations:
- %PROGRAMFILES%\Windows Embedded 8 Standard\Toolset\Embedded Tools\
- tap_x86.exe
- tap_amd64.exe
- %PROGRAM FILES%\ Windows Embedded 8 Standard\Toolset\IBW\x86\sources\tap.exe
- %PROGRAM FILES%\ Windows Embedded 8 Standard\Toolset\IBW\AMD64\sources\tap.exe
Command-Line Options and Parameters
Option |
Description |
|---|---|
|
Specifies the file name of the output file. The default name of the output file is devices.pmq. If you specify a file name for the output file, it must have a .pmq file name extension and TAP adds one if it does not. |
|
Changes the registry path to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001 from the default value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet. |
|
Ignores software-enumerated devices. |
|
Runs TAP in quiet mode. |
|
Displays all command-line options for TAP. |
Known Issues
USB Hubs on Honeywell Boards
TAP.exe cannot autodetect USB Hubs on Honeywell Boards and thus cannot automatically add drivers for those hubs. To work around this issue, you must either run TAP.exe on a system where the USB drivers are already installed and working correctly or you must manually add these drivers to your image. The drivers are:- INF-usbhub3
- INF-usbxhci
The driver binaries needed are:
- usbhub3.inf
- USBHUB3.SYS
- usbxhci.inf
- USBXHCI.SYS
- UCX01000.SYS
These driver binaries can be obtained by unzipping the following cab files in your catalogs modules\Driver directory:
Important
You must install the latest Windows Embedded 8 Standard Toolkit (Standard 8 Toolkit) to use these workarounds. If you are using an older version of Standard 8 Toolkit, the workaround will not result in the drivers being added correctly.