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

Re: winealsa: improve sound quality for IDsDriverImpl
by Jerry Jenkins 05 Oct '03

05 Oct '03

Robert Reif wrote: > I just cut the parts out of a bigger patch and I guess I missed something. > The memory clearing part is the 8 bit hardware buffer bug fix. The locking > is to fix the SetFormat bug. > > The problem is that when the hardware primary buffer format changes > which causes a new buffer to be mmapped, the mixer thread continues > to use the old deleted buffer address. The timer callback gets the > resource shared which doesn't prevent the primary buffer from changing > it's address even with the new locking I tried to add. It's overkill to > have the timer callback get the resource exclusive every time because > format changes almost never happen and the extra locking is only needed > when they do. > Do you mean that the problem occurs only when we change the format? If this bug will cause continuing interval or click noise which I have encountered, your patch is going to be a big help for me. I am really looking forward to having your patch now :-). But take your time; I'll wait until you finish it.

1 0

Fwd: [ros-kernel] Task Manager
by Steven Edwards 04 Oct '03

04 Oct '03

You guys are going to like this Note: forwarded message attached. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 0

[ANNOUNCE]WineWorks - yet another utility to configure Wine!
by Subhobroto Sinha 04 Oct '03

04 Oct '03

Hello all, well this is NOT yet another effort to imitate WineCfg! WineCfg needs Wine to be running to work. WineWorks does NOT need Wine to be running. WineWorks has been developed using Qt 3.1.1 WineWorks has been written keeping it in mind as MORE of a troubleshooting tool rather than a customization and configuring tool. That is something WineCfg is there for. I intend to make WineWorks as a tool which can HELP a user figure out potential problems which can hinder running Wine on his machine and to resolve those issues so that Wine may be up and going... all from a easy to use GUI. Please try out the program and send reports back to <subhobrotosinha at yahoo dot com> with [WINEWORKS] in the subject line and an optional line appended to it if required. I will soon put the details up on my site as soon as I get a few reports in my mail box. The program is attached compressed as 'WineWorks.zip' and has MD5 Sum '145a82af87efa62c8a694c5a1c18a0a5'. NOTE: It's recommended that you run WineWorks from a shell window to see the trace/debug messages. That way you can see what it's doing behind the scenes and where it went wrong (if it did).. Thanks ;) Regards Subhobroto Sinha __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

2 1

Re: [ANNOUNCE]WineWorks - yet another utility to configure Wine!
by Ivan Leo Murray-Smith 04 Oct '03

04 Oct '03

Cool! It looks great considering it's a 0.1 And it has a brilliant solution for the start menu, OK, maybe IE isn't listed, but it's much more that what wine does now for menus (Nothing). Also, it allows users to know which programs are native linux ones and which ones are windows ones. BTW, this is going to be free software, isn't it? You obviously forgot to link attach the source.

1 0

Re: improve sound quality for IDsDriverImpl
by Robert Reif 04 Oct '03

04 Oct '03

1 0

Of Start Menu, Shortcuts and broken functions...
by Subhobroto Sinha 04 Oct '03

04 Oct '03

