windowswideopen.com

To use enable verbose status messages by editing the registry, follow these steps:
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
4. On the Edit menu, point to New, and then click DWORD Value.
5. Type verbosestatus, and then press ENTER.
6. Double-click the new key that you created, type 1 in the Value data box, and then click OK.
7. Quit Registry Editor.
Note Windows does not display status messages if the following key is present and the value is set to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages
Operating System Windows 2000 Windows XPOperating System Windows 2000 Windows XP

No Comments »
Filed under: Operating System, Windows XP, Windows 2000

How to modify visual effect on Windows XP for performance.

1. Right Click on My Computer on the desktop of the Windows XP machine.
2. Select properties.
3. Select the Advanced tab -> Performance -> Settings
4. Select the Adjust for best performance radio button which unchecks all visual effect features.

The Visual Effects tab in the Performance Options dialog box allows you to select the settings you want to use for the visual effects and performance of Windows XP. with an easy way to set your preferences for the and performance of Windows XP. You can choose one of the following options:

1. Let Windows Windows choose what’s best for my computer
2. Adjust for best performance
3. Adjust for best appearance
4. Custom

The custom option allows you to choose which visual effect you want toenable/disable. Adjusting for best apperance uses all of the effects listed; adjusting for best performance uses none of them.
performance Uncategorized visual effects Windows XP XPperformance Uncategorized visual effects Windows XP XP

No Comments »
Filed under: Windows XP

SchedLgU.txt and SchedLog.txt exit/results codes defined:

You will only have a SchedLgU.txt or a SchedLog.txt depending on your operating system.Below is a list of the most common return codes, their meanings and some suggestions for you..

Result: The task completed with an excode of (100a518).

The job is completed successfully, but in many cases the internal tasks of the job are not completed successfully.

For code 0 or 0×0: The operation completed successfully.

For code 1 or 0×1: Incorrect function called or unknown function called.

For code 10 or 0xa: The environment is incorrect.

For code 0×8009000f: General Access denied

General page initialization failed. The specific error is: 0×80041315:

The task scheduler service is not running..
Unable to start task.

The specific error is:

0×80070002: The system cannot find the file specified.

Try using the Task page Browse button to locate the application.
Result Codes and Error Conditions are defined in Ntstatus.h or Winerror.h. These files are available on the MSDN Web site or through MSDN subscription. Because these are commonly used files, a search with the search engine is not likely to produce any useful result..
If a program does not start because the path to the program file is incorrect or because you typed a command-line switch within quotation marks, the following entry is added to the Schedlog.txt (Schedlgu.txt in Windows 2000/2003/XP) file:

“<program name>.job” (<program file name>) <date><time> ** ERROR **

Unable to start task.

The specific error is:

<error code>: The system cannot find the file specified. Try using the Task page Browse button to locate the application.
There is no formal standard for exit codes and no generic list of what exit codes mean. The meaning of the exit code is determined by the application vendor.

Use “err.exe” to track the exit code you are seeing.

A few common return codes are:

0×0: The operation completed successfully.

0×1: An incorrect function was called or an unknown function was called.

0xa: The environment is incorrect.

If the result code has the “C0000XXX” format, the task did not complete successfully (the “C” indicates an error condition).

The most common “C” error code is “0xC000013A: The application terminated as a result of a CTRL+C”.

x8004130f: No account information could be found in the Task Scheduler security database for the task indicated.
Explained Task Scheduler Task Scheduler Exit Codes Task Scheduler Results Codes Defined Task Scheduler Return CodesExplained Task Scheduler Task Scheduler Exit Codes Task Scheduler Results Codes Defined Task Scheduler Return Codes

No Comments »
Filed under: Task Scheduler

The AT Scheduler is a command line Scheduler.

This means, all work is done at CMD interface. To start working with the AT Scheduler, go to a CMD prompt. To do this, follow these steps.

Click on “Start” and select “Run”

Type in “CMD” (without the quotes) and click “OK”.

You will be at a command line interface.

Note The AT Scheduler does not care about your current directory location. For the sake of clarity, we are using the root of the C: drive in this troubleshooter.

C:>\AT /?

