Jump to content
  • entries
  • comments
  • views

mini upgraded to Mavericks



My mini's been prompting me about the new OS X upgrade to Mavericks. I finally got around to checking with Elgato to see if EyeTV had any known problems with it. Only issue they've found is with a multi-monitor setup, something I don't have to worry about for my TV. So I went ahead with the upgrade.


The download took almost an hour, so I made sure to copy the installer before running it. I did this as the installer will delete itself after it finishes, presumably to free up the 5.31 GB of space it takes, and I didn't want to have to download it again when I get around to upgrading my MacBook Pro. I'm holding off on that as I've less than a week to go to finish Stay Frosty 2 and I don't wish to risk any problems with my development setup at this time. I had a situation after one OS X upgrade where Parallels wasn't happy - and Parallels is critical for Stay Frosty 2 as I use a Linux VM for the ARM compiler that's used for Harmony/Melody development.


The upgrade didn't have any issues, though I did have a minor panic when it rebooted and switched to 1080p (which my TV doesn't support) and I couldn't remote into it from my MacBook Pro. I dug out my extra monitor and plugged it in and discovered it was still installing the update, which is why the screen sharing service wasn't active yet.



Once it was done my settings were restored and the mini correctly switched back to 1080i when I plugged it into the TV. I watched a few recordings and everything seems to be fine.


Recommended Comments

"I had a situation after one OS X upgrade where Parallels wasn't happy - and Parallels is critical for Stay Frosty 2 as I use a Linux VM for the ARM compiler that's used for Harmony/Melody development."


Yikes -- that would drive me nuts. Surely there has to be an ARM compiler that would work for Harmony/Melody that runs under OS X, right?


If I ever get a chance to do some more 2600 hacking, I'll probably see what can be done about that. I can't stand having to flip between OSes, especially for something that should be able to work.

Link to comment

I used to use GCC-3.3 Toolchain OS X, but they stopped creating the Mac builds after that version.


I switched to Sourcery CodeBench Lite Edition as it optimized the code better (smaller binary so more space left for other things).


Switching to Linux under Parallels works extremely well. All the source code is on my Mac's hard drive. I even edit the C files using X Code. The Linux VM is set up so it has directly access the source code directory on my Mac, so there's no hassle with copying files back and forth. As soon as I save from X Code the ARM compiler under Linux sees the changes. As soon as I compile the C files under Linux, dasm on the Mac can merge the results into the 2600 BIN file.

Link to comment

I've told my wife we'll upgrade her MacBook to Mavericks after the first patch. (i.e. next month)


I'm waiting for the rumored Hawsell upgrade for the Mini before I pull the trigger to get one (and the 27" monitor) for my "home computer". The iMacs were upgraded outside of the big event, but the rumor sites don't have any new news.

Link to comment

I'm looking forward to the memory compression. I don't need it for the mini, but my (late 2008) MacBook Pro is maxed out with 8GB of RAM and I occasionally exceed that.


With the iPad I decided I don't need a laptop anymore, so I'm planning to replace my MacBook Pro in a few months. I'm tempted by the new Mac Pro, though may end up with next update to the mini. I'll be making that decision in January/February.

Link to comment

I'm avoiding Mavericks at home for the time being. I'm running older versions of some Adobe apps which reportedly have compatibility issues, and I don't want to upgrade them (not because I'm a luddite, but because I'm cheap, plus the newer versions of Illustrator break FreeHand importing).


We'll be getting some Mac Pros at work as soon as they ship, and we'll start beating them up pretty good in the spring in anticipation of rolling them out over the summer. There are some known incompatibilities there (Media Composer, ProTools among them), so we can't deploy them yet as full production machines, but we can still give them a pretty good thrashing. The bigger issue is how do we secure them in a lab environment? I've seen no evidence of any Kensington slot, and even our Apple rep doesn't know yet. Hopefully, there will be an elegant third-party option that doesn't include superglue or drilling.


I suspect a Mac Mini update will be happening soon. They're due. The question is, when will Apple have sufficient supplies to meet laptop demand? They likely won't update the Mini until then.

Link to comment
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...