Leopard Upgrade or Fresh Install???

Hey guys... I hope you all are doing ok!!
My question is... I have a mac pro and I am going to upgrade it to Leopard and was wondering if I should do an upgrade or a fresh install (reformat)??
My concerns:
Upgrading - will some of my applications somehow become corrupted in the upgrade process or will not function 100%??
I would do a fresh install, it's just a hassle to reinstall all my applications, especially final cut.
Im running full adobe master suite, aperture, final cut studio, parallels w/ windows xp pro
Any help would be appreciated!!

Before you embark on your project, get a bootable, external HD, and make a bootable backup/clone before upgrading/updating and ensure that works like the original. That allows you to revert to the previous good state without having to reinstall anything. See these for details:
http://docs.info.apple.com/article.html?artnum=106941
http://www.macmaps.com/upgradefaq.html
http://www.macmaps.com/backup.html
http://www.thexlab.com/faqs/installswupdates.html
http://www.thexlab.com/faqs/backuprecovery.html
WRT the upgrade options, see:
http://discussions.apple.com/thread.jspa?messageID=5757385
http://discussions.apple.com/thread.jspa?messageID=5666369
http://discussions.apple.com/thread.jspa?messageID=5646414

Similar Messages

SQL 2008 R2 In-Place Upgrade or Fresh Install to SQL2104

We have a server running Windows 2008 R2 and SQL 2008 R2 currently. We will call it SQL01. This houses databases for about 8 different applications and also has the name hard coded into a lot, I repeat, a lot of various things.
We are at the point where one of our applications needs to be upgraded and it only works with SQL 2014. So we need to either do an in-place upgrade or fresh install.
The obvious choice to me as a system admin is to do a fresh install, but the development side of the department knows how many places the name "SQL01" is hard coded and they want to do an in-place upgrade to avoid all the issues that would show
up if we changed names.
I have several questions, and I'd appreciate that the answers address them all if possible.
1. What are people's experiences with in-place upgrades from SQL 2008 R2 to SQL 2014?
2. To avoid this naming and coding issue, do companies use a permanent alias for their SQL servers? Like with exchange, we have an alias or A record pointing "mail" to the current Exchange server. As we do upgrades and the Exchange
server names change, the "mail" entry will always be pointed to the current one. Do people do this for SQL as well to avoid our issue of hard coding names?
3. I've head that you can also have both SQL 2008 R2 and SQL 2014 on the same server running together. This really doesn't help though if the SQL 2014 instance would need to be something other than the default which everything is currently pointed
to correct?
4. Is there any advice about a better way to go about this? Or a better way to do this moving forward? Other than not hard coding which I can't change now?
Thanks!

Hello,
Adding to the answers provided above, please consider discontinued features no longer available on SQL Server 2014.
I often see company configuring SQL Server aliases when installing SQL Server on SharePoint environments. You can certainly use DNS or use the following article.
http://msdn.microsoft.com/en-us/library/ms190445.aspx
An in-place upgrade is easier but is difficult to rollback in case something goes wrong. Meanwhile, a side-by-side upgrade provides you more control over what is upgraded, it keeps the legacy server online during the upgrade allowing you to easy rollback if
needed, but is not an automated process and the instance will not keep the same name, requiring you to use aliases or other ways to avoid client redirection.
Since you cannot change the application, go for a side-by-side upgrade and try the DNS alias or the client-side alias as I provided the procedure above.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrade or fresh install??

Got my snow leopard upgrade dvd and wondering if there is any advantage to doing a fresh install as opposed to an upgrade...
obviously making a backup first.

I've done both and didn't notice much difference myself.
I did an upgrade originally and it was fast and everything except flipformac worked like before only faster it felt like.
Way better than any Windows upgrade I've ever done in the past.
Later I did a fresh install to see if there would be any noticeable difference and there wasn't from what I can tell. Fresh install is actually more of a hassle than anything since:
#1 It's alot harder to actually do a clean install of the harddrive with snow leopard compared to leopard since you actually have to manually go up into the menu to select the drive and erase it. In Leopard setup it actually asked you if you wanted to erase your drive during setup.
#2 You have to find your applications disc and reintall iLife, iPhoto,iMovie,etc. since they are not installed with Snow Leopard.
So unless you have a good reason I say don't bother with fresh install and just do the upgrade.
Oh there is only one really good reason I can think of and that is if you are going to use bootcamp and it fails to partition your drive since it's fragmented and you need to erase the drive but even in that case there is software you can use to fix that.
p.s. Remember macos isn't like windows where it uses a registry database to store info every time you install and remove applications so there really is no junk to build up over time in macos. On Windows, a clean install is noticeably faster than an upgrade I find, but on macos it's not like I said.
Message was edited by: daviangel
Message was edited by: daviangel

Help deciding whether to Patch, Upgrade or Fresh Install

Soon we will be upgrading one of the Oracle database targets to 11gR1 (11.1.0.7).
Here is the existing OEM Grid Control configuration:
* RHEL 4 Update 1
* GC 10.2.0.2
* Repository: 10.1.0.5 (single instance)
* Agents 10.2.0.3
* 17 Hosts targets
* 13 Database targets
* 10 User Defined Metrics
To monitor the upgraded 11gR1 target database, I have the following options:
OPTION 1) Patch GC to 10.2.0.5
OPTION 2) Patch GC to 10.2.0.5, then upgrade to 11g (11.1.0.1)
Installing the 10.2.0.5 patch set would require less effort than upgrading to 11g, but let’s suppose the final goal is to upgrade to:
*RHEL 5 Update 2 (on a new virtual server)
*GC 11.1.0.1
*Repository: 11.2.0.1
Knowing we have Option 2, I wonder if there might be third Option. For example:
OPTION 3) Fresh install of OEM 11g Grid Control and manually add targets and UDMs
My question is Option 3 feasible and would it be less effort than Option 2 given the ease with which agents can discover various targets?

Choose Option 3

CS5.5 upgrade or fresh install?

Does anyone know if CS5.5 will be a upgrade version we can install over 5, or will it need to be a fresh install?
thanks

Hello
Can't instal my CS5.5 without errors???
Have now tried to install on my CS5.5 Production Premium twice, and get the same error every time. Had previously installed 5.0.3 without any problems.
I have run the Clean Tool, so there was nothing left of 5.0.3, however, I get errors during installation (installation 2).
I've now reinstalled my OS Windows 7 64 Ultimate but with the same result (installation 3)?
Can't activate my Cuda with 5.5, worked fine in 5.03 thought?
Cant't log in with my Adobe ID under installation but it works fin in my browser thought?
Not fun at all :-(
/Mikael Bergstrom
Sweden
Log file
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 91 error(s), 2 warning(s)
----------- Payload: {CFA46C39-C539-4BE9-9364-495003C714AD} Adobe SwitchBoard 2.0 2.0.0.0 -----------
WARNING: DF029: ARKServiceControl::StartService: Service not started/stopped SwitchBoard. Current State: 0 Exit Code: 0 Service Specific Exit Code: 0(Seq 1)
----------- Payload: {2EE4F060-CEE6-4002-AA8B-91B791541767} Pixel Bender Toolkit 2.6.0.0 -----------
WARNING: DF035: CreateAlias:Icon file does not exist at C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\windows\pb_app.icofile:\\\C:\PIXELB~1\source\winwood\Staging 0X1.5E5AC7P-1020rea\windows\pb_app.ico42178f80493091e8e552c84a2897e9da68fce32_32_f8049309 1e8e552c84a2897e9da68fce for icon C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Production Premium CS5.5\Adobe Pixel Bender Toolkit 2.6.lnk with target C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\Pixel Bender Toolkit.exe(Seq 89)
----------- Payload: {7202D4A7-F7E6-4e7a-B77D-7B1C4E8B5CA6} Adobe Flash Player 10 ActiveX 10.0.0.0 -----------
ERROR: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\user\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\user\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
----------- Payload: {F194231A-13B9-45B9-9699-1B9AC6500263} Adobe Encore CS5.1 Library 5.1.0.0 -----------
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2710)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2726)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2728)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2732)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2736)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2738)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2740)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2742)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2746)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2748)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2752)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2754)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2756)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2770)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2772)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2774)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2776)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2778)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2784)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2794)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2796)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2798)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2800)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2802)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2804)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2814)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2816)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2818)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2820)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2822)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2826)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2836)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2838)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2842)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2844)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2848)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2854)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2858)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2860)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2864)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2866)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2870)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2898)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2900)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2902)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2904)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2906)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2908)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2910)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2912)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2914)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2916)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2918)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2920)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2922)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2924)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2926)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2928)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2938)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2958)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2970)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2972)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2980)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2982)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2992)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2994)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2998)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3054)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3066)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3084)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3094)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3118)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3156)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3158)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3160)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3162)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3164)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3166)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3168)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3172)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3174)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3176)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3184)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3186)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3196)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3198)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 3214)
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Flash Player 10 ActiveX: Install failed
Log file 2
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 91 error(s), 2 warning(s)
----------- Payload: {CFA46C39-C539-4BE9-9364-495003C714AD} Adobe SwitchBoard 2.0 2.0.0.0 -----------
WARNING: DF029: ARKServiceControl::StartService: Service not started/stopped SwitchBoard. Current State: 0 Exit Code: 0 Service Specific Exit Code: 0(Seq 1)
----------- Payload: {2EE4F060-CEE6-4002-AA8B-91B791541767} Pixel Bender Toolkit 2.6.0.0 -----------
WARNING: DF035: CreateAlias:Icon file does not exist at C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\windows\pb_app.icofile:\\\C:\PIXELB~1\source\winwood\Staging 0X1.5E5AC7P-1020rea\windows\pb_app.ico42178f80493091e8e552c84a2897e9da68fce32_32_f8049309 1e8e552c84a2897e9da68fce for icon C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Production Premium CS5.5\Adobe Pixel Bender Toolkit 2.6.lnk with target C:\Program Files (x86)\Adobe\Adobe Utilities - CS5.5\Pixel Bender Toolkit 2.6\Pixel Bender Toolkit.exe(Seq 89)
----------- Payload: {7202D4A7-F7E6-4e7a-B77D-7B1C4E8B5CA6} Adobe Flash Player 10 ActiveX 10.0.0.0 -----------
ERROR: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\user\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
MSI Error message: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\Users\user\AppData\Local\Temp\InstallAX.exe, command: -install activex -msi
----------- Payload: {F194231A-13B9-45B9-9699-1B9AC6500263} Adobe Encore CS5.1 Library 5.1.0.0 -----------
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2710)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2726)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2728)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2732)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2736)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2738)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2740)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2742)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2746)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2748)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2752)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2754)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2756)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2770)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2772)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2774)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2776)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2778)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2784)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2794)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2796)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2798)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2800)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2802)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2804)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2814)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2816)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2818)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2820)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2822)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2826)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2836)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2838)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2842)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2844)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2848)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2854)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2858)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2860)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2864)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2866)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2870)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2898)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2900)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2902)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2904)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2906)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2908)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2910)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2912)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2914)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2916)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2918)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2920)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2922)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2924)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2926)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2928)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2938)
ERROR: DS012: LocalizeFile:Localized string not found for locale 'en_GB'(Seq 2958)

