|Image from www.october212015.com|
Tuesday, October 20, 2015
Wednesday, September 16, 2015
Saturday, August 29, 2015
|Image courtesy of http://www.digitalesq.com/|
Saturday, June 13, 2015
Thursday, April 25, 2013
If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes. Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple, do not start any copying or moving of files until the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on the installation. So instead of increasing our delay to God-Knows-How-Much , we went for another approach. That is to continuously try to kill the process ( after a certain delay ) until it is actually out of the task list. This would mean a:) continuously monitoring the task list to see if the process is still alive b:) create a loop that will do the monitoring of the task list, try to kill the process, delay for some time and repeat again.