wine-devel

wine-devel@winehq.org

8 participants
84486 discussions

Re: Registry problem
by steve.lustbader＠philips.com 09 Oct '02

09 Oct '02

I'm using the latest cvs source (I update every day). I tried using a native advapi32 (from WinXP, which is all I have access to), but that just resulted in lots of other problems (unimplemented functions in ntdll.dll, etc. When I try to run WinAmp, it exits immediately with that same error. It doesn't run at all, unlike the installer, which runs but then ends with the error (probably when it tries to run winamp itself). Is it possible that sound isn't set up properly on my system? I don't really need sound on it, so I haven't played around with it too much. It's just the normal Redhat 7.2 install, with whatever sound settings it picked. I can listen to mp3's with xmms, though. -Steve Sylvain Petreolle To: Steve Lustbader/ANR/MS/PHILIPS@AMEC <spetreolle@yaho wine-devel(a)winehq.com o.fr> cc: Subject: Re: Registry problem 10/09/2002 02:18 AM Classification: What version of wine did you use ? With CVS of Oct 08, I install without problem. --- steve.lustbader(a)philips.com a écrit : > I started having a problem with today's source that appears > to be either registry or sound related. When I tried to > install Winamp (v 2.81 lite) in wine, I get this error: > > wine client error:8091280: sendmsg: Bad file descriptor > > Output from +reg,+relay ends with > > 08091280:Call > ntdll.NtQueryValueKey(00000048,40124878,00000002,406e2acc,00000100,406e2ac0) > ret=40977acc > trace:reg:NtQueryValueKey (0x48,L"WaveMapper",2,0x406e2acc,256) > wine client error:8091280: sendmsg: Bad file descriptor > > (the last 100 lines of the output can be seen at > http://www.lustbader.net/winamp.txt) > > I tried getting rid of my ~/fake_c and ~/.wine directories > and running wineinstall again, but that didn't help. > > -Steve > > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 2

Registry problem
by twickline2＠triad.rr.com 09 Oct '02

09 Oct '02

-Steve PS - Uwe, I'd love to be able to quote email correctly, but I'm forced to use Lotus Notes at work, which doesn't seem to know how to reply very well. If anyone knows how to make Notes behave like a normal mail client, let me know. Reply and cut out what you don't need...... Posted from Lotus Notes Build V60_M13_04032002 Tom

1 0

Re: Registry problem
by steve.lustbader＠philips.com 09 Oct '02

09 Oct '02

I tried the cvs source from October 7, and the problem doesn't occur (although winamp does crash with an unimplemented MSVCRT function when I try to run it). steve.lustbader+FromInterNet@ philips.com To: Sylvain Petreolle <spetreolle(a)yahoo.fr> Sent by: cc: wine-devel(a)winehq.com wine-devel-admin(a)winehq.com (bcc: Steve Lustbader/ANR/MS/PHILIPS) Subject: Re: Registry problem 10/09/2002 10:42 AM Classification: I'm using the latest cvs source (I update every day). I tried using a native advapi32 (from WinXP, which is all I have access to), but that just resulted in lots of other problems (unimplemented functions in ntdll.dll, etc. When I try to run WinAmp, it exits immediately with that same error. It doesn't run at all, unlike the installer, which runs but then ends with the error (probably when it tries to run winamp itself). Is it possible that sound isn't set up properly on my system? I don't really need sound on it, so I haven't played around with it too much. It's just the normal Redhat 7.2 install, with whatever sound settings it picked. I can listen to mp3's with xmms, though. -Steve Sylvain Petreolle To: Steve Lustbader/ANR/MS/PHILIPS@AMEC <spetreolle@yaho wine-devel(a)winehq.com o.fr> cc: Subject: Re: Registry problem 10/09/2002 02:18 AM Classification: What version of wine did you use ? With CVS of Oct 08, I install without problem. --- steve.lustbader(a)philips.com a écrit : > I started having a problem with today's source that appears > to be either registry or sound related. When I tried to > install Winamp (v 2.81 lite) in wine, I get this error: > > wine client error:8091280: sendmsg: Bad file descriptor > > Output from +reg,+relay ends with > > 08091280:Call > ntdll.NtQueryValueKey(00000048,40124878,00000002,406e2acc,00000100,406e2ac0) > ret=40977acc > trace:reg:NtQueryValueKey (0x48,L"WaveMapper",2,0x406e2acc,256) > wine client error:8091280: sendmsg: Bad file descriptor > > (the last 100 lines of the output can be seen at > http://www.lustbader.net/winamp.txt) > > I tried getting rid of my ~/fake_c and ~/.wine directories > and running wineinstall again, but that didn't help. > > -Steve > > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 1

Re: Major tidy up of Scroll.c to add foundations for flatscroll bars
by Alexandre Julliard 09 Oct '02

09 Oct '02

"Andrew M. Johnston" <johnstonam(a)logica.com> writes: > controls.h - improve the scroll bar nonclient separation > nonclient.c - remove NC_TrackScrollBar and use scrollbar WINAPI routine > scrollbar.c - complete rewrite using similar structure and logic > - unified drawing code > - simpler event processing logic > - minimised drawing > - better conformance to windows on LINEUP and LINEDOWN events All the flat scrollbar stuff has nothing to do in scroll.c, the normal scrollbars shouldn't need to know anything about flatsb at all. The flatsb control should intercept messages it needs to change by subclassing the windows, and call down to the normal scrollbar where necessary. > Note: it is possible to split the scroll changes up into three consistent parts if > really necessary That would be nice. Also if you could avoid unnecessary changes like renaming SCROLLBAR_INFO to SCROLL_INFO that would make it easier to see what is really being changed. -- Alexandre Julliard julliard(a)winehq.com

3 5

Listview
by Dimitrie O. Paun 09 Oct '02

09 Oct '02

Hi folks, Here's a quick status update on the listview. Currently, the listview goes through a major cleanup. It is required -- the file is huge (over 10000 lines when I started, now it's 9200 with more features!), and has accumulated a lot of cruft over the last few years. This is very normal for such a complex control as listview, and we need to prep the code to add more features. At the same time, I go over the code, review it for correctness, fix bugs, and implement the missing functionality. While it may look I do mostly code reorganizations, this is not the case: a lot of corner bugs have been fixed, functionality has been enhanced, code has been cleaned up, and simplified. Due to the cleaner code base, we are in a better position to fix problem, and add features. The downside of all this is that (1) old bugs, and missing functionality is exposed, (2) new bugs are introduced. On top of it all, two major efforts were happening simultaneously: Guy's ICON mode work, and mine. Guy did a wonderful job at fixing some of the issues in ICON mode, unfortunately my changes interacted with his in a nasty way. So we have some problems. I am aware of some of them, and I'm working to fix them. But it will take some time, as I trying to fix a problem, I see some cleanup that needs doing _before_ I work on the bug itself. Currently, I am aware of the following problems: -- selection (clicking on items sometimes does not select them) -- drawing (focus, background, etc.) -- calculating item rectangles If you are experience problems with the listview, I'd like to hear from you. If you want to help, some test cases will help quite a bit. -- Dimi.

3 10

wine on sparc solaris
by Juraj Hercek 09 Oct '02

09 Oct '02

Hi, Since no one had similar problems as I did on sparc solaris (no reply to my previous email sent to wine-devel on /Wed Oct 02 2002 - 09:38:12 CDT/ ). I started to debug it. First problem lies here: $WINE_ROOT/dlls/ntdll/virtual.c:986 There is a condition that says: (char *)base + size > (char *)ADDRESS_SPACE_LIMIT If base+size is above address space limit, NtAllocateVirtualMemory fails. Problem is, that addresses returned by wine_anon_mmap function ($WINE_ROOT/library/port.c:458) - which in turn calls system mmap - are far behind ADDRESS_SPACE_LIMIT (ADDRESS_SPACE_LIMIT=0xc0000000, definition in $WINE_ROOT/dlls/ntdll/virtual.c:110). Just to be precise, they are around 0xfe000000 and higher. I changed address space limit to -1, just to avoid this problem (I know, this is probably not the best solution, but I didn't find better one at the moment). After this change NtAllocateVirtualMemory passed. When I run it again, I got stuck in setup_dos_mem() function ($WINE_ROOT/msdos/dosmem.c:489) where is error saying: "Cannot use first megabyte for DOS address space, please report." After deeper insight I figured out that try_mmap_fixed() function failed ($WINE_ROOT/library/port.c:431), because memory page we were trying to allocate was alredy mapped. So, question is: Is there any way how to solve these two problems (address space limit, already mapped pages) correctly? Thanks for reply. Juraj

1 0

LoadLibrary during PROCESS_ATTACH
by Uwe Bonnes 09 Oct '02

09 Oct '02

Hallo, I am trying to debug Xilinx webpack version 5.1. If I understand things right, the "ise" application crashed because it unloads a dll, but later still accesses this dll. This seems to happen, because during MODULE_InitDLL of the dll it calls a Loadlibrary on itself. As MODULE_InitDLL sets WINE_MODREF_MARKER, and the flow of execution in LoadLibrary checks for WINE_MODREF_MARKER before incrementing the RefCount, the refcount gets wrong and the application unloaded. Forcing the increment of RefCount in MODULE_LoadLibraryExA unconditional of WINE_MODREF_MARKER makes the application continue. Do we need the check for WINE_MODREF_MARKER in MODULE_LoadLibraryEx? Do we still need MODULE_LoadLibraryEx at all? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 2

Registry problem
by steve.lustbader＠philips.com 09 Oct '02

09 Oct '02

I started having a problem with today's source that appears to be either registry or sound related. When I tried to install Winamp (v 2.81 lite) in wine, I get this error: wine client error:8091280: sendmsg: Bad file descriptor Output from +reg,+relay ends with 08091280:Call ntdll.NtQueryValueKey(00000048,40124878,00000002,406e2acc,00000100,406e2ac0) ret=40977acc trace:reg:NtQueryValueKey (0x48,L"WaveMapper",2,0x406e2acc,256) wine client error:8091280: sendmsg: Bad file descriptor (the last 100 lines of the output can be seen at http://www.lustbader.net/winamp.txt) I tried getting rid of my ~/fake_c and ~/.wine directories and running wineinstall again, but that didn't help. -Steve

4 4

Re: Re: jack audio driver
by chrismorgan＠rcn.com 08 Oct '02

08 Oct '02

> > From: Eric Pouech <eric.pouech(a)wanadoo.fr> > Date: 2002/10/08 Tue PM 03:48:04 EDT > To: Chris Morgan <cmorgan(a)alum.wpi.edu> > CC: wine-devel(a)winehq.com > Subject: Re: jack audio driver > > Chris Morgan a écrit : > > > > I have an audio driver for the jack audio server, > > http://jackit.sourceforge.net. This is a callback based server, so each time > > the server needs audio data it executes a client callback function. I was > > wondering if there was any interest in having this driver as part of mainline > > wine code as an example of how to write a wine audio driver for a callback > > based architecture. > well, it depends what you look at > jack way well be the standardized API for audio application > interoperability on Linux > but, some folks may argue that arts may well become the same > as of today, I don't like the number of sound drivers that we already > have (OSS, alsa, arts, nas) just for linux > it, of course, reflects the mess in low level audio interface in linux It really is a mess. It seems clear that we should do away for the most part with having applications interface directly with sound drivers like oss/alsa, and instead go through sound servers like arts/jack/etc. In technical aspects a callback based architecture is far superior to a polling based architecture. It has a lower latency and enforces a cleaner sound implementation on applications. What I haven't seen yet is a widely used audio server that people agree upon. Someone really needs to take the lead and start pushing a callback based sound server that is under active development(arts appears not to be) that is not kde/gnome specific.</rant> > what I really fear is the real maintenance of those drivers > as of today, OSS is maintained, I cannot really tell the same for the > others > it's never a bad idea to share code, but I fear we're not going to be > able to maintain all the drivers (but we don't maintain them all today > anyway) > so go for it > (sorry for thinking while writing ;-) Wonder when we can phase out the OSS driver and concentrate on the ALSA one. Seems like a waste to support two drivers that fulfill the same role. Chris

2 1

jack audio driver
by Chris Morgan 08 Oct '02

08 Oct '02

I have an audio driver for the jack audio server, http://jackit.sourceforge.net. This is a callback based server, so each time the server needs audio data it executes a client callback function. I was wondering if there was any interest in having this driver as part of mainline wine code as an example of how to write a wine audio driver for a callback based architecture. Chris

2 1

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