[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#793879: Bug#793879: Bug#793879: (no subject)

On 07/28/2015 10:12 PM, Austin English wrote:
> On Tue, Jul 28, 2015 at 3:05 PM, Eric Christensen
> <eric@christensenplace.us> wrote:
>> On Tuesday, July 28, 2015 02:39:45 PM Austin English wrote:
>>> You're not getting any messages about creating a WINEPREFIX, so it
>>> looks like you're using an existing one still.
>> How do I find out what's being used?  I didn't see WINEPREFIX being set
>> anywhere that I grep'd.
> Good question. I believe the debian packages set up a default one for
> Wine64 at ~/.wine64 (but someone more familiar with Debian's packaging
> would have to confirm).

That's correct. WINEPREFIX is set in /usr/bin/wine if it is NOT
specified by the user. If WINEARCH is win64 or /usr/bin/wine32 is not
installed (executable), then this will be ~/.wine64 (this is for "wine"
in Debian Jessie), otherwise ~/.wine.
Note that this is not true if you directly use wine64 or any of the
binaries linking to wine-wrapper (wineboot, winecfg, ...).

> There may be an easier way, but here's
> something I tested locally that should work:
> austin@debian-laptop:~$ WINEDEBUG=file wine wineboot 2>&1 | grep
> dosdevices | head -n1
> trace:file:wine_nt_to_unix_file_name L"\\windows" not found in
> /home/austin/.wine/dosdevices/c:/windows
> austin@debian-laptop:~$ WINEPREFIX=~/.winetest WINEDEBUG=file wine
> wineboot 2>&1 | grep dosdevices | head -n1
> trace:file:wine_nt_to_unix_file_name L"\\??\\C:\\windows" ->
> "/home/austin/.winetest/dosdevices/c:/windows"

Further, if you create/change a wineprefix, you'll get a line like this:
  wine: configuration in '/home/jens/.wine' has been updated.

You can check if you have a 32- or 64-bit wineprefix with the following
command (here for ~/.wine):
  cat .wine/system.reg | grep "^\#arch="

>>>> wine: Bad EXE format for Z:\home\echristensen\Downloads\amhc34062b.exe.
>>> Could you run 'file' on that executable?
>> $ file amhc34062b.exe
>> amhc34062b.exe: PE32 executable (GUI) Intel 80386, for MS Windows
> That's a 32-bit executable, not a 64-bit one. Try wine/wine32 instead of wine64.

Indeed, and since only "wine" has the wineprefix logic (~/.wine or
~/.wine64) you should always use the same command, preferrably "wine",
if in doubt together with WINEARCH:
  WINEARCH=win32 wine [foo.exe|wineboot|winecfg]


Reply to: