http://bugs.winehq.org/show_bug.cgi?id=10259
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #9 from Anastasius Focht focht@gmx.net 2007-11-02 07:52:30 --- Hello,
--- quote --- 0009:Call KERNEL32.OpenFileMappingA(0002001f,00000000,0033e830 "Local\Mso97SharedDg19211105606") ret=30cc0994 0009:Ret KERNEL32.OpenFileMappingA() retval=00000000 ret=30cc0994 0009:Call KERNEL32.CreateFileMappingA(ffffffff,316291ac,04000004,00000000,0001effc,0033e830 "Local\Mso97SharedDg19211105606") ret=30cc0afb 0009:Ret KERNEL32.CreateFileMappingA() retval=00000000 ret=30cc0afb 0009:Call KERNEL32.GetLastError() ret=30cc0b03 0009:Ret KERNEL32.GetLastError() retval=00000005 ret=30cc0b03 --- quote ---
--- quote --- Why is it trying to create a file mapping with a handle of INVALID_HANDLE_VALUE? --- quote ---
Perfectly valid call. From MSDN:
--- snip --- If hFile is INVALID_HANDLE_VALUE, the calling process must also specify a size for the file mapping object in the dwMaximumSizeHigh and dwMaximumSizeLow parameters. In this scenario, CreateFileMapping creates a file mapping object of a specified size that is backed by the system paging file instead of by a file in the file system. --- snip ---
Anyway the relays provided here are not boiling down to the problem because of "RelayFromExclude = L"winex11.drv;user32;gdi32;advapi32;kernel32". One has to see the internal calls made to "W" mapping API and especially Ntdll section stuff to see the real failure. You should rerun with at least +ntdll. Although the returned last error ERROR_ACCESS_DENIED (5) indicates an access rights problem. Maybe some security related improvements/bugfixes were made in the near past triggering such issues (code paths) now.
Regards