Thank you all for testing.
The xml project is for passing information absent in g-code to the CAMotics. Now it is a table of used tools, stock dimensions and sim resolution. Maybe a something else in the future as the CAMotics will develop.
If there are a tooltables synced between CB and CM, and correct stock size is of no interest, .nc will suffice )
Regarding the error:
I doubt one could launch native app (external to to vm) from the virtual machine.
cb2cm.config is stored in CamBam's system folder (Tools->Browse System Folder).
Upon CB startup, plugin tries to detect CM executable in location specified in config, else looks in some common locations (Program Files ...), else tries to find a running windows process named 'camotics' and determine the path it was started from. Detected location is stored in config for the next run.
e.g. my config entry is <camotics_path>D:\winp\app\camotics\camotics.exe</camotics_path>
Thanks for suggestion of pathless .nc files - it is a right way. Fix will follow )