Page 1 of 1
Setup taking ages!?
Posted: 2009-09-09 10:28
by Maj0rMatt
Im sure this is a common problem but nether the less this is ridiculous ive been trying to bootup the setup for the pr core for over an hour and now and ive been waiting for 45 mins and still nothing. Does anyone have a fix or some advice? Im running vist ultimate 32bit.
thanks
Re: Setup taking ages!?
Posted: 2009-09-09 10:55
by gomimin
No need to make up a second thread

Moderators can you merge them please?
Did you install BF2, patched to 1.41 and then to 1.50final? Did you do a reboot after doing so?
Did you install it at default path? c:\programm files (x86) ...
If so did a licence agreement appear after starting core installation?
Re: Setup taking ages!?
Posted: 2009-09-09 12:31
by com_kieffer
disable uac.
Re: Setup taking ages!?
Posted: 2009-09-09 15:07
by Maj0rMatt
I have disabled UAC and still nothing is happening. Earlier this morning I went through and uninstalled and re installed everything to do with bf2 and still nothing the install worked yesterday but why not today?
thanks guys
Re: Setup taking ages!?
Posted: 2009-09-09 18:16
by thepalerider
Maj0rMatt
It is important to only start the installer ONCE. The files are compressed and as you know the archive is over a gig! It took me (AMD 4800x2+ 2 gigs ram) a little over 10 min. to see the install window open for Core and a little over 5 for levels. If you are taking longer than that try rebooting and just open the installer after you reboot and the system is fully loaded.(+4 mim?)
If it still doesn't work try a new download.
Your org. maybe corrupted.
Good luck
Re: Setup taking ages!?
Posted: 2009-09-09 20:10
by Snares
Install InstallShield 10.5:
http://support.installshield.com/kb/fil ... te1050.exe
Install InstallShield 11:
http://support.installshield.com/kb/fil ... te1100.exe
(From
Q108322: Update to the Latest InstallShield Installation Engines.)
Update the Windows Installer...
Download details: Windows Installer 4.5
If it still won't work, go run disk cleanup and check "Temporary Files."
Also, you might try running the patch from a command prompt. That might generate some kind of meaningful error.