UncleJohnsBand Wrote:Then you know Windows....by nature...does not like duplicate volumes....thus the confusion that the windows API is having.
Yes, I know Windows does not like duplicate volumes. But this is not a duplicate volume, I only have one E:. The new disk does not have its own driveletter, it is mounted as a mountpoint in an empty directory (E:\Shares\Video) on the old E: drive. In the same way you mount filesystems in Unix. I am sure you already grasped this but I just want to make clear exactly what my setup is.
So if I look at the size of E: in windows (for example just by taking properties of E: it tells med size and free space of this disk (or rater the filesystem on this partition). And if I do the exact same thing on E:\Shares\Video it tells me the size and free space on the new drive. This is also what I expected EWA to do aswell, i.e. not to grab the size of the drive-letter disk and instead view the size and free space of the drive the selected folder is on. Perhaps I am one of the few people that uses this approach but it was really easy just to copy all recordings to the new drive and not having to reconfigure anything within GBPVR.
If this is a problem with Windows API I can live with it, everything is working fine. Just wondered if it was an easy fix because in that case it would have been nice. I love the functionality of GBPVR and EWA so this is not such a big thing for me.
UncleJohnsBand Wrote:Try chaninging your recordings setting in the config.xml file in the GBPVR directory to use a unc encoding rather than the mapped drive.....i.e. instead of using e:\dir\dir......use \\pcname\sharename.....
This may work.....let me know.
I will try this approach and after a test (I just viewed Properties of the share) it looks promising. Right now I have a few recordings scheduled but when they are through I will try it...