Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #49112 > unrolled thread

What broke during Setup Assistant (new iMac)

Back to article view | Back to comp.sys.mac.system

Contents

  What broke during Setup Assistant (new iMac) Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-09-28 08:25 -0400
    Re: What broke during Setup Assistant (new iMac) Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-09-28 10:54 -0400
    Re: What broke during Setup Assistant (new iMac) me@home.spamsucks.ca (Király) - 2013-09-28 15:05 +0000
      Re: What broke during Setup Assistant (new iMac) Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-09-28 11:09 -0400
        Re: What broke during Setup Assistant (new iMac) Your Name <YourName@YourISP.com> - 2013-09-29 09:45 +1200
          Re: What broke during Setup Assistant (new iMac) Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-09-28 18:06 -0400
            Re: What broke during Setup Assistant (new iMac) Your Name <YourName@YourISP.com> - 2013-09-29 11:31 +1200
          Re: What broke during Setup Assistant (new iMac) nospam <nospam@nospam.invalid> - 2013-09-28 21:00 -0400
    Re: What broke during Setup Assistant (new iMac) / last fix Alan Browne <alan.browne@FreelunchVideotron.ca> - 2013-09-28 13:31 -0400

#49112 — What broke during Setup Assistant (new iMac)

So it got here.  In the end I ran Setup Assistant - and wish I had used 
Migration instead.  It took a little over 5 hours.  Had I belayed the 
documents until after the "Setup", it would have been far less and I 
could have transferred at leisure afterwards.

("it" is a late 2012 iMac, i7 (3.4GHz), 1 TB/fusion, with 2 GB graphics 
(680).  "it" will be getting an additional 16 GB of RAM next week).

What broke:

Adobe Photosshop Deactivation.

It needed to be done with admin privileges, so logged in as admin. 
Still would not deactivate.  Even logged in as root.  Re-booted, 
re-this'd and re-that'd.  No result.  Checked via Google and found a 
couple things to try, etc. and so.  E-mailed a support guy (who's e-mail 
was on the support blog) and he replied pretty quick:

QUOTE   We are sorry but the interfaces used by cs5 version of our
    products to check for admin permissions has been deprecated and
    replaced with other ones by Apple in later releases. This is causing
    this issue.

    For now I would recommend you to use same serial number on new
    machine and contact adobe support to help you out with activation
    issue if you face on new machine..
ENDQUOTE

BUT Adobe Support page also has a "Chat" with support.  So I gave it a 
whirl.  Within 1 minute I had a fellow on the other end.  Described the 
issue.  He asked for the license and my e-mail and immediately RESET my 
install counts to 0 and told me to simply Uninstall CS3-PS.  (I still 
haven't installed on the new Mac, but shouldn't be an issue).

It would appear that the response to what is broken described by the 
first guy is to verify, reset and then tell people to unistall.

