May 2001 - Wine-Devel - list.winehq.org

Re: Small fixes in controls/menu.c

by kenon＠go2.pl

On Sun, May 20, 2001 at 11:33:45PM +0200, gerard patel wrote: > At 10:20 AM 20/05/2001 -0700, you wrote: > >gerard patel <gerard.patel(a)asi.fr> writes: > > > >> (patch using NC_HandleNCCalcSize instead of SetWindowPos) > >> > >> IMO it's better and it solves my problem as well. > > > >I think the SetWindowPos one was better. If the app handles > >WM_NCCALCSIZE we shouldn't try to bypass it. > > But does Windows send this message in this case ? From what > I can see in the traces, I don't think so. > Maybe Maciek could look at the behaviour of his app under > Windows. Or I could download it and try to solve the problem > myself (I'd better not :-/) > I have small experience in debugging apps under windows ,so any hints are welcomed. In attachement WIN.3_11 you can see listing generated under windows 3.11. ( Borland WinSight ) (If you want get a listing generated under win98/95 - no problem , but I'll have to format&reinstall ,because this copy of windows stopped functioning about 6 months ago ) WINE_SETWINPOS ,WINE_NCALC- under wine with first and second version of patch. I think WINE_NCALC is more similar to WIN.3_11 . I'm wondering why menu->Height == 0. I'll investigate it. Maciek --

May 22, 2001

Re: Wine build failure in tools/winebuild/spec16 due to recent change

by Ove Kaaven

On Mon, 21 May 2001, Marcus Meissner wrote: > Changelog: > In case our stat already supports 64bit operations (like FreeBSD > stat does), we don't need to stub them, we can just define the > x64 functions to x. You know, glibc would also have such an interface if you used the -D_FILE_OFFSET_BITS=64 compilation option. Wouldn't it be simpler to unify the 64-bit interface code by using that?

May 21, 2001

Re: warning fixes

by Francois Gouget

On Mon, 21 May 2001, eric pouech wrote: > ChangeLog: fixed a couple of warnings This does not fix the warnings, it just hides the bug. As the comments say, the assignments are plain wrong in the first place. /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__environ = GetEnvironmentStringsA(); + MSVCRT__environ = (char**)GetEnvironmentStringsA(); MSVCRT___initenv = MSVCRT__environ; /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__wenviron = GetEnvironmentStringsW(); + MSVCRT__wenviron = (WCHAR**)GetEnvironmentStringsW(); MSVCRT___winitenv = MSVCRT__wenviron; -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Avoid the Gates of Hell - use Linux.

May 21, 2001

Re: problem starting winword 97SR2

by James Juran

Heiko Nardmann wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 21 May 2001 13:05, Andreas Mohr wrote: > > On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote: > > > When starting WinWord I get a dialog saying that either I have not enough > > > work space or memory space. The program exits then. > > > > > > So after playing with the debug options I found out that this happens > > > after a key named "Office.SharedMemory.1" is accessed inside the > > > registry. Can someone tell me what to do to make word no longer complain? > > > > [HKEY_LOCAL_MACHINE\\Software\\Classes\\Office.SharedMemory.1] > > "CLSID" = "{000c0114-0000-0000-c000-000000000046}" > > "IID" = "{000c0507-0000-0000-c000-000000000046}" > > > > But don't think that your Wine config is broken if you don't have registry > > settings from an already installed Office ? > > Hmm ... I did not install Office on my machine, just copied the following > files from my Windows NT machine into a separate directory: > > - - winword.exe > - - mso97.dll > - - wwintl32.dll > > To be honest: I even have not installed Windows at all on this machine > although I have a license for it. > > The files stated above are enough to resolve the linker dependencies. You will need to run the installation program or manually copy all the registry entries from an existing installation. The Microsoft Office applications put tons of stuff in the registry which is necessary for them to run. -- James Juran jamesjuran(a)alumni.psu.edu

May 21, 2001

Anybody know int-31?

by Bob Goodwin

I want to run an application that requires win95 but relys heavily on DOS interupt functions. Specifically it requires interupt 31 which is just a stub in Wine. It appears (from R.B.'s list) that there is no limit on calls to interupt_31-AX=0305 (request the address of (?:the:a) save/restore handler.) That implies more than one thread could have a save/restore pointer. When calling the save/restore handler function, the only parameter passed is a byte in AL to indicate whether to save the current context or restore a saved context. My question is, are there multiple copies of the save/restore function or at least multiple entry points? It seems that this would be the only way of having multiple unique context saves. It would be differrent if a unique `handle' was returned by int_31 instead of a call address. If only one context can be stored at a time, do I need a spin-lock within the save/restore function to keep other applications holding until their turn? Thanks. Bob Goodwin

May 21, 2001

Re: Networking with Mandrake 8.0 and SuSE 7.1

by Steve Fox

This weekend I upgraded to Mandrake's 2.4.4 kernel from Cooker (since it fixed both my mouse and token ring) and suddenly this problem has gone away (using Notes 5.0.7 and wine-20010305). I'm still planning to go through Mandrake's 2.2.19 SRPM and find which patch messes things up (I can't use a Linus-only kernel because I need reiserfs). I will post again once I have narrowed down the list of suspects. I'm guessing it has to be a common patch since SuSE seems to have the same symptoms. Steve Fox IBM Linux Technology Center http://www.ibm.com/linux/ltc http://k-lug.com

May 21, 2001

Re: problem starting winword 97SR2

by Heiko Nardmann

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 21 May 2001 14:40, Heiko Nardmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 21 May 2001 14:09, Heiko Nardmann wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Monday 21 May 2001 13:05, Andreas Mohr wrote: > > > On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote: > > > > When starting WinWord I get a dialog saying that either I have not > > > > enough work space or memory space. The program exits then. > > > > This happens with CVS version, too, which I just compiled and installed. - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7CRSRpm53PRScYygRAhk2AKC+eu8s5jBxNbigCDL/G+w+Sd7eTwCeIBcV xr9+ceOMQ4rEcUFj6fkB6bk= =LTIH -----END PGP SIGNATURE-----

May 21, 2001

Re: problem starting winword 97SR2

by Heiko Nardmann

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 21 May 2001 14:09, Heiko Nardmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 21 May 2001 13:05, Andreas Mohr wrote: > > On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote: > > > When starting WinWord I get a dialog saying that either I have not > > > enough work space or memory space. The program exits then. > > > > > > So after playing with the debug options I found out that this happens > > > after a key named "Office.SharedMemory.1" is accessed inside the > > > registry. Can someone tell me what to do to make word no longer > > > complain? > > > > [HKEY_LOCAL_MACHINE\\Software\\Classes\\Office.SharedMemory.1] > > "CLSID" = "{000c0114-0000-0000-c000-000000000046}" > > "IID" = "{000c0507-0000-0000-c000-000000000046}" > > And now I have to say that this did not work. Sorry ... Any other idea? Here are the lines of debug with +all which contain references to this SharedMemory stuff; maybe someone can tell me what to do: Call advapi32.211: RegDeleteKeyA(80000000,3079075c "Office.SharedMemory.1") ret=307907f6 fs=008f Call ntdll.419: RtlInitAnsiString(405b6b88,3079075c "Office.SharedMemory.1") ret=407c591a fs=008f Ret ntdll.419: RtlInitAnsiString() retval=00000016 ret=407c591a fs=008f Call ntdll.281: RtlAnsiStringToUnicodeString(405b6b90,405b6b88,00000001) ret=407c5926 fs=008f trace:heap:HeapAlloc (40360000,00000002,0000002c): returning 403a7a2c Ret ntdll.281: RtlAnsiStringToUnicodeString() retval=00000000 ret=407c5926 fs=008f Call ntdll.132: NtOpenKey(405b6bd4,00000000,405b6b98) ret=407c593d fs=008f trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6bd4) 080687e8: open_key( parent=-2147483648, access=00000000, name=L"Office.SharedMemory.1" ) Create key \\Machine\\Software\\Classes Open key ERROR 080687e8: open_key() = c0000034 { hkey=0 } Ret ntdll.132: NtOpenKey() retval=c0000034 ret=407c593d fs=008f Call ntdll.396: RtlFreeUnicodeString(405b6b90) ret=407c5945 fs=008f trace:heap:HeapFree (40360000,00000002,403a7a2c): returning TRUE Ret ntdll.396: RtlFreeUnicodeString() retval=00000001 ret=407c5945 fs=008f Call ntdll.466: RtlNtStatusToDosError(c0000034) ret=407c594b fs=008f Ret ntdll.466: RtlNtStatusToDosError() retval=00000002 ret=407c594b fs=008f Ret advapi32.211: RegDeleteKeyA() retval=00000002 ret=307907f6 fs=008f Call advapi32.211: RegDeleteKeyA(80000000,3079075c "Office.SharedMemory.1") ret=307907f6 fs=008f Call ntdll.419: RtlInitAnsiString(405b6b88,3079075c "Office.SharedMemory.1") ret=407c591a fs=008f Ret ntdll.419: RtlInitAnsiString() retval=00000016 ret=407c591a fs=008f Call ntdll.281: RtlAnsiStringToUnicodeString(405b6b90,405b6b88,00000001) ret=407c5926 fs=008f trace:heap:HeapAlloc (40360000,00000002,0000002c): returning 403a7a2c Ret ntdll.281: RtlAnsiStringToUnicodeString() retval=00000000 ret=407c5926 fs=008f Call ntdll.132: NtOpenKey(405b6bd4,00000000,405b6b98) ret=407c593d fs=008f trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6bd4) 080687e8: open_key( parent=-2147483648, access=00000000, name=L"Office.SharedMemory.1" ) Open key ERROR 080687e8: open_key() = c0000034 { hkey=0 } Ret ntdll.132: NtOpenKey() retval=c0000034 ret=407c593d fs=008f - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7CQy2pm53PRScYygRAknkAKD4itFKCJQH4hHwXyZBzL0OQP6hjACg54JL YL/rNoN1Zd5m0EsNZ0FZaYU= =nahH -----END PGP SIGNATURE-----

