wine-devel

wine-devel@winehq.org

9 participants
84397 discussions

Re: Configuration/Announce
by Alexandre Julliard 22 May '01

22 May '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > First of all, your Wine configuration file now needs a WinMM section > containing the following: > [WinMM] > "Drivers" = "wineoss.drv" > "WaveMapper" = "msacm.drv" > "MidiMapper" = "midimap.drv" > > Not adding this will print the following message > > You didn't setup properly the config file for the Wine multimedia modules. > > Will use the hard-coded setup, but this will disapear soon. > > Please add a WinMM section to your Wine config file. > Note that the above configuration will be shortly required, so don't > wait before setting your configuration up Please keep the defaults. There is no reason to force people to update their configuration file when there are workable defaults that we can use. Ideally Wine should behave reasonably even with an empty configuration file; this is not entirely possible because things like paths don't have reasonable defaults, but forcing people to specify things that we could guess is not user-friendly. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Small clean up
by Francois Gouget 22 May '01

22 May '01

On Tue, 22 May 2001, Dmitry Timoshkov wrote: > Hello. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Small clean up. > > diff -u cvs/wine/dlls/kernel/comm.c wine/dlls/kernel/comm.c > --- cvs/wine/dlls/kernel/comm.c Sun Apr 22 07:54:54 2001 > +++ wine/dlls/kernel/comm.c Thu May 17 14:21:58 2001 > @@ -535,7 +535,7 @@ > return IE_HARDWARE; > } else { > unknown[port] = SEGPTR_ALLOC(40); > - bzero(unknown[port],40); > + memset(unknown[port], 0, 40); > COM[port].fd = fd; > COM[port].commerror = 0; > COM[port].eventmask = 0; Checking for other instances of this problem I found one in 'misc/comm.c'. But CVS claims that: cvs server: misc/comm.c is a new entry, no comparison available Yet I'm pretty sure I did not create such a file. But when a file is deleted CVS should not give me such a message. Is it because I made changes to these files (probably traces) that CVS did not dare delete them? But shouldn't it say 'was removed, no comparison available'? I also have this message for: cvs server: dlls/ddraw/ddraw/dga.c is a new entry, no comparison available cvs server: dlls/ddraw/ddraw/x11.c is a new entry, no comparison available cvs server: dlls/winspool/winspool.spec is a new entry, no comparison available cvs server: misc/comm.c is a new entry, no comparison available -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Broadcast message : fin du monde dans cinq minutes, repentez vous !

2 1

Re: Anybody know int-31?
by Alexandre Julliard 22 May '01

22 May '01

Bob Goodwin <goodie1(a)pacbell.net> writes: > 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. No, the app is supposed to allocate a buffer of the right size (as returned by the int31 call) and pass it to the save/restore function in ES:EDI. Anyway, I'm not sure you need this functionality at all, the current implementation should work OK (except that it needs a dummy protected mode entry point). -- Alexandre Julliard julliard(a)winehq.com

1 0

vxd support?
by Osvaldo Fornaro 22 May '01

22 May '01

Hi, I were far from the project for a while, so sorry if this topic is trivial, but I wish to use a parallel port scanner with wine. Under Windows, appears a device to treat the parallel port as a SCSI port, but is based on a VxD archive, and wine don't find it. Is there any solution to deal with VxD or not yet? Thanks in advance. -- Dr. Osvaldo Fornaro <ofornaro(a)exa.unicen.edu.ar> Universidad Nacional del Centro de la Provincia de Buenos Aires Instituto de Física de Materiales Tandil - CICPBA Pinto 399 (B7000GHG) Argentina

3 3

Question on exposing non-windows functions from dlls...
by Mike Bond 22 May '01

22 May '01

I just submitted a patch to wine-patches that provides the implementation of spawnl and spawnlp. I had been hoping to implement execl and execlp as well but found that the underlying functionality that I would need is not exposed outside scheduler/process.c. My question is what guidelines are there, if any, are there to exposing non-win functions, such as exec_wine_binary in scheduler/process.c? Also, from just a cursory glance at exec_wine_binary that I may need to wrap it to do some of the work that fork_and_exec and PROCESS_Create are doing, such as calling DOSFS_GetFullName. I'm not sure what, if anything, the server would need to know about this. -- TTFN MikeB

3 5

Re: Patch for a bug in server/select.c
by Alexandre Julliard 22 May '01

22 May '01

Bang Jun-Young <bjy(a)mogua.org> writes: > It has been observed that poll always returns POLLNVAL without waiting > when fd is -1. Then we cannot use the current code on NetBSD, otherwise we'll be eating 100% CPU as soon as an fd becomes -1. You'll probably need to do a poll() wrapper that removes the invalid fds before calling the real poll. Or you could ask the NetBSD folks to fix their implementation. -- Alexandre Julliard julliard(a)winehq.com

2 1

history of CVS files?
by Heiko Nardmann 22 May '01

22 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How can I see the history of files in CVS? Is there a WebCVS access provided? Reason: I have a 20010112 version of wine running fine but current CVS version does not start any windows application. - -- 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 iD8DBQE7CiQypm53PRScYygRAuZsAKDhwkJRltKTFWU8Dtmg4DHIOGkYMwCgsusj Izxj4GqmLT7dYzVkEpZVHjA= =DzY7 -----END PGP SIGNATURE-----

3 2

problem starting winword 97SR2
by Heiko Nardmann 22 May '01

22 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? BTW: I use wine 20010112 since the last snapshot 20010418 does not work on my machine (unhandled exception). Here is the last line from the logfile when starting wine with '+reg': trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6d10) - -- 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 iD8DBQE7COAjpm53PRScYygRAibvAKCXFuh51LK3S//Ber6iQSjgjvrmNwCffRTy MRUAdaCXrhST+oDmu5WHjtg= =2kDj -----END PGP SIGNATURE-----

3 6

Re: Small fixes in controls/menu.c
by gerard patel 22 May '01

22 May '01

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 :-/) Gerard

2 1

Re: Wine build failure in tools/winebuild/spec16 due to recent change
by Ove Kaaven 21 May '01

21 May '01

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?

1 0

Jump to page:

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