Answers Database M1.2 MAP: Problems with map3_nt.zip patch when installed in MYXILINX directory on Windows NT and Win95 systems: FATAL_ERROR:baspm:baspmdlm.c fail to open libx4kma.dll Record #2641 Product Family: Software Product Line: FPGA Implementation Product Part: map Product Version: 1.2. Problem Title: M1.2 MAP: Problems with map3_nt.zip patch when installed in MYXILINX directory on Windows NT and Win95 systems: FATAL_ERROR:baspm:baspmdlm.c fail to open libx4kma.dll Problem Description: Urgency: standard General Description: Map M1.2.11 with the map3_nt.zip patch may issue the following error on Windows NT and Windows 95 platforms when the following two conditions are true. 1. the patch is run from the Design Manager/Flow Engine GUI, and 2. the patch is installed in a separate location pointed to by the MYXILINX variable. The following error is issued: FATAL_ERROR:baspm:baspmdlm.c fail to open libx4kma.dll--1.2.11 map3_nt.zip patch Depending on whether Map is run from the Design Manager or from a DOS box in Windows NT, and whether the patch is installed in a separate MYXILINX area or installed over the Xilinx install directory, the results have been observed to vary as follows: WINDOWS NT: ===========            Patch installed Patch installed            to MYXILINX to XILINX dir.                --------------- --------------- Run from GUI Can't load Works ok ------------ libx4kma.dll Run from DOS box system crash system crash ------------ Win95: ======             Patch installed Patch installed             to MYXILINX to XILINX dir.                 --------------- ---------------   Run from GUI Can't load Works ok   ------------ libx4kma.dll   Run from DOS   box Works ok Works ok   ------------ In one test case, the design processes with no problem in M1.3.7. Solution 1: In general, installing patches in a separate MYXILINX directory on Windows NT systems shows varying degrees of success from system to system. The most reliable approach is to install any Xilinx patches to the Windows95/NT platform software to the XILINX directory instead. This means that any existing files are also in the patch must be overwritten. Reference Number: 18625 End of Record #2641 - Last Modified: 10/06/97 22:26

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!