Thanks for your three (very different) replies.
From Scott's comments I take it that the mount/unmount
of file systems is such a basic part of *nix that it might take some lateral thinking to circumvent it.
As for Sylvain's suggestion, I set up automounting this evening, but unfortunately this did not solve my problem: the same processes attached to /dev/cdrom were still open (5 belonging to wine and 1 to wineserver), and <eject> gave a "device busy" response.
Tony Lambregts:
What version of Wine are you useing. Disk changing should not be a problem under the latest releases of Wine.
I'm not exactly sure. As you guessed I'm using Transgamings current winex installation (subscription version).
WineX is a different flavor of Wine, So it may still have this problem. In other words if you have this problem when useing Wine then you should report it to http://bugs.winehw.org . Since you have this problem under WineX I guess you should be contacting Transgaming.
I guess, except that's where I first posted this message and got no satisfactory response. Perhaps I ought to approach them more directly as you suggest.
I regularly use Riven which is a five disk set. In order to play the game I have to change disks when I move from one island to the next. I do recall that about a year ago that there was a problem in that Wine would not close off files so that umount would not work.
There is one possible significant difference between installation of a program and changing disks in the course of a game as you describe: in the first case wine is running setup.exe which is on the CD, and hence wine has processes open which access the CD drive. In your case wine is running the game program which has been transferred to the hard disk. It is now Riven which accesses the CD drive and (conceivably) when the time comes to change the CD, it will first close down all processes which use the drive. Maybe.
Thanks for your comments. I would welcome further discussion if anybody cares to join in.
Roger Young r.young@irl.cri.nz
r.young@irl.cri.nz wrote:
Tony Lambregts:
What version of Wine are you useing. Disk changing should not be a problem under the latest releases of Wine.
I'm not exactly sure. As you guessed I'm using Transgamings current winex installation (subscription version).
So this should be the latest. What does "wine -v" give you?
WineX is a different flavor of Wine, So it may still have this problem. In other words if you have this problem when useing Wine then you should report it to http://bugs.winehw.org . Since you have this problem under WineX I guess you should be contacting Transgaming.
I guess, except that's where I first posted this message and got no satisfactory response. Perhaps I ought to approach them more directly as you suggest.
Actually I would suggest that you try Wine. ie install wine and see if you have the same problem with the latest tarball. If you do not have this problem with it, then the problem is with the Transgaming version. If you still have the same problem with Wine then start a bug report in bugzilla. Like I said I have not seen this problem for about a year.
I regularly use Riven which is a five disk set. In order to play the game I have to change disks when I move from one island to the next. I do recall that about a year ago that there was a problem in that Wine would not close off files so that umount would not work.
There is one possible significant difference between installation of a program and changing disks in the course of a game as you describe: in the first case wine is running setup.exe which is on the CD, and hence wine has processes open which access the CD drive. In your case wine is running the game program which has been transferred to the hard disk. It is now Riven which accesses the CD drive and (conceivably) when the time comes to change the CD, it will first close down all processes which use the drive. Maybe.
I only have the one game to go by so I can't be an authority on this. I can only say that it used to be a problem for me. It would not let me go from one island to the next because it would not release the CD. Then again about a year ago it would not install either <g>.
Thanks for your comments. I would welcome further discussion if anybody cares to join in.
I recall there was a section on this in the Trouble Shooting Guide. Ah yes, Google gives me this.
http://www.winehq.org/fom-meta/cache/223.html
If you have not already done so please have a look .
Since this list is primarily for Wine I would suggest (like I said before) to install the latest Wine (not WineX) and see if you still have this problem. If it is still a problem then start a bug report.
--- r.young@irl.cri.nz a écrit : > Thanks for your three (very different) replies.
From Scott's comments I take it that the mount/unmount of file systems is such a basic part of *nix that it might take some lateral thinking to circumvent it.
As for Sylvain's suggestion, I set up automounting this evening, but unfortunately this did not solve my problem: the same processes attached to /dev/cdrom were still open (5 belonging to wine and 1 to wineserver), and <eject> gave a "device busy" response.
you dont have to use "eject" if you have set the automount correctly. make sure you have edited your /etc/fstab to mount yhour cdrom drive with the automounter. then you can eject the cd without "eject"' and "umount". simply press the eject button of your drive.
===== Sylvain Petreolle spetreolle@users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259
"Don't think you are. Know you are." Morpheus, in "Matrix".
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com