Organizing

As I've written before, I confess I'm more than just a bit of a digital hoarder.

I have a 500 GB drive in my laptop. 500 GB should be more than enough for anyone these days—unless you're editing feature-length CGI motion pictures. If you are doing that sort of work, you shouldn't be doing it on a laptop (despite what Apple would have you believe).

Just sayin'.

Whenever I get a new laptop (or am forced to transfer my data off and back on during a repair), I don't actually go through stuff before that happens; much like when you physically move and just toss stuff in another box that should be thrown out.

Because of that, I have documents and data from twenty years ago. Records of things I don't own, don't care about, and don't need. I noticed the other day I had "only" 80 GB free on my drive.

It was time to do some housecleaning.

I know I didn't want to just get rid of everything. It had to be curated and moved to an external drive. Trouble was, I already had an "Archive" drive that was full of crap already. My folder structure had also changed considerably since I set up that archive drive so it wouldn't just be a matter of dragging folders. No, this was going to require getting down and dirty and pretty much going through everything.

I finished the project up last night. I had removed nearly 200 GB from the main drive and completely reorganized the folders on the archive drive and eliminating duplcates on the archive.

The only problem was this morning I realized that at some point I had deleted a folder completely that I wanted to keep. (I'm not surprised. I was working on this until nearly 2 am.) Of course, in my anal-retentiveness I had long since emptied the trash on not only the main drive but also the old archive drive and the new archive. This morning (before I realized what was missing) I overwrote my existing Carbon Copy clone of the main drive.

D'oh!

No problem, I thought. My backup routine includes not only a Carbon Copy clone, but also a regular backup to a Time Machine on our home network. I fired up time machine and…discovered that my Pictures folder HAD NOT BACKED UP SINCE APRIL.

Everything else was there. Pictures was not.

What the fuck, Apple? I mean seriously. WHAT THE FUCK.

"It just works." My ass it does.

I checked Time Machine settings, and Pictures was not, in any way, excluded from the backup routine.

(If you use Time Machine I would seriously consider taking a moment to verify that none of your top-level folders are missing from your backups.)

Since I obviously can't rely on Time Machine any more, I should probably get another Carbon Copy clone drive going and alternate them on a daily basis.

Now the missing folder wasn't anything that I'd go into a suicidal funk over if I couldn't get back; it was just several years of screenshots off the television…but I wanted them back.

I sighed, took a deep breath, and restored most recent "TV Screencaps" folder that the Time Machine had. It obviously didn't contain everything, but it was better than what had transferred from the original archive drive.

I located a file restore utility called Magoshare on the interwebs this afternoon. Almost every application I ran across that claimed to be able to restore deleted files would list them, but if you actually wanted to restore thm, you'd have to cough up anywhere between 70 and 100 bucks. Not in my budget at the moment. Magoshare on the other hand, would let you restore up to 500 MB for free, and I couldn't imagine that I had anywhere near that much still missing. I haven't done anything to my original external archive drive, so I knew the data was still there; it just wasn't indexed. Magoshare has been humming away for the last six hours locating every erased file on the drive. It still hasn't found the folder in question, but I'm not surprised. The progress bar is about a third of the way across (currently having found 400,000 files) and it's telling me it's going to be another four hours before it's finished scanning.

Tomorrow morning, if the missing folder or its contents aren't found, I'm going to take it as a sign from on high to simply move on…

UPDATE:

It's time to move on.

This Pleases Me

As you've no doubt heard by now (if you follow tech news at all), last week Apple surprised nearly everyone by releasing new versions of the 13- and 15-inch  Touchbar MacBook Pro. Amid the other upgrades and improvements was the addition of the Third Generation Butterfly Keyboard "to decrease the noise level" of the previous generation. Not as Apple was quick to point out, to increase the reliability of the keyboard itself. Because you know, the problem with the previous generation of keyboards was reported by only a very small number of users. That's why they're replacing even out-of-warranty keyboards free of charge now and refunding the folks who've forked out money to get them repaired in the past.

It has nothing to do with all the bad press and multiple class-action lawsuits. Um. Yeah. Whatever, Apple.

As the folks at iFixit quickly discovered, Apple's redesign includes what I call a keyboard condom; a extremely thin layer of silicone polymer between the key mechanism and key cap that not only cuts down on the sound of the keyboards, but also does it's best to keep out the detritus that can render the previous keyboards inoperable.

While this will affect me in no way whatsoever because Apple has categorically stated these new parts will not be used to repair the previous generations, ("We're going to replace pieces that break with more pieces that will break!") it at least it restores my faith enough that I wouldn't hesitate to buy a new machine if/when the need arises.

It's About Fuckin' Time

I just got mine back from repair yesterday afternoon.

Via The Verge:

Apple has officially acknowledged that there are problems with its "butterfly" mechanism built into the keyboards of the recent MacBook and MacBook Pro laptops. The company is now offering an extended keyboard service program for computers affected by the issue, via iMore.

The extended warranty covers replacement of one or more keys or the whole keyboard, depending on the extent of users' problems, and it covers eligible laptops up to four years after the computer was bought at retail. (Every MacBook and MacBook Pro model with the butterfly switches seems to be included.) That's dramatically longer than the limited warranty the computers ship with or even Apple's extended AppleCare Plus.

According to Apple's service page, the program covers the following issues:

●  Letters or characters repeat unexpectedly
●  Letters or characters do not appear
●  Key(s) feel "sticky" or do not respond in a consistent manner

Complaints from users about Apple's recent laptop keyboards have grown in the past weeks and months, with people saying that the keyboards tend to fail entirely when encountering dust and the fragile design makes them difficult to repair. And while it's certainly taken longer than most users would probably have liked, it's good to see Apple is finally taking steps to solve the problem.

It Finally Happened

It took nearly a decade, but I finally had a truly horrific encounter at Apple's Genius Bar.

This was the third time the keyboard on my year-old MacBook Pro has gone out. This time it was the "b" and "n" keys. As of yesterday morning, both were either double-typing or not typing at all.

We arrived a few minutes before my scheduled appointment. Our genius acknowledged our presence and a few moments later had us at the Bar. Unfortunately, he was simultaneously servicing four other customers at the same time, and it was nearly 40 minutes before he actually addressed my issue.

Ben had a similar but worse problem with his MBP a few months ago. At that time my faith in Apple had been restored because instead of more bullshit sending the unit out for another top case replacement, the Genius spoke with his manager and simply swapped out the entire laptop. That is the Apple of old.

No such luck with me last night. First, the Genius insisted on taking the laptop to the back to blow out the keys—even though I'd told him I'd already done that multiple times with no improvement. That obviously did not solve the issue, so instead of proposing swapping the machine out, he said it would have to be sent out AGAIN for top case replacement. He didn't even consider speaking with his manager to get it replaced outright.

Seriously? THIS IS THE THIRD FUCKING TIME IN A YEAR. Am I going to have to go through this every six months? It was obvious the guy was either new or had drunk too deeply of the Apple Kool-Aid. While he admitted that I was having trouble with this keyboard, he refused to acknowledge that this was a systemic problem affecting most of the 2016/2017 models. (Maybe they have a corporate gag order in place since they've been slapped multiple class-action lawsuits over the design of this keyboard.) In any case, it was obvious he was simply working from a script and not even considering deviating to "surprise and delight" the way Ben's Genius had done.

I'm in a quandary about what to do when I get it back from repair (probably next Thurday or Friday). I can either sell it to a local reseller for a third of what I paid for it and possibly get a used 2015 or 2014 model that does not have these keyboard issues for a reasonable amount of money, or I can keep it and probably go through this bullshit every six months until my Apple Care runs out.

Except for the keyboard breaking down, I do genuinely like that laptop. It's fast. The display is amazing. Touch ID is undeniably convenient. All things that are painfully obvious as I type away on Ben's old 2010 MBP that I am so incredibly thankful we didn't sell after he upgraded. (I've had to transfer my profile back and forth so many times now I've got it down to a science!)

And please, don't tell me I to buy a Dell or an HP. I support those things at work, and the only thing I hate more than the 2016/17 MBP keyboards is Windows.

Helping Out a Friend

A few weeks ago my buddy Mark (I know far too many Marks) in California was telling me he was ready to throw his MacBook Pro (mid 2012) through a wall.  It had gotten slow and unresponsive to the point of being unusable.

He couldn't afford to upgrade to a new one—something I strongly dissuaded him from doing anyway based on my own experience over the past year—and instead suggested he increase the RAM and swap out the spinning hard drive with an SSD since his was the last year of "upgradeable" MBPs and it would be a relatively easy process.

He didn't feel comfortable doing it himself, and since I have always been his hardware go-to guy but now lived 700 miles away, he asked, "Can they do that at the Apple Store?"

"Probably, but you're better off just buying the parts and sending it all to me. It will be cheaper in the long run and you'll know all your data will be transferred properly."

"Tell me what I need to buy."

So last Thursday the machine arrived, along with 8GB RAM and a new 512 GB Intel SSD.

Patient on the operating table.

And for once—a rare instance for my experience with Apple these days—everything just worked. It took only about two hours to swap in the new parts, load a fresh copy of the O/S (I had it on a USB thumb drive that I'd created for work a few days earlier), and restore his data from the old drive.

"It's ALIVE!"

Working on this "old" Mac reminded me just how much we've lost in Jony Ive's unrelenting quest to build a Mac no thicker than a sheet of paper. Never mind the loss of ports or the stupid fucking keyboard on the latest models. It's the little things like MagSafe and that slowly glowing (but otherwise invisible) indicator on the right side of the bottom case that showed the machine was sleeping when the cover was closed) that initially made me such a fan of Apple. And of course this:

Having the two machines side by side, however, did highlight how much better the display has gotten over the past five years, even leaving out the fact that Mark's wasn't a retina display and mine was. The brightness and color saturation were so much better on my 2016 it was ridiculous.

But c'mon Jony…how about bringing back a little of that "surprise and delight" factor Apple used to be known for?

My Faith In Apple Has Been Restored

Somewhat.

Last Wednesday evening Ben's MacBook Pro started acting up again. The machine already had the entire top case replaced two months ago because of keyboard issues and here we were again. This time the keyboard had suddenly become completely unresponsive. We attached an external one and were able to do the normal troubleshooting (resetting the SMC and PRAM), but the problem remained. After a totally useless 30 minute call to Apple Care, Ben made an appointment to take it in again to the Genius Bar for repair and unhappily resolved himself to being without his machine until the first of next week. He was able to successfully clone his drive, so restoring his applications and data wouldn't be as much of a clusterfuck as it was the last time we had to do this.

As I've written before, going to an Apple Store used to be fun for me, but lately it's become an unpleasant chore because of a certain—attitude—that the employees are starting to throw. So when we arrived at the Scottsdale Quarter store (where Ben bought the laptop and where it was last repaired) I expected the usual unfriendly customer service we've consistently gotten from Apple of late.

But that didn't happen. I was pleasantly surprised. Everyone from the concierge to the Genius himself was how I remember Apple used to be.

After listening to Ben explain that this was his only computer and it was the second time we'd been in for the same problem (and that I too was on my second MBP because of keyboard issues), we fully expected the guy to simply say, "I'm so sorry to hear that! We'll send it off for another bottom case replacement and you'll have it back in 3-4 days."

But he didn't.

"Hold on a sec…" he said, and disappeared to the back.

Several minutes passed, and he reappeared with a shiny new white box in hand.

"I spoke to my manager, and we're just going to give you a new one, if that's okay," he said. "We'd like to send your old one Engineering. They're actively tracking these keyboard issues."

I am incorrigible..

I don't know if it was because it was a slow night or if he was genuinely interested in this problem (he struck me as not only an Apple employee but also a fan), but we then proceeded to have a long discussion about these keyboards and Apple's general design philosophy. It was very refreshing to speak to an Apple employee who  actually knew their shit and seemed generally interested in their customers.

After we got back home, Ben booted to the cloned drive and restored everything to the new machine in 30 minutes. Back in business!

(As an aside, if you're a Mac User and you're not using Carbon Copy Cloner for your backups—you do backup, right?—you should be. It's proven to be much more reliable—and user-friendly—than Apple's Time Machine ever was.)

This doesn't mean won't bitch about Apple in the future if it's warranted, but this trip to the Genius Bar was definitely a much-needed breath of fresh air.

Oh, We Can't Do That!

About two months ago I got an email from my supervisor asking, "Do you know Mac and how to fix issues?

I responded that I was no expert by any means, but I did know my way around the OS. I asked what was up.

She responded, "Nothing right now but I may ping you at some point."

Because, you know, this is a government agency and we are hip deep in need to know bullshit—for even the littlest things.

A week later I got an invite for a meeting titled, "Mac Computers and Exchange" at the headquarters of our famous magazine.

Turns out there's been a years-long problem with the Macs crapping out and losing connection to the Exchange server, forcing calls to the Service Desk for password resets multiple times a day. (How exactly they were speaking to the exchange server through Outlook without being bound to the domain was something I never got a clear answer for, but I was pretty sure all the problems would disappear if the machines were actually on the domain.

The guy from the network group claimed it was a pain to add the machines to the domain. I knew this was bullshit from having worked at DISH, where there were literally hundreds of Macs on the domain—all of which worked flawlessly.

I did my own outside research on binding Macs to Active Directory and realized it wasn't nearly as much trouble as the network guy had indicated—especially since he said they were already set up for it on the back end. I convinced the magazine folks to lend me one of their machines so I could do some troubleshooting.

Back at my office, after wiping and doing a clean install of the OS, I easily bound it to our domain. I hadn't yet gotten the links to our MS Office installer, so I set up Apple Mail to connect to the Exchange Server. Rock steady. After logging in initially, it never prompted for my credentials again.

The general consensus among the Mac Troubleshooting team was that several applications (Adobe CS and Outlook among them) were having issues getting past our anal-retentive firewall. Even though it was set up in networking with the correct name and port, getting to certain locations—easily accessible on a Windows machine—was impossible.

After speaking with the magazine's webmaster, I got a list of websites that needed to be whitelisted in order to get past the firewall to connect to Adobe services. I was also told that several certificates needed to be copied from my Windows machine.

I added the sites and the certificates, and I was able to connect Adobe Creative Cloud and download applications and fonts. I could also get to most websites—on Chrome at least. (Safari refused—and is continuing to refuse—to connect to anything outside the firewall.)

Even while logged into Adobe, Apple Mail and the connection to the Exchange server remained steady. I felt like I was making progress. I'd been documenting everything in mails to the group and getting positive feedback from the magazine folks.

A few days later I was finally able to install MS Office. Sure enough, once I started using Outlook all hell broke loose. Not doing anything on the machine, Outlook would kick me out, prompt for credentials and then lock my account.

I asked the magazine's webmaster (who had become the group's de facto contact person) if they'd ever considered just using the native Apple apps for mail and calendar. "I don't remember the exact reason because it was several years ago, but we were told by network security we couldn't do that."

WTF.

Apparently unlike anyone else on this fucking team, I actually went to the Google and did some research on the Outlook issue. I discovered the credential-prompting problem was at one point fairly common and had been addressed by a subsequent Office update. Imagine that.

Of course, the only problem in our locked-down environment was getting the Office update because—of course—the automatic downloader in Office was being blocked by the fucking firewall.

More research led me to the direct download link from Microsoft, and once it was downloaded and installed, the prompting issue—for the most part—disappeared.

After the update, for the rest of the day I remained connected without so much as a hiccup.I left everything logged in that evening, but returned to work the next day to discover that at some point Outlook had logged me out and was once again prompting for my credentials. Discouraged, I stepped away from it for a while and went back to my other duties (i.e. wasting time on the internet).

Apple released the 10.13.4 OS update late last week, and at this point I felt I had nothing to lose by upgrading the machine. Outlook still wasn't working 100% and the worst case scenario would be that the update would break something horrifically and  I'd have to wipe and reinstall everything again. I could live with if the update actually did something to alleviate this issue.

So last Friday I downloaded the "combo update" package for 10.13.4 (because the App Store is also blocked by our firewall) and upgraded the machine.

I stayed logged into both our domain, Adobe CC, and our Exchange Server through Outlook over the weekend. Except for one unrelated incident this morning that caused everyone to be bounced, the connection has been rock steady.

All's well and good, right?

Well, not so fast. When you work for a government agency, you can't just  go fixing things, y'know. Prior to our last meeting, just getting as far as I had prior to the upgrades was met with a flurry of "Oh well, we can't do thats" from the network guy. The magazine people were fine with binding to the domain. They'd have access to network resources without having to jump through hoops, and if the Outlook/firewall issue was solved, this solution could be implemented for other Mac-using (or wanna-be-Mac-using) departments in the organization (such as Video and Creative, who have their own set of issues).

For shits and giggles—since this was not specifically part of my purview)  I loaded our Citrix client on this loaner machine, and was able to access my Citrix desktop and use all the same Windows tools I do through Citrix on my Windows laptop.

In a way this was frustrating because It makes me want a Mac at work. The UI is so much more elegant than Windows. The machine boots up and connects in a heartbeat, and it's just a much more pleasant user experience. Since I was told I'm now the backup Mac support guy for the magazine a good case could be made for it, right?

Yeah, well, that's not going to happen and eventually I'm going to have to return the loaner.

Last week I was working with one of the guys in Creative who—who, along with the other members of the team—is struggling with the Adobe Suite on an admittedly decent Dell workstation. Recently they've been complaining about how it takes forever to do anything and have asked for quotes on more powerful machines (10 core processors, SSDs, 32GB RAM). They got a quote of around $4K for the monsters and of course, there was much hand-wringing.

While I was trying to get this particular user's CC apps to update to the latest version (they refused, because the latest version of Windows 10 is not installed on the machine) I told him that they really should be using Macs. "Duh!" was his response.

I related the research I'd been doing for the magazine, and suggested that for the amount of money they were going to lay out for new Windows machines, if the problems fully integrating Macs into our environment could be solved, that taxpayer-provided funding would be better spent on buying Apple gear.

I told him I'd run the idea past his supervisor.

I met with her yesterday, and she said she'd spoken to purchasing about this and got nothing but pushback. It was obvious they had little to no knowledge of the work that we'd been doing over at the magazine and was still quoting the company line,  "Macs don't work in our environment."

Well no, they don't—if it's going to be business as usual and my suggestion that the machines be put on the domain continues to be ignored.

At this point I'm frustrated because they want solutions—but yet it seems they don't. The entrenched bureaucracy in Networking and Network Security are dismissing my recommendations and more than anything else I'm getting the attitude from them that I don't know what I'm doing, and furthermore why should they listen to a contract employee anyway? I'm almost to the point of asking my supervisor why I even need to be on this team if all my suggestions are shot down. What's the point?

If nothing else, this exercise has made me realize I really want to work somewhere that I can support Macs.

 

Quote of the Day

I think Apple has shown across multiple years and multiple products that they only care about making the keyboard thinner, and they will make some efforts to make the thin keyboard tolerable, but that they are no longer interested in keeping it a good keyboard if that means they can't make it thinner. And so I just have to kind of resign myself to accept that." ~ Marco Arment

PREACH, Sister!

Hilarious!

Benjamin Button Reviews The New MacBook Pro

The new MacBook Pro shows that Apple is finally becoming serious about developers.

Gone is the gimmicky TouchBar, gone are the four USB-C ports that forced power users to carry a suitcase full of dongles. In their place we get a cornucopia of developer-friendly ports: two USB 3.0 and Thunderbolt 2 ports, a redesigned power connector, and a long-awaited HDMI port.

Photographers will rejoice at the surprising and welcome addition of an SDXC card reader, a sign that Apple might be thinking seriously about photography.

The new MagSafe connector is a bit of Apple design genius. The charging cord stays seated securely, but pops right off if you yank on it. No more worries about destroying your $2k laptop just by accidentally kicking a cord.

What hasn't changed: Apple has kept the beautiful Retina display, and storage and memory are the same as before. The new machines will be slightly thicker (to accomodate the USB ports) and 200 grams heavier, but it's not clear how this will affect battery life.

Interestingly, Apple has removed the fingerprint reader and its associated dedicated chip, perhaps assuming that developers would not comfortable with a machine they don't fully control.

The most obvious change is the redesigned keyboard. Removing the Touchbar creates room for a row of physical function buttons and, in a nice touch, an escape key. This isn't a perfect solution: the function buttons map to a confusing series of actions that can send windows flying around the screen with an errant keystroke, and the new physical off switch is too close to the backspace key. But it is certainly a huge step forward, and it will be interesting to see how software developers take advantage of this clever new feature.

Everything about the new machine seems designed for typists. The trackpad has been made smaller, so you're less likely to brush against it with your palm. The keys themselves are much more comfortable to type on, with improved key travel, a softer feel, and more satisfying tactile feedback. You no longer feel like you're tapping on the glass surface of an iPad. And not having a TouchBar me ans no longer having to look down at your hands all the time.

Despite the many improvements, Apple is actually dropping the price on its flagship 15" MacBook Pro by $400, another sign that they're serious about winning over developers.

The release is an encouraging sign of life at Apple, whose products have not seen significant changes since the company introduced a separate operating system for its laptops in 2019. There's even speculation that Apple may refresh its antiquated Mac Pro and desktop macs, neither of which hav e been updated since their release in 2022.

Rumors are also swirling that the company will add a headphone jack to its already popular iPhone. The announcement could come as early as this month.

Mood

Now it's Ben's turn to have his 2017 MacBook Pro sent off for top-case replacement. He was having slightly different problems, but since EVERYTHING on these machines is apparently soldered/glued in place, individual parts can't be swapped out.

It Seems I'm Not The Only One

MacOS is starving for attention. It is stagnating. It is falling apart. High Sierra is in many ways pathetic and scary in how sloppy things were done with it how many bugs there still are in many areas. The security bugs are embarrassing. I mean, it's getting worse. Every release seems like it's getting worse. Sierra was a terrible release also. Very unreliable, lots of bugs, lots of problems, lots of subsystems and things that were seemingly rewritten for vague reasons and then were worse and more buggy. This is increasing over time because they are not putting the resources into the OS that it needs to be stable and secure and to be moved forward.

I've found myself just more and more annoyed that things that used to reliably work, don't work anymore. And then I see these software issues that are just disheartening and it makes me just feel like I want to throw my hands in the air and plop them down on the desk and say, "Now what? Now what do I do? Cuz I'm just screwed. Where am I gonna go? It's just frustrating because it used to be this was my happy place. And maybe the problem is because I'm clinging to the Mac and the Mac is dead, but I don't know where the issue is. Is it me? The Mac? Is it Apple?" ~ Casey Liss, speaking on this week's Accidental Tech Podcast

Fixed. For Now.

Well, it's fixed. It has been for a couple weeks now. I just haven't bothered to write about it because I know y'all are tired of hearing me bitch.

As expected, the entire top case was replaced. At minimum that included the keyboard, trackpad, and battery. I suspect that the system board was also new, since the SSD (hard wired to said board) was returned with a clean install of Sierra (unfortunately not High Sierra as it had gone out with).

The keyboard (as evidenced by the new markings on the control and option keys) is from the mid-2017 line, even though my original was a late-2016 model, leading me to believe that the entire machine was swapped out except for the bottom cover (where the serial number is engraved) and that the serial number itself was transferred from one machine to another in firmware. I understand there are some minor internal changes in the 2017 keyboard design (there have been far fewer complaints of keyboard issues), so hopefully this will be the last trouble I have with this laptop for however long I end up keeping it.

Robopsychosis

If you're tired of hearing me bitch about Apple and technology, you might want to just skip past this one because it's gonna be a long one.

"It Just Works!"

Except when it doesn't.

As I wrote a few days ago, I'd decided to bite the bullet and take my six-month-old MacBook Pro into the Apple store so that the wonky keyboard could be replaced. I knew it was going to have to be sent out because the entire top case would have to be replaced. I went ahead and made the appointment.

I'd upgraded Ben's old MacBook with a 512GB hard drive and bumped the RAM to 8 GB—the same configuration I had on my new machine which would allow me to effortlessly move all my data onto the old machine while the new one was getting fixed and not have to pick and choose like I did the last time I had to use the trusty old warhorse.

I'd initially wanted to get my data transferred before I took the machine in for service in case I ran into any glitches, so as I'd done dozens of times before when restoring my entire profile onto a different machine, Friday night I installed a fresh copy of the OS on the old machine, logged in with a Temp Admin account, and then ran Migration Assistant. It kept crapping out. Even though everything was properly checked off, the first attempt transferred everything except the Applications. What the hell? I attempted to go back and just select "Applications" at that point, and after churning away for another hour or so it informed me it was finished. I logged in and nothing had been transferred.

At this point I wiped and reinstalled again. This time I selected only Applications. Success! But when I went back and attempted to restore everything else, it crapped out each time it got around to discovering "Other Files and Folders." After banging my head against the wall for the better part of the evening, I decided to attempt a peer-to-peer restore from my new machine to the old one. Once again I wiped and reinstalled the OS. Set up the peer-to-peer option for restore and waited. And waited. Because it was going over our wireless network, it was going to take hours, but it seemed to be working. That was fine. I was ready for bed anyway.

Saturday morning I woke to find it hung at "51 minutes remaining" on restoring just my profile (it hadn't even gotten around to the Applications or "Other Files and Folders." No problem; my appointment wasn't until 11:45. It was only 7 am. I had plenty of time.

Except it never changed. Finally at 10:45, I pulled the plug and wiped and reinstalled the OS on the new machine before taking it in. Call me paranoid, but I don't trust Apple that much with all my data. I figured I could sort out the Time Machine issue one way or another when I got back. Little did I realize it would literally take all day yesterday get up and running again. Flashback to 2009 and Windows HELL.

Upon arrival at Apple Biltmore, the concierge  gave me more than a little attitude when I approached her. I don't know what the problem was, but she was anything other than smiles and welcoming vibes. In fact, the whole energy level of the place was vile. I remember when I used to enjoy going there, whether it was to buy something or get something fixed. Now I dread it.

I explained my problem to the "Genius" and he whisked the laptop to the back for several minutes, finally returning to say that yes, he was able to verify my issues. He said it would be 3-5 days for the repair

Upon returning home, no matter what I did to restore the data, it wasn't working. I wasn't too worried; I knew all my data was safe, and most importantly I had multiple manual backups of my photos and music in case something was really seriously out of whack. Everything could be restored. Finally, somewhere around 9 pm I did a deep dive on Google and the overwhelming recommendation was to run a repair on the Time Machine. I started that as I went to bed.

Yesterday morning, finished, it reported multiple errors, none of which could be repaired.

FUCK.

"The data is safe. The data is safe. Your important stuff is backed up multiple places." Nonetheless, my anxiety level was rising.

So once again I wiped and reinstalled the OS. At this point I knew i was going to have to reinstall all my apps either by moving them manually from the Time Machine or worse—from scratch—and then manually pull the rest of my data from the Time Machine. While I didn't look forward to it, it was probably well past time for such an endeavor. Multiple installs and uninstalls of apps and multiple OS upgrades over the years since I last did a clean install probably guaranteed there was a lot of sludge on the drive that needed to go away. It would also afford me a new, good backup to use with Migration Assitant when I got my machine back from repair. And if nothing else, philosophically it was a good way to start the new year. My two main concerns however were restoring my mail folders (I store pretty much everything locally, and based on past experience, moving Apple Mail from one machine to another is a pain in the ass, unlike Windows and Outlook where it's generally just a matter of copying a .pst file.) and my Chrome Bookmarks. I hadn't bothered to export them before all this started, foolishly thinking everything was safe and sound.

By late morning I'd located the mailboxes. Each one had to be individually imported back into the new instance of Mail I'd set up, but everything was there. I know it's a silly, first-world problem, but I like to keep that stuff. My anxiety level dropped a bit.

When I fired up Chrome, I logged in and—braise the baby cheebus—all my bookmarks were there. The same went for my RSS Reader. Since I switched to Feedly some months ago it was simple to reattach it to the Reader. Anxiety level continued to drop.

The rest of the day was still spent in robopsychosis, but at least my anxiety had bottomed out; I copied all my apps over from the Time Machine backup, knowing full well that more than just a couple of them wouldn't work properly at first. That proved to be the case, and a simple uninstall and reinstall from the Mac App store solved 95% of the problems. The remainder were licensing issues, solved by contacting the developers who—amazingly—were actually working yesterday and able to help me get everything sorted out.

Ben and I headed out yesterday afternoon to do our usual Sunday grocery run and prior to leaving I started manually copying the +150GB worth of music files back from the Time Machine. When we got home, everything was transferred, and firing up iTunes verified that everything was present and accounted for.

As if I hadn't experienced enough Tech Hell this past weekend, Ben and I decided to switch cell providers. We'd been with Verizon for years and were very happy with the coverage and service, but in the interest of saving money, a few months ago we switched to T-Mobile. BIG mistake. The old adage of "you get what you pay for" could never be more true. Coverage was spotty (Ben had no service at his school), customer service was a joke, and while we still owed $1000 on the two new phones, we knew we had to get out of the contract.

So back to Verizon we went. Unfortunately, we had to buy two new phones because T-Mobile phones are locked to the carrier. Supposedly our numbers were ported over (we got these at Target), but as of this morning, all the phones are still active with duplicate phone numbers, and it's causing nothing but grief for sending/receiving calls and SMS messages. We'll get it sorted today, but damn…really?!?

Anyhow, before we went on our Verizon run, I set to copying the ±150GB worth of personal photos and um…"other" pictures from the Time Machine. It was still running by the time we got back, but eventually everything came through.

By the time 2018 arrived last night, the Mac was back in order except for the issues caused by two different phones with the same number trying to link to the Messages application.

Lesson learned? I really do have a lot of stuff on my laptop that I can't afford to lose. Multiple Time Machine disks are necessary and I need to run disk repair on a regular basis on each of them to prevent this from ever happening again—because having to go through all this is exactly the kind of shit that sent me fleeing Microsoft, and as much as I bitch about Apple, I could never go back.

 

The Ongoing Keyboard Saga

I know y'all are probably as tired of hearing me bitch about the keyboard issues on my six-month-old MacBook Pro as Ben is, but this is my blog and I'll bitch if I want to.

This week I finally reached the end of my rope with this fucking keyboard. I got a little cash for tending my sister's cats over the holidays, so I bit the bullet and ordered a larger hard drive and more memory for Ben's old MacBook so I can transfer all my data and then take mine in for service and comfortably be without it for however long it takes Apple to replace the entire top case—because just the keyboard can't be replaced. No, the entire top case and battery (because it's  glued in place) has to be swapped out as well . The hardware I ordered is due to arrive from Amazon today and tomorrow, and I have an appointment at the Apple Store on Saturday.