Upgrade or Fresh Install of VC3

I've been using VC 2.5 for a year now. Just got VC3 the other day. Is it better to upgrade or do a fresh install of VC 3? I did perform a fresh install but noticed many media files missing from Ver.3. that I had gotten use to using in 2.5 For example VC3 only showed 6 animated backdrops, where I had access to nearly 30 in VC 2.5. VC 3 also lacked a large number of the audio clips from ver 2.5. (VC 3 actually has a number of other music clips in labelled file folders, but they weren't the same types of music. Would performing an "upgrade" have merged all the media files and made them all available to me or did I fail to load some media file folder somehwere on the new VC 3 disk?

There is additional content available for VC3 that should restore all the backgrounds etc that you aren't seeing. (it was split from the application install to make trial downloads easier for people. 200MB versus 3GB download to try the product)
If you bought the DVD version, the additional content installer is located in a folder called "content" on the DVD. Just run the setup.exe there and you should be fine. (There is also an option during the main installer to install the additional content when you install the application, but if you already installed the app, just run the setup.exe in the "content" folder.)
If you purchased the ESD version, you should be able to download the additional content installer from the same page that you downloaded the app install. It is about a 2.5GB file.

Leopard Upgrade, ILife 09 Install On A PowerPC G4

Hi.
I have a PowerPC G4 1.25 GHz Mac Mini. with 1 GB DDR SDRAM. The internal HD is 40 GB with only 9.5 GB still free. It is up to date, running 10.4.11 currently.
I bought the Mac Box Set (Leopard, iLife 09 and iWork 09). What I am thinking of doing is to do a clean install by erasing and installing Leopard. (This Mac Mini originally came with panther and was upgraded to Tiger. Seemed like a good idea to clear the cruft with an erase and install.)
The specs and user comments suggests that this should work fine. Is there anything I need to know or do before I do the erase and install?
Everything is backed up, so that is taken care of.
After installing Leopard, I would like to install the iLife 09. Will this be okay? Will the iLife 09 install on a PowerPC mac? Looking at the specs, iMovie 09 and Garageband 09 seem to require an intel processor. Does this mean that these two apps will not install on my powerPC Mac Mini from the iLife dvd? Or, will they install but be sort of stripped down, perhaps missing some of their features.
What problems, if any, do you foresee in this? Is there anything that I need to know before starting? Any advice, including a walk through description would be really, really appreciated. Thanks so much.

