wine users - Apr 2012 - Re: Problems with ImgBurn, err:aspi:ASPI_GetNumControllers

Well, I finally found something of a solution.  It's not ideal, but that may
be down to my distro or my unfamiliarity with "udisks".  I have to
unmount the udisks auto-mounted optical device and then manually mount that
drive to /media/cdrom0 (or wherever).  At which point I can start ImgBurn and
change the Interface (Tools->Settings->I/O->Page1) to SPTI.  The drive
can then be detected, so long as it is mapped in winecfg (Drives->Drive
mappings).

Thing is, this isn't 100% reliable.  In some cases I end up having to use
"eject" on the command line to open the drive tray and/or unmount the
device.  I had one situation where during the same Wine session, ImgBurn
'lost' the CD-ROM.  Unfortunately an errant mouse click minimized the
"ImgBurn Log" and I was unable to copy the log messages (once the
ImgBurn Log is minimized, the only way to get it back to hack Wine's
registry and restart ImgBurn).  I also couldn't eject or unmount the optical
device no matter what I did...  Well, other than a reboot.

I'm going to poke around and see if I can't get udisks and Wine
cooperating in such a way that udisks mounted optical devices just work under
Wine.  At which point, I'll call this thread solved.  If anyone else has
suggestions, I'd be happy to hear them.

Hadn't realized ImgBrun keeps a running log until I went to its Forums... 
Odd thing is, where I thought the error would appear is not there.  Though I
think it may have been this.


Code:
W 10:03:55 I/O Interface 'SPTI - Device Enumeration Method' has been
changed!
I 10:03:55 Searching for SCSI / ATAPI devices...
E 10:03:57 Device->Initialise() Failed!
E 10:03:57 Device: [0:0:0] (D:)
E 10:03:57 This drive will not be visible in the program.



Which to me would indicate that the device may have been in use by a
'phantom' process.  Given that I couldn't eject or umount either.