It's as if the machine knows what's going to happen. Now all of a sudden I have not one wonky key, but five that either won't type without pounding on them or type double characters. I've followed Apple's ridiculous keyboard "maintenance" instructions and now in addition to the aforementioned keys still not working, two of them are brighter than the others. (Obviously the compressed air loosened and blew away something under the keycaps that controlled the brightness.)

I swear this is the worst MacBook I've ever bought from Apple. Every day I regret not purchasing last year's model when I had the opportunity. I pray to the gods that the keyboard is fixed/reverted/redesigned on the next iteration of these machines because at that time this one is getting replaced as soon as possible thereafter.

Call Me Crazy

…but this non-Apple mockup of a future MacBook Pro certainly seems to be the direction Cupertino is heading. I'm not sure how I feel about a touchscreen keyboard since I hated the one on my old iPad, but as was pointed out by JP earlier today in a conversation we were having, if Apple provides some sort of haptic feedback to simulate actual key presses, it might not be such a bad way to go

And getting rid of mechanical keys would certainly do away with their current crop of keyboard problems that stem from Jony Ive's fanatical drive to make the thinnest device possible. I mean, you can't get much thinner than a touch screen, can you? It would also alleviate my own personal bugaboo about keyboards in general, the way the most used physical keys get worn down and shiny from constant use.

