Captain Mono

So I came back an hour ago after watching 5 minutes of the second Pirates of Caribbean, whatever it is called – Dead Man’s Chest? Yeah, whatever. I had been wanting to see it for a long time and considering that tomorrow will most likely be the last day it’s going to be in theatres here, I finally decided to go and watch it at this theatre near my hotel. So I quickly finished dinner – which wasn’t too bad btw, which is a rarity these days – and reached the theatre. Only the second time in my life was I planning to watch a movie “alone” – what’s the big deal with doing that anyways? I mean if you really want to watch the movie you shouldn’t really care who you’re with, right? I’m in for watching movies alone after being sceptical for the best part of my life. Anyways, I digress.

I reached the theatre, bought the ticket and entered the hall, you know the usual drill. At this point I would like to state for the record, my complete distaste for multiplexes with halls that are only slightly bigger than your living room (unless you live in Mumbai or New York of course, in which case any place is bigger than your living room). I mean this hall had only 52 seats (yes, I had time to count as I was waiting for the movie to begin) – 52 seats? Give me the single screen theatres over multiplexes any day. Call me old fashioned, but I like my movie screens big and the halls bigger. Call me old fashioned, but I’m not sure what I’m gaining with multiplexes – I pay more to watch the movie on a smaller screen with worse audio. And yes, being close to the screen is suddenly a good thing?!! WTF!

Talking about crappy audio brings us back to today’s movie. The previews start and there’s this constant hiss in the audio – never mind, I thought, it must be just the previews. Not the first time the stuff leading up to the movie is in stereo and the movie that follows is in Dolby or DSS or whatever the latest buzzword is. But of course this audio wasn’t even in stereo because the sound was coming from only one direction – right in front of me (where the screen is) – and I could just about make out what they were saying. Wait a minute, is this MONO? No way, I thought to myself. That’s not possible. Ah, the previews are over, the movie begins, surely everything will be fine now. There’s the production house banner – OMG the hiss is still there! The movie starts and yes, it’s still there. I can just about make out what the actors are saying over that annoying hiss and I start to realize that the four speakers on the left and right walls are just for show – I wonder if they are just empty enclosures – not the best publicity for Bose I tell you.

I somehow sit through the first scene and just as Jack Sparrow, correction “Captain” Jack Sparrow, is about to make his first appearance on screen (or so I think, because I never made it that far) I decide enough is enough, I don’t need to put up with this. By the way talking about sadda Johnny Deep Singh an Edward “Scissorpaws” reference on Frasier as I type this – some coincidence, eh? I walk out of the hall and happen to catch the “projectionist” just as I am moving out. What the hell is the matter with the audio I ask him, what’s with that noise? He replies with the M word. “No problem, the audio is mono”. AARGH!!! How can you even utter those words with a straight face?!!!! He added we have a digital print (with great audio I presume) but this screen has only mono audio. That would explain all the noise because to make an audio signal distributed over 5 channels audible with only one, you would have to make it exceptionally loud, bringing in all the noise. Well, that is putting it in simple terms – which is the best I can do.

Anyways, atleast the guy was understanding when I said mono sound is unacceptable to me and he took me straight to the manager/ owner who gave me a refund, no further questions asked. I didn’t expect them to be this “co-operative” to be honest, which is why I even considered sitting through the movie – but 23 seconds after the thought entered my head, I realized I just couldn’t do it – refund or no refund. I don’t know how the other half-a-dozen people watching the movie could put up with that crap! This multiplex has 3 screens, so I naturally asked if the other two had mono sound as well. Thankfully, the answer was no. Ah, great. So I pay 25% more than the guys in the other theaters (because English movie tickets are more expensive than Hindi movies which were playing on the other two screens – go figure) and I’m the one who gets mono audio! Ain’t life grand?

Take my advice, if you are in Muscat and you see a movie playing at Al Nasr screen number 3, don’t bother.

How to force reinstall Java on Mac OS X

If you’ve managed to screw up your existing Java installation on Mac OS X, or you’re looking to downgrade for reason(s) best know to you, here’s a nice and easy way of preventing Mac OS X from telling you it knows best ((The “installer cannot run on this machine because it does not have…” messages)).

Note: This method does not require Pacifist and/ or modification of the installation package in any other way.

Disclaimer: This works on Mac OS X 10.3.9. It may or may not work on Tiger. It may or may not blow up your computer. You run it at your own risk.

And finally, the method:
Step 1 (aka Duh!)
Download the version you need to install on your machine from Apple’s site.

Step 2 (aka My Lucky Day)
Run it and see if it lets you do the needful. If this step is successful, you shouldn’t have been reading this page in the first place. Thanks for wasting my bandwidth. If not, exit the installer and proceed.

Step 3 (aka The Good Stuff)
In Finder, go to folder /System/Library/Frameworks/JavaVM.framework/Resources and move the files “version.plist” and “Info-macos.plist” to a safe place like the Desktop. The moving process might prompt you for password and involve two separate transactions – copying files to the target location and then deleting them from the source.
Hope I have been successful in complicating a simple process.

Step 4 (aka Eureka)
Run the installer again and watch as it proceeds with installation. You didn’t think it would work, did you?

Step 5 (aka Double Check)
Open Terminal and type “java -version”. Is it what you just installed?

Step 6 (aka Optional)
If you answered yes to #5, it’s safe to delete the files you kept as backup. You may, however, want to keep them for reasons best known to you. Leave a comment, below, reassuring everyone that this method actually works.
If you answered no or if step 4 didn’t work for you and you are running Panther, leave a comment so I can take down this post/ blog. If you are running Tiger, please drop in a line to let all the regular readers of this blog (half a dozen Windows users) know that this technique won’t run on 10.4.

Note on disclaimer: In case you are wondering, I was kidding about the blowing up bit. This technique builds on the method described in an official Apple Technical Note. While the note says that removing one file would do just fine, my experiments showed you needed to remove both, especially if you are changing versions. Also, like I said above, you can install any version of Java intended for your OS, not just the one that came with your CD/ DVD like the note says.

Symptoms (aka when to use this method)
This method is known to fix the “Segmentation Fault” and “HotSpot not at correct virtual address. Sharing disabled.” states that some Java installations may find themselves in.