All tag results for ‘Command-line’
May 14th, 2008 · No Comments · 114 views
Consider the following scenario:
- You create a scheduled task on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1).
- One or more command-line arguments in this scheduled task are enclosed in quotation marks.
In this scenario, the scheduled task does not run as expected. Additionally, a value of 0×1 appears in the Last Run Result column.
For example, assume that you create a scheduled task by running the following command-line argument:
schtasks /create /tn "Test Scheduled Task" /tr "c:\temp.bat \"1-Jan-70 8:00:00\"" /sc daily /st 03:15:00 /ru System
The scheduled task fails after it starts at 03:15. However, if you delete the quotation marks around “1-Jan-70 8:00:00,” the scheduled task runs successfully.
Note: The issue does not occur in Windows Vista or in Windows Server 2003.
May 7th, 2008 · No Comments · 349 views
How do you manage a Windows Server 2008 Server Core? It has no GUI, so you normally would have to use the command line. You can, however, use Remote Server Administration Tools, as described in this article, from your Vista SP1 machine so you can enjoy a GUI interface. Keep reading →
June 20th, 2007 · No Comments · 929 views
Consider the following scenario. A 16-bit application is running on a Windows Vista-based computer. This 16-bit application passes command-line parameters to another application. For example, the 16-bit application calls the ShellExecute function to start another application. Meanwhile, the 16-bit application passes command-line parameters to the newly-started application.
In this scenario, the second application starts. However, the second application does not receive the command-line parameters. Therefore, the second application may not work as expected.