May 21, 2001

Re: problem starting winword 97SR2

by Heiko Nardmann

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 21 May 2001 13:05, Andreas Mohr wrote: > On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote: > > When starting WinWord I get a dialog saying that either I have not enough > > work space or memory space. The program exits then. > > > > So after playing with the debug options I found out that this happens > > after a key named "Office.SharedMemory.1" is accessed inside the > > registry. Can someone tell me what to do to make word no longer complain? > > [HKEY_LOCAL_MACHINE\\Software\\Classes\\Office.SharedMemory.1] > "CLSID" = "{000c0114-0000-0000-c000-000000000046}" > "IID" = "{000c0507-0000-0000-c000-000000000046}" > > But don't think that your Wine config is broken if you don't have registry > settings from an already installed Office ? Hmm ... I did not install Office on my machine, just copied the following files from my Windows NT machine into a separate directory: - - winword.exe - - mso97.dll - - wwintl32.dll To be honest: I even have not installed Windows at all on this machine although I have a license for it. The files stated above are enough to resolve the linker dependencies. Additionally I added a font alias: "Alias0" = "Tahoma,-adobe-helvetica-" This is because I did not get xfstt work together with my Windows Exceed X Server (to use the original tahoma.ttf files). This suppresses the error message saying that it could not find Tahoma font. - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7CQVopm53PRScYygRAhC3AJ9LT7kmMKs70B1pBSxd8Cu/+O5XLwCfQacB cEGRUSg6rZCePcagBBBrWdA= =66Sq -----END PGP SIGNATURE-----

May 21, 2001

Re: problem starting winword 97SR2

by Andreas Mohr

On Mon, May 21, 2001 at 11:30:11AM +0200, Heiko Nardmann wrote: > When starting WinWord I get a dialog saying that either I have not enough > work space or memory space. The program exits then. > > So after playing with the debug options I found out that this happens after > a key named "Office.SharedMemory.1" is accessed inside the registry. Can > someone tell me what to do to make word no longer complain? [HKEY_LOCAL_MACHINE\\Software\\Classes\\Office.SharedMemory.1] "CLSID" = "{000c0114-0000-0000-c000-000000000046}" "IID" = "{000c0507-0000-0000-c000-000000000046}" But don't think that your Wine config is broken if you don't have registry settings from an already installed Office ? -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.germany.net/100-30936/

May 21, 2001