Hi,
Huh? How come I know of this issue and there's no bug against it here...
(I did think there was a bug about this, but perhaps it's a ticket that never
got linked to this app page) ... anyway, I can confirm the behavior you're
seeing ; it appears to be some issue with the .msi installer when it reaches
the end of the first filecopy operation, and has to wait for 2nd disk to be
inserted before commencing the second filecopy stage .....
... at least, that's how it appears in linux -- now that I read your outlay
of proceedings, I become suspicious there's a DRM 'parcel' involved here
somewhere (disc copy protection routine) that may be thwarting things...
Anyhow, the suggestion over at WineHQ is to copy all the files from the disc
media into a directory on your harddrive, and install in that manner --
"[i]if installing from the 3 cd set there is a chance that it wont install all the files or even ask from disk's 2 and 3
use the following command or similar to copy the missing files (from cd2 and 3) to the doom 3 directory
cp -av /media/cdrom/Setup/Data/base/pak00* ~/.wine/drive_c/Program Files/Doom 3/base
use the patch from ftp://ftp.idsoftware.com/idstuff/doom3/win32/DOOM3-1.3.1.exe
to update to 1.3.1 - the game will work without the cd's[/i]"
citing: http://appdb.winehq.org/objectManager.php?sClass=version&iId=2887
So, I think the gist of it is to start the installation as per normal, wait
for it to fail, and when it does just cancel the failed attempt. Apparently
it will have already created the game directory structure layout, so then
it's just a matter of copying the files manually from all the discs.
On the Mac, and assuming your Crossover Games bottle is named Doom3, you would
copy the files into the following path;
~/Library/Application Support/CrossOver Games/Bottles/Doom3/drive_c/Program Files/Doom 3/base
Having completed that, you would then download the patch from the idsoftware
ftp server, and install that into the same bottle as a 'Other Application'.
You may still need to install other runtime dependencies (like directx9modern
or whatever) as required.
If this is anywhere near the mark, you should then be able to launch the
Doom3.exe file and have things work -- let us know how it goes.. =)
Cheers!
