[Wine] Re: "cmd.exe /c echo '%ProgramFiles%' returned empty string

dE_logics wineforum-user at winehq.org
Fri Nov 11 00:40:41 CST 2011


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.


I've downloaded winetricks. winetricks is a bash script, so it can be placed anywhere. The '.' in the './' represents the current location, thus ./winetricks asks bash to execute the winetricks script which's in the current directory.


DanKegel wrote:
> 
> dE_logics wrote:
> > 
> > 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
> > 
> > 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
> > 
> 
> 
> I seem to recall hearing that the "returned empty string" symptom happens when running 32 bit wine on a 64 bit system, and was caused by a missing wine.inf entry for wow64.
> Or something like that.  I haven't had time to investigate since I heard that.
> 
> 
> > 
> > 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.
> > 
> 
> 
> WINE is how you tell winetricks which wine to run.
> 
> WINEPREFIX is how you tell wine (and winetricks) where the fake C drive and
> registry live.
> 
> Do you really have two versions of wine?   What program are you trying to install?


Yes, this system is 64 bit and this problem exists when you try running a 64 bit wine prefix on a 32 bit wine installation. But in my case, every prefix is 32bit.

This time around, since the WINE variable doesn't appear to be working, I had to drop it and use the prefix of wine-1.3.32 (static build) with wine-1.3.29 (system install). I installed a few packages using winetricks, after which it suddenly stopped working and started giving this error.

Later on (now) I noticed that some wine processes where still running in background which were causing this problem.

However, the main issue now is, the WINE variable doesn't appear to be working.

I'm trying to make soundforge 10 work. Currently there analyzer graph is bank.







More information about the wine-users mailing list