Hi! The Red Cross Rescue team on Tyrifjorden in Norway are working with maping A river, and we are going to buy the program. But can we after the project is finnish transfer the licens to an other PC? We are using an PC in the SAR boat now, and want to use another PC in the office from the autum.

Hi,
This is no problem - you need to deactivate the license on the old computer using the Deactivate License button in the "About Reefmaster" window, and then reactivate on the new computer. You can in any case activate ReefMaster on two PC's simultaneously, so if you are working across two computers you won't need to deactivate the first one.

One issue with moving workspaces between computers is that ReefMaster expects sonar log files to be in the original location from which they were imported. Whilst it is possible to locate each file individually when prompted, it is usually easier to copy sonar logs to the new PC in the same location that they were originally stored - e.g. if your sonar logs were in C:\sonar_logs, then create the same folder on the new PC and put the existing logs there.

Matt

Som Matt sier går det helt fint Thor. :) Jeg bruker selv en laptopp i båten, og en annen hjemme.

Thanks to you both for the quick reply ;-)

Matt wrote: I am running ReefMaster Pro in a VirtualBox guest from a Linux host. I plan
to put my workspace folders on a shared host folder and use git as a change
management tool. I think it would be good to keep the tracks and any other
asset files in the workspace folder along side the rmdb file.

/my_workspace/
/my_workspace/.gitignore # file for git
/my_workspace/.git/ # local git repository folder
/my_workspace/my_workspace.rmdb
/my_workspace/sonar_logs/
/my_workspace/sonar_logs/t1.sl2
/my_workspace/sonar_logs/t2.sl2

Can you think of any issues is this scheme?

cootcraig wrote:
Possibly the UNC paths for

/my_workspace/sonar_logs/t1.sl2
/my_workspace/sonar_logs/t2.sl2

will be an issue. I think the full path to
the host shared files would be

\\vboxsrv\rm\my_workspace\sonar_logs\t1.sl2
...

It shouldn't matter where you store your sonar log files, and UNC paths should work just fine.
The issue is still what happens when sonar files are moved, or a database is moved to another computer. At the moment, we only have a way of reconnecting sonar log files one by one, and this is rather tedious. If you have a better suggestion, then I would be interested to hear it. One possibility is some kind of "root" directory that can be updated, with relative paths to sonar logs retained. This mechanism would also work in the case where all files are located in a single directory.

Matt wrote:
The relative path is what I was thinking, since I plan to place the sonar log files into a sub/relative directory.

I think this would be the easiest solution, I'll look into it. The way it could work is to scan all imported sonar log files and look for the highest common directory ancestor in the existing paths. This could then be replaced.

For now I'm afraid you need to ensure that the log file paths are identical, or else update each track manually (or reimport them all, of course).

Matt wrote:
This is working for me. All the files are on a host shared folder. Here is the workspace file:

\\VBOXSVR\reefmaster\Runyon_Lake\Runyon_Lake.rmdb

And here is one of the sonar log files:

\\VBOXSVR\reefmaster\Runyon_Lake\sonar_logs\Chart 09_08_2015 [0].sl2

I can easily reproduce this path on another virtualbox host if needed.