The problem will NOT be fixed for Foundation F1.5i.
A workaround that can be used with the Alliance 2.1i and Foundation F1.5i releases, as well as the F2.1i release, is to specify the Foundation path locally for each of your projects using a project-specific coregen.ini file as follows:
Create a coregen.ini file in your project directory with the following line in it:
set FoundationPath=<path_to_Xilinx_Foundation _directory>
Example: set FoundationPath=c:\\fndtn2_1i
Note that you must use a double backslash for the path delimiter for this to work. C:\\fndtn2_1i corresponds to the top level Foundation 2.1i installation directory.