Salvage old data?

[Beartooth]

For years, I could install, and sometimes run, legacy private map
software under Wine. But in order to connect it with my GPSs, I had to
keep a separate hard drive with XP, and do that there.

Then came a brief time when I could also actually make my Garmin
GPSs talk with the software under Wine. I transferred all my data to it,
and gleefully wiped XP off my machine.

Then the connecting failed again, and has continued to. Recently,
however, I've installed virtual XP under VirtualBox in Fedora Linux 14.
Once again, my GPSs talk to my software. However, I deleted much of the
old data off the GPSs to make space for new, and have it preserved only
in the old Wine files.

Is there an easy way, (preferably with a web site to walk the
subtechnoid through it!) to copy those old waypoints, routes, tracks, and
even maps into the files of the virtual XP??

--
Beartooth Staffwright, Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.

[John Drescher]

On Sun, Jul 24, 2011 at 1:57 PM, Beartooth <[email protected]> wrote:

       For years, I could install, and sometimes run, legacy private map
software under Wine. But in order to connect it with my GPSs, I had to
keep a separate hard drive with XP, and do that there.

       Then came a brief time when I could also actually make my Garmin
GPSs talk with the software under Wine. I transferred all my data to it,
and gleefully wiped XP off my machine.

       Then the connecting failed again, and has continued to. Recently,
however, I've installed virtual XP under VirtualBox in Fedora Linux 14.
Once again, my GPSs talk to my software. However, I deleted much of the
old data off the GPSs to make space for new, and have it preserved only
in the old Wine files.

       Is there an easy way, (preferably with a web site to walk the
subtechnoid through it!) to copy those old waypoints, routes, tracks, and
even maps into the files of the virtual XP??

I think this is more of a question for the software vendor than wine.

John

[dimesio]

On Sun, Jul 24, 2011 at 1:57 PM, Beartooth <[email protected]> wrote:

              Is there an easy way, (preferably with a web site to walk the
subtechnoid through it!) to copy those old waypoints, routes, tracks, and
even maps into the files of the virtual XP??

I think this is more of a question for the software vendor than wine.

If I understand correctly, it's a question about how to copy files from the wineprefix to the VM. The answer is, the same way you would copy any other file from the host to the guest. That's not a Wine question; ask your distro or a VirtualBox forum.

[Beartooth]

On Sun, 24 Jul 2011 15:37:48 -0500, dimesio wrote:
[....]

If I understand correctly, it's a question about how to copy files from
the wineprefix to the VM.

No. Not remotely. I could do that, if it were all. My bad.

I need to know *what* files to copy, and especially whether
anything in any of them might be the cause of my lost ability to
get the GPSs to talk to the software.

I do have one clue whether the loss of this ability came from
something in Wine, or in Garmin, or what. That is that the new installs
on the virtual XP under VirtualBox came from the exact same CDs and DVDs
as the ones that so soon failed under Wine. (That's why it seems good
sense to ask here.)

For instance, if I make it a point *not* to copy any .exe files,
am I then safe?? How about .ini? .sys? .Ink? .wix?

How about folders that have one or more .exe files several levels
down? Ditto for scripts?

Is there any way, especially any canonical way, to find out why a
program that once worked under Wine ceases to work? Or to specify that
any .zzz file (for some zzz), and only such files, can be map data, and
therefore harmless at worst?

I don't think it could be file corruption, because I tried the
same things on at least four PCs. All worked at first, and all soon
ceased to. (I'm the only user in this house of GPS software, and can't
use it on more than one machine at a time. Garmin understood that when I
asked.)

--
Beartooth Staffwright, Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.

[John Drescher]

       I need to know *what* files to copy, and especially whether
anything in any of them might be the cause of my lost ability to
get the GPSs to talk to the software.

Ask Garmin that.

       I do have one clue whether the loss of this ability came from
something in Wine, or in Garmin, or what. That is that the new installs
on the virtual XP under VirtualBox came from the exact same CDs and DVDs
as the ones that so soon failed under Wine. (That's why it seems good
sense to ask here.)

       For instance, if I make it a point *not* to copy any .exe files,
am I then safe?? How about .ini? .sys? .Ink? .wix?

       How about folders that have one or more .exe files several levels
down? Ditto for scripts?

       Is there any way, especially any canonical way, to find out why a
program that once worked under Wine ceases to work? Or to specify that
any .zzz file (for some zzz), and only such files, can be map data, and
therefore harmless at worst?

Updates to wine could have broken your application.

       I don't think it could be file corruption, because I tried the
same things on at least four PCs. All worked at first, and all soon
ceased to. (I'm the only user in this house of GPS software, and can't
use it on more than one machine at a time. Garmin understood that when I
asked.)

When you talked to them did you ask them how to copy the data? The
wine user forum is not the place to ask how to copy / export / import
data from applications to other installs of the same application.

John

[dimesio]

Is there any way, especially any canonical way, to find out why a
program that once worked under Wine ceases to work?

http://wiki.winehq.org/RegressionTesting

Or to specify that
any .zzz file (for some zzz), and only such files, can be map data, and
therefore harmless at worst?

As John said, ask Garmin.

[lahmbi5678]

You could try to find out, which files Garmin software uses to store data and copy them over.

Regression testing is quite some effort, but might yield the exact patch(es) that broke the communication, with that information you could file a bug, and hopefully the regression would be corrected in future wine versions. That would probably be the best solution.

But there might be a much simpler way. Did you try to install older wine versions? Depending on your Linux and package manager this should be quite easy. Even if regression testing is to hard for you, you still could file a bug, pointing out, which wine release broke your software.