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

Re: [Wine]Softlinking to a dvd-drive with inconsistent mount points? => HAL-Support

by Jesse Allen

On 8/27/05, wino(a)piments.com <wino(a)piments.com> wrote: > > Your Amiga example is fine, asking for the second of a pair of production > disks by name is helpful and the critisism of win2k not finding the CD in > F: is valid. But all that has nothing to do creating rediculous pathnames > which will inevitably not fit into any message box or space allowed for > file name display. You will end up having to scroll around , resize > everything and even then you will probably be missing the filename cos it > got chopped off. > > Well, I see no point of naming a mount point the label of the disk, when an installer can just look at the label when a disk is inserted for automatic detection anyways! So we are talking about how well an installer is written. Having these mount points do not improve the usability of the installer.

Aug. 27, 2005

Re: [Wine]Softlinking to a dvd-drive with inconsistent mount points? => HAL-Support

by Jesse Allen

On 8/27/05, Detlef Riekenberg <wine.dev(a)web.de> wrote: > > Am Freitag, den 26.08.2005, 12:50 +0200 schrieb Holly Bostick: > > >>Problem solved: > > >>http://portal.suse.com/sdb/en/2005/05/dkukawka_hal_mountpoints.html > > > > Thanks Hiji, that was useful for me too. > > Thats an ugly workaround that should be forbidden. See Below. > > > > It might be nice to be able to symlink "d::" to /dev/hdc > > > and have wine figure out where that's mounted, > > > instead of having to specify both the device and the mount point. > > IMHO thats the only possible Way and wine must go that Way ASAP! > (and use the old method for systems, where the new way dis not work) No. I don't want that at all. Many times I mount a loop back iso image to /mnt/cdrom. Wine needs to look there first because I'm wanting /mnt/cdrom to emulate a cd-drive in wine, not have wine look for where /dev/hdc is mounted and find it's not mounted at all. In another words, I use the wine environment to emulate disks for me, without the need of emulation software in wine.

Aug. 27, 2005

Re: [Wine]Softlinking to a dvd-drive with inconsistent mount points? => HAL-Support

by wino＠piments.com

