[rivviepop]

I won't go into the hell I encountered doing a DST upgrade to a SnapServer 4500 - but for you unix/linux nerds all I can say is "MY /etc/fstab IS ZERO BYTES?!" after an upgrade. You infer the rest, I had a heart attack.

This weekend it was my stupid calendar! Somehow I had not one, not two, but three different events listed for all the DST change days on my Pearl. I keep the Sharks hockey schedule, so imagine 3 events "Sharks vs. Ducks" at 6:30p, 7:30p, and 8:30p. I have no ****ing clue how, but there they were.

I logged into Mobical, and for the same days two events were there! Not three, not one, but two. Another "how the..." moment during the new DST month of March. So I sat here on my Pearl and fixed the days (only a handful, maybe 10-15 game days) so that I had the right times. They I tried a new SyncML (SyncJe client). Nope, all the extra events were still there for March. *sigh*

So then I did a complete slow-sync from the SyncJe client (this basically pushes everything again from scratch) and.... well, my extra events are gone! You'd think "yay!", right?

Nope. Now all the events in my Mobical are Sweden offsets (or GMT or something). Motherf***er. My handset is now right, but Mobical has everything listed at like 3am or whatnot.

I give up. I hate technology.

[mark0341]

Wirelessly posted (BLACKBERRY 8703e (ALLTEL): BlackBerry8703e/4.1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/106)

I feel your pain.

[rivviepop]

Did I mention my (not cheap) analog watch still thinks it's the 1st of March thanks to 28 days in February? It's only been what, 2000+ years since Romulus, Julius Caesar and whatever other Romans were involved that saddled us with this screwup calendar, can't we have fixed this problem by now in watches?

rant rant rant.

[LunkHead]

Same here rivviepop.... My Mobical is all messed up as well...

[LunkHead]

Originally Posted by rivviepop

Did I mention my (not cheap) analog watch still thinks it's the 1st of March thanks to 28 days in February? It's only been what, 2000+ years since Romulus, Julius Caesar and whatever other Romans were involved that saddled us with this screwup calendar, can't we have fixed this problem by now in watches?

rant rant rant.

That was funny!!!!!

[JSanders]

Originally Posted by rivviepop

Did I mention my (not cheap) analog watch still thinks it's the 1st of March thanks to 28 days in February? It's only been what, 2000+ years since Romulus, Julius Caesar and whatever other Romans were involved that saddled us with this screwup calendar, can't we have fixed this problem by now in watches?

rant rant rant.

haha, yea, I actually caught myself last Friday writing a check and glancing at my watch and almost dated the check for February 30, until my brain slipped in gear.

[blakeatl]

Originally Posted by JSanders

haha, yea, I actually caught myself last Friday writing a check and glancing at my watch and almost dated the check for February 30, until my brain slipped in gear.

Wow! That would have been a doosie! I wonder when the company would be able to cash that one?

[*&))]

my treo had me going to appointments on the 29 this year, but it has me going place i have no business on a regular

[rivviepop]

Holy crudsicles, I just fixed it. Completely accidentally.

I upgraded today from the .64 to .71 Pearl OS to fix a very specific bug that Idokorro support found in .64 (vi over SSH oriented). The old DST patch that was installed got wonky then was removed when I ran the apploader, as expected; I regrabbed it OTA, the old one was 1.5 and new was 2.3 so *something* was fixed by RIM.

During the upgrade my SyncJe settings got lost (random, eh?), so I rekeyed my reg info and the server setup, then hit Sync just to be sure it was working. I logged into Mobical, and voila -- my entire calendar was back on track.

I'm back in the game. I love technology.

[jetspeedz]

what an unnecessary burdon on everyone, especially on the IT folks around the world

[Chinasaur]

We spent an entire month testing OS image, Oracle and JRE and JVM variations simply because of the switch from JVM 1.4.2_10 to 1.4.2_13 and JRE 5 Update 5 to Update 10.

Wasted time we didn't have.

Thanks Washington

[kathrynhr]

I still think we should just split the difference - spring forward 30 minutes this spring and stay there permanently - instead of all this parading back and forth nonsense.

[LunkHead]

Originally Posted by rivviepop

Holy crudsicles, I just fixed it. Completely accidentally.

I upgraded today from the .64 to .71 Pearl OS to fix a very specific bug that Idokorro support found in .64 (vi over SSH oriented). The old DST patch that was installed got wonky then was removed when I ran the apploader, as expected; I regrabbed it OTA, the old one was 1.5 and new was 2.3 so *something* was fixed by RIM.

During the upgrade my SyncJe settings got lost (random, eh?), so I rekeyed my reg info and the server setup, then hit Sync just to be sure it was working. I logged into Mobical, and voila -- my entire calendar was back on track.

I'm back in the game. I love technology.

Sweet! I will giver er a whirl! Thanks again!

[LunkHead]

I upgraded to the new SyncJe client... Had to delete all calender info off the device and delete all calendar info off the Mobical site... Entered everything again and all is good now.... What a pain!

[CaptSwerve]

so my phone jumped ahead an hour last night (i use it as my alarm clock).. i ended going to class at 8 instead of 9..

[cliffr39]

Originally Posted by mr_smith

so my phone jumped ahead an hour last night (i use it as my alarm clock).. i ended going to class at 8 instead of 9..

that sucks but better early than late

Originally Posted by kathrynhr

I still think we should just split the difference - spring forward 30 minutes this spring and stay there permanently - instead of all this parading back and forth nonsense.

I completely agree and been thinking this way for years! It never made sense to me why we do it but some other US states don't and then other places are off by 30 minutes and stay that way all year.