Answers Database

Installing and Running Xact Step 6.0 over a Network.


Record #816

Product Family:  Software

Product Line:  Merged Core

Problem Title:
Installing and Running Xact Step 6.0 over a Network.


Problem Description:
Installing the software on a network is very similar to running the software
from the CD.  The following will describe what you need to do in order to
run the Xact Step 6.0 software on a PC over a network.


Solution 1:

Step 1.  From a PC execute and follow the instructions in the setup.exe program

from the root directory of the Xact Step 6.0 CD.  You must set the install
paths to the network drive where you wish to install the software.

In Step 1 you will have fully installed the Xilinx software to run over the
network for the PC which you executed the setup program from, in order to set
up each additional PCs (that may or may not have write priveleges to that
network directory) do the following.

The following procedures assume that C:\ is a local drive and that N:\ is the
Network drive that contains the N:\XACT and possibly the N:\PROSER directories.
The CDROM (or certain files from the CDROM) must also be accessible for
copying to local systems.  We will assume that a CDROM is on D:\.

The first thing that must be checked is the version of WIN32S that is running.
The version that is required by the Xilinx tools, and the version that is on
the XACTstep CD-ROM, is 1.25.142.0.  You can verify this by running XMEM or
XINFO (Windows executables found on the XACTstep CD-ROM in D:\XBBS\UTILS) or
looking at the file:  C:\WINDOWS\SYSTEM\WIN32S.INI.  You can run XINFO by
choosing File -> Run in the Program Manager and selecting
D:\XBBS\UTILS\XINFO\XINFO.EXE.	XMEM is run in the same fashion.

If the version currently running is not 1.25.142.0, you must exit Windows and
use the batch file on the XACTstep CD-ROM in the D:\XBBS\UTILS directory.  The
file is called RMWIN32S.BAT and will remove the current WIN32S.  Simply type
RMWIN32S at the DOS prompt and follow the directions.  Then you must re-enter
Windows and re-install WIN32S by choosing File -> Run and selecting
D:\WIN32S\DISK1\SETUP.EXE and following the directions.


XACTstep only.

The following procedures describe how to set up a PC to run the Xilinx XACTstep
core tools directly from the Network.:

 	1)  If running Windows, exit.

 	2)  Create a local XACTstep directory with a DATA sub-directory.

 		Example:  mkdir C:\NETXACT
			     mkdir C:\NETXACT\DATA

 	3)  Copy the PARTLIST.XCT file from the Network XACTstep DATA
     sub-directory to the local XACTstep DATA sub-directory.

 		Example:  copy N:\XACT\DATA\PARTLIST.XCT C:\NETXACT\DATA

	4)  If the directory C:\XACTUSER does not exist, create it now.

		Example:  mkdir C:\XACTUSER

	5)  Copy all the D:\XACT\WINDOWS\SYSTEM files from the XACTstep
     CD-ROM to the C:\WINDOWS\SYSTEM directory.

	Example:  copy D:\XACT\WINDOWS\SYSTEM\*.* C:\WINDOWS\SYSTEM

	6)  Create the following path on your C: drive:
     C:\WINDOWS\ASYM\RUNTIME

		Example:  mkdir C:\WINDOWS\ASYM
			  mkdir C:\WINDOWS\ASYM\RUNTIME

	7)  Copy all the D:\XACT\WINDOWS\ASYM\RUNTIME files to this new
     directory.

	      Example:	copy D:\XACT\WINDOWS\ASYM\RUNTIME\*.*
     C:\WINDOWS\ASYM\RUNTIME

 	8)  Make the three following changes to the AUTOEXEC.BAT file:

 		SET XACT=C:\NETXACT;N:\XACT

 	NOTE:  The first directory in the XACT environment variable MUST
contain a writable version of the PARTLIST.XCT data file in its DATA
sub-directory.	The second path included in XACT is the CD XACTstep directory
and is used by the XACTstep software to locate data files.

 		SET PATH=N:\XACT;<other_paths>

 	NOTE:  The only path added to the PATH environment variable are the
CD-ROM executable path 	XACT.  The local paths created in the previous steps
do not need to be added.

 		SET XACTUSER=C:\NETXACT

 	NOTE:  To ensure that the XACTstep software has directory that can be
written to, the XACTUSER environment variable should be set to a local
directory.  Because a local XACTstep directory has already been created to
store a local copy of the partlist it can be used as the temporary file
storage area as well.

	      9)  Make sure the following line exists in your