On Sat, 27 Aug 2005 21:57:06 +0200, Detlef Riekenberg <wine.dev(a)web.de> wrote: > Am Freitag, den 26.08.2005, 12:50 +0200 schrieb Holly Bostick: > >>> Problem solved: >> >>http://portal.suse.com/sdb/en/2005/05/dkukawka_hal_mountpoints.html > >> > Thanks Hiji, that was useful for me too. > > Thats an ugly workaround that should be forbidden. See Below. > >> > It might be nice to be able to symlink "d::" to /dev/hdc >> > and have wine figure out where that's mounted, >> > instead of having to specify both the device and the mount point. > > IMHO thats the only possible Way and wine must go that Way ASAP! > (and use the old method for systems, where the new way dis not work) > > >> Of course ~/.wine/drive_c (or wherever it's placed since Wine now >> allows you to place the wine directory on first run), is going to >> automatically be C:\. > > This is the default Location used by "wineprefixcreate" > >> The user's $HOME directory, >> >> is automatically symlinked to D:\ > > "D:\" is not created by "wineprefixcreate". > >> /tmp, ..., is automatically symlinked to E:\, which Wine seems to > > "e:\" is not created by "wineprefixcreate". > "c:\windows\temp" is used as the default Temporary Directory. > >> C:\Windows\temp, where it always is under Windows) > > This is the default Location in win9x, if "TEMP" is not set in > "config.sys" or "autoexec.bat" when starting this DOS-Taskswitcher. > > %USERPROFILE%\Local Settings\Temp" is the default for W2k and above. > (Replace the second Part with the Translation in your Language). > (WinNT 4.0 is > > The actual Location is always found in "TEMP" > >> / , being the third of the necessary directories that everyone is known >> to have, is automatically symlinked to Z:\ > > This is also created by "wineprefixcreate" > > >> I honestly don't know what SuSE was thinking with that one-- what >> earthly reason could the majority of users have to need their CD/DVD >> mounted to the label of the media itself? Yeah, I want /media/Far Cry >> one minute, and /media/Office 2003 the next. Like I even know the LABEL >> of most of the media I mount (and that's just retail disks, nothing said >> about backup disks or other self-burned media). So how am I supposed to >> know where it is, if I don't know the label? > > That's the best thing they did, but many Years to late! > > I used this semantic since 1985 when the computers had one or two > floppy-disks, the hd was optional with a size about 40MB and was very > surprised, when i changed my system. > > When a different medium (Disk) was needed and not present, the first > system asks: > 'Please insert Volume "Application, Disk 2" in any Drive'. > The system detected the Media-Change and closed the Requester automatic, > no matter in which Drive you inserted the Disk > (DF0:, DF1: DF2 or DF3: for Floppy-Disks). > Even the Requester was created automatic, when the required medium was > not found and the Application did not forbid this behaviour explicit. > > About 20 Years later in 1994, a different System told me to insert the > "Installation CD #2" in drive "E:" and was unable to detect, that the > required medium was already present in drive "F:". > > Thats the way: The software-vendors are inflexible and the users do not > complain. > > The First system was my Amiga and the second was the Software "WISO > Sparbuch 2004" on Windows 2000. > > > So with the HAL-System, linux is on the right way. > Please do not be fixed on the old style, be flexible. > > Software need to use "/media/LABEL_OF_THE_MEDIA" to be more flexible, > but that do not work, if the user create that ugly workaround above. > >> I could maybe see it for USB sticks, or Flash cards, >> but those are different rules than the ones for CD/DVD drives. > > Which rules? > Why use different behaviour? > They are all media! > > Even Linux can use the semantic with the Volume-Label. > No matter, on which Harddisk or which Partition the Files are. > Mount find the Label. > >> And I don't even like this /media thing anyway; half >> the time I start typing ls -la /mnt/wherever and get nothing (of >> course). Phooey. > > Thats the Problem. The change was very late and many user must learn the > flexible way. > > > IMHO, it's required for wine to handle the HAL-Message-System ASAP. > > Yuck! It does not surprise me at all that SuSE has gone that way , it is trying to be a semi-free, semi-open source windows replica. And for better and for worse is going a long way to achieving that aim. This sort of thing sucks (incidentally "suse" is french for suck ... in every sense of the term!). I dont think it is old-fashioned or inflexible to expect a cdrom I put in my cd drive to end up at /mnt/cdrom . It makes more sense than "/media/Some dumb, long name with spaces and/or commas (c)2005 Beetlejuice-inc.com" . I can be expected to know whether I put my medium in the CD drive or the USB port. I may not know the volume names of all the possible "flexible" media mounted in CDs DVDs USBs Bluetooth devices and God knows what else at any given time and I see no utility in having to type ls /media and start guessing. Your Amiga example is fine, asking for the second of a pair of production disks by name is helpful and the critisism of win2k not finding the CD in F: is valid. But all that has nothing to do creating rediculous pathnames which will inevitably not fit into any message box or space allowed for file name display. You will end up having to scroll around , resize everything and even then you will probably be missing the filename cos it got chopped off. Basically it's a mess. Give me /mnt/dvd anyday, and keep gatesisms out of Linux. I get the feeling I am soon going to hate suse as much as XP. (well, OK, not quite. It does have its good points!) Thanks for the link to the xml hack, it may come in useful one day.

Aug. 27, 2005

Re: accessing WRT binaries on the web

by Hans Leidekker

On Saturday 27 August 2005 13:34, Filip Navara wrote: > >Is this some kind of conflict between the MinGW definitions and wine's own > >version? > > I remember Hans incorrectly adding these defintions to the MinGW library I remember that too now :-). I wrongly assumed Wine's header was correct. Paul, there's a patch in my RPMS that backs out these defines. It's called w32api_lib_directx_dxguid_c_02.patch.gz -Hans

Aug. 27, 2005

Re: [Wine]Softlinking to a dvd-drive with inconsistent mount points? => HAL-Support

by Detlef Riekenberg

