Changes between Version 7 and Version 8 of OldZipInstall


Ignore:
Timestamp:
Jan 19, 2016 5:50:15 PM (6 years ago)
Author:
toby
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OldZipInstall

    v7 v8  
    55The minimal files needed to run subversion can be downloaded as a zip file, along with a batch file that will install GSAS-II from the server.
    66
    7  1.    Download the svn kit using one of these URLs: https://subversion.xray.aps.anl.gov/pyGSAS/install/GSASIIsvn.zip or https://subversion.xray.aps.anl.gov/trac/pyGSAS/browser/install/GSASIIsvn.zip?format=raw
     7 1.    Download the svn kit using one of these URLs: https://subversion.xray.aps.anl.gov/pyGSAS/install/GSASIIproxy.zip or https://subversion.xray.aps.anl.gov/trac/pyGSAS/browser/install/GSASIIproxy.zip?format=raw
    88
    9  2.   Open the downloaded GSASIIsvn.zip in the Windows Explorer -- you should see a single folder named GSAS-II. Drag this folder to where you would like to install the software.
     9 2.   Open the downloaded GSASIIproxy.zip in the Windows Explorer -- you should see a single folder named GSAS-II. Drag this folder to where you would like to install the software.
    1010
    11  3. Open this folder in its new location and double-click on the bootstrap.bat file. A "DOS" (cmd.exe) window will open and you should see:
     11 3. Open this folder in its new location and run the ```bootstrap.py``` file. If Python is in your system's path, double-click on the ```bootstrap.bat`` file. this will A "DOS" (cmd.exe) window will open. If you need to use a version of Python that is not in your path, you will need to edit the .bat file to include the path or use an alternate way to invoke Python (see WinAnacondaInstall or WinCanopyInstall).
     12
     13 4. When the ```bootstrap.py``` file runs, you will see a prompt like this:
    1214{{{
    13     ***********************************************************
    14     Please enter proxy server information, if required for your
    15     web environment. Note that the proxy address will be a
    16     computer address (proxy.mysite.com) and the proxy port will
    17     be a number, such as 80. If not needed or you are unsure,
    18     leave the next answer blank.
    19     ***********************************************************
    20     Enter the proxy address [none needed]:
    21 }}}
    22  4. If a proxy is entered in step 3, then supply a port for the proxy:
    23 {{{
    24     Enter the proxy port [8080]:
    25 }}}
    26  5. You will then see this text:
    27 {{{
    28     *****************************************
    29     Preparing to load/update GSAS-II
    30     *****************************************
    31     Press any key to continue . . .
     15
     16==========================================================
     17Enter the proxy address [none needed]:
     18
    3219}}}
    3320
    34    Press Enter and the transfer of files should start. Note that a message like this:
     21 At most sites you can simply press Enter to use the default value (no proxy), but if you do enter a proxy address, you will also be prompted to supply a port for the proxy:
    3522{{{
    36 svn: OPTIONS of 'https://subversion.xray.aps.anl.gov/pyGSAS/trunk': Could not con
    37 nect to server (https://subversion.xray.aps.anl.gov)
     23Enter the proxy port [8080]:
    3824}}}
    39 is an indication that a proxy server may be needed.
    4025
    41 If it runs correctly, after it completes you should see:
     26 Assuming that GSAS-II needs to install pyOpenGL (usual, depending on the Python installation), this will cause lots of warning messages to flash past but unless the script halts with an error, everything is most likely fine.
    4227
    43 {{{
    44 ...
    45 A    gsas2mac.ico
    46 A    GSASIIstruct.py
    47 A    ImageCalibrants.py
    48 A    GSASIIspc.py
    49 Checked out revision 331.
    50 Files have been loaded. Press Return to start GSAS-II.
    51 Press any key to continue . . .
    52     }}}
     28 After the script completes, a file named ```RunGSASII.bat``` is created with the locations of GSAS-II and Python hardcoded and a shortcut to start GSAS-II is created on the desktop linked to ```RunGSASII.bat```. The extension ``.gpx``` is registered so that GSAS-II project files will be shown with the GSAS-II icon and so that clicking on them will open them in GSAS-II.
    5329
    54   If GSAS-II fails to start, you should debug that by starting a DOS window (use Start to run cmd.exe) and then in that window type
     30** Debugging **:   If GSAS-II fails to start, you should debug that by starting a DOS window (use Start to run cmd.exe) and then in that window type
    5531
    5632{{{
     
    6036to see what error is occurring.
    6137
    62     After GSAS-II has been installed, it can be started by clicking on the GSASII.BAT file. Note that this file should not be moved from the installation directory. Also, it assumes that the Python package is found in the path. If this is not the case, it will be necessary to edit the .BAT file to add a full path for the python command (change `python %gsasloc%\GSASII.py %1` to `"C:\EPD dist\PYTHON27\python.exe" %gsasloc%\GSASII.py %1`, etc.)
    6338
     39** Add shortcut(s) to Start Menu ** (optional):
    6440
    65   4.  Make a desktop shortcut to GSAS-II (optional)
     41 Right-click on Start Menu, select open from list of choices
    6642
    67     Right-click on the GSASII.py file and select "Create Shortcut". Drag the new shortcut to the desktop (or your preferred location). This may work for you as-is, but you may want to or need to make changes. To do that right-click on the shortcut and select properties. This opens the properties dialog. In that window make these changes:
     43 Left-click on Programs folder
    6844
    69     '''Target:''' If you obtain an error where Windows does not know what program to associate with .py files, either associate them with the python installed on your computer or add the full path to python before the path to the GSASII.bat file in the "Target:" box:
     45 Right-click on a blank section of folder and select new->folder to create place for shortcuts, name the new folder GSAS-II (or whatever you prefer)
    7046
    71         {{{C:\PYTHON27\python.exe C:\GSASII\GSASII.bat $*}}}
    72 
    73     If you used a directory that has spaces in the name put the names in quotes, e.g.:
    74 
    75         {{{"C:\EPD dist\PYTHON27\python.exe" C:\GSASII\GSASII.bat $*}}}
    76 
    77     Note the $* is optional, but it allows files to be "dropped" onto the shortcut.
    78 
    79     '''Start in:''' Change this box to wherever you would like to have GSAS-II start -- where you keep your data files. (Optional)
    80 
    81     '''Change Icon:''' Use this button to change the icon to the GSAS2.ico file in the C:\GSASII directory (optional).
    82 
    83     You may also want to rename this shortcut.
    84 
    85   5.  Add shortcut(s) to Start Menu (optional)
    86         Right-click on Start Menu, select open from list of choices
    87 
    88         Left-click on Programs folder
    89 
    90         Right-click on a blank section of folder and select new->folder to create place for shortcuts, name the new folder GSAS-II (or whatever you prefer)
    91 
    92         Copy the shortcut(s) created above from the desktop to the new folder in Start Menu\Programs
     47 Copy the shortcut(s) created above from the desktop to the new folder in Start Menu\Programs
    9348
    9449== Updating GSAS-II to the latest version ==
    9550
    96 GSAS-II is updated often (sometimes daily). The version that has been installed can be determined from the revision number listed when the Help/About GSAS-II menu is used. A summary of what is changed in each revision can be found in https://subversion.xray.aps.anl.gov/trac/pyGSAS/timeline. At any point, the bootstrap.bat file (see step 3, above) can be run again. When this is done, only the files that have been changed will be downloaded, so the transfer will take much less time. If you have made changes in any files, the subversion program (svn) will attempt to merge your changes with the updates on the server. This will usually succeed, but if there are conflicts, you will need to resolve them yourself before GSAS-II will run properly.
     51GSAS-II is updated often (sometimes daily). The version that has been installed can be determined from the revision number listed when the Help/About GSAS-II menu is used. A summary of what is changed in each revision can be found in https://subversion.xray.aps.anl.gov/trac/pyGSAS/timeline. At any point, the ```bootstrap.py``` file (see step 3, above) can be run again. When this is done, only the files that have been changed will be downloaded, so the transfer will take much less time. If you have made changes in any files, the subversion program (svn) will attempt to merge your changes with the updates on the server. This will usually succeed, but if there are conflicts, you will need to resolve them yourself before GSAS-II will run properly.