wine-devel

wine-devel@winehq.org

15 participants
84452 discussions

Re: VersionNumber reg. key
by Jeff Smith 05 Sep '02

05 Sep '02

My $0.02: I say don't create, and dynamically 'lie' about it's value. I'm sure it's easier said than done, but that's my thoughts, anyway. -- Jeff S >From: Ender <winedev(a)admdev.com> >To: wine-devel(a)winehq.com >Subject: VersionNumber reg. key >Date: Wed, 4 Sep 2002 21:28:32 -0500 (CDT) >read the HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\VersionNumber >key. And of course, as this is a 'required' key in Windows, there was no >code to cope with failure :) >whether or not Wine should dynamically 'lie' about this registry key, >depending what winver the current thread is running in. > - Ender _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

3 2

[Bug 448] - need help debugging 16-32-bit parameter passing
by Martin Wilck 05 Sep '02

05 Sep '02

Included below are my latest results for Bug 448. The problem there is that winsock connects to port 512 although a service at port 5557 was specified. The winsock functions seem to work correctly: -> getservbyname16 returns port 0x15b5 = 5557 -> connect16 receives port 512 (!) directly after that. (the only thing that happens in between is a socket() call). The interesting part is that 512 in network byte order is 0x0002, i.e. the same as the protocol family (0x0002=AF_INET). Is it possible that something gets overwritten here when connect() is called? My problem is that I have no clue hall the magic relaying between 16 and 32 bit code in wine works. Perhaps someone can give me a hint? Martin ------- Additional Comments From martin.wilck(a)fujitsu-siemens.com 2002-09-05 07:58 ------- I finally got some time to look into this. It does not seem to be a winsock error. By inserting some TRACES, I can clearly see that getservbyname() correctly returns port 5557 (hex 0x15b5): trace:winsock:WINSOCK_getservbyname16 "ctsql", "tcp" trace:winsock:__ws_getservbyname name ctsql proto tcp flag 2 i 6 trace:winsock:WS_dup_se s_name ctsql s_port 15b5 s_proto tcp trace:winsock:WS_dup_se 16 s_port 15b5 trace:winsock:__ws_getservbyname s_name ctsql s_port 15b5 s_proto tcp [ ... ] But when "connect" is called, it is passed port 512 (hex 0200): trace:winsock:WINSOCK_connect16 socket 0048, ptr 0x40c493d6, length 16 sockaddr_in: family 2, address 172.25.186.5, port 512 02 00 02 00 ac 19 ba 05 00 00 00 00 00 00 00 00 Interestingly, (since the port is in network byte order) the hex patterns for address family and port are both 0x0002. This looks as if either - the app is assigning the family to the port number (?) (This would mean that the shouldn't be able to run on Windows either, since you say all was fine in 20011108, there must be another reason) - something goes wrong when the argument is passed from the 16- to 32bit layer. Have to look further. -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

1 0

Trying to debug Paradise Poker client
by Per Nystrom 05 Sep '02

05 Sep '02

Hi, I filed bug 1007 (kernel32.dll.Heap32* functions unimplemented) on this, but I'm not even sure that's the real problem. One thing that I'm seeing is retval=00000000 (FALSE) from all the calls to advapi32.CryptAcquireContextA() -- since this application relies *heavily* on encryption, I wonder if this is a good place to start. If I run it with the advapi32 dll overridden to use native, I get a different error and the App seems to crash even earlier in its execution. The following is what I got using the native advapi32 dll: fixme:file:VxDCall_VMM Unknown service 00010029 08070158:Ret kernel32.VxDCall4() retval=ffffffff ret=bfe81d8d fs=008f eax=ffffffff ebx=00000000 ecx=4011faa8 edx=405c6a00 esi=00000064 edi=00000001 ebp=405c6d5c esp=405c6d40 ds=002b es=002b gs=0ac7 flags=00000202 08070158:Call kernel32.CreateEventA(00000005,00000064,00000001,71467c2a "\205\300u\020h\024$EqSj\001S\377\327\243LPJqU\350\304\262\377\377;\363t\007V\377\025<\022Eq_^][\303\203=LPJq") ret=00000001 err:win32:CreateEventW Bad security attributes pointer 0x5 08070158:Ret kernel32.CreateEventA() retval=00000000 ret=00000001 wine: Unhandled exception, starting debugger... I'm attaching the entire relay trace (compressed) from running with the builtin advapi32 dll; it's much larger but probably more useful for fixing the problem. Any help is greatly appreciated! Per Nystrom System specifics: wine was built from the very latest in the CVS repository as of tonight Pentium II, 128Mb RAM and 1+ Gb swap running Red Hat 7.1 with updated X (4.2.0) glibc-2.2.4-29 gcc-2.96-81 -- "When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl."

2 1

Re: [PATCH] winsock-test.diff
by Alexandre Julliard 05 Sep '02

05 Sep '02

Martin Wilck <Martin.Wilck(a)Fujitsu-Siemens.com> writes: > Rationale: > - Make it easier to add new unit tests. > - Conform better to the usual wine unit testing scheme > (instead of running different tests from the same file, > run separate files testing different functionality) That's not really the usual scheme. It may look that way because we have few tests at the moment, but we can't put each test in a separate file, or we will end up with thousands of them. The right approach is to follow more or less the layout of the source files, that is if two APIs are implemented in the same source file they should be tested in the same test file; so I think the current winsock tests are OK as they are. And in any case #including .c files is strongly discouraged. -- Alexandre Julliard julliard(a)winehq.com

2 1

Tab Controls without name
by Fabian Cenedese 05 Sep '02

05 Sep '02

Hi I found something that would be easy to fix in case it really should be fixed. Working with tab controls I have the case where I set the tab name to empty because it's too big to be shown. In the TCITEM structure I set the text pointer to NULL instead of a "". Thus Wine stopped at some point doing a strlen on a NULL pointer. Obvious. Then I checked MSDN if this is allowed or not. It always says string pointer, never is a NULL pointer a possible value. Ok, so my code is wrong, easy to change. But still (the often cited sentence): It used to work in Windows. So now I don't know if Wine should be clean (and NULL pointer in tab name is not allowed) or if it should behave as Windows (no matter what docs say) and a NULL pointer is just an empty name... bye Fabi

2 2

VersionNumber reg. key
by Ender 05 Sep '02

05 Sep '02

Hi all, A few weeks ago I was setting up a fake-windows install, and ran across a few pieces of software that just crashed.. like the Visual Studio installer. After a little bit of investigation, I discovered these were trying to read the HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\VersionNumber key. And of course, as this is a 'required' key in Windows, there was no code to cope with failure :) At the very least this should be added to the default registry with a dummy value (oh yeah, values are like: "4.90.3000"). But my question is whether or not Wine should dynamically 'lie' about this registry key, depending what winver the current thread is running in. Thoughts? - Ender

