I recently acquired a new computer and have begun the “Migration” from old to new. I know it’s not a quick process (600+ Gb from machine to machine) but by my math this estimation, using FW800, was WAY OUT. The problem turns out that the computer was going to sleep during this migration!! Why the HELL would it do such a stupid thing? There were no options for sleeping as it’s a fresh install. Shame on Apple.
After three failed attempts, I had to find a solution to me sitting at two idle computers for 8 hours.
AND HERE IT IS!
(standby for video)
I needed to be able to leave it also… so in an audio Macgyver moment of desperation I turn to my biggest fan. The cable for the Trackball is moved by an oscillating fan. The headphones are on top of an upside down trackball, this and the duct tape give the trackball some weight to push on the keyboard (for computer 1) the movement also pushes a button on a Magic Trackpad (computer 1)
so far attempt number four is going smoothly (knock on wood)
as entertaining this MacGuyveresque post is Anthony You Could try terminal commands in the future to get rid of this irritating behavior
Instructions to disable Safe Sleep *
Using the Terminal program, run the following two commands:
$ sudo pmset -a hibernatemode 0
$ sudo nvram “use-nvramrc?”=false
To free up the hard disk space used by the sleep image file:
$ sudo rm /private/var/vm/sleepimage
To re-enable Safe Sleep
$ sudo pmset -a hibernatemode 3
$ sudo nvram “use-nvramrc?”=true
and yes this was pretty damn creative
HisLeft Hand liked this on Facebook.
Ian Bodzasi liked this on Facebook.
Thanks for that, but I refuse to use terminal. I didn’t invest in a powerhouse computer with an advanced and efficient GUI to be a programmer on the side.
I hate computers with a passion, I like working.
BESIDES my stubbornness: We’ve come far enough in computing not to have the most simple of logical processes solved only by what I’d like to call advanced programming.
$ sudo pmset -a hibernatemode 0
$ sudo nvram “use-nvramrc?”=false
should be at the FRONT of any installation process… irritating behavior of programmers is what’s lead to problem in the first place
I’m happy to say… it worked!
but I’d still like to smash it!