In VB, The shell command (and many, many others) spawns a process, and then immediately returns to the next line of code execution. This isn't a problem, really. The problem comes about, when you want to WAIT for a spawned process to finish, before spawning a new process. For example, if I wanted to spawn notepad, and a calculator at the same time, this code would work (technically, it's not at the same time, but it's one immediately after the other, and doesn't wait.... so it appears to be at the same time):
shell "c:\windows\notepad.exe"
shell "c:\windows\system32\calc.exe"
Comatose
Taboo Programmer
2,910 posts since Dec 2004
Reputation Points: 361
Solved Threads: 215
Ok, I'm not clear on what you are doing really. I understand that you want to install the updates, 1 by 1..... but when does windows conflict? What's the problem? Do you know the commandline needed to launch the updates you want to launch? Doing this in a batch file is possible, (assuming I understand exactly what you are doing), but I don't see the pro's of using a batch versus a VB program.....
Comatose
Taboo Programmer
2,910 posts since Dec 2004
Reputation Points: 361
Solved Threads: 215