Difference between revisions of "Talk:Wine"

From ArchWiki
Jump to: navigation, search
(use https for links to archlinux.org)
(new discussion: cd to EXE's dir before running?)
Line 1: Line 1:
 +
== cd to EXE's dir before running? ==
 +
<div style="border-style: dotted;">
 +
To run a windows application:
 +
$ wine <path to exe>
 +
</div>
 +
Some EXEs have problems if not run from directory invoked. Should this be fixed?
 +
[[User:Axper|axper]] ([[User talk:Axper|talk]]) 17:55, 24 February 2014 (UTC)
 +
 
== Poor writing ==
 
== Poor writing ==
 
Throughout the article, I see: a lack of grammar, repetitive or overly verbose statements, and overuse of the [note] tag.  Anyone else want to correct this? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 22:23, 17 July 2012 (UTC)
 
Throughout the article, I see: a lack of grammar, repetitive or overly verbose statements, and overuse of the [note] tag.  Anyone else want to correct this? [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 22:23, 17 July 2012 (UTC)

Revision as of 17:55, 24 February 2014

cd to EXE's dir before running?

To run a windows application:

$ wine <path to exe>

Some EXEs have problems if not run from directory invoked. Should this be fixed? axper (talk) 17:55, 24 February 2014 (UTC)

Poor writing

Throughout the article, I see: a lack of grammar, repetitive or overly verbose statements, and overuse of the [note] tag. Anyone else want to correct this? T1nk3r3r (talk) 22:23, 17 July 2012 (UTC)

Going to edit 'architectural differences' soon. Too much information that is already stated elsewhere. Not sure it even requires its own subheading. T1nk3r3r (talk) 02:49, 18 July 2012 (UTC)

"A win64 WINEARCH is meant to be able to run 32-bit Windows applications as well as 64-bit ones."

Not necessarily. From Wine64 page: "There are still some pointer to int32 casts that need to be fixed. Most of these issue an appropriate warning. " T1nk3r3r (talk) 04:43, 18 July 2012 (UTC)

WINEARCH=win32

Wine seems to treat empty folders as win64 prefix folders, making it confusing to create win32 prefixes in empty folders. It gives the error [wine: WINEARCH set to win32 but '/home/wine/photoshop' is a 64-bit installation]. Perhaps we should add a note about this? See this bugreport http://bugs.winehq.org/show_bug.cgi?id=29661 -- JKAbrams 14:35, 20 Jan 2012 (EDT)

Yup, feel free to add that note. --Svenstaro 12:24, 20 January 2012 (EST)

I have to wonder why the Arch packagers activate WoW64 at all. I might fathom some security benefit? I would think any competent linux user that has a 64-bit Windows app knows to compile from source(and from git). As easy as: make configure --enable-win64 && make && make install. As far as I can tell from WineHQ: Wine WoW64 support is workable, but further work is low priority. T1nk3r3r (talk) 08:21, 31 July 2012 (UTC)

Sound

I resolve the problem with the sound on PulseAudio use of wine-multimedia from AUR

Maybe should be add information about it in the article Moriarty (talk) 23:41, 20 January 2013 (UTC)

There is an effort to consolidate Pulseaudio support in the new Wine sound system, but it will take time.

Some talk about this on Wine Bugzilla: http://bugs.winehq.org/show_bug.cgi?id=10495 T1nk3r3r (talk) 04:07, 21 January 2013 (UTC)