Windows Forum

Ask something
Discussion Locked

Issues with 'startup' entries (long)

0 helpful
4 replies

by herk.papadakis

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Is there a way to designate a particular order in which the 'startup' folder will execute 'startup entries'?

I have an application which once in a while will need to update certain SQL files on over 85 laptops. In order for this to take effect the 'SQL Service' has to be running first (once you reboot the laptop). The actual patch file gets entered into the 'startup' folder automatically and it starts executing before the 'SQL Service' entry. The name of the patch is 'AppPatch' (which I cannot modify) so it starts first (which promptly display a 'runtime error') because SQL has not start it yet.

Thank you for any help

4 replies

by sgt_shultz

well, this isn't the step by step you are looking for but can you change the sql service to start manually, the figure out command line for starting it. then write batch file that starts sql server, and have that batch file call your appPatch batch file? put that batch file in startup?
or, if custom app, fix it so it looks for updates upon starting?

by herk.papadakis

I thought about doing that, except I have 85 nurses which I do not want to try to do this everytime they turn on their laptop. The other issue is that the patch file is not in the 'startup' folder everyday. We actually use an application to push thefiles to the laptop(s) which in turn creates the patch file in the startup folder. The theory is we push multiple files to the laptop(s) and once they turn them on the patch file executes and updates SQL tables. Actually it is working OK. If the laptop is in good shape (defrag...) then SQL runs quickly and we have no problem.

by sgt_shultz

well, it shouldn't matter if the batch file is there. get a book on NT Shell scripting and you will see ways to check for a file and run stuff conditionally. you need to help us help you more. you aren't giving us your os version or enough details. do some experimenting?

by herk.papadakis

Sorry, the OS is W98.
Let me try to explain how all works.
A - The ?startup? contains the ?SQLSRV.EXE? file which executes and starts SQL services.

B - I receive an update to the SQL app. The update is SQL script, which I have to run against the SQL db on the SQL-DB Server. Once done I use the ESD Manager (Electronic Software Distribution) from the App. Server in order to pass the update to the laptops. Simple in terms of execution. Open ESD, pick required file, which has an *.luf extension, pick names of laptops to get updated and I am done. At this point the ESD creates the ?AplPatch.exe? file. The ?AplPatch.exe? contains SQL Scripts.

C - During the day our users have to either dial-in or come to the office to sync their laptop db with the server db. During the sync process the ?AplPatch.exe? file gets uploaded to the laptop(s) and it is placed in the ?startup? folder. The next time the user reboots the laptop the ?AplPatch.exe? starts to execute. Here is where my problem begins. Because ?AplPatch.exe? contains SQL scripts the SQLSRV.EXE has to run 1st, otherwise the user gets a run time error. It is always a matter of milliseconds. If the user has done a defrag lately the SQLSRV.EXE runs quick and the ?AplPatch.exe? has not finished loading, then everything works correctly. If the laptop is running slow, then the SQLSRV.EXE has not finished loading yet and the ?AplPatch.exe? comes right behind it and because SQLSRV.EXE it's not loaded yet the ?AplPatch.exe? creates the run time.

The workaround is to manually go to the ?startup? folder and re-execute the ?AplPatch.exe? again.

What I am looking for is, a way to modify the registry and specified a time lapse for the entries in the ?startup'. Something I can put in place once and not have to worry about it again. My users are nurses and they are familiar with the SQL App, but I do not want them venturing with the OS.

This discussion is closed to new replies.