RunOnce and FBA

[Guest]

I've got an ELO touchscreen serial device on my machine that, when it boots
into its default configuration, has inverted the Y axis. I created a
component that consists of a RunOnce request of the ELO's calibration
software. It has a dependency on the existance of the serial device as well.
All is fine, but when FBA runs, it appears to process the RunOnce request
before the touchscreen is initialized. The calibration software runs and
immediately fails, saying that there isn't a device attached to the system.
What I'd like to do is have the RunOnce work like it does in a normal
system--after the next boot, and not during FBA. Any ideas?

 

[KM]

William,

Not really sure I understand what "next boot" you meant for your RunOnce command but you definitely have some options to choose:
- FBA Generic Command (you have more control on when it gets executed specifying the command FBA phase)
- Explorer RunOnceEx key
- Explorer StartUp items
and more..

KM

 

[Guest]

"Next boot" after FBA has completed. The "first boot" of an XPE image runs
the FBA. The "next boot" is the first boot of the operating system itself.
I'll look into the generic command, but since I'm running a custom shell,
explorer registry keys won't do me much good. Thanks.

 

[RoyH]

William,

We also run a custom shell and have found that controlling some startup
activity through a Login script is simple, effective and easy to modify
remotely. You may need to control timing to wait for the ELO drivers to
load completely, but I think the newest ELO driver will give you a
return code so that you can control a try - wait - repeat loop.
For things that should run just once, I often simply create a
"calibrate.don" file and use the existence of the file to skip the
activity on subsequent logons. This makes it really easy for the
support folks to re-trigger the one-time activity, as needed for
recovery, by renaming or deleting the "calibrate.don" file.

HTH, Roy

 

[RussR]

Hi William,

I have experienced similar issues where I wanted to run some things by
issuing a RunOnce request in Target Designer under Extra Resources. It
unfortunately ran too early during the first boot process and none of the
other things I wanted to control had been initialized. So to get around
this, I used an FBG Generic command in target designer under Extra
resources. It is important to set the Phase to 8499 so it is one of the
last things that runs in FBA. this is to gurantee that all your things are
initialized. Set the filepath to whatever directory your program or batch
file or whatever is in. For example if you wanted to run a batch file
called domystuff.bat and it resided in the \windows directory you'd set it
up this way.
Filepath: %11%\cmd.exe
Arguments: /c %10%\domystuff.bat

Hope this helps, it has not failed me so far.