wine-devel

wine-devel@winehq.org

84471 discussions

rfc: 16bit USER function
by Michael Stefaniuc 25 Sep '02

25 Sep '02

Hello, i would like to move USER functions of the type $type WINAPI $function16(@args) { return $function(@args); } from windows/*.c to dlls/user/user16.c but i don't know if that's the right place to put them because there are already some dlls/user/*16.c files. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

2 1

Re: RESEND: Handle shortened *optval arg. in WS_setsockopt / WS_SO_RCVTIMEO
by Greg Turner 25 Sep '02

25 Sep '02

hmm, somehow this failed to make it through to the list.... Trying again... ---- awesome, thanks for your input Rein! I am no unix sockets guru (nor, obviously, am I a winsock guru ;) so this is really helpful, I'll try and submit a revision to my revision (which is apparently already in wine). That explains the time value out I was seeing of 10,000! 3 hours sounded like an awfully long time to me so I probably should have guessed those were mili's :). Basically, from your advice, I see two options. One, the obvious one, which I'll implement for now, is to convert miliseconds-> <seconds,miliseconds> and be done with it. The other would be a "correct" solution that actually works -- judging by your post, just converting the arguments won't, and I'll need to learn a little bit more about wine-winsock to make it do the right thing. I'll do the easy thing, post it to patches, then look into do_block and get back to the list if I find that this is all beyond my abilities (a quite probable scenario ;) Thanks again for the hand-holding, keep it coming, please, as I may be somewhat "out of my league" here, and I don't want to screw up wine out of ignorance. -- Greg Turner <gmturner007(a)ameritech.net> "Waiting periods are only a step. Registration is only a step. The prohibition of private firearms is the goal." -U.S. Attorney General Janet Reno, December 1993 Rein Klazes wrote: >On Tue, 24 Sep 2002 16:10:43 -0500, you wrote: > > > > >>+ if (level == SOL_SOCKET && optname == SO_RCVTIMEO && optlen < sizeof(struct timeval)) { >>+ if (optlen == sizeof(time_t)) { >>+ /* Apparently WinSock will accept a shortened struct timeval. >> >> > >In Unix the arg optval points to a struct timeval, in windows to a >(32bit) int, no mystery here. The latter is the timeout in >milliseconds. Further a non-zero timeout less then 500 (msec) is taken >as 500 msec. > > > >>+ FIXME: should we do the same for SO_SNDTIMEO? */ >> >> > >Of course, its the same issue. > > > >>+ WARN("Short struct timeval in SO_RCVTIMEO: assuming time_t\n"); >>+ tval.tv_sec = *(time_t*)optval; >>+ tval.tv_usec = 0; >> >> > >You will need to convert from milliseconds here. > > >Unfortunately this does not work (a recv timing out). The socket in >wine is non-blocking internally, any blocking will be done in the >function do_block() using a select(). SO_RCVTMO has no effect there. > >Rein. > -- Greg Turner <gmturner007(a)ameritech.net> "Waiting periods are only a step. Registration is only a step. The prohibition of private firearms is the goal." -U.S. Attorney General Janet Reno, December 1993

1 0

ToDo's
by Thomas Wickline 25 Sep '02

25 Sep '02

Thanks to everyone who has gave feedback on this. Here is a draft of eveything up to today. As always in need of feedback ;) Tom Wine ToDo's as of 9/25/02 Contact : twickline2(a)triad.rr.com Wine ToDo OverView Window management: * Window management needs proper inter-process handling of activation, focus, repaint. National Language Support: * ASCII function work Winsock: * Winsock1 calls,in particular select(),use direct system calls instead of using related wine APIs * More unit tests need to be written * Make sure OOB data is handled properly. Check client-size blocking. * WS2: "provider" interface * WS2: Support other kind of services, like IrDA. * Fix stubs left in ws2_32.spec. DirectSound: * Make the latency configurable (tunable). * More intelligent prebuffering. * Complete support for hardware secondary buffers through the HAL (for a future ALSA multimedia wave audio driver). * 3D sound buffers. * Sound capture (recording). Sound drivers: * Alsa driver (on final 0.9 interface) Video: * Implement native codecs (RLE...) * DIB engine to do 32-bit graphics manipulation DDE: * Enhance memory management issues (interprocess sending) Wineconsole: * Add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind) Native programs: * Winhelp: fix invocation thru WinHelp * Winedbg: make winedbg use dbghelp DLL File management: * Implement NT file namespace * UNC support * Allow flexibility in FS "mounting" (for example, SMB shares) TrueType fonts: * Libfontconfig support Tools: * Wine installation process should install and configure wine * Winemaker fixes * Run C regression tests on Windows with MSVC * Compile Wine with -DSTRICT * Work on WRC as it does not find system headers Instructions: * Write a proper Users Guide Introduction * Documentation updates Aspect or Component: * More DLL Separation * BiDi support * Review of Wine Server Protocol * Finalize Server Protocol * PAM (Pluggable Authentication Modules) * Visual C++'s native COM support * Add DWARF2 support * Speed up PDB support * Create replacement of browser component (Internet Explorer/I Porting issues for Mingw/Cygwin/MS_VC * Better seperation of win16/32 code. * Remove/rewite win16/9x api dependancy on newer code * Remove/rewrite wineisms from code * Documentation fixes low priority items: * VxD support with dynamic loading Add links to: Tasklets: http://bugs.winehq.com/buglist.cgi?keywords=tasklet tasklist: http://bugs.winehq.com/buglist.cgi?keywords=tasklist For a full list of .9/1.0 task's

3 3

Re: ToDo's
by Steven Edwards 25 Sep '02

25 Sep '02

Eric POUECH wrote: >>Here is the status of what I have so far on the ToDo's. >>I am not sure what section to put alot of this in so I just made >>Tools , Instructions & Aspect or Component for now. >>As much feedback as possiable is welcomed . >> >> > >here's some feedback: > >Sound drivers >- Alsa driver (on final 0.9 interface) > >Video: >- implement native codecs (RLE...) > >DDE: >- enhance memory management issues (interprocess sending) > >wineconsole: >- add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind) > >file management: >- implement NT file namespace >- UNC support >- allow flexibility in FS "mounting" (for example, SMB shares) >(NB: I think we should make that clearer and not keep it shadowed in the Aspect/component list) > >(native) programs: >- winhelp: fix invocation thru WinHelp >- winedbg: make winedbg use dbghelp DLL (and implement it of course) > >--8<--------- >remove the Multimedia wave audio section >SEH support has been lately enhanced, is there still known issues ? >IMO, Dwarf2 support should not be added to winedbg. use of gdb proxy should be required instead. (even if it means adding PDB support to gdb, but that'd be a better investment) > >we should make clear what the low priority items are (VxD support with dynamic loading for example) > >A+ > > I dont know if any of these are in any of the TODOs but here goes. all of these would go under porting issues for Mingw/Cygwin/MS_VC - Better seperation of win16/32 code. - remove/rewite win16/9x api dependancy on newer code - remove/rewrite wineisms from code - documentation fixes I think all of this is high priortity but I am biased =) Thanks Steven

2 2

Hand Cursor
by Gustavo Junior Alves 25 Sep '02

25 Sep '02

The "hand cursor" hotspot is in wrong position (lower-right instead in the finger). Where I find information abou how I can fix it? Thanks, Gustavo

2 1

Re: RESEND: Handle shortened *optval arg. in WS_setsockopt / WS_SO_RCVTIMEO
by Rein Klazes 25 Sep '02

25 Sep '02

On Tue, 24 Sep 2002 16:10:43 -0500, you wrote: > + if (level == SOL_SOCKET && optname == SO_RCVTIMEO && optlen < sizeof(struct timeval)) { > + if (optlen == sizeof(time_t)) { > + /* Apparently WinSock will accept a shortened struct timeval. In Unix the arg optval points to a struct timeval, in windows to a (32bit) int, no mystery here. The latter is the timeout in milliseconds. Further a non-zero timeout less then 500 (msec) is taken as 500 msec. > + FIXME: should we do the same for SO_SNDTIMEO? */ Of course, its the same issue. > + WARN("Short struct timeval in SO_RCVTIMEO: assuming time_t\n"); > + tval.tv_sec = *(time_t*)optval; > + tval.tv_usec = 0; You will need to convert from milliseconds here. Unfortunately this does not work (a recv timing out). The socket in wine is non-blocking internally, any blocking will be done in the function do_block() using a select(). SO_RCVTMO has no effect there. Rein. -- Rein Klazes rklazes(a)xs4all.nl

2 1

Re: WineLib and DLLs (Winedump)
by steve.lustbader＠philips.com 25 Sep '02

25 Sep '02

>>> Does it matter that the dll is exporting C++ classes, not straight C >>> functions? >> >>That could make things slightly more complicated, since MS and gcc use >>different name mangling systems. if you declare functions with extern "C" >>linkage you should be OK. However there are differences in how gcc and MS >>call methods on objects (and in the vtable layout etc), so in general its not >>advised to mix win32 c++ dlls with a winelib exe and vice versa (i.e you >>should implement mydll.dll as a real wine dll rather than as just a stub for >>linking). > >Actually, it's a win32 c++ app with lots of win32 c++ dlls and one winelib >c++ dll. The winelib dll depends on two other win32 c++ dlls, which the app >also depends on. I'm trying to avoid turning those other dlls into winelib >dlls, since one of them uses ATL. Am I trying to do something that can't >really be done? Is it possible to make the stub dll that winelib generates I mean take the stub that _winedump_ generates and have it forward the calls >forward calls to the win32 dll (ie, give it both the gcc mangled name and the >msvc mangled name)? > >-Steve

1 0

Re: WineLib and DLLs (Winedump)
by steve.lustbader＠philips.com 25 Sep '02

25 Sep '02

>> Does it matter that the dll is exporting C++ classes, not straight C >> functions? > >That could make things slightly more complicated, since MS and gcc use >different name mangling systems. if you declare functions with extern "C" >linkage you should be OK. However there are differences in how gcc and MS >call methods on objects (and in the vtable layout etc), so in general its not >advised to mix win32 c++ dlls with a winelib exe and vice versa (i.e you >should implement mydll.dll as a real wine dll rather than as just a stub for >linking). Actually, it's a win32 c++ app with lots of win32 c++ dlls and one winelib c++ dll. The winelib dll depends on two other win32 c++ dlls, which the app also depends on. I'm trying to avoid turning those other dlls into winelib dlls, since one of them uses ATL. Am I trying to do something that can't really be done? Is it possible to make the stub dll that winelib generates forward calls to the win32 dll (ie, give it both the gcc mangled name and the msvc mangled name)? -Steve

1 0

Re: d3d8 header patch.
by Dimitrie O. Paun 25 Sep '02

25 Sep '02

On September 25, 2002 09:13 am, Yong Chi wrote: > I gave a .txt extension this time to make sure that the attachment got > treated as a text file. =) Excellent. But you didn't send it in the right format. Do cvs diff -u include/d3d8.h You should add diff -u to your .cvsrc file. -- Dimi.

2 1

another MZ_Exec() problem...
by chrismorgan＠rcn.com 25 Sep '02

25 Sep '02

Inside of MZ_Exec() I call out to CreateProcessA() if the executable is PE. I've set the lpEnvironment parameter of CreateProcessA() to null to have it inherit the environment of the caller but this isn't working correctly. The path and other environment variables aren't being inherited. Ideas on how to either get CreateProcessA() to inherit properly or where I can find the environment settings? I noticed the env_ptr in the parmeter block but I'm unsure if this is what I'm looking for or where to find more information about it. Thanks, Chris

3 2

Re: d3d8 header patch.
by Uwe Bonnes 25 Sep '02

25 Sep '02

>Hello! >I gave a .txt extension this time to make sure that the attachment got > treated as a text file. =) Now again as a unified diff (diff -u), and everybody is hapy :-) Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

