Roy Miller

Q: HowTo revert new MacBook Pro, Mac Pro or iMac to Snow Leopard

Hi all,

 

the following instructions were provided to me by our Apple Enterprise tech, and I've successfully performed these steps on a newly purchased MacBook Pro.

 

Please note the following - as of 15 Aug 2011:

- this technique will work on new MacBook Pro, Mac Pro or iMac computers UNTIL Apple modifies the hardware in these computers

- this technique will NEVER work on currently shipping MacBook Air or Mac Mini computers

- this configuration of Snow Leopard installed on a computer that shipped with Lion is not supported by Apple Support.  It is entirely possible that after a trip for an AppleCare support incident, or the Apple Genius Bar, that the computer will return with Lion installed.

 

with these caveats, here are the step-by-step instructions:


---------------------------------------------------------------------

 

HowTo - NetRestore - Install Mac OS X 10.6.8 on new Mac delivered with Mac OS X 10.7.0

 

    note:  this only applies to Macbook Pro, Mac Pro, and iMac computers that originally shipped with Mac OS X 10.6.x. 

               Current Macbook Air and Mac Mini computers cannot be downgraded.

 

Required resources:

    - another computer, running Mac OS X 10.6.8

    - spare external disk

    - Snow Leopard installation disc  (Mac OS X 10.6.0 or 10.6.3 Box Set)

    - Snow Leopard 10.6.8 Combo image file  (download from Apple Support Downloads page)

    - System Image Utility 10.6.8  (download Mac OS X 10.6.8 Update Combo v1.1.dmg from Apple Support Downloads page)

 

 

Procedure:

 

A. Create the NetImage:

1) mount the base source image  (Mac OS X 10.6.3.dmg - created from Box Set Installer)

2) launch System Image Utility  (from Server Admin Tools)

3) when source (from mounted image) appears in SIU screen, click Custom button

4) drag "Customize Package Selection" from Automator Library window to location

        between existing "Define Image Source" and "Create Image"

5) drag "Add Packages and Post-Install Scripts" from Automator Library to location

        between "Customize Package Selection" and "Create Image"

6) in the "Customize Package Selection" section:

    a) expand the "Mac OS X" triangle

    b) select options desired

    c) collapse the "Mac OS X" triangle

7) mount the appropriate update image  (Mac OS X 10.6.8 v1.1 Combo.dmg)

8) copy the MacOSXUpdCombo10.6.8.pkg package to a new local directory  (Desktop/parts/)

9) drag the MacOSXUpdCombo10.6.8.pkg icon from local directory to the

        "Add Packages and Post-Install Scripts" section of the SIU window

10) in the "Create Image" section:

        a) select the type "NetRestore"

        b) set the "Installed Volume:" field to "Macintosh HD"  (no quotes, can be any name)

        c) select the "Save To:" location

            (will be faster to a second local internal disk)

            (not faster to another partition on the same disk)

        d) set the "Image Name:" field to "Snow Leopard 10.6.8 NetRestore"

        e) the fields "Network Disk:", "Description:", and "Image Index:" don't

            matter unless one is going to use results on a NetBoot Server

11) click the Run button

12) when the dialogs appear, ignore the text and click OK for proper completion

            Dialog text:    "Image creation in progress. 

                            Cancel the image creation to proceed"

 

B. Post-process to create Restore Image:

1) find the directory created in the above process, named as in A.10d above

            (Snow Leopard 10.6.8 NetRestore.nbi)

2) in this directory are three files:

    - i386

    - NBImageInfo.plist

    - NetInstall.dmg

3) mount the NetInstall image  (double-click the NetInstall.dmg file)

4) navigate into the Contents of the package, to:  System/Installation/Packages/

5) copy the System.dmg file out to desktop or other work location

6) rename System.dmg to meaningful name, such as "Snow Leopard 10.6.8 System.dmg"

7) copy this .dmg file to external, bootable, Snow Leopard 10.6.8 system disk  (install in /Users/Shared/)

 

 

C. Install Snow Leopard 10.6.8 on new MacBook Pro or Mac Pro

 

via command line:

1) boot MacBook Pro or Mac Pro from external source prepared in B.7

2) open Terminal