1 0

Re: Partial implementation of NotifyRegister notifications
by Alexandre Julliard 05 Sep '02

05 Sep '02

Joshua Thielen <thielen(a)netprince.net> writes: > I expect there to be problems with this patch (some of it is probably > a bit over my head) so eyes are requested, please! I already know that > the number and order of the segment messages (NFY_LOADSEG and FREESEG) > doesn't exactly match those sent in Windows, and I'm not totally sure > of the affect this patch will have on 16-bit memory and threading > details in wine. You should really have some kind of TOOLHELP_SendNotification function instead of calling wine_call_to_16_regs all over the place. Also the handling of segmented pointers (especially the lpstrModuleName) doesn't look right. Apart from that, it looks quite reasonable. -- Alexandre Julliard julliard(a)winehq.com

1 0

Catching MFC exception
by Fabian Cenedese 04 Sep '02

04 Sep '02

Hi I found one of the wrong behaviours though I don't know where to solve it. For creating an ocx one can give a window title. I gave a "" to the CreateControl function. But this poses a problem to MFC, it's only prepared for valid strings or NULL pointers. That's why it generates the exception: void AFXAPI AfxThrowOleException(SCODE sc){ #ifdef _DEBUG TRACE1("Warning: constructing COleException, scode = %s.\n", AfxGetFullScodeString(sc)); #endif COleException* pException = new COleException; pException->m_sc = sc; THROW(pException); } In Windows this is caught by another function in MFC and doesn't do any harm: BOOL AFX_CDECL COleControlSite::SafeSetProperty(DISPID dwDispID, VARTYPE vtProp, ...) { va_list argList; // really only one arg, but... va_start(argList, vtProp); BOOL bSuccess; TRY { SetPropertyV(dwDispID, vtProp, argList); bSuccess = TRUE; } CATCH_ALL(e) { DELETE_EXCEPTION(e); bSuccess = FALSE; } END_CATCH_ALL va_end(argList); return bSuccess; } Now it seems that the exception handling inside (or wherever) the MFC.dll doesn't work if running in Wine or the MFC exceptions are different and the exception comes right through. I can overcome this problem by giving a valid window title but that solves it only for me. I have no idea how and if this can be solved but maybe this description gives a hint to a programmer with more insight. Thanks Fabi

2 1

Re: LsaNtStatusToWinError implementation
by Andriy Palamarchuk 04 Sep '02

04 Sep '02

--- Andriy Palamarchuk <apa3a(a)yahoo.com> wrote: > Changelog: > Implemented LsaNtStatusToWinError, conformance > tests, added definitions of the error and status > constants, used by the function. Please ignore this patch. I just found out that I should call RtlNtStatusToDosError from this function instead of implementing the mapping myself. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

1 0

Wine error codes
by Sylvain Petreolle 04 Sep '02

04 Sep '02

hi, having problem with IE 6 exiting immediately using a patched shdocvw, I would know if wine exit codes are documented somewhere ? ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel