BEFORE you install them you should use WINEPREFIX=<somepathhere>. A wine prefix can sort of be thought of as an instance of windows, but separate from others. In this way if something happens and messes up program "A" you can delete it without affecting others like program "B:.
So, personally, I like to keep things separate. I have 3 separate wine prefix's for what I am using right now.:
BINGO for my visual basic program for calling, etc., Bingo games that requires Windows
LEGACY for my genealogy program that requires being in Windows
GEDSTAR for a program to extract my genealogy data so I can view it on my Android device, and it requires Windows
If something happens and I mess up Bingo I can always delete it and start over without ever touching the other 2. When you just let it default, wine will put anything you install in the .wine folder. You mess up something in .wine so you have to recreate it and you lose the other programs you installed.
To create a prefix, change your install execution to something like
Code: Select all
WINEPREFIX=<some path herer> wine <installer name here>
It just requires the WINEPREFIX=<some path here> to each wine statement.
This is by far the best way to do things I think. Right now I'm just trying to help you get this running. When we get it to run then I can walk you through putting it in it's own prefix so things are separate from each other.