The AT command schedules commands and programs to run on a computer at a specified time and date. The Schedule service must be running to use the AT command.

AT [\\computername] [ [id] [/DELETE] | /DELETE [/YES]]

AT [\\computername] time [/INTERACTIVE] [ /EVERY:date[,…] | /NEXT:date[,…]] “command”

\\computername Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted.

id Is an identification number assigned to a scheduled command.

/delete Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled.

/yes Used with cancel all jobs command when no further confirmation is desired.

time Specifies the time when command is to run.

/interactive Allows the job to interact with the desktop of the user who is logged on at the time the job runs.

/every:date[,…] Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed.

/next:date[,…] Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed.

“command” Is the Windows NT command, or batch program to be run.

IMPORTANT: Tasks that Administrators want to run in the System Context must be setup using the AT command at a command line.

If any aspect of the task is modified (except changing the Task Name in the Task Scheduler User Interface) through the UI, the Set Account Information dialog will appear requesting that you enter a password once you hit Ok or Apply. The Domain and User Name of the user who is modifying the task is already entered as the user who’s context the task will run under in the Run As section. At this point the task will never run in the System Context again. This is because you’ve already hit Ok or Apply and erased the System Account information from within the task. Even canceling out of the Set Account Information will not restore the System Account as the Context to run the task in. If the credentials are changed and no password has been entered the task will fail with the following error:

“At<number>.job” (<executable>) <date/time> ** ERROR **

The attempt to log on to the account associated with the task failed, therefore, the task did not run.

The specific error is:

0×8007052e: Logon failure: unknown user name or bad password.

Verify that the task’s Run-as name and password are valid and try again.

.

Command line examples
Some basic examples of AT command lines:

The following command line schedules a task that runs notepad interactively the next time 12:00pm occurs.

C:\>at 12:00pm /interactive notepad.exe

The following command line schedules a task that runs notepad interactively on the server named TEST the next time 12:00pm occurs.

C:\>at \\TEST 12:00pm /interactive notepad.exe

The following command line displays the currently scheduled jobs on the server named TEST. Sample output is shown as well. (Note that each scheduled task is given an ID).

C:\>at \\TEST

Status ID Day Time Command Line

———————————————————–

1 Tomorrow 1:59 AM map.exe

2 Tomorrow 3:00 AM notepad.exe

The following command deletes the AT scheduled job with an ID of 1 from the Task Scheduler on the server named TEST.

C:\>at \\TEST 1 /delete

The following command schedules a task that runs notepad interactively every week on Thursday.

C:\>at 7:03pm /interactive /every:thursday notepad.exe

The following command schedules a task that runs notepad interactively every month on the 20th day.

C:\>at 7:03pm /interactive /every:20 notepad.exe
AT Command Task SchedulerAT Command Task Scheduler

No Comments »
Filed under: Task Scheduler

What is the task scheduler?

The Task Scheduler service allows you to perform automated tasks on a chosen computer. With this service you can schedule any batch file, program, or document to run at a time that is convenient for you or when a specific event occurs. Task Scheduler monitors the time or event criteria you choose and then executes the task when those criteria are met.

With the Task Scheduler you can:

• Create tasks.
• Schedule a task to run at a specific time or when a specific event occurs.
• Change the schedule for a task.
• Customize how tasks run.
• Stop a scheduled task.

There is a log file SchedLgU.Txt that captures the activity of Scheduled Tasks. By default the log file is located here: %SystemRoot%\Tasks\SchedLgU.Txt or on most systems : C:\Windows\Tasks\SchedLgU.Txt.

How to move the Task Scheduler log SchedLgU.Txt to different folder

If you need to move the task schdeuler log to different folder then here are the steps:

1. Click Start, Run and type Regedit.exe
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SchedulingAgent
3. Backup the SchedulingAgent key to a safe location.
4. Open the the LogPath value.
5. Change the path to the new target folder.
6. Close Regedit
7. Restart the Task Scheduler service by completing the following
8. Start -> Run -> Type services.msc
9. Locate the task Scheduler service in the list -> right click and select restart.
10. move the SchedLgU.txt file from %Systemroot%\tasks to the new folder.

Task SchedulerTask Scheduler

No Comments »
Filed under: Task Scheduler