Am Freitag, den 26.08.2005, 12:50 +0200 schrieb Holly Bostick: >>Problem solved: > >>http://portal.suse.com/sdb/en/2005/05/dkukawka_hal_mountpoints.html > > Thanks Hiji, that was useful for me too. Thats an ugly workaround that should be forbidden. See Below. > > It might be nice to be able to symlink "d::" to /dev/hdc > > and have wine figure out where that's mounted, > > instead of having to specify both the device and the mount point. IMHO thats the only possible Way and wine must go that Way ASAP! (and use the old method for systems, where the new way dis not work) > Of course ~/.wine/drive_c (or wherever it's placed since Wine now > allows you to place the wine directory on first run), is going to > automatically be C:\. This is the default Location used by "wineprefixcreate" > The user's $HOME directory, > > is automatically symlinked to D:\ "D:\" is not created by "wineprefixcreate". > /tmp, ..., is automatically symlinked to E:\, which Wine seems to "e:\" is not created by "wineprefixcreate". "c:\windows\temp" is used as the default Temporary Directory. > C:\Windows\temp, where it always is under Windows) This is the default Location in win9x, if "TEMP" is not set in "config.sys" or "autoexec.bat" when starting this DOS-Taskswitcher. %USERPROFILE%\Local Settings\Temp" is the default for W2k and above. (Replace the second Part with the Translation in your Language). (WinNT 4.0 is The actual Location is always found in "TEMP" > / , being the third of the necessary directories that everyone is known > to have, is automatically symlinked to Z:\ This is also created by "wineprefixcreate" > I honestly don't know what SuSE was thinking with that one-- what > earthly reason could the majority of users have to need their CD/DVD > mounted to the label of the media itself? Yeah, I want /media/Far Cry > one minute, and /media/Office 2003 the next. Like I even know the LABEL > of most of the media I mount (and that's just retail disks, nothing said > about backup disks or other self-burned media). So how am I supposed to > know where it is, if I don't know the label? That's the best thing they did, but many Years to late! I used this semantic since 1985 when the computers had one or two floppy-disks, the hd was optional with a size about 40MB and was very surprised, when i changed my system. When a different medium (Disk) was needed and not present, the first system asks: 'Please insert Volume "Application, Disk 2" in any Drive'. The system detected the Media-Change and closed the Requester automatic, no matter in which Drive you inserted the Disk (DF0:, DF1: DF2 or DF3: for Floppy-Disks). Even the Requester was created automatic, when the required medium was not found and the Application did not forbid this behaviour explicit. About 20 Years later in 1994, a different System told me to insert the "Installation CD #2" in drive "E:" and was unable to detect, that the required medium was already present in drive "F:". Thats the way: The software-vendors are inflexible and the users do not complain. The First system was my Amiga and the second was the Software "WISO Sparbuch 2004" on Windows 2000. So with the HAL-System, linux is on the right way. Please do not be fixed on the old style, be flexible. Software need to use "/media/LABEL_OF_THE_MEDIA" to be more flexible, but that do not work, if the user create that ugly workaround above. > I could maybe see it for USB sticks, or Flash cards, > but those are different rules than the ones for CD/DVD drives. Which rules? Why use different behaviour? They are all media! Even Linux can use the semantic with the Volume-Label. No matter, on which Harddisk or which Partition the Files are. Mount find the Label. > And I don't even like this /media thing anyway; half > the time I start typing ls -la /mnt/wherever and get nothing (of > course). Phooey. Thats the Problem. The change was very late and many user must learn the flexible way. IMHO, it's required for wine to handle the HAL-Message-System ASAP. -- By By ... ... Detlef

Aug. 27, 2005

Re: [d3d8] use wined3dformat when calling wined3d #2 resent

by Jesse Allen

On 8/26/05, Oliver Stieber <oliver_stieber(a)yahoo.co.uk> wrote: > > This patch is a resend of an earlier patch '[d3d8] use wined3dformat when > calling wined3d' > > > This patch adds a stray close parenthesis to wine/dlls/d3d8/directx.c line 644. Thanks, Jesse

Aug. 27, 2005

Re: Googletalk and Wine

by Andrew Neil Ramage

Below Andrew You can be the captain I will draw the chart Sailing into destiny Closer to the heart Closer to the Heart by Rush (A Farewell to Kings, 1977) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ James Hawkins wrote: > On 8/26/05, Andrew Neil Ramage <nrsc16850(a)blueyonder.co.uk> wrote: > >>Googletalk is a free chat program from Google with integrated VoIP. I >>installed the program and received a message saying Googletalk required >>Windows 2000, XP or 2003. The program started after installation and >>almost immewdiately crashed. Here is the output. >> > > > This has been fixed in CVS. > I just downloaded and installed the CVS, and tried running googletalk again. This was the result. ndrew(a)apollo:~/.wine/drive_c/Program Files/Google/Google Talk> ls googletalk.exe uninstall.exe andrew(a)apollo:~/.wine/drive_c/Program Files/Google/Google Talk> wine googletalk.exe fixme:advapi:LookupAccountSidW ((null),sid=0x403cfae8,0x406cfcf8,0x406cfcf4(64),0x406cfd78,0x406cfcf0(64),0x406cfcd4): semi-stub fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! fixme:richedit:RichEditANSIWndProc WM_SETFONT: stub fixme:richedit:RichEditANSIWndProc EM_SHOWSCROLLBAR: stub fixme:richedit:RichEditANSIWndProc EM_SHOWSCROLLBAR: stub fixme:richedit:RichEditANSIWndProc EM_SETTEXTMODE: stub fixme:richedit:RichEditANSIWndProc WM_SETFONT: stub fixme:richedit:RichEditANSIWndProc EM_SHOWSCROLLBAR: stub fixme:richedit:RichEditANSIWndProc EM_SHOWSCROLLBAR: stub fixme:richedit:RichEditANSIWndProc EM_HIDESELECTION: stub err:x11drv:X11DRV_CreateWindow invalid window height -2 fixme:keyboard:RegisterHotKey (0x10028,0,0x00000008,27): stub fixme:richedit:RichEditANSIWndProc EM_HIDESELECTION: stub fixme:richedit:RichEditANSIWndProc EM_HIDESELECTION: stub fixme:sensapi:IsNetworkAlive 0x406ce880 err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! err:syslevel:_EnterSysLevel (0x40835a20, level 2): Holding 0x4124ae40, level 3. Expect deadlock! X Error of failed request: RenderBadPicture (invalid Picture parameter) Major opcode of failed request: 152 (RENDER) Minor opcode of failed request: 7 (RenderFreePicture) Picture id in failed request: 0x740065 Serial number of failed request: 13344 Current serial number in output stream: 13347 andrew(a)apollo:~/.wine/drive_c/Program Files/Google/Google Talk>

