Wine-portable: where are stored configuration files in pupsave?

[Dingo]

I'm using wine-portable

viewtopic.php?p=279#p279

Very successfully with my pupsave on a USB drive formatted in VFAT

recently I bought a new USB own that I formatted in ext2, then I copied the whole content of old USB pendrive into this.

No problem apart for wine-portable. There are some windows executable that show an UI in Greek characters, while the same executable, when running in old pendrive, presented an UI in English.

I also get an erratic error of wine executable not found, so, I would reinstall from scratch wine-portable.

Knows anyone where are stored the configuration files for portable wine In pupsave? In order to delete these

[mikeslr]

Other than icons in /usr/share/pixmaps and desktop files in /usr/share/applications, registering wine-portable only write ones file to your system, a bash-script: /usr/bin/wine.sh.

wine.sh is a complex script. If you can figure out exactly what wine.sh does beyond mounting the wine.sfs in the wine-portable folder, you know more than I.

I suspect, however, that something went wrong in your copying from one USB to the other. And I wouldn't use Linux Ext2: too prone to corruption, especially as your 'Windows' programs will be doing a lot of reading and writing from the USB-Key. I run wine-portable 3.3 without a problem from Linux Ext3 partitions on USB-Keys and hard-drives. But I'm not sure I ever copied the /wine-data folder, into which non-portable programs are installed and configured. In /wine-data/drive_c/windows you'll find the equivalent of Windows registry.

The first thing I'd try is to uninstall the windows programs displaying the faulty characters and then reinstall them. If that doesn't resolve the problems, I'd format the USB-Key as Linux Ext3, and start from scratch.

[bigpup]

The principal advantage of using wine-portable is if you employ a SaveFile. Under Wine, window programs are installed into a "false drive_c". Wine-portable is located outside of "Puppy-Space" and only linked to Puppy via a few files. Consequently, its drive_c does not occupy space in your SaveFile: only the size of the partition it is on determines how much space can be occupied by Window programs. It provides this lesser advantage if you are using a SaveFolder in that the entire Wine-portable folder --including any programs you've installed-- can be moved or copied to a different computer without having to re-install programs. Additionally, the same wine-portable can be used by many Puppies (and debiandogs) on your computer.

Have you looked in the wine-portable directory?
This seems to say everything is going to be in it.

I copied the whole content of old USB pendrive into this.

How you did this could be the problem.
So how did you do it?

Note:
Rox file manager has a issue in copy and paste of very large amounts at one time.
It will seem to complete, but it still has stuff in the cache that is still being written to new location.
This will happen with USB drives for sure.
If the USB drive does not have an activity light that you can see turn off when complete.
Give it a minute or two to fully complete after Rox stops showing activity.

[Dingo]

I copied the whole content of old USB pendrive into this.

How you did this could be the problem.
So how did you do it?

I was aware of this bug, so, after copying was completed and rox window disappeared, I typed sync in a terminal window in order to be safer, but I'll be carefully in checking what can be happened

[Dingo]

@bigpup @mikeslr
After some experiments, I think my fault was copying whole wine portable folder with all programs installed. Unpacking a fresh wine-portable application and reinstalling programs, works without issues.

I had a problem with wine executable not found, even if wine.sh was in right place in /usr/bin, but I found a workaround using the full path for wine portable executable in

Set
Run action

For now everything works in this way and it allows to me to have enough time to find the cause of this issue

[mikewalsh]

@Dingo :-

Actually, copying the entire thing shouldn't present a problem at all. That is, after all, the whole point of a 'portable' application; not only can it be 'portable' by means of installing it to a USB stick - in which case it can be physically moved from one location to another - it can ALSO be considered 'portable' because of the ability to move / copy it electronically, from one drive to another.

Your issue was most likely due to file corruption during the copy process - Ext2 is not really recommended these days, since flash drive life-spans are far greater than they used to be. And what bigpup was saying about the delayed drive 'caching' effect probably didn't help, either.

Mike.