Manually recorded series don't "get" daylight savings

I have a manual series for Sunday nights--The Simpsons and Family Guy seem to do a poor job of flagging "new" versus "repeat" in the schedule and a standard series recording will get me all of the daily reruns on a bunch of channels. So, I set a manual recording for each show. Every spring and fall, the DVR seems to screw it up--I have to delete the series and enter them again.
For example, a week ago, I had a manual recording from 8-8:30 and another for 9-9:30. Those morphed into 9-9:30 and 10-10:30. Obviously, I can keep one (since it basically switched the show it is taping) but I'd think that the record command would keep up with the time change.
Thanks!

The alarm issue is a known problem and apparently Apple plans on fixing it with iOS 4.2. Here's a link to news items about the alarm issue.
http://www.google.ca/search?q=applealarmissue&hl=en&client=firefox-a&hs=M4Z&rls=org.mozilla:en-US:official&prmd=nfd&sour ce=univ&tbs=nws:1&tbo=u&ei=jqLZTMLiOITWtQPt2pi3Bw&sa=X&oi=news_group&ct=title&re snum=1&ved=0CCIQqAIwAA

Similar Messages

When I generate the "Create Process Manual" Report I'm not getting any links

Hi
I have a BPMN diagram in Oracle BPA 11.1.1.3. Many activities have links. When I generate the "Create Process Manual" report I don't get any links.
Regards

Thanks, HDMI does not appear to be option in either output or sound effects. Even when connect the RCA to the headphone jack. then and option appears in both output and sound effects, heaphones. Still not working.

Manual request for email still gets email when not requesting sync

I have an iPhone 4s with a mail for exchange account set up on it. My settings are set for manual so I don't get email pushed to me all the time. I am using iOS6 at the moment. Whenever I turn on the phone, it checks and updates my inbox. Even when on 5.1.1, it checked now and then without me asking to sync but now on OS6, it has happened everytime I boot up alongside the occasional not requested sync. Anyone else have this issue? Is there a fix?

How will that fix the problem? I have been using the refresh and load more messages options on the email accounts. There are extended periods throughout the day that email will not be received. Samsung did not have a solution and neither did Verizon technical support. There are several others with the same issues. We should not have to do manual syncs and it is a sporadic problem.

Can't Get Manual Recording To Work

I have been unable to get manual recording to work and thought this was something to do with having dual monitors. I have now disabled my second monitor, and it is still not working for me. It's possible that I have done something wrong or have misunderstood what manual recording is.
To that end I have made a 3 minute video showing you the steps I took while attempting a manual recording of just three print screens. Please could someone take a look ta the video and tell me if what you see is expected behaviour. Thank you.
manual-recording.mp4 - Google Drive

Thank you for taking a look at the video Rick. You can probably tell this problem is driving me mad.
I did as you suggested but it made no difference to the outcome. So next I uninstalled Captivate, and re-installed with only one monitor active, just in case that mattered. I then kept it at one monitor but even with only one monitor videos appear in my manual captures.
So next I re-enabled my second monitor and ran the test again. On monitor 1, video is included no matter what, and on monitor 2 it isn't. I have filed a bug report with Adobe but so far the response has been to try running it as administrator and also to check the error logs. I checked those and there is nothing but informationals in there.
I also ran the entire test when running as an admin, and the results were the same.

