August 2005 - Wine-Devel - list.winehq.org

Re: PATCH: winelauncher tmp file

by Vincent Béron

Le mar 09/08/2005 à 16:23, Marcus Meissner a écrit : [snip] > @@ -87,6 +87,7 @@ > > # ok, we really give up now, this system is hosed ;-) > cat $MSGFILE > + rm MSGFILE + rm $MSGFILE But I'm pretty sure Alexandre would have catched it... Vincent

Aug. 9, 2005

Re: wine/ tools/winegcc/winegcc.c tools/winegcc/Ma ...

by Marcelo Duarte

Hum.... I do make and the error occurs compile ntdll. I do make again and it builds. Is this behavior correct? OS Fedora Core 2 gcc --version gcc (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7) Marcelo Duarte escreveu: > This patch cause a error: winegcc: prelink failed. > OS: Fedora Core 2 with last updates from Lecacy Fedora. > > ... > Alexandre Julliard escreveu: >> Log message: >> Added support for the --image-base linker option in winegcc using >> the >> prelink tool. >> >> >> > > >

Aug. 9, 2005

Re: MSHTML: Report BINDSTATUS_MIMETYPEAVAILABLE in AboutProtocol::Start [RESEND]

by Alexandre Julliard

Jacek Caban <jack(a)itma.pwr.wroc.pl> writes: > Is there something wrong with this patch? It breaks make test because one of the todo_wine tests now partially succeed. Could you please fix the test and resubmit? -- Alexandre Julliard julliard(a)winehq.org

Aug. 9, 2005

Re: WINEALSA: remove crackling in DirectSound/ALSA combination

by Jacek Caban

Hello. Alex Villacís Lasso wrote: > > * Can somebody check if the DirectSound tests actually pass in Windows? You can check it here: http://test.winehq.org/data/ Jacek

Aug. 9, 2005

Re: Porting Device Drivers to Winehq

by John Shillinglaw

Thank you all for your help. I was vaguely aware that wine could not use the 95 drivers for my card, and developing pcmcia-cs / alsa drivers was my goal. Finding accurate, recent win 95 decodeing info/ tools on the net was difficult, and I knew that wine developers face the same problem in developing wine to support apps. Your help was a good start in my endeavor and thank you again. On Tue, 2005-08-09 at 11:00 -0400, Kuba Ober wrote: > > > wine-devel(a)winehq.org

Aug. 9, 2005

Re: wine/ tools/winegcc/winegcc.c tools/winegcc/Ma ...

by Marcelo Duarte

This patch cause a error: winegcc: prelink failed. OS: Fedora Core 2 with last updates from Lecacy Fedora. Output: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./kernel32.spec comm.drv.spec.o krnl386.exe.spec.o stress.spec.o system.drv.spec.o toolhelp.spec.o win87em.spec.o windebug.spec.o atom16.o error16.o registry16.o toolhelp16.o win87em.o actctx.o atom.o change.o comm.o computername.o console.o cpu.o debugger.o dosmem.o editline.o environ.o except.o fiber.o file.o file16.o format_msg.o global16.o heap.o instr.o kernel_main.o lcformat.o local16.o locale.o lzexpand.o module.o ne_module.o ne_segment.o oldconfig.o path.o powermgnt.o process.o profile.o pthread.o relay16.o resource.o resource16.o selector.o snoop16.o stress.o string.o sync.o syslevel.o system.o tape.o task.o thread.o thunk.o time.o toolhelp.o utthunk.o version.o virtual.o volume.o vxd.o windebug.o wowthunk.o relay16asm.o kernel32.dll.dbg.o kernel.res -Wl,--image-base,0x7b800000 -o kernel32.dll.so -L../../dlls -L../../dlls/ntdll -lntdll -L../../libs/wine -lwine -L../../libs/unicode -lwine_unicode -L../../libs/port -lwine_port winegcc: prelink failed. make[2]: ** [kernel32.dll.so] Erro 2 make[2]: Leaving directory `/home/mduarte/wine/dlls/kernel' make[1]: ** [kernel] Erro 2 make[1]: Leaving directory `/home/mduarte/wine/dlls' make: ** [dlls] Erro 2 Alexandre Julliard escreveu: >ChangeSet ID: 19399 >CVSROOT: /opt/cvs-commit >Module name: wine >Changes by: julliard(a)wine.codeweavers.com 2005/08/09 06:12:30 > >Modified files: > tools/winegcc : winegcc.c Makefile.in > . : configure.ac configure Make.rules.in > >Log message: > Added support for the --image-base linker option in winegcc using the > prelink tool. > >Patch: http://cvs.winehq.org/patch.py?id=19399 > >Old revision New revision Changes Path > 1.39 1.40 +32 -3 wine/tools/winegcc/winegcc.c > 1.14 1.15 +2 -1 wine/tools/winegcc/Makefile.in > 1.391 1.392 +6 -0 wine/configure.ac > 1.690 1.691 +48 -1 wine/configure > 1.187 1.188 +1 -0 wine/Make.rules.in > > > > >

