On Tue, Jul 28, 2015 at 3:05 PM, Eric Christensen <[email protected]> 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). 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" >> > 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. -- -Austin _______________________________________________ pkg-wine-party mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-wine-party
