Tel: 800-362-6797
+1-248-827-4440
International
Facebook
Click for A Free Demo
 
 

Seasonal Time Changes

This page provides information about applying time changes to your DAD system during Daylight Saving for new dates beginning in 2007. For information about changing these settings for other Microsoft applications please refer to: http://support.microsoft.com/gp/cp_dst
 
Users should be aware that some locations within the United States do not observe the time change. Users within the European Union should also be aware that the dates of the time change can be different from the dates for the United States.
 
The dates for the time changes are as follows:
 

  United States European Union
 

Year DST Begins at 2 a.m. DST Ends at 2 a.m. Summertime period begins at 1 a.m. UT Summertime period ends at 1 a.m. UT
2012 March 11 November 4 March 25 October 28
2013 March 10 November 3 March 31 October 27
2014 March 9 November 2 March 30 October 26
2015 March 8 November 1 March 29 October 25

 
In general, ENCO is encouraging all users to update their machines to adjust for the new time change. The changes made to the system are all within the Registry. Users should make sure that they are logged into the operating system as an Administrator equivalent user.
 
If you do NOT make these changes, your workstation will not change to Daylight Savings Time on the proper date.
 
Windows 2003 Server
If you are running Windows 2003 server you should download and run the KB931836 patch from Microsoft. We have placed this patch on our FTP site for your convenience. Download the EXE and run it on your machine.
ftp://ftp.enco.com/pub/utilities/TimeZonePatch/Win2k3server/
 
Windows XP
If you are running Windows XP you should download and run the KB951072 patch from Microsoft. We have placed this patch on our FTP site for your convenience. Download the EXE and run it on your machine.
ftp://ftp.enco.com/pub/utilities/TimeZonePatch/WinXP
 
Windows 2000
If you are running Windows 2000 you should download and run 2KDSTFIX.EXE from our FTP site. This is a self-extracting ZIP file. Once extracted, run the 2KDSTFIX.BAT file. This will in turn run the REG and VBS script to make the necessary changes.
ftp://ftp.enco.com/pub/utilities/TimeZonePatch/Win2k
 
Windows NT
If you are running Windows NT, Microsoft has discontinued support for NT. Because of this, there is not a patch available from Microsoft. We have found a patch program from a third party that works with NT. This program has been placed on our FTP site for your convenience. Download the EXE and run it on your machine.
ftp://ftp.enco.com/pub/utilities/TimeZonePatch/WinNT
 
Novell Netware
If you are running a Novell Netware file server, you can visit the following link for more information.
https://secure-support.novell.com/KanisaPlatform/Publishing/60/3397648_f.SAL_Public.html

NOTE: ENCO System is no longer supporting Netware systems.
The change in time is a relatively easy process. The Windows operating system will change the time on the proper date and time. DAD will see this time change and continue to operate normally.
 
The main area of interest in preparing for the time change is the way a system is being synced. There are many ways a system can have time sync. If you are unsure about your configuration, call ENCO Tech Support at 1.248.827.4440.
 
For facilities that are receiving a relay closure to SYNC the time or are getting time from a Time Server, you should make sure the Date/Time Properties window has the option to "Automatically adjust clock for daylight saving changes" is checked. This will allow the Windows operating system to change the time.
 
Windows Date/Time Properties
 
For facilities that are receiving a time sync from an external source such as a GPS Clock or something that is sending time data strings to the workstation you should determine if the external device will automatically change the time. If the external device makes the adjustment for the time change and sends a time data string that includes HOURS, then you should have the checkbox unchecked. This will prevent both the external device and the Windows operating system from setting the time.

PLAYLISTS

Users should try to avoid having Branch and Timed Events such as Timed Recordings scheduled during the time change. Programmers should remember that in the Fall they will have a 25-hour day and in the Spring a 23-hour day. They should plan to adjust the playlists accordingly. DAD will not automatically re-play the hour in the Fall or skip the hour in the Spring.

DAD for DOS

NOTE: Do not use any Branch Events between 2 AM and 3 AM (inclusive) for SPRING or between 1 AM and 2 AM (inclusive) for FALL or your machine could get stuck in a loop and play that same hour again and again.
 
To gracefully change your system time:

For the FALL time change:

Create a Command Cut to perform the following:
 
[line 1] SYNC 4000
 
[line 2] SYNC 2000
 
[line 3] SYNC 0000
 
[line 4] TIMESYNC SERVER (network users only)
 
This Command Cut will set the clock to 1:40, 1:20, then 1:00, within the course of 0.5 seconds. The reason for the 3-step process is to avoid using a SYSTEM DCL command to call the DOS function TIME 01:00:00.
 
Schedule this Command Cut in one playback machine at 2 AM. The best way to accomplish this is to load playback machine 3 or 4 or any generally unused playback machine with a playlist that looks like this:
 
TIMED EVENT AT 02:00:00  A
 
99999 FALL BACK  N
 
Make sure the Command Cut has a Normal Transition.
 

For the SPRING time change:

Create a Command Cut to perform the following:
 
[line 1] SYNC 2000
 
[line 2] SYNC 4000
 
[line 3] SYNC 0000
 
[line 4] TIMESYNC SERVER (network users only)
 
This Command Cut will set the clock to 2:20, 2:40, then 3:00, within the course of 0.5 seconds. The reason for the 3-step process is to avoid using a SYSTEM DCL command to call the DOS function TIME 03:00:00.
 
Schedule this Command Cut in one playback machine at 2 AM. The best way to accomplish this is to load playback machine 3 or 4 or any generally unused playback machine with a playlist that looks like this:
 
TIMED EVENT AT 02:00:00  A
 
99998 SPRING AHEAD  N
 
Make sure the Command Cut has a Normal Transition.
 

For network users:

Create another command cut called SYNC TO SERVER and enter this command:
  • [line 1] TIMESYNC LOCAL
Create another playlist that will run in your remaining workstations:
  • TIMED EVENT AT 02:00:15 A

    99992 SYNC TO SERVER N
*****NOTE******
 
For network users using TIMESYNC, make sure you execute the first command listed above from the workstation that updates your server so that the server time will also be corrected. This workstation must have console operator rights. If you are not using TIMESYNC, make sure you update your server time Saturday night or Sunday morning by executing the following command at the server colon prompt: set time hh:mm:ss[a/p]
  • examples: set time 11:30:00p

    set time 1:00:00a