Difference between revisions of "WINE"
(→User Notes: note about sound access) |
|||
| Line 12: | Line 12: | ||
On the other system, things seem to run more or less properly, but the Program Manager (progman.exe, which seems to be one user-friendly way of invoking applications - "wine progman" to start it) has a character limitation in its "Execute" dialog which is too short for most programs stored in the general format "c:\program files\nameofapp\nameofapp.exe" or longer. (It is still possible to run such programs from the console, but this severely limits the usefulness of progman.) | On the other system, things seem to run more or less properly, but the Program Manager (progman.exe, which seems to be one user-friendly way of invoking applications - "wine progman" to start it) has a character limitation in its "Execute" dialog which is too short for most programs stored in the general format "c:\program files\nameofapp\nameofapp.exe" or longer. (It is still possible to run such programs from the console, but this severely limits the usefulness of progman.) | ||
| + | |||
| + | '''2006-09-08''' Adding a user to the group "dip" seemed to enable WINE to access the sound system one time when it complained that it could not (on Ubuntu Dapper). This could have been a fluke, however, and I have not confirmed it. Used {{linuxcmd|usermod}} to make the group assignment. | ||
Revision as of 20:32, 8 September 2006
WINE is an acronym for WINE Is Not an Emulator. It is a FOSS program which provides a Windows API so that Windows programs can run under Linux. (This is consistent with some definitions of the word "emulator", despite the acronym.)
|
This page is a seed article. You can help HTYP water it: make a request to expand a given page and/or donate to help give us more writing-hours!
|
Links
- WineHQ: official homepage
How To
- winecfg
- is the GUI-based configuration applet for WINE; it is generally not set up in a KDE menu, so you have to run it from the console.
- wine program_filename[.ext] parameters
- runs a program in WINE. When WINE is installed, it will usually configure the window manager (KDE, Nautilus...) to recognize Windows programs and execute them with WINE, but if you run it from a console you will see any error or warning messages coming from WINE.
User Notes
Woozle
These are problems I have run into trying to use WINE on two different systems.
On one system, nothing will run; this appears to be because no drives are configured. However, when you run wineconfig and attempt to create some, an error message on the console says "unable to define devicename of 'C:', targetpath of '/'" (using the autodetected value "/" for C:'s path, but I tried one or two others and got the same results). On exiting and reloading winecfg, any values which were created are lost (so apparently they are not being saved).
On the other system, things seem to run more or less properly, but the Program Manager (progman.exe, which seems to be one user-friendly way of invoking applications - "wine progman" to start it) has a character limitation in its "Execute" dialog which is too short for most programs stored in the general format "c:\program files\nameofapp\nameofapp.exe" or longer. (It is still possible to run such programs from the console, but this severely limits the usefulness of progman.)
2006-09-08 Adding a user to the group "dip" seemed to enable WINE to access the sound system one time when it complained that it could not (on Ubuntu Dapper). This could have been a fluke, however, and I have not confirmed it. Used usermod to make the group assignment.