Doing some web development, using Chrome’s Developer Tools & got the javascript console open. Every time an HTTP GET fires sync or async, I get 4 lines in the console from “tswebclient.js” spamming my console.

This comes from the TrueSuite software that runs my Eikon USB fingerprint scanner on OS X (Mountain Lion). Disabling the Chrome extension keeps my console nice & clean for my *own* debug messages.

Changing Magnet URIs in Google Chrome

At one point, I clicked a link on the Skype website which started with “skype://…”. This is a magnet URL which will cause the appropriate application on your system to launch & handle the request.

Well, Chrome asked me what to do. Should I allow Skype to be launched & run off to do as the website instructed (a possible security risk)? Or should I “Do Nothing”? I accidentally clicked “Do Nothing”.

Now… what that did was seemingly permanently disable my ability to use the Skype-specific magnet URI.

To re-enable this function, I found that inside:
/Users/[username]/Library/Application Support/Google/Chrome/
… is a file named “Local State”.

Inside there, I found a key “protocol_handler” with a hash table, and inside that was:
“excluded_schemes”: {…, “skype”: true, … }

I changed that to “false”, shut down & relaunched Chrome.

Boom. Works.

OS X 10.6 Terminal Crash on Launch

Boss at work reports Terminal.app is crashing upon launch. He can’t use the email batch exporter I wrote; this is chapping his ass.

I launch it from his Dock… crash log reports BAD_ACCESS_something-or-other. No help there.
I try trashing his terminal preferences; no dice.
I downloaded iTerm2, as suggested by Adam, and bring that up on his Mac. It works.

So without thinking, I type: open /Applications/Terminal.app [Enter] into iTerm2, and it crashes as it has been.

Wait a minute.

open /Applications/Utilities/Terminal.app [Enter] … Success.

Somehow, Terminal.app got copied into /Applications (mistakenly), and that’s what his Dock shortcut was calling. Kill that copy, kill the shortcut, drag to Dock from /Applications/Utilities, and all is well.

I have no idea why having the app exist in a different place would cause this behavior… some mysterious callback shit, no doubt.

AFP Weirdness Appears to be Perms Mystery

Problem: User connects his Mac (running Snow Leopard 10.6.x) to Apple Xserve (running OS X Server 10.6.x) over AFP, authenticates successfully, yet cannot view contents of a particular folder.

Investigation: SSH into Xserve, verify permissions of folder, its contents and its parents, ownerships, group memberships, etc. Everything appears to be in order. What could be the problem?

Solution: Remove trailing space in folder name. Instead of “Software_DD-MM-YYYY”, creator of folder has named it “Software_DD-MM-YYYY ” with a space character at the end. Removal of space at the end = contents viewable.

Stupid computers.

OS X (Snow Leopard) Terminal Wish-List

Answers may exist for these questions, but I don’t know them.

I wish I did, and my google-fu is weak.

1. How can I get Terminal.app to preserve the highlighted state of previously-selected text when I paste into that window? E.g., I often need to copy & paste the same “put” command in an sftp session. In Tiger’s (10.4.x) Terminal.app, I could simply click once on the appropriate Terminal window, the text would remain highlighted, copy, paste & be on my way. Since the upgrade to 10.6.x, however, the paste action causes the previously-dragged text selection highlight to disappear; after pasting, nothing is selected. Now I must re-drag to select, copy and paste every time.

2. Why doesn’t the up arrow work in sftp? On the command line and in an ssh session, you can press the up arrow to scroll through the list of previously-issued commands. Not so in the sftp client on OS X. Why not? Is there something I can configure on the client or server side to make this work properly?

I tried using iTerm instead of Terminal.app. Text remains highlighted after pasting, but iTerm doesn’t highlight or select end-of-line characters. I have to press the return key manually each time to enter the command. And the up arrow doesn’t work either. X11’s xterm is a piece of shit.

So what fixes or options exist to circumvent this behavior?

Apple Snow Leopard Info

Notes for my own future reference:

After upgrading to 10.6.x (and running all available software updates), if someone cannot connect to a previously-available SaMBa share over the network:

killall -9 NetAuthAgent

… and try again. Worked for Nate’s machine.

Note also that Migration Assistant worked over the network for the very first time today. I had 2 MacBooks (1 aluminum with no Firewire, and 1 new Pro unibody) hanging off an isolated gigabit switch. The new one complained about lost network connectivity once; I suggest disabling screensaver & sleeping before doing this again in the future.

Everything seems fine until/unless I hear otherwise.

Added 2/8/10: Dunno if it’s related to Snow Leopard (what OS X version is Jim running?), but a failed firmware update could very well fuck up an otherwise problem-free MacBook Pro. Apple has a Firmware Restoration process involving burning a CD.

FrameMaker on Mac: Pay Attention, Adobe!

About a year ago, I ranted about Adobe having abandoned the Mac platform for their FrameMaker product. In that post, I quoted then-product-manager Aseem Dokania thusly:

…I believe there are some good workarounds available now for using windows applications on Mac. It may be possible to use one of them for FrameMaker.

Under the realistic threat that (code-named) Mandar Warrior Princess’ G5 iMac may die in the near future, I decided to give it a shot. It’s a number of years later, and technology actually makes it pretty easy to do what Aseem said on your Intel-based Mac. I still think he’s an asshole, though.

If you run 10.5.x (Leopard) on your Mac, you have the Boot Camp option, but you can only run Windows or OS X at one time. You have to reboot the machine to switch.

So for late-comers like me who still run 10.4.x (Tiger), and those who wish to run both operating systems concurrently, you have to install VMware or Parallels. These allow you to run a virtual machine on your Mac; essentially, Windows appears to run as an “application” on the Mac in its own… ahem… window.

Next, you install a version of Windows on the virtual machine. Finally, you install FrameMaker 9 for Windows, and you’re off!

None of it is very elegant (vis-à-vis having a Mac-native version), but it will work.

Mac users are screwed either way, though.

Adobe no longer makes FrameMaker for Mac; therefore your upgrade eligibility is nil, as they require upgrades be for the same platform. That juicy $399 upgrade price tag is there just to mock you.

So, how much will it really cost?

VMware and Parallels each retail for about $80. You can pick up a version of Windows XP 2002 (w/o service packs) on Amazon for $119. The full version of FrameMaker 9 for Windows is $999.

Total: $1,198.00

So here’s what I propose, Adobe.

Offer a “Mac Upgrade” option to customers like me who undoubtedly continue to faithfully shell out cash for Photoshop & Illustrator upgrades. Offer FrameMaker 9 for $800 to those with valid Mac FM serial numbers, thus subsidizing the purchase of the extra software required to make it work on my Mac.

I submitted this to Adobe via their website, but will likely not hear from them.

It’s too bad, though. It’s exactly this type of consideration that would make me (and many other Mac users) think, “okay, at least they’re trying not to be complete assholes about this,” and pay the $800.