- Wine-Devel - list.winehq.org

Patch Manager
by Fabian Cenedese Feb. 15, 2003

Feb. 15, 2003

Hi I have never supplied patches myself. But I read all the mails about how to submit patches. I saw on the wxWindows page that they have a Patch- Manager. Mainly just a form to enter all necessary data. Maybe something like that could be useful here too. http://sourceforge.net/tracker/?group_id=9863&atid=309863&func=add bye Fabi

4 3

VC++ nmake not working with Wine 20030115 when it worked with 200208xx
by J. Grant Feb. 14, 2003

Feb. 14, 2003

Hi, Calling nmake from /wcmd/ used to work, now it does not. I can't see why not, here is the debugger ouput if anyone knows whats wrong I'd be happy to hear! Breakpoint 1 at 0x40009bd0 (_end+0x37fae414) *** Invalid address 0x40011f80 (_end+0x37fb67c4) <snip> Unhandled exception: unimplemented function msvcrt.dll.__p__pgmptr called in 32- bit code (0x40733056). In 32-bit mode. 0x40733056 (__wine_unimplemented+0x56 [msvcrt.spec.c:47] in msvcrt.dll.so): jmp 0x40733050 (__wine_unimplemented+0x50 [msvcrt.spec.c:47] in msvcrt.dll.so) 47 for (;;) RtlRaiseException( &rec ); Wine-dbg> There are a few unknown functions with "__p__pgmptr" void __wine_stub_msvcrt_dll_122(void) { __wine_unimplemented("__p__pgmptr"); } I'm not sure why this problem occures now, when it worked before. Comments welcome Regards JG

5 16

Non-applied patches
by Shachar Shemesh Feb. 14, 2003

Feb. 14, 2003

Hi Alexandre, I'm just trying to understand whether you are still trying to fight the backlog, my patches fell through the cracks, or that you decided not to apply them. I am referring to: http://www.winehq.com/hypermail/wine-patches/2003/01/0399.html and http://www.winehq.com/hypermail/wine-patches/2003/01/0401.html If the last option, please explain what is wrong with them. Sh. P.S. A simple mail saying "I'm still fighting the backlog, I'll let you know when I've covered all the submitted patches" will suffice, as far as I'm concerned. -- Shachar Shemesh Open Source integration consultant http://www.consumer.org.il/sun/

2 2

Re: Listview delete column zero
by Duane Clark Feb. 14, 2003

Feb. 14, 2003

Duane Clark wrote: > While the MSDN specifically says that column zero should not be deleted, > it does in fact work on WinNT, and at least one app depends on it. On > WinNT, deleting column zero deletes the last column of items but the > first header. Since no app will ever depend on that bizarre behavior, > we just delete the last column including the header. > I probably should have mentioned why the app deletes column zero. It repeatedly deletes column zero, testing the returned Boolean until it gets false, and then it starts inserting new columns. So it ends up completely replacing the listview contents.

2 2

edit control bug - EM_LIMITTEXT does not work
by Felipe W Damasio Feb. 14, 2003

Feb. 14, 2003

Hi, When you try to limit the maximum chars accepted in an edit control by doing something like this: SendMessage(hwndEdit, EM_LIMITTEXT, 10, 0); Wine simply ignores it, and let the user type more than 10 (in this example) characters. This looks bad, because the user could eventually overflow the allocated memory for the dialog, making the program crash. Cesar Mello (mello(a)elipse.com.br) coded a little program to show this limitation: ftp://ftp.elipse.com.br/pub/about1/about1-src.tar.gz I just created a bug entry on bugs.winehq: http://bugs.winehq.com/show_bug.cgi?id=1280 Could someone help me with this? Thanks a lot and kind regards, Felipe

1 0

Re: For your consideration, here's a preview of some new seh_try_macros-type
by Rolf Kalbermatter Feb. 14, 2003

Feb. 14, 2003

