Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.apps > #32191 > unrolled thread
| Started by | ANTant@zimage.com (Ant) |
|---|---|
| First post | 2015-09-28 22:55 -0500 |
| Last post | 2015-09-29 23:17 +0000 |
| Articles | 20 on this page of 113 — 7 participants |
Back to article view | Back to comp.sys.mac.apps
Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-28 22:55 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-29 00:01 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-28 23:13 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 08:01 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 16:13 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-29 12:17 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 16:49 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 12:56 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 18:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 14:26 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 23:18 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 20:51 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 02:10 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 21:41 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 04:05 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 13:58 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 21:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 16:34 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 22:48 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 18:51 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-29 19:54 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 20:52 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 01:27 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 21:42 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 04:05 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 23:19 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-09-29 23:16 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 23:21 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 05:08 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 00:36 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-09-30 01:08 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 03:14 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-30 12:24 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-09-30 10:03 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 15:11 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 16:46 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 21:58 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 17:00 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 01:27 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 22:53 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 04:08 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 00:25 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-10-01 01:42 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 06:02 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 01:29 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 06:36 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 16:12 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 21:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-10-01 21:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 17:00 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 18:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 16:13 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 21:37 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 17:21 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 22:49 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-10-01 13:33 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 18:27 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Alan Browne <alan.browne@freelunchvideotron.ca> - 2015-10-01 11:06 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 18:29 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 16:17 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 21:32 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 17:23 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-01 22:52 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 18:10 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-10-01 20:48 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-10-02 03:07 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-30 11:17 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 16:08 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-30 12:24 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 16:50 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 06:30 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 03:20 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 15:00 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 19:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 16:47 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-09-30 00:32 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 00:43 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-09-30 01:50 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-30 03:50 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 15:05 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-30 16:10 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-30 11:17 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-30 19:24 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-30 15:47 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-30 20:47 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-30 17:14 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-10-01 13:27 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-10-01 11:38 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-10-01 16:08 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-10-01 18:44 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-09-30 18:37 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-10-01 13:30 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? David Ritz <dritz@mindspring.com> - 2015-10-01 12:19 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-10-01 21:25 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Andreas Rutishauser <andreas@macandreas.ch> - 2015-10-01 06:26 +0200
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Andreas Rutishauser <andreas@macandreas.ch> - 2015-09-30 05:22 +0200
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 22:26 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 04:15 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-29 19:03 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 15:25 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 22:36 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2015-09-30 03:55 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 21:26 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 16:36 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-29 17:47 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 17:16 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-29 18:33 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 20:39 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 22:53 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? ANTant@zimage.com (Ant) - 2015-09-29 20:40 -0500
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 22:53 +0000
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? nospam <nospam@nospam.invalid> - 2015-09-29 18:57 -0400
Re: Any catches on restoring from an old Mac OS X v10.8.5 Time Machine HDD backup to new SSD on a 13.3" MacBook Pro (9,2; MD102ll/A)? Jolly Roger <jollyroger@pobox.com> - 2015-09-29 23:17 +0000
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-10-01 21:32 +0000 |
| Message-ID | <d75n46Frd4cU1@mid.individual.net> |
| In reply to | #32316 |
Ant <ANTant@zimage.com> wrote: > >> I believe he said he already turned on FileVault, which means the >> contents of the drive are encrypted. So I really don't get his hesitance >> to simply erase the volume and hand it over. Apple's not interested in >> spending the considerable time and money it would take to get the data >> off a failing hard drive. > > Actually, it isn't. :( You say that as if you have no choice in the matter, which is frankly ridiculous. All you have to do is turn FileVault on, let it encrypt the drive, then erase the drive with a normal erase in Disk Utility. Doing so will ensure even if someone does spend the time and mon to scan the volume will only find garbled encrypted pieces of files that they cannot put together or decrypt. You are being unreasonably and extremely paranoid about this considering how easy it is to protect the data from prying eyes. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-10-01 17:23 -0500 |
| Message-ID | <BdidnWzAkIzYL5DLnZ2dnUU7-Y_46u6z@earthlink.com> |
| In reply to | #32320 |
> >> I believe he said he already turned on FileVault, which means the
> >> contents of the drive are encrypted. So I really don't get his hesitance
> >> to simply erase the volume and hand it over. Apple's not interested in
> >> spending the considerable time and money it would take to get the data
> >> off a failing hard drive.
> >
> > Actually, it isn't. :(
> You say that as if you have no choice in the matter, which is frankly
> ridiculous. All you have to do is turn FileVault on, let it encrypt the
> drive, then erase the drive with a normal erase in Disk Utility. Doing so
> will ensure even if someone does spend the time and mon to scan the volume
> will only find garbled encrypted pieces of files that they cannot put
> together or decrypt.
> You are being unreasonably and extremely paranoid about this considering
> how easy it is to protect the data from prying eyes.
Isn't it a bad idea to start now on a dying HDD? I know encrypting can
take a very long time with data on it. I remember encrypting my own
drives and that took hours and a few days.
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-10-01 22:52 +0000 |
| Message-ID | <d75ropFs7suU2@mid.individual.net> |
| In reply to | #32324 |
On 2015-10-01, Ant <ANTant@zimage.com> wrote: >> >> I believe he said he already turned on FileVault, which means the >> >> contents of the drive are encrypted. So I really don't get his hesitance >> >> to simply erase the volume and hand it over. Apple's not interested in >> >> spending the considerable time and money it would take to get the data >> >> off a failing hard drive. >> > >> > Actually, it isn't. :( > >> You say that as if you have no choice in the matter, which is frankly >> ridiculous. All you have to do is turn FileVault on, let it encrypt the >> drive, then erase the drive with a normal erase in Disk Utility. Doing so >> will ensure even if someone does spend the time and mon to scan the volume >> will only find garbled encrypted pieces of files that they cannot put >> together or decrypt. > >> You are being unreasonably and extremely paranoid about this considering >> how easy it is to protect the data from prying eyes. > > Isn't it a bad idea to start now on a dying HDD? I know encrypting can > take a very long time with data on it. I remember encrypting my own > drives and that took hours and a few days. Why is it a bad idea? The data is backed up, so losing it isn't a concern. If the drive dies in the middle of it, the drive is dead and cannot be accessed to get the data off of it anyway. You have also balked at simple erasing the drive, as if that somehow is dangerous or risky. You are being completely irrational. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-10-01 18:10 -0500 |
| Message-ID | <EZidnbKQzdjJIJDLnZ2dnUU7-R2dnZ2d@earthlink.com> |
| In reply to | #32327 |
> >> >> I believe he said he already turned on FileVault, which means the
> >> >> contents of the drive are encrypted. So I really don't get his hesitance
> >> >> to simply erase the volume and hand it over. Apple's not interested in
> >> >> spending the considerable time and money it would take to get the data
> >> >> off a failing hard drive.
> >> >
> >> > Actually, it isn't. :(
> >
> >> You say that as if you have no choice in the matter, which is frankly
> >> ridiculous. All you have to do is turn FileVault on, let it encrypt the
> >> drive, then erase the drive with a normal erase in Disk Utility. Doing so
> >> will ensure even if someone does spend the time and mon to scan the volume
> >> will only find garbled encrypted pieces of files that they cannot put
> >> together or decrypt.
> >
> >> You are being unreasonably and extremely paranoid about this considering
> >> how easy it is to protect the data from prying eyes.
> >
> > Isn't it a bad idea to start now on a dying HDD? I know encrypting can
> > take a very long time with data on it. I remember encrypting my own
> > drives and that took hours and a few days.
> Why is it a bad idea? The data is backed up, so losing it isn't a
> concern. If the drive dies in the middle of it, the drive is dead and
> cannot be accessed to get the data off of it anyway.
Alright. I will encrypt before tomorrow's appointment since this
HDD death is expected. Maybe it will die before the appointment to show
them the problem. Ha. I wonder how long it will take to encrypt. :/
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-10-01 20:48 -0500 |
| Message-ID | <c92dnSq5TuLLf5DLnZ2dnUU7-WmdnZ2d@earthlink.com> |
| In reply to | #32328 |
...
> > Why is it a bad idea? The data is backed up, so losing it isn't a
> > concern. If the drive dies in the middle of it, the drive is dead and
> > cannot be accessed to get the data off of it anyway.
> Alright. I will encrypt before tomorrow's appointment since this
> HDD death is expected. Maybe it will die before the appointment to show
> them the problem. Ha. I wonder how long it will take to encrypt. :/
Estimated time is unknown to finish. :/
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-10-02 03:07 +0000 |
| Message-ID | <d76amoF1651U1@mid.individual.net> |
| In reply to | #32330 |
On 2015-10-02, Ant <ANTant@zimage.com> wrote: > ... >> > Why is it a bad idea? The data is backed up, so losing it isn't a >> > concern. If the drive dies in the middle of it, the drive is dead and >> > cannot be accessed to get the data off of it anyway. > >> Alright. I will encrypt before tomorrow's appointment since this >> HDD death is expected. Maybe it will die before the appointment to show >> them the problem. Ha. I wonder how long it will take to encrypt. :/ > > Estimated time is unknown to finish. :/ Erasing would have been much faster. And you could have done it DAYS ago, if you hadn't been so stubborn. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2015-09-30 11:17 -0400 |
| Message-ID | <300920151117354147%nospam@nospam.invalid> |
| In reply to | #32261 |
In article <alpine.OSX.2.20.1509300944440.734@mako.ath.cx>, David Ritz <dritz@mindspring.com> wrote: > >> I'd lean toward doing the migration, following a clean install on the > >> new drive, if it ever gets that far. > > > Ever gets that far? > > You still haven't determined that the HDD is the problem. If it's a > different hardware issue, you're just spinning your wheels. it's very clear that the hard drive is the problem.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-09-30 16:08 +0000 |
| Message-ID | <d72fobF21kpU1@mid.individual.net> |
| In reply to | #32265 |
On 2015-09-30, nospam <nospam@nospam.invalid> wrote: > In article <alpine.OSX.2.20.1509300944440.734@mako.ath.cx>, David Ritz ><dritz@mindspring.com> wrote: > >> >> I'd lean toward doing the migration, following a clean install on the >> >> new drive, if it ever gets that far. >> >> > Ever gets that far? >> >> You still haven't determined that the HDD is the problem. If it's a >> different hardware issue, you're just spinning your wheels. > > it's very clear that the hard drive is the problem. Nah, it may not be the only problem. There could be an issue with the ATA controller hardware, for instance. Best to let Apple run a full diagnostic on it to be sure. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2015-09-30 12:24 -0400 |
| Message-ID | <300920151224003219%nospam@nospam.invalid> |
| In reply to | #32266 |
In article <d72fobF21kpU1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote: > >> You still haven't determined that the HDD is the problem. If it's a > >> different hardware issue, you're just spinning your wheels. > > > > it's very clear that the hard drive is the problem. > > Nah, it may not be the only problem. There could be an issue with the > ATA controller hardware, for instance. Best to let Apple run a full > diagnostic on it to be sure. it's highly unlikely that anything on the logic board was damaged due to a fall. the hard drive has moving parts and although there are shock sensors, it still can sustain damage.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-09-30 16:50 +0000 |
| Message-ID | <d72i62F21kpU6@mid.individual.net> |
| In reply to | #32268 |
On 2015-09-30, nospam <nospam@nospam.invalid> wrote: > In article <d72fobF21kpU1@mid.individual.net>, Jolly Roger ><jollyroger@pobox.com> wrote: > >> >> You still haven't determined that the HDD is the problem. If it's a >> >> different hardware issue, you're just spinning your wheels. >> > >> > it's very clear that the hard drive is the problem. >> >> Nah, it may not be the only problem. There could be an issue with the >> ATA controller hardware, for instance. Best to let Apple run a full >> diagnostic on it to be sure. > > it's highly unlikely that anything on the logic board was damaged due > to a fall. Unlikely, but not impossible. > the hard drive has moving parts and although there are shock sensors, > it still can sustain damage. Sure, and it's still best to let Apple run a full diagnostic to be sure. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-09-30 06:30 +0000 |
| Message-ID | <d71draFo4t8U1@mid.individual.net> |
| In reply to | #32251 |
Ant <ANTant@zimage.com> wrote: >>>>> OK, cool. Recovering would be faster and nicer since we don't have >>>>> to reconfigure. I was surprised TM's restore was after a three hours >>>>> restore on Saturday. :) >>>> >>>> I will point out that simply restoring from a Time Machine will not >>>> install a recovery partition on the replacement disk. That only takes >>>> place when one first installs the operating system. >>> >>> Interesting. How do you put a recovery partition back then onto a new >>> disk? I am surprised it doesn't do that. > >> Why bother when it's very easy to just install the OS which creates a >> recovery partition and then restore from backup? You are making this more >> complicated than it has to be. > > Because I thought TM puts the recovery partition in it. :( More > time wasted since TM erases that Mac OS X partition. :/ Time Machine doesn't erase anything. You did that yourself in Disk Utility after *booting* on the Time Machine volume, which I would avoid personally. I wouldn't boot on the backup disk, personally. >>>> I'd highly recommend running the installer, after which you can >>>> restore from your backup or perform a system migration from the Time >>>> Machine backup. > >> Yep. It's the best way. > > Argh. More work to do. I am also surprised you can't make a recovery > partition after doing a full TM restore. Bah! I didn't say it wasn't possible. It's just way simpler and easier to make the USB installer which you do with a single terminal command and only takes a few minutes. Manually creating a recovery partition is more complicated. >>>> I'd also ask, why isn't your account planning on updating to a newer >>>> version of the operating system, while going to all the trouble to >>>> upgrade the boot disk? It would seem the timing is right. >>> >>> Doesn't he have to buy it? > >> No, the latest versions of OS X are free - since 10.9 (10.10 is the current >> release, and 10.11 will be released soon). > > Hmmm. Those newer versions could break his old stuff to have more work. > Grr. Nah, not much broke from 10.8 to 10.10. -- Sent from my iPhone
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-09-30 03:20 -0500 |
| Message-ID | <ipidnTIfN_LUBpbLnZ2dnUU7-YX46u6z@earthlink.com> |
| In reply to | #32254 |
> >>>> I will point out that simply restoring from a Time Machine will not
> >>>> install a recovery partition on the replacement disk. That only takes
> >>>> place when one first installs the operating system.
> >>>
> >>> Interesting. How do you put a recovery partition back then onto a new
> >>> disk? I am surprised it doesn't do that.
> >
> >> Why bother when it's very easy to just install the OS which creates a
> >> recovery partition and then restore from backup? You are making this more
> >> complicated than it has to be.
> >
> > Because I thought TM puts the recovery partition in it. :( More
> > time wasted since TM erases that Mac OS X partition. :/
> Time Machine doesn't erase anything. You did that yourself in Disk Utility
> after *booting* on the Time Machine volume, which I would avoid personally.
> I wouldn't boot on the backup disk, personally.
I pretty sure TM said it would erase the partition where old Mac OS X
data was on.
> >>>> I'd highly recommend running the installer, after which you can
> >>>> restore from your backup or perform a system migration from the Time
> >>>> Machine backup.
> >
> >> Yep. It's the best way.
> >
> > Argh. More work to do. I am also surprised you can't make a recovery
> > partition after doing a full TM restore. Bah!
> I didn't say it wasn't possible. It's just way simpler and easier to make
> the USB installer which you do with a single terminal command and only
> takes a few minutes. Manually creating a recovery partition is more
> complicated.
Do you have the instructions for that? I guess I will make a USB
installer of Mac OS X then. :(
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-09-30 15:00 +0000 |
| Message-ID | <d72bnqF16p4U1@mid.individual.net> |
| In reply to | #32257 |
Ant <ANTant@zimage.com> wrote: >>>>>> I will point out that simply restoring from a Time Machine will not >>>>>> install a recovery partition on the replacement disk. That only takes >>>>>> place when one first installs the operating system. >>>>> >>>>> Interesting. How do you put a recovery partition back then onto a new >>>>> disk? I am surprised it doesn't do that. >>> >>>> Why bother when it's very easy to just install the OS which creates a >>>> recovery partition and then restore from backup? You are making this more >>>> complicated than it has to be. >>> >>> Because I thought TM puts the recovery partition in it. :( More >>> time wasted since TM erases that Mac OS X partition. :/ > >> Time Machine doesn't erase anything. You did that yourself in Disk Utility >> after *booting* on the Time Machine volume, which I would avoid personally. >> I wouldn't boot on the backup disk, personally. > > I pretty sure TM said it would erase the partition where old Mac OS X > data was on. That wasn't Time Machine. You booted to the Recovery partition on the Time Machine volume and ran a utility. >>>>>> I'd highly recommend running the installer, after which you can >>>>>> restore from your backup or perform a system migration from the Time >>>>>> Machine backup. >>> >>>> Yep. It's the best way. >>> >>> Argh. More work to do. I am also surprised you can't make a recovery >>> partition after doing a full TM restore. Bah! >> I didn't say it wasn't possible. It's just way simpler and easier to make >> the USB installer which you do with a single terminal command and only >> takes a few minutes. Manually creating a recovery partition is more >> complicated. > > Do you have the instructions for that? I guess I will make a USB > installer of Mac OS X then. :( Here you go. I typically use the command-line method myself, but the GUI method looks fine too: <http://arstechnica.com/apple/2014/10/how-to-make-your-own-bootable-os-x-10-10-yosemite-usb-install-drive/> -- Sent from my iPhone
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-09-30 19:26 +0000 |
| Message-ID | <d72rc1F577rU1@mid.individual.net> |
| In reply to | #32260 |
On 2015-09-30, Jolly Roger <jollyroger@pobox.com> wrote: > Ant <ANTant@zimage.com> wrote: >> >> Do you have the instructions for that? I guess I will make a USB >> installer of Mac OS X then. :( > > Here you go. I typically use the command-line method myself, but the GUI > method looks fine too: > ><http://arstechnica.com/apple/2014/10/how-to-make-your-own-bootable-os-x-10-10-yosemite-usb-install-drive/> > FYI: El Capitan was released today, making Yosemite the new "previous release". While these instructions probably work for El Capitan as well, I advise you to stick with Yosemite for your client's machine, since a lot of stuff is changing in El Capitan that could effect software compatibility for third-party apps. Not much at all broke going from Mountain Lion to Yosemite in comparison. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-09-30 16:47 -0500 |
| Message-ID | <8pGdnQWvWt_6xZHLnZ2dnUU7-WWdnZ2d@earthlink.com> |
| In reply to | #32271 |
> >> Do you have the instructions for that? I guess I will make a USB
> >> installer of Mac OS X then. :(
> >
> > Here you go. I typically use the command-line method myself, but the GUI
> > method looks fine too:
> >
> ><http://arstechnica.com/apple/2014/10/how-to-make-your-own-bootable-os-x-10-10-yosemite-usb-install-drive/>
> FYI: El Capitan was released today, making Yosemite the new "previous
> release". While these instructions probably work for El Capitan as well,
> I advise you to stick with Yosemite for your client's machine, since a
> lot of stuff is changing in El Capitan that could effect software
> compatibility for third-party apps. Not much at all broke going from
> Mountain Lion to Yosemite in comparison.
Thanks. :)
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | David Ritz <dritz@mindspring.com> |
|---|---|
| Date | 2015-09-30 00:32 -0500 |
| Message-ID | <alpine.OSX.2.20.1509300010050.734@mako.ath.cx> |
| In reply to | #32248 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message On Tuesday, 29 September 2015 23:21 -0500, in article <i4ydnXhYTp_K_pbLnZ2dnUU7-LudnZ2d@earthlink.com>, Ant <ANTant@zimage.com> wrote: > In comp.sys.mac.apps David Ritz <dritz@mindspring.com> wrote: >> On Tuesday, 29 September 2015 21:42 -0500, >> in article <g5ednespX9aO0ZbLnZ2dnUU7-QmdnZ2d@earthlink.com>, >> Ant <ANTant@zimage.com> wrote: >>> OK, cool. Recovering would be faster and nicer since we don't have >>> to reconfigure. I was surprised TM's restore was after a three >>> hours restore on Saturday. :) >> I will point out that simply restoring from a Time Machine will not >> install a recovery partition on the replacement disk. That only >> takes place when one first installs the operating system. > Interesting. How do you put a recovery partition back then onto a > new disk? I am surprised it doesn't do that. Time Machine does not backup the recovery partition. How could it restore what it hasn't backed up? While it's possible to restore a full disk clone, including all partitions, it doesn't sound like there's a disk from which such a clone can be made. It's been reformatted at least once. Additionally, this may not have been possible, if the disk was damaged in the drop. >> I'd highly recommend running the installer, after which you can >> restore from your backup or perform a system migration from the >> Time Machine backup. >> I'd also ask, why isn't your account planning on updating to a >> newer version of the operating system, while going to all the >> trouble to upgrade the boot disk? It would seem the timing is >> right. > Doesn't he have to buy it? I believe all that's required is a download from the App Store. Both Mavericks and Yosemite were released without charge. I fully expect that El Capitan will be the same. This should be true for any supported Mac with App Store, including late versions of OS X 10.6. >> Also note, there remains a somewhat significant chance that it may >> not be a disk issue at all. A trip to the Genius Bar is still well >> worth considering. > Yeah, I am trying to convince him. Would you like to borrow my clue-by-four? -- David Ritz <dritz@mindspring.com> Recipient of the Golden Mallet Award for Usenet Achievement. Be kind to animals; kiss a shark. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYLc9YACgkQUrwpmRoS3usNygCdEZbi/xX2Vi8rg+oyca/4TYb+ Xr0AoPfIMH64SDApBdDQPXCbl47iajs3 =6Kgh -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-09-30 00:43 -0500 |
| Message-ID | <kK6dnYUjOvH165bLnZ2dnUU7-aWdnZ2d@earthlink.com> |
| In reply to | #32250 |
> >>> OK, cool. Recovering would be faster and nicer since we don't have
> >>> to reconfigure. I was surprised TM's restore was after a three
> >>> hours restore on Saturday. :)
> >> I will point out that simply restoring from a Time Machine will not
> >> install a recovery partition on the replacement disk. That only
> >> takes place when one first installs the operating system.
> > Interesting. How do you put a recovery partition back then onto a
> > new disk? I am surprised it doesn't do that.
> Time Machine does not backup the recovery partition. How could it
> restore what it hasn't backed up?
I was expecting it would back that partition up too beside Mac OS X
partition.
> While it's possible to restore a full disk clone, including all
> partitions, it doesn't sound like there's a disk from which such a
> clone can be made. It's been reformatted at least once. Additionally,
> this may not have been possible, if the disk was damaged in the drop.
Interesting. I used Windows cloning softwares (e.g., Ghost) that can do
the whole disks, partitions, etc.
> >> I'd highly recommend running the installer, after which you can
> >> restore from your backup or perform a system migration from the
> >> Time Machine backup.
> >> I'd also ask, why isn't your account planning on updating to a
> >> newer version of the operating system, while going to all the
> >> trouble to upgrade the boot disk? It would seem the timing is
> >> right.
> > Doesn't he have to buy it?
> I believe all that's required is a download from the App Store. Both
> Mavericks and Yosemite were released without charge. I fully expect
> that El Capitan will be the same. This should be true for any
> supported Mac with App Store, including late versions of OS X 10.6.
Does that have to be on the same machine or can it be done on a
different machine?
> >> Also note, there remains a somewhat significant chance that it may
> >> not be a disk issue at all. A trip to the Genius Bar is still well
> >> worth considering.
> > Yeah, I am trying to convince him.
> Would you like to borrow my clue-by-four?
YES please!
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | David Ritz <dritz@mindspring.com> |
|---|---|
| Date | 2015-09-30 01:50 -0500 |
| Message-ID | <alpine.OSX.2.20.1509300118030.734@mako.ath.cx> |
| In reply to | #32252 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message On Wednesday, 30 September 2015 00:43 -0500, in article <kK6dnYUjOvH165bLnZ2dnUU7-aWdnZ2d@earthlink.com>, Ant <ANTant@zimage.com> wrote: > David Ritz wrote: >> While it's possible to restore a full disk clone, including all >> partitions, it doesn't sound like there's a disk from which such a >> clone can be made. It's been reformatted at least once. >> Additionally, this may not have been possible, if the disk was >> damaged in the drop. > Interesting. I used Windows cloning softwares (e.g., Ghost) that can > do the whole disks, partitions, etc. One can do the same using Disk Utility, including producing block for block identical whole disk clones. To do such a whole disk clone requires booting to an external drive, perhaps even a USB flash drive with the utilities and installer on it. By booting to an external drive, nothing is active and live on any of the partitions to be cloned. >>>> I'd highly recommend running the installer, after which you can >>>> restore from your backup or perform a system migration from the >>>> Time Machine backup. >>>> I'd also ask, why isn't your account planning on updating to a >>>> newer version of the operating system, while going to all the >>>> trouble to upgrade the boot disk? It would seem the timing is >>>> right. >>> Doesn't he have to buy it? >> I believe all that's required is a download from the App Store. >> Both Mavericks and Yosemite were released without charge. I fully >> expect that El Capitan will be the same. This should be true for >> any supported Mac with App Store, including late versions of OS X >> 10.6. > Does that have to be on the same machine or can it be done on a > different machine? You may be able to download the installer once and copy it to other machines. You'll still be required to provide App Store credentials for the owner of the machine where the OS is being installed, when the installer runs. Do keep in mind: Running the Install OS X $NAME.app from /Applications will cause the app to be deleted, upon completion of the installation. It's not a bad idea to copy the installer somewhere outside of the Applications directory, for safekeeping. It beats the hell out of having to re-download the 5.6Gb file again, at some later date. -- David Ritz <dritz@mindspring.com> Be kind to animals; kiss a shark. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlYLhkwACgkQUrwpmRoS3uundACgyTkxw5R8AYV7LQs5maLn7K0n 0XgAn31ROhSIKp0EpntlwPqzApCFbR+f =PflX -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | ANTant@zimage.com (Ant) |
|---|---|
| Date | 2015-09-30 03:50 -0500 |
| Message-ID | <N-qdnRs2lP3wP5bLnZ2dnUU7-f2dnZ2d@earthlink.com> |
| In reply to | #32255 |
> >> While it's possible to restore a full disk clone, including all
> >> partitions, it doesn't sound like there's a disk from which such a
> >> clone can be made. It's been reformatted at least once.
> >> Additionally, this may not have been possible, if the disk was
> >> damaged in the drop.
> > Interesting. I used Windows cloning softwares (e.g., Ghost) that can
> > do the whole disks, partitions, etc.
> One can do the same using Disk Utility, including producing block for
> block identical whole disk clones. To do such a whole disk clone
> requires booting to an external drive, perhaps even a USB flash drive
> with the utilities and installer on it. By booting to an external
> drive, nothing is active and live on any of the partitions to be
> cloned.
Interesting. I should check that out.
> >>>> I'd highly recommend running the installer, after which you can
> >>>> restore from your backup or perform a system migration from the
> >>>> Time Machine backup.
> >>>> I'd also ask, why isn't your account planning on updating to a
> >>>> newer version of the operating system, while going to all the
> >>>> trouble to upgrade the boot disk? It would seem the timing is
> >>>> right.
> >>> Doesn't he have to buy it?
> >> I believe all that's required is a download from the App Store.
> >> Both Mavericks and Yosemite were released without charge. I fully
> >> expect that El Capitan will be the same. This should be true for
> >> any supported Mac with App Store, including late versions of OS X
> >> 10.6.
> > Does that have to be on the same machine or can it be done on a
> > different machine?
> You may be able to download the installer once and copy it to other
> machines. You'll still be required to provide App Store credentials
> for the owner of the machine where the OS is being installed, when
> the installer runs.
> Do keep in mind: Running the Install OS X $NAME.app from /Applications
> will cause the app to be deleted, upon completion of the installation.
> It's not a bad idea to copy the installer somewhere outside of the
> Applications directory, for safekeeping. It beats the hell out of
> having to re-download the 5.6Gb file again, at some later date.
Thanks. Yes, 5.6 GB is huge even on a fast Internet connection.
--
Quote of the Week: Allah's Apostle said, "Once while a prophet amongst
the prophets was taking a rest underneath a tree, an ant bit him. He,
therefore, ordered that his luggage be taken away from underneath that
tree and then ordered that the dwelling place of the ants should be set
on fire. Allah sent him a revelation: 'Wouldn't it have been sufficient
to burn a single ant (that bit you)?'" --Translation of Sahih Bukhari,
Book 54, Number 536
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.home.dhs.org (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / Please nuke ANT if replying by e-mail privately. If credit-
( ) ing, then please kindly use Ant nickname and AQFL URL/link.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2015-09-30 15:05 +0000 |
| Message-ID | <d72c16F193hU1@mid.individual.net> |
| In reply to | #32258 |
Ant <ANTant@zimage.com> wrote: > >> Do keep in mind: Running the Install OS X $NAME.app from /Applications >> will cause the app to be deleted, upon completion of the installation. >> It's not a bad idea to copy the installer somewhere outside of the >> Applications directory, for safekeeping. It beats the hell out of >> having to re-download the 5.6Gb file again, at some later date. > > Thanks. Yes, 5.6 GB is huge even on a fast Internet connection. Immediately after downloading the Yosemite installer from the App Store, if the installer launches, quit it. Then just right-click the installer, and choose Compress from the pop-up menu that appears. That will create a zipped copy of the installer that you can archive or transfer to other computers. That's what I do for all OS X installers I download from the App Store. ;) -- Sent from my iPhone
[toc] | [prev] | [next] | [standalone]
Page 4 of 6 — ← Prev page 1 2 3 [4] 5 6 Next page →
Back to top | Article view | comp.sys.mac.apps
csiph-web