September 2004 - Wine-Devel

Vincent Beron:"Re:dividsion by zero in winword"
by Robbert Xerox Sept. 25, 2004

Sept. 25, 2004

> So maybe we should actually check for the FAT signature at buff[0x36] or > buff[0x52] first, and then do the calculations if we actually do find > one of them. > > Changelog: > Make sure we're really looking at a FAT before doing some calculations > based on the contents of the first sector of a partition. That doesn't solve the real issue, a FAT signature is not a guarantee that the rest of the block is valid, so we still need to check these values against zero. The code should not crash no matter what garbage the block contains. -- Alexandre Julliard Well, Vincent's Beron patch solves at least my problem, i.e. the error is gone and the programs work fine now.thx Robbert ___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com

1 0

Error popop text not on terminal
by J. Grant Sept. 24, 2004

Sept. 24, 2004

Hello, I am using eDonkey2000, installed on my CVS build. I installed with my config set to "win98", however I get the error in the attached popup when trying to run. I changed my config to "win2k" and I still have the problems, so I do not think that made any difference. Could the attached screenshot error text be displayed on the terminal with the other useful info please? (I normally see missing DLLs listed on the terminal, and occasionally also as a dialog. This error was only on a popup.) it is really hard to read the text on the popups, and I cannot copy paste into emails like this. If this popup could have only come from the program, I wonder if there is any way to log the program gui text from this msg box on the terminal? You can download the installer exe from this url if you would like to try yourself: http://www.overnet.com/downloads.php (the installer downloads and installs the program it seems) Over the course of several runs (restart of the process required for each missing dll), several popups I copied from my win2k install to get it working: kernel32.dll ntdll.dll user32.dll advapi32.dll rpcrt4.dll shell32.dll imm32.dll wsock32.dll ws2_32.dll ws2help.dll oleaut32.dll Into c:\windows\system as requested by the popups. On my win2k install these were in the "system32" dir. I wonder why is it hunting for them in "system" ? It does run though, see log attached. The screenshot shows the corrupted title bar, which cannot be moved. Any ideas how to solve this corruption problem? Also, perhaps there is a way to simplify the install of programs such as this which require so many dlls? Kind regards JG -- Homepage: http://jguk.org/ Blog: http://jguk.org/index.html#blog Radio: http://jguk.org/index.html#radio Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file fixme:font:WineEngCreateFontInstance just using first face for now WCMD Version 0.17 D:\>c:\>File not found c:\>c:\opt>c:\opt\ed2k>Volume in drive c is Volume Serial Number is 0000-0000 Directory of c:\opt\ed2k\ 20/09/2004 01:19 <DIR> . 20/09/2004 00:32 <DIR> .. 20/09/2004 01:15 418 5.html 20/09/2004 01:15 400 74.html 20/09/2004 00:32 11,504 contact.dat 20/09/2004 00:32 260 def.html 20/09/2004 01:19 <DIR> dis-plugins 20/09/2004 00:32 2,009,248 edonkey2000.exe 20/09/2004 01:19 0 filters.txt 20/09/2004 01:19 5 friend.met 20/09/2004 01:19 5 friend.met.bak 20/09/2004 01:19 5 known.met 20/09/2004 01:19 5 known.met.bak 20/09/2004 01:15 53 log.txt 20/09/2004 00:32 511 media.xml 07/12/1999 13:00 77,878 msvcirt.dll 29/08/2000 04:19 401,462 MSVCP60.DLL 20/09/2004 01:19 <DIR> Plugins 20/09/2004 01:19 1,233 pref.xml 20/09/2004 00:32 4,152 reg.jpg 20/09/2004 01:19 4,087 server.met 20/09/2004 01:19 4,087 server.met.bak 20/09/2004 01:19 39 share.dat 20/09/2004 01:19 39 share.dat.bak 20/09/2004 00:32 <DIR> Skins 20/09/2004 00:32 <DIR> temp 20/09/2004 00:32 37,125 uninstall_eDonkey2000.exe 21 files 2,552,516 bytes 6 directories 3,674,771,456 bytes free c:\opt\ed2k>c:\opt\ed2k>err:module:import_dll No implementation for MSVCRT.dll.??_U(a)YAPAXI@Z imported from L"C:\\opt\\ed2k\\MSVCIRT.dll", setting to 0xdeadbeef err:module:import_dll No implementation for MSVCRT.dll.??_V(a)YAXPAX@Z imported from L"C:\\opt\\ed2k\\MSVCIRT.dll", setting to 0xdeadbeef Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file fixme:font:WineEngCreateFontInstance just using first face for now fixme:ole:CoCreateInstance no classfactory created for CLSID {4955dd33-b159-11d0-8fcf-00aa006bcc59}, hres is 0x80040154 fixme:imm:ImmGetContext (0x10020): stub fixme:imm:ImmReleaseContext (0x10020, 0x40336368): stub ixme:imm:ImmReleaseContext (0x10020, 0x40336368): stub fixme:imm:ImmGetContext (0x501ca): stub fixme:imm:ImmReleaseContext (0x501ca, 0x40336360): stub fixme:imm:ImmGetContext (0x501ca): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x501ca, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406bda74): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be104): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x5007a): stub fixme:imm:ImmReleaseContext (0x5007a, 0x40336360): stub fixme:imm:ImmGetContext (0x5007a): stub fixme:imm:ImmReleaseContext (0x5007a, 0x40336360): stub fixme:imm:ImmGetContext (0x5007a): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x5007a, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406bde84): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be0e8): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be0e8): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be0e4): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be0e4): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be0e4): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x70254): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70254, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:system:SystemParametersInfoW Unimplemented action: 4100 (SPI_GETCOMBOBOXANIMATION) fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x6025e): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x6025e, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x702ae): stub fixme:imm:ImmReleaseContext (0x702ae, 0x40336360): stub fixme:imm:ImmGetContext (0x80254): stub fixme:imm:ImmReleaseContext (0x80254, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x50264): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50264, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406bdb8c): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub QPixmap::fromMimeSource: Cannot find pixmap "C:\opt\ed2k\skins\default\x-dis.png" in the mime source factory fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406be060): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmSetCandidateWindow (0x40336360, 0x406bdb20): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x70250): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x70250, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x502e6): stub fixme:imm:ImmReleaseContext (0x502e6, 0x40336360): stub fixme:system:SystemParametersInfoW Unimplemented action: 4098 (SPI_GETMENUANIMATION) fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:system:SystemParametersInfoW Unimplemented action: 4098 (SPI_GETMENUANIMATION) fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50238): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50238, 0x40336360): stub fixme:imm:ImmGetContext (0x50228): stub fixme:imm:ImmReleaseContext (0x50228, 0x40336360): stub fixme:imm:ImmGetContext (0x50228): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50228, 0x40336360): stub fixme:imm:ImmGetContext (0x50228): stub fixme:imm:ImmReleaseContext (0x50228, 0x40336360): stub fixme:imm:ImmGetContext (0x50228): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50228, 0x40336360): stub fixme:imm:ImmGetContext (0x50228): stub fixme:imm:ImmReleaseContext (0x50228, 0x40336360): stub fixme:imm:ImmGetContext (0x50228): stub fixme:imm:ImmNotifyIME (0x40336360, 21, 4, 0): stub fixme:imm:ImmReleaseContext (0x50228, 0x40336360): stub fixme:imm:ImmGetContext (0x802c8): stub fixme:imm:ImmReleaseContext (0x802c8, 0x40336360): stub fixme:imm:ImmGetContext (0x502c2): stub fixme:imm:ImmReleaseContext (0x502c2, 0x40336360): stub

1 0

Re: Getting winebuild to work on HP-UX
by Warren_Baird/CSI＠cimmetry.com Sept. 24, 2004

Sept. 24, 2004

(BTW, apologies for the Firewall/CSI thing in my previous message's "From:" line - they've been mucking about with our external mail server, and it messed something up - Hope people didn't get bounces if they tried replying directly - hopefully it'll be fixed for this message.) Alexandre Julliard wrote: > No, pretty much everything that can be done in C already is, the rest > really needs to be in assembly. It's a perfect opportunity to learn > PA-RISC assembly <g> I was afraid you'd say that -- 'cause I know as soon as I'm done the HP-UX port, I'm going to be asked to do an AIX port. Oh well - maybe I can piggyback off some of the MacOS stuff... I don't suppose there's any documentation around anywhere talking about exactly what the assembly code in winebuild is trying to accomplish, and why it can't be done in C? I'm afraid that my assembly is rough enough that I haven't been able to figure out what all of the import/export set up code is trying to do. Taking a description of what it's supposed to do, and then learning enough pa-risc assembly to do it will certainly be faster than reverse-engineering the assembly that's there and then trying to implement it for the pa-risc. Here's a brief summary of where I am: after making a few changes to various Makefile.in files to fix places where .so was used instead of $(LIBEXT), and fixing winegcc so that .so wasn't hardcoded in it either (patches will be forthcoming this aft), I'm at the point where the vast majority of the .c files compile (about 1470 - my linux build has 1596 .o files in it) - but nothing outside of libs/loader links, because of winebuild... So my next goal is really to get winebuild working... I guess I'll be cracking the pa-risc assembly language manual open soon... :-) Warren