Hello all, Recently there has been a revived interest in putting up a 'Windows' like 'Start Menu' onto the Window managers. That's good.Thanks. But as I see it, this task is REALLY easy. Once we resolve the Windows shorcut files,figuring out how to implement the resolved menu entries for respective Desktop environments is dependent on the Desktop environment themselves, and people wanting to implement the 'Start Menu' on that environment. Windows maintains it's 'Start Menu' under '%ROOTDIR%\Documents and Settings\%USER%\Start Menu' (yeah I am talking >=NT,Win2k. For 9x, it will be probably 'C:\WINDOWS\Start Menu'), and this folder contains LOADS of shortcut (.lnk) files. So if we can just recurse through this folder and read out the .lnk files into compatible menu/desktop entries of the corresponding Desktop environment (KDE,GNOME...), we have a working, synchronized 'Start Menu'. And that's JUST what McCormack's 'winemenubuilder' does, and reading out the code I can see it's THE thing we need. Unfortunately, 'winemenubuilder' shipped from Wine-20030618 - the VERY version from which IPersistFile::Load() (the VERY function used to resolve windows shortcuts) got broken, so I could not see 'winemenubuilder' in practise! (Mike, if you are reading this, could you tell me on what Wine ver you originally developed it, and does 'winemenubuilder' work now ? Thanks) You yourself may try out 'winemenubuilder', and if it works let me know. I will know that I was at fault all along,and that would be good news for me ! Now, there arises the problem. Microsoft really does not tell us what's the data structure of .lnk files, though if Alexandre (or somebody of his status..) requested Matt Pietrek for that information, we can probably get it. Till then we are having to do with reverse engg., and let me tell you,that worked fine till Wine-20030618, i.e the Wine tarball release on the 18th June 2003. >From Wine-20030618 , the way Wine handled COM went a MAJOR overhaul, and it worked great in most cases and older code had to rewritten... .. and resolution of shortcuts just stopped working since then. So I have downgraded to using Wine 20030508 since it's the last version till which resolution of shortcuts works (though the code in 'shelllink.c' for this version is not nice to look at ;) ). DETAILS: -------- You see, the resolving of shortcuts is handled through IPersistFile::Load() using COM. The code for this instance of the interface can be found in 'dlls/shell32/shelllink.c'. IPersistFile::Load() calls IPersistFile_fnLoad from 'dlls/shell32/shelllink.c', which passes control to IPersistStream_Load() after a CreateStreamOnFile() call. Now the problem starts in IPersistStream_Load() at/after the following piece of code: 'if( hdr.dwFlags & SCF_DESCRIPTION ) r = Stream_LoadString( pLoadStream, unicode, &This->sDescription );'... Everything before this seems to work just fine! [That's a pity because most of the time we just require the program location from the shortcut file, and that's ALWAYS dumped correctly into 'This->pPidl' You can verify this by adding the following code after 'r = Stream_LoadLocation( pLoadStream );' in 'shelllink.c' LPCITEMIDLIST pidltemp = This->pPidl; do { char szSubho[MAX_PATH]; _dbg_ILSimpleGetText(pidltemp, szSubho, MAX_PATH); TRACE ("name=\"%s\"\n",szSubho); pidltemp = _dbg_ILGetNext(pidltemp); }while (pidltemp->mkid.cb); You need to turn on the trace messages and you shall see the program path resolved allright! I had even tried to put a 'return S_OK;' after the Stream_LoadLocation() call,because ALL i required was the program path, but unfortunately that did NOT work :( ] The call 'Stream_LoadString( pLoadStream, unicode, &This->sDescription );' works in some cases and fails in some. But you can be sure that all the following Stream_LoadString() calls starting from 'Stream_LoadString( pLoadStream, unicode, &This->sPathRel);' WILL fail! It did everytime on my SuSE 8.2,Wine-20030911. Thus, IPersistStream_fnLoad() will NEVER return S_OK ! The last time I debugged, I found that 'IStream_Read(pStm, &len, sizeof(len), &count);' under 'Stream_LoadString( IStream* pStm, BOOL unicode, LPWSTR *pstr )' was failing at/after the 'Description' string was read from the Windows shortcut file, apparently because the 'number of bytes read!=number of bytes to be read'( i.e, for those of you going through the 'shelllink.c' code, the 'count != len' condition was getting satisfied..) You may again verify this by turning on tracing and observing the messages for the above APIs from Wine while running my shortcut resolving code (found in the archives) OR McCormack's 'winemenubuilder'. I hope to get a suitable response to this post. PLEASE correct me if I have gone wrong anywhere! Thanks :=) Also, I will be VERY happy to recieve pseudocode/algorithm for the mentioned APIs specially Stream_LoadString() and IPersistStream_fnLoad() as I am having a hard time understanding a few lines in the code. And could someone send me the layout of .lnk files ? Please keep up the good work. Regards Subhobroto Sinha __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

3 2

Re: winealsa: improve sound quality for IDsDriverImpl
by Jerry Jenkins 04 Oct '03

04 Oct '03