Aug. 27, 2005

Re: old version freetype installed warning

by Dmitry Timoshkov

"Yuri Kozlov" <kozlov.y(a)gmail.com> wrote: > changelog: > gdi: old version freetype installed warning added > --- wine/dlls/gdi/freetype.c 2005-08-20 08:33:00.000000000 +0400 > +++ bwine/dlls/gdi/freetype.c 2005-08-27 16:05:47.000000000 +0400 > @@ -438,6 +438,7 @@ > /* There are too many bugs in FreeType < 2.1.9 for bitmap font support */ > if(!FT_IS_SCALABLE(ft_face) && FT_SimpleVersion < ((2 << 16) | (1 << 8) | (9 << 0))) { > pFT_Done_Face(ft_face); > + WARN("Please, update FreeType library (>=2.1.9) -- font %s will not be load\n", debugstr_a(file)); If it's supposed to be a user visible message then it should use MESSAGE instead of a WARN. -- Dmitry.

Aug. 27, 2005

Re: [COMCTL32] Set default size in ToolBar.SetBitmapSize

by Dmitry Timoshkov

"Yuri Kozlov" <kozlov.y(a)gmail.com> wrote: > changelog: > [COMCTL32] set default size for toolbar bitmap if not specified > --- wine/dlls/comctl32/toolbar.c 2005-08-16 19:25:16.000000000 +0400 > +++ bwine/dlls/comctl32/toolbar.c 2005-08-27 13:12:46.000000000 +0400 > @@ -4719,7 +4719,7 @@ > FIXME("wParam is %d. Perhaps image list index?\n", wParam); > > if ((LOWORD(lParam) <= 0) || (HIWORD(lParam)<=0)) > - return FALSE; > + lParam = MAKELONG(16, 15); Better use MAKELPARAM here since it's a 64-bit entity in Win64. -- Dmitry.

Aug. 27, 2005

Re: Wine device drivers proposal

by Evgeny F

In message Mon, 28 Mar 2005 02:30:28 -0800, Damjan Jovanovic wrote: > I propose adding a driver loading system to Wine that > works as follows: > -CreateFile() gets a device filename, like (in my > case) \\.\MiiScan0 > -Currently, Wine's behaviour for such a filename is to > try load a VXD. > -In the case of VXD loading failure, a search is > performed in (Wine's) C:\Windows\System32\Drivers (or > somewhere else?) for a matching driver. > > The driver is then loaded and used for (at least): > ReadFile() > WriteFile() > DeviceIoControl() > CloseHandle() I am doing now a dll which should load scanner microdriver and implement all the surrounding API's. Can anybody tell, what naming convention Windows uses for USB devices ("\\.\????")? > 2. The driver is a file giving a process to start and > some IPC method to use. Wine starts the process and > uses the IPC method to communicate with the driver. > This is good as far as Wine's current ReadFile() and > WriteFile() go, since they don't have to know they're > not writing to an actual file. The problem here is, > which IPC method supports both read() and write() on > the same file descriptor, preserves message > boundaries, and carries out-of-band data for > DeviceIoControl()? I was thinking TCP sockets, but > they don't preserve message boundaries. Local UNIX sockets would do fine, do we really have to preserve message bounderies? Evgeny

Aug. 27, 2005