Forums

Is there some sort of common solution to "Error:-1603" during an installation with "Windows Installer"

------------------------Details---------------------------------------

After successfully installing both Tomb Raider Chronciles and Tomb Raider Legends with PoL scripts, I hit a snag with Tomb Raider: Angel of Darkness.

My CD's for "Tomb Raider: Angel of Darkness" were bought a few years after the original game was released and are pre-patched to version 52. The PoL script wouldn't work since there are some different file names.

Therefor PoL script would not find my CDrom until I changed the script as follows.

# POL_SetupWindow_check_cdrom "Lara Croft Tomb Raider The Angel Of Darkness.msi"        
POL_SetupWindow_check_cdrom "Lara Croft Tomb Raider Angel Of Darkeness.msi"

Before doing these changes I had tried various other ways of trying to install the game with the "Manual Installation" script. i.e. copying files to HDD in same folder, in diferrent folders, switching mount points in the wine configaruation, raw iso images, etc. Without success, all fail at some point with 1603 error, or refused to recognise the files from the 2nd disc.

Here is where it happened during the slightly modified PoL script.
The Install for this game crashes about 3/4 the way through with "Error:-1603" with "Updating Component Registration"
info: http://www.tech-faq.com/error-1603.html
At a guess, I think "Users cannot install software packaged in the Windows Installer format to a drive that is substituted for another drive." is most relevant cos of the way it seems wine drives work. (Don't quote me, I'm a newbie at this)

I also changed the following without success.
# WORKINGWINEVERSION="1.1.35"
# http://appdb.winehq.org/objectManager.php?sClass=version&iId=4145&iTestingId=78666&bShowAll=true
# lists almost all versions of wine working. Chose 1.4.1 cos some meantion of 1.5.x having issues with cd's on forum
# Not essential to make the script work, changed in order to see if it fixed installation problems
WORKINGWINEVERSION="1.4.1"

Note: http://bugs.winehq.org/show_bug.cgi?id=21153
Seems to have been reported by the same person who wrote the PoL Script (NSLW) and meantions 2 cd installs.
http://www.playonmac.com/en/topic-3202-scripts_Tomb_Raider_IIVI.html

Any help will be appreciated, thanks.

Do this. Create a folder in your home folder (doesnt matter what its called) and copy both discs in to that folder, then when the script asks for an install file, point it to the MSI in that directory. That usually fixes the multi-disc error.

Before you do that, make sure you delete that virtual drive and install it from the script again nice and fresh. But yeah. Copying the CDs to a folder will most likely take care of that for you.

Should probably also meantion that it installs and plays fine on winXP, so I don't think the disks are damaged.

Yeah. Thats to be expected. Windows programs run on Windows ;) lol

Ok, so dumped all the files from both disks in a folder under home. Same result as previous time I tried from single folder. Installations fails with 1603 error.

Also tried to install with the .msi file directly, and not the "setup.exe". This "crashed" wine immediately.

Tried using the .msi in the PoL script by changing
# wine "setup.exe"
wine "Lara Croft Tomb Raider Angel Of Darkeness.msi"
It did nothing during the install either

Edité par Spryte

Dont change that. It should automatically do that. You shouldnt start making changes to the script until we have finished troubleshooting.

First, lets do this; we need the debug output and your system specs (as per forum rules). Run playonlinux from the terminal, and try to install it again to a fresh virtual drive, DONT modify the script, and post the output here.

After reading various sources before I posted initially, I suspected I'd probably run into some sort of CD protection scheme for my particular release of the game. I had hoped, that the error 1603 might be a common problem that I could solve by installing .net into the "prefix" or updated IS or something.

So at this point I've solved my problem, of getting the game to work, by buying the gog.com version (also v52) and installing that with the PoL "manual Install" script. And it works as well as any of the http://appdb.winehq.org/ reviews.

While this proves it can work on my hardware It doesn't help me get it installed on my brothers computer. So I'll post the debug output as soon as I get a chance.

------------------------------------------------------
re "Dont change that. It should automatically do that. You shouldnt start making changes to the script until we have finished troubleshooting. "

As I said in 1st post the original PoL script for the game doesn't work "as is" because I have a later release of the game (i.e. it's already patched to v52). The script looks for original release cd's to install and then patches it to v 42 and then v52

So, all I've done is alter the script to detect my CD's, and use this as an alternate method of trying to get the install to complete. The reason I've done this is, because the script uses an interest way of copying the CD's files to the "prefixes" folders and then mount's this folder as a windows "E:" drive using wine, and runs the installation from there. Which is rather diffent from running the "Manual Install" script from ether the cd's, iso's or contents of cd's, in a folder or folders. All of which I had tried previously.

Ive also tried various versions of wine. I tried the install at least 30 times with various variations of the above factors, but at best I get the install failure error 1603.

Thereafter as you mentioned running the *.msi to install the game instead of the seup.exe, I tried it both with the "manual install" script and "edited" PoL script. Neither of which worked. So script is back to my original edit for cd detection.

------------------------------------------------------
Debug info will be from "Manual install" script using a single folder holding the contents of both CD's.