What do you think?




Apple Teaches Us To Accept Being Inconvenienced

"It just works!"

If you buy into the Apple ecosystem, something you need to know is that you're going to be inconvenienced…a lot.

When I got my latest iPhone, I knew going in that I'd be losing the headphone jack. No problem, I thought; it comes with an adapter that I can use to connect it to the head unit in the car (sadly, Anderson is not bluetooth-equipped). What I didn't forsee were those rare instances when I wanted to listen to music through headphones as I fell asleep. I have bluetooth earphones, but they're impossible to sleep in. And yeah, I could pull out the crappy lightning earbuds that came with the phone, but for me they're also incredibly uncomfortable, fall out, and sound like crap. So I'm faced with either bringing the stupid headphone-to-lightning adapter in from the car every damn day on the off chance I might want to fall asleep to music, or dropping $10 for another fucking adapter that I can keep bedside.

And then there's the ongoing issue with my nearly-new $2K laptop and it's goddamned keyboard. When you buy something from Apple, it comes with the expectation that—at least hardware wise—you're getting the finest engineering on the planet. That used to be true, but lately it seems that in Jony Ive's quest to make everything no thicker than a sheet of paper, that has fallen by the wayside. While I figured out how to safely remove the keycaps and blow compressed air into the butterfly mechanism to clean out dustI shouldn't have to.

