August 2005 - Wine-Devel - list.winehq.org

Re: LZDone is exported by kernel32

by Alexandre Julliard

Francois Gouget <fgouget(a)free.fr> writes: > Should the same treatment be applied to the other functions too? > Examples: LZStart, LZInit, GetExpandedNameA, etc. > It's strange that winapi_check does not complain about them. > > Does it really work to declare LZDone as exported by multiple dlls in > a single comment? Should winapi_check scan the forwards and ask that > we mention them all in the relevant dll documentation? It's probably better to only mention the dll that the code is in, the documentation for a dll function shouldn't have to know about other dlls that may forward to that function. -- Alexandre Julliard julliard(a)winehq.org

Aug. 10, 2005

Re: Delete Dll(Un)RegisterServer in d3dxof.dll?

by Alexandre Julliard

Francois Gouget <fgouget(a)free.fr> writes: > Now if I look at the APIs exported by d3dxof.dll on various versions > of Windows I don't see these APIs either. However it's possible that > they are only exported in recent versions of DirectX and I'm not sure > the DirectX dlls I have are that recent. > > So I think the question boils down to this: should the > Dll(Un)RegisterServer functions be removed or should they be exported? They should probably be removed, and the corresponding classes and interfaces should be registered by some other dll. -- Alexandre Julliard julliard(a)winehq.org

Aug. 10, 2005

Re: Protect included headers with the proper autoconf macros

by Jacek Caban

Francois Gouget wrote: > On Wed, 10 Aug 2005, Jacek Caban wrote: > [...] > >> But it won't change anything as if HAVE_LIBXML2 is defined >> then HAVE_LIBXML_PARSER_H is defined too, so >> #ifdef HAVE_LIBXML_PARSER_H will be always true here. > > > Yes but if you remove the #ifdef HAVE_LIBXML_PARSER_H check > winapi_check will rightly complain that the include is unprotected > because it, nor the casual reader, will know all the complex relations > between HAVE_LIBXML_PARSER_H and HAVE_LIBXML2. > Ah, I see. So Mike's solution is good for this. Jacek

Aug. 10, 2005

Re: Protect included headers with the proper autoconf macros

by Francois Gouget

On Wed, 10 Aug 2005, Jacek Caban wrote: [...] > But it won't change anything as if HAVE_LIBXML2 is defined > then HAVE_LIBXML_PARSER_H is defined too, so > #ifdef HAVE_LIBXML_PARSER_H will be always true here. Yes but if you remove the #ifdef HAVE_LIBXML_PARSER_H check winapi_check will rightly complain that the include is unprotected because it, nor the casual reader, will know all the complex relations between HAVE_LIBXML_PARSER_H and HAVE_LIBXML2. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Hiroshima '45 - Czernobyl '86 - Windows '95

Aug. 10, 2005

Re: LZDone is exported by kernel32

by Francois Gouget

On Wed, 9 Aug 2005, Vincent Béron wrote: > Changelog: > LZDone is also exported by kernel32 now. Should the same treatment be applied to the other functions too? Examples: LZStart, LZInit, GetExpandedNameA, etc. It's strange that winapi_check does not complain about them. Does it really work to declare LZDone as exported by multiple dlls in a single comment? Should winapi_check scan the forwards and ask that we mention them all in the relevant dll documentation? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ May your Tongue stick to the Roof of your Mouth with the Force of a Thousand Caramels.

Aug. 10, 2005

crosscompiler

by Dimitrije Jankovic

Recently, a target option was added to winebuild, and winebuild code was changed to use this option instead of preprocessor defines. I was wondering if a similar option will be added to winegcc, based on which it would pass the corresponding option to winebuild. When using winegcc to crossbuild wine dlls between different platforms (for instance x86-linux and sparc-solaris) that have different endianess more problems arise, especially related to resources. The resource compiler has --endianess option that caould be used to crosscompile resources, but winebuild always reads resource files as if they were compiled natively, maining --endianess cannot be used to crossbuild. Correct me if I'm wrong. If I want to be able to crossbuild from x86-linux to sparc-solaris, I need to compile resources with big-endianess and have winebuild use the target option to recognize that resource file was compiled with big-endianess and read it as such, and not natively. This is not the case currently. Like I said, winebuild reads the res file using native byteorder and fails to check res header. Regards, Dimitrije

Aug. 10, 2005

Missing functions in wldap32.spec

by Francois Gouget