2 1

Re: Get AdjustWindowRect working better
by Alexandre Julliard Sept. 24, 2004

Sept. 24, 2004

Richard Cohen <richard(a)daijobu.co.uk> writes: > We shouldn't create a new file for *every single* test, but we should > do so for an unrelated test. How 'unmanageable' is adding 1 line to > Makefile.in? There are more than 700 APIs in user32 alone. If we create a new file for each one, that means 700 source files. Plus, with all the debug symbols, the smallest object file weighs in at least 100K, so that's a minimum of 70Mb of object files in that single directory. Multiply that by the 150 dlls we have and it should be obvious why it's unmanageable. > I would rather have the tests as *maintaineable*. If a test fails, > isn't it easier to look through 200 lines than 2000 lines ? No, since you get a line number with the failure message, you don't have to look through the whole file. -- Alexandre Julliard julliard(a)winehq.org

2 3

Re: Register Component Categories Manager
by Robert Shearman Sept. 24, 2004

Sept. 24, 2004

Robert Shearman wrote: > Changelog: > Register component categories manager. Sorry, this patch is wrong. It seems it is already registered by comcat.dll, but some versions of the native ole32 seem to include the component categories manager. Rob

1 0

Re: Accept WM_SYSCHAR message for processsing in TranslateAcceleratorW
by Rein Klazes Sept. 24, 2004

Sept. 24, 2004

On Thu, 16 Sep 2004 19:54:57 +0900, you wrote: > Hello, > Hi Dmitry, This patch is causing a regression in Agent (still existing in current CVS). If I use <alt>+W to access the Windows menu the program reacts as if I pressed just the 'W'. This is also an accelator key causing the current thread to be 'Watched'. Same thing with <ALT>+H, it should bring up the help menu. Now it causes the headers to display, normally behind the 'H' key. <ALT>-E works normal, probably because the 'E' is not accelerated. > this patch makes accelerator keys in my test MDI app (compiled with MSVC) > work under Wine. The problem is that Wine correctly generates WM_SYSKEY* > and WM_SYSCHAR messages when there is no focus window, but WM_SYSCHAR > is not considered by TranslateAcceleratorW as a valid input. Uhh, "The problem is that Wine correctly generates ...". Do you mean this is a hack? BTW. Your other patch "Make message flow for MDI ..." fixes the problem with maximized/restored MDI windows in Agent, thanks. Rein. -- Rein Klazes rklazes(a)xs4all.nl

