Showing posts with label Apple. Show all posts
Showing posts with label Apple. Show all posts

Tuesday, January 8, 2019

Merry Christmas: Apple Macintosh SE

Christmas, 2018.
My brother has given to me a circa-1989/1990 Apple Macintosh SE HDFD. It's in a "carrying" case, includes an external 800K floppy drive, Apple Desktop Bus keyboard and mouse, power cord, manuals, and System 6 install disks.

The system has 2.5MB RAM, a 20MB SCSI hard drive, and a 1.44MB internal floppy.

2.5MB RAM
20MB Hard drive (with "stuff" on it)
System 6, at your service...
My wife wanted to know what I'd do with it... well, the answer is: play with it.

The first thing I did was look into "useful" upgrades: Network, Memory, Capacity.

I found an Asante MacCon adapter for the SE
I found 4 x 1MB RAM SIMMs for the SE
I found this gizmo: SCSI2SD

DING-DING-DING!

I can work with this.

And then I ran across this: macrepository.org

Sunday, December 16, 2012

iOS device non-glare screens

I've never been happy with the high-gloss screens on iOS devices: in my opinion, they're fingerprint magnets, regardless of their "oleophobic" coatings.

Since getting my first iPad (the gateway device that suck[er]ed me into the clutches of iOS), I've put non-glare screen films on my devices. Not only does a good film improve the experience for me, I've saved an iPhone from serious damage thanks to it.

I haven't tried them all—they're awful pricey for much experimentation—but I have had both success and failure with various brand's implementation of the film. For the purpose of this post, I'll stick to making only positive recommendations, leaving out any negative reviews; you can find those all over the Internet...

The iLuv "Glare-free protective film" was the first I tried, based on an online recommendation. As it turns out, it was a great choice, and it gave me my first taste of the difficulties involved in getting screen protectors properly "installed" on a device—especially one with the square inches of coverage that an iPad represents. The only negative part of my experience was the lack of local purchase options for the various devices (iPad, iPod Touch, iPhone). Online was the only option for some of them, and after adding both tax & shipping, they were a bit of an investment.

That's when I was introduced to the Power Support HD Anti-Glare screen protectors, the only screen protector I've ever found sold in the Apple retail stores. While all screen protectors have some amount of impact on the original glossy screen—the stated reason why Apple didn't make matte screens a standard option—I've preferred the non-glare aspect of the Power Support film far more than any loss in color fidelity in the Retina display. Similarly, the Apple retail stores in my area only carried the iPhone version; getting them for iPod or iPad are also online experiences.

And with the introduction of a new form-factor—the iPad Mini—it becomes a waiting game to see who will support the new screen first (as of this writing, it was iLuv).

Links:
iLuv
Power Support

Friday, March 25, 2011

iPhone Battery Drain--Fix!

It's happened to me twice now, but this time I was able to do something about it...

My iPhone went bonkers yesterday and stared draining the battery like there was no tomorrow. It went from fully-charged to 20% in 3 hours; that's just nuts.

I did what every iOS user does in that situation: kill all the backgrounded stuff and restart the device. Usually that works pretty well. This time it didn't.

The phone was using the battery so "hard" that the device was warm to the touch. Again, that's just nuts.

So I got the thing connected to my office WiFi and started watching the syslogger for my firewall; every TCP connection would then be logged for the device.

Sure enough, I found the culprit: the Exchange ActiveSync service for my home email (yes, I run an Exchange server at home) was getting requests from the phone every couple of seconds.

Given that I had problems with my Inbox earlier this week using Thunderbird, I assumed that I had another "broken" email message in my Inbox, and moved all the messages to another folder. The inbox cleared up on my iPhone, but it was still going after the server like gangbusters.

So I deleted the EAS profile from the phone. Blissful silence from the syslogger was the result. Then I re-applied the EAS configuration profile to the phone to re-establish the EAS connection, and voila!, the phone isn't going apeshit anymore.

I'm not sure I want to tempt fate and put all the messages from my inbox back, but I am pretty happy with the result: the battery should once again last all day.

Monday, March 7, 2011

Blackberry vs iPhone

Executive Summary: don't give up your corporate Blackberry in favor of an iPhone, regardless of whether you're on Verizon or AT&T.

Background:
I've been a Verizon customer for as long as I can remember—over 15 years—and have been a Blackberry/RIM customer and BES+Exchange administrator for over 5 years. I've used and supported Blackberry devices going back to the 7250 (CDMA Color "click wheel"), and still believe that the "Curve 2" is the best device they've come out with for Verizon to date.

That said: for anything other than phone calls and interacting with the corporate Exchange server, the Blackberry pretty much sucks. The Java platform is slow and clunky, and something as simple as web browsing is an exercise in futility.

When the iPhone was released, I thought it was a clever toy. I had associates with them that loved them, but in many ways my Blackberry Curve was better. I had a flash for my camera. I could take motion video. I could type long messages on the thumb keyboard with a minimum of errors, and when AutoCorrect was 'invoked', it normally made sense; better yet, I had complete configuration control over AutoCorrect in the Settings application. Had the iPhone come to Verizon in its pre-iOS4 incarnations, there's no doubt that I'd have stuck with my Blackberry.

Enter the iPad.

To be sure, I agreed with many of the tech press who thought of the iPad as a bit of a toy—"an iPod Touch on steroids"—from the rumors and actual announcement by Apple in early 2010. I had no desire to buy one, and would probably still be a happy laptop-only guy had I not won one in a drawing. Of course, it was "only" the $500 16GB WiFi model, but it was enough: in short order, I realized how useful a smaller, pocket-sized version of the iPad would be, and soon had an iPod Touch to complement the iPad.