Hi, I scanned the Wine spec files and compared them to the APIs exported on Windows and discovered that the following APIs were missing from wldap32.spec. I don't know if that's intentional, maybe you're planning to add them later on. In any case here's the list: cldap_open cldap_openA cldap_openW ldap_abandon ldap_add ldap_addA ldap_addW ldap_add_ext ldap_add_extA ldap_add_extW ldap_add_ext_s ldap_add_ext_sA ldap_add_ext_sW ldap_add_s ldap_add_sA ldap_add_sW ldap_cleanup ldap_close_extended_op ldap_connect ldap_control_free ldap_control_freeA ldap_control_freeW ldap_controls_free ldap_controls_freeA ldap_controls_freeW ldap_count_entries ldap_count_references ldap_count_values ldap_count_valuesA ldap_count_valuesW ldap_count_values_len ldap_create_page_control ldap_create_page_controlA ldap_create_page_controlW ldap_create_sort_control ldap_create_sort_controlA ldap_create_sort_controlW ldap_delete ldap_deleteA ldap_deleteW ldap_delete_ext ldap_delete_extA ldap_delete_extW ldap_delete_ext_s ldap_delete_ext_sA ldap_delete_ext_sW ldap_delete_s ldap_delete_sA ldap_delete_sW ldap_encode_sort_controlA ldap_encode_sort_controlW ldap_escape_filter_element ldap_escape_filter_elementA ldap_escape_filter_elementW ldap_extended_operation ldap_extended_operationA ldap_extended_operationW ldap_first_attribute ldap_first_attributeA ldap_first_attributeW ldap_first_entry ldap_first_reference ldap_free_controls ldap_free_controlsA ldap_free_controlsW ldap_get_next_page ldap_get_next_page_s ldap_get_paged_count ldap_get_values ldap_get_valuesA ldap_get_valuesW ldap_get_values_len ldap_get_values_lenA ldap_get_values_lenW ldap_modify ldap_modifyA ldap_modifyW ldap_modify_ext ldap_modify_extA ldap_modify_extW ldap_modify_ext_s ldap_modify_ext_sA ldap_modify_ext_sW ldap_modify_s ldap_modify_sA ldap_modify_sW ldap_modrdn ldap_modrdn2 ldap_modrdn2A ldap_modrdn2W ldap_modrdn2_s ldap_modrdn2_sA ldap_modrdn2_sW ldap_modrdnA ldap_modrdnW ldap_modrdn_s ldap_modrdn_sA ldap_modrdn_sW ldap_msgfree ldap_next_attribute ldap_next_attributeA ldap_next_attributeW ldap_next_entry ldap_next_reference ldap_parse_page_control ldap_parse_page_controlA ldap_parse_page_controlW ldap_parse_reference ldap_parse_referenceA ldap_parse_referenceW ldap_parse_result ldap_parse_resultA ldap_parse_resultW ldap_parse_sort_control ldap_parse_sort_controlA ldap_parse_sort_controlW ldap_rename_ext ldap_rename_extA ldap_rename_extW ldap_rename_ext_s ldap_rename_ext_sA ldap_rename_ext_sW ldap_result ldap_search_abandon_page ldap_search_init_page ldap_search_init_pageA ldap_search_init_pageW ldap_set_dbg_flags ldap_set_dbg_routine ldap_set_option ldap_set_optionA ldap_set_optionW ldap_sslinit ldap_sslinitA ldap_sslinitW ldap_startup ldap_value_free_len -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ There are 10 types of people in the world... those who understand binary and those who don't.

Aug. 10, 2005

IE6 installer claims unimplemented function in advpack.dll (IsNTAdmin)

by Hans Kristian Rosbach

Wine CVS of about 1 hour old. ie6setup.exe from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=1e1550cb-5e5d-48f5… $ wine ie6setup.exe fixme:advapi:CheckTokenMembership ((nil) 0x6ed886d0 0x7fddfd9c) stub! fixme:advapi:DecryptFileA "C:\\install\\IXP000.TMP\\" 00000000 fixme:advpack:TranslateInfString ("C:\\install\\IXP000.TMP\\IESetup.inf" "Options.NTx86" "Options.NTx86" "InstallDir" 0x10253f8 260 0x7fdcf83c (nil)): stubfixme:advpack:NeedReboot (0x00000000): stub wine: Call from 0x1013ac7 to unimplemented function advpack.dll.IsNTAdmin, aborting wine: Unhandled exception (thread 000b), starting debugger... -HK

Aug. 10, 2005

Delete Dll(Un)RegisterServer in d3dxof.dll?

by Francois Gouget

Hi, I'm relaying a question from Vincent Béron: we both had a look at the winapi_check output and noticed that the comments of these functions claim they are exported but in fact they are not: they are not mentioned anywhere in the spec file. Now if I look at the APIs exported by d3dxof.dll on various versions of Windows I don't see these APIs either. However it's possible that they are only exported in recent versions of DirectX and I'm not sure the DirectX dlls I have are that recent. So I think the question boils down to this: should the Dll(Un)RegisterServer functions be removed or should they be exported? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Good judgment comes from experience, and experience comes from bad judgment -- Barry LePatner

Aug. 10, 2005

Re: Porting Device Drivers to Winehq

by Damjan Jovanovic

--- John Shillinglaw <jshillinglaw(a)hotpop.com> wrote: > Hello, > > Can anyone point me to documentation/help or tools > for disassembling > Windows 95 drv and vxd files and/or porting them to > wine?? > > I have a Roland SCP-55 Soundcanvas card (pcmcia ) > which is not > recognized by linux, and Windows XP ( which I don't > like using anyway ) > will not recognize the drivers when it prompts for a > driver file. > > Ideally I'd like to decode the windows drivers to > help with developing a > pure linux driver. > > Barring that, it seems that I should have better > luck with wine since it > happly emulates and runs win 95 stuff. > > However, while I've found plenty in the wine docs > about running /porting > windows _programs_, almost nothing about what to do > with the win 95 > *.inf *.drv *.vxd and *.ini that come in the driver > package for the > pcmcia card. > > Thanks for the help, > John > > Running 2.6.12-gentoo-r6 and Wine-072505 on an IBM > T20 Pentium III > Thinkpad. > Hmmm... if you had a .sys file, it would be easy to reverse engineer, since Windows WDM drivers are nicely stacked and it is easy to insert "filter" drivers into the stack, to monitor IRP flow. Tools like usbsnoopy do this for USB drivers, I believe there are similar ones that work for other drivers in general. I never had a look at how you write VxD's, but there is stuff in the MSDN library (it should be accessible online, look for VDDs in the Windows DDK documentation). And have a look at whether the ReactOS project supports VxD's. Good luck, such device drivers are very ugly :-). Damjan Jovanovic ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

Aug. 10, 2005