11.8 Special error-messages in MagiC

The alternative operating system MagiC has some error-messages that are not present under normal TOS:

Fatal error while booting
Fatal error in gemdos
Out of internal memory
Memory block destroyed by user program
Fatal error in aes
System stack overflow

When any of these errors occur, they are displayed directly on the screen in capital letters.

11.8.1 Fatal error while booting

Cause:

The system has insufficient memory free for initialisation.
Internal data structures have been destroyed and are therefore in an inconsistent condition.

Remedy: Reinstall system, remove hard disk driver, boot from floppy disk, deactivate AUTO-folder.

11.8.2 Fatal error in gemdos

Cause:

With a Falcon the screen is placed at an invalid address.
During termination of a process the parent is invalid.
With a Falcon Srealloc() cannot be performed.
Internal data structures have been destroyed and are therefore in an inconsistent condition.

Remedy: Depending on circumstances.

11.8.3 Out of internal memory

Cause: The system request to open a file, a directory or a drive partition can not be executed because the internal memory blocks are fully occupied.

Remedy: If the problem does not disappear when one copies ADDMEM two or three times under different names into the AUTO-folder, then the cause is a user program that, for instance, does not close files or folders (missing Fclose or Dclosedir).

11.8.4 Memory block destroyed by user program

Cause: A user program has overwritten an allocated block of memory or a 'foreign' block of memory.

Remedy: The user program can not be used under MagiC. Although it may appear to work under TOS or MultiTOS, its use is risky as the results are indeterminate.

11.8.5 Fatal error in aes

Cause:

Insufficient memory free for starting the AES.
Internal data structures of the AES have been destroyed and are therefore in an inconsistent condition.
An invalid object tree was passed to form_button.
The fixed background memory for menus is insufficient, as a menu has an inadmissible size.
VDI device 1 is invalid.

Remedy: Depending on circumstances.

11.8.6 System stack overflow

Cause: The system stack of a user program has overflowed.

Remedy: Compared to TOS the stack in MagiC 3 is many times larger, so the cause can only be a program running amok or a defective driver (TSR-program or device driver). Remove faulty programs!

MagiC

Scrollable input fields

The background-DMA of MagiC