October 2007 - Wine-Devel - list.winehq.org

Re: shlwapi: Update exported API entries according to the info published by Geoff Chappell

by Robert Shearman

Dmitry Timoshkov wrote: > +1 stdcall ParseURLA(str ptr) > +2 stdcall ParseURLW(wstr ptr) > +12 stdcall SHCreateMemStream(ptr long) > +168 stdcall ConnectToConnectionPoint(ptr ptr long ptr ptr ptr) > +169 stdcall IUnknown_AtomicRelease(long) > +172 stdcall IUnknown_GetWindow(ptr ptr) > +174 stdcall IUnknown_SetSite(ptr ptr) > +176 stdcall IUnknown_QueryService(ptr ptr ptr ptr) > +184 stdcall IStream_Read(ptr ptr long) SHIStream_Read > +185 stdcall SHMessageBoxCheckA(ptr str str long long str) > +191 stdcall SHMessageBoxCheckW(ptr wstr wstr long long wstr) > > +199 stdcall IUnknown_Set(ptr ptr) > +203 stdcall SHStripMneumonicA(str) > +204 stdcall SHIsChildOrSelf(long long) > +212 stdcall IStream_Write(ptr ptr long) SHIStream_Write > +213 stdcall IStream_Reset(ptr) > +214 stdcall IStream_Size(ptr ptr) > +215 stdcall SHAnsiToUnicode(str ptr long) > +217 stdcall SHUnicodeToAnsi(wstr ptr ptr) > +219 stdcall QISearch(long long long long) > +225 stdcall SHStripMneumonicW(wstr) > +256 stdcall IUnknown_GetSite(ptr ptr ptr) > +276 stdcall WhichPlatform() > +280 stdcall SHRegGetIntW(ptr wstr long) > +345 stdcall SHAnsiToAnsi(str ptr long) > +346 stdcall SHUnicodeToUnicode(wstr ptr long) > +353 stub SHFormatDateTimeA > +354 stub SHFormatDateTimeW > +388 varargs ShellMessageBoxW(long long wstr wstr long) ShellMessageBoxWrapW > +418 stdcall MLFreeLibrary(long) > +432 stub SHSendMessageBroadcastA > +433 stub SHSendMessageBroadcastW > +437 stdcall IsOS(long) > +462 stub UrlFixupW > +467 stub SHRunIndirectRegClientCommand > +512 stub IStream_ReadPidl > +513 stub IStream_WritePidl > These are all exported by ordinal only up to Windows 2003 SP1 (w/ IE 6.0). +196 stub -noname SHVerbExistsNA #stdcall @(ptr ptr ptr ptr) dnsapi.DnsRecordSetCompare You need to fix the name of the function in the comment here. -- Rob Shearman

Oct. 25, 2007

Re: shlwapi: Update exported API entries according to theinfopublished by Geoff Chappell

by Dmitry Timoshkov

"Alexandre Julliard" <julliard(a)winehq.org> wrote: > "Dmitry Timoshkov" <dmitry(a)codeweavers.com> writes: > >> I've removed -noname for entries that according to Geoff started to be >> exported by name in some Windows versions. We have some such entries >> already. > > If the function was newly added in that version then it's OK, but if > the function is available by ordinal in earlier versions then it has > to be -noname for imports to work correctly. That means that if/once apps start to import shlwapi APIs by name they will not work in Wine. Also, do you mean that APIs for which entries -noname has been already removed need to be fixed to have -noname again? -- Dmitry.

Oct. 25, 2007

Re: shlwapi: Update exported API entries according to the infopublished by Geoff Chappell

by Alexandre Julliard

"Dmitry Timoshkov" <dmitry(a)codeweavers.com> writes: > I've removed -noname for entries that according to Geoff started to be > exported by name in some Windows versions. We have some such entries > already. If the function was newly added in that version then it's OK, but if the function is available by ordinal in earlier versions then it has to be -noname for imports to work correctly. -- Alexandre Julliard julliard(a)winehq.org

Oct. 25, 2007

Re: shlwapi: Update exported API entries according to the infopublished by Geoff Chappell

by Dmitry Timoshkov

"Alexandre Julliard" <julliard(a)winehq.org> wrote: >> @@ -1,18 +1,18 @@ >> -1 stdcall -noname ParseURLA(str ptr) >> -2 stdcall -noname ParseURLW(wstr ptr) >> +1 stdcall ParseURLA(str ptr) >> +2 stdcall ParseURLW(wstr ptr) > > That doesn't look right, why are you removing -noname on these and > many other functions? AFAICT they are not exported by name in most > shlwapi versions. I've removed -noname for entries that according to Geoff started to be exported by name in some Windows versions. We have some such entries already. -- Dmitry.

Oct. 25, 2007

Re: winex11.drv: Support HWND_TOPMOST/HWND_BOTTOM windows using NETWM states.

by Alexandre Julliard

