Re: New eject command issue

2005-11-12 Thread Christian Costa
Brian Vincent wrote: On 11/7/05, Christian Costa [EMAIL PROTECTED] wrote: The error (21) suggest the drive is not ready or is finishing something. Could you add a delay before the ejection IOCTL ? No difference with this: if (!DeviceIoControl( handle,

Re: New eject command issue

2005-11-07 Thread Alexandre Julliard
Brian Vincent [EMAIL PROTECTED] writes: Maybe I'm just unclear on the usage. It appears the first time it unmounts the drive and then the second time it actually ejects it. Is that intended behavior? No, it should be able to eject the first time. -- Alexandre Julliard [EMAIL PROTECTED]

Re: New eject command issue

2005-11-07 Thread Christian Costa
Brian Vincent wrote: On 11/5/05, Brian Vincent [EMAIL PROTECTED] wrote: Then wine eject doesn't work the first time I try it. The second time I run it, it works fine. Maybe I'm just unclear on the usage. It appears the first time it unmounts the drive and then the second time it

Re: New eject command issue

2005-11-07 Thread wino
On Mon, 07 Nov 2005 23:39:20 +0100, Christian Costa [EMAIL PROTECTED] wrote: Brian Vincent wrote: On 11/5/05, Brian Vincent [EMAIL PROTECTED] wrote: Then wine eject doesn't work the first time I try it. The second time I run it, it works fine. Maybe I'm just unclear on the usage. It

Re: New eject command issue

2005-11-05 Thread Brian Vincent
On 11/1/05, Christian Costa [EMAIL PROTECTED] wrote: I tried to use the new eject command and this does not seem to work. Odd thing here as well. Fedora Core 4. This is wine CVS as of a few days ago, I don't think anything has changed in this area. If dosdevices contains a normal: lrwxrwxrwx

Re: New eject command issue

2005-11-05 Thread Brian Vincent
On 11/5/05, Brian Vincent [EMAIL PROTECTED] wrote: Then wine eject doesn't work the first time I try it. The second time I run it, it works fine. Maybe I'm just unclear on the usage. It appears the first time it unmounts the drive and then the second time it actually ejects it. Is that

Re: New eject command issue

2005-11-03 Thread Christian Costa
FSCTL_DISMOUNT_VOLUME : in DIR_unmount_device (in ntdll/directory.c): - unmount_device server call (in fd.c) is called but in unmount_device, the function tries to retreive a device object given the device return by fstat but no device object has been previously created so

Re: New eject command issue

2005-11-03 Thread Alexandre Julliard
Christian Costa [EMAIL PROTECTED] writes: I will hack FILE_GetDeviceInfo just to make it recognize my cdrom as removable and try to see if it helps. However, I don't understand well why forcing the drive as cdrom (instead of relying on autodetection) is not taken into account. This could

Re: New eject command issue

2005-11-03 Thread Christian Costa
Alexandre Julliard wrote: Christian Costa [EMAIL PROTECTED] writes: I will hack FILE_GetDeviceInfo just to make it recognize my cdrom as removable and try to see if it helps. However, I don't understand well why forcing the drive as cdrom (instead of relying on autodetection) is not

Re: New eject command issue

2005-11-02 Thread Christian Costa
Alexandre Julliard wrote: Christian Costa [EMAIL PROTECTED] writes: If I set H: to autodetect, GetDriveType returns DRIVE_FIXED (3). Then you need to figure out why FILE_GetDeviceInfo doesn't recognize it as a CDROM. Something wrong is happening here, fstatfs return a good fs

Re: New eject command issue

2005-11-02 Thread Alexandre Julliard
Christian Costa [EMAIL PROTECTED] writes: Something wrong is happening here, fstatfs return a good fs magic ID for reiserfs and vfat partitions. However, for the cdrom it returns 0x9fa1 which corresponds to OPENPROM fs !?! (and this for my cdreader and my cd recorder) Something is wrong

New eject command issue

2005-11-01 Thread Christian Costa
Hi, I tried to use the new eject command and this does not seem to work. For that, I run a exe on the cdrom and try to eject the cdrom with : WINEDEBUG=+eject wine eject and I get : trace:eject:eject_cd ejecting h: warn:eject:eject_cd IOCTL_STORAGE_MEDIA_REMOVAL failed with err 170

Re: New eject command issue

2005-11-01 Thread Alexandre Julliard
Christian Costa [EMAIL PROTECTED] writes: and I get : trace:eject:eject_cd ejecting h: warn:eject:eject_cd IOCTL_STORAGE_MEDIA_REMOVAL failed with err 170 warn:eject:eject_cd IOCTL_STORAGE_EJECT_MEDIA failed with err 170 and nothing happen and files are still open on the cdrom as shown

Re: New eject command issue

2005-11-01 Thread Christian Costa
Sounds like your cdrom drive has not been detected as a removable device. Is it a real CD or a disk image? A real CD. in dosdevices : lrwxrwxrwx1 titantitan 10 oct 11 22:18 h: - /mnt/cdrom/ lrwxrwxrwx1 titantitan 9 mai 19 2004 h:: - /dev/scd0 And in

Re: New eject command issue

2005-11-01 Thread Alexandre Julliard
Christian Costa [EMAIL PROTECTED] writes: A real CD. in dosdevices : lrwxrwxrwx1 titantitan 10 oct 11 22:18 h: - /mnt/cdrom/ lrwxrwxrwx1 titantitan 9 mai 19 2004 h:: - /dev/scd0 And in winecfg the drive type is set to CDROM. You should set it to

Re: New eject command issue

2005-11-01 Thread Christian Costa
Alexandre Julliard wrote: Christian Costa [EMAIL PROTECTED] writes: A real CD. in dosdevices : lrwxrwxrwx1 titantitan 10 oct 11 22:18 h: - /mnt/cdrom/ lrwxrwxrwx1 titantitan 9 mai 19 2004 h:: - /dev/scd0 And in winecfg the drive type is set to CDROM.

Re: New eject command issue

2005-11-01 Thread Alexandre Julliard
Christian Costa [EMAIL PROTECTED] writes: If I set H: to autodetect, GetDriveType returns DRIVE_FIXED (3). Then you need to figure out why FILE_GetDeviceInfo doesn't recognize it as a CDROM. -- Alexandre Julliard [EMAIL PROTECTED]