c:\windows\system.ini file.
In the [386Enh] section there should be a line that states: device=daikon.386
If this line doesn't exist add it and save your system.ini.

 	10)  Reboot your machine or execute your AUTOEXEC.BAT file so the new
changes take effect.

 	11)  Start Windows.


Now that the system has been properly configured to run the software from the
Network, all that remains is to create a Network program group.  To create a
program icon, perform the following steps:

 	1)  To create a new program group in the Program Manager, select the
New command from the File menu.  The New Program Object dialog is displayed.

 	2)  Select the Program Group radio box and click on OK.  The Program
Group Properties dialog is displayed.

 	3)  Enter the name of the new group in the Description text field and
click on OK.  For example, type "Network XACTstep 6.0".  The new program group
is created and displayed in the Program Manager.

 	4)  To create a new Program Item in the new group, select the New
command from the File menu.

 	5)  Select the Program Item radio box and click on OK.	The Program
Item Properties dialog is displayed.

 	6)  In the Description text field, type:  Xilinx Design Manager

 	7)  In the Command Line text field, type: N:\XACT\DSGNMGR.EXE

 	8)  In the Working Directory text field, type: C:\NETXACT

 	9)  Click on OK.



PRO Series and XACTstep.

The following procedures describe how to set up a PC to run both the Viewlogic
PRO Series and the Xilinx XACTstep tools directly from the Network.:

 	1)  If running Windows, exit.

 	2)  Create a local PRO Series directory with a STANDARD sub-directory.

 		Example:  mkdir C:\NETPROSER
 			  mkdir C:\NTPROSER\STANDARD

 	3)  Create a local XACTstep directory with a DATA sub-directory.

 		Example:  mkdir C:\NETXACT
			  mkdir C:\NETXACT\DATA

 	4)  Copy the PARTLIST.XCT file from the Network XACTstep DATA
sub-directory to the local XACTstep DATA sub-directory.

 	Example:  copy N:\XACT\DATA\PARTLIST.XCT C:\CDXACT\DATA

	5)  If the directory C:\XACTUSER does not exist, create it now.

		Example:  mkdir C:\XACTUSER

	6)  Copy all the D:\XACT\WINDOWS\SYSTEM files from the XACTstep
CD-ROM to the C:\WINDOWS\SYSTEM directory.

	Example:  copy D:\XACT\WINDOWS\SYSTEM\*.* C:\WINDOWS\SYSTEM

	7)  Create the following path on your C: drive:
     C:\WINDOWS\ASYM\RUNTIME

		Example:  mkdir C:\WINDOWS\ASYM
			  mkdir C:\WINDOWS\ASYM\RUNTIME

	8)  Copy all the D:\XACT\WINDOWS\ASYM\RUNTIME files to this new
directory.

	   Example:  copy D:\XACT\WINDOWS\ASYM\RUNTIME\*.*
C:\WINDOWS\ASYM\RUNTIME

	9)  Copy all the D:\PROSER\WINDOWS files from the XACTstep CD-ROM
to the C:\WINDOWS directory.

		Example:  copy D:\PROSER\WINDOWS*.* C:\WINDOWS

	10)  Copy all the D:\PROSER\WINDOWS\SYSTEM files from the XACTstep
CD-ROM to the C:\WINDOWS\SYSTEM directory.

	Example:  copy D:\PROSER\WINDOWS\SYSTEM\*.* C:\WINDOWS\SYSTEM

	11)  Make the four following changes to the AUTOEXEC.BAT file:

 		SET WDIR=C:\NTPROSER\STANDARD;N:\PROSER\STANDARD

 	NOTE:  The first directory in the WDIR environment variable MUST be a
writable directory.  This is where the project information will be written.
The second path included in WDIR is the Network PRO Series STANDARD directory
and is used by the PRO Series software to find data files.

 		SET XACT=C:\NETXACT;N:\XACT;N:\PROSER

 	NOTE:  The first directory in the XACT environment variable MUST
contain a writable version of the PARTLIST.XCT data file in its DATA
sub-directory.	This is used by Xilinx PROflow which will fail if the Network
version which is not writable is used.	The second path included in XACT is
the Netowrk XACT directory and is used by the XACTstep software to locate
data files.

 		SET PATH=N:\XACT;N:\PROSER;<other_paths>

 	NOTE:  The only paths added to the PATH environment variable are the
