ObjectDock / ReadyNAS Duo "conflict"

ObjectDock now takes at least 5 minutes to load.

As the title reads; since I added a shortcut to my ReadyNAS storage device, ObjectDock takes several minutes to load, and is completely unusable until then. This only seems to happen when the ReadyNAS is switched off, and I assume it's because with it being a network device, the shortcut is essentially pointing to something that "doesn't exist" or is not responding due to its (currently) power-off state?

Anyone else have this combination of NAS storage with a shortcut to it placed in ObjectDock?

2,598 views 4 replies
Reply #1 Top

This only seems to happen when the ReadyNAS is switched off, and I assume it's because with it being a network device, the shortcut is essentially pointing to something that "doesn't exist" or is not responding due to its (currently) power-off state?
End of quote

It would be just like clicking on a unplugged drive in explorer......it takes about a minute of "looking" to come back and tell you it's not there. I'd suggest making a menu style link to "My Computer" and navigate the extra step to avoid the delay at startup.

Reply #2 Top

That doesn't work either though - the NAS doesn't show up in My Computer, only in My Network Places. If there's a way to make a shortcut to that instead, I'll certainly try it. At the moment, my shortcut to the NAS is "\\192.168.x.x\". Any idea what the shortcut syntax would be to My Network Places?

Thanks for the reply - I'm sure there's a way around it.  :thumbsup:

Reply #3 Top

I think a link to network places will likely result in the same delay you're already seeing. Try mapping it and see if it shortens your wait time.

Reply #4 Top

Oops! Sorry, I forgot to reply to this. I did finally find a workaround, and it involved the "Folders with names" docklet. I just added a new Folders docklet, included the IP + path info as a destination, and it works a treat! No more 5 minute wait while it figures out whether it's reachable or not...

^_^

 

Thanks for the help Lantec. Drive mapping was going to be the next step, had this not worked.