![]() ![]() If I pass some funny arguments in, nothing happens with the application, but Process Explorer will catch and display them. ![]() For example a basic Windows Form C# application looks something like: private void Form1_Load(object sender, EventArgs e) I called taskmanager with my own odd command and the behavoir did not change:įrom a basic programming stand point, any application is going to have a main method of some sort where arguments can be passed in. Just because a command is sent, does not mean that a program accepts those arguments, or any. If I had to make an educated guess, I'd say that the numeric parameter was meant to be an internal startup indicator, possibly used for debugging purposes and then left behind. Manually starting the program using any of the arguments above doesn't seem to have any noticeable effect. The executable imports a couple of API functions (namely GetCommandLineW and CommandLineToArgvW) which are used to retrieve and parse command line arguments. Windows Vista and earlier operating systems are unaffected. Things worked in a similar way during the development phase of Windows 8, up until the Release Preview. Open a command prompt, type or paste taskmgr.exe, and press Enter. Type or paste taskmgr.exe in the Start menu search bar, and press Enter press Win+ R, type or paste taskmgr.exe in the textbox, and press Enter navigate to the System32 folder and double-click the taskmgr.exe executable start the System Configuration utility ( msconfig.exe), click the Tools tab, select the Task Manager item from the list, and click Launch. Start a non-elevated Task Manager, and click the Show processes from all users button. Press Ctrl+ Alt+ Del, and click Start Task Manager. Right-click the taskbar, and click Start Task Manager. Apparently it's not a documented behavior. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |