http://bugs.winehq.org/show_bug.cgi?id=21322
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Component|-unknown |kernel32
--- Comment #2 from Dan Kegel dank@kegel.com 2010-01-14 08:25:30 --- Nope! Reverting that did nothing here.
I looked closer. After the program runs, system.reg contains [System\CurrentControlSet\Control\Session Manager\Environment] "PATH"=str(2):"C:\windows\system32;C:\windows;C:\windows\system32\wbem" and user.reg contains [Environment] "PATH"=";"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\.";"C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin\win95.""
which doesn't seem that bad. Maybe the problem is that Wine isn't combining the system-wide and the user-specific PATH settings properly; it should append them. A comment in http://www.tomshardware.com/forum/29472-45-environment-variable-where agrees with this. Looking at kernel32/process.c:set_registry_environment(), it seems as if in wine, user-specific registry settings simply override the system-wide ones, even for PATH.
So unless I'm reading set_registry_environment() wrong, this is a kernel32 bug, and not a regression. I must have been wrong when I said this worked before. And sure enough, running wine-1.1.31's cmd still shows the screwed up PATH.