// do something here

I have really been liking a couple of freeware iPhone, iPod touch, iPad, and iOS Simulator tools that I found. They both run great on my iMac, and are super simple to use, while providing some great missing functionality that the Xcode tools do not have.

The first is iExplorer from Macroplant, which allows you to spelunk through the file system of a device connected to your system. It works with stock devices as well as jailbroken devices. Here is the link to download this application:

iExplorer

The other tool is iOS-Simulator Cropper from Curious Times. This tool take screen shots from the iOS Simulator and, shockingly enough, automatically crops them down so that you can use them in your marketing materials or for uploading to the App Store. Here is the link to download this application:

iOS-Simulator Cropper

EDIT: I changed the link to iExplorer (the application formerly known as iPhone Explorer), so the link above should not be broken any more.

This is not so much a development issue as just a general usability issue, but it had frustrated me for a while and I am glad I got the issue behind me.

The problem was that my Garage Band v6 (2011 version) had some problems with the loops. When I would fire up the program, some of the loops in the loop browser showed up sort of grayed out with an arrow next to them. When I click on one of the grayed arrowed loops, I would get a message about how I needed to use Software Update to download the loops onto my computer. However, when I would go to Software Update, it would insist that there were no updates available. Also, when I went back into Garage Band to do the same thing again, it would respond with this message:

You have already initiated the installation of additional content for GarageBand via Software Update. For additional information please open the ‘Software Update’ application.

The battle of wits has begun.

Finally after trying to uninstall and reinstall a couple of times, and after looking through umpteen dozen posts on how this fixed it or that fixed it, I came upon this post on Apple’s web site:

Update the loop library (this link is dead as of 2/23/2012)

Finally I have slain the ROUS that was my loop browser issue.

EDIT:

The link above appears to be dead as of February 23, 2012, a quick Google search for “update the loop library” with specifying the site of apple.com yielded this link on Apple’s web site:

Update the loop library

I do not recall the exact contents of the now dead link, but from what I remember, I think that link and this one recommended very similar steps of actions.

I have to hand it to Apple, they really did a nice job with the Mac OS X Migration Assistant.

I decided that my battle tested MacBook Pro has had enough after 3 years of torture, and so I ambled down to the local Micro Center to pick up a shiny new 21.5″ iMac. Being the lazy developer type that I am, I decided to try and look into using the Migration Assistant so that I would not have to take out an external hard drive or USB memory stick to manually move lots of files from the old MacBook to the iMac.

The first attempt to use Migration Assistant did not go as smoothly as I had hoped. Since both machines were on the same wireless router, I first tried to use the wireless option for communications in the Migration Assistant. Bad move, the time for completion was fluctuating between 20 to 24 hours.

And of course, as I started to look at using Firewire, I discovered that the iMac has a Firewire 800 port, while the 2008 MacBook Pro has a Firewire 400 port. Back to the venerable Micro Center for a supporting cable.

Once I set up the Migration Assistant to run over Firewire, the estimated completion time never went over 50 minutes or so. I went downstairs to watch a bit of TV, and when I came back up a couple hours later, it was finished.

So I rebooted the iMac, and lo and behold, all of my stuffs from the MacBook Pro were on the iMac. Genius! (Bar???)

OK, now to the rant part of this post. That would be the “Rawhide in A” comment you see in this post’s title.

To my Yahoo e-mail address comes this message from some kind of guitar web site. In it, they have some news story on their web site that describes the top 20 movie scenes featuring guitar playing. I can’t pass that up, since I really like movies and I really, really like guitars.

In at number 3 on the list is the Bob’s Country Bunker scene from “The Blues Brothers”, and since I am pretty sure that it is a law in the United States that you have to watch any Good Ole Boys or Bob’s Country Bunker scene whenever the chance is presented to you, I click the YouTube link for the scene and start watching the 2 minute clip.

About 10 seconds into the clip, I do a bit of a double take. My wife and I both are big fans of the Leinenkugel Brewery in Chippewa Falls, Wisconsin, and so I am watching this clip, and I swear that I see the pretty unmistakable script Leinenkugel’s logo in the movie. Take a look at this screen capture 14 seconds in to the clip:

And I think that is very strange, since I never noticed it before, and I am the kind of person that notices things like that.

So I fire up the 25th Anniversary DVD of “The Blues Brothers”, and at about 1:21:02 into the extended version of the movie (side A), I see the following image:

Does anyone have any idea why my supposedly better widescreen edition of the movie does not have something that was in either a broadcast or pan-and-scan version of the movie??? It looks to me like for this scene, they just took the 4×3 image and chopped the top and bottom parts off to make it look widescreen, if this is the case that is disappointing. (I am not sure what to make of the IMDb technical specifications page for the movie, it lists both 1.33 and 1.85 ratios.)

BTW, happy belated 80th birthday to Leonard Nimoy. I used to be a huge Trek fan, but even I had no idea that William Shatner and Leonard Nimoy were born just 4 days apart of each other back on 1931. Fascinating…

I just got the inspiration to add the following line of code to the app delegate header of my latest iPhone application:

#define  VERY_YES  YES

If you are wondering about the etymology of this, please check out the following informational message:

Where does the term “very yes” originate from?

I leave it to the imagination and creativity of my fellow developers to adapt this code to run in other flavors of C.  Please make sure to credit me if you decide to use it.

If you are using Xcode for either Macintosh or iPhone development, please go to one of your implementation files in Xcode right now, hold down Control and Command and press the up arrow. Your life will be much better.

I was having some issues with the Windows XP installation in Boot Camp on my MacBook Pro, so I decided to turn it into a Windows 7 machine.

Unfortunately, the machine ended up running incredibly hot, even though I was booting it up and not really doing anything processing intensive on the machine.

As it turns out, I found that other users had some luck by enabling the Powermizer mode of their Nvidia GeForce 8600M GT internal graphics card. This would scale back the GPU processing and allow the idle fan speed of about 2000 RPM to properly cool the MacBook Pro.

As is the case with any registry hacks, edits or low level driver manipulation, you can quite easily do more harm than good. Please follow my advice at your own risk.

Alas, there is no setting that I could find for this in the newest 64-bit Windows drivers for the Nvidia GeForce 8600M GT internal graphics card in my MacBook Pro.  After a little digging, I found that I could add the following DWORD values to my registry to enable a lower power mode:

• PerfLevelSvc (0×00003333)
• PowerMizerEnable (0×00000001)
• PowerMizerLevel (0×00000001)
• PowerMizerLevelAC (0×00000001)

The key that these values were added to was HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{FIND_YOUR_GUID}\0000. You will have to find the GUID to use in the key above, just look at all of the 0000 keys inside of the Video key for the one that has a whole mess of values in the right hand pane, this will likely be it.