how to declare COM class?
by Yong Chi 25 Sep '02

25 Sep '02

Hello! I am one of those lurkers who finally decide to write code after many attempts. I declared a COM class best I can from looking at other COM class but I am getting syntax errors. I could not find any guide/manual on COM development. Can someone help or point to a guide on COM development? Thanks in advance...

4 4

Re: Listview Large Icon (LVS_ICON) rewrite.
by Dimitrie O. Paun 25 Sep '02

25 Sep '02

On September 24, 2002 12:07 am, Guy L. Albertelli wrote: > This is a major rewrite of the LVS_ICON (large icon) code. Not everything > is working correctly yet. Known problems: > 1. Focus rectangles are left drawn incorrectly when scrolling window. I think I know what the problem is, I'll try to fix it. > 2. Background is incorrect for at least Outlook (white instead of grey). Hm, I don't have Outlook. Any pointers and/or ideas? > 3. Scrolling in Outlook is not correct. What's the problem with this one? I might be able to fix it... -- Dimi.

2 1

Re: [patch] Listview fixes
by Dimitrie O. Paun 24 Sep '02

24 Sep '02

On September 24, 2002 05:43 pm, Paul Rupe wrote: > - Initialize memory to prevent crashes when -debugmsg +listview is on > + ZeroMemory(&lvItem, sizeof(lvItem)); Guys, *Please* stop adding these ZeroMemory calls! They just hide bugs, it is almost always the wrong fix (for the listview at least). Alexandre, you can apply the patch, I'll go through the ZeroMemory one more time anyway... -- Dimi.

