April 2002 - Wine-Devel - list.winehq.org

Re: Wine not releasing CDROM

by Duane Clark

Tony Lambregts wrote: > > If this is the case then some regression testing is in order. Is it > just in agent or are other programs showing this behavior? I guess I should have mentioned that this was not with agent. It was with a program where I was using the CD, but then could not get the CD out of the drive until exiting the wine program.

April 22, 2002

Re: Wine not releasing CDROM

by Duane Clark

lawson_whitney(a)juno.com wrote: > On Mon, 22 Apr 2002, Oliver Sampson wrote: > > >> Howdy, >> I'm seeing a strange behavior and I thought I'd let the Devel >> community know about it: >> >> While using Agent v1.8, and while having a CD in my CD tray (although >> unmounted!), if I start agent under wine, I'm able to open and close >> my CD tray. However, if I try to use the attachment window to attach >> >>... > > > If you don't want Wine to attempt raw device access, don't give it a > "Device" = in the [Drive X] entry, I think. Your average Windows app is > inquisitive and tries to look at all drives that have defined devices. It appears to me that there is a new behavior just as Oliver describes. I also had problems this weekend with wine grabbing ahold of the CD and not releasing it, which I don't think has ever been a problem before.

April 22, 2002

Re: Wine not releasing CDROM

by Tony Lambregts

Duane Clark wrote: > lawson_whitney(a)juno.com wrote: > >> On Mon, 22 Apr 2002, Oliver Sampson wrote: >> >> >>> Howdy, >>> I'm seeing a strange behavior and I thought I'd let the Devel >>> community know about it: >>> > >> While using Agent v1.8, and while having a CD in my CD tray (although > >>> unmounted!), if I start agent under wine, I'm able to open and close >>> my CD tray. However, if I try to use the attachment window to attach >>> >>> ... >> >> >> >> If you don't want Wine to attempt raw device access, don't give it a >> "Device" = in the [Drive X] entry, I think. Your average Windows app is >> inquisitive and tries to look at all drives that have defined devices. > > > It appears to me that there is a new behavior just as Oliver > describes. I also had problems this weekend with wine grabbing ahold > of the CD and not releasing it, which I don't think has ever been a > problem before. > If this is the case then some regression testing is in order. Is it just in agent or are other programs showing this behavior? Tony Lambregts

April 22, 2002

RE: wine/objects dc.c

by Medland, Bill

This broke our app. Any ideas why? It was the change on line 348; the other three were ok. (The result is it then goes through an attempt to close down windows which aren't even fully open yet so that X11DRV_GetDC is passed a window for which the pDriverData hasn't been set yet.) Bill > -----Original Message----- > From: Alexandre Julliard [mailto:julliard(a)wine.codeweavers.com] > Sent: Sunday, April 21, 2002 3:11 PM > To: wine-cvs(a)winehq.com > Subject: wine/objects dc.c > > > ChangeSet ID: 1019427035919545120866136 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 02/04/21 17:10:35 > > Modified files: > objects : dc.c > > Log message: > Fixed handling of visible region in Save/RestoreDC. > > Patch: http://cvs.winehq.com/patch.py?id=1019427035919545120866136 > > Revision Changes Path > 1.73 +4 -4 wine/objects/dc.c > >

April 22, 2002

Re: dlls/kernel/comm.c build failure

by Marcus Meissner

On Mon, Apr 22, 2002 at 08:46:03AM +0200, Gerald Pfeifer wrote: > The following patch > > revision 1.56 > date: 2002/04/21 22:06:09; author: julliard; state: Exp; lines: +24 -0 > <wine(a)gc2.kloepfer.org> > Faster serial speed cases for non Linux systems. > > broke dlls/kernel/comm.c on FreeBSD 4.5 (and probably all non-Linux > systems) > > /usr/bin/gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_REENTRANT -I/usr/X11R6/include -o comm.o comm.c > comm.c: In function `SetCommState': > comm.c:1063: `CBR_230400' undeclared (first use in this function) > comm.c:1063: (Each undeclared identifier is reported only once > comm.c:1063: for each function it appears in.) > gmake[2]: *** [comm.o] Error 1 > gmake[2]: Leaving directory `/.amd_mnt/vexpert/files8/test/wine/dlls/kernel' > gmake[1]: *** [kernel/kernel32.dll.so] Error 2 > > apparently because CBR_230400 is not #defined in include/winbase.h. > > The patch below fixes this, but I suppose it's not what will go in > finally... I would suggest just dropping those 2 cases, MSDN does not list them either. - case CBR_230400: - case CBR_460800: Ciao, Marcus

April 22, 2002

RE: su to root failure in wineinstall

by Medland, Bill

