F:/Partition_LocalUsr 0
disku d:\\mydata\\myscolpart 0
is also possible
the order of the partitions in the usm.ini determine the partition priority for file read / write
]]>cache ./Cache 256
disku ./Partition_LocalUsr 0
diska ./Partition_LockedApp 0
logsp ./Logs 0
The number at the end of every partition line is the maximal amount of data that you can store (in Mo i think) on a partition, 0 meaning that there's no restriction of size.
As you can see, every directory is "relative" to a default location: "cache" and "logsp" are relative to "C:\Users\UserName\AppData\Local\Scol Voyager", "disku" is relative to user document directory (default: "C:\Users\UserName\Documents\Scol Voyager"), and "diska" is relative to Scol installation path (default: "C:\Program Files\Scol Voyager").
So, as you can see, a problem could append when changing the user partition "disku" to another drive, as apparently, it uses a relative path to a default location that is under "C:\". Anyway, you can try to change "disku" with a full path ("d:\toto\tutu") to see if it works, but i did not test this manipulation.
Another solution could be to create a "symbolic link" (if you are under win7), using the command "mklink" (with "/D" option for a directory) on the command line.
yes you can copy or move the scol voyager any where you want, just launch the scol.exe after that to register the new path
you can also move partitions by editing the usm.ini file