1. Download the following files:
Mirrors for these files can be found at
Note that the links for these files are on non-NIST servers.
ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_win/exptool.zip (~300 K bytes)
or ftp://ftp.ncnr.nist.gov/pub/cryst/gsas/exe_win/exptool.exe (~700 K bytes)
2. Run the programs
mkdir c:\gsas chdir c:\gsas c:\temp\gsaskit.exe -d c:\temp\tcltk80p2+.exe c:\temp\expgui.exeNote that gsaskit.exe must be run in the location where you want the files to be placed and that you must use the -d option. For this reason you must know what you are doing to do this from the Windows interface. (Using WinZip is another good way to unzip the file with the correct directory structure or to uncompress expgui_alpha.zip). The tcltk80p2+.exe and expgui.exe files can be run from Windows.
The previous steps will cause the files to be unpacked. The default locations for installation are:
gsaskit.exe c:\gsas tcltk80p2+.exe c:\expgui expgui.exe c:\gsas\expgui
These files can be located on other disks and in directories with other names, but the expgui files in expgui.exe must be located in a subdirectory of the GSAS files and each directory name must be 8 characters or less, so location Z:\i\think\this\will\work\gsas should be OK, but C:\longwindows\namesarenotgood\for dos probably will not work. If these files will be located on a fileserver, the file server must be mapped to appear as a disk drive (must be assigned a name such as F:).
3. When needed, install TCLDUMP and EXPTOOL
4. Create a shortcut:
More information about EXPGUI, including information on how it
can be customized, can be found on web pages expgui.html
found in the \gsas\expgui\doc directory.
6. Add the statement "SET GSAS=C:\GSAS" (again pick the appropriate drive letter) to your auto exec.bat file.
7. Add the statement "SET PGPLOT_FONT=C:\GSAS\FONTS\GRFONT.DAT"
8. Make sure you have sufficient environment space for these additions and two more that are done by gsas.bat each time you run gsas.
Note, to add more environment space in Win95/98, add the following line to the CONFIG.SYS file in the root directory
SHELL=C:\WINDOWS\COMMAND.COM /P /E:4096add the following line to the SYSTEM.INI file (in c:\windows) under the heading [NonWindowsApp]
CommandEnvSize=2424(thanks to Louis Farrugia [firstname.lastname@example.org] for this). 3. What versions of Windows can I use?
The other appears to be a graphics mode problem. Not all modes work on all machines. Try mode A. If you still have problems, see if it is an EXPGUI problem: Try using a plotting program (RAWPLOT is a good choice) from PC-GSAS or GSAS.BAT. If the plotting program does not work there either, first check PGPLOT_FONT is defined (by opening a DOS box and type SET, also see question 2, above.) If the plotting program runs in PC-GSAS or GSAS.BAT but not EXPGUI, you have a real EXPGUI bug and should bug me.
GSAS is written by Allen C. Larson and Robert B. Von Dreele, MS-H805, Los Alamos National Laboratory, Los Alamos, NM 87545. Problems, questions or kudos concerning GSAS should be sent to Robert B. Von Dreele at email@example.com
GSAS is Copyright, 1984-1997, The Regents of the University of California. The GSAS software was produced under a U.S. Government contract (W-7405-ENG-36) by the Los Alamos National Laboratory, which is operated by the University of California for the U.S. Department of Energy. The U.S. Government is licensed to use, reproduce, and distribute this software. Permission is granted to the public to copy and use this software without charge, provided that this notice and any statement of authorship are reproduced on all copies. Neither the Government nor the University makes any warranty, express or implied, or assumes any liability or responsibility for the use of this software.
EXPGUI is written by Brian H. Toby of the NIST Center for Neutron Research, Brian.Toby@NIST.GOV with help from Jonathan Wasserman.
EXPGUI is not subject to copyright. Have fun with it.
Neither the U.S. Government nor any author makes any warranty, expressed or implied, or assumes any liability or responsibility for the use of this information or the software described here. Brand names cited here are used for identification purposes and do not consitute an endorsement by NIST.
Brian Toby (Brian.Toby@NIST.GOV)
$Revision: 374 $ $Date: 2009-12-04 23:05:06 +0000 (Fri, 04 Dec 2009) $