wine users - Nov 2011 - "cmd.exe /c echo '%ProgramFiles%' returned empty string"

hi.

I'm trying to install a program using winetricks, but I'm using a
separate wine install and WINEPREFIX, I run any command as such -

WINEARCH="win32" WINE='/home/de/media_writeit!/FOSS/additional
packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32'
WINEPREFIX='/home/de/media_writeit!/temp(others)/walkthrough'
./winetricks

And it returns - 

/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine
1.3.32/wine-1.3.32 cmd.exe /c echo '%ProgramFiles%' returned empty
string

Also in the winetricks wiki it has not been explained properly how to point out
to a seperate wine install.

I tried exporting all the WINE, WINEPREFIX and WINEARCH variables, but it
doesn't workout.

On the other hand - 

WINEPREFIX='/home/de/media_writeit!/temp(others)/walkthrough'
'/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with
wine 1.3.32/wine-1.3.32/bin/wine' cmd

C:\>echo %ProgramFiles%
C:\Program Files

C:\>

So this is what you're telling winetricks:
> '/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works
with wine 1.3.32/wine-1.3.32'
And this is what you use when you run cmd.exe directly:
> '/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works
with wine 1.3.32/wine-1.3.32/bin/wine
See the difference?

Martin Gregorie wrote:
> On Thu, 2011-11-10 at 22:35 -0600, dimesio wrote:
> 
> > dE_logics wrote:
> > 
> > > Nothing will happen (and nothing happened), winetricks is only
available in the current directory, so it says command not found.
> > > 
> > > 
> > 
> > How did you get winetricks? I've never used ./ in front of it, and
it executes just fine for me.
> > 
> > 
> Some distros (the RedHat ones and probably others) don't include
'.' or
> $HOME in $PATH by default. The first thing I do when I set up a new
> login users is to make sure '.', $HOME and $HOME/bin are added to
$PATH,
> preferably at the right end. Its such an automatic action that its easy
> to forget you did it years ago.
> 
> To dE_logics:
> 
> It sounds like your $HOME directory isn't in your search path. Post the
> output from this:
> 
> <code>
> echo $PATH
> </code>
> 
> So we can see what your search path looks like.
> 
> 
> Martin

Having '.' and $HOME in $PATH can lead to subtle failures,
if you create a file that has the same name as an existing command.

Simple example: the updatedb command from mlocate

Martin Gregorie wrote:
> On Thu, 2011-11-10 at 22:35 -0600, dimesio wrote:
> 
> > dE_logics wrote:
> > 
> > > Nothing will happen (and nothing happened), winetricks is only
available in the current directory, so it says command not found.
> > > 
> > > 
> > 
> > How did you get winetricks? I've never used ./ in front of it, and
it executes just fine for me.
> > 
> > 
> Some distros (the RedHat ones and probably others) don't include
'.' or
> $HOME in $PATH by default. The first thing I do when I set up a new
> login users is to make sure '.', $HOME and $HOME/bin are added to
$PATH,
> preferably at the right end. Its such an automatic action that its easy
> to forget you did it years ago.
> 
> To dE_logics:
> 
> It sounds like your $HOME directory isn't in your search path. Post the
> output from this:
> 
> <code>
> echo $PATH
> </code>
> 
> So we can see what your search path looks like.
> 
> 
> Martin

I've not seen any distro which sets '.' in it's PATH.

Also why will I need $HOME in $PATH?

PATH for user is - 
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/bin

Also '.' in $HOME doesn't make sense.


Martin Gregorie wrote:
> On Fri, 2011-11-11 at 07:33 -0600, Usurp wrote:
> 
> 
> > Having '.' and $HOME in $PATH can lead to subtle failures,
> > if you create a file that has the same name as an existing command.
> > 
> > Simple example: the updatedb command from mlocate
> > 
> > 
> That is why, if you're wise, you always run 'which' to check
check
> whether the script/program name you just thought up is going to clash
> with anything else. Its also why I said "add them to the right hand
> end", as in:
> 
> export PATH="$PATH:$HOME/bin:."
> 
> $PATH is searched left to right, so doing it this way guarantees that
> pre-existing stuff takes precedence over anything you wrote without
> first checking for name clashes.
> 
> Martin

I didn't know that presidency part, thanks.

On Thu, Nov 10, 2011 at 11:16, dE_logics <wineforum-user at winehq.org>
wrote:
> hi.
>
> I'm trying to install a program using winetricks, but I'm using a
separate wine install and WINEPREFIX, I run any command as such -
>
> WINEARCH="win32"
WINE='/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works
with wine 1.3.32/wine-1.3.32'
WINEPREFIX='/home/de/media_writeit!/temp(others)/walkthrough'
./winetricks
>
Cmd command-line arguments parsing has some issues. You should avoid
using special characters like '(', ')' or '!' in your
paths (probably
also holds for many other programs TBH)

Fr?d?ric

I think you're using WINE wrong.
It needs to point to the wine binary, not the directory that contains it.

e.g. I often do

export WINE=$HOME/wine-git/wine