November 2003 - Wine-devel - list.winehq.org

Re: Winealsa : add support for Alsa 1.0
by Alexandre Julliard 27 Nov '03

27 Nov '03

Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: > this patch is an attempt to provide Alsa 1.0 support into winealsa. > > the file audio_09.c is the current audio.c for alsa 0.9 with small > modifications to > ensure compatibility with the new alsa API. I don't think we want yet another duplicate of that code. Please try to support both in the same file, there aren't that many differences. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: RFH: *ReAlloc* mess
by Juan Lang 27 Nov '03

27 Nov '03

NetApiBufferReallocate: - does not allocate memory when NULL is the original pointer passed in - frees memory when the new size is 0 HTH, --Juan __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/

1 0

Descrepancy between Windows and GLIBC version of [v]snprintf
by Daniel Gehriger 26 Nov '03

26 Nov '03

Hi, I found a problem with the _snprintf() / _vsnprintf() functions. Wine seems to use the forward these function calls to their native implementation (eg. in GLIBC). The problem is that they behave differently under Windows and GLIBC: Both function take a parameter to specify the maximum number of characters to write. Under Windows, if the formated string is equal in length to or exceeds the specified number, the terminating NULL will NOT be written to the buffer. Under Linux, the terminating NULL is ALWAYS written. The test program below produces the following output (only when linked dynamically, of course) : Under Windows: 0000000001**** Under Wine: 000000000 When compiled on Linux: 000000000 --------------------------------------------------------- #include <stdio.h> #include <memory.h> int main() { char buffer[16]; memset(buffer, 0, 16); memset(buffer, '*', 15); int len = _snprintf(buffer, 10, "%010d", 1); printf("%d : %s\n", len, buffer); return 0; } --------------------------------------------------------- Regards, Daniel

3 3

PRIVATE flag sends dllwrap for a loop.
by Steven Edwards 26 Nov '03

26 Nov '03

Hello, This is a problem I have had for a while building WINE dlls for use on Windows and ReactOS. When linking the dlls dllwrap always complains that it cant find the symbol private that is added to the .def file. When I remove this symbol and rebuild my import libs and dlls I dont have any problems so lets disable it for now. Changelog: Disable PRIVATE name on for exports in def files. Index: spec32.c =================================================================== RCS file: /home/wine/wine/tools/winebuild/spec32.c,v retrieving revision 1.72 diff -u -r1.72 spec32.c --- spec32.c 3 Nov 2003 22:19:44 -0000 1.72 +++ spec32.c 20 Nov 2003 18:21:56 -0000 @@ -900,7 +900,9 @@ fprintf( outfile, " @%d", odp->ordinal ); if (!odp->name) fprintf( outfile, " NONAME" ); if (is_data) fprintf( outfile, " DATA" ); +#if 0 if (odp->flags & FLAG_PRIVATE) fprintf( outfile, " PRIVATE" ); +#endif fprintf( outfile, "\n" ); } } __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/

2 3

Re: netapi32: implement Netbios()
by Juan Lang 26 Nov '03

26 Nov '03

Hi Uwe et al.. Uwe said: > Saying a little more may help. > > What's needed to test you patch? What programs show > improvement? Good questions. I have little test programs that I've been using, but NetBIOS is hard to test without knowing something about your network configuration, so they're not much use for netapi32/tests. I don't know of any programs that work now that didn't, except what I'm working on: I'm trying to implement the Network Neighborhood. I've been tweaking WINE's SMB code to use Netbios() rather than implementing the netbios-over-tcpip stuff directly. That work isn't done yet, watch this space for more :) There was an article a while back linked here about some HP management program (for their NAS appliance) that didn't discover their box under WINE because of lack of NetBIOS support. I suspect this may now work, but I don't know. > Any configuration items needed in a .ini file or the > registry? Needed? No, should work as-is. You may configure some things in the registry if you need to. Many are configured in the same way as Win98's reg, but not all. I didn't know a good place to document these; comments in winedefault.reg??? > And thanks for your work :-) You're very welcome :) --Juan __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/

1 0

Re: netapi32: implement Netbios()
by Uwe Bonnes 26 Nov '03

26 Nov '03

>>>>> "Juan" == Juan Lang <juan_lang(a)yahoo.com> writes: Juan> Apologies for the size of the patch, I didn't see any useful way Juan> to shrink it. Juan> ChangeLog: implement rather a lot of Netbios() Juan> I could say a bit more than that, but it wouldn't mean much to Juan> most people. Where there was nearly none, now there is some. Saying a little more may help. What's needed to test you patch? What programs show improvement? Any configuration items needed in a .ini file or the registry? Just some thoughts. And thanks for your work :-) 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

debugger problems
by Chris Morgan 26 Nov '03

26 Nov '03

I'm trying to debug a crash in some changes to the jack audio driver and can't seem to have the wine debugger show me the actual source code of the crash. I start up the debugger and get this: oaded debug information from ELF 'wine' ((nil)) No debug information in 32bit DLL 'C:\Program Files\winamp\Winamp.exe' (0x400000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x401d0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x404b0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x408c0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x40840000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x406f0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40a00000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40980000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x40a50000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40aa0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x40900000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x40b50000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINSPOOL.DRV' (0x40c40000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMDLG32.DLL' (0x40bd0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEAUT32.DLL' (0x40c80000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40e10000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEJACK.DRV' (0x410e0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM32.DLL' (0x41130000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM.DRV' (0x41120000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MIDIMAP.DRV' (0x41270000) In 32-bit mode. Wine-dbg> I run and get a crash: Backtrace: =>0 0x41101541 (WINEJACK.DRV..data+0x14541) (ebp=42b87748) 1 0x410e6cbf (WINEJACK.DRV..text+0x5cbf in WINEJACK.DRV) (ebp=42b877cc) 2 0x410e7e10 (WINEJACK.DRV..text+0x6e10 in WINEJACK.DRV) (ebp=42b87804) 3 0x410e9111 (WINEJACK.DRV.wodMessage+0x131 in WINEJACK.DRV) (ebp=42b8783c) 4 0x40b70999 (WINMM.DLL.joySetThreshold+0xd89 in WINMM.DLL) (ebp=42b878ac) 5 0x40b711a4 (WINMM.DLL.joySetThreshold+0x1594 in WINMM.DLL) (ebp=42b878dc) 6 0x40b813e6 (WINMM.DLL.midiStreamStop+0x266 in WINMM.DLL) (ebp=42b87948) 7 0x40b818f4 (WINMM.DLL.waveOutOpen+0x54 in WINMM.DLL) (ebp=42b87974) 8 0x41121362 (MSACM.DRV..text+0x362 in MSACM.DRV) (ebp=42b879a8) 9 0x4112158b (MSACM.DRV..text+0x58b in MSACM.DRV) (ebp=42b87a14) 10 0x411225e7 (MSACM.DRV.wodMessage+0xe7 in MSACM.DRV) (ebp=42b87a4c) 11 0x40b70999 (WINMM.DLL.joySetThreshold+0xd89 in WINMM.DLL) (ebp=42b87abc) 12 0x40b711a4 (WINMM.DLL.joySetThreshold+0x1594 in WINMM.DLL) (ebp=42b87aec) 13 0x40b813e6 (WINMM.DLL.midiStreamStop+0x266 in WINMM.DLL) (ebp=42b87b58) 14 0x40b818f4 (WINMM.DLL.waveOutOpen+0x54 in WINMM.DLL) (ebp=42b87b84) 15 0x42a69ca6 (DSOUND.DLL.DirectSoundCreate8+0x5d6 in DSOUND.DLL) (ebp=42b87c44) 16 0x425f90eb (OUT_DS.DLL..text+0x10eb in OUT_DS.DLL) (ebp=00000000) 0x41101541 (WINEJACK.DRV..data+0x14541): movb %al,0x0(%edx) Wine-dbg>list Enter path to file '': What am I doing wrong here? Chris

3 3

Re: Intresting page
by Ivan Leo Murray-Smith 26 Nov '03

26 Nov '03

> Hmm. I'd be wary of trusting a page with such obviously manipulated > screenshots (check out the different background colours/fonts of some of > the labels), and "Write in HERE or die LMAO!" as the link to the > guestbook :-) I think they manipulated the screenshots to avoid someone hosting them and saying "I took this screenshot on my pc". Also, if you look on google you can find links to pages that talk about neptune, nashville and so on.

1 0

Intresting page
by Ivan Leo Murray-Smith 26 Nov '03

26 Nov '03

Lists (And screenshots) of lots of stuff m$ never released, like windows neptune, Whistler Advanced Server, Cairo, Nashville (Windows 96), windows titanium, windows 99, and more. http://ad-iso.mine.nu/~air101/

2 1

PE stack trick not working on lowmem machines
by Marcus Meissner 26 Nov '03

26 Nov '03

Hi, On SuSE 8.2, i586 glibc, loader/wine-* crash due to the 256 MB static array in main(). The test machine has just 64MB RAM and 200MB swap. If I start decreasing the array it works, up to 201MB. $ /lib/ld-linux.so.2 ./wine-kthread ./wine-kthread: error while loading shared libraries: ./wine-kthread: cannot map zero-fill pages: Cannot allocate memory $ So ld.so really wants to get 20xMB memory but fails. -> Not good on low memory machines. (Not sure if we should fix it.) Btw, why don't we use -Wa,--noexecstack ? Ciao, Marcus

3 3