[OT] Mac Beach Ball Party (or welcome to hell, here's your mac)
stephenREVOLUTION2 at barncard.com
Fri May 11 17:12:56 EDT 2012
thanks Scott. I'll do that,
I'm really not happy to completely reinstall here, I don't think that will
fix things permanently.
I gave a call to my favorite RAM company RAMJET, and their memory expert
told me that the Mac Pro on Lion REALLY needs more than the 6 stock gigs
installed (!) and suggested I get a 3-stick upgrade of 4 gb modules to get
up to 15 gigs, so I ordered them and we'll see how that works out. I will
never fully understand memory math and why these have to work in threes -
(is it the 64 bits?) -- currently there are 6 1 gig sticks, with two open
slots. I will lose one of the 1 gig sticks, so the total goes to 15g.
William Gibson had no idea about how astronomical ram size would go. None
of us did.
I will report back
On Fri, May 11, 2012 at 1:51 PM, Scott Rossi <scott at tactilemedia.com> wrote:
> This probably has nothing to do with anything you've mentioned, but during
> recent "Let's figure out what Apple changed and turn it off" session I
> recently went though, we found that file locking is enabled via Time
> settings, and disabling the setting there supposedly prevents files from
> being auto-locked in the Finder (and thus unable to be overwritten).
> Just throwing it out there...
> Scott Rossi
> Creative Director
> Tactile Media, UX Design
> Recently, Jacque Landman Gay wrote:
> > On 5/11/12 2:00 PM, stephen barncard wrote:
> >> My lovely Mac pro is in hell. Yes I have a lot of apps, and yes I am
> >> running Lion.
> >> And that doesn't help either as it insists on loading every app and
> >> document I had running the last time*.
> > System prefs -> General -> Restore windows when quitting and re-opening
> > apps [turn this off]
> > I never turn off my Mac so I'm not sure if that also works on a restart
> > but if you haven't unchecked it, it's worth trying. Or just leave your
> > Mac on all the time, it's meant to be used that way. I only restart
> > after a system update.
> > What I hate even more than that, and for which there is NO solution, is
> > the auto-save that wrecks whatever I'm working on as soon as I make any
> > temporary change. Whoever made *that* decision is the one I'd like to
> > track down and torture. There isn't even a Terminal command to get rid
> > of it. I don't want every single tentative edit to be saved, I want to
> > decide what's temporary and what should be overwritten. I lost work
> > yesterday because of this stupid, idiotic behavior and had to go digging
> > through the Star Wars interface to get back the original, which was
> > difficult because they ALL LOOK ALIKE if the document is more than one
> > page long. Don't get me started.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
San Francisco Ca. USA
more about sqb <http://www.google.com/profiles/sbarncar>
More information about the use-livecode