Make no mistake: for me, the iPod Touch was a miniature iPad; in no way was the iPad ever like an iPod Touch on steroids. And I still carried my Blackberry in order to "get work done."

I soon discovered the limitations of he WiFi-only lifestyle: while WiFi has become fairly ubiquitous in my town and areas where I work and live, coverage just isn't universal. One solution would be an upgrade of the iPad by replacing it with a 3G model; another would be replacing the Touch with an iPhone. Unfortunately, both solutions leave the other device "unconnected", force you into multiple data plans, or force you to leave/change carriers. My solution was to add the Verizon MiFi.

That choice turned out to be genius: not only did it answer the need I had for the two iOS devices, it also filled the gap for my laptop use. Now I didn't need to plan my on-call outings around local hotspots: the hotspot came with me. On more than one occasion, having the MiFi in the car gave me and/or my wife constant connectivity for all the devices at hand.

So this setup worked fine for the better part of a year: I'd keep my Blackberry for phone and email; the MiFi was "always on" and available in the car; use the iPod for casual gaming and web browsing; the iPad was a pure entertainment device—movies, social networking, Angry Birds HD—while still keeping a laptop and desktop for "real work". My business life was primarily supported on the business Blackberry's phone/data plan, and my personal life was primarily supported on the personal MiFi data plan.

When the Verizon iPhone finally made its appearance in 2011, I decided to take the plunge: I'd eject the Blackberry and iPod in favor of the iPhone in order to pilot the device for the company.

Results:
The iPhone on Verizon is a very capable phone. Shortly after my switch, I had to work with a vendor's tech support for an issue and spent over 4 hours on a call. This is no feat for a Verizon Blackberry, but is anecdotally known to be problematic on AT&T iPhones.

As expected, all my iOS applications were able to move from the iPod to the iPhone, but in order to match some of the corporate Blackberry functionality, I had to add a couple additional apps: While iPhone supports Exchange ActiveSync (EAS), [in my environment] it only supports synchronization of mail, contacts and calendar. I'm a regular user of Tasks and Notes, so iMExchange 2 was my fix. Later, I learned that the only way to manage out-of-office notifications "natively" is through Safari, so I added iGone to improve the experience a bit. Great: free functionality on the Blackberry can only be achieved with $4 in applications on the iPhone.

But wait; there's more: EAS, VPN, iMExchange and any other interactions with the corporate network rely on your Windows/Active Directory logon. When your corporate policy requires you to change your password on a regular basis, you must manually change it on your iOS devices to match. And you better do it quickly, or your devices could fail to logon enough times to lock you out of your account. Yet another place where the Blackberry excels (because it uses a proxy agent to access your stuff); and unlike my other conversion issues, "there's no app for that."

As a replacement for the iPod Touch, I really appreciate the additional functionality of the GPS, accelerometer and always-on connectivity (the WiFi-only devices drop their connections when in stand-by, while iPhone switches to 3G when in standby).

Other nits:
  • the Calendar app on iPhone—whether a side-effect of EAS or a "standard" iOS functionality—removes stubbed-in meeting invitations. Before I started using iPhone, meeting invites were always written to my calendar as "tentative"; they stayed that way until I chose to do something about them. With iPhone, those tentatives are removed and aren't part of my calendar at all if I don't take some sort of action.
  • Sound/vibrate on iPhone—With iPhone, you have two states for sound/vibration: "noisy" and "silent". While you have a great deal of control over the ringtones for phone calls, you are otherwise brutally limited in your control over notification sounds and/or vibration. In contrast, Profiles on the Blackberry are wonderful. Not only can you set per-contact notification styles, you can set up various sound-only, vibrate-only and sound+vibrate profiles for various message types. Further, on the newer Blackberrys, you can set up a "bedside mode" profile that is automatically invoked when some combination of "plugged in" and time rules are met. In my case, I would switch to "phone only" from 11pm to 6am when on the charger, and "vibrate only" at any other time.
  • Virtual Keyboard on iPhone (and to be fair, any touch-only device) is nowhere as reliable or responsive as the thumb-board of the Blackberry. To be fair, I think some of the Blackberry models have terrible keyboards, too, but the frequency in which I accidentally hit "delete" instead of "m" on iPhone is just appalling. And Apples insistence that no 3rd parties "muck with" the keyboard means there will never be any real improvements in it.
  • Email Management: The only place iPhone beats Blackberry for email management is support for multiple Exchange connections (starting in iOS 4); there's no way to connect to multiple BES servers using Blackberry. That said, however, the Blackberry is the hands-down champion for email management. The Blackberry "knows" that it's a messaging platform. When a new message comes in, the device can be configured to jump directly to it when unholstered or awakened from "sleep." In contrast, messaging is just another app (albiet built-in) on iPhone. When a new message comes in, you may get notification, but when you invoke the app, it returns to the last state you left it; sometimes, that requires 3-4 taps to get to the new message. In addition, with iPhone, you can't:
    • Filter messages from being forwarded to the handheld; Blackberry has a robust ruleset for managing this.
    • Select multiple messages for mark-as-read/unread (although you can move or delete multiple messages) or mark read before a given date—I used this function all the time on my BB.
    • Delete on the handheld but leave on the server.
Wrap-up:
So that's it: I've joined many of you that are in a love/hate relationship with an iPhone. The Apple hegemony is set up so that I'll likely never see my "nits" addressed, and some of them—like the EAS password issue—are deal-breakers for my recommendation as a replacement for a business Blackberry. Personally, I'm not ready to give up on iPhone and go back to a Blackberry, but I've been on one long enough to have interest in what RIM decides to do with Qnx after they get the Playbook released. If they manage to breathe new life into their devices and put some good, basic functionality back into their OS, I can see myself going back to Blackberry for my corporate life.