http://bugs.winehq.org/show_bug.cgi?id=29905
--- Comment #4 from Anastasius Focht focht@gmx.net 2012-02-16 16:09:35 CST --- Hello,
unfortunately I had WinVer still set to "Windows 2000", hence it worked due to fallback.
With "XP" mode (default) it still fails.
--- snip --- 0009:Call KERNEL32.CreateFileMappingW(ffffffff,0032e604,00000004,00000000,0000003c,0032e610 L"Session\0\Microsoft_VS90_causality_sharedmemory-68") ret=3f089149 0009: create_mapping( access=000f000f, attributes=00000080, protect=00000043, size=0000003c, file_handle=0000, objattr={rootdir=0010,sd={control=00000004,owner=<not present>,group=<not present>,sacl={},dacl={{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=10000000,AceFlags=0,Sid={S-1-5-21-0-0-0-1000}}}},name=L"Session\0\Microsoft_VS90_causality_sharedmemory-68"} ) 0009: create_mapping() = OBJECT_PATH_NOT_FOUND { handle=0000 } 0009:Ret KERNEL32.CreateFileMappingW() retval=00000000 ret=3f089149 --- snip ---
The "Sessions" directory and symlinks are there.
You can use the very useful object manager namespace viewer "winobj" from "sysinternals" to peek into wineserver at runtime.
http://technet.microsoft.com/en-us/sysinternals/bb896657
Running "winobj" on Windows (>=XP) might give some insight how the session directories/symlinks/objects are organized.
Regards