Each time I clicked Continue I got a Runtime Error and the installation crashed.
I tried 3 different machines and got the same result, and I even downloaded the installation software from the WD website. But each time I got a runtime error.
After doing a bit of research, it appears the problem was that WD didn’t populate the default Software share on the box before it left the factory, and so it just crashes!
This is what I had to do to fix it:
1. Go to the WD link below to download the zip file:
NAS35GOnboardingDevice_MBL_Duo_1.5.3.15_12162011
http://www.wdc.com/wdproducts/wdsmartwareupdate/nasduo.asp
2. Click on the Download now button
3. Save the zip file to your desktop and extract the files
4. You will then see the Software folder. **IGNORE all the other folders**
5. Open the Software folder
6. Copy all of the files in Software folder to the public/Software folder in the Duo.
Note: Delete any existing files in the public/Software folder first
So that’s is what I did – and it worked. But it took a while to do and was a pain!
So now we could run the setup again and continue with the install – this time it worked fine.
The last part is a list of 4 next step options.
Clicking on Open your My Book Live Duo option just opens the shares.
I have tried PogoPlug, which this appears to simply be a more full featured take on the same idea. The big issue was with remote access, streaming, etc. you are limited by the upload speeds of your home network. That at times was a very big and frustrating limitation.
thanks Anthony
I have a PogoPlug here for review and so will compare the two.
And I agree, upload speeds are a big issue!
I got a WD My Book Live Duo 2 days ago. Everything worked well after the instalation but suddenly the server was gone from my MacBook pro and my IMAC’s Finders. I called the technical support and he confirmed that this issue has been reported in OS X 10.6 and 10.7. This person said that they had to talk to Apple because the problem is with the OS X 10.6. Has anyone experience this issue? Any fix?
Thanks for this – I haven’t experienced this myself, but let’s hope a fix is forthcoming soon though.