Dan Kegel <dank(a)kegel.com> wrote: >Alexandre Julliard wrote: >> There are people building Wine with the Sun compiler. Also it makes >> sense for at least some dlls to allow building them with MSVC to test >> them under Windows. And in general using different compilers is a good >> way to shake out bugs from the code. > >I always build my conformance tests both in the normal way >and standalone with msvc. >IMHO every executable and DLL we do should run on Windows, too, >if it doesn't absolutely have to make Unix system calls. I regularly compile some of the DLLs under MSVC. The current state of DLLs is so that the non core DLLs compile usually almost fine but linking is a quite big issue I haven't fully tackled. If I link with the MSCV libs I get often undefined imports and linking with MSVC generated import libs from Wine source requires some hand work, as the MSVC IDE only generates the import lib AFTER the entire DLL has been successfully created, so you get sort of a catch 22 situation. Another issue is that most of the DLLs are not yet in a state where they can possibly be put into a current Windows installation, without causing all sorts of crashes and weird problems. The interdependencies between DLLs in a W2K installation is really enormous and a lot of functions in the Wine DLLs are not yet implemented or not fully complient. Rolf Kalbermatter

2 1

DirectSound problems
by Matthieu Foillard Feb. 14, 2003

Feb. 14, 2003

It seems that there is a bug with DirectSound. Using Half-life, when i start the console, it goes into un infinite loop : $ /usr/bin/wine --debugmsg +dsound Program\ Files/Half-Life/hl.exe -- -opengl -game cstrike -windowed -console -noipx 2> /tmp/log it says : ... warn:dsound:DSOUND_MixCancelAt (0x403f6318, 0), buf_mixpos=25296 trace:dsound:IDirectSoundBufferImpl_Unlock (0x403f6318,0x403f6410,65536,(nil),0):stub trace:dsound:IDirectSoundBufferImpl_Lock (0x403f6318,0,65536,0x40760064,0x40760054,0x4076005c,0x40760058,0x00000000) at 60129 trace:dsound:IDirectSoundBufferImpl_Lock ->65536.0 trace:dsound:IDirectSoundBufferImpl_Lock locking prebuffered region, ouch warn:dsound:DSOUND_MixCancelAt (0x403f6318, 0), buf_mixpos=25296 trace:dsound:IDirectSoundBufferImpl_Unlock (0x403f6318,0x403f6410,65536,(nil),0):stub trace:dsound:IDirectSoundBufferImpl_Lock (0x403f6318,0,65536,0x40760064,0x40760054,0x4076005c,0x40760058,0x00000000) at 60129 trace:dsound:IDirectSoundBufferImpl_Lock ->65536.0 trace:dsound:IDirectSoundBufferImpl_Lock locking prebuffered region, ouch ... Over and over and the game console is "lock". If I disable sound (by comment out oss driver in ~/.wine/config) it works fine. I have this problem using both oss and arts driver. Sometimes after some times, it works and the game console unlocks and all goes fine. Sometimes i wait for a long time and it never works. i have an es1370 sound card, kernel 2.4.20, /dev/dsp0 and /dev/dsp1 are both working. It seems that the game menu use /dev/dsp1 and the game itself (e.g. the console) uses /dev/dsp0. I can't explain this. Thanks for your help mgf -- Matthieu Foillard <m.foillard(a)taktile.com> tel : 0146090496 - gsm : 0686574170 pgp : 0x1609654F

1 0

Re: wine/dlls/comctl32 listview.c
by Rein Klazes Feb. 14, 2003

Feb. 14, 2003

On Tue, 11 Feb 2003 16:17:31 -0600, you wrote: > Modified files: > dlls/comctl32 : listview.c > > Log message: > Dimitrie O. Paun <dpaun(a)rogers.com> > Compute matrix of first paint when we actually have some items > (problem first spotted & debugged by Duane Clark). This causes a rgeression in newsbin. The listview with the headers do not update during a "retrieve all headers". Until something else triggers a redraw, eg uncover window pane. From then everything works as expected. Rein. -- Rein Klazes rklazes(a)xs4all.nl

3 3

named pipes still broken?
by Dan Kegel Feb. 14, 2003

Feb. 14, 2003

Is it just me, or are named pipes broken for other people, too? In my tests, Wine can create named pipes, but the reading side can't open them. (Even without my recent changes to sync.c which added filename checking.) - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

Re: 2GB visible partition size
by Duane Clark Feb. 14, 2003

Feb. 14, 2003

Tony Lambregts wrote: > Alexandre Julliard wrote: >> >>Well, yes, if we really need to change the fstype it should be a >>generic option that allows all types to be specified, not just >>NTFS. And it shouldn't overload the existing "type" parameter, it >>should be a separate entry. >> > OK. I guess my biggest problem with this is that the most obvious name > for this entry is "Filesytem" which is already used <g>. Since the parameter of interest is specifically named "fsname" rather than "fstype" or "Filesystem", perhaps that should be the configurable parameter name. I would think that would eliminate any confusion.

2 1