2016-12-08 10:01 AEST by Arthur Barrett - We don't allow repositories on NAS devices.

If you map H: to a network share \\server\share then use the CVSNT Control Panel 'repositories' tab to 
create the repo h:\nasrepo you get the error message: "You must store the repository on a local drive.  
Network drives are not allowed."

Even if we don't want to change the support of NAS drives with repositories, there are several minor 
problems:

i) the message in the control panel should explain that SAN's are OK.  e.g.: You must store the repository 
on a local drive or on a SAN.  Repositories on Network shares and NAS are not allowed."

ii) if you try and use a UNC path the error message is confusing: "You must specify an absolute root for a 
pathname".  It should be the same as i) above or "You cannot specify a UNC Path for the repository".

iii) if the 'Name' field (alias) is empty as you are entering a UNC path, it automatically enters the double 
slash:
       //server/share/path/to/repo

Ideally it should ignore the //server/share part and just echo the /path/to/repo, or at least remove the 
double slash.  I suspect it's not easy though, because the current functionality probably relies on equating 
the character positions.  So worse case scenario we use some other character - e.g.: 
\\server\share\nasrepo would be echoed as /_server/share/nasrepo

iv) you can create a repository on the command line to a UNC path, and the 'alias' repo name incorrectly 
starts with a double-slash.  It should follow the same rules as iii) above.  It may be easier to 'remove' the 
leading server/share name from the command line than it is in the control panel.

v) we should at least consider disabling the creation of repositories on network shares in the command 
line - though I know we specifically didn't do this so we could 'force' support for customers who really 
wanted it.