1 0

ToDo's
by Thomas Wickline 24 Sep '02

24 Sep '02

Hello, Here is the status of what I have so far on the ToDo's. I am not sure what section to put alot of this in so I just made Tools , Instructions & Aspect or Component for now. As much feedback as possiable is welcomed . Tom ----------------------- Wine ToDo's as of 9/24/02 Contact : twickline2(a)triad.rr.com Wine ToDo OverView Window management * Window management needs proper inter-process handling of activation, focus, repaint. National Language Support * ASCII function work Winsock * Winsock1 calls,in particular select(),use direct system calls instead of using related wine APIs * More unit tests need to be written * Make sure OOB data is handled properly. Check client-size blocking. * WS2: "provider" interface * WS2: Support other kind of services, like IrDA. * Fix stubs left in ws2_32.spec Multimedia wave audio * Open Sound System: Support for full-duplex. Fix bugs. * Drivers for other APIs (ALSA, Esound, others). DirectSound * Make the latency configurable (tunable). * More intelligent prebuffering. * Complete support for hardware secondary buffers through the HAL (for a future ALSA multimedia wave audio driver). * 3D sound buffers. * Sound capture (recording). Tools * wine installation process should install and configure wine * winemaker fixes * Run C regression tests on Windows with MSVC * Compile Wine with -DSTRICT * Work on WRC as it does not find system headers Instructions * Write a proper Users Guide Introduction * Documentation updates Aspect or Component * More DLL Separation * BiDi support * Review of Wine Server Protocol * Finalize Server Protocol * VxD support * PAM (Pluggable Authentication Modules) * SEH support * Visual C++'s native COM support * Complete the SMB code (Server Message Block) * Implement WinNT file handling * Add DWARF2 support * Implement a DIB engine * Speed up PDB support * Network UNC path handling * Libfontconfig support * Create replacement of browser component (Internet Explorer/I Add links to: Tasklets: http://bugs.winehq.com/buglist.cgi?keywords=tasklet tasklist: http://bugs.winehq.com/buglist.cgi?keywords=tasklist For a full list of .9/1.0 task's

2 1

RFC: Winsock todo's
by Martin Wilck 24 Sep '02

24 Sep '02

