On Jun 3, 3:52 pm, "Martin Grossen, eMVP [AVNET Silica]"
<martin.gros...@nospam.avnet.com> wrote:
> 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

Martin,

Thanks for the reply. Perhaps I was not clear enough in my original
post. I am aware that the Run key should be the solution. However, the
run key does not execute when Explorer is not running as the shell. I
just tested your instructions and it does not work even when "CMD -
Windows Command Processor" is in the image. To test, I set cmd.exe as
the shell so that explorer would not run. From there I checked the
registry and the Run key was indeed set according to your
instructions, but it still had no effect.

Just a note here, I am currently trying to run a VBScript using
wscript.exe. So my run command looks like

C:\WINDOWS\system32\wscript.exe //nologo C:\test.vbs

I have also tested batch scripts using the same settings as you
describe and get the same results either way, nothing works.

Kyle