Results for "Author: aminehaddad"
Most people use GetTickCount, but to be honest this makes GetTickCount look like a joke. QueryPerformanceCounter finds the time in microseconds, and not milliseconds (like GetTickCount). Why use this? If you wanted to see the time that it took for the cpu to proccess an API call, GetTickCount would find 0, because it takes less then a millisecond. But QueryPerformanceCounter would find the real time. I suggest using this because it is much more precise.
This program reads the output of CLI (Command Line Interface) Applications. Examples of CLI Applications are: -PING -NETSTAT -TRACERT This program will grab the output and call events so that you can process the commands. For example, if you ping a person, the output that is usely returned to the screen by the command prompt is captured and called into an event! This isnt a cheap method, it doesnt use any file input/output. Please vote if you like, would like to hear complaints about bugs if you find any, but I also appreciate comments ;) Thanks again -Endra
This program grabs the output from the Command Prompt (CMD.EXE or COMMAND.COM) and reads the output from whatever command you give it. NO EXTERNAL FILES! Really good for lots of programs, I really needed this so decided to share. This also kills the PID (ProcessID) when you cancel (thanks to Nick Campbeln for his PID Killing Function). This is also compatible with C/CPP programs (\n bug fixed). If you like this program please vote ;) Have fun!
Just like the previous versions except with a much better DOS like environment! For new users, this grabs output of CLI programs like PING, NETSTAT, etc. Some changes were made but none to the control! 'NEW IN V2.1: ' -Nice more DOS like environment ' -Replaced TextBox with Rich Text Format Box (More then 65535 chars allowed) ' -Added support to the DOS 'CLS' command (Clear Screen) ' -Replaced output of DOS 'CD' command to be C:\ ' -Made it show default path as C:\> ' -Colors changed ' -Added KeyPress event so you can press ENTER instead of clicking Execute
Most people use GetTickCount, but to be honest this makes GetTickCount look like a joke. QueryPerformanceCounter finds the time in microseconds, and not milliseconds (like GetTickCount). Why use this? If you wanted to see the time that it took for the cpu to proccess an API call, GetTickCount would find 0, because it takes less then a millisecond. But QueryPerformanceCounter would find the real time. I suggest using this because it is much more precise.
Just like the previous versions except with a much better DOS like environment! For new users, this grabs output of CLI programs like PING, NETSTAT, etc. Some changes were made but none to the control! 'NEW IN V2.1: ' -Nice more DOS like environment ' -Replaced TextBox with Rich Text Format Box (More then 65535 chars allowed) ' -Added support to the DOS 'CLS' command (Clear Screen) ' -Replaced output of DOS 'CD' command to be C:\ ' -Made it show default path as C:\> ' -Colors changed ' -Added KeyPress event so you can press ENTER instead of clicking Execute
This program grabs the output from the Command Prompt (CMD.EXE or COMMAND.COM) and reads the output from whatever command you give it. NO EXTERNAL FILES! Really good for lots of programs, I really needed this so decided to share. This also kills the PID (ProcessID) when you cancel (thanks to Nick Campbeln for his PID Killing Function). This is also compatible with C/CPP programs (\n bug fixed). If you like this program please vote ;) Have fun!
This program reads the output of CLI (Command Line Interface) Applications. Examples of CLI Applications are: -PING -NETSTAT -TRACERT This program will grab the output and call events so that you can process the commands. For example, if you ping a person, the output that is usely returned to the screen by the command prompt is captured and called into an event! This isnt a cheap method, it doesnt use any file input/output. Please vote if you like, would like to hear complaints about bugs if you find any, but I also appreciate comments ;) Thanks again -Endra
Most people use GetTickCount, but to be honest this makes GetTickCount look like a joke. QueryPerformanceCounter finds the time in microseconds, and not milliseconds (like GetTickCount). Why use this? If you wanted to see the time that it took for the cpu to proccess an API call, GetTickCount would find 0, because it takes less then a millisecond. But QueryPerformanceCounter would find the real time. I suggest using this because it is much more precise.
Just like the previous versions except with a much better DOS like environment! For new users, this grabs output of CLI programs like PING, NETSTAT, etc. Some changes were made but none to the control! 'NEW IN V2.1: ' -Nice more DOS like environment ' -Replaced TextBox with Rich Text Format Box (More then 65535 chars allowed) ' -Added support to the DOS 'CLS' command (Clear Screen) ' -Replaced output of DOS 'CD' command to be C:\ ' -Made it show default path as C:\> ' -Colors changed ' -Added KeyPress event so you can press ENTER instead of clicking Execute
This program grabs the output from the Command Prompt (CMD.EXE or COMMAND.COM) and reads the output from whatever command you give it. NO EXTERNAL FILES! Really good for lots of programs, I really needed this so decided to share. This also kills the PID (ProcessID) when you cancel (thanks to Nick Campbeln for his PID Killing Function). This is also compatible with C/CPP programs (\n bug fixed). If you like this program please vote ;) Have fun!
This program reads the output of CLI (Command Line Interface) Applications. Examples of CLI Applications are: -PING -NETSTAT -TRACERT This program will grab the output and call events so that you can process the commands. For example, if you ping a person, the output that is usely returned to the screen by the command prompt is captured and called into an event! This isnt a cheap method, it doesnt use any file input/output. Please vote if you like, would like to hear complaints about bugs if you find any, but I also appreciate comments ;) Thanks again -Endra
Most people use GetTickCount, but to be honest this makes GetTickCount look like a joke. QueryPerformanceCounter finds the time in microseconds, and not milliseconds (like GetTickCount). Why use this? If you wanted to see the time that it took for the cpu to proccess an API call, GetTickCount would find 0, because it takes less then a millisecond. But QueryPerformanceCounter would find the real time. I suggest using this because it is much more precise.
Just like the previous versions except with a much better DOS like environment! For new users, this grabs output of CLI programs like PING, NETSTAT, etc. Some changes were made but none to the control! 'NEW IN V2.1: ' -Nice more DOS like environment ' -Replaced TextBox with Rich Text Format Box (More then 65535 chars allowed) ' -Added support to the DOS 'CLS' command (Clear Screen) ' -Replaced output of DOS 'CD' command to be C:\ ' -Made it show default path as C:\> ' -Colors changed ' -Added KeyPress event so you can press ENTER instead of clicking Execute
This program grabs the output from the Command Prompt (CMD.EXE or COMMAND.COM) and reads the output from whatever command you give it. NO EXTERNAL FILES! Really good for lots of programs, I really needed this so decided to share. This also kills the PID (ProcessID) when you cancel (thanks to Nick Campbeln for his PID Killing Function). This is also compatible with C/CPP programs (\n bug fixed). If you like this program please vote ;) Have fun!
This program reads the output of CLI (Command Line Interface) Applications. Examples of CLI Applications are: -PING -NETSTAT -TRACERT This program will grab the output and call events so that you can process the commands. For example, if you ping a person, the output that is usely returned to the screen by the command prompt is captured and called into an event! This isnt a cheap method, it doesnt use any file input/output. Please vote if you like, would like to hear complaints about bugs if you find any, but I also appreciate comments ;) Thanks again -Endra
Most people use GetTickCount, but to be honest this makes GetTickCount look like a joke. QueryPerformanceCounter finds the time in microseconds, and not milliseconds (like GetTickCount). Why use this? If you wanted to see the time that it took for the cpu to proccess an API call, GetTickCount would find 0, because it takes less then a millisecond. But QueryPerformanceCounter would find the real time. I suggest using this because it is much more precise.
Just like the previous versions except with a much better DOS like environment! For new users, this grabs output of CLI programs like PING, NETSTAT, etc. Some changes were made but none to the control! 'NEW IN V2.1: ' -Nice more DOS like environment ' -Replaced TextBox with Rich Text Format Box (More then 65535 chars allowed) ' -Added support to the DOS 'CLS' command (Clear Screen) ' -Replaced output of DOS 'CD' command to be C:\ ' -Made it show default path as C:\> ' -Colors changed ' -Added KeyPress event so you can press ENTER instead of clicking Execute
This program grabs the output from the Command Prompt (CMD.EXE or COMMAND.COM) and reads the output from whatever command you give it. NO EXTERNAL FILES! Really good for lots of programs, I really needed this so decided to share. This also kills the PID (ProcessID) when you cancel (thanks to Nick Campbeln for his PID Killing Function). This is also compatible with C/CPP programs (\n bug fixed). If you like this program please vote ;) Have fun!
This program reads the output of CLI (Command Line Interface) Applications. Examples of CLI Applications are: -PING -NETSTAT -TRACERT This program will grab the output and call events so that you can process the commands. For example, if you ping a person, the output that is usely returned to the screen by the command prompt is captured and called into an event! This isnt a cheap method, it doesnt use any file input/output. Please vote if you like, would like to hear complaints about bugs if you find any, but I also appreciate comments ;) Thanks again -Endra