Woodland Potter wrote:
Oh... but look at the prices for internal Hard Drives! Hmm... could replace the 40 Gig internal with a new, larger one. Wonder if that would that be worth it. What do you think? Is there anything to be aware of in replacing the internal Hard Drive?
Assuming you plan on keeping the "old" Mini around for a while, a new hard drive is not a bad idea. Not only will you get a lot more space for files, you will probably see a noticeable improvement in responsiveness, especially if you get a 7200 rpm model. This is because a newer drive will almost certainly have inherently better performance characteristics than the original (lower average seek time, a larger cache & improved caching algorithms, etc.) and because the same amount of file data can be concentrated into a smaller physical area of the drive, reducing the number of track seeks the drive has to perform. A side benefit is that the new drive may even use less energy that the older, smaller one & thus your Mini will run cooler.
This will not make the old soldier comparable to a newer Mac with a faster architecture, but it is likely to result in noticeably if not dramatically faster boot times & application launches, shorter waits while the "spinning beach ball" is displayed, & quicker switches between running applications -- basically anything that requires reading from or writing to the drive.
Things to be aware of include making sure you get a drive with the right interface: you do not want a Serial ATA interface (often referred to as "SATA") but the older Ultra ATA kind (now often referred to as "PATA," for parallel ATA). Almost any new PATA drive will be either ATA-6 (also called ATA/100) or ATA-7 (also called ATA/133). Either one is a good choice. ATA-7 is potentially faster but the Mini's controller may not support it. If so, it will operate at the fastest ATA level it supports. Avoid ATA-5 (also called ATA/66) because the drive will be older & less apt to have the latest performance improvements.
If possible, get the specs for the original drive & make sure the power requirements for the new one are lower. They probably will be because lower energy consumption has become increasingly important over the last few years, but it never hurts to check.
I assume from the "putty knife" comment that you are familiar with opening the Mini & any reassembly steps necessary to restore its heat sinking ability to factory standards. If not, either learn about them or don't try this mod.
Also remember that you could just add an external drive instead, but if you like DIY projects or the idea of retaining the one-box form factor, this is a viable alternative.

Can't shut down / restart after Leopard upgrade - can't install updates

(While I found a topic with the same subject from last November, which is marked "answered", as far as my machine is concerned, nothing in that thread helps)
Having upgraded to Leopard, I have found that the regular shutdown process never works. I invariably get told that Firefox (or something else) is still running but not only is the "Force Quit" dialog empty, but a "ps aux" command does not list any process related to Firefox in it.
For the last few months, I've been doing shutdown -h now, the only mechanism that would work.
However, there's a new update which has a button to restart, but it WON"T restart. I just get the usual problems as above. If I do a shutdown -r now, I can reboot, but it looks like the software update did not actually happen, as I simply get prompted again to install/restart.
Anyone know how to really solve this problem?

