1. Blacktron Fanand Music Pants = 6LKMNDHR
2. Robo Pilotand Astro Pants = 6LK3RRY4
3. Frog
4. Grapple Guy (nerdyboi) Mac Os Catalina
5. Rabbit

View Mohamed Isa Hashim’s profile on LinkedIn, the world's largest professional community. Mohamed Isa has 3 jobs listed on their profile. See the complete profile on LinkedIn and discover. The last standalone driver Digidesign produced was for Mac OS X 10.5 Leopard. Is there any way I can get this device working with OS X 10.7 Lion? It just seems like a waste to have perfectly good hardware without even open source driver support. New Mac OS X 10.5.6 test build has over 90 fixes — Apple seems to be making a fair bit of progress on the upcoming Mac OS X 10.5.6 update. This week, the company released a new test build of the package to its update testers. Apple released Security Update 2008-002 yesterday and this led to a problem for some users on Mac OS X 10.5 using our Instant Hijack component. The Instant Hijack component is optionally installed by Airfoil, Audio Hijack Pro, and Nicecast, and enables these applications to grab audio from applications that are already running. Feb 03, 2007 When the Mac OS died with its antiquated architecture, they bought Jobs start-up company NeXT, which made a GUI based on the Unix BSD core. Which is why Macs don't crash. Word misbehaves and dies, and a message tells you it died and that your other programs are fine. When Vista comes out, it will have some of this stuff.

UPDATE 2/24/2017:I’m back with drobo!When I originally wrote this post, 5-years ago, it was definitely with a different “drobo” — as a company, and “drobo” as a product. Last year I met with their new CEO Mihir Shah and I was able to fully “air my grievances” and the grievances of many drobo users at the time, even though none of it happened on his watch.

Mihir is the opposite of what I experienced before — he’s a CEO obsessed with customer service and their experience with drobo. He personally called over 500 drobo users last year to talk one-on-one about their drobo experience and what they can do to make it even better (btw: when was the last time a CEO of a big company called to ask you what you think?). Anyway, he convinced a very skeptical me to give them a 2nd chance, which I did over six months ago (I didn’t want to write about it until I had a good amount of time to evaluate the units — one at home, and one on my desk at the office, which is seen here where I’m posing with Mihir).

I’ll have a full review of their latest units coming soon, but they have updated the policies that I had written about below (which I felt were vastly unfair and needed addressing at the time), and more improvements along these lines are on the way, but I now see Drobo, their products, their customer service and their leadership in a new light, and I felt this post needed an update. More soon.

I’ve finally reached the point that I’m done with my drobo, which I use for the archiving of my photos. I actually use three drobos: one in my office, one in Brad’s office (onsite backup), and one at home (offsite backup). Now sadly I’m going to have to move to a different platform altogether because drobo finally pushed me to the point of no return.

What I love about drobo
What drew me to drobo in the beginning was the fact that it constantly monitors the health of my hard drives. So if one starts going bad, or gets full, my drobo will warn me, and robotically shift my data to other drives installed in my drobo until I can replace that drive. Keeping a photo archive intact is very, very important to us photographers.

Why I’m done with drobo
Because for the fourth time one of my drobos is a brick.

Wait, are all the hard drives installed in my drobo still working? Yup. Can I access my photos? Nope. Not a one.

When I came into work a couple of days ago, I cringed when I saw an all too familiar problem — my drobo cycling on/off over and over again. It doesn’t mount, and I can’t access my photos — essentially it’s a brick. Again. (see the video of my drobo below, and you’ll see it cycling on/off in what we now call “The drobo death spiral.” Note: This is not an exciting video).

Scott, can’t you just pop those drives into something else and get your photos back?
Nope. It’s a proprietary system that only a drobo can read. Sigh.

I went to their site, followed their troubleshooting guide, and it still just cycles on/off (by the way, as I mentioned above, this isn’t the first time this has happened — drobo has had to replace my entire drobo unit [not including the drives] before).

In fact, this was the fourth recorded incident Brad and I have had with drobo so far. And while you’re waiting for your new drobo, you cannot access any of your photos or files on your bricked drobo. You’re basically locked out.

This is the moment that I knew I was done with drobo
When my photo assistant Brad called their tech support for me, they told him my dead drobo is out of warranty. To get my photos back, I would have to pay nearly $300 for drobocare (an extended warranty program). So basically, while my drobo is supposed to protect my photo archive, what it has actually done is hold my photo archive hostage for almost $300.

