Thanks for your response Vincent. Perhaps I was unclear. <br><br>About 5 months ago I could run from a bash shell,<br>export WINEPATH="/path/to/dll_dir_1" <br>and running wcmd /c set would show that the PATH variable had the standard c:\windows\ wine paths but it would also have the paths I set in the WINEPATH variable in bash. It's this passing of the linux shell WINEPATH and appending it to the wine WINEPATH that seems to have disappeared.
<br><br><br>Thanks,<br>Daniel<br><br><br><div><span class="gmail_quote">On 8/2/06, <b class="gmail_sendername">Vincent Povirk</b> <<a href="mailto:madewokherd+d41d@gmail.com">madewokherd+d41d@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I've never heard of WINEPATH, but it seems to still be there. Running<br>"z:\bin\sh -c set" from within wcmd shows that wine is setting it. But
<br>setting it manually (even within a program called from wine) doesn't<br>seem to have any effect.<br><br>You can probably work around it by having an app running in wine (such<br>as wcmd) set it and then call your program.
<br><br>--<br>Vincent Povirk<br></blockquote></div><br>