(Also note: I phoned Adobe Support as well - activation is automated and 
they don't do activation debugging over the phone anymore).

Not nearly the Adobe nightmare I expected (although the episode did cost 
me nearly an hour).

DiVX - something broke resulting in a startup error.  In the end I 
unistalled DiVX (per a blog somewhere).  Need to re-install that at some 
point when a video doesn't play, I suppose.

Something else broke (don't recall the name of it).  Deleted some /tmp 
files per a blog somewhere - seems to have solved it.

Another thing broke (don't recall the name now)  but I can't delete the 
folder (per a blog instruction) - doesn't recognize my sudo password - 
so I have to set that correctly (or is it now my admin password?). 
We'll see if it's still broken on next startup.

MS Office 2008 transferred fine - minor worry - it uses PPC based 
installers.  Can still be installed w/o those installers, but it's one 
less thing to worry about.

Still need to install PS and Fusion.  But generally everything has gone 
well to this point.  No more CD/DVD drive but have a cheap USB one that 
should do the trick.

On startup sometimes the mouse doesn't connect for a long time - this 
morning the iMac was frozen on wake from sleep.  Hit the back button 
once - it "slept" (or something) then came back with the mouse working. 
Bizarre - stay tuned.

OS was at 10.8.3 on arrival - now at 10.8.5.

Thanks to Mezei, Empson, Lewis, Your Name, nospam and others who replied 
to the other thread.

-- 
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible
to pick up a piece of shit by the clean end."
                                                  -Unknown

[toc] | [next] | [standalone]

#49115

On 2013.09.28 08:25 , Alan Browne wrote:

oops

> BUT Adobe Support page also has a "Chat" with support.  So I gave it a
> whirl.  Within 1 minute I had a fellow on the other end.  Described the
> issue.  He asked for the license and my e-mail and immediately RESET my
> install counts to 0 and told me to simply Uninstall CS3-PS.  (I still
                                                       CS5-PS

> haven't installed on the new Mac, but shouldn't be an issue).

And now it's installed and working fine.  Just remains to do an update 
to sort out the Bridge/DNG converter issue.  That can wait until the 
next photo import.

-- 
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible
to pick up a piece of shit by the clean end."
                                                  -Unknown

[toc] | [prev] | [next] | [standalone]

#49117

Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> 
> So it got here.  In the end I ran Setup Assistant - and wish I had used 
> Migration instead.

I really don't think so. Had you opted for Migration Assistant, you 
would have had an identical list of issues that you reported here, and 
then a whole bunch of other ones on top of that. Be glad you did what 
you did.

-- 
K.

Lang may your lum reek.

[toc] | [prev] | [next] | [standalone]

#49118

On 2013.09.28 11:05 , Király wrote:
> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>
>> So it got here.  In the end I ran Setup Assistant - and wish I had used
>> Migration instead.
>
> I really don't think so. Had you opted for Migration Assistant, you
> would have had an identical list of issues that you reported here, and
> then a whole bunch of other ones on top of that. Be glad you did what
> you did.

I disagree.

Yes, the issues I had I would have had, but the file copy would not have 
brought any issues (the Empson replies regarding UID refer).

-- 
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible
to pick up a piece of shit by the clean end."
                                                  -Unknown

[toc] | [prev] | [next] | [standalone]

#49122

In article <xsqdnZZmyZ6-bNvPnZ2dnUVZ_uSdnZ2d@giganews.com>, Alan Browne
<alan.browne@FreelunchVideotron.ca> wrote:

> On 2013.09.28 11:05 , Király wrote:
> > Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> >>
> >> So it got here.  In the end I ran Setup Assistant - and wish I had used
> >> Migration instead.
> >
> > I really don't think so. Had you opted for Migration Assistant, you
> > would have had an identical list of issues that you reported here, and
> > then a whole bunch of other ones on top of that. Be glad you did what
> > you did.
> 
> I disagree.
> 
> Yes, the issues I had I would have had, but the file copy would not have 
> brought any issues (the Empson replies regarding UID refer).

Personally I never use either when setting up a new computer. It's far
easier and safer to simply copy the user's own documents manually and
reinstall the applications from the original installer. That way you
also avoid copying across corrupted files, garbage files, etc.

[toc] | [prev] | [next] | [standalone]

#49124

On 2013.09.28 17:45 , Your Name wrote:
> In article <xsqdnZZmyZ6-bNvPnZ2dnUVZ_uSdnZ2d@giganews.com>, Alan Browne
> <alan.browne@FreelunchVideotron.ca> wrote:
>
>> On 2013.09.28 11:05 , Király wrote:
>>> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>>>
>>>> So it got here.  In the end I ran Setup Assistant - and wish I had used
>>>> Migration instead.
>>>
>>> I really don't think so. Had you opted for Migration Assistant, you
>>> would have had an identical list of issues that you reported here, and
>>> then a whole bunch of other ones on top of that. Be glad you did what
>>> you did.
>>
>> I disagree.
>>
>> Yes, the issues I had I would have had, but the file copy would not have
>> brought any issues (the Empson replies regarding UID refer).
>
> Personally I never use either when setting up a new computer. It's far
> easier and safer to simply copy the user's own documents manually and
> reinstall the applications from the original installer. That way you
> also avoid copying across corrupted files, garbage files, etc.

I used to agree with that, but I'd now say that most will work fine and 
whatever breaks can be fixed easily enough.  The only post transfer app 
issue I had was Thunderbird not logging in properly to one password 
access account.  That took all of 30 seconds to fix.  Oh, and the 
transferred sys-monitor app that didn't work (other post) and that was 
just an issue of deleting it - hadn't used it in years.


-- 
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible
to pick up a piece of shit by the clean end."
                                                  -Unknown

[toc] | [prev] | [next] | [standalone]

#49126

In article <25CdnXIOmaZ9z9rPnZ2dnUVZ_hCdnZ2d@giganews.com>, Alan Browne
<alan.browne@FreelunchVideotron.ca> wrote:
> On 2013.09.28 17:45 , Your Name wrote:
> > In article <xsqdnZZmyZ6-bNvPnZ2dnUVZ_uSdnZ2d@giganews.com>, Alan Browne
> > <alan.browne@FreelunchVideotron.ca> wrote:
> >> On 2013.09.28 11:05 , Király wrote:
> >>> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> >>>>
> >>>> So it got here.  In the end I ran Setup Assistant - and wish I had used
> >>>> Migration instead.
> >>>
> >>> I really don't think so. Had you opted for Migration Assistant, you
> >>> would have had an identical list of issues that you reported here, and
> >>> then a whole bunch of other ones on top of that. Be glad you did what
> >>> you did.
> >>
> >> I disagree.
> >>
> >> Yes, the issues I had I would have had, but the file copy would not have
> >> brought any issues (the Empson replies regarding UID refer).
> >
> > Personally I never use either when setting up a new computer. It's far
> > easier and safer to simply copy the user's own documents manually and
> > reinstall the applications from the original installer. That way you
> > also avoid copying across corrupted files, garbage files, etc.
> 
> I used to agree with that, but I'd now say that most will work fine and 
> whatever breaks can be fixed easily enough.  The only post transfer app 
> issue I had was Thunderbird not logging in properly to one password 
> access account.  That took all of 30 seconds to fix.  Oh, and the 
> transferred sys-monitor app that didn't work (other post) and that was 
> just an issue of deleting it - hadn't used it in years.

If you have the space and are keeping both computers (at least for a
while), then it's often better to not copy anything at all. Just set-up
the new computer totally fresh and then copy across your own documents
from the old computer as and when you need them. Anything left on the
old computer after (for example) six months is probably never going to
be used again anyway.

The other option is to clone the hard drive of the old computer to an
external drive (or remove the computer's hard drive and put it in an
external case), and then use the above "copy as needed" approach.

[toc] | [prev] | [next] | [standalone]

#49130

In article <290920130945111526%YourName@YourISP.com>, Your Name
<YourName@YourISP.com> wrote:

> Personally I never use either when setting up a new computer.

since when do you set up a new computer??

you keep bragging how you are still using a 15 year old computer
running 10.2.

> It's far
> easier and safer to simply copy the user's own documents manually and
> reinstall the applications from the original installer. That way you
> also avoid copying across corrupted files, garbage files, etc.

there's a shitload more to copy than just the documents, including all
the installed apps, their preference files and support files (which can
be in a variety of places), network settings, keychain and more. 

migration makes it *much* easier.

[toc] | [prev] | [next] | [standalone]

#49119 — Re: What broke during Setup Assistant (new iMac) / last fix

On 2013.09.28 08:25 , Alan Browne wrote:


> Another thing broke (don't recall the name now)  but I can't delete the
> folder (per a blog instruction) - doesn't recognize my sudo password -
> so I have to set that correctly (or is it now my admin password?). We'll
> see if it's still broken on next startup.

It was this: "“/Library/StartupItems/BRESINKx86Monitoring” has not been 
started because it does not have the proper security settings."

I followed the advice on an Apple forum:
https://discussions.apple.com/thread/3459792?start=0&tstart=0

System now boots w/o issues.

-- 
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible
to pick up a piece of shit by the clean end."
                                                  -Unknown

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web