2 8

Re: Support remote operations in wineserver
by Alexandre Julliard Sept. 24, 2004

Sept. 24, 2004

"Alexander Yaworsky" <yaworsky(a)migusoft.ru> writes: > Hello > > I guess that original patch was too large. > I sent small pieces of it and they have been committed; however it seems that > this part cannot be downsized. Well, I'm not going to commit that part since it doesn't actually do anything with the remote operation, and it's not clear at all that the requests you added will be appropriate to whatever mechanism we use to do the remote operation. -- Alexandre Julliard julliard(a)winehq.org

4 5

Re: reading HEX and OCTAL numbers from input field
by James Hawkins Sept. 24, 2004

Sept. 24, 2004

> Yes, I've put brown bag over my head Na, it's ok. You're new to the developemnt process of wine, and it can take a while to get a hang of the process. Just stick with it and things will be better in no time. On Thu, 23 Sep 2004 23:56:32 -0700, Primorec <igor.furlan(a)gmail.com> wrote: > Just forget my post.. I have not noticed that this feature was > already implemented. > > Yes, I've put brown bag over my head > > > > > On Thu, 23 Sep 2004 23:05:36 -0700, Primorec <igor.furlan(a)gmail.com> wrote: > > This patch allows user to enter HEX and/or OCTAL numbers into the form > > input field. > > > > This is my first patch and in the same time my second C program (first > > one was Hello World). > > So, please, have a mercy and be tolerant. > > > > Thanks > > > > Igor > > > > ? patch.diff > > Index: dlls/oleaut32/variant.c > > =================================================================== > > RCS file: /home/wine/wine/dlls/oleaut32/variant.c,v > > retrieving revision 1.102 > > diff -u -u -r1.102 variant.c > > --- dlls/oleaut32/variant.c 22 Sep 2004 19:12:18 -0000 1.102 > > +++ dlls/oleaut32/variant.c 24 Sep 2004 05:44:43 -0000 > > @@ -1556,6 +1556,8 @@ > > DWORD dwState = B_EXPONENT_START|B_INEXACT_ZEROS; > > int iMaxDigits = sizeof(rgbTmp) / sizeof(BYTE); > > int cchUsed = 0; > > + int value = 0; > > + OLECHAR first_element; > > > > TRACE("(%s,%ld,0x%08lx,%p,%p)\n", debugstr_w(lpszStr), lcid, > > dwFlags, pNumprs, rgbDig); > > > > @@ -1571,6 +1573,73 @@ > > pNumprs->nBaseShift = 0; > > pNumprs->nPwr10 = 0; > > > > + first_element = *lpszStr++; > > + > > + if ((first_element == '&') && (pNumprs->dwInFlags & NUMPRS_HEX_OCT)) > > + { > > + /* printf("TONY's hex string %s \n", debugstr_w(lpszStr)); */ > > + > > + first_element = *lpszStr++; > > + > > + if (first_element == 'h' || first_element == 'H') > > + { > > + pNumprs->nBaseShift = 4; /* hex number */ > > + first_element = *lpszStr++; > > + } > > + else > > + { > > + pNumprs->nBaseShift = 3; /* octal number */ > > + > > + if (first_element == 'o' || first_element == '0') > > + { > > + first_element = *lpszStr++; > > + } > > + } > > + > > + while (first_element == '0') > > + first_element = *lpszStr++; > > + > > + while (first_element != 0) > > + { > > + if (pNumprs->nBaseShift == 4) > > + { > > + if (first_element >= 'a' && first_element <= 'f') > > + value = first_element - 'a' + 10; /* making integer value > > out of hex character */ > > + else if (first_element >= 'A' && first_element <= 'F') > > + value = first_element - 'A' + 10; /* making integer value > > out of hex character */ > > + else if (first_element >= '0' && first_element <= '9') > > + value = first_element - '0'; > > + } > > + else > > + { > > + if (first_element >= '0' && first_element <= '7') > > + value = first_element - '0'; > > + } > > + rgbTmp[cchUsed] = value; > > + cchUsed++; /* count digits */ > > + first_element = *lpszStr++; > > + } > > + > > + if (cchUsed == 0) > > + { > > + value = 0; > > + rgbTmp[cchUsed] = value; > > + cchUsed = 1; > > + } > > + > > + pNumprs->cDig = cchUsed; > > + > > + memcpy(rgbDig, rgbTmp, pNumprs->cDig * sizeof(BYTE)); > > + return S_OK; > > + } > > + > > + if (!pNumprs || !rgbDig) > > + return E_INVALIDARG; > > + > > + if (pNumprs->cDig < iMaxDigits) > > + iMaxDigits = pNumprs->cDig; > > + > > + > > if (!lpszStr) > > return DISP_E_TYPEMISMATCH; > > > > @@ -1971,6 +2040,26 @@ > > > > if (pNumprs->nBaseShift) > > { > > + > > + /* we have to be sure that the number does not use more than 32 bits > > + * I am not sure if this is 100% valid - perhaps we should test for 64 ?? */ > > + int bitCount = (pNumprs->nBaseShift) * (pNumprs->cDig); > > + if (bitCount > 32) > > + return DISP_E_OVERFLOW; > > + > > + ULONG intValue = 0; > > + for ( ; pNumprs->cDig > 0; pNumprs->cDig--) > > + intValue = (intValue << (pNumprs->nBaseShift)) + *rgbDig++; > > + > > + FIXME("Only VTBIT_I2 implemented. Need to add other cases : > > VTBIT_I1, VTBIT_UI1 ... etc \n"); > > + if (dwVtBits & VTBIT_I2) > > + { > > + V_VT(pVarDst) = VT_I2; > > + V_I2(pVarDst) = intValue; > > + return S_OK; > > + } > > + > > + > > /* nBaseShift indicates a hex or octal number */ > > ULONG64 ul64 = 0; > > LONG64 l64; > > > > -- James Hawkins

1 0

Re: Contributing to WINE
by Dan Kegel Sept. 24, 2004

Sept. 24, 2004

Alexandre Julliard wrote: > I got his mails and replied (even though they were sent as Word > documents which was a big pain to read). I imagine he never got the > replies, it seems your mail setup needs some work. Maybe you should fax your first reply to make sure he gets it. Specops fax # is, according to their web site, 632 532-5875. - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

1 0

Re: [dx9-2] Make d3d8 know about the wined3d device
by Alexandre Julliard Sept. 23, 2004

Sept. 23, 2004

"Ann and Jason Edmeades" <us(a)the-edmeades.demon.co.uk> writes: > +/* No reference counting is required as there will be only one reference from > + Direct3DCreateX, and released when the reference count of that object gets to 0 */ > ULONG WINAPI IWineD3DImpl_AddRef(IWineD3D *iface) { > + IWineD3DImpl *This = (IWineD3DImpl *)iface; > + FIXME("(%p) : AddRef should never be called\n", This); > return 1; > } > > ULONG WINAPI IWineD3DImpl_Release(IWineD3D *iface) { > + IWineD3DImpl *This = (IWineD3DImpl *)iface; > + TRACE("(%p) : Releasing\n", This); > + HeapFree(GetProcessHeap(), 0, This); > return 0; > } If you are going to free the object on Release() then you should really do proper ref counting. It costs basically nothing and it will avoid a lot of headaches. Dummy refcounting is OK only if the count really doesn't matter, i.e. the object never gets released. -- Alexandre Julliard julliard(a)winehq.org

1 0