Apple’s OS X 10.8.4 to deliver WiFi compatibility, FaceTime fix, 802.11ac, and more

FairerPlatform reports, “To paraphrase Harry Truman, ‘The only thing new in the world are the Apple secrets you do not know.’ Well, here is a small dent in that deficit courtesy of the publicly knowable sources about what’s inside OS X 10.8.4 12E55.”

From Apple’s notes as per MacRumors:

The 10.8.4 update is recommended for all OS X Mountain Lion users and has features and fixes that improve the stability, compatibility, and security of your Mac, including the following:

• Compatibility improvements when connecting to certain enterprise Wi-Fi networks
• Microsoft Exchange compatibility improvements in Calendar
• A fix for an issue that prevented FaceTime calls to non-U.S. phone numbers
• A fix for an issue that may prevent scheduled sleep after using Boot Camp
• Improved VoiceOver compatibility with text in PDF documents
• Includes Safari 6.0.5

“Known scuttlebutt also includes the existence of 802.11ac (a.k.a. gigabit wifi) references in OS X 10.8.4,” FairerPlatform reports.

Full article here.

95 Comments

  1. No mention of slow-as-molasses initial Time Machine backups over certain network interfaces / locations. Guess we get to deal with this a while longer. : (

  2. I can mention that one ongoing battle is also being addressed in 10.8.4, that being the dire problem of Safari devouring all the RAM available then forcing itself, if not the entire OS X system into Sit&Spin mode. This is the #1 reason to loathe Safari. So far, I have been unable to repeat this bug in Safari 6.0.5. Therefore I can cautiously call out an enthusiastic HURRAH.

      1. Chromium does not have this problem- even with extensions installed despite both being WebKit browsers. Apple software has become the home of the eternal beta.
        I do not know if Dave Hyatt is still in charge of Safari development, but someone needs a swift kick in the arse over Safari instability.

          1. KDE developed Webkit’s base- Apple added to it and released it as webkit.
            I do not hate Safari, I just wish it were stable. If Google can make Chromium stable (I do not use Chrome as it is laced with Google phone home features) Apple should be able to make Safari stable again.

        1. If not – he has battles with multiple browsers (installed in his machine) which feed off similar System & Library services that are getting tangled. Furthermore, I can almost guarantee he did not do a clean install, but a patch.

          Solution is, remove the competing browsers and strictly use Safari. But of course he loathes the Best Browser on the planet. “Son son choix.”

        1. Both situations are what exactly? 10.8.3 / 10.8.4?

          Obvious to you is a very vague description, though some seem to experience what you have.

          I can vow, that not once, on over 200 machines, running 10.8.3 with 70% of those machines running 4 Gb of ram, machines which are on and using Safari for nearly 24 hrs a day since 10.8.3 was provide… have ever once SIT&SPUN and brought the system down. Not one. And not mine machine at home either. Yet, I don’t fart around with the competitors browsers either.

          Can not wait, until 10.8.4 arrives for public upgrade and Safari is included. The update should state the ratification that the nasty bug (a horrid memory leak in Safari experienced by few) has been finally eliminated… and perhaps a kind thanks from Apple – a special note to Mr. Derek Currie for his valiant work on Beta Testing Safari.

            1. you come to offer help ?
              yet all you mention is the next safari is lacking the bug
              that you’ve been yapping to apple over a year about
              you wish to be worshipped and congratulated
              what help did that do to earn this praise
              stating the obvious to you as others the big can’t be recreated
              theres no bug you just over exceeded your ram limits
              and your web devs are all a mess due to third party crap
              others haven’t got their hands on the os
              yet you continue telling others they are useless users
              not a power user like yourself so obtaining a beta makes you god you are a pompous arse boastful and purposely pressing buttons to those you feel are below you
              no one appreciates it it doesn’t help

            2. My goodness what a stupid thread. Folks, go have fun with Safari and STFU if you DON’T like beta testers or beta testing. I have no use for any of this blether garbage being spewed here. But you can thank ME for giving my time freely to help IMPROVE Apple software. If you don’t want to thank me, fine. But do please STFU anyway, lazy selfish bums.

    1. Safari had been a failure. I’d like to go back some day when the sit and spin is fixed. Mine loads a one inch progress blue line and sits there. I’ve been using Firefox for years due to this.

      1. 1) Reset Safari – place checkmark on all options – hit ok
        2) Preferences – Security – uncheck internet plug-in, so it doesn’t allow java
        3) Preferences – Privacy – press – remove all website Data
        4) Preferences – Extensions – turn off
        5) closes Preference window
        6) Quit Safari
        7) Restart your Mac
        8) enjoy Safari again

        9) if you have Adobe Flash – think about uninstalling it

        1. Sorry, FireFox is funded by Microsoft.
          I try hard to make sure, that nothing that company has there hands in, gets installed on my machine.

          10) uninstall FireFox with “AppCleaner” or “TrashMe”
          11) do a Secure Empty Trash
          12) Restart your Mac
          13) Enjoy Safari once again.

            1. Derek, there is the Mozilla Foundation and the Mozilla Corporation.

              And though, I may not be fully correct, specially in terms of what percentage funding comes from, I am still correct. Microsoft provides the facilities still to this day for the Mozilla engineers to work out of in Redmond.

              So, I think your accusation of me tripping and me being a troll – makes you wrong once again.

              “The Mozilla Corporation is a tax-paying entity, which gives it much greater freedom in the revenue and business activities it can pursue. The majority of the revenues comes from Google Inc., which is the default search engine on Mozilla Firefox.” – wiki

              “Contractual arrangements with companies like Google and Nokia are also accepted, but due to the strict rules governing the non-profit status of the Foundation, such things are taken care of by the Mozilla Corporation.”

              Foundation also accepts, sometimes quite substantial, donations from companies such as AOL and Google and many others. The Foundation uses a slice of this income to fund enterprises in keeping with the aims of the organization. In 2007, the Foundation made grants to the University of Toronto Adaptive Technology Resource Center, The Perl Foundation, Creative Commons and the GNOME Foundation to name but a few.” — technobuffalo

              August 24, 2006 5:05 PM PDT
              Microsoft offers helping hand to Firefox

              http://news.cnet.com/Microsoft-offers-helping-hand-to-Firefox/2100-1032_3-6109455.html?

              “In August 2006, Microsoft posted a letter on Mozilla newsgroups and offered to open up a new open-source facility at its headquarters in Redmond, Wash., to Mozilla software engineers. Mozilla responded by accepting the offer.”

              “Microsoft’s offer to help came on Saturday when Sam Ramji, director of the company’s open-source lab, posted an open letter on a blog used by Mozilla developers. Microsoft offered to open up a new open-source facility at its headquarters in Redmond, Wash., to Mozilla software engineers, including giving them one-on-one time with Microsoft workers. The offer includes help with Mozilla’s Thunderbird e-mail client.”

        2. I use Safari for personal stuff, Firefox for work stuff (just to keep a firm line drawn), and FF is the #1 reason my machine gets slow. Usually because its hogging CPU (presumably a thread gone astray), but sometimes because its using several GB of RAM, forcing lots of page-swapping. I’ve been debating switching to Safari-only, separation be damned.

          Is it a coincidence that “open source” rhymes with “open sores”? I’ve always found the former to be painful….thankfully never had the latter.

          1. Open source has benefits! 😀 Open source has deficits. 😥

            I’ve been sort of involved with the Gnu Privacy Guard project on the side lines and it has been interesting to watch. GPG provides some wonderful security capabilities to OS X for free that would not exist without it. You’d think Apple would notice and work with them in a symbiotic manner. But that’s not the case. So GPG gets broken A LOT because Apple changes OS X over time, forcing the kind and devoted GPG writers to catch up and compensate, which takes A LOT of time and patience, all given freely. As a GPG user, that gets very frustrating. On the other hand, it’s pointless to complain, knowing all of the above. Therefore, instead I like to cheer them on and write up happy, smiley, shiny reviews of GPG on occasion, as I did last week at my Mac-Security blog, accessible by clicking on my avatar. 😉

            1. You use FireFox Derek.
              The memory leak claim to Safari is believed to actually being caused by your Firefox.

              Give Safari a fair shake by doing a clean install of OSX 10.8.3 and avoid installing FireFox.
              Then enjoy Safari once again.

              It is you who start the insults believing your sarcastic remarks somehow is a positive influence.

              No worries here if you wish to continue the thread or not. There are others who may read.

              – until next thread, Derek

            2. I am always in play mode; acting with in character. I take nothing too seriously. Specially here. Comments, opinions, sarcasm, nasty words… if that is where you fall – all others win.

              Again Derek – you are an intelligent guy, yet you use your super hero powers for the underground. Still, I encourage you to keep on computing happily as a Mac enthusiast.

              And thanks for nailing those Safari bugs, Apple is better off you came to their aid.

      2. Maybe you need to upgrade from that G3 iMac then. I’ve never had that issue with Safari. As a matter of fact it works better than Firefox, Chrome or Opera for me.

        1. So you assume they’re not a power user because they don’t have issues with Safari? I’m more inclined to think you aren’t the power user if you can’t get the most out of your set-up.

          1. Yes, I am assuming that and I also assume you’re writing this stuff just to get someone upset. FAIL. Sorry.

            Most problems with software these days are related to poor memory management. It’s inherent in the old coding languages we still use today. When C is abolished forever, I’ll take another look and see how we’re doing.

            1. Safari only allows Java. It contains NO Java. Safari is written in Objective C, not C++. This is, as I’ve stated several times, all about memory management. Go read about pointers, go read about buffer overflows, go read about the #1 cause of both security flaws and application stalling and application crashing: Bad memory management.

              Java: Has superior memory management at the core than any version of C. Go read about that as well. And go read about the fact that Oracle’s Java plugin is the problem with Java relative to Safari, which has nothing to do with Apple.

              What ignorant flamebait is next is line?

          1. Ignorant you clearly are.

            I come here to help people. But I do enjoy ripping trolls to shreds. How sad that you’re just another anonymous coward troll. That always stinks of severe insecurity problems as well as the whiff of being paid to hate. Whichever it is, you’re lost and require finding yourself. Get busy.

            1. why search, click and view your bs blog
              it lacks all integrity and appears highly unprofessional
              and as for help, you are joking right

        2. Shame shame.

          As I thought, you were not cleanly installing the system and safari on the many Macs you tested.

          If as mentioned, you have been cleanly installing OSX on an external drive in order to test Safari and consistently finding slow Safari results on ever machine you test. It comes to mind the apparently dead obvious issue is the portable Hard Drive you been testing with. Guessing s 4800 rpm (slow) and what a 500 Mb (small) HD. Also ported through what Firewire 400, 800 or USB – what’s the scenario? Nevertheless, booting from that on every Mac you try is silly.
          Please do it right.

          OSX loves using its Virtual Memory. It automatically allocates and adjusts on the fly, very much like Windows Vista handed memory.

          The RAM disk is not a fast alternative to real memory also. And doubling up on Apples own virtual memory management is just effecting slower results Derek. Plus dare I think finally that is why the system might have croaked in your tests. OSX is designed not to crash when applications do. It can still happen yet for other reasons.

          Oh and one last thing, if you are done with the thread, leave.

        1. I had expeienced something like what you described Derek; of spinning beach ball in Safari. However, never a memory leak or power suck from Safari. I have monitored my Mac well. I do not consider myself a power user… however I have a good understanding whats going on – on my machine.

          Typically, Safari eats about 80 to 95 Mb of real memory, and on the fly it will virtualize up to an additional 100 – 250 Mb more. Also, ranging in about the same measure 100 – 250 Mb of real memory is consumed by Safari Web Content. So Safari can use up to a quarter of a Gb, 500 Mb at times.

          Regarding CPU consumption; 0.2 % to 5.2%.
          Threads hit a high of 10 to 21.

          When I do beach ball, as it has happened, I do as mention. Purge the Cookie Data and Reset Safari. It seems to have positive effects. Annoying still though to have to do this.
          In my opinion, regarding my situation during beach ball city, my guess leads to the thinking it is my internet – and not Safari.

          Suggestion, under Network settings, press “Advance”.
          Under TCP/IP – press Renew DHCP Lease. (if pertains to your connection type)
          Under Hardware, try setting to configure to “Manually” and MTU to “Custom” then adjusting the range up to approximately 1500.
          If the problem persists, try dropping it close to 1280.
          Compare the two scenarios and select whats better.

          Other then that, sorry to say, my i7 iMac 10.8.3 has not seen actually as described. I have NEVER, seen “Safari, devouring all the RAM available then forcing itself, if not the entire OS X system into Sit&Spin mode” — but only Safari its self.

          1. We all live inside our inner worlds and attempt, with our meagre human minds, to make sense of it all. That we get it wrong on a regular basis is, sad to say, entirely normal.

            Thankfully, with time and experience we thrash through our inner jungle and get better glimpses of what’s out there in the real world. I’ve been bashing away at computers on a professional level since 1993, after having learned how to be scientific by way of three previous degrees. So I tend to be very strict and analytical about most things I state as fact. Just so you know.

            One way around the Safari-Ate-My-RAM! problem is to have lots and lots of RAM. That works! But if you like to elaborate upon OS X and have only, merely, a measly 3 or 4 GB of RAM, you’re hosed if you expect Safari to jump through hoops for you. And I do.

            Maybe some day soon I’ll get that 16 GB of RAM and won’t care any longer how poorly Safari manages its memory. Then I’ll let all the little peon regular users suffer with Sit&Spin while I laugh and laugh at them. On second thought NO. I think I’ll stay human and avoid becoming psychopathic. That will allow me to help others and solve problems in the outer world.

            Just talking to myself, no doubt… 😉

            1. My iMac i7 has 16 GB RAM and I have these memory issues frequently with Safari. I can’t figure it out. First Safari becomes slow, then, over time, it beach balls, then eventually begins locking up the whole system. It occurs eventually even after completely clean installs. I have installed Firefox when Safari is becoming slow and do not have these problems with FIrefox and find it operates as speedily as Safari did after the time consuming clean install. I prefer Safari when it works. I’m still not sure what is causing this because it comes on so slowly that I can’t tie it to a particular event or installation. It happened today, again, whole system this time. Frustrating.

            2. No. NO. NO!!!!!!

              I’ve been saving up to have 16 GB of RAM in my Mac Mini Server, and now you’re telling me IT WON’T HELP STOP SAFARI Sit&Spin?! I shall drink poison! ;cry;

              No really.

              Anyway, if my testing is correct, that problem is GONE in Safari v6.0.5. (I had a fun hammering session with it yesterday). If this proves to be true, you can send me wreaths of olive branches as well as accolades of frankincense and myrrh; Not that I did anything to fix it, except bitch about it. 😉

            3. “Not that I did anything to fix it, except bitch about it” – derek

              Because the ‘weenis’ doesn’t know if it is a BUG or not.

              Hey everyone 6.0.5 solved issues for everyone… upgrade when Apple offers it. Or buy 10.9 with the newer Safari 6.0.6. Dah. What amazing advise.

        2. Well, Safari 6.0.5 is still not available to me.
          And, I am guessing it comes with 10.8.4 – which I have no update offered officially here in Canada, either.

          I am not a beta tester, and for those who are, they really should have a few machines to tinker with. And clean install those test systems.

          1. My testing is always on dedicated testing volumes with nothing but clean installs. It’s very helpful for sorting out the third party software problems from Apple specific problems. I’ve been beta testing OS X for Apple, for free, for about a year now. I don’t think of it as masochism as I have a penchant for it. Somehow it’s a form of fun and interest for me. I always did like being extremely NOT like other people.

        3. Derek says, “This is the #1 reason to loathe Safari. So far, I have been unable to repeat this bug in Safari 6.0.5”.

          How exactly do you attempt to repeat a bug?
          Do you code or clean code for Safari?

          Of course, it is understood you have not seen the Memory Leak occur in 6.0.5. However, honestly, Safari 6.0.5 is not yet GM (gold master) nor ready for public update. Correct.

          1. Wow, you’re really dedicated to this subject and/or me. Kind of spooky. But let’s continue the show:

            I have done a lot of coding and even studied to become a software project director. However, it is clear that I am no master coder. Instead, I am strangely good and learning about, analyzing and predicting system behavior. Any kind of system! So that’s my perspective. I learn the ‘system’ of how Safari works then predict its behavior. When my expectations match factual results on various machines on various occasions, and those results prove to be a problem, I figure it’s worth reporting that problem to those who can affect change upon the system. I like doing that sort of thing.

            Apple has had me ranting at them for all of the past year about this problem with Safari. In version 6.0.4 they began to address the problem and it was noticable. However, I’ve been doing my best to overload 6.0.5 with cache and multiple pages at the same time and it has not yet going into Sit&Spin. Thus my ‘HURRAH’ somewhere back up this thread somewhere. Then I perform the same overload tests on Safari 6.0.4 and watch it grind that volume’s system to a Sit&Spin halt.

            There are lots of little tricks to clean out the crap that Safari has dumped into RAM, specifically its RAM ‘scratch space’. But no one should have to do any of them ever, obviously.

            1. Well Derek, I run Safari exclusively on 4 different machines within my family group and rarely have any problems with it. On each machine I normally would have four to five windows up with a total of 60 – 100 active tabs at any one time. I’m a reasonably heavy Safari user. Many times Safari, along with OSX would be up for months at a time before I may need to shut down for a problem or software update install. I have loads of third party apps on my machines as well and none of the machines have more than 8 gigs of RAM. Seems your problem is something other than just Safari. On one of my machines I recently solved a long running problem where the HDD seemed to run almost endlessly and slowed down the machine’s performance substantially. Seems it was some left-over Blackberry files which remained on the machine long after the BB software was uninstalled. Don’t just jump to the conclusion it must be Apple’s fault.

            2. From my testing, it is entirely Apple’s fault. I’m not interested in teaching how to perform beta testing. And I gave up long ago bothering to convince anyone to trust me. It’s a total waste of time.

              But this big voice out in the void helped Apple to STOP THE PROBLEM via Safari v6.0.5. At least that is my current conclusion from all the bashing I’ve thrown at Safari.

              So think about it. Safari v6.0.4 has this Sit&Spin, lock up Safari and the system problem. Safari 6.0.5 does not! That’s on the same hardware and system except for the progression to OS X 10.6.4. Get it yet?

              Subject concluded.

            3. In deed your subject has concluded.
              FUD on Safari by Derek Currie

              Happy Safari 6.0.5 has come to your rescue Derek. And offering the sign of relief to all in Apples next update. Also, I would like to thank all who experienced and shared similar cases that Derek has. It must have been difficult and annoying times. Though, He thinks its obvious – he never offered any numbers or data to exemplify his situation. Stating only it occurs repetitively on every machine he touches. Lets imagine, as he does, that all his ranting finally effected Apple to actually fix his problem and for everyone else. Keep up the great Beta Testing Derek and God Bless you.

    2. I don’t use many plugins and don’t experience this problem at all. You might want to test a virgin copy of Safari for comparison before laying blame. That said, if the plugin architecture is at fault, then that would be Safari’s problem anyway. 🙂

      1. I think I’ve been very clear about my testing situation. Please read what I wrote. I also just added my concluding words in reply to “.me”.

        I will say, however, that casually testing software versus rigorously testing software under controlled circumstances are two VASTLY different things. I started beta testing software, professionally, back in 1996 at Eastman Kodak. So…

        1. Uhmmmm speechless – doinks.

          “Apple has had me ranting at them for all of the past year about this problem with Safari. In version 6.0.4 they began to address the problem and it was noticeable.” – derek

          “I’ve been beta testing OS X for Apple, for free, for about a year now. I don’t think of it as masochism as I have a penchant for it.” – derek

          “’I’ve been saving up to have 16 GB of RAM in my Mac Mini Server, and now you’re telling me IT WON’T HELP STOP SAFARI Sit&Spin?” – derek

          A beta tester for about a year, who hasn’t even tested the addition of more ram? With access to more machines – have you never thought about trying it? It is your passion right?

          …and now you have been a Beta Tester for Kodak too. Wow – I am becoming so impressed with you – you’re my hero. ahhhhh

            1. As troll of trolls, its you whom made yourself in shackles to be heckled at. Once again, righteously boasting with articulated proudness that you had a profound effect on the next rendition of Safari.

  3. Yeah, but have they fixed the bloody annoying bug in Desktop & Screen Saver preferences? When you add a folder of Desktop pics, sometime in the future (very randomly) it will disappear leaving you with the default Desktop pic. :/

  4. Wow, lots of bitching about safari. I’m a Apple tech and my mother inlaw’s iMac (1st gen aluminum) just had a RAM failure so for the last 24 hours she has 1gig only with 10.8.3 running fine, well needs a restart every few hours or so to clear out the swap files but no spinning beach ball when surfing.

    I do get people form time to time saying safari is very slow and what not but I find these are the people who have been upgrading an old install from 10.2 or whatever. It seams to me that changes in webkit and the OS have almost dictated a clean install is in order. Just incase it helps anyone I throw it out there.

    1. great advise CanadianThomas
      as i said – please do a clean install for those having these spinning beach balls that kill the system – rare but few claim it happens – even to the best of us – but since Derek has 10.8.4 and 6.0.5 he should be happy – so put it on your Mac mini dude

  5. Nah. Darek is 100% right. Safari and particularly the safari web process suck down a ton of ram. The longer you leave it running and the more tabs it has the quicker it will suck down ram eventually the Mac slows to a crawl while it starts swapping to disk which not only slows hard drive based macs but also starts eating away at wear cycles on ssd based macs. Btw this has nothing to do with upgrading. All my installs of mountain lion are clean installs. Hopefully darek is right about apple finally addressing this. 10.9 is supposed to have a rewritten safari as well, so it might not be as implausible as it first might seem.

    1. well joe,

      i presently have 30 youtube pages opened, all playing different videos – yes with Flash latest back on my system just to try what has been claimed,

      another 20 pages of random news and interests – including MDN which i type now this message

      – i yes in an attempt to over load the Safari and bring down my system… power user weeeeeeeee – foolish user – abnormal

      my quad processor i7 with 4 Gb of stock Apple ram holds steady now for fifteen minutes

      Flash plug in is sucking 20% of my CPU and a whopping 345.8 Mb of real ram

      Safari its self is using 4% of my CPU and 234.8 Mb of real ram

      Safari Web Content using 7.4% of CPU and 296.3 Mb of real ram

      —–

      50 pages no freaking joke, 31.4% use of CPU, 876.9 Mb of ram for Safari – not quit 1/4 of my machine here…

      In addition, adobe illustrator, yahoo messenger and Activities Monitor are running too…

      I don’t typically open 50 websites at once, nor would i think the average user would… nevertheless I don’t see any issues. Its been now 1 hr. safari seems fine.

      just saying

      1. Just leave safari running for a week or two. You WILL have problems with that many tabs running. Since you are on a newer mac, you might even have an SSD, which obviously helps mitigate the problem, at least on the surface, since swapping to SSD is very fast. But obviously, the long term effect will be that the SSD drive will wear out faster. Safari has problems, I know Darek and I are not the only ones to have experienced it, and I do think flash contributes to the problem, although, I am pretty sure the safari web content process has eaten a ton of ram even with plugins turned off. I hope the next update to Mountain Lion fixes it, and if not, hopefully 10.9 does, because it really screws up the memory profile of my machines, and typically requires hours of swapping crap back into memory after killing safari.

        1. And nothing either on of you said refers to Apple VMM.
          Virtual Memory Management. Which would be the culprit here to both of your cases, nonetheless, I am confident to say, Apples VMM solution works extremely well on so many machines. And not just mine.

          Lastly, to run Safari in such extreme situations where memory sits at a constant over load – is just irresponsible beta testing. Apple loves to here those extreme cases, this filters out cap usages for the average user. Meaning, your situations are unimportant reports due to the foolish way you handle applications.

          Its as if testing for VM in Adobe Photoshop and allocating
          4 Tetra bytes to a scratch disc yet not having a device which honestly is available. Derek hasn’t got 16 Gb of real ram, though has several machines to test. Irresponsible. And pushing limits far too beyond average use.

          Reports of true Memory Leaks would be – not regaining -accessed blocks of memory after using a particular application under normal use.

          Oh god, Safari sucks, because I have pushed the limits of the accessible ram and beyond, as it can not obtain the virtual memory it wishes. Oh crap, I only got a 250 Gb hard drive – yeah – duh, sure its clean as a whistle but golly gee the new Safari wants at least 1.2 Gb and 600 Gb free on my hard drive to play with VM to boot the app. Irresponsible and foolish. Specially to call this a bug.

        2. A week or two in that state is not a normal condition or state to use any computer furthermore its irresponsible beta testing. Apple doesn’t wish to hear from BS testing such as that Joe. Apple wishes normal, happy medium and average use of the OS and typical conditions that are easily reproducible. Those cases are what Apple wishes to iron out – stock situations to cover the average use of the computer. Extremes are widely measured to establish limitations, not to iron what some think are BUGs. Talk about pure ignoramuses.

  6. OT Rant at the trolls: I have to state, on the record, that I’ve never read so much technological ignorance and troll baiting as is found in this thread. Please kiss my dainty posterior. Now back to technology news and commentary… 😛

    1. No, better you remain a psychopath.
      By not checked things with physical ram allocated to 16 Mb puts you in poor light; looking foolish and amateurish as a beta tester. Furthermore, to use the old trick of a “scratch disc” which Apple Virtual Memory already does, just places you lower on the credibility scale.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.