DosTips.com

So i have batch1 as this

and then i reboot computer (windows8) and batch2 starts. It seems like the batch is starting before windows. Because ther is only a black background and the cmdwindow,

When i "x" the batchfile,windows contiune booting. My problem is that i need the computer connectet to internet to get my batch working. So i need the batch to load after the windows is finnish loading.

Any clue?

Don't automatically start batch2.bat?

Yury wrote:

Code: Select all

@echo off

set timeout=60

>nul timeout /nobreak /t %timeout%

::::::::::::::::::::::::::::::::::

But the windows wil not boot until the bach is closed.

ShadowThief wrote:Don't automatically start batch2.bat?

If that was a solution i have noe created this post.

Instead of running the batch file from the RunOnce key, add a self delete command to the bottom of it and place a shortcut to your batch file in the startup folder, "%AppData%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup".

Compo wrote:Instead of running the batch file from the RunOnce key, add a self delete command to the bottom of it and place a shortcut to your batch file in the startup folder, "%AppData%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup".

"%AppData%\Microsoft\Windows\Start Menu\Programs\Startup"

Yury wrote:

Compo wrote:Instead of running the batch file from the RunOnce key, add a self delete command to the bottom of it and place a shortcut to your batch file in the startup folder, "%AppData%\Roaming\Microsoft\Windows\Start Menu\Programs\Startup".

This will not work for me because the batch is in diffrens path from pc to pc. (running from usb)
I got a answer from diffrent forum. http://superuser.com/questions/834047/batch-is-starting-too-fast-after-reboot/834196#834196

I saw the solution from the other forum and it only introduces a delay in the execution of the batch file. But if what you really need to check is if there is Internet access you can use something like this:

I believe windows starts your batch file and then waits for it to complete before loading the desktop and connecting to the internet. if you make the batch start another instance of itself and have the initial instance exit, windows will assume the batch has completed and should continue to load the desktop..

Good thinking Ed, that's important too.

I assumed that problem was solved when the ping delay was hailed as a solution.

Try a different approach:

Create a scheduled task to run the batch file, and set a trigger to run at log-on.

If you need it - under advanced properties there is an option to delay running the task. 30 seconds would probably work.