MobileMe Fails to Launch Well, But Finally Launches

On 7/14/08 1:08 AM, "Mark Issacs" <markimac.com> wrote:

> Watch the next week and see who in the exec suite is suddenly looking
> for employment elsewhere!

Nobody - Apple doesn't fire execs for "minor" issues like this.

Let's keep it in perspective - Apple/AT&T had a decision to make: Spend
untold millions upgrading servers (and more) for a one day rush or ride out
the storm and everything will be just ducky come Monday.

For better or worse (for their customers, anyways), they chose the latter.

Nobody at Apple or AT&T will be fired over what happened this weekend.
--
Shawn King

On Jul 14, 2008, at 11:31 AM, Shawn King wrote:

> Let's keep it in perspective - Apple/AT&T had a decision to make:
> Spend
> untold millions upgrading servers (and more) for a one day rush or
> ride out
> the storm and everything will be just ducky come Monday.

Apple had another choice it could have made--officially releasing 2.0
a day or two before the 3G. it was obviously ready and already out
there.

i also don't understand why they didn't just stop the 2.0 download
servers for a while when the activation servers were choking. allowing
people to download and install updates that rendered phones inactive
until the servers could catch up was another bad decision.

i agree that this is not really a fireable offense but for a company
that takes pride in a great user experience it was a miserable failure.

On Jul 14, 2008, at 8:31 AM, Shawn King wrote:

> On 7/14/08 1:08 AM, "Mark Issacs" <markimac.com> wrote:
>
>> Watch the next week and see who in the exec suite is suddenly looking
>> for employment elsewhere!
>
> Nobody - Apple doesn't fire execs for "minor" issues like this.
>
> Let's keep it in perspective - Apple/AT&T had a decision to make:
> Spend
> untold millions upgrading servers (and more) for a one day rush or
> ride out
> the storm and everything will be just ducky come Monday.
>
> For better or worse (for their customers, anyways), they chose the
> latter.
>
> Nobody at Apple or AT&T will be fired over what happened this weekend.

However, I suspect that the other part of the problem (Apple's long
outage of .mac/MobileMe service during the transition) could result in
one or more employment changes. The short planned outage lasted far
too long, and *somebody* undoubtedly told Mr Jobs something like
"We're ready for this conversion to MobileMe". Jobs: "Are you
sure?" Same somebody: "yes".

The early Friday activation problems were as much the customers as the
infrastructure: aside from a few score journalists (and only those
without loaners from Apple) and bloggers, who *needed* a phone the
moment it was released? No one.

Even had I been planning to upgrade (I'm not--no 3G here), I would
have waited a couple of weeks.

   --John

I'm running 10.4.11 and am not getting an option to download the MobileMe preference pane when I open the .Mac pane. Anyone else see this? Maybe it's because my .Mac/MobileMe account renews in 97 days.

Still stuttering: published iWeb-sites have no comment, no google maps

Willi

I tried the “trick” noted, but I still operate in 10.4.something.  No prompt came along.  Instead, I got a message saying that connection was not allowed at all.  I will try later, but wonder if this is a Tiger only workaround and have not a clue as to what to do with nothing from downloads or otherwise....

LW

On Jul 15, 2008, at 12:08 AM, TidBITS Editors wrote:

After you apply it, simply close System Preferences and open it again to find the MobileMe preference pane in place of .Mac; you don't need to restart the Mac.

After I upgraded, my system.log was filled with

Jul 13 16:53:35 G5 kextd[14839]: in-memory mkext doesn't match on-disk mkext; non-boot kexts won't be loaded

repeated every 30 seconds. So you probably should restart your Mac after the upgrade. I restarted both my G5 and my PBG4 after upgrading them.

Am I just imagining things, or are RSS feed:// URL's now being synchronized? I've always wanted that, and it seems that it is happening. I usually use Safari on my G5, and my Powerbook used to just accumulate RSS entries, which I bulk cleared every once in a while. Now they're more or less the same.

The one thing that'll take getting used to is my iPod Touch beeping every time I get new email in my .Mac, err, MobileMe account. I wonder how that will affect the battery life? I haven't yet tried to read mail away from a network to see if that annoying inability to read a lot of plain text messages has been fixed (does "push" really mean "push the entire message"), or whether Mail is still for the iPhone rather than the iPod Touch.

The one thing I didn't see at the App store was any kind of ssh terminal client. I'd like to have one for those rare times that I really need to get something done using the command line and I'm away from home.

On Jul 15, 2008, at 5:21 AM, Willi Bauer wrote:

> Still stuttering: published iWeb-sites have no comment, no google maps

As of Tuesday morning, the stack effect for photo albums is broken and
photo slideshows do not display in iWeb sites.

Alan Forkosh Oakland, CA
aforkoshmac.com

Several readers noted that our article yesterday failed to mention that the MobileMe software update appears only when you're running Leopard. Sorry for any confusion! Apple hasn't explained at all what will happen (and when) to Tiger and users of older Mac OS releases that rely on .Mac sync. I have a query into them to find an answer. We also updated our article online to clear this up.

Ditto the problem of going to the dot Mac pane in Systems Preferences and not having any option to upgrade. I'm running system 10.4.11.

On 15-Jul-2008, at 11:06, Paul Schinder wrote:
> The one thing I didn't see at the App store was any kind of ssh
> terminal client. I'd like to have one for those rare times that I
> really need to get something done using the command line and I'm
> away from home.

Agreed. That is the one thing that I am waiting on before getting my
iTouch.

Well, and some spare cash.

One thing I need to contribute to the .Mac to MobileMe pref upgrade is
that it took until Sunday night before I could get the upgrade prompt.
Periodically I tried opening the preferences (and checking Update
before I found out that that wouldn't work) with out much luck. Sunday
night I tried again, but this time I switched away to another app.
When I came back I had the prompt to update. Now I don't know if
Apple's servers where overloaded, if they were rolling the update out
in batches or just waiting a bit on that pref pane was what did the
trick. For those with 10.5 it might be something to try.

One other thing, even after updating it took until this morning (well
maybe late last night) for the iDisk settings to show 20GB.

--
Michael

On Jul 15, 2008, at 10:06 AM, Alan Forkosh wrote:

>
> As of Tuesday morning, the stack effect for photo albums is broken and
> photo slideshows do not display in iWeb sites.

The stack effect and slideshows on iWeb managed sites now work.

Alan Forkosh Oakland, CA
aforkoshmac.com

>> As of Tuesday morning, the stack effect for photo albums is broken
>> and
>> photo slideshows do not display in iWeb sites.
>
> The stack effect and slideshows on iWeb managed sites now work.

I still don't know what the 'stack effect' is, but the slideshow has
always worked for me, as I was updating a vacation album immediately
after the changeover.

Mobile Me is supposed to work G4 computers with 10.4.11 as .Mac. So
far, we can't get it to work on my wife's computer, and it has wiped
out the contacts and calendar on her iPhone. It has also backed up the
no-contact version of her phone.

John

> Mobile Me is supposed to work G4 computers with 10.4.11 as .Mac. So > far, we can't get it to work on my wife's computer, and it has wiped > out the contacts and calendar on her iPhone. It has also backed up the > no-contact version of her phone. > > I'm not using an iPhone, but I had the problem with the .Mac connection to MobileMe not working on my 10.4.11 G4 machine. The solution, from an earlier message I sent: > > Specifically, quit System Preference and then go into ~/Library/Preferences > and delete the file: > > com.apple.DotMacSync.plist > > then go back into the .Mac control panel and you should be able to configure synchronization again. Thanks. Do others confirm this? My wife's going to be very unhappy if I make a new problem. John