I report success.
The solution addresses the use of
Virtual Box on Ubuntu 18.04 LTS.
For my kickstart, I was using tips linked
HERE and
HERE.
Here is the process, for the record:
0. Manually create a
Timeshift system image; check your settings for it to be inclusive.
1. Install
virtualbox and
virtualbox-ext-pack packages from the Ubuntu repository.
2. Open up the Terminal seal and unleash the following incantation:
sudo usermod -a -G vboxusers $USER3. Logout and log back in, to complete the ritual.
{I know this step is required probably due to some security concerns with the extension pack suite of features, but it is so much voodoo people and infact so much Linuxy that it is just idiosyncratic.}
4. Open up
Virtual Box.
5. Click the big "New". The
Virtual Box will guide you through the creation process of your desired
Windows environment. Mind you need to know what kind of
Windows image file you have, including whether it is 64-bit capable or 32-bit only. Under the first link provided early in this post, there is a download link to a
Windows 10 image file, apparently available also for free under the terms of running a non-activated
Windows version.
In case you have trouble setting up a virtual machine, seek further guidance, for example, ask on the forum.
In my case, I have given the 64-bit virtual machine some 5~6 gigabytes of RAM {my majority} - knowing Linux will cope with smaller amount, eventually using the swapfile*, when the
Virtual Box claims given sum - also have I enabled 2D and 3D acceleration with whooping 256 megabytes of video memory, access to more than one CPU {infact, both of them}, paravirtualization interface set to default, USB controller at version 3.
* mind to have swapfile properly configured, in order to avoid applications possibly shutting down, which could affect also the
Virtual Box.
6. Crucial step. Start your GPS device and plug it into the USB slot. Under the "Settings", go to the "USB" section and to the right of the "USB device filters" {the big text field}, click the second icon counting from the top {the one with a plus sign}, which in self description, says: "adds new USB filter with all fields set to the values of the selected USB device". Find something relating to
TomTom, Sat-Nav, GPS or alike among the options and pick it up. Save the settings.
7. Install your
Windows.
8. Through the web-browser, download
MyDriveConnect for
Windows and install it. Mind to unplug your GPS device beforehand and have it plugged back in not sooner than having the installed application already running.
Should be done.
9. Just for the trick, some people - including myself - had reported
MyDriveConnect getting broken in the aftermath of a big map update. There is one simple thing to do after each big map update in order to solve. Go to your
%localappdata% folder, find "TomTom" and delete the entire "HOME3" directory. It will reset your
MyDriveConnect settings but is confirmed to work. Alternatively, in the
Windows taskbar, find
MyDriveConnect tray icon, rightclick, pick up "Settings", head to the downloads section {third tab} and press to clear the download bin or how is it called in your language. Might work.
PS:
Regarding point number six, there could be couple of detected active USB devices. Mind when a USB is claimed temporarily by the
Virtual Box, it is usable only within the virtual machine for the time and unavailable for the major background system. In my case, for example, I use a bluetooth mouse, but it seems to have been hooked under a USB type of connection, therefore, when selected, the mouse responded only within the virtual machine during the operation. That is only a minor nuisance to watch out for. The bigger problem is that there appeared also a second type of USB device which if selected, renders the virtual machine permanently stuck on a black screen, chocking up the entire
Virtual Box application apparently beyond any easy fix. That is why did I recommend to make a
Timeshift image, so that not to bother with trying to manually untangle the knot but to revert and start over - following a hard reset, preferably. I speculate that this quirky "USB" thing could be a kind of umbilical cord, connecting the virtual machine with the major background system resources, so that when selected, the connection becomes interrupted, disallowing any action on the virtual machine to be performed, as well as depriving the virtual machine from the access to necessary computational supply.