> sox -c1 -r44100 -sw /usr/share/sounds/pop.wav -tossdsp /dev/audio && > wine winamp > > has the problem, but > > sox -c1 -r44100 -sb /usr/share/sounds/pop.wav -tossdsp /dev/audio && > wine winamp > > is unbelievably good. How could it be? I should find out if it's > something is wrong with my system or something else. > Only one of my sound cards suffers from the problem when the format of primary buffer is 22050 samples per second, 8-bit stereo. The other is OK. It appears to be a big challenge for me. And I am a little curious about how many peoples would have such experience. I submitted a new patch, please test it.

3 5

Re: Wineconf 2004, otherwise known as...
by Ivan Leo Murray-Smith 04 Oct '03

04 Oct '03

> I think 2 days is good. Then it can be a weekend. Also, if Lionel lets us know when he's going snowboarding, we can try and avoid that period (Unless he's going from the 1th to the 30th). > > At the last Wineconf, we had a fair number of 'presentations', and > I think we might do better with a bit less of that, and a bit > more 'working sessions'. > > My pet idea was to have an 'installfest', > perhaps the night before, where we brought a stack of CDs and > had Aric and Marcus and all other install experts work feverishly > to get as many of them as possible to install. Install for who? I do want to try and get this thing together, I can let you know for sure by Monday of Tuesday, by then I can also figure out what the costs will be. BTW, are you in visiting anything interesting like Pompei, or do you want to stay in the hotel during all the conference?

1 0

Re: Check before adding http:// in HTTP_DealWithProxy
by Andreas Mohr 04 Oct '03

04 Oct '03

Hi, On Sat, Oct 04, 2003 at 03:34:58PM +0200, Uwe Bonnes wrote: > Changelog: > dlls/wininet/http.c: HTTP_DealWithProxy() > Only add http:// to proxy string when needed > -- > Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de > > Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt > --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- > Index: wine/dlls/wininet/http.c > =================================================================== > RCS file: /home/wine/wine/dlls/wininet/http.c,v > retrieving revision 1.42 > diff -u -r1.42 http.c > --- wine/dlls/wininet/http.c 25 Sep 2003 20:25:22 -0000 1.42 > +++ wine/dlls/wininet/http.c 4 Oct 2003 13:31:53 -0000 > @@ -503,8 +503,12 @@ > UrlComponents.dwStructSize = sizeof UrlComponents; > UrlComponents.lpszHostName = buf; > UrlComponents.dwHostNameLength = MAXHOSTNAME; > - > - sprintf(proxy, "http://%s/", hIC->lpszProxy); > + > + if(strncmp(lpwhr->lpszPath, "http://", sizeof("http://") -1) == 0) Last time I checked (i.e. right now), HtTp was complete case insensitive in my browser... -- Microsoft prepares new round of .doc office format lock-in (just forget about OpenOffice/StarOffice .doc interoperability then, ok?) http://news.com.com/2100-1012_3-5069246.html

1 0

Fw: About Explorer clone
by Martin Fuchs 04 Oct '03

04 Oct '03

Here is the complete mail... Hello, PETREOLLE Sylvain wrote: > Can your explorer clone be compiled with Wine sources and/or tools ? > I have both Windows 2000/XP with latest Cygwin / RedHat Linux environments > to test it. Yes, I have put a "Makefile.Wine" into CVS for compiling as Winelib application. Just put the explorer source into the directory "wine/programs/explorer" and use "make -f Makefile.Wine" zu build it. If it complains about a too old Makefile, issue an "touch Makefile". > Another point : Im not easy with ansi-related questions. > You give 2 versions of explorer into the binary snapshot on your website. > What are the differences between them ? The ANSI version "explorer-ansi.exe" doesn't use Unicode strings. You can use it instead of "explorer.exe" on older systems such as Win 98. To compile the Unicode version add "UNICODE=1" to the make command line. > Both are randomly crashing on my W200 Pro when browsing the Start menu, > which makes me want to have a debug version to see where the crash occurs. If you find out, what causes the crash in your installation, you can inform me of it. My explorer implementation is currently far from complete. The TODO list is growing steadyly. ;-) Martin

1 0