Changes

Jump to: navigation, search

FutureOS

257 bytes removed, 10:56, 9 August 2006
/* Supporting it all */
== Supporting it all ==
The idea of FutureOS was not only to develop a very fast, easy programmable OS which is able to deal with big files and applications. One point that lead to the development of FutureOS was the wish that it should be possible to support all hardware (ever made for the CPC) with just one OS. Remember, there are 3.5” B-drives, Vortex F1-D-drives, hard-discs, real-time-clocks, serial interfaces and much more. Every piece of hardware has its own software (DOS on Eprom, drivers or whatever). Sadly all these software packages for expansion hardware aren’t compatible under AmsDOS L. FutureOS was designed to work with all known hardware expansions for the CPC. You can use a 3.5” B-drive, external Vortex F1-S or F1-D, a serial interface (or two!), different RAM expansions and maybe a hard-disc (Dobbertin HD20 or CPC-IDE; CPC-IDE since system .9). And all the stuff All that is reported to work properly together.Another point is, that you Most of the low level system resources can program very be accessed freely, e. You g you can use interrupt mode 1 or 2 (standard under FutureOS). If you design Using IM 2 is mandatory when designing expansion hardware, you will love IM 2. A programmer can use almost all Z80-CPU registers. In contrast to all other CPC-OS, which steals the second register set of the Z80regular case, FutureOS allows you to treat all freely use both set of registers like you want (the only exception is the I register, which is used when IM 2 is active). Further you can use all the RST vectors and the Interrupt-Entry at &0038 (IM 1) for your own programs. You like to program that free way? Just assemble your program for start address &0000: own RSTs, own charset, all Z80 registers, expansion-memory usage between &4000-&7FFF. FutureOS programs can be made very mighty and efficient.
== Plug and Play? ==
Anonymous user