James McKenzie <jjmckenzie51@xxxxxxxxxxxxx> wrote: > Setup programs MUST be run from the directory from which the > installation is to take place. Unless, IIRC, it is a multi-CD installation. The shell from which wine was started is still camped out waiting for wine to exit, and the shell's current directory is on the CD. This keeps the first CD from being unmounted and replaced with the second one, even if "wine eject" is used, because the CD can't be unmounted while any process has its current directory there and "wine eject" can't change the shell's current directory. I think the FAQ recommends [code] wine "/media/cdrom0/Komplete 6 Setup PC.exe" [/code] if it is the first disk of a multi-CD installation. If there's some multi-CD set that doesn't work when run that way, you could try something like this (untested), being sure to include the parentheses: [code] ( cd /media/cdrom0 && exec wine "Komplete 6 Setup PC.exe" ) [/code] The parentheses cause everything within them to be run in a subshell -- a subprocess of the current shell -- so only the subshell changes its current directory to /media/cdrom0. Then the "exec" arranges for wine to _replace_ the subshell process, rather than being run as a child of the subshell, so only the wine process has its current directory on the CD (and one hopes that "wine eject" knows how to deal with that).
