Hi Kyle

Of course, you can not use the FBA (First Boot Agent) or
the RunOnce.
Per naming and definition, both will only processed during the first boot
of the system.
The standard RUN key in the registry will help you.
(HKLM/Software/Microsoft/Windows/Current Version/Run)
You can do this easely (to test) by adding a "Extra Registry Data" and the
batch as a "Extra File" resource int your image via Target Designer.
Of course more elegant is to cretae a own component in component designer
with the registry key and the file in a own repository.
This is the same as you can drag and drop something in the
Autostart folder of your Explorer-Shel.

The right command for the key in the registry is:

C:\System32\cmd.exe /c yourpath\yourbatch.bat

of course, you must have the component "CMD - Windows Command Processor"
included in your image.

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

"kthompson" <thompsonk87@gmail.com> schrieb im Newsbeitrag
news:f3de6fbc-6cd4-4c8e-aee0-5334c75acf8e@r66g2000hsg.googlegroups.com...
>I am attempting to find a way that I can run a VBScript or a batch
> file every time my image boots. This is more difficult than just
> adding another Run key because I am not running explorer as the shell.
> I was under the impression that in the abscence of explorer, the FBA
> would process the Run items at every boot. However, testing has proved
> this to be false, at least in my case. I also tried adding a RunOnce
> item because a source indicated it is processed by the FBA during the
> initial boot and every logon thereafter.
>
> After some searching I am at a loss. So far I have tried setting the
> Userinit key to run my script as suggested in the discussion entitled
> "What runs the Run/Runonce settings ?". I have also tried adding a Run
> item in TD with CMD as the filepath and batch/script included in the
> arguments. This was suggested in another discussion entitled "Run
> batch command after fba".
>
> So currently I am at a loss, I want the script to run every time the
> system boots and not just once during the initial FBA. For reference,
> I am currectly running minlogon. I have also been testing lately with
> the command shell for simplicity instead of our custom shell. Both the
> command shell and the custom shell have exhibited the same symptoms I
> described above.
>
> It seems like this is a common problem, but I have not found a
> resolution. Does anyone has some insight or suggestions?
>
> Kyle