3) find the restore target device specification

        a) run the command  "diskutil list"

        b) look for a 650 MB partition, labelled "Recovery HD" (likely disk0s3)

        c) the target partition should be immediately prior to the "Recovery HD" partition

        d) for a new computer with a 500 GB drive, this partition should be

                labelled "Macintosh HD", with a size of 499.2 GB

        e) make note of it's Device Identifier, likely disk0s2

4) issue the following asr (Apple Software Restore) command

    sudo asr restore --source "/path/to/restore.dmg" --target /dev/disk0s2 --erase

        (replace "/path/to/restore.dmg" with the path to the location and name used in step b.7)

5) this process proceeds and completes quickly, about 3-5 minutes. This is due to

        the "--erase" parameter; it indicates a block-copy operation

        If the process seems slow, likely the "--erase" option was omitted and

        the copy is being done as a file-copy operation.  Quit (ctl-c) and

        examine the command used...

 

 

via DiskUtility GUI:

 

1) boot MacBook Pro or Mac Pro from external source prepared in B.7

2) launch /Applications/Utilities/DiskUtility.app

3) select the computer hard drive  (typically "Macintosh HD")

4) click on the "Restore" tab

5) click on the "Image..." button to specify the "Source"

6) navigate to /Users/Shared/ and select the "Snow Leopard 10.6.8 System.dmg" file

7) drag the computer hard drive volume (Macintosh HD) to the "Destination" field

            (note: grab the volume, not the disk!!)

8) enable the "Erase destination" checkbox

9) click the "Restore" button

10) in the ensuing "Are you sure?" dialog, click the "Erase" button

11) authenticate with the local admin credentials

 

 

Apple Tech recommends leaving the Restore partition alone, and installing in the "Macintosh HD" partition only

 

commands to know:

    - asr

    - diskutil      (diskutil -list to see partitions)

    - hdiutil

Posted on Aug 15, 2011 9:00 AM

Close

Q: HowTo revert new MacBook Pro, Mac Pro or iMac to Snow Leopard

  • All replies
  • Helpful answers