Robert Shearman <rob(a)codeweavers.com> writes: > */ > -static void update_wm_states( Display *display, struct x11drv_win_data *data, BOOL force ) > +static void update_wm_states( Display *display, struct x11drv_win_data *data, > + BOOL force, BOOL set_zorder, HWND insert_after ) > { > static const unsigned int state_atoms[NB_WM_STATES] = > { > XATOM__NET_WM_STATE_FULLSCREEN, > XATOM__NET_WM_STATE_SKIP_PAGER, > - XATOM__NET_WM_STATE_SKIP_TASKBAR > + XATOM__NET_WM_STATE_SKIP_TASKBAR, > + XATOM__NET_WM_STATE_ABOVE, > + XATOM__NET_WM_STATE_BELOW, It's not that easy, there's a lot more to HWND_TOPMOST than simply setting window manager hints, it needs to enforce proper ordering in the server, and set/clear the WS_EX_TOPMOST style as needed. I have that on my todo list... -- Alexandre Julliard julliard(a)winehq.org

Oct. 25, 2007

Re: shlwapi: Update exported API entries according to the info published by Geoff Chappell

by Alexandre Julliard

Dmitry Timoshkov <dmitry(a)codeweavers.com> writes: > @@ -1,18 +1,18 @@ > -1 stdcall -noname ParseURLA(str ptr) > -2 stdcall -noname ParseURLW(wstr ptr) > +1 stdcall ParseURLA(str ptr) > +2 stdcall ParseURLW(wstr ptr) That doesn't look right, why are you removing -noname on these and many other functions? AFAICT they are not exported by name in most shlwapi versions. -- Alexandre Julliard julliard(a)winehq.org

Oct. 25, 2007

Re: COM/DCOM of WINE

by L. Rahyen

On Thursday October 25 2007 08:08, Fong, Man To wrote: > > Dear Sir / Madam, > > > > We are developing a software which is running on Linux platform. The > > software will retrieve the information from TETRA Connectivity Server > > (TCS) which is running on Window 2003 server. The communication > > protocol, pre-defined by TCS manufacturing, is DCOM. Since the > > communication protocol is not opened by the manufacturer. We must > > install the API provided by the manufacturer on our workstation > > running on Linux. Does WINE support the DCOM function? Yes. We recommend to use latest version of WINE (from http://winehq.org or from your distribution repository if it has recent versions). If something will not work for you please fill a bug report at http://bugs.winehq.org . In case if builtin DCOM support doesn't work as expected you can run "winetricks dcom98" to use native DCOM instead (you can download winetricks at http://kegel.com/wine/winetricks ). If this workaround helps you should mention this in your bug report as well. Thanks for using WINE.

Oct. 25, 2007

Re: Anything wrong with my patch from 16.10. about w32x86andwin40creation?

by Markus Gömmel

> We of course have to create the directory, but I think it would be > better if the dll that uses it did that. Hm, so you suggest putting it into WINSPOOL_LoadSystemPrinters()? Cause this looks like the only function who is definitely called during wine startup, isn't it? So we should include creation of "spool" and "spool/drivers" into this as well? Thanks for everybodies time Markus

Oct. 25, 2007

COM/DCOM of WINE

by Fong, Man To

> Dear Sir / Madam, > > We are developing a software which is running on Linux platform. The > software will retrieve the information from TETRA Connectivity Server > (TCS) which is running on Window 2003 server. The communication > protocol, pre-defined by TCS manufacturing, is DCOM. Since the > communication protocol is not opened by the manufacturer. We must > install the API provided by the manufacturer on our workstation > running on Linux. Does WINE support the DCOM function? > > Best Regards, > CLP Engineering > Project Engineer > MT Fong Disclaimer: This e-mail is intended for the addressee(s) only. It is privileged and may also be confidential. Any copying, modification, retransmission or other use of this e-mail or the information contained therein is prohibited. If you are not the addressee(s) or have received this e-mail in error, please contact the sender and delete this email from your computer systems. Internet communications cannot be guaranteed to be timely, secure, error-free or virus-free. The sender will not accept any responsibility for any errors or omissions contained in this e-mail. Website: http://www.clpgroup.com

Oct. 25, 2007

Re: start:start.c Display messages in the console encoding.

by Anatoly Lyutin

Kirill K. Smirnov wrote: > > WriteFile does not output unicode characters to console screen buffer, so if > ConsoleOutputCP is smth like 65001, this will fail. > The page http://msdn2.microsoft.com/en-us/library/ms687401.aspx contains > remedy by Microsoft how to deal with problem: > 1) If device handle is console, then output wide chars using WriteConsoleW > 2) If device handle is not console, then convert wide chars to ConsoleOutputCP > and output using WriteFileA. > > Hmm. I shall work above these a question. Thank you for opinion. > This way is already implemented in cmd (See WCMD_output_asis_len function). > > And it may be much better to convert start utility to unicode. > > Yes, I agree with you. > -- > Kirill > > P.S. all this manipulations is supposed to be done by msvcrt printf function > family, but wine lacks this functionality :-( > -- Best regards Anatoly Lyutin.

Oct. 25, 2007