AnalytiCalc Abstract: AnalytiCalc is a large and powerful spreadsheet program with sufficient extra features to have some pretentions of acting as an "integrated system". It is a virtual memory system supporting up to 18000 columns and 18000 rows, multiple equations per cell, an outlining system, built-in cell annotation, and datafile access from any cell(s) of the sheet, plus an array of functions not present in most commercial spreadsheets. This disk represents the fifth version of an initial Amiga port of AnalytiCalc, and as such the console interface is somewhat crude and uses a set of command files in an externally assigned area (assigned to DK:) to handle the function keys. Arrow keys and the HELP key are interpreted automatically. NOTE THAT ANALYTICALC RUNS WITH THE AmigaDos CON: DRIVER and DOES NOT WORK WITH CONMAN 1.3 UNDER AMIGADOS 1.3. AnalytiCalc for the Amiga uses files compatible with those for AnalytiCalc on MS-DOS, VMS, or RSX-11M or IAS. An example project planner spreadsheet is included in the distribution to show off some of the things you can do. More example sheets will be forthcoming in the future. AnalytiCalc also supports matrix math, FFTs, infinite windowing, linear regression, date arithmetic, internal and external macros, LOTS of cell addressing modes, goal seeking in up to 8 dimensions, and more. AnalytiCalc fits (barely) in 512K of memory (in non interlace mode) and needs AmigaDos 1.2 or later. You must also either assign DK: as some directory where keypad .CMD files are or click CANCEL on a requestor when AnalytiCalc asks for drive DK to be mounted somewhere. Display sizes supported can be up to 132 characters wide by up to 76 lines long. Sorry; I don't think AnalytiCalc supports proportional fonts very well, though it should manage not to be totally brain damaged with them. The manual requires an 80 column printer. To see the documentation you need either a printer 80 columns wide to print it, or an 80 column screen to view it on. ** PLEASE read the README.1ST file for brief instructions on setting up a working AnalytiCalc disk. Please read the manual at least once over lightly too... *** SOME DO-NOT'S 1. DO NOT use AnalytiCalc until you have read the documentation. 2. DO NOT forget to make regular backup copies of your database. 3. DO NOT exit (X) the progam without saving your work if you want it saved. (You will be asked to confirm you really want to leave, however.) GETTING STARTED. See the README.1ST file!!! If you haven't already printed the documentation, please do so before trying to operate AnalytiCalc. Then, READ IT! You should also make sure that you have placed a "write-protect" tab on your AnalytiCalc distribution diskettes, so that they can't be accidentally erased or overwritten. You should now make a copy of your AnalytiCalc disks. These will also serve as your "run-time" system diskettes. Please read the document files and release notes. You'll need a bit of AmigaDos familiarity to set things up (read how to use the ASSIGN command and the SETMAP command and ASSIGN something as DK:; also set your stack large with the STACK command.) If you are using disk file memory, FACC is a good thing to use also. PLEASE READ THE MANUALS though, to save us all a lot of headaches. SOME MAXIMUMS AND MINIMUMS. Minimum RAM Memory required .....................about 500K Minimum Disk Drives required...............................1 Minimum Disk Storage required...........................880K Number of Columns......................................18000 Number of Rows.........................................18000 Maximum Length of Formulas (characters)..................109 Number of cells that can be full at once...............18000 Number of simultaneous named areas permitted.............300 Number of scratch cells outside spreadsheet...............60 Precision of calculations (digits; 8 bytes used)..........16 Total maximum storage managed (bytes)..............2,113,020 Maximum depth of document nesting (outline processor)......4 Maximum number of parameters varying to goal seek..........8 Maximum record size for data files accessed as database..128 Maximum number of files namable in one sheet.........>18000 Maximum cell columns displayable on one screen............20 Maximum number of rows displayable in one display.........75 Maximum simultaneous different cell display formats per sheet (taken from large set)...........................76 Length of format specification (characters)................9 DISCLAIMER. In no event will the Author be liable to you for any damages, including any lost profits, lost savings or other incidental or consequential dmages arising out of the use of or inability to use these programs, even if the Author has been advised of the possibility of such damages, or for any claim by any other party. THE USER-SUPPORTED CONCEPT. User-Supported Software You are encouraged to copy and share this program with others. If after evaluating this program you find it to be useful, I hope you will send a $10 donation. Glenn C. Everhart 25 Sleigh Ride Rd. Glen Mills, Pa. 19342 To Be Done: Future plans for AnalytiCalc: 1. Allow data files to be on a logical device. (Actually, FACC may make this need obsolete). 2. Fix bugs as they are discovered. 3. Someday add an IDCMP interface to support menus properly. Auxiliary files: 1. Check that DIFrw (DIF to or from AnalytiCalc saved format converter) and ACGRAF (character graphics utility) work as specified. 2. Port some of the BASIC graphics packages to Amiga. Possibly compile some of them. 3. Supply the Business Expense Report, manpower planner, and income tax templates as extra examples. Possibly do a game of LIFE template too, just for fun. Other programs: Port the DBAG relational database to Amiga from VAX. This is a roughly dBase III compatible database available from DECUS. The Amiga port is in very early stages presently. I have found that Absoft Fortran 2.3 is a stable and usable compiler and would like to acknowledge gratefully its contribution. He who wants to add to or modify AnalytiCalc needs Absoft Fortran 2.3 (or later, I suppose) to build it with. Anyone who has Absoft Fortran-020 for the 68020 is invited to recompile this program to use the faster chips. I didn't have either money or machine to try a 68020/68881 version, but see no reason why it would fail. I have also seen that there are some bugs in Absoft Fortran's handling of con: and raw: windows which I have reported to Absoft. Hopefully this will permit upgrading of user interface soon, as these problems are fixed. The bugs require use of REWIND, which I suspect is causing the problems with ConMan 1.3. The normal AmigaDos CON: driver works fine. (It seems that you CAN do both read and write to CON: windows in Absoft Fortran 2.3, but you must issue a REWIND on the unit between them. This is not always needed in V2.2, but occasionally happens. (This accounts for the occasionally flaky behavior of DTC, which was compiled with V2.2 before I found the foregoing out.) Since then I have basically abandoned Absoft's console handling in favor of using raw: myself. Glenn Everhart 6 November 1987 Small AnalytiCalc can run in 512K, but is VERY tight. It does not need any extra stack. The executables here may need to be unpacked before they'll fit in 512K though. In general, to shrink it, the routines in file AnalyO.Ftn can be overlaid against each other. Those with the Absoft Fortran compiler may want to try this. AnalytiCalc uses a window on the Workbench screen. Thus, it can run interlaced or non interlaced (that is, on a 640 by 400 window or a 640 by 200 window). Just tell it whether to use the interlace (640 by 400) window dimensions at startup. DO NOT tell it to use the interlace dimensions if you have not in fact turned interlace on in Preferences and booted that way. It WILL crash if you do this. SetLace is NOT equivalent. Glenn Everhart May 9, 1988 Enjoy... Additions: PB and GB supplement PP and GP commands. These save or load a spreadsheet in an Amiga specific "binary" format, faster than the corresponding PP and GP commands. NOTE: Spreadsheets saved with the PB command cannot be used in AnalytiCalc internal commands like *X or the like, and are not portable across machine types. They are faster than saving with PPx and loading with GPx, but the PPx commands have been sped up also in V23-1A. AnalytiCalc starts MUCH faster now than earlier versions. If this disk is renamed, the icons for some documents and executable files need to have the disk name changed. Use the Workbench icon tool to do this.