Yesterday, the N-key just stopped working altogether. Since I knew this was eventually going to happen, I'd ordered a replacement key cat and it was supposedly sitting at home in my mailbox, so I pried the top off the key again and gave the whole thing another good dusting. The functionality returned to what it was prior to yesterday, and after getting a really good look at what's going on under there I decided that I would live with it until I absolutely had to tear the key completely apart to replace the dome mechanism.

I shouldn't have to do this, Apple.

Yes, it's obviously still under warranty, but taking the machine back to Apple is also an unacceptable solution because for some reason the key can't just be replaced by their Geniuses like I was about to do. No, the whole thing has to be sent out for a complete upper case replacement because the keyboard is glued in place and I'd be without it for one-to-two weeks. And even then there'd be no guarantee another key wouldn't get fucked up.

What the hell, Apple?

There are rumblings of a manufacturer recall. My fingers are crossed.

Finally, there's the issue of my Apple ID. Last week Apple finally started allowing people to change their main Apple ID to an icloud.com or mac.com address (something that you haven't been able to do ever). When I set up my account back in 2009 on my very first Mac, I chose voenixrising because I was new to the this untrusted environment and didn't want to use my real name because reasons. Over the years, that of course changed, and now I use my realname@icloud.com (an alias I set up under the main account) address for pretty much everything.

