Hal didn't run a scheduled event.

Cause:

The event was created after its start time. In other words, if you created the event at 4:00pm but said you wanted it to run daily at 2:00pm, then HAL will wait until the next day before running the event.

Solution:

Cause:

The scheduled event affects a light or appliance and the light or appliance is turned off at the base. HAL ran the scheduled event, but because the light or appliance was turned off it didn't receive the command. In other words, if a lamp is physically turned "off" then HAL can't control it.

Solution:

Cause:

Some of HAL's files may have been corrupted. System crashes, hard drive problems, viruses, and rebooting the computer without shutting down HAL may cause relevant files to be damaged.

Solution:

Cause:

HAL isn't running or the computer's power management is enabled. If HAL isn't running or the computer's power management is enabled (hard drive spins down when not in use), then HAL can't control lights or appliances, download information from the Internet, answer phone calls, respond to verbal commands, or anything else.

Solution:

Disable the computer's power management if it's enabled. To disable it, go to Start… Settings… Control Panel. When the Control Panel screen appears, double-click on POWER MANAGEMENT. In the Power Management screen, set the field "Turn off hard disks" to NEVER. If the computer's microphone is part of the monitor or draws power from the monitor and you want to be able to talk to HAL at any time through the monitor, then you must set the field "Turn off monitor" to NEVER. If the computer's microphone isn't connected to the monitor in any way, then you can set the "Turn off monitor" field to any option.