Network executable paths XACT and PROSER.  You do NOT need to add the local
paths created in the previous steps.

 		SET XACTUSER=C:\NETXACT

 	NOTE:  To ensure that the XACTstep software has directory that can be
written to, the XACTUSER environment variable should be set to a local
directory.  Because a local XACTstep directory has already been created to
store a local copy of the partlist it can be used as the temporary file storage
area as well.

	      12)  Make sure the following line exists in your
c:\windows\system.ini file.
In the [386Enh] section there should be a line that states: device = daikon.386
If this line doesn't exist add it and save your system.ini.

  	13)  Reboot your machine or execute your AUTOEXEC.BAT file so the new
changes take effect.

 	14)  Start Windows.


Now that the system has been properly configured to run the software from the
Network, all that remains is to create a Network program group.  To create a
program icon for Xilinx PROflow, perform the following steps:

 	1)  To create a new program group in the Program Manager, select the
New command from the File menu.  The New Program Object dialog is displayed.

 	2)  Select the Program Group radio box and click on OK.  The Program
Group Properties dialog is displayed.

 	3)  Enter the name of the new group in the Description text field and
click on OK.  For example, type "Network XACTstep 6.0".  The new program group
is created and displayed in the Program Manager.

 	4)  To create a new Program Item in the new group, select the New
command from the File menu.

 	5)  Select the Program Item radio box and click on OK.	The Program
Item Properties dialog is displayed.

 	6)  In the Description text field, type:  Xilinx PROflow

 	7)  In the Command Line text field, type:  N:\PROSER\PSFM.EXE

 	8)  In the Working Directory text field, type:	C:\NTPROSER

 	NOTE:  It is important that the Working Directory be located on the
same drive as projects that will be used in Xilinx PROflow.

 	9)  Click on OK.


Creating Other Icons.

We have described how to create the Design Manager and PROflow icons.  You
can add other icons in the same way, with the Network path in the Command
Line field and a writable path in the Working Directory.  Here are the paths
of some useful Windows tools that cannot be accessed through the Design Manager
or PROflow:

Simulation Utility:		N:\XACT\XSIMWIN.EXE
Symbol Generator:		N:\XACT\SYMWIN.EXE
Memory Generator:		N:\XACT\MEMWIN.EXE

Online Documentation:
Xilinx Apps Info:		N:\XACT\ONLINE\ONLINEDB\DBLINK.PDF
Xilinx Online Docs:		N:\XACT\ONLINE\ONLINE\LINKPAGE.PDF
PRO Series Online Docs:		N:\PROSER\ONLINE\PROLINK.PDF

In order to use the Adobe Acrobat Reader to access the Online Documentation,
you must install it or create an icon pointing to the XACTstep directory on
the Network.
To install, choose File -> Run and select D:\ACROBAT\DISK1\SETUP.EXE.  Or,
the icon to run from the Network would have a Command Line of
N:\ACROBAT\ACRO_LE.EXE and a Working Directory of something local,
like C:\NETXACT or C:\NTPROSER




This list contains all the files that are installed under the \windows
directory when the PROseries tools, XACT core tools, and tutorials are
installed.

PROSER or PROSYN program files in \windows :
_default.pif		bprogen.pif		bvhdl.pif
bvhdlw.pif		pinsave.pif		sysblock.pif
syscmd.pif		timerpt.pif		xalttmp.pif
xemake.pif

PROSER or PROSYN program files in \windows\system :
cstext.vbx		gauge.vbx		mh3b200.vbx
mhgchk.vbx		mhgcmb.vbx		mhgdir.vbx
mhgdrl.vbx		mhgfil.vbx		mhgfrm.vbx
mhglbl.vbx		mhgmul.vbx		mhgopt.vbx
mhin200.vbx		mhinint.vbx		mhmq200.vbx
mhrun400.vbx		mhsl200.vbx		olecli.dll
sbc.vbx			threed.vbx		toolhelp.dll
vbrun300.dll		vshare.386

XACT program files in \windows\system :
cmdialog.vbx		ctl3d.dll		ctl3d32.dll
daikon.386		threed.vbx		vbrun300.dll

Tutorial files in \windows\asym\runtime
mtb30anm.sbk		mtb30bas.dll		mtb30bmp.dll
mtb30cmp.dll		mtb30flt.dll		mtb30lnl.dll
mtb30mm.dll		mtb30mm.ini		mtb30net.exe
mtb30run.exe		mtb30utl.dll		pcdxbmp.dll
photo.dll		mtbload.exe		pcdlib.dll



End of Record #816