I know what some of you are saying right now: “We told you so.” When Brad told drobo how supremely unhappy we were with that $300 hostage-situation, they eventually emailed back and lowered the price to $100. We passed on the “deal.”

At this point, I’d rather give that $100 to you. Seriously.
Rather than sending $100 to drobo on a solution that I’m going to abandon shortly, I’d rather just give the money to you to help me find a better solution.

To that end I’m offering a $100 bounty to whomever can help me choose a new photo archival storage system now that I’m “dumping drobo” (by the way, that would make a great slogan for a t-shirt).

I need about 12 TB of storage, which sadly may be conservative thanks to my 36-megapixel Nikon D800 which eats up drive space like a plague of locusts.

Just leave me a comment here with any advice you have for big storage, and if I go with your suggestion I’ll cut you a $100 check for your time and research (I’m only doing this for one person, so if 50 people say “try dropbox” I’m only cutting one check to one person. Just so you know).

Blacktron Fanand Music Pants = 6LKMNDHR

My plea to drobo
I’ve been using drobos for a few years now, and have recommended them to a number of my personal friends. A lot of photographers out here have drobos, and we count on drobo to keep our images safe. But obviously there can come a point where our hard drives are actually OK but our drobos have failed.

Robo Pilotand Astro Pants = 6LK3RRY4

If the drobo is a truly well-made product, shouldn’t it work reliably for more than a year? We don’t expect it to last 20 years, but it should darn well work perfectly for at least two or three. In short, drobo (the company) should have enough confidence in their technology and their product to stand behind their product for more than 12 months

My plea to drobo is simple… If our drobo’s power supply goes bad, or our drobos won’t mount, or whatever the problem is (unless we caused it by immersing our drobo in water, or dropping it off a counter, etc.) — we need you to replace it free of charge for a more reasonable amount of time than just one year. Otherwise the whole thing is worthless. Like my drobo is now.

So, that’s my story
While I love a lot of things about the drobo (the industrial design, the idea behind it, and the ability to easily swap drives in/out as needed), I hate that often I can’t get it to mount (ask Brad about this one). And worse than that, I can’t have a solution that protects me when all is well, but when it gets a cold (which it clearly often does), it locks me out and then holds me hostage. That I can’t live with.

UPDATE:I wrote this Wednesday night and planned on releasing it today, but when I went to save the post as a draft, I accidentally released the post instead (not the first time I’ve done that sadly). Even though I immediately changed the post release status as soon as I realized the mistake, by Thursday morning news of it was already bouncing around the web, and it quickly made it’s way back to drobo. They contacted me directly to see how they could resolve the issue and I even talked with drobo’s CEO a number of times during the day. He really seems like a very down-to-earth guy who seems genuinely interested in addressing his customer’s issues, but of course just fixing my problem won’t fix the bigger problem of their warranty policy, so I once again declined. However, to his credit he listened to my ideas (and rants) about how drobo might address this going forward so other photographers that get in this situation might be protected, and I even offered him the opportunity to respond directly to my readers here on blog. Hey, it’s a start. :)

When Apple first released a developer preview of OS X back in 98/99 (IIRC) I actually emailed Jobs about using OpenSSH in the new OS (there was a lot of controversy about the munitions export act in the USA, and I was involved in the OpenSSH project - he said that they would be distributing OpenSSH, which was a big win at the time - anyway I digress), I also asked about POSIX compliance.

He said in his reply (and I wish I could find it) that POSIX compliance was a big deal for OS X, and part of the reason why so much of the FreeBSD userland was being used (I was also involved in some parts of FreeBSD at the time - there was a whole initiative around making it fully Posix compliant, way before any other free UNIX).

Frog

I knew some of the history with Next and POSIX, your comment tied the story together for me. It does show that Jobs learned his lesson when he went back to Apple.

Grapple Guy (nerdyboi) Mac Os Catalina

Now more on the topic at hand. Apple need to handle security issues better. Not just in terms of disclosure but in response times and communication with the industry. You don't see many/any Apple reps at the major conferences, and no engagement at all. It was always generally known within the industry that Apple owed much of its OS X security to the fact that it just wasn't a big target. The commercial UNIX releases and Linux were targetted because they ran the worlds servers, and Windows was targeted because it was the worlds desktop. Now with OS X gaining market share they are getting more attention from sec experts and hackers.

Rabbit

Microsoft reformed their security policies back in 2000, after IIS 4 had a horrible run and the code red worm ran wild. Many top security and secure coding experts went to work at Microsoft at the time - it was a major shift (implementing security checks in every step of the dev process across the whole company). Apple have only had to do this more recently, and they haven't really perfected it.