binaryfactory.ca

Weird bug. Switching the USB port in use fixed it. iPad 2 with Lion, iOS 4.3.5.

First, you buy a LaCie D2 drive. You’re excited.

My new Lacie D2 Network drive is Time Machine compatible. That means it’s really easy to setup with Time Machine – no hacks required, it just gets detected.

LaCie D2 Network – Time Machine

Then, you get blamed for running a .exe from a share on it. That exe was the MS Office installer. Why was that a problem? EXEs are not compatible with the drive’s operating system !

It was related to running the .exe file on the drive.  The file is proprietary to an OS such as XP, Vista, or Mac OS X.  Running the file on a non-conforming OS is going to create severe havoc and other issues.  I am glad the reset resolved the issue.

Lacie Tech Support doesn’t know what a share is

And then, you ask them about firmware updates to fix some small issues here and there, and this is what they tell you, barely over a year after you bought it:

Since this type of unit is no longer made, it’s unlikely there will be any further firmware updates for

So am I surprised that my piece of junk Lacie D2 NAS does not support the latest AFP protocol required for Time Machine?

Of course I’m not. But who cares, it’s not like I trusted the thing as my main backup anyways.

Cause: The LaCie NAS OS does not support Time Machine with Mac OS X Lion.
Solution: Use Mac OS X 10.6.x or earlier when using Time Machine to back up your Mac to a LaCie network hard drive.

But I’m sorry. The solution is actually to buy hardware from a company that at least pretends to give a damn. Apple should be ashamed of allowing this junk in an Apple store. I don’t care how cool your USB sticks look or how fast your Thunderbolt drives are, LaCie, I’d rather use old Sony 1.44inch floppies. Oh, and I called my D2 “Lassie”, cause it runs like a dog.

1. Back up your SHSH blobs using Tiny Umbrella. That’s unrelated but you should do it at every firmware release anyways.
2. Check your hosts file and comment out entries for gs.apple.com (I forgot to do this, as I always do)
   

   Comment out ALL entries for gs.apple.com

3. Dev-Team Blog – Download redsn0w (you may permanently lose ability to unlock if you use redsn0w, as usual)
4. Back it up !
5. Update it in iTunes using the update button. For a cleaner result use restore. I  can’t vouch for how good the update is on this one, as I had to do a restore after I forgot to do step 2..
6. Eat a snack as iTunes restores your phone. If you have authorization issues be sure to check your hosts file for entries entered by Tiny Umbrella, and kick yourself for not following step 2.
   

   This is usually caused by authorization failures

7. Once the restore of the firmware is done, close iTunes before restoring the backup. That way, if the Jailbreak fails, you haven’t wasted time restoring data.
8. Run redsn0w
9. I recommend eating fat-free cheese as you wait as it is a healthy snack that will leave your fingers relatively grease free.
10. Run Cydia twice (1st time will prepare the filesystem, second time download package info).
11. If there are any updates to be done, go for it.
12. Launch iTunes and restore.
13. Go to sleep as iTunes compresses the gigs and gigs of music that were on your phone before you ruined it all.

If you want to keep your old AppleTV simply because you don’t want to pay for a new one or because you love having storage to keep your files available, check Remote HD out..

If you “jailbreak” your AppleTV, you can then install their Airplay module on it. To activate it (license), you connect to it using the Remote HD App on your iOS device.

I’m not sure how long it will be until Apple finds a way to block it from theApp Store. It is pretty expensive now but it is a useful app, and sure is cheaper than an AppleTV 2.

Instructions quoted below can be found at http://www.remotehd.com/AppleTV/Download

If you are not using the latest Apple TV Software (version 3.0.2), update the Apple TV software from Settings > General > Update Software.
Unlock your Apple TV using opensource atvusb-creator.
Step by step instructions can be found here and here.

Connect to your AppleTV using your preferred SSH client:
Host: appletv.local
Username: frontrow
Password: frontrow

Recommended SSH clients are:
OS X: Use the buit-in SSH command line client using Terminal.app
Windows: Putty Download putty.exe from here

Here’s an example of how to connect to the Apple TV using Terminal.app on OS X:

ssh frontrow@appletv.local
Password: frontrow
Once connected, run these commands one by one.
These commands will download, uncompress, install/upgrade Remote HD plugin and restart the Apple TV interface.

scp ssh.remotehd.com:RemoteHelper.tar RemoteHelper.tar
tar xvf RemoteHelper.tar
./install-RemoteHelper

“frontrow” without the quotes is the default password.
If prompted with a security prompt to confirm connecting, type in yes.

Thats it, you’re done! Now grab your device and have Remote HD scan for available connections. Your Apple TV should show up in the list of available WiFi-connections – just tap to connect!
The default password is empty.

To get facetime working on your firewall you need to be sure some ports can be used. For most home users this won’t be a problem but it may be different at work. Here is the Apple KB Article on it :

http://support.apple.com/kb/HT4245

If the Wi-Fi network router that you are connected to uses a firewall or security software to restrict Internet access, contact the network administrator and reference this technical article. To use FaceTime on a restricted Wi-Fi network, port forwarding must be enabled for ports 443 (TCP), 3478–3497 (UDP), 16384–16386 (UDP), and 16393–16402 (UDP).

Make sure those UDP port ranges have a good priority in your QoS configuration and you should be good to go. It is worth noting that DNS and HTTP must be open to the outside as well, but they are probably used only to establish the call (same for HTTPS/443) so the QoS config should not matter.