Aug. 9, 2005

WINEALSA: remove crackling in DirectSound/ALSA combination

by Alex Villacís Lasso

For a long time, I have been annoyed by a faint crackling that can be heard on the sound output of any DirectSound program when full hardware acceleration is enabled on the ALSA driver. Even after a patch I sent earlier (which corrected a bigger artifact), this crackling remained. Last night, I finally set upon removing this crackling, based on a comment in IDsDriverBufferImpl_GetPosition() in dlls/winmm/winealsa/audio.c, line 3302: //* /*FIXME*/: snd_pcm_mmap_hw_ptr() should not be accessed by a user app. *// //* It will NOT return what why want anyway. *// hw_ptr = _snd_pcm_mmap_hw_ptr(wwo->pcm); I thought, maybe it is not returning the correct information for GetPosition, so that is why the crackling exists, since new samples are off-position from what they should be in order to guarantee a smooth sound. So I deduced, maybe the IDsDriverBufferImpl object can keep a simulation of a hardware pointer and use that instead of the (slightly incorrect) hardware pointer. My original intention was to remove entirely the need to reference _snd_pcm_mmap_hw_ptr(), since this is obviously an internal alsa-lib function and should not be used from inside the app (as the comment rightly indicates). However, I found out that the simulated hardware pointer tends to lag behind the real hardware pointer, and horrible mixups happen if the difference approaches or exceeds the length of the mmap buffer. So the simulated pointer is loosely kept close to the hardware pointer in the supplied patch. The good news: the patch sort of works (in my setup, at least, with Fedora Core 4). All the games I have (Japanese RPGs) now have smooth sound, unless the CPU load is too high. The bad news: the patch does nothing to make the dsound tests pass in Wine (but they were already failing before the patch :-) What I would like to know is the following: * Is there any ALSA user for which the DirectSound tests have *actually* passed? In full acceleration mode? * Can somebody check if the DirectSound tests actually pass in Windows? The test code seems very straightforward, but (in my setup at least) they trigger many more errors and FIXMEs than my RPGs, and that is even without taxing the CPU with graphics and bitmap manipulation, as the RPGs do. * Can somebody using the ALSA driver acknowledge whether they have the crackling problem too, and whether this patch actually solves it for them too? * Can somebody please test this patch (even if they don't have the crackling issue) and check whether any previously working game breaks because of it? Also, can some ALSA or DirectSound guru comment on the specifics of *why* the patch actually works? I am not entirely convinced that a mere loose updating of the simulated pointer from the hardware pointer is enough to have a smooth sound, but it works. I also don't understand how did the crackling appear in the first place, even though the direct hardware pointer was used. Any comments or reports are welcome (especially why the patch works). Alex Villacís Lasso Changelog: * Remove crackling in DirectSound/ALSA playback with full hardware acceleration

