Changes
removed polemics
== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mices mice and the Dobbertin HD20.
One idea of FutureOS was to support any hardware available. For example there are 3.5" B-drives, Vortex F1-D-drives, hard-discs, real-time-clocks, serial interfaces etc. Hardware expansion usually need drivers, which can be flexible added to an OS. In contrast to this one of the future goals of FutureOS is to provide a monolithik architecture, where all drivers are implemented in a hardcoded way.
== Utilities ==
Tools like copy, format, verify or refresh a disc exist. You can copy files from different discs and partitions to other discs and partitions at once.
=== Machine monitor ===
== Developing for FutureOS ==
Most of the low level hardware resources must be accessed by the application itself, as FutureOS doesn't provide support for them. E.g. FutureOS doesn't include interrupt handling, which means, that you have to write your own handler at #38 or can switch to interrupt mode 2, if you own a special hardware expansion, which allows this mode. Depending on the existance existence and type of your own interrupt handler you may use the second Z80 register set when interrupts are enabled.
=== Z80 Assembler ===
== Conclusion ==
FutureOS was designed as a library with some fast routines, while the application has to access and manage most of the resources of the machine by itself. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of word processors, scientific mathematics, graphics, sound (especially MP3), spreadsheet, management of big amounts of data, bigger games and programming languages should be possible in this environment, though, apart from a MP3 player, none of the examples were written so far during the last 16 years.
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.