> -----Original Message----- > From: Enrico Horn [mailto:farmboy1(a)subdimension.com] > Sent: Monday, April 22, 2002 2:58 AM > To: wine-devel(a)winehq.com > Subject: Re: su to root failure in wineinstall > > > Hi, > On Saturday 20 April 2002 21:23, Thomas Hardman wrote: > > Wine build complete. > > > > Performing 'make install' as root to install binaries, > enter root password > > Password: > > /bin/bash: - : unrecognized option > > > > Either you entered an incorrect password or we failed to run > > 'make install' correctly. > > If you didn't enter an incorrect password then please report this > > error to wine-devel(a)winehq.com. > > > > Installation failed, aborting. > > earthops:/usr/src/wine-20020411$ > > That is an error(typo?) in wineinstall > Find this line in wineinstall: > if ! su root -c"$sucommand" > > and put a space between -c and "$sucommand" > > That should do it. And if that doesn't work then find the line where it adds ldconfig to sucommand and explicitly specify /sbin/ldconfig (or wherever yours is) Bill > > Enrico > farmboy1(a)subdimension.com >

April 22, 2002

RE: bug?

by Medland, Bill

> -----Original Message----- > From: Rikard Björklind [mailto:olof(a)linux.nu] > Sent: Saturday, April 20, 2002 5:38 AM > To: wine-devel(a)winehq.com > Subject: bug? > > > Hi, I tried to use ./tools/wineinstall: > > Performing 'make install' as root to install binaries, enter > root password > Password: [here I wrote the password] > /bin/bash: - : unrecognized option > > What's wrong? > > Probably failed to run the ldconfig. Check the /etc/ld.so.conf to see that the location of the wine lib directory is included (probably /usr/local/lib) and su root and run /sbin/ldconfig. Bill

April 22, 2002

Re: Wine not releasing CDROM

by lawson_whitney＠juno.com

On Mon, 22 Apr 2002, Oliver Sampson wrote: > Howdy, > I'm seeing a strange behavior and I thought I'd let the Devel > community know about it: > > While using Agent v1.8, and while having a CD in my CD tray (although > unmounted!), if I start agent under wine, I'm able to open and close > my CD tray. However, if I try to use the attachment window to attach > something, the CD-ROM drive spins up, and I'm unable to open it. Even > if I attach nothing, the CD-ROM drive is claimed by wine so that I > can't eject the Drive. Once I exit agent, the drive is released so > that I can open the drive. Note that the CD-ROM was never mounted. > Even a check during the blocked period shows no mounted device, even > though the "eject' command says "device busy." > > Interestingly, when I just tried this again for this email, I noticed > the following output messages (It seems that there are some floppy > drive assumptions, also.) If you don't want Wine to attempt raw device access, don't give it a "Device" = in the [Drive X] entry, I think. Your average Windows app is inquisitive and tries to look at all drives that have defined devices. > > Oliver > > ---output---- > 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' ;; MS-DOS drives configuration ;; ;; Each section has the following format: ;; [Drive X] .... ;; "Device"="/dev/xx" (only if you want to allow raw device access) Lawson If you don't want my peaches, then don't shake my tree.

April 22, 2002

Wine not releasing CDROM

by Oliver Sampson

Howdy, I'm seeing a strange behavior and I thought I'd let the Devel community know about it: While using Agent v1.8, and while having a CD in my CD tray (although unmounted!), if I start agent under wine, I'm able to open and close my CD tray. However, if I try to use the attachment window to attach something, the CD-ROM drive spins up, and I'm unable to open it. Even if I attach nothing, the CD-ROM drive is claimed by wine so that I can't eject the Drive. Once I exit agent, the drive is released so that I can open the drive. Note that the CD-ROM was never mounted. Even a check during the blocked period shows no mounted device, even though the "eject' command says "device busy." Interestingly, when I just tried this again for this email, I noticed the following output messages (It seems that there are some floppy drive assumptions, also.) Oliver ---output---- 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 The filesystem is not FAT !! (device=/dev/cdrom) err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on /dev/cdrom (D:). err:dosfs:DRIVE_ReadSuperblock The filesystem is not FAT !! (device=/dev/cdrom) Invalid or unreadable superblock on /dev/cdrom (D:). Maybe not FAT? fixme:listview:LISTVIEW_UnsupportedStyles LVS_EDITLABELS fixme:listview:LISTVIEW_UnsupportedStyles LVS_SHAREIMAGELISTS ==================================================== Oliver Sampson olsam(a)quickaudio.com http://www.oliversampson.com

April 22, 2002

Re: [PATCH] Big winsock2 / overlapped patch

by Martin Wilck

On Fri, 19 Apr 2002, Sylvain Petreolle wrote: > > I know the patch is much too big but I have no time > > now to split it into > > pieces before next week. > If the patch is too big, then gzip it and send it > as an attachment :) I didn't mean to say it's too big for an email :) What I meant was it is big for humans to read & understand, and too big for Alexandre to apply as a single chunk. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

April 22, 2002