Adding AAAA records to DNS manually (Server Manager don't let you add them)

Using the following webpage http://www.isi.edu/~bmanning/v6DNS.html#named.conf I have been able to get IPv6 name resolution setup, so that clients will use IPv6 for connecting to my server on the LAN when possible (e.g. Mail, iChat, Web).
This is working well, and the records also display in Server Manager. I have tested add/remove/update to existing records in DNS to make sure the manually added AAAA records don't get wiped out, and they don't .
NOTE: Put AAAA records above A records. Not sure why, but this prevented a few problems I initially had.
I haven't had a go at making a reverse lookup zone yet for IPv6, but if/when I do, I shall post here.
Below is a before -> after of the following files I had to edit, using nano under sudo in Terminal:
Zone name: test.com
File: /var/named/zones/db.test.com.zone.apple
Owner: root:wheel
*Before AAAA:*
;GUID=9ACB60A1-BB9E-496A-BF3F-D23D8BA52DE4
$TTL 10800
test.com. IN SOA test.com. admin.test.com (
2009081800 ;Serial
86400 ;Refresh
3600 ;Retry
604800 ;Expire
345600 ;Negative caching TTL
test.com. IN NS test.com.
test.com. IN A 172.16.0.143
test.com. IN HINFO "Mac Pro 1.1, 9GB RAM" "Mac OS X Leopard Server 10.5"
SipuraSPA.test.com. IN A 172.16.0.148
camera.test.com. IN A 172.16.0.175
dd-wrt.test.com. IN A 172.16.0.200
XBMC.test.com. IN A 172.16.0.147
XBMC.test.com. IN HINFO "Microsoft XBox" "XBox Media Center"
Office-Mac-mini.test.com. IN A 172.16.0.149
Office-Mac-mini.test.com. IN HINFO "Mac Mini G4" "Mac OS X Leopard 10.5"
N95.test.com. IN A 172.16.0.141
N95.test.com. IN HINFO "Nokia N95 8GB" "Symbian OS"
switch.test.com. IN A 172.16.0.173
ucs.test.com. IN A 172.16.0.230
LinksysPAP.test.com. IN A 172.16.0.152
wireless.test.com. IN A 172.16.0.131
trixbox.test.com. IN A 172.16.0.129
trixbox.test.com. IN HINFO "Dell Precision Workstation" "Trixbox 2.6"
trixbox.test.com. IN TXT "IP PBX"
intranet.test.com. IN A 172.16.0.143
lb.dns-sd.udp IN PTR test.com.
test.com. IN MX 10 test.com.
*After AAAA:*
;GUID=9ACB60A1-BB9E-496A-BF3F-D23D8BA52DE4
$TTL 10800
test.com. IN SOA test.com. admin.test.com (
2009081800 ;Serial
86400 ;Refresh
3600 ;Retry
604800 ;Expire
345600 ;Negative caching TTL
test.com. IN NS test.com.
test.com. IN AAAA 2002:aaaa:aaaa:0000:0217:f2ff:fe04:35ec
test.com. IN A 172.16.0.143
test.com. IN HINFO "Mac Pro 1.1, 9GB RAM" "Mac OS X Leopard Server 10.5"
SipuraSPA.test.com. IN A 172.16.0.148
camera.test.com. IN A 172.16.0.175
dd-wrt.test.com. IN A 172.16.0.200
XBMC.test.com. IN A 172.16.0.147
XBMC.test.com. IN HINFO "Microsoft XBox" "XBox Media Center"
Office-Mac-mini.test.com. IN A 172.16.0.149
Office-Mac-mini.test.com. IN HINFO "Mac Mini G4" "Mac OS X Leopard 10.5"
N95.test.com. IN A 172.16.0.141
N95.test.com. IN HINFO "Nokia N95 8GB" "Symbian OS"
switch.test.com. IN A 172.16.0.173
ucs.test.com. IN A 172.16.0.230
LinksysPAP.test.com. IN A 172.16.0.152
wireless.test.com. IN A 172.16.0.131
trixbox.test.com. IN AAAA 2002:aaaa:aaaa:0000:020d:56ff:fe10:deb7
trixbox.test.com. IN A 172.16.0.129
trixbox.test.com. IN HINFO "Dell Precision Workstation" "Trixbox 2.6"
trixbox.test.com. IN TXT "IP PBX"
intranet.test.com. IN AAAA 2002:aaaa:aaaa:0000:0217:f2ff:fe04:35ec
intranet.test.com. IN A 172.16.0.143
lb.dns-sd.udp IN PTR test.com.
test.com. IN MX 10 test.com.
I hope this comes in handy for someone.
Tony

Tony,
Be aware that your ;SERIAL directive MUST change if you made changes to the file.
The <serial-number> directive is a numerical value incremented every time the zone file is altered to indicate it is time for named to reload the zone.
I do not know for sure, but this might be why the data has not been wiped out or otherwise modified by Named or might have caused or is hiding some of the difficulty you experienced.
Peter

My iphone 4 has changed to daylight savings. I do not live in an area with daylight savings? How do i keep the phone on automatic with the correct time?

My iphone 4 has changed to daylight savings. I do not live in an area with daylight savings? How do i keep the phone on automatic with the correct time?

I have the same issue. I live in Arizona and we also don't do that stupid daylight savings. When I put it to auto it says Denver. Location should pick up Phoenix. Needs to get fixed because I have to manually set it every time I travel now until DST is over.

Time Conversion from Local to UTC Help! - Daylight Savings Problem?

Hi,
I am trying to use the generic conversion of local time to UTC time. I thought I had everything working since I use the "Get Date/Time in Seconds" and then convert to "Seconds to Date/Time" witht the "to UTC" flag set true. Then I convert back to a timestamp.
I thought I had everything working until I hit Daylight Savings for the Pacific Standard Time. Now the Labview is off by 1 hour!
Is there an update to the Subvi's that do this? Is this a known error? Please help. Thank you!
Attachments:
test25_LocalToUTC_Time.vi ‏8 KB

Here is the path you are doing that is causing the logic to fall apart for you.
1. You are getting the current time. In your images, it is 12:41 pm PDT which is 7:41 pm GMT
2. You are asking for the date/time record (that cluster that breaks out everything) but are saying it is UTC, so you get a date/time record that 19:41 UTC (7:41 pm). And the DST flag is 0. (Because UTC doesn't observe daylight savings time.)
3. Now you are taking that date/time record and converting back to an actual date/time. You don't wire up the UTC flag so it defaults to false. Thus the date/time record is interpreted as local. That DST flag is still 0 in your cluster. So you are actually converting the time to 7:41 pm PST, which is actually 8:41 PDT. (+1 hour for spring forward based on the month/date info.)
4. You are displaying that time stamp in the indicator labelled "Current Date/Time (UTC)", but it is not truly UTC, it is actually the conversion of a local time from PST to PDT, and it is not even the current local time. It is actually a "local" time 8 hours into the future. If you put the carat into that indicator's display format, you'll see that the UTC time is in the future as well. You call it UTC, but you are displaying a future local time.
The inconsistent conversions from local to UTC, and not accounting for the change of the DST flag from daylight time to UTC are what is confusing you. You kind of get lucky during standard time because the DST flag is 0 for both local standard time and UTC. But the conversions are still wrong, but it is a case of two wrongs are making it look right. Even in standard time your input timestamp and your output timestamp indicator don't match which you would see if you used an Equals? function on them.

Daylight Savings time, and how dates are stored internally and displayed

This is probably a question that appears here annually, but I couldn't really find clear answers, so I'll try asking this in my own words:
I'm in the Eastern timezone, and this Sunday, we'll be turning our clocks back an hour at 2:00 AM. That means that accordign to us humans, the time 1:30 AM will occur twice on Sunday.
I've got an Oracle application that runs every 5 minutes around the clock, and it selects records from a certain table whose updated timestamp (TIMESTAMP(6)) is greater than SYSDATE - 5/1440, meaning any record that was updated in the last 5 minutes. Will we have a problem with some records being processed twice on Sunday morning? I'm theorizing that everything will be OK, that internally, Oracle stores DATE fields using something like an epoch which then gets interpreted when we display them. An epoch value will continue to grow each second no matter what “time” it is according to the U.S. Congress.
A simpler way to look at the question might be as follows:
If you store SYSDATE in a DATE column in row “X” at 1:30 AM before the time change, and you store sysdate in row “Y” exactly one hour later, will Oracle say that X’s timestamp is 60 minutes less than Y’s timestamp? All fields that are related to my particular situation are either DATE or TIMESTAMP(6).
We use 11g.

>
That settles that! Thank you! My theory was wrong! I appreciate the help.
>
You may think it settles that but, sorry to burst your bubble, that doesn't really settle much of anything.
One thing that was settled is the answer to this question
>
But are they talking about what you can EXTRACT and DISPLAY from the field or what is actually STORED internally?
>
which is, as Mark stated, they are talking about what is stored internally.
The other thing that was settled is that you will pull the same, or mostly the same, data twice during that one hour. I say 'mostly the same' because of the major flaw your extraction method has to begin with.
>
If you store SYSDATE in a DATE column in row “X” at 1:30 AM before the time change, and you store sysdate in row “Y” exactly one hour later, will Oracle say that X’s timestamp is 60 minutes less than Y’s timestamp?
>
No - they will have the same time since 'one hour later' would have been 2:30 AM but the clock was turned back an hour so is again 1:30 AM. So the second time your job runs for 5 minutes at 1:30 AM it will pull both the original 1:30 AM data AND the data inserted an hour later.
And Oracle will say that data stored in row "Z" exactly 45 minutes later than "X" at 1:30 AM will have a date of 1:15 AM and will appear to have been stored earlier.
Your method of extracting data is seriously flawed to begin with so the daylight savings time issue is the least of your problems. The reason is related to the answer to this question you asked
>
do people avoid using DATE and TIMESTAMP datatypes because they are too simple?
>
That method isn't reliable - that is why people avoid using a date/timestamp value for pulling data. And the more often you pull data the worse the problems will be.
>
I've got an Oracle application that runs every 5 minutes around the clock, and it selects records from a certain table whose updated timestamp (TIMESTAMP(6)) is greater than SYSDATE - 5/1440, meaning any record that was updated in the last 5 minutes
>
No - it doesn't do that at all, at least not reliably. And THAT is the why your method is seriously flawed.
The reason is that the value that you use for that DATE or TIMESTAMP column (e.g. SYSDATE) is assigned BEFORE the transaction is committed. But your code that extracts the data is only pulling data for values that HAVE BEEN committed.
1. A transaction begins at 11:59 AM and performs an INSERT of one (or any number) of records. The value of SYSDATE used is 11:59 AM.
2. The transaction is COMMITTED at 12:03 AM.
3. Your job, which runs every five minutes pulls data for the period 11:55:00 AM to 11:59:59 AM. This job will NOT see the records inserted in step #1 because they had not been committed when your job query began execution - read consistency
4. Your job next pulls data for the period 12:00:00 AM to 12:04:59 AM. This job will also NOT see the records inserted in step #1 because the SYSDATE value used was 11:59 AM which is BEFORE this jobs time range.
You have one or ANY NUMBER of records that ARE NEVER PULLED!
That is why people don't (or shouldn't) use DATE/TIMESTAMP values for pulling data. If you only pull data once per day (e.g. after midnight to get 'yesterdays' data) then the only data you will miss is for data where the transaction began before midnight but the commit happened after midnight. Some environments have no, or very little, activity at that time of night and so may never have a 'missing data' problem.
Creating your tables with ROW DEPENDENCIES will store an SCN at the row level (at a cost of about 6 bytes per row) and you can use the commit SCN to pull data.
Just another caveat though - either of those approaches will still NEVER detect rows that have been deleted. So if you need those you need yet a different approach such as using a materialized view log that captures ALL changes.

All my calendar events moved back one hour after daylight savings

After daylight savings I noticed that all my calendar events are now showing one hour later. With an average of 10 events a day, there is no way to manually correct this- HELP!!!!! I was just one hour late to my first appointment of the day thanks to iCal and it's syncing to my iPhone.

OK, I did this. Then I closed iCal, then I reopened it. All my appts remain one hour late. Perhaps this will prevent this from happening during the next daylight change, I guess I will find out. "Time Zone support" to me implies that the time should be corrected if the computer moves to a new time zone.....
Irregarless. I've still got hundreds of appts showing an hour late, and as I enter more and more each day, it will become more and more confusing as to which ones are set to the correct time, and which ones are one hour late. How can I get all my appoints to show the correct time?????
HELP!

Site synchronization and daylight savings/standard time

The familiar problem of Dreamweaver not accounting for the
change from Daylight Savings to Standard time persists with CS3.
This only shows up on Windows machines. Windows (tested with both
XP and Vista) maintains all file times in UTC, and changes the
locally displayed time based on the time zone. The remote servers
are all Linux boxes running Apache. DW connection is through SFTP.
Dreamweaver appears unable to figure out the local time stamp
offset imposed by Windows. After changing from Daylight Savings to
Standard time, Check In operations produce a message that all
remote files are dated an hour later than the local files. This is
the opposite behavior one sees in the Spring, when the change from
Standard to DST has Dreamweaver believing all remote files are an
hour out of date.
In the past I have manually changed the file modification
times on all files for every site. Given that this comes to several
hundred thousand individual files, it is a pain. Searching yet
again for a method to convince Dreamweaver to correctly interpret
the file timestamps produced little more than Google's listing
thousands of search hits for other folks mentioning the same
problem.
It made no difference which timezone the server was in (or
set to) relative to the PC running Dreamweaver. The timezones could
be identical or different -- DW always complained the remote files
were an hour later than the local ones. I changed timezones on both
the server and the local machine. No help. Neither was rebuilding
the site cache nor manually deleting the WinFileCache*.dat file. I
also tried manually editing a dwsync.xml file in a _notes folder to
see if I could alter DW's view of the world. Again, no such luck.
Making matters far worse, however, Dreamweaver complains
about file time differences in newly modified files as well. A
standard Synchronize command produces "Resolve" errors for every
newly modified file that is not first checked out from the remote
site using DW, saying both local and remote versions have changed
since the last sync. Running "Check In" on a newly modified file
that was not explicitly checked out (e.g. an image or other binary
file) does nothing, as DW sees a timestamp discrepancy. These files
must first be Put to the site, with the corresponding DW error
dialog, and then be checked in.
I am suspecting the problem stems from Dreamweaver's lack of
support for the
MDTM
command. Many other products, ranging from commercial packages
such as WS_FTP and Microsoft's Expression Web, to $30 shareware
programs such as Beyond Compare, to freeware programs including
WinSCP all correctly interpret Windows timestamps as well as
preserving the correct time upon file uploads. Is there any
solution other than changing the timestamps by an hour on every
file or getting every file from all sites to satisfy Dreamweaver's
belief that the files are all an hour newer than they actually are?
The former is a non-trivial task given the sheer number of files to
change; the latter is a bandwidth PITA for ~90GB of data.
Message to Adobe: Please fix this problem. It hits users
connecting Windows local machines to Linux servers twice a year.
Your competitors as well as shareware authors have sorted this
matter out.

Ethan H wrote:
> The familiar problem of Dreamweaver not accounting for
the change from Daylight
> Savings to Standard time persists with CS3.
Yes, it's a bug, and it's a PITA.
> Message to Adobe: Please fix this problem.
Message to Ethan H: This is a user-to-user forum. To get the
message to
the right people in Adobe, submit a bug report:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Yes, I'm sure that Adobe knows about the problem without you
going to
the effort to submit a report, but the bug report/feature
request form
is how the development team assesses its priorities.
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of
ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

Daylight Savings Time and Alarmsk

Since the daylight savings time updated over the weekend the alarms I had programmed on my iPhone will not set properly. The phone displays the correct current time so I know the clock has updated but any alarms I have set for the hour of 2am - 3am don't display the proper time. They keep reverting to 1-2am. I have deleted them and recreated them with the same results, on 2 different iPhones, a 4gig and an 8gig.

I see im not the only one that gets up early. v1.1.3 and updated to 1.1.4 I am unable to set the alarm to any time in 2AM (2:01, 3, 4, 5, etc..) any time set to 2AM shows 1AM in the alarm. 2PM shows fine. Any hour of the day shows fine. The error is setting a time of 2AM as it will not show that time and will revert to 1AM.
I am in a zone that uses DST.
I guess apple doesnt want us to wake up to pay the bills.
I hope someone has a fix for this before I goto bed... busting out the old alarm clock now.

Energy Act of 2005 and Daylight Savings Time

We currently use Sun Studio compilers. We use the embedded tools.h RogueWave libraries. The Energy Act of 2005 changes the dates for Daylight Savings Time starting in 2007. Will there be any patches from Sun to handle this? We currently use RWZoneSimple which is extensible, but we were hoping for an update from Sun.
Thanks in advance. Sorry if this has been covered, I just couldn't find anything.
Further Reading:
http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005

The RW Tools.h++ library that comes with Sun Studio has been updated with the new DST rules. I don't think the patches have been released yet.
If you have a service contract with Sun, you can get a pre-release version of the patch via your support channel.
Otherwise, check the Sun Studio patch page from time to time
http://developers.sun.com/sunstudio/downloads/patches/index.jsp
Look for a C++ compiler patch that includes a fix for bug 6456479.
RW Tools.h++ does its own DST calculations. Other libraries rely on the Solaris functions in libc. Patches for Solaris are available now as follows:
S10 - 118833-24(sparc), 118855-19(x86)
(The fix is included in S10u2.)
S 9 - 112874-34(sparc), 114432-24(x86)
S 8 - 108993-62(sparc), 108994-62(x86)

SimpleDateFormat and Daylight Savings Time

I am trying to parse into a Date "April 15 1999" with "MMM d YYYY" using SimpleDateFormat. This string parses w/out error and the resulting Date is: Thu Apr 15 00:00:00 PST 1999. This is correct in that I am in California. The problem is that 4/15 is Daylight Savings Time in 1999. The getTimeZone result for the parent DateFormat is "SystemV/PST8PDT". I have wrestled with this for over a day now, I admit it, I need help.
Anyone have any ideas what could be happening here?
Thanks
Roger

When I run BigDaddy's code I get MST for the TZ (which is correct, my default is Mountain TZ and we don't observe DST. By this I surmise that BDLH's default is Pacific TZ and that it observes DST. The following code shows the setting of the TZ to "America/Los_Angeles" and produces the correct result. Windows XP.
import java.text.*;
import java.util.*;
public class PTest {
    public static void main(String[] args) throws ParseException {
        SimpleDateFormat sdf = new SimpleDateFormat("MMM dd yyyy");
        Date dte = sdf.parse("April 15 1999");
        System.out.println(dte);
        SimpleDateFormat sdf2 = new SimpleDateFormat("MMM dd yyyy zzzz");
        sdf2.setTimeZone(TimeZone.getTimeZone("America/Los_Angeles"));
        System.out.println(sdf2.format(dte));
}

Australian daylight savings time wrong under Mac OS X 10.7

The 'set date and time automatically' option displays the wrong time under Mac OS X 10.7 in Australia. I use Apple Asia (time.asia.apple.com) and I don't think it accounts for daylight savings time. I know I have the option the set the time manually, so it is not a large problem, However I'm just raising the issue. The time currently in Australia is 5:45pm and my computer running Lion displays 4:45pm. My iPhone running iOS 5 has no issues and displays the right time.

markpb91 wrote:
Coffs Harbour, northern NSW along the coast. So I'm on Sydney AES time.
Beautiful part of the world! I have under Date and Time in System Preference marked as such
Date and Time    South Asia (have set automatically unticked)
Then Time Zone set for Australian Eastern Daylight saving time
                                   Melbourne - Australia    (I'm in Ballarat)
                                   With set time automatically up the top unticked
They are the settings I have always used and my computers have always reverted to and from Daylight savings (except of course I'm in Queensland, Then I have to reset my location and remember to set it back.
Other than that if may come down to trashing your pref file for date and time.
Good Luck

WebLogic and Daylight Savings Error

We are running a Weblogic 7 SP1 cluster on Windows 2000 Server and
when daylight savings arrived, our server dates advanced one day, to
be one day ahead, but the time stayed correct. Has anyone seen this
bizarre event? Haven't found anything in any newsgroup.
Thanks.

When I run BigDaddy's code I get MST for the TZ (which is correct, my default is Mountain TZ and we don't observe DST. By this I surmise that BDLH's default is Pacific TZ and that it observes DST. The following code shows the setting of the TZ to "America/Los_Angeles" and produces the correct result. Windows XP.
import java.text.*;
import java.util.*;
public class PTest {
    public static void main(String[] args) throws ParseException {
        SimpleDateFormat sdf = new SimpleDateFormat("MMM dd yyyy");
        Date dte = sdf.parse("April 15 1999");
        System.out.println(dte);
        SimpleDateFormat sdf2 = new SimpleDateFormat("MMM dd yyyy zzzz");
        sdf2.setTimeZone(TimeZone.getTimeZone("America/Los_Angeles"));
        System.out.println(sdf2.format(dte));
}

Manually recorded series don't "get" daylight savings

Similar Messages

Maybe you are looking for