I have not really played with this much but if I do a

subst P: C:\temp
Start the pogolug drive and it grabs Q:
Run Subst P:\temp /d and remove the P: drive Pogo stays at Q: and I receive no errors access it.

Maybe the Pogoplug is rebooting overnight and losing its connect or something?

Place Shifting Enthusiasts

I am using ver 1.0.0.16, but unfortunately Map Network Drive crashes a Vista Home Edition PC.

The good news is that Pogoplus boots to R: drive as I already have P: & Q: drive assigned.

I then share R: drive as "Pogo"

When I use the "Map Network Drive" I get a blue screen of death :-(

This happens every time so it would be good to know if this is a reported bug.

Obviously a good workaround would be the ability for the pogoplus to assign a drive on boot.

Hey Baldwig,

As I'm looking at this, I think I see your problem - you can't actually share the whole R: drive - you have to share the service (corresponding to the partitions on your drives) one by one. I have successfully set up mapped network drives for my drives between Vista and XP, transferred files, done syncing and backup, but trying to share with the whole of the P drive won't work for the same reason's you cannot defrag the P (or in your case, R) drive - http://www.pogoplugged.com/forum/thread/11675/Defragging-Drive-P/ for more details.

hope that helps!
Jon - QA, Cloud Engines

Update on my BSOD issue:

I changed the Pogo PC program to run on an old XP Pro PC and managed to do the tasks above without a crash. I guess it must be a Vista issue !!

HOWEVER - the sporadic PogoPlug Drive assigning issue is still happening on XP.

:) I hear a feature request coming out of this thread.

Jon.QA said: Indeed :) the feature request I have listed is "user assignable drive letter for Pogoplug service" - sound about right?

Any idea if this will make it into version 2.xx of the driver?

This is indeed very important as a lot of people are using Pogoplug as a remote sync target.  

Hope to see this feature soon.