@jseifer: three are SATA one i…
@jseifer: three are SATA one is PATA, so either three will work for you or one will. Other than that, what’s the warranty?
@jseifer: three are SATA one is PATA, so either three will work for you or one will. Other than that, what’s the warranty?
Our 8mo is getting his seventh tooth, no wonder he isn’t sleeping well these days
Yaya! Going to the Lego store in Downtown Disney! I just wish I was 10 again :)
It seems that there is a compatibility problem between the version of Samba, the Windows networking layer built into OSX, installed in Mac OSX Leopard/10.5 and what most NAS (network attached storage) drives use.
I discovered this when trying to get my brand new Mapower MAP-KC31N NAS enclosure to work with it - the drive works fine with Windows, and my Mac can get to the Windows machine, but the Mac cannot connect to the KC31N. The KC31N itself is based on the the “Landisk” controller, which is used in a whole range of inexpensive NAS drives and generally seems to work well, and were it not for the fact that I’m hooking it to a Mac I’d be none the wiser.
Looking around further I’ve discovered that not only is the KC31N incompatible, but a while range of other NAS drives, including more well known brands - Iomega, DLink, etc, that do not use the Landisck adapter. With all of this I’m inclined to think it’s an incompatibility stemming from the version/configuration of Samba itself and therefore something they need to fix.
So come on Apple, please fix this bug so us customers can get back to their work. How’s about it?
In the interests if keeping some data off my laptop’s main drive but still accessible, I bought a Firewire/IEEE-1394 hard drive enclosure and stuck a 120gb drive in it. Well, tonight when I plugged it in the drive, after having it roaming the house for the day, the drive wasn’t identified by OSX - the drive was on, I could hear it purring away, but it wasn’t actually doing anything. As it turns out, the enclosure is controlled by the Prolific PL3507 chipset that has reliability problems, which sucks. Amusingly, the enclosure also has a USB connector, and when I plugged the drive in that way it worked! Go figure. So, time to get realistic with this and set up a Solaris & ZFS/RAIDZ-driven NAS, to heck with this silly single-drive, single point of failure BS, lets bring on some reliability for a change.
Anyone in the Tampa region need a UNIX admin? Email ndownes@tampabay.rr.com
Note: This isn’t for me but for a friend in Tampa :)
Remember folks, there’s no point in twittering if you have nothing to twitter about.