--------------------------------------------------------------------------- M i n e r v a S o f t w a r e T e c h n i c a l R e l e a s e Number: 010/GmHDsc Minerva House Date: 12/12/89 Baring Crescent Author: MK Exeter, Devon Pages: 01 EX1 1TL Using GammaPlot on a hard disc --------------------------------------------------------------------------- To use GammaPlot on a hard disc, you should have a RISC OS machine. If your GammaPlot is pre v2.00 you should make a backup and convert it using the RISC OS support disc. The software may be copied to the hard disc as follows (use the desktop drag mechanism to copy the files): 1. Copy the contents of the LIBRARY directory to the LIBRARY directory on the hard disc. This should be the directory which ADFS perceives as the library; normally it will be $.LIBRARY but some users may have changed it. 2. Copy everything else wherever you like. It is suggested that a directory called $.Gamma should be used 3. Now start GammaPlot by double-clicking on the !Gamma icon in the directory used. Before doing this, you may wish to use the task manager to allocate as much memory as possible to the NEXT slot (see Archimedes User Guide). 4. Once you are in GammaPlot, use the *command option to issue the command to select the directory containing your data files, eg: *dir :4.$.Gamma you may then proceed as normal. Common pitfalls --------------- 1. The library is not called $.LIBRARY on drive 4. This is most common with a 310 with hard disc upgrade since the machine will be configured to have drive :0 as the default and will therefore expect to find the library on the floppy disc. Fix by configuring to drive :4. 2. The user attempts to start GammaPlot by SHIFT-BREAK or by double-clicking on !Boot. This will not work! Start by double-clicking on the !Gamma Application which shows GammaPlot Symbol in the directory viewer. 3. The modules do not initialise properly. This can happen if you re-start GammaPlot after a failure or quitting. Fix by pressing CTRL-BREAK. 4. The modules do not load. This can happen if the module RAMMANAGER does not match the module Gamma in the library, for example an update has been provided and only one module was copied over. Fix by deleting all copies of these modules and re-copying these two files from the latest GammaPlot master disc available. 5. The wrong module loads, eg. GammaPlot still asks for the master disc even after upgrading to un-protected. This is similar to (4) above but note that the unprotected module is probably called GammaNP. This will not load if Gamma is present as the actual filename used is Gamma* --01---010/GmHDsc----------------------------------------------------------