Wine directory structure questions

Rundi · 01-03-2005, 12:23 PM

I am trying to help my brother set up Wine on his computer. I installed Mandrake 10.1 to dual boot with WinME. I downloaded the most recent rpm for wine from winehq and installed the rpm.

This is as far as I've got. The configuration process is where things stopped being easy. I've been trying to refer to the wine documentation, but the documentation is not always clear for me. So far as I've been able to determine from my reading, the installation of the wine rpm does not complete the installation process.

As best I understand I must still (1) Set up the wine configuration file and (2) set up some "fake" windows directory structure for wine to use.

A certain program called WineSetupTk has been mentioned as making setup easier. Can I use this program even though I installed from an rpm instead of source or some other method?

Finally, the directory structure questions. Does the wine rpm create the directories it requires, and if so, where are they? My current understanding is the wine rpm install does not create the directories and I must do that myself. (It seems people suggest creating these directories under the user's home directory). From my reading of the documentation it isn't clear if I am supposed to create certain set directories with particular names or if I can create directories with whatever names I want.

Should I just copy over the directories from the WinME drive?

I'm sorry if these are stupid questions, but wine hasn't clicked with me yet so I can read the documentation and half of the time it seems clear as mud.

Rundi

miko3k · 01-03-2005, 02:58 PM

wine can use either real windows OR it need a fake. winme is maybe old enough so you can even force wine to use windows native dlls to fine-tune your wine installation. there is a tool called wineprefixcrate in source distribution (i don't know about rpm) which creates following directories ($CROOT is a directory where you have your fake c drive)

"$CROOT/My Documents"
"$CROOT/My Documents/My Music"
"$CROOT/My Documents/My Pictures"
"$CROOT/My Documents/My Video"
"$CROOT/Program Files"
"$CROOT/Program Files/Common Files"
"$CROOT/windows"
"$CROOT/windows/command"
"$CROOT/windows/fonts"
"$CROOT/windows/inf"
"$CROOT/windows/profiles"
"$CROOT/windows/profiles/Administrator"
"$CROOT/windows/Start Menu"
"$CROOT/windows/Application Data"
"$CROOT/windows/Start Menu/Programs"
"$CROOT/windows/Start Menu/Programs/Startup"
"$CROOT/windows/system"
"$CROOT/windows/temp"

configuration of windows drives it done via symlinks. you must place them in ~/.wine/dosdevices (maybe there is some system-wide location too). such symlink is called same as drive (for example c

and points to directory with fake drive (for example /mnt/my_windows_drive).

actually... the best thing you should do is to grab source, upack it and type cd tool; ./wineinstall. it does everything for you

Rundi · 01-03-2005, 07:00 PM

Thanks for the reply.

Okay, I've done some more poking around. I do seem to have the directories you mention, so apparently the rpm install did that as well.

Other people have also suggested using the source, which I am willing to do if necessary. But what do you mean by "It does everything for you"? Does the wineinstall create all the symlinks, copy all the dlls and brush my teeth? I mean, there doesn't seem much point in trying to use source if I don't even know if there is any problem with my rpm install.

This is embarrassing, but I just don't know where to proceed. I don't have any error. Wine is installed. I can load up the "clock" I can load the "file manager" I can load "minesweeper" I can load "notepad" I can load the "program manager" I can load the "registery editor"

The only things I can't load are the "control panel" (it says no applets installed, of course) and the uninstaller (it says no programs installed, no duh!) Basically it seems like I have wine "running" but yet I haven't configured any configuration file or created any symlinks and I'm not entirely sure if I still need to do that, how to do that, or how to install windows programs so wine can use them. I find myself in the proverbial position of having a car but not knowing how to start it.

The winehq documentation states

Quote:

If you just installed Wine for the first time and want to finish Wine installation by configuring it now, then you could use our sample configuration file config (which can be found in the directory documentation/samples/ of the Wine source code directory) as a base for adapting the Wine configuration file to the settings you want. First, I should mention that you should not forget to make sure that any previous configuration file at ~/.wine/config has been safely moved out of the way instead of simply overwriting it when you will now copy over the sample configuration file.

If you don't have a pre-existing configuration file and thus need to copy over our sample configuration file to the standard Wine configuration file location, do in a terminal:

$ mkdir ~/.wine/
$ cp dir_to_wine_source_code/documentation/samples/config ~/.wine/config

Otherwise, simply use the already existing configuration file at ~/.wine/config.

Now you can start adapting the configuration file's settings with an editor according to the documentation below.

This has caused me no end of confusion because I have the ~/.wine/ directory but there is no config file in the directory. There is a folder "dosdevices" and another folder "drive_c" and then three files: "system.reg" "userdef.reg" and "user.reg". Thinking I would be a good little boy I copied the file "config" file from the source tree on the winehq website but using the default file only caused my wine install to stop loading.

I am beginning to wonder if those instructions about the config file were for a source install, not a rpm install. Or am I talking nonsense?

If anyone could point me as to how I should proceed it would be much appreciated. I can copy windows files to my Linux drive if that is what I should do. Or I can make a copy of windows files on another fat32 paritition (right now I have a empty fat32 parition)

Thanks again,

Rundi