search

macressler / bwapi

Automatically exported from code.google.com/p/bwapi
1 stars 0 forks source link

Installer does not prompt for missing install path #491

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download BWAPI 4.0.0 and full install with all gateways.
2. Run chaos launcher at the end of install pointing it to Starcraft.exe in 
settings.
3. Check the plugin BWAPI Injector (1.16.1) RELEASE

What is the expected output? What do you see instead?
Expected output: Launching Starcraft.
Output: Error: Unable to find ...\Starcraft\bwapi-data\BWAPI.dll

What version of the product are you using? On what operating system?
BWAPI 4.0.0 on Windows 7.

Please provide any additional information below.
The BWAPI 4.0.0 dll is not provided in the installer. Using an older BWAPI.dll 
will lead to failure to load AI. Must pull the read only source code and build 
that and copy that to the bwapi-data folder to work around.

Original issue reported on code.google.com by georgetw...@gmail.com on 24 Jun 2013 at 1:06

GoogleCodeExporter commented 9 years ago 
Can you open the Registry, locate "SOFTWARE\Blizzard Entertainment\Starcraft" 
and paste the value of "InstallPath"?

Did chaoslauncher ever prompt you to locate your Starcraft installation?

Original comment by AHeinerm on 24 Jun 2013 at 8:50

GoogleCodeExporter commented 9 years ago 
That is, in HKEY_CURRENT_USER. If not, then check HKEY_LOCAL_MACHINE.

Original comment by AHeinerm on 24 Jun 2013 at 8:55

GoogleCodeExporter commented 9 years ago 
It did prompt me to locate Starcraft.exe which I did.

I did not find the InstallPath.

Original comment by georgetw...@gmail.com on 25 Jun 2013 at 9:16

GoogleCodeExporter commented 9 years ago 
Then that is the issue. The installer itself attempted to locate the 
installpath, which wasn't set (because you may have copied Starcraft from 
elsewhere instead of installing it or some other reason). Since you've located 
it via Chaoslauncher, installing a second time should put the files in their 
correct locations.

The real issue should be if the installpath is not found, then the installer 
itself should ask to locate it.

I'll have this done for the next release.

Thanks.

Original comment by AHeinerm on 25 Jun 2013 at 10:32

GoogleCodeExporter commented 9 years ago 
Fixed in r4400.

Original comment by AHeinerm on 12 Aug 2013 at 8:03