Well, it turns out that I was wrong about the original thread not helping. As a last act of a desperate user, I went to the place in user accounts where the login items are specified and pulled out EVERYTHING except my microsoft keyboard/mouse drivers (don't laugh...the only thing I hate about Macs are their keyboards and mice) and my system is now working perfectly...shuts down properly every time, etc...the updater was able to do its job.
I have absolutely no idea which item caused the problem and I don't care.
It works!

Fresh Install or Upgrade

I currently have Windows 2003, IIS6 and CF7 and CF8
successfully running side by side on my development server. CF7 is
loaded in stand alone mode while CF8 is loaded in multi-server
mode. I have 15 CF8 instances running on that server in a
pre-development environment. Next week I will be switching over our
Development side to CF8 and just connecting it to one of the
instances on that server. As it stands right now, we are not
thinking of running multiple instances in our test and production
environments but I was thinking of installing the multiple server
configuration and with just 1 instance just in case someone changes
their mind down the road.. So,
My question is this: What is the best approach to installing
CF8 in those environments, just upgrading or fresh install? Does an
upgrade remove the previous version? If not, do I have to do a
manual uninstall? I have always done fresh installs on major
version changes as I have not wanted any previous version file
hanging around to cause problems. But upgrading seems the painless
way to go especially when it just ports all of your settings,
datasources and k2 verity collections over.
What is the best practice?

fluxxy1245 wrote:
hi
I recently purchased the latest mountain Lion.
i was wondering what was the best thing to do.
A complete fresh install
or just upgrading from the previous OSX Lion.
I have 3 macs :
- iMac 27" (2009)
- Mac Mini (2010)
- MacBook Pro 13" (2011)
The 3 of them came with with Snow Leopard.
And I did an upgrade to Lion, shortly after it was relased.
If we upgrade :
- does leave unnecessary files
- is there a difference in speed and hard-disk space
or does it manage it all very well
Thanks for the info
maybe some links would be welcome that give an in-depth explanation about that
There is some house-keeping that you need to do before/after upgrading to Mountain Lion.
For installed, third-party applications (and device drivers where indicated), does the vendor offer latest OS X Mountain Lion support. Drivers that worked in Snow Leopard or Lion, may not work well in Mountain Lion without upgrades.
You may have to re-install some third-party applications that have system dependencies that have changed in Mountain Lion.
You may have to update your Printer preferences if printers do not work after the upgrade.
You should count on a minimum of 4GB of memory (8GB is better) in each Mac.
Although the upgrade process will not touch /Users, it is sound due diligence to backup user data on all these Macs beforehand.
Upgrading is simpler, multiple Mountain Lion downloads not withstanding. If these Macs have been through prior OS X updates, they may not operate as fast as a full, clean install would deliver. If you want to do a full, clean install, download the free Lion Diskmaker. It will automatically build a bootable, USB installer for Mountain Lion from your first ML purchase and download. I used it to make a clean install on my SSD. Works perfectly.

AE CS4 Will not open after Snow Leopard Upgrade

Ok, i posted this earlier but I don't think I was clear enough to get an answer. I recently did a clean install of Snow Leopard and a fresh install of my Production Studio CS4. Upon getting it all installed, I realized that After Effects will NOT open at all. It just bounces on the Dock a few times and then stops. Then after that, when you click on it, it bounces once, then stops. Every other program works great, only after effects is not working. Why is this? Is there something I need to do? I reeinstalled just the AE and downloaded the newest update, still, the same thing. I would appreciate any suggestions to get it running.

I experienced this when upgrading to Snow Leopard myself.
After Effects is one of many, many applications which require Rosetta to be installed. In Snow Leopard, Rosetta is an optional install on the disk. So just make sure you install it.
Now, the thing also is that once Rosetta is installed, the OS still seems to have AE flagged as an app which requires a missing component to launch. This was fixed after a couple of restarts, in my case.

DVD SP keeps hanging even after a fresh install

DVD SP keeps hanging on me. When I try and drag anything into a menu background, turn on the simulator or play a track.
I have tried re installing FCP suit 2, also tried un-installing it and installing again, I have even done an erase and install of OSX Leopard and and fresh install of FCP2 and I'm still having this problem.
I really can't think of any thing else I can try. This makes no sense to me at all.
Is anyone else having this problem with FCP2 and Leopard?

Does it just hang permanently or does it beachball for 3 or 4 seconds and then come back?
Also, what type of footage are you working with?

Should I upgrade my iphoto panther to Leopard or export and fresh install?

My Panther iphoto library got corrupted some how and I had to create a new library. I did not like this because it changed all the order of my photos and I could not organize them the way they were. I still have the corrupted library on my hard drive. I never deleted it for fear that I did not get all of my photos onto the new library. I think I pretty much did but not for sure. The dates that I imported the original library pics were all correct. Now that I had to redo the library half the dates are wrong because it's going by the created dates on the photos instead of the day they were imported. It's all very confusing to me.
Anyway.....now, I just purchased a copy of Leopard. I was thinking of doing a fresh install instead of upgrading my g4 in hopes that I would start with a clean slate. Only problem is trying to back up all those photos and then reimporting them. Do you guys think I should not mess with it or buy a firewire external hard drive, export or back up my files, do a fresh install and then re-import? One of the reasons I also want to start fresh is because my daughter went in and started deleting a bunch of folders she did not think she needed and I had to get thousands of files out of the trash. I don't know if I put everything back into the correct place. Come to think of it. My itunes library was corrupted as well and I had to create another one of those. So I have 4 libraries of music and photos filling up my 120 gig hard drive. Sounds like a good time for a fresh install upgrade right???
Tim

Anyway.....now, I just purchased a copy of Leopard.
iPhoto '08 is not included on the Leopard upgrade - it is on the iLife '08 upgrade (a separate purchase from the OS)
And upgrading the software will not fix a corrupted library - you need to have a good clean working library before you upgrade iPhoto
LN

Preparing for Snow Leopard - fresh install or upgrade?

I have two Mac's at home currently running 10.5.8 that I will be upgrading to Snow Leopard. My question is, do I need to do a fresh install or upgrade over the existing OS and is there a preferred approach?
Mac 1: Macbook Pro (late 2007)
Key Applications in use:
- VM Ware Fusion
- Bootcamp (Vista)
- Logic Express 8
- MS Office 2008
Mac 2: Mac Mini (2009)
Key applications in use:
- Plex
- MacTheRipper
Thanks in advance!
Message was edited by: mapexvenus

Since no one yet has SL to determine what options are available you will have to wait until Friday.
But in the most general terms a fresh install is always preferable. You can prepare by doing the following:
1. Repair your hard drive and permissions.
2. Make and test a bootable clone to another internal or external drive.
Because you have two Macs you will need to purchase the Family Pack. You cannot install a single-user license on more than one CPU at a time.

2007 iMac freezes up, rainbow wheel appears when this happens. I know the computer is starting to get old but I can't afford a new one at this time and would love to continue using my Mac, but it's frustrating. Would a fresh install or OS upgrade resolve?

My circa 2007 iMac freezes up, and rainbow wheel appears when this happens. I know the computer is starting to get old but I can't afford a new one at this time and would love to continue using my Mac, but it's frustrating. Most of the time I ONLY have 1 thing open at a time, and keep my tabs down to a minimum. I bought this to do film editing on but with it acting like this I cannot do that. I know I need a ram upgrade (currently running 2 gb) and my OS is old, 10.5.8, but I think even with it being a bit outdated it should run better than this. Would a fresh install or OS upgrade resolve this? Or any other suggestions to keep this clunker chugging along for a little while longer?

How full is the hard drive?
Do you run any virus software or hard drive "cleaner" software like MacKeeper?
If your model is from 2007 you can install up to 6 GBs of RAM.
2 GBs is the barest of minimum RAM for OS X to run on.
Especially if doing video work. You simply do not have sufficient RAM.
Also OS X 10.5.8 Leopard support ended around 2009.
You could update to OS X 10.6 Snow Leopard, at least.
It is available on disc from the Apple store for U.S. $19.99.
I Would seriously upgrade your iMac's RAM to the max. 6 GBs before doing this.
Reliable Mac RAM can be purchase from online Mac RAM source Crucial memory or OWC ( also known as macsales).

Will time machine HD be picked up on a fresh install on snow leopard?

Hi guys i am going to do a fresh install on my machine. I recently upgraded OS's from leopard using the upgrade install that just wrote over my existing setup. I didnt want to restore from my time machine but just wanted to drag files from my time machine HD manually after the fresh install but im concerned that the HD wont be picked up by the new system.
I just wanted to make sure that my old time machine backup and all files will be seen by the fresh install so i dont loose any data.
Has anybody done this before?
thanks Jamie

jamie8286 wrote:
Hi guys i am going to do a fresh install on my machine. I recently upgraded OS's from leopard using the upgrade install that just wrote over my existing setup. I didnt want to restore from my time machine but just wanted to drag files from my time machine HD manually after the fresh install but im concerned that the HD wont be picked up by the new system.
Time Machine puts special "deny everybody everything" permissions on it's backups, and if you copy them via the Finder you may have all sorts of locked file and/or permissions issues with them, especially if you have multiple users. Not to mention the problem of getting everything you need. Complex applications that came with their own installers, for example, will probably have to be re-installed (and any license/purchase keys re-entered).
If you want a fresh copy of OSX, just do the install again. If you want to get rid of old stuff in your user folder, you're probably much better off just deleting what you don't want.
Or erase your disk, install OSX, then use +Setup Assistant+ to transfer the data you want from your backups. See #19 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
I just wanted to make sure that my old time machine backup and all files will be seen by the fresh install so i dont loose any data.
If you replace all the data on your internal HD, your next Time Machine backup will be a full one -- everything on the internal HD will be backed-up again. So it may have to delete a lot of old backups to make room for the new one.
If your TM disk isn't well over the size of the data currently on your HD plus 120% of the data you put back on it, there won't be room for a new full backup. You'll have to erase the disk and let TM start over.
Either way, TM will, sooner or later, delete it's copies of anything you don't put back.

Leopard Upgrade or Fresh Install???

Similar Messages

Maybe you are looking for