Ummm, not being funny, but is the update process itself not a "triggered event"? Can't you just add on the running of BUU to the update task itself, so basically as soon as the update task completes, it then just moves on to BUU? and how do you trigger the "search for updates"? because if it is from the command line, that doesn't necessarily mean the task scheduler is triggered, unless that's how you call it. Another way to prevent an infinite loop, would be to have a flip flop counter, basically set a variable to 1, and on each run, if it equals one, set it to 2 and run the update again, if it's 2, set it to 1 and skip the update command. or use 0 and 1. but you get the idea, just create a flag that monitors if it's a first run or not.
post #331 of 399
5/12/16 at 5:13pm