The Following User Says Thank You to urilabob For This Useful Post: | ||
![]() |
2007-09-08
, 13:04
|
Posts: 82 |
Thanked: 1 time |
Joined on Apr 2006
|
#2
|
![]() |
2007-09-08
, 15:49
|
Posts: 32 |
Thanked: 2 times |
Joined on Jul 2007
|
#3
|
![]() |
2008-01-27
, 15:52
|
Posts: 21 |
Thanked: 0 times |
Joined on Jan 2008
|
#4
|
![]() |
2008-01-27
, 18:01
|
|
Posts: 239 |
Thanked: 53 times |
Joined on Jan 2008
@ Massachusetts
|
#5
|
![]() |
2008-01-28
, 04:37
|
Posts: 16 |
Thanked: 2 times |
Joined on Dec 2007
|
#6
|
![]() |
2008-04-07
, 04:19
|
Posts: 13 |
Thanked: 1 time |
Joined on Mar 2008
@ USA
|
#7
|
![]() |
2008-04-07
, 16:43
|
Posts: 155 |
Thanked: 69 times |
Joined on Apr 2008
|
#8
|
![]() |
2008-08-24
, 15:41
|
Posts: 32 |
Thanked: 2 times |
Joined on Jul 2007
|
#9
|
![]() |
2010-06-06
, 21:27
|
|
Posts: 99 |
Thanked: 64 times |
Joined on Jun 2009
@ Stuttgart/Germany
|
#10
|
Obviously I've checked it carefully afterward, the alarm setting looks correct. Tried various experiments, setting dummy alarms and testing them. So far, they all seem to work correctly. I also checked that the system time is the same as that being shown in calendar, so it seems to be a problem of the alarm computing the wrong time, rather than the time being set wrong in calendar. Has anyone else seen anything similar (or know of pointers to similar threads)?