So when news of this change became known, I was ecstatic. I could finally ditch the otherwise unused g-mail account I'd been using as an Apple ID. I logged in, went through all the steps, sent up all the offerings to the Apple gods, did the proscribed incantations and…"you cannot use an icloud address as your main ID."

WHAT THE FUCK, APPLE?

And that error only occurred when attempting to use the realname@icloud.com account. Every other alias I'd created could be used.

I called AppleCare the next day, and to his credit, the guy on the other end of the line was incredibly helpful. Unfortunately, we still couldn't get it switched over at that time because apparently if you have been using an @icloud.com address as your emergency backup address in the Apple world, you can't use it as your main ID for thirty days after you unhook it as the emergency contact. And my realname@icloud.com was the backup.

Inconvenience, thy name is Apple.

UPDATE: Late this afternoon the H-key started acting up. Again. So I gently pried the keycap off and dusted it out. I noticed when I replaced the cap it was loose on one corner. It turns out one of the little pins on the butterfly mechanism had broken off at some point.

So now I have two wonky keys. They work, but not without issues. I'd take the damn laptop into Apple tomorrow if Ben's old backup machine was usable enough for me to transfer everything over, but it isn't. It needs both a RAM upgrade as well as a larger hard drive so I don't have to pick and choose what to restore from Time Machine when restoring to it. Until I can afford to make those upgrades, I guess I'm just going to have to carry the little Apple bluetooth keyboard I bought back in 2010 with me.

