StartUp FAQ's
1. How do I configure StartUp to leave after running from Extras bar?
When you usually leave StartUp after launching all entries I suggest to set the set the StartUp properties as follows:
- set global preferences
- select menu option File->Preferences->Global or press Ctrl-K
- press the space bar twice to select page 3 of 4
- check option 'System screen'
- check option 'Extras bar'
- press the space bar to select page 4 of 4
- select 'Yes' for 'Exit after execution on StartUp' (for new files only)
- press Enter to save the changes
- set file preferences (for the current file)
- select menu option File->Preferences->File or press Ctrl-F
- select 'Yes' for 'Exit after execution on StartUp'
- press Enter to save the changes
2. How do I need to configure StartUp combined with ASU?
ASU does not launch a specific StartUp file. Instead ASU launches the StartUp program on drive C: (!) and StartUp itself opens the last accessed StartUp file.
Do as follows to ensure that StartUp is correctly configured for ASU:
- launch StartUp (from Extras bar or the appropriate file from the System screen)
- press 'Esc' to ignore file preferences
- set global preferences
- select menu option File->Preferences->Global or press Ctrl-K
- Press the space bar twice to select page 3 of 4
- check option 'System screen'
- check option 'Extras bar'
- press the space bar to select page 4 of 4
- select 'Yes' for 'Exit after execution on StartUp' (for new files only)
- select 'Yes' for 'Close other files before execution' (for new files only)
- select 'Yes' for 'Exit after execution on StartUp' (for new files only)
- press 'Enter' to save this global preferences
- set file preferences (for the current file)
- choose menu option File->Preferences->File or press Ctrl-F
- select 'Yes' for 'Exit after execution on StartUp' (for the current file only)
- select 'Yes' for 'Close other files before execution' (for the current file only)
- select 'Yes' for 'Exit after execution on StartUp' (for the current file only)
- press 'Enter' to save the preferences of the current file
- exit StartUp to make sure StartUp opens this file when launched via 'Extras bar'
3. I get the message 'Error in StartUp/EXECUTE& 10: Out of memory'. Resolution?
This message usually occurs when the machine runs out of memory - typically when launching too many entries.
Define less entries in your StartUp file and/or run 'Close other files' before launching StartUp entries.
4. I get the message 'Error in StartUp\INSERTRECORD 36: End of file' and cannot insert records into my StartUp file. Resolution?
Several users reported this error running StartUp the first time on a Series 5mx. But unfortunately this error is still not reproducible.
However, the following alternative workarounds are known for this problem:
- Copy a working StartUp file from another EPOC device and replace the faulty StartUp file. This may be a useful approach when you bought a new machine as replacment.
- Delete the faulty StartUp file and create a new StartUp file from the System screen by selecting the menu option File->Create new->File (Ctrl-N). Define a name for your StartUp file and select the program StartUp. The next time you launch StartUp from the Extras bar this file will be opened.
5. I get the message 'Error in StartUp\OPENDB 39: access denied' when launching StartUp. Resolution?
You're using StartUp V2.05 or older. This bug has been fixed in V2.06. Please
upgrade to a newer version.
6. I get the message 'Error in StartUp\OPENDB 66 file is corrupt' when launching StartUp. Resolution?
The StartUp database is corrupt. A 'minor' corruption may be fixed automatically by StartUp, but when you receive this error message you need to
- either delete the corrupt file (and create a new one)
- or restore a working copy from your backup
Reinstalling StartUp does not help, because existing StartUp files won't be deleted.
7. I get the message 'not found' when launching a PowerBase file. Resolution?
You're using StartUp V2.05 or older. This bug has been fixed in V2.06. Please
upgrade to a newer version.