Aug. 9, 2005

Re: Porting Device Drivers to Winehq

by Kuba Ober

On Tuesday 09 August 2005 10:19, John Shillinglaw wrote: > Hello, > > Can anyone point me to documentation/help or tools for disassembling > Windows 95 drv and vxd files and/or porting them to wine?? > > I have a Roland SCP-55 Soundcanvas card (pcmcia ) which is not > recognized by linux I'd start by politely asking Roland for the specs. Only if they openly refuse it's time to start working on a linux driver. As far as using wine for the task, I bet you might be better off instead by looking how the ndiswrapper folks have done it for NDIS drivers. Probably there's some wine code that you could snatch to implement something special that the driver needs, but presumably it'll be all rudimentary low-level stuff related to interfacing with the PCMCIA stack and so on, which is not present in wine anyway IIRC. Disclaimer: I'd start by extending ndiswrapper, but there of course are other ways :) Cheers, Kuba

Aug. 9, 2005

Re: Porting Device Drivers to Winehq

by Andreas Mohr

Hi, On Tue, Aug 09, 2005 at 10:19:24AM -0400, John Shillinglaw wrote: > Hello, > > Can anyone point me to documentation/help or tools for disassembling > Windows 95 drv and vxd files and/or porting them to wine?? This is a rather totally wrong kind of query, since Wine won't be able to help you at all, since it doesn't support any binary VxDs. You really want to try ALSA instead, and especially look at http://www.alsa-project.org/alsa-doc/index.php?vendor=vendor-Roland_Edirol#… which unfortunately doesn't list any SCP-xxx card. > I have a Roland SCP-55 Soundcanvas card (pcmcia ) which is not > recognized by linux, and Windows XP ( which I don't like using anyway ) > will not recognize the drivers when it prompts for a driver file. This is an all too common situation... > Ideally I'd like to decode the windows drivers to help with developing a > pure linux driver. Very nice! That's the only really useful solution anyway... Oh, and I'd like to especially encourage you to *not* throw that card away and buy a new one, since Linux *does* need more sound drivers in order to be able to finally support *all* cards on the market. I've written an ALSA driver for the entirely undocumented Aztech PCI168 card (a low-end, crap card), by spending some weeks reverse-engineering Windows drivers using IDA (Interactive DisAssembler). (you might want to search the wine-devel archive for recent discussions of IDA, since someone asked about a nice selection of good disassemblers) > However, while I've found plenty in the wine docs about running /porting > windows _programs_, almost nothing about what to do with the win 95 > *.inf *.drv *.vxd and *.ini that come in the driver package for the > pcmcia card. ...since we don't (~= cannot) support that at all. It should be done entirely via Linux kernel driver anyway. Another idea would be to try and see whether virtual machines such as VMWare can give an insight what the hardware interface looks like. But, most importantly, you should ask Roland whether they will give you (parts of) the card specs required to be able to write a driver (without laborous reverse-engineering, that is). And of course you should read all relevant ALSA pages about supporting an undocumented sound card. And maybe the SCP-55 card is similar to another Roland card supported by ALSA? That could be a start... Feel free to ask me about further ALSA driver specifics, I may be able to help. Andreas

Aug. 9, 2005

Re: Porting Device Drivers to Winehq

by Juan Lang

Hi John, > Can anyone point me to documentation/help or tools for disassembling > Windows 95 drv and vxd files and/or porting them to wine?? No. Wine doesn't provide support for device drivers. We have some fake VxDs in there, just for some old apps that called them to do non-device driver type things. > Ideally I'd like to decode the windows drivers to help with developing a > pure linux driver. Yep, that's what you'll want to do. Disassembly may help. People around here seem to like IDA Pro. Search the wine-devel archives for more suggestions for disassemblers. Good luck, --Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Aug. 9, 2005