This is a RFC for comments. I may currently be the "offical" winsock maintainer in wine, but I wrote only a very small part of the code. I invite everybody, especially the authors of the other parts of winsock, to comment on these opinions. On Son, 2002-09-22, 18.48 Thomas Wickline wrote: > Can you give me a update on winsock todo's ? > And any other todo that you are aware of .. I have received very few bug reports lately, so I guess the basic Winsock functionality is working. A few important patches went in after the latest CVS snapshot, though. In general, the Winsock implementation in wine has a few parts that look really hackish and would need substantial cleanup. IMO this applies to the async.c file in total, but maybe I am doing injustice to authors of that file. I just find the code is really hard to read. Things like the User-space callbacks in WSAAccept() are impossible to implement correctly because the Unix accept() system call doesn't support callbacks. I do not like the fact that some Winsock1 calls, in particular select(), use direct system calls instead of using related wine APIs, e.g. WaitforMultipleEvents(). Actually if you have sockets with overlapped IO this may cause havoc. Changing this seems to be an average-difficulty task, suitable for contributors with some insight into wine internals. I'd like to see this fixed before 1.0. There are quite a few stubs left in ws2_32.spec. Some of these can probably be implemented easily and would be good work for beginners or casual wine contributors looking for a simple task, e.g. WSADuplicateSocketW(), WSAAddressToString[AW], WSAHtonl(). More unit tests need to be written, also a nice task for people interested in Winsock. Wine has no concept of the Winsock2 "provider" interface. All calls to these functions are either stubs or dummy functions, such as WSAEnumProtocols(). I had a patch for this, but never got it ready for prime-time. It is unrealistic to support a "real" provider interface, allowing (like Windows) to hook new protocol handlers in the network stack, but at least we should pass some realistic information to clients. Should be done for 1.0. There is no such thing as a QOS or socket group concept in wine either, but these seem to be rarely-used features -> post-1.0, if needed at all. Although I had a relevant part in implementing the asynchronous IO in winsock, I am not quite content with it because it is not really asynchronous. Alexandre is against using threads. On Linux at least, Ben LaHaise's asyncio can be expected to become part of the 2.6 kernel series, and if that happens the wine asynchronous IO functionality should be rewritten to use the asyncio API on systems that support it. (I still havent't figured out whether aio will support sockets, though). A non-winsock todo that comes to my mind is support for NT security concepts such as tokens. But that would be a big one and should probably also be postponed after 1.0 Martin -- 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

2 2

Re: Edit updates
by Dimitrie O. Paun 24 Sep '02

24 Sep '02

On September 24, 2002 02:09 am, Dimitrie O. Paun wrote: > This patch is trying to bring the edit.c in line > with the other controls. There is a problem with this patch, please don't apply. -- Dimi.

1 0

Using winbind with Wine
by Martin Wilck 24 Sep '02

24 Sep '02

Hello, There has been a discussion on wine-devel about using winbind for purposes like user authorization, retrieving user and group information, and more. It seemed reasonable to use PAM and NSS for the basic lookups and leave it to the sysadmin to configure these services to use winbind. Winbind offers some more functionality than that, though, such as SID lookups. Continuing along that line, it would be desirable to have a more generic interface than what winbindd currently offers - actually it would be nice to be able to access all RPC calls that samba supports through an interface like winbindd's. * Are there any plans by the Samba team to extend winbindd in this direction? * If no, would the Samba team accept patches from wine developers implementing such extensions to winbindd? * Does winbind support client requests (from the Unix side) where strings are in Unicode format, i.e. could wine pass Unicode strings from Windows applications to windbind directly? * If no, would it be possible to extend winbindd to support this without modifying the samba libraries? Martin -- 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

winebootup
by Raul Dias 24 Sep '02

24 Sep '02

Hi, What happened to winebootup? >From documentation/packaging.sgml: <varlistentry><term><filename>winebootup</filename></term> <listitem> <para> Winelib app to be found in programs/. It'll be called by the winelauncher wine wrapper startup script for every first-time wine invocation. Its purpose is to process all Windows startup autorun mechanisms, such as wininit.ini, win.ini Load=/Run=, registry keys: RenameFiles/Run/RunOnce*/RunServices*, Startup folders. </para> </listitem> </varlistentry> and it not under wine's tree. Does it exist? (or ever did?) Is there something similar to handle RunOnce keys? I just want to avoid doing a duplicated work. []'s Raul Dias

2 1

Re: Correct and update executable types in PathIsExe
by Jeff Smith 24 Sep '02

24 Sep '02

I was just going by what MSDN says. Screensavers (SCR) are just like regular executables with a standard (I believe) command-line arguement interface. I really know next to nothing about SCF files. BTW, my version of Windows (95-OSR-2.1) is so old, it doesn't even have .cmd -- Jeff Smith >From: Alexandre Julliard <julliard(a)winehq.com> >To: "Jeff Smith" <whydoubt(a)hotmail.com> >CC: wine-devel(a)winehq.com >Subject: Re: Correct and update executable types in PathIsExe >Date: 23 Sep 2002 11:13:43 -0700 > >.pif is clearly right, but are you sure about .scr and .scf? My >version of Windows doesn't do that. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

1 0

Re: winapi update
by Alexandre Julliard 24 Sep '02

24 Sep '02

Patrik Stridvall <ps(a)leissner.se> writes: > Fixed some issues found by winapi_check. I'd prefer that we didn't add standard headers on the dll separation hacks. We don't want to give the impression that these functions are legitimate exports. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: export {Start,End}GraphicsExposures from x11drv
by Alexandre Julliard 23 Sep '02

23 Sep '02

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > Fundamentally, the main purpose of a USER driver is to deal > with windowing, and as such, it needs to be able to compute > invalidated areas. It thus makes sense to for it to export > functions that let you query this information. > > The start/end interface used by x11drv makes sense, and it > looks sane enough to be exported. I disagree. Graphics exposures are a very X11 specific concept, they don't belong in the generic driver interface. This kind of change leads to the approach that we used before: do everything in USER and add a few strategically placed calls to x11drv where we really need it. That's the wrong approach, because it cannot be adapted to other drivers except by adding more and more driver calls all over USER. The new approach is to put the driver in charge as much as possible; this means a lot more work is done inside the driver functions, which in turn gives a lot more flexibility. Of course reconciling that with dll separation is not always trivial, but that's part of the fun... -- Alexandre Julliard julliard(a)winehq.com

2 9

Re: Correct and update executable types in PathIsExe
by Alexandre Julliard 23 Sep '02

23 Sep '02

"Jeff Smith" <whydoubt(a)hotmail.com> writes: > Looking at PathIsExe, I thought PID was probably supposed to be PIF > (Program Information File). I checked MSDN, and found this was the > case. I also found two more types that need to be recognized: SCR > (SCReensaver) and SCF (Shell Command File?). .pif is clearly right, but are you sure about .scr and .scf? My version of Windows doesn't do that. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: Correct and update executable types in PathIsExe
by Rolf Kalbermatter 23 Sep '02

23 Sep '02

>Jeff Smith" <whydoubt(a)hotmail.com> writes: > >> Looking at PathIsExe, I thought PID was probably supposed to be PIF >> (Program Information File). I checked MSDN, and found this was the >> case. I also found two more types that need to be recognized: SCR >> (SCReensaver) and SCF (Shell Command File?). > >.pif is clearly right, but are you sure about .scr and .scf? My >version of Windows doesn't do that. It doesn't do it always. I had it once and disabled it immediately since I use an application with its own .scf file types. When enabled it captors the scf files directly on shell level and it wasn't possible to select scf files in the file dialog anymore!!! They are really text files in the way of Ini files. It may be possible that it comes with certain versions of Internet Explorer or Active Desktop or whatever. The scf extension when enabled is linked to SHCmdFile which starts explorer.exe without command arguments and then probably passes a DDE execute command to App: Folders, Topic: AppProperties with the command [ShellFile("%1","%1",%S)]. It is therefore not a Windows executable but really a shell extension feature. SCR files really are special exes. They are usually started by the screen saver control panel or system and not by a user double click. Windows adds links to the HKR keys to execute them as executable but again this happens on the shell level and not in the kernel. The file without any arguments started should display the configuration dialog if any. For the Test case the shell calls the file with argument /S. Installation is done by calling "rundll32.exe desk.cpl,InstallScreenSaver %l". I would not recommend trying to enable scf files at all in Wine. They are certainly no executables. I have no idea how the Wine pholosophy is in terms of enabling and supporting Windows shell features in Wine itself. It seems not useful to do that other than in the internal Wine browser/explorer eventually with help of Shell32. I would believe that Windows makes those types only indirectly executable through their registry entry and the shell which can interprete and resolve them. Rolf Kalbermatter

1 0

Name Mangling in WineLib
by steve.lustbader＠philips.com 23 Sep '02

23 Sep '02

I'm building a WineLib dll in C++ that gets called by a Windows app run by wine. Is there a way to specify how exported function and class names get mangled when compiling with winelib? The Windows app expects MSVC mangled names, so it can't find the exported symbols in my dll, since the names are mangled differently. I'd like to be able to make my dll export the MSVC style names, instead of g++ names. I think spec files used to provide similar functionality, but not any more... -Steve

1 0

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