No problem with your suggestion. However, 2 hours later it did the same
again!
John
On 16/02/17 18:13, jre wrote:
> With these commands you were still using ~/.wine. You have to either export WINEPREFIX or specify it for every command.
> Further I think I've seen Wine complaining about "~" in the past, so maybe either use $HOME or the path directly.
>
> To rule out any issues with existing profiles, let's start fresh again,
> and make sure that the first command is done and the wineserver had time
> to shut down between the commands. So what happens for:
>
> WINEARCH=win32 WINEPREFIX=/home/john/.wine32-test wine wineboot
> sleep 10
> WINEPREFIX=/home/john/.wine32-test winecfg
>
>
> ** Changed in: wine1.6 (Ubuntu)
> Status: New => Incomplete
>
No problem with your suggestion. However, 2 hours later it did the same
again!
John
On 16/02/17 18:13, jre wrote: /home/john/ .wine32- test wine wineboot /home/john/ .wine32- test winecfg
> With these commands you were still using ~/.wine. You have to either export WINEPREFIX or specify it for every command.
> Further I think I've seen Wine complaining about "~" in the past, so maybe either use $HOME or the path directly.
>
> To rule out any issues with existing profiles, let's start fresh again,
> and make sure that the first command is done and the wineserver had time
> to shut down between the commands. So what happens for:
>
> WINEARCH=win32 WINEPREFIX=
> sleep 10
> WINEPREFIX=
>
>
> ** Changed in: wine1.6 (Ubuntu)
> Status: New => Incomplete
>