This is BULLSHIT, Apple.

"At Least Make It Reliable!"

My thoughts exactly.

I haven't had any further issues with the keyboard on my MBP—only because it's been covered with a silicone keybaord skin, preventing anything from actually coming in contact with it.

And I hate it. The things never fit properly (I've tried four so far), always tending to bunch up on one end or the other, and much like putting a case on an iPhone, what's the point of Apple going to such lengths to create something that you want to touch, but is obviously so prone to damage you never actually get to?

After living with this computer for three months now and knowing what I do, if I had a chance to go back to last May, I definitely would've purchased the 2015 model—with the old keyboard design and no Touchbar—when I had the opportunity. The Touchbar remains of dubious utility and the fact that I have to put a condom on the keyboard to ensure that it works when I need it to work is ridiculous.

(audio source)

WTF?


A new photo of the alleged "iPhone 8" engineering validation test codenamed "Ferrari" has been published on social media, with the image showing the locations of the charging coil, the stacked main board, and a void for where the L-shaped battery goes.

I'm long past the point where my entire existence revolves around the next iPhone rumor to hit the newsfeed—especially since they start appearing the moment after any particular current iPhone model is released. Yes, I own one, but for me it's just a phone. I appreciate its technology and while as recently as ten years ago I didn't even own a mobile, today I can't imagine leaving the house without it.

That being said, what struck me about this latest "leaked" image is that FoxConn—one of the biggest, most sophisticated electronics manufacturers on the planet—is still using Windows XP?!?

"It Just Works!"

Except, of course, when it doesn't.

Shortly after that post bemoaning my continuing keyboard woes, the situation worsened. One key was consistently typing double letters and another wouldn't type at all unless I pressed down really hard.

Reluctantly, yesterday afternoon I made an appointment to take the machine into the Genius Bar, resolving myself to the fact that I'd be without my Mac for a few days.

With little else to do this morning however, I started poking around YouTube. Even if it wasn't obvious from Apple's own forums, the sheer number of videos posted about these keys not working properly was confirmation that my problem wasn't by any means unique. Also, it seems these new keyboards aren't as unfathomable as I'd feared.

After watching the video I figured I had nothing to lose by trying this. After all, I already had an appointment scheduled at Apple. Taking a deep breath, I slowly pried off the first keycap. I got out my trusty can of compressed air and gave the mechanism in the key socket a good dusting and carefully snapped the key back on. Viola! No more double letters. I repeated the procedure with the other offending key and afterward it was once again fully functional.

I haven't cancelled my 5:45 pm appointment just yet; I'm waiting to see how this plays out the rest of the day. But right now, things are back to normal.

While I still feel this is a huge design blunder on Apple's part (the tolerances are now so tiny that the slightest bit of dust or dead skin cells or whatever can apparently muck up the mechanism), it's nice to know that the fix is relatively easy and straightforward—and while I sure don't look forward to doing this again, it certainly beats Apple having to send the fucking machine out for an entire top case replacement.

I bought a silicone keyboard cover right after I got the laptop because my anal-retentiveness hates the way the keys eventually wear down and get all shiny. But wasn't a perfect fit, it bunched up, and I didn't much care for the way it felt while typing. But if it prevents stuff getting down into the key mechanism, I may just have to live with it.

#firstworldproblems

Stepping Into The Matrix

We went out to Arrowhead Mall yesterday because Ben needed new shirts for work and JC Penney was having a huge sale. He also wanted to go to the Apple Store to look at MacBooks; he has become increasingly disenchanted with his decision to leave the Church of Jobs earlier this year and wanted to check out the new models.

While Arrowhead has had an Apple Store forever, they have remodeled and now have one of the new designs:

That's right. The new stores are like stepping into one of the "artificial constructs" of the Matrix. I even had to look to find the iconic Apple logo outside the store.

Anyway, the model Ben wants is the 15-inch 2.9/16/512 Touchbar, that even with his education discount comes in at $2500—twice what he paid for his Lenovo Yoga with similar specs a few months ago—so it's not happening any time soon.

Even then I'm in no hurry for him to switch back. While Ben loves technology, Ben is also one of those Technology Cursed. He has issues with pretty much every piece of gear he buys, and with my own ongoing problem with the keyboard (yes, it's happening—albeit with different, random keys this time—on the replacement machine I got) on my new Mac, I don't want him jumping into that shark pool until Apple fixes this mess. (If I could do it over, I would go back and get the 2015 pre-butterfly key model because this is really starting to piss me off. There's no logic to it; like with the first one I had, the h-key went wonky. Then it cleared up and the g-key lost its mind. Now it's the n-key. Hardware? Software? Sun spots? Apple will repair it, but from what I understand it will have to be sent out because the entire fucking top case needs to be replaced and I'll be without a machine for a week—and there's no guarantee the problem won't recur. I'm not yet to the point where I'm ready to go without but if it gets any worse I may reconsider that stance.)

Why I'm Still a Fanboy

Let's face it: Apple has issues. It's a company that has grown from a single garage to a multi-national behemoth. And like all mega-corporations, it has its share of problems.

Less than a week after getting my new MacBook, one of the keys stopped working. Or rather, I should say it worked intermittently. Sometimes it wouldn't register at all; other times it would produce a double character. Annoying, to say the least, and not expected from a brand new two-thousand dollar machine, much less one from Apple.

A quick search revealed numerous complaints surrounding the new butterfly keyboard on these Macs. I followed the recommendations, from blowing compressed air into the affected key to the wholly ridiculous procedure of reloading the OS.

Blowing air seemed to alleviate the problem to the point that I canceled the Genius Bar appointment I'd scheduled for Friday evening.

Of course the moment I canceled the appointment the key started typing double characters. (Hey, it wasn't not typing any more!)

Fuck.

I made another appointment and took the machine in today, expecting the worst and gearing up for a confrontation. (After all, it was barely a week old.)

Imagine my surprise then when—after explaining what was going on to the Genius and mentioning it was only a week old—he said, "Oh heck, we'll just swap the whole thing out."

This is the outcome I was going to fight for if it had not been offered. After all, I was still in Apple's 14-day no-questions-asked return/exchange window.

After verifying my educational pricing purchase (I was never asked for Ben's education credentials when I picked the machine up a week ago), the machine was swapped out and the old one wiped of my data as I watched. The Genius then offered to help me set up the new one, but by that time he'd already sensed I was more than capable of doing it myself.

I set up the machine with a temp account (something you need to do if you're planning on restoring from a Time Machine backup), verified that all the keys worked normally and that there were no dead pixels on the display, and was on my way less than a half-hour after arriving at the store.

Many things can be said about Apple's Quality Control these days. No longer under the watchful eye of taskmaster Jobs, I believe that the company's attempt to adhere to what are now expected annual multi-platform hardware and software upgrades isn't allowing much opportunity to squash every software bug and hardware glitch before new product rolls out the door. This is what's most frustrating because you don't expect to encounter these type of issues with an Apple product. "It just works," after all.

But based on my own experience—and despite some horror stories from friends and others posted online—Apple's Customer Service is exemplary and what I still strive to emulate in my own professional life (when I'm not cussing out my customers under my breath, that is). This, more than anything else is what keeps me a loyal customer.

 

Back to "Normal"

They weren't the circumstances under which I wanted this to happen, but since it did, I'm going to make the best of it—even if it means #backindebt again.

Say hello to my new Mac.

I've had it less than 24 hours, but I have to say that everything I've read online about this machine is true. It's beautiful. It's responsive. The display is awesome. But what do I like the most?

The keyboard.

I'd been a little worried about how it would "feel" in relation to all previous iterations of the Apple keyboard because of all the negative press the redesign initially received, but at least for me, it's an absolute joy to use. The keyboard illumination is uniform and has no light leak at all.

You know what I like second most? The fact that encountering a page full of animated gifs online or using Adobe Bridge no longer sends the fans into overdrive. That is wonderful!

Yeah, I kind of miss the glowing Apple logo on the case, and I still think the Touch Bar is more gimmick than anything else, but there's no denying it's a cool gimmick, and maybe some day I'll actually use it for more than just changing screen brightness or playback volume…

Since this time I was able to restore from my last Time Machine backup in full—in comparison to having to pick and choose what to leave out because Ben's old MacBook couldn't hold it all—bringing this machine online and have everything work from the get go was a breeze.

And now there's a new rule in this house: NO LIQUIDS ANYWHERE NEAR OUR TECH!

First World Problem

Conundrum

Since it doesn't make fiscal sense to have my Mac repaired—the estimate being only a couple hundred dollars less than the cost of a new machine—I am now faced with finding a replacement.

At the time I bought it four years ago, my machine was the top of the line: 3 GHz i7, 8GB RAM, and a 512GB SSD…so obviously I'm going to want something similar.

Apple is still offering all models of the 2015 MacBook Pro (MagSafe, multiple ports, retina display), but with a refresh imminent, it's hard to say for how long they'll be available. With Ben's education discount, I can get a 2.7 GHz i5/8/512 for $1559. If I want to bump that up to a 3.1 GHz i7, the price jumps to $1829. Both of these are custom orders, so I can't just walk into an Apple Store and go home with one.

And this is where the conundrum comes in.

I can get the 2016 non-Touchbar model (2.4 GHz i7/8/512) for $1899. This would also be a custom order.  For the same price I can get the Touchbar model with a faster processor (2.9 GHz i5/8/512)…and it's in stock.

When the Touchbar Macs came out last year I was immediately enthralled, but despite the "cool" factor, I still do question the ultimate usefulness of the feature. And then there's the whole loss-of-ports thing. How much of a problem that would ultimately be for me is probably overblown since the only items I connect via USB A/B are my Time Machine and occasionally my phone—and USB C to USB A/B adapters are readily available.

It's all kind of academic at this point since I can't do anything about this for a couple weeks. Let's just call it a birthday present to myself.

Thankfully I have Ben's old 2010 MacBook to use in the meantime. After several extremely frustrating hours I think I've finally beaten it into enough submission that it's now properly syncing messages with the phone and only occasionally prompting me to enter my Apple password to validate a piece of purchased software.

Best Case/Worst Case

At Ben's recommendation, instead of taking it to Apple, I took the Mac into a local, highly-recommended shop today.

Worst case scenario is the system board. $900 including labor. (Better than what I was reading about Apple.)

Best case, $50 to simply clean the thing out.

The tech told me it might also be a simple matter of the power button being hosed. If that's the case, it's an upper case/keyboard replacement (because both items are apparently sealed to each other) at around $300, including labor. (The fact the charging light came on was a good indication the system board wasn't fried.)

Should hear something from them within 24 hours.

Fingers crossed.

UPDATE: Worse than Worst Case. Pretty much everything except the display is shot and needs replacement. Time to buy a new Mac.

At least Gazelle is giving me $185 to offset the cost of a new one a bit…