- Wine-devel - list.winehq.org

Bug #931
by Dusan Vujosevic 13 Aug '02

13 Aug '02

I seems that the problem I noted in bug #931 goes away when "PerfectGraphics" is set to false (????). I tracked the problem down to implementation of PATINVERT in BITBLT_InternalStretchBlt() (in graphics/x11drv/bitblt.c). It check whether 'perfect_graphics' is on and if it is it actually doesn't do the drawing: case PATINVERT: /* 0x5a */ if (perfect_graphics()) break; Maybe I'm missing soemthing here but I think that test should be: case PATINVERT: /* 0x5a */ if (!perfect_graphics()) break; That would give a more logical behaviour where there would not be any drawing errors when "PerfectGraphics" is set to True. (There are other spots where this is used in similar fashion) Another question is why have the "PerfectGraphics" option at all when it produces drawing artifacts? D.

2 1

Incomplete support in Win32
by Shachar Shemesh 13 Aug '02

13 Aug '02

Hi all, As you may know (I make a lot more noise than actual work), I am trying to implement BiDi support for WINE. The most promising place to start seemed to be GetCharacterPlacement, that does everything even remotely BiDi related. The most immediate thing to do was to call GetCharacterPlacement from ExtTextOut in order to do the BiDi rearrenging. In typical MS fashion, however, it seems that this will not work. Despite the fact that you are supposed to be able to call GetCharacterPlacement once, and then call ExtTextOut with the result as many times as necessary (speeding up the process, and suggesting that GetCharacterPlacement can do anything ExtTextOut can do), it seems there is one thing that ExtTextOut is expected to know how to do, and GetCharacterPlacement does not know. For those who are really interested, this is specfying the base directionality of the paragraph. I am pretty sure the way Windows implements this is by having a common parent function used for reordering by both ExtTextOut and GetCharacterPlacement. I think such an arrangment is awfully crude. I was considering an alternative solution, and would like your opinion. What I thought of doing was adding a bit to the flags GetCharacterPlacement gets, which says "right to left paragraph, if you'll be so kind". My question is - how acceptable is such a behaviour. Is that a huge no-no, or is that a harmless little tweak? It goes without saying that I will document the fact that this is a WINE only flag, and that there are unused bits in the GetCharacterPlacement current flags set. Another alternative I was considering was to add a directional push at the start of the string in order to achieve this without changing the algorithm. The problem is that I am not sure what affect this will have on the reordering, not to mention the fact that I will then need to copy and widen the string inside ExtTextOut, which is an inconvinence to say the least. Your opinios, please. Shachar

2 1

WineHQ.com server crash
by Jeremy Newman 13 Aug '02

13 Aug '02

On 10:00:12 CST the wine.codeweavers.com a.k.a www.winehq.com server suffered catastrophic hardware failure. The power supply suddenly decided of its own free will that the motherboard and all of the attached components needed 3x the recommended voltage (or something). wine.codeweavers.com (ver 3.0) on-line and operational. Sorry for the inconvenience of downtime. I now return you to your regularly scheduled mailing list. -- __ _WebGeek/NetAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | .` / -_) | | / ' \/ _` | ' \ -= mailto:jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

1 0

Re: Agent crashes on accessing Disk
by Rein Klazes 12 Aug '02

12 Aug '02

