https://bugs.winehq.org/show_bug.cgi?id=56087
--- Comment #25 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
There is also a policy that bug triagers and developers should not have to experiment with the application themselves, but may ask the users to do it. I shouldn't be forced to download and try the application myself when I'm wondering if something could make a difference.
The original issue stated in the bug title has been confirmed. It may be an application bug, though, so this is worth investigating and a valid reason to try to reproduce the issue.
It has been reported that the application itself works when the image is mounted through cdemu. The reporter uses fuseiso and the application can't find its disk, although it seems, to me, that it has been properly mounted. If the application behavior depends on the mounting tool, there is a valid reason to experiment with different mounting tools. There may be something wrong with fuseiso or the way Wine interacts with fuseiso mounted images. This needs investigation.
The bug reporter has found that the disk image is an HFS/ISO9660 hybrid. There is indeed a bug in udisksctl regarding HFS/ISO9660 hybrid images: https://github.com/storaged-project/udisks/issues/1155. So, if I wanted to try to check the application on my current system, this would be a stumbling block, and that tool can't be used to further experiment the issues. He also confirmed that the ISO disk label is "Thrillride" according to blkid. The bug reporter is contributing to the examination of the issue with initiative and valuable feedback.
This seems more than just 'user needs to learn how to use linux and wine'.
So I finally got to download & test the application.
I created a fresh 32-bit wineprefix with wine 9.0-rc3.
Since udisksctl can't be used, I mounted the disk image with: $ sudo mount -t iso9660 Thrillride.iso ~/var/GameLauncher/Images/Thrillride This made a /dev/loop0 device and the Windows content were present in the target directory.
I ran winecfg in my home directory (so not from the disk directory), to remove file associations, and Wine had already setup a drive of type CD-ROM for the device /dev/loop0 with the path to the mount-point.
Then I 'cd' into ~/var/GameLauncher/Images/Thrillride and ran "wine AutoRun.exe". The autorun appeared with sound and I clicked INSTALL. The Setup program appeared and I could install the application (optimal install). The Indeo software setup failed with error -119 (this is bug 50218). I rejected all the other windows: registration, update, readme & reboot.
Then I 'cd' to the drive_c/Sierra/Thrillride in the wineprefix (~/var/Wine.sh/App/3-D Ultra Pinball Thrillride.wine) and ran 'wine Pinball.exe' The screen size changed to 800x600 and a black window appeared with the attached message, repeating itself when I clicked 'ok'. When I click 'ok' the following line is printed several times in the terminal, at a 1 second interval:
wine: Read access denied for device L"\??\I:\", FS volume label and serial are not available.
So: • I didn't get the original issue: The install button of the AutoRun launched the installer. • I could reproduce the 'application can't find the disk' issue.
$ udevadm info -q env -n /dev/loop0 | grep ID_FS_LABEL ID_FS_LABEL=Thrillride ID_FS_LABEL_ENC=Thrillride
Regards.