Answers Database

Design Manager M1: Design Manager does not start when I double click theicon (PC)


Record #2284

Product Family:  Software

Product Line:  M1 Graphical/General

Problem Title:
Design Manager M1: Design Manager does not start when I double click
theicon (PC)



Problem Description:
Keyword: design manager, start, icon

Urgency: Standard

General Description:

On Win95 or WinNT, the Design Manager does not start when you double
click the shortcut icon, nor when you select Start->Programs->Xilinx->Design
Manager.  No error message or warning is generated.


Solution 1:

Check your system enviroment by opening up your autoexec.bat file (win95) or
Control Panel->System->environment  (winNT).

Verify that the 'XILINX' variable is set correctly.

Correct setting:
SET XILINX = C:\XILINX

Incorrect setting:
SET XILINX = C:\XILINX;C:\any\other\path

Please refer to your "Quickstart Guide" for additional detail on environment set
tings.




Solution 2:

The TEMP directory may point to a directory that is not there
or is read only.  Design Manager is unable to create temporary files
in the directory pointed to by TEMP.

Solution:

1. If the TEMP variable is not set, edit the autoexec.bat
(Win95) or add it to your environment (WinNT).	Make sure that
the TEMP variable points to a valid location.

2. If the TEMP directory is already set, verify that the
directory exists.  If not, create the directory.  Remember, this
directory must exist and it must be readable and writeable. Once the
directory has been created, the computer must be restarted.

NOTE: The TEMP variable should not have a trailing '\'.  This can
cause invalid directory names to be formed.



Solution 3:

Try placing the XILINX variable closer to the top of the autoexec.bat file.  It
has been seen that the Design Manager will not start or is slow to start if the
XILINX variable is placed toward the bottom of the autoexec.bat.



Solution 4:

Some autoexec.bat files contain subsections that specify
certain commands that are executed depending on what
operating system is being booted.  These subsections are
typically designated by "goto" statements.

Make sure that your XILINX and PATH variables are set
*before* any "goto" statements and outside of any such
subsections.  Ideally, they should be placed at the
beginning of the autoexec.bat file.



End of Record #2284