Hello, I noticed this while attempting to run a DOS software suite. The CALL command in wcmd doesn't seem to honor the set PATH. If I put this in my environment (via regedit): c:\windows;c:\windows\system;e:\;e:\test;f:\;f:\downloads\daphne\tools Then I put the following in f:\downloads\daphne\tools\bob.bat: path c:\windows;c:\windows\system;e:\;e:\test;f:\;f:\downloads\daphne\tools path CALL bob Then run bob.bat from the shell, from the f:\downloads\daphne working directory: F:\downloads\daphne>bob F:\downloads\daphne>path c:\windows;c:\windows\system;e:\;e:\test;f:\;f:\downloads\daphne\tools F:\downloads\daphne>path PATH=c:\windows;c:\windows\system;e:\;e:\test;f:\;f:\downloads\daphne\tools F:\downloads\daphne>CALL bob File not found F:\downloads\daphne> F:\downloads\daphne> You can see that CALL doesn't honor PATH. It should loop until interrupted. Is this a bug? Any way around it?
Jesse Guardiani wrote:> Is this a bug?If cmd on Windows follows PATH, then it's a bug.> Any way around it?Since you have an excellent bug report, you could report it to wine-devel@winehq.org and then watch as nothing happens :-). (Probably, but who knows!) Or check out the source code, conjure up a patch, make sure it adheres to HACKING, then send it to wine-patches@winehq.org. There's development info here: http://www.winehq.org/site/resources There's also a Wine Developer's Guide, but I couldn't find it linked from anywhere on either the winehq.org main pages or the wiki.winehq.org main pages. It's out there.... somewhere...
On Sun, 29 Jan 2006 04:26:23 +0000 (UTC), in gmane.comp.emulators.wine.user you wrote:>Hello, > >I noticed this while attempting to run a DOS software suite. The CALL command in >wcmd doesn't seem to honor the set PATH.I have sent a patch that fixes this problem: http://www.winehq.org/pipermail/wine-patches/2006-February/023954.html Rein.