Execute TAP.EXE without KB or MOUSE

  • Thread starter Thread starter thx
  • Start date Start date
T

thx

Hi,

I'm having an issue with my XPe image.

I cannot get my USB mouse or KB to work with the minlogon macro sample.

So, I would like to have TAP.exe run when the image boots without any
user intervention.

I've tried to do this with a registry key for autoexec.bat to be called
( under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
) & adding tap.exe to the batch file.

The system boots, but of course when I look for the devices.pmq file, it
doesn't exist.

1. Any other ideas as to how to accomplish this?

2. Is the minlogon macro sample write protected? Possibly the
devices.pmq file is being created in ram and never actually written to disk?

TIA
 
Sounds like you're getting confused about the process of running TAP...

The recommended method of running TAP is from Windows PE (stands for
"Pre Execution", or the "installer" version of Windows). You boot your
target hardware into WinPE from CD 1 of the XPE tools, then run TAP.
(There might be a trick involved if you don't have a hard disk in the
config to save the PMQ file to...using a network drive is the best
method.) You DON'T need to build an XPE configuration prior to running
TAP.

Search for the topics "Running Target Anaylzer" and "Detect Hardware
Devices with Target Analyzer and Windows PE" in the XPE documentation.

-- Don
 
Sounds like you're getting confused about the process of running TAP...

The recommended method of running TAP is from Windows PE (stands for
"Pre Execution", or the "installer" version of Windows). You boot your
target hardware into WinPE from CD 1 of the XPE tools, then run TAP.
(There might be a trick involved if you don't have a hard disk in the
config to save the PMQ file to...using a network drive is the best
method.) You DON'T need to build an XPE configuration prior to running
TAP.

Search for the topics "Running Target Anaylzer" and "Detect Hardware
Devices with Target Analyzer and Windows PE" in the XPE documentation.

-- Don
Click to expand...
Thanks for your input Don.

This method is used by "Configuring an XP Embedded Thin Client" By Sean
D. Liming & John R. Malin.

I've had no issues running TAP.exe from a minlogon macro sample on a CF
with USB KB and MOUSE support.

I've run into the issue now, when I do not have access to a KB or Mouse.

I'll look into the WinPE method, but if it is not able to configure my
KB and Mouse support, it will not fair any better.

Anyone else have ideas.
 
Sorry, I didn't realize it was a thin client (CF boot). Maybe you
don't have a CD drive?

I haven't used it, but it looks like the Minlogon macro component uses
the Command shell. For this shell, the proper registry for a startup
batch file is:
[HKLM\Software\Microsoft\Command Processor]
"AutoRun"="{Path to batch file}"

Put some debugging (ECHO or PAUSE) in your batch file so you can see if
gets executed.

If you're using the standard Minlogon macro, there's no EWF (disk write
protection overlay), so you should be able to write your PMQ directly
to the boot CF.

-- Don
 
Sorry, I didn't realize it was a thin client (CF boot). Maybe you
don't have a CD drive?

I haven't used it, but it looks like the Minlogon macro component uses
the Command shell. For this shell, the proper registry for a startup
batch file is:
[HKLM\Software\Microsoft\Command Processor]
"AutoRun"="{Path to batch file}"

Put some debugging (ECHO or PAUSE) in your batch file so you can see if
gets executed.

If you're using the standard Minlogon macro, there's no EWF (disk write
protection overlay), so you should be able to write your PMQ directly
to the boot CF.

-- Don
Click to expand...


Thanks again Don.

I'll try this change.

Where is this documented?

TIA
 
I haven't used it, but it looks like the Minlogon macro component uses
the Command shell. For this shell, the proper registry for a startup
batch file is:
[HKLM\Software\Microsoft\Command Processor]
"AutoRun"="{Path to batch file}"
Click to expand...


Or you can change the CMD Shell component properties in TD (somewhat documented way).
Change the path to shell from just cmd.exe to something like "cmd.exe /K said:
Put some debugging (ECHO or PAUSE) in your batch file so you can see if
gets executed.
Click to expand...

Echo's would definitely help, but Pause statemnets may not (no KB or mouse :-) ).
 
Sorry, I didn't realize it was a thin client (CF boot). Maybe you
don't have a CD drive?

I haven't used it, but it looks like the Minlogon macro component uses
the Command shell. For this shell, the proper registry for a startup
batch file is:
[HKLM\Software\Microsoft\Command Processor]
"AutoRun"="{Path to batch file}"

Put some debugging (ECHO or PAUSE) in your batch file so you can see if
gets executed.

If you're using the standard Minlogon macro, there's no EWF (disk write
protection overlay), so you should be able to write your PMQ directly
to the boot CF.

-- Don
Click to expand...

Awesome, [HKLM\Software\Microsoft\Command Processor]"AutoRun"="{Path to
batch file}" worked.

Now I have my devices.pmq, off to phase 2.
 
Back
Top