On Sun, 11 Aug 2002 18:18:37 +0200, you wrote: > On Sun, 11 Aug 2002 17:26:17 +0200, Rein Klazes <rklazes(a)xs4all.nl> > wrote: > > >On Sun, 11 Aug 2002 14:21:57 +0200, you wrote: > > > >> Howdy, > >> I've just found a problem with Agent when trying to save attachments > >> from email, that I thought I'd share with the devel community. (It's > >> happening in both v1.9 and v1.92.) This is also happening with my > >> just updated today CVS version. > >> > >> > >> When I tried to save an attachment, the following messages appear: > > > >[snip] > > > >Oliver, I always get essentially the same messages as those, but no > >crash. So it is quite possible that they are unrelated to the crash. > > > >Look at the backtrace in the debugger, the last messages before the > >crash with relay debugging enabled, and (because this is Agent) check > >that if you have native windows dll's lying around that Agent doesn't > >use them. > > This is a linux only install, so there are no Windows.dlls on my > system. > > I did a --debug message -relay, and here's the output from the console > window. I've included it all even though only the last couple of > lines look pertinent. For a backtrace type 'bt' in the console at the "Wine-dbg>" prompt, no additional debug messages enabled; Relay debugging: run with "--debugmsg +relay" and capture the output in a file. With a texteditor look for the line where the first indication of the crash is (search for something like "starting debugger" or "unhandled exception"). In the lines above this you can see what the program was doing at that moment. To post logs: try to preserve the line-breaks. In Agent I usually use "Paste as Quote (Custom)", Agent doesn't insert additional line-breaks in that case. Attaching as "plain text" is another possibility. Rein. -- Rein Klazes rklazes(a)xs4all.nl

2 2

RE: Very basic question concerning compiling WINE
by Medland, Bill 12 Aug '02

12 Aug '02

> -----Original Message----- > From: Steven Rubenstein [mailto:SJR(a)electricspectric.com] > Sent: Friday, August 09, 2002 6:11 PM > To: wine-devel(a)winehq.com > Subject: Very basic question concerning compiling WINE > > > *** I hope this isn't appropriate, in that I posted this same > question > to wine-user(a)winehq.com. I'm still not sure who reads what. *** > > I am an intermediate Linux user. I dual boot into Redhat 7.3 > and Windows > ME. It would be nice to be able to run the stuff in Windows > from Linux > (for 2 reasons: to avoid booting and rebooting, and trying to > get away > from Windows altogether someday), so I am now learning WINE. > > I see a bunch of postings on this list about compiling. > Question: Would > I expect to compile, as opposed to just running the WINE > configuration > that came with Redhat 7.3? (Probably a pretty broad question, but if > anyone has a word to say, I'm all ears.) > > SJR > > > I echo Tony's views. However the following might be useful to you. It is possible to get approximately monthly updates to the rpms on RedHat; the LinuxEasy rpm copies available via www.winehq.com/downloads (if they are available) are in the correct version. I would certainly say that you will need to upgrade or replace the one that comes with RedHat 7.3. It's great that RedHat provide it but that version is woefully out-of-date now. However I would seriously advocate building from scratch. (Before doing so, remember to uninstall the wine that RedHat put there). I have been building Wine on RedHat for a year and a half now; on RedHat 7.3 for many months. I find it quite easy. Bill

1 0

wine + cvs + proxy = ?
by Fabian Cenedese 12 Aug '02

12 Aug '02

Hi all I'd like to stay up-to-date by using cvs on wine. Unfortunately cvs isn't able to go through a proxy if it isn't invisible, I can't enter the proxy info anywhere in cvs (confirmed on cvs mailing list). So I wondered if there is a better solution than to download the wine-snapshots and reinstall the sources every time. Does anyone have similar problems and maybe a solution? Thanks Fabi

2 1

WINS support in Wine
by Claudiu Costin 11 Aug '02

11 Aug '02

Dear friends, I want to bypass WINS client routines and use LMHOSTS as a mean to "resolve" Windows machines names. Sincerly, on Win2k I haven't success, even I setup the c:\winnt\drivers\etc\lmhosts file. But, I need this to work to surpase the Outlook dialog in Wine which say me that there are networking problems and it cannot resolve/find my "exchange_name" server. My desire is to make Outlook Exchange support work on Wine. You, know, if I succeed this, then I'll not be forced to reboot on Windows when I'm at my job. P.S. Thanks in advance for help have a nice day, -- Claudiu Costin, claudiuc(a)kde.org Linux-KDE Romania http://www.ro.kde.org

1 0

Agent crashes on accessing Disk
by Oliver Sampson 11 Aug '02

11 Aug '02

Howdy, I've just found a problem with Agent when trying to save attachments from email, that I thought I'd share with the devel community. (It's happening in both v1.9 and v1.92.) This is also happening with my just updated today CVS version. When I tried to save an attachment, the following messages appear: ------------------ [olsam(a)friday agent]$ wine ~/bin/Agent/1.9/agent.exe err:mmsys:MMDRV_InitHardcoded You didn't setup properly the config file for the Wine multimedia modules. Will use the hard-coded setup, but this will disappear soon. Please add a WinMM section to your Wine config file. fixme:file:SetFileAttributesA (D:\data\agent\):2000 attribute(s) not implemented. fixme:ddeml:DdeConnectList (1,49159,49160,0,(nil)): stub fixme:ddeml:DdeQueryNextServer (1,0): stub fixme:ddeml:DdeDisconnectList (1): stub fixme:ddeml:DdeConnectList (1,49159,49160,0,(nil)): stub fixme:ddeml:DdeQueryNextServer (1,0): stub fixme:ddeml:DdeDisconnectList (1): stub fixme:ddeml:DdeConnectList (1,49159,49160,0,(nil)): stub fixme:ddeml:DdeQueryNextServer (1,0): stub fixme:ddeml:DdeDisconnectList (1): stub fixme:ras:RasEnumConnectionsA (0x411b3990,0x40485cc8,0x41119308),stub! fixme:ras:RasEnumConnectionsA RAS support is not implemented ! Configure program to use LAN connection/winsock instead ! fixme:ras:RasEnumConnectionsA (0x411b0020,0x4048653c,0x40486584),stub! fixme:ras:RasEnumConnectionsA RAS support is not implemented ! Configure program to use LAN connection/winsock instead ! fixme:commdlg:GetFileName95 Flags 0x00000002 not yet implemented err:shell:SHGetSpecialFolderPathA Failed to create directory 'C:\WINDOWS\Desktop'. err:shell:SHGetSpecialFolderPathA Failed to create directory 'C:\WINDOWS\Desktop'. err:shell:SHGetSpecialFolderPathA Failed to create directory 'C:\WINDOWS\Desktop'. err:shell:SHGetSpecialFolderPathA Failed to create directory 'C:\WINDOWS\Desktop'. wine: Unhandled exception, starting debugger... fixme:console:SetConsoleCtrlHandler (0x4038bc04,1) - no error checking or testing yet err:wineconsole:WCUSER_SetFont wrong font err:wineconsole:WCUSER_SetFont wrong font Terminated ------------ I wasn't sure if it was the "Desktop" message was the problem, so I created a 'Desktop' folder in my /usr/share/wine-c/winddows directory. (This was quite a surprise, since saving attachments was never a problem before.) Why do I need a Desktop folder anyhow? And if it's really necessary, shouldn't the install script check for it and create it for me? I as a user don't want to be concerned with those things. After creating the Desktop directory, and then trying to save the attachment again, the console displayed these messages: ---------------------- [olsam(a)friday agent]$ err:mmsys:MMDRV_InitHardcoded You didn't setup properly the config file for the Wine multimedia modules. Will use the hard-coded setup, but this will disappear soon. Please add a WinMM section to your Wine config file. fixme:file:SetFileAttributesA (D:\data\agent\):2000 attribute(s) not implemented. fixme:ras:RasEnumConnectionsA (0x411e1b70,0x40485cb8,0x411492b0),stub! fixme:ras:RasEnumConnectionsA RAS support is not implemented ! Configure program to use LAN connection/winsock instead ! fixme:ras:RasEnumConnectionsA (0x411e1448,0x4048653c,0x40486584),stub! fixme:ras:RasEnumConnectionsA RAS support is not implemented ! Configure program to use LAN connection/winsock instead ! fixme:commdlg:GetFileName95 Flags 0x00000002 not yet implemented err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/fd0' for drive A: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on /dev/fd0 (A:). err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/fd0' for drive A: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' Invalid or unreadable superblock on /dev/fd0 (A:). Maybe not FAT? err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/cdrom' for drive D: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on /dev/cdrom (D:). err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/cdrom' for drive D: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' Invalid or unreadable superblock on /dev/cdrom (D:). Maybe not FAT? err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/cdrom' for drive D: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on /dev/cdrom (D:). err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/cdrom' for drive D: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' Invalid or unreadable superblock on /dev/cdrom (D:). Maybe not FAT? err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/cdrom' for drive D: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on /dev/cdrom (D:). err:dosfs:DRIVE_ReadSuperblock Couldn't open device '/dev/cdrom' for drive D: ! (no permission) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! Perhaps you have not properly edited or created your Wine configuration file. This is (supposed to be) '/home/olsam/.wine/config' Invalid or unreadable superblock on /dev/cdrom (D:). Maybe not FAT? wine: Unhandled exception, starting debugger... fixme:console:SetConsoleCtrlHandler (0x4038bc04,1) - no error checking or testing yet err:wineconsole:WCUSER_SetFont wrong font err:wineconsole:WCUSER_SetFont wrong font [1]+ Terminated wine ~/bin/Agent/1.92/agent.exe ----------------- So, why is it trying to access my floppy and CD-ROM in the first place. This is similar to a problem that I reported some time ago, but that was just annoying; this is preventing me from working. (It's also a bit of a PITA, because it's the program I use to write emails like this. :-) Thanks, ==================================================== Oliver Sampson olsam(a)quickaudio.com http://www.oliversampson.com

2 2

thread handling fix for BSD and Solaris
by Pierre Beyssac 10 Aug '02

10 Aug '02

Hi, Here's a patch to fix a EFAULT error returned by ptrace calls in server/context_i386.c, causing tons of "file_set_error: Bad address" errors. Two arguments to ptrace were reversed. This is tested on FreeBSD and checked with NetBSD and Solaris ptrace(2) manual pages. --- wine-20020804.orig/server/context_i386.c Sun Mar 10 01:18:36 2002 +++ wine-20020804/server/context_i386.c Sat Aug 10 19:07:31 2002 @@ -224,7 +224,7 @@ if (flags & CONTEXT_FULL) { struct regs regs; - if (ptrace( PTRACE_GETREGS, pid, 0, (int) &regs ) == -1) goto error; + if (ptrace( PTRACE_GETREGS, pid, (int) &regs, 0 ) == -1) goto error; if (flags & CONTEXT_INTEGER) { context->Eax = regs.r_eax; @@ -259,7 +259,7 @@ { /* we can use context->FloatSave directly as it is using the */ /* correct structure (the same as fsave/frstor) */ - if (ptrace( PTRACE_GETFPREGS, pid, 0, (int) &context->FloatSave ) == -1) goto error; + if (ptrace( PTRACE_GETFPREGS, pid, (int) &context->FloatSave, 0 ) == -1) goto error; context->FloatSave.Cr0NpxState = 0; /* FIXME */ } return; @@ -332,7 +332,7 @@ if (flags & CONTEXT_FULL) { struct reg regs; - if (ptrace( PTRACE_GETREGS, pid, 0, (int) &regs ) == -1) goto error; + if (ptrace( PTRACE_GETREGS, pid, (caddr_t) &regs, 0 ) == -1) goto error; if (flags & CONTEXT_INTEGER) { context->Eax = regs.r_eax; @@ -367,7 +367,7 @@ { /* we can use context->FloatSave directly as it is using the */ /* correct structure (the same as fsave/frstor) */ - if (ptrace( PTRACE_GETFPREGS, pid, 0, (int) &context->FloatSave ) == -1) goto error; + if (ptrace( PTRACE_GETFPREGS, pid, (caddr_t) &context->FloatSave, 0 ) == -1) goto error; context->FloatSave.Cr0NpxState = 0; /* FIXME */ } return; @@ -423,7 +423,7 @@ { /* we can use context->FloatSave directly as it is using the */ /* correct structure (the same as fsave/frstor) */ - if (ptrace( PTRACE_SETFPREGS, pid, 0, (int) &context->FloatSave ) == -1) goto error; + if (ptrace( PTRACE_SETFPREGS, pid, (caddr_t) &context->FloatSave, 0 ) == -1) goto error; } return; error: -- Pierre Beyssac pb(a)fasterix.frmug.org pb(a)fasterix.freenix.org Free domains: http://www.eu.org/ or mail dns-manager(a)EU.org

2 2

sys/asoundlib.h:1: This header is deprecated
by Gerald Pfeifer 10 Aug '02

10 Aug '02

On a SuSE Linux 8.0 box[1] I'm getting the following #warning a few times while building the current CVS version of Wine: In file included from alsa.h:23, from audio.c:46: /usr/include/sys/asoundlib.h:1: warning: #warning This header is deprecated, use <alsa/asoundlib.h> instead. Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

2 2