first Previous Page 8 of 25 last Next
  • by Tech Harmony,

    Tech Harmony Tech Harmony Sep 10, 2011 10:18 PM in response to zirkenz
    Level 1 (4 points)
    Sep 10, 2011 10:18 PM in response to zirkenz

    Thank you for doing all that @zirkenz. Truly epic!

     

    I'd be curious about the results of an Xbench test.

     

    System Profiler will show you how your RAM, HD, processor, etc. post up

     

    Activity Monitor (set to show all processes) can give you a sense of the processes running ... I sort it so the most intensive CPU processes are at the top. There are also little graphs depicting how your memory is being used.

     

    Something like MenuMeters will show you a view of each of your cores/threads and how hard they are working...

     

    You can try booting into Safe Mode and running Geekbench....

     

    But it sounds like your next step would be re-installing Lion (or installing Lion to a bootable external drive) so that you can see if your Geekbenches are working alright under Lion.

     

    Usually if OSX doesn't like the machine it's running on, it won't even boot or it will kernel panic almost immediately. It's amazing to me that Apple would cripple the ability of its own software to run on its own compatible machines while others are getting OSX to run fantastically on machines it was never designed for. Is this Apple intentionally controlling how its computers are run to a whole new level? An automatic leftover from a habit of control? Or is it really some other problem (e.g. hardware)?

  • by zirkenz,

    zirkenz zirkenz Sep 10, 2011 11:48 PM in response to Tech Harmony
    Level 1 (0 points)
    Sep 10, 2011 11:48 PM in response to Tech Harmony

    Xbench scores also low. I really belive that they did something when building this imac or i have a bad part in the computer.

     

    But at least i was able to do roy's method so a win there i.e i did something i thought i could never do being over my head and all.    I will post my notes and pics soon.

     

    Now that i have done it twice it was actually pretty straightforward. I don't understand your geekbench scores but if you are getting correct scores now with the ssd installed, i suspect your scores should actually be much higher. The benchmark is based on stock with minimum ram that comes with it. Adding Ram, faster hard drive, running a 64 bit test, etc would result in higher scores. So i wonder how much of a performance hit you are taking or perhaps your system was not locked down or neutered by Apple but i do suspect that you should be getting higher scores with the ssd installed. No one else has reported in, i wish they would so we can see if this is a trend,especially if they bought the system late aug and it came with lion.

     

     

    TARGET DISK MODE INSTRUCTIONS

     

    Make sure you make a lion recovery thumb drive by downloading and using the apple lion recovery assistant from the support site before doing this.

     

    You need a mac running SL (host), the system being downgraded (other system) and a firewire 400-400 or 400-800 or 800-800 cable. Download the combo updater v 1.1 from the support site and place it on your host desktop.

     

     

     

    1. System being downgraded (other system) should be off. Connect the firewire to the host and other system.

     

    2. Boot The other system while holding down the T key until a firewire logo appears on other system.

     

    3. You will see a firewire logo on the other system and HD of the other system will mount on to your host desktop. Launch Disk Utility from the host system and either partition in 2 if you want to dual boot or erase the other system's HD for a one partition SL install. If you partition into 2 and delete the lion partition later, you will be left with 2 partitions that can't be joined together unless you create a bootable clone of your SL partition and restore/reinstall (see all my postings).

     

    4. Pop in the Mac Box Set SL (and perhaps the upgrade retail disc) disc in the host system optical drive, double click the installer, select the other system HD as the destination and let it do its thing. Your host system will auto boot but it will boot off the other system's HD. Let it finish installing and go through set up.

     

    5. Then run the combo updater.  shutdown the host, power down the other system, disconnect the firewire cable.

     

    6. Turn on the other system. It should boot SL 10.6.8, then run software update. If you partitioned it into 2 lion and SL then when restarting hold down the option key and select the SL partition.

     

    7. Download and run geekbench 32 bit free version and post score with your system specs here.

     

     

    Note: You may not get the geekbench scores that is benchmarked for your system after you downrade by either TDM or Roy's methods.

  • by Tech Harmony,

    Tech Harmony Tech Harmony Sep 11, 2011 10:52 AM in response to zirkenz
    Level 1 (4 points)
    Sep 11, 2011 10:52 AM in response to zirkenz

    Nice "Target Disk Method" instructions @zirkenz. And if you ever need to roll out virgin OSX installs, you know how to do it

     

    Here's the page I was comparing my Geekbench to http://www.primatelabs.ca/blog/2011/02/macbookpro-benchmarks-early-2011/

     

    This fella says that Geekbench doesn't account for graphics cards, storage devices etc, so he doesn't even list SSDs vs. 7200rpm stock drives, etc. I'm supposed to be getting 5900 and I get 5915 (MBP 2011, i5 2.3GHz 2415M, 10.6.8 downgrade).

     

    I can boot off my Lion external drive later and run Geekbench again to see if I get the same results booting over USB! But I've got too much open right now to futz with it

     

    With Geekbench, it shows you the individual scores and breakdowns and information about your model. Did you find other benchmarks that indicated if, perhaps, some one part of your rig isn't performing? Perhaps the number of cores or threads, the memory, Bus Frequency, BIOS (that's where they might have messed with your firmware but c'mon Apple!)... if it's down in Integer Score, Floating Point Score, Memory Score, etc, that would be harder to suss out. I mean, if every category is just slower, that's one thing, but if one score is bringing down the others or if you're "missing" a component compared with other folks with your machine, that should tell you something.

  • by Tech Harmony,

    Tech Harmony Tech Harmony Sep 11, 2011 11:20 AM in response to Tech Harmony
    Level 1 (4 points)
    Sep 11, 2011 11:20 AM in response to Tech Harmony

    @zirkenz, think of it this way: if OSX has the ability to detect your motherboard, firmware and then somehow throttle your processor, why doesn't Apple do the same thing to the happintosh community and cripple their machines too? Just googling for geekbenches, you come up with folks getting stellar benchmarks on all kinds of rigs... it could be that you're missing a driver (kext) somehow but we can't really talk about that here without confusing the heck out of people. It also wouldn't make much sense since your processor/model originally shipped with Snow Leo 10.6.x Sandybridge support: meaning all relevant drivers should be present.

     

    And what if it's something silly like you need Geekbench 64bit to test your extra cores (It looks like Xbench may only come in the 32bit variety so it would make sense if it were low too....)

     

    Interesting thread on a guy not happy with his iMac i7 scores (although still better than your 55xx) http://att.macrumors.com/showthread.php?t=1150348

  • by Roy Miller,

    Roy Miller Roy Miller Sep 12, 2011 7:30 AM in response to zirkenz
    Level 1 (30 points)
    Sep 12, 2011 7:30 AM in response to zirkenz

    Hey Zirkenz,

     

    congrats on getting through a challenging process!

     

    I have a concern about installing any OS on another computer via Target Disk Mode (TDM).  My concern is that the computer to which the TDM computer is attached will define the hardware for which the installer installs system components.

     

    That is, when a computer is booted in TDM, it is essentially reduced to an external fireware disk.  That disk is then mounted on the host system to which it is connected, and the resources installed are appropriate for the host system hardware.

     

    An example, using real Mac models is:

    - boot up a Mac Pro, as normal

    - connect a Mac Mini to the Mac Pro, using a Firewire cable

    - connect a USB keyboard to the Mac Mini

    - boot the Mac Mini, holding down the "T" key on the Mac Mini keyboard

    - the Mac Mini internal disk now mounts on the Mac Pro system

    - depending on the Mac Pro user account preferences set for Finder, the Mac Mini internal disk will appear on the desktop, in the left side of a Finder window, or may be only visible in the Disk Utility interface.

     

    at this point, that Mac Mini disk knows nothing about the Mac Mini hardware - it is just an external firewire disk.

     

    If one installs a system on this TDM Mac Mini disk, the system installed will be one appropriate for the Mac Pro, not for the Mac Mini!  It cannot contain Mac Mini-specific drivers, etc, as the install process is completely unaware that a Mac Mini is involved in any way!

     

    So, I hear you and understand that you arrived at the same geekbench scores using either install path (TDM & "Roy's Method").  I don't have an answer for you there.  However, I'm sure that using the TDM method will not install the appropriate system for computer booted in TDM, unless both systems are at least close to identical.

     

    If you were to mount a current Mac Mini in TDM mode on another current Mac Mini, this methodology would likely install proper system resources.  Again, only because the host system is the "same" as the TDM system.

     

    I hope this is clear, because I believe it is a critical point to understand.

     

    cheers,
    Roy

  • by Roy Miller,

    Roy Miller Roy Miller Sep 12, 2011 7:48 AM in response to zirkenz
    Level 1 (30 points)
    Sep 12, 2011 7:48 AM in response to zirkenz

    @zirkenz

    the system.dmg which i renamed is only 4.82gb, the 10.6.3 image is 10.42 gb in system image utility and 6.1-6.6 as a .dmg file and the combo update is 1.09 gb. How does a 4.82gb file contain everything? Is this the right size?

     

    a) the 10.6.3 image (Mac Box Set?) is an installer, that contains not only what needs to be installed, but also the installer engine and all the extra pre- and post-flight install scripts, multiple language support, optional installs like "all the currently known printer drivers", etc.

     

    b) the combo update (presumably Combo Update 10.6.8 v1.1) is also an installer, with an install engine, additional scripts, etc., in addition to the payload - which is comprised of the parts that need to be installed.

     

    c) The resulting file of the process is not an installer.  It is an installed system, that has been packaged in a dmg image file. It contains a bootable system, with all the Apple applications and system files, and is ready to boot a computer, just as if you pulled that computer out of an Apple box, and turned it on.  The resulting file does not contain the installer engines, scripts, and tools necessary to perform installer tasks.

     

    so, my conclusion is, an image file of an installed system will always be smaller than the image file of the installer itself.

     

    you can check this out by mounting both the 10.6.3 installer image and the resulting 10.6.8 image from the procedure.  The first will show an installer disc, identical to inserting the install DVD.  The second will show an installed system, with an /Application folder, a /System folder, a /Library folder, a /Users folder, etc.

     

    Note to anyone wondering how to mount an image file:  double click on the image file (one with ".dmg" extension)

     

    hope this clears up some confusion.

  • by Roy Miller,

    Roy Miller Roy Miller Sep 12, 2011 7:51 AM in response to zirkenz
    Level 1 (30 points)
    Sep 12, 2011 7:51 AM in response to zirkenz

    So either Apple has done something in the firmware to neuter the system or the roy installer/TDM method lacks core i support ...

     

    a) unlikely that any firmware neutering exists or has occured, in my opinion

     

    b) the "Roy Installer" method does properly install a system that supports core i chips

     

    c) the TDM method will not support core i chips, unless the host system is a core i system  (please see seperate post above about what happens in TDM method)

  • by Josh1565,

    Josh1565 Josh1565 Sep 12, 2011 9:17 AM in response to Roy Miller
    Level 1 (0 points)
    Sep 12, 2011 9:17 AM in response to Roy Miller

    Roy,

     

    Does it seems feasible that you could follow all your steps as exact, but instead of using an external disk with a SLeo 10.6.8 install on it to restore the .dmg we created, could you jsut leave the "Snow Leopard 10.6.8 System.dmg" on the computer you created it on, put that computer into TDM, boot up the new iMac holding down option key, select that host computer that is in TDM and continue along the process?  This would jsut be instead of having an install of SLeo on an external drive.  This should work since you are doing a restore rather than an install, and therefore will not cause the problems assocaited with using unlike machines in TDM for an install.

     

    Did I make sense?  I tested this methd on older imac with 10.6.8 I set-up to test this process and it worked, but that is obviously not relevant to doing it on the new iMacs (yet to arrive).

     

    Thanks again for the help.

     

    Josh

  • by Tech Harmony,

    Tech Harmony Tech Harmony Sep 12, 2011 9:54 AM in response to Roy Miller
    Level 1 (4 points)
    Sep 12, 2011 9:54 AM in response to Roy Miller

    Merry Monday Roy

     

    Regarding TDM (Target Disc Mode) and TDM Installs:

     

    Historically you could literally hook up an OSX drive -- external or TDM -- to another machine and could happily boot and run from the drive, as long as the new host machine were capable of running the OS to begin with. All of the drivers are present in each OSX and the external/TDM drive would automatically detect its host at boot and boot up.

     

    If you look in /System/Library/Extensions (look but don't touch!) this is where the highest level drivers for our systems live. You will see, for example, dozens of video card drivers for machines other than the one you are using. One would think that if the installer targets specific model Macs, it would only install those video card drivers relevant to the model, not ones for every other Mac model that the OS can support. And yet, there they are!

     

    Maybe Apple has changed its methods with the advent of Sandybridge processors and I can't speak to Lion, but historically external systems (on USB drives, Firewire, or TDM) could be booted to any Mac that could handle the OS level. I've relied on this feature many many times.

     

    Often the first thing I did with a new computer is remove the stock drive and put in my original drive, from my old machine, and the computer would boot right up, no problems.

     

    I confess I never ran Geekbenches under these various conditions to see if the system were running more slowly, but I never noticed. No kernel panics, no stability issues... trust me, you would know pretty fast if your Mac didn't like your OS

     

    I'm not saying Apple can't have changed all this but historically they seem to install a "universal system."

     

    YMMV

  • by Roy Miller,

    Roy Miller Roy Miller Sep 12, 2011 9:58 AM in response to Josh1565
    Level 1 (30 points)
    Sep 12, 2011 9:58 AM in response to Josh1565

    @Josh

     

    I think I have the picture you describe.  The only issue I see from reading your wording is that the contents of the new iMac hard drive need to be replaced by the contents of System.dmg (or whatever you have named the result of the process). 

    ... could you jsut leave the "Snow Leopard 10.6.8 System.dmg" on the computer you created it on, put that computer into TDM, boot up the new iMac holding down option key, select that host computer that is in TDM and continue along the process?

    First, if you are using "The Procedure", you end up with a version of Snow Leopard 10.6.8 v1.1 that should run any model Mac computer that can correctly run SL 10.6.8.  This list includes all current and recent models, with the exception of the current MacBook Air and Mac Mini. 

     

    Disclaimer note:  if you have an older computer that is capable of running SL 10.6.8 correctly, this procedure is a more complicated way of getting SL 10.6.8 installed on it.  If SL is already installed, it is much easier to just run the appropriate updaters.

     

    It sounds like you have

    (a) a computer currently running SL 10.6.8 (or close system version)

    (b) a new MacBook Pro, Mac Pro, or iMac, soon to be delivered with Lion installed

    (c) no "extra" external disk

     

    Under these circumstances, I suggest:

    1. - update your system in (a) above to 10.6.8, if not already there

    2. - follow "The Procedure" on that computer, from A through B, storing the results somewhere on that computer.  (don't even need a new computer, external disk, etc. to do this)

    3. - when you've finished with part B, check out that System.dmg or renamed file by mounting it (double-click to open & mount)

    4. - look at the folder layout in this image - should look just like a newly acquired Snow Leopard system, except some folders don't have fancy icons

    5. - when curiosity is satisfied, unmount the mounted image file (drag to trash, select and cmd-E, click the Eject triangle in a Finder window, etc.)

     

    now your are ready for the new computer (assuming an iMac).  When it arrives, connect the new iMac to your existing computer with a firewire cable, and boot the iMac into Target Disk mode.  When the disk appears, follow part C of the procedure to replace the contents of the Macintosh HD partiion on the new iMac.  This means running Disk utility on your existing computer, selecting the appropriate iMac partition, and select the System.dmg or otherwise named file from where you put it on your existing system as the source for replacing the contents of the iMac hard drive partition.

     

    Did this make sense?

     

    This should work since you are doing a restore rather than an install, and therefore will not cause the problems assocaited with using unlike machines in TDM for an install.

    Yes - because "The Procedure" creates a "universal" system, meaning it contains drivers and support files for several computer models.

     

    put that computer into TDM, boot up the new iMac holding down option key, select that host computer that is in TDM and continue along the process?

    Here, trying to option-boot the new iMac from another computer's installed system could be problematic, depending on the other computer and what system was installed on it.  Simpler in my mind to just have the iMac internal hard drive be the "external TDM disk" on the existing computer.   That I believe will always work (as long as both computers have firewire ports!), while option-booting the iMac may or may not boot.

     

    In terms of the topology of the disks, and not being booted on the iMac internal drive, your process seems to me that it would work.

     

    cheers!

  • by Roy Miller,

    Roy Miller Roy Miller Sep 12, 2011 10:09 AM in response to Tech Harmony
    Level 1 (30 points)
    Sep 12, 2011 10:09 AM in response to Tech Harmony

    Cool Tech! 

     

    I'm probably running on some old assumptions.

     

    However, I do know for sure from personal past experiences that system discs delivered with a PowerBook would not boot a G4 or G5 tower, whereas when I purchased a retail system install disc I could boot any of those machines.

     

    If you look in /System/Library/Extensions (look but don't touch!) this is where the highest level drivers for our systems live. You will see, for example, dozens of video card drivers for machines other than the one you are using. One would think that if the installer targets specific model Macs, it would only install those video card drivers relevant to the model, not ones for every other Mac model that the OS can support. And yet, there they are!

    I take it that you are convinced that the drivers installed in /System/... represent drivers for video cards from other computer models, rather than drivers for video cards that could be added to this specific collection of hardware we call a computer. 

     

    It certainly could be that "universal" type systems get installed, at least these days.  I haven't directly investigated this - but maybe time to try a small experiment! 

     

    "look but don't touch!" - like it!  But of course, having burned my fingers long ago, I already know that everything is /System/Libarary/.... is hot! 

     

    Merry Monday back at you - you and Zirkenz have been busy over the weekend!  I got to play in my garden...

  • by Josh1565,

    Josh1565 Josh1565 Sep 12, 2011 10:13 AM in response to Roy Miller
    Level 1 (0 points)
    Sep 12, 2011 10:13 AM in response to Roy Miller

    Hey Roy,

     

    Thanks again.  Your description of how to perform the restore without an external disk, and just using the existing 10.6.8 iMac(old) is exactly how I was doing it.  In the test I conducted, I merely wanted to see if the thigngs I had done from A-C were correct, but instead of using an external disk, I connected it via TDM assuming my old iMac were the new one (in TDM as external to the MBP I did the process on).  All worked perfectly.

     

    Now the new iMac jsut has to arrive.  I have done the screen captures for most of steps A&B and revised the instructions a little for those who are having troubles...hope I can complete that soon and post.

     

    Thanks again.

     

    Josh

  • by Steve Jolly,

    Steve Jolly Steve Jolly Sep 12, 2011 10:54 AM in response to Roy Miller
    Level 1 (35 points)
    Sep 12, 2011 10:54 AM in response to Roy Miller

    Roy,

     

    Speaking as a "lurker" on this thread for the past few days, my thanks for your crystal-clear exposition and directions in your discussions over here. When you get time, please check in at the somewhat larger existing thread dealing with falling back to Snow Leopard on the new 2011 "Lion Locked" Mac Minis.

     

    When you have time, we'd appreciate your posting some of your information on the "Roy Method" as applicable to the 2011 Mini.

     

           https://discussions.apple.com/thread/3209335?start=210&tstart=0

     

    You are of course totally correct in your explanation of why Target Disk Mode doesn't work well in configuringan installation for a "Lion" Mac, because the OSX installer will install the software needed for the "hosting" Mac computer for which it's playing out the install, not the "target drive" Lion Mac's chips and motherboard, which appear as just a dumb firewire drive to the installer.

     

    Zirkenz,  please bring some of this knowledge back to us over at the other thread!...

     

    One last final comment: some of our visitors on the other thread have a problem believing that the slowdown and other problems encountered in running Snow Leopard on any "Lion designed" machine (like the new Mini) is not due to Apple building some evil poison-pill code into the installers; it's just that Snow Leopard lacks the resources that it's expecting to find when it tries to run on those machines.

     

    There are lots of little pre-Lion-supportive code snippets in the chips of older Macs, and different chips and motherboard connections are now running the new "Lion" Macs. All of those little hooks and helpers are missing, when Snow Leopard goes looking for them. So, Snow Leopard struggles because it's strangled -- not by intent but by the machine it's running on. And, that's why it's taking a little time for "virtualization" companies to come up with a smooth solution that allows Snow Leopard to run as a "virtual machine" on a Lion-designed Mac.

     

    Everyone I've talked to at Apple or at various software companies agrees that running Snow Leopard on Lion machines will happen, and that "this is just the way it is" and not part of some draconian Apple plot. Therefore, it's a solveable problem, and we WILL be running Snow Leopard at close-to-or-FULL speed, soon, on the various "Lion" machines.

     

    Lots of folks are working on solutions (but few of them are as clear and elegant as the Roy Method is proving to be for some kinds of installations). Hope this info is helpful, and thanks for all of your work on resolving this frustrating situation.

  • by Tech Harmony,

    Tech Harmony Tech Harmony Sep 12, 2011 10:45 AM in response to Roy Miller
    Level 1 (4 points)
    Sep 12, 2011 10:45 AM in response to Roy Miller

    @Roy Jealous of the gardening! Woot!

     

    Yeah those grey restore discs were specific to product line... but I think they just put like a detector on those discs to keep them from booting on machines outside of their product line... The actual results of those installs were universal.

     

    ...

     

    Okay, I did a quick comparison between the video kexts in my MBP 2011 @ 10.6.8 and a client's Mac Pro 10.6.7 and they both had the same 30+ graphics drivers (for ATI Radeon, buiilt-in Intel, and some GeForces (Nvidia)) except for one: the Mac Pro did not have the ATI6000 driver. I believe this would be installed if I upgraded her to 10.6.8 but I don't like to run Software Updates remotely like that for client systems so I'm not going to test it right now

     

    But the timing is right because the newer machines have access to the ATI Radeon 6000 line and all came out after 10.6.8/Lion. Although the Mac Pro line is still in the 5000's at the Apple Store, I don't think they have ever shipped with built-in Intel graphics and yet drivers for on-board Intel are still present in the Mac Pro.

     

    Now these are just video drivers and yes, it is possible that there are differences within the driver contents themselves, but while Apple does micro-manage lots of things, they don't usually do it in this case....

  • by Roy Miller,

    Roy Miller Roy Miller Sep 12, 2011 10:48 AM in response to Josh1565
    Level 1 (30 points)
    Sep 12, 2011 10:48 AM in response to Josh1565

    Great Josh - and I just learned, based on Tech Harmony's information on TDM, that my concerns about the potential mismatch of hardware in TDM mounting my be baseless.

     

    @ Tech & Zirkenz - I just did a small test of option-booting my loaded Mac Pro from a Target Disk Mode mounted internal hard drive on my MacBook Pro 13".  It appeared to work flawlessly, although to be fair I didn't exercise it very much!

     

    so, Zirkenz, the good news, or perhaps bad news, is that it does appear that your TDM method installs the same system arrived at via "The Procedure".  I'll reserve a little scepticism about that for now - I want to ask my Apple Tech rep if this is so and if so, why did I not use that methodology.

     

    cheers!

first Previous Page 8 of 25 last Next