4.6 | APPLEWORKS & MULTIRAM |
The actual time an action on a large file takes say be as little as half the time AppleWorks shows or as much as twice the stated time. The differences in actual versus approximate stated times will vary depending on the type of file in use and the operation called for.
For example, a sort on a large database file could be double the time Indicated if the sort is being performed on several fields with each record having information in the fields selected. A sort on the same database with only a few records having information in the fields being sorted could take half the time AppleWorks approximated. Moat of the time, however, the time stated by AppleWorks will closely approximate the actual time required to perform the selected operation on the large file.
Some activities may take what seems to he an extraordinarily long time to finish. If. this is the came, before restarting AppleWorks, give the action at least five minutes to finish. This should be more than enough time for any simple action on a large file to have been completed. More complex actions. like a recalculation on a complex, large spreadsheet may take somewhat longer to finish. In general, the larger the file and the more complex the task, the longer the time required. Look at the benchmark samples later ii, this section for some sample times to perform simple tasks.
MultiRam C Size
If you configure the AppleWorks Startup disk so that the entire program resides in memory at once (thereby speeding access to overlay portions of AppleWorks), approximately 130k will be used for the program. With a 256k MultiRam C, that would leave approximately 99k for large files: with 512k. approximately 283k would he left for files.
If the cumulative size of files on the Desktop grows larger than the available Desktop memory (total memory less 130k), then floppy users should have the Program disk in a disk drive as parts of the program will be Overwritten by data and AppleWorks will have to go to the Program disk to return the overwritten program segments to memory when they are needed.
Do not load AppleWorks into memory at bootup if you intend to consistently fill all of your desktop space with files. If data files fill most of the desktop, most of the program segments that took two minutes to load during bootup will be overwritten. You will have lost the advantage that you sought.
As suggested in the configuration section. you may want to configure two copies of AppleWorks. Use the copy that loads the program into memory if you will he working for a long session and do not anticipate filling the Desktop. The two minute wait during bootup will be offset by time savings achieved from the program being in memory. Boot the copy that doesn’t load AppleWorks into memory if you will be using the Apple a short while and/or will be working with a full Desktop.
File Size DifferencesAppleWorks shows you the size of tiles on the Desktop and on a disk drive. The file sizes shown are an approximation of the actual sizes.