CPCWiki - THE Amstrad CPC encyclopedia! - User contributions [en]

Dobbertin Harddisc

2007-02-20T18:30:10Z

84.151.212.26: /* Other harddisc solutions for the CPC */

[[Image:Dobbertin.gif|thumb|Dobbertin Logo]]

A harddisc manufactured by the German company called [[Dobbertin]].
One of the first ways to connect a Harddisc to the CPC.
The Dobbertin harddisc has a capacity of 20MB.
The disc was partitioned in four partitions of 5152Kb each.
It was delivered with drivers for [[CP/M]](2.2 and CP/M+) and allows up to 512 directory entries for each drive.

Reviewed in [[Amstrad Computer User]].

== Pictures ==
<gallery caption="Dobbertin 20 Mb Harddisc">

Image:Dobbertin 20 Mb Harddisc.JPG|Dobbertin 20 Mb Harddisc
Image:Dobbertin 20 Mb Harddisc interface.JPG|Dobbertin 20 Mb Harddisc interface
Image:Dobbertin 20 Mb Harddisc inside 1.JPG|Inside 1
Image:Dobbertin 20 Mb Harddisc inside 2.JPG|Inside 2
Image:Dobbertin 20 Mb Harddisc inside 3.JPG|Inside 3
Image:Dobbertin 20 Mb Harddisc inside 4.JPG|Inside 4

</gallery>

== Software using the Dobbertin Harddrive ==

[[FutureOS]]

[[X-DDOS]]

== Technical Specifications ==

From the promo:

* Controler: Seagade ST11M XT-controler.

== Other harddisc solutions for the CPC ==

[[Vortex Winchester Drive]] (MFM)

Modern:

[[SYMBiFACE II]] (IDE)

[[CPC-IDE]] (IDE)

[[HDCPC]] (IDE)

== Promo ==
<gallery caption="Dobbertin EPROM 224">
Image:Dobbertin festplatte page1.jpg|Frontpage
Image:Dobbertin festplatte page2.jpg|Contents
</gallery>

[[Category:Hardware]] [[Category:Peripherals]]

Vortex Computersysteme

2007-02-20T18:27:36Z

84.151.212.26: /* Para Plus */

[[Image:Vortex-logo.jpg|thumb|Vortex Logo]]
'''Vortex Computersysteme''' from Neckarsulm, Germany, was a hardware and software manufacturer for the Amstrad CPC. It was founded in 1984 by Mr. Michel and his brother, Mr. Majer and Mrs. Armbruster. Vortex now is called ICP (Intelligent Computer Peripherals) an is an Adaptec Company, specialized in RAID-Controllers.

== F1 ==

A 5.25" disc drive. 80 tracks and 708Kb.

* '''F1 - S''' Single 5.25" drive with controller.
* '''F1 - Z''' Single 5.25" drive without controller.
* '''F1 - D''' Double 5.25" drive with controller.

The disc drive also was available as an extended versions :

* '''F1 - XRS''' which also contains a [[RS232]] interface.
* '''F1 - X''' which can be updated with a [[RS232]] interface.

On the F1-S/D Controllers the Disc operation system [[VDOS]] 1.0 on ROM was included.

On the F1-X/XRS Controllers the Disc operation system [[VDOS]] 2.0 on ROM was included.

Manual can be found here [[F1]]

<gallery caption="The Vortex F1 Drives">

Image:F1-x.jpg|F1-Z Disc Drive
Image:FD1.jpg|F1-D Disc Drive

</gallery>

== M1 ==
A 3.5" disc drive. 80 tracks and 708KB Formatted per Disk.

* '''M1 - S''' Single 3.5" drive with controller.
* '''M1 - Z''' Single 3.5" drive without controller.
* '''M1 - D''' Double 3.5" drive with controller.

The disc drive also was available as an extended version:

* '''M1-XRS''' which also contains a [[RS232]] interface.
* '''M1-X''' which can be updated with a [[RS232]] interface.

On the M1-S/D Controllers the Disc operation system VDOS 1.0 on ROM was included.

On the M1-X/XRS Controllers the Disc operation system VDOS 2.0 on ROM was included.

== The Vortex disc drive controller ==

The Vortex disc controler was similar to Amstrads own controller.
It used the same controler chip, the [[FDC|NEC765]].

<gallery caption="The Vortex Disc Drive Controller">

Image:vortex controler 1.jpg|A anonymous box houses the controller
Image:vortex controler 2.jpg|Look inside the controller
Image:vortex controler 3.jpg|Controller with [[VDOS]] mounted

</gallery>

== SP ==

RAM expansion card. Not compatible to the [[dk'tronics]] memory expansion. Sold in different sizes of RAM as '''SP 64''', '''SP 128''', '''SP 256''', '''SP 320''' and '''SP 512''' (resulting in a maximum RAM size of the computer of 576KiB). Usable under [[BASIC]] and [[CP/M]] and offering a RAM disc.

<gallery caption="The Vortex Expansion RAM card">
Image:sp512top.jpg|The Vortex Expansion RAM card
Image:cpc464bf.jpg|CPC 464 before put the Expansion RAM card
Image:cpc464af.jpg|CPC 464 after put the Expansion RAM card
</gallery>

== Vector ==
A maths program to print functions or to find a function which follows given points. Released 1986.

== Para Plus ==

A program to transfer data [[Vortex Para Plus]]
The Vortex Para Plus is the newer Version of Vortex Para which only works under CP/M 2.2
Para and Para plus can transfer data between different CP/M formats. (Kaypro, Osborne etc..)

== VDOS ==

The disc operating system [[VDOS]] for use with Vortex drives

== Weblinks ==
[http://www.vortex.de Vortex/ICP-Homepage]

[http://www.kjthacker.f2s.com/docs/sp512.html Vortex SP512 RAM Card]

[[Category:Peripherals]] [[Category:CPC related companies]]

Vortex Computersysteme

2007-02-20T18:27:21Z

84.151.212.26: /* Para Plus */

[[Image:Vortex-logo.jpg|thumb|Vortex Logo]]
'''Vortex Computersysteme''' from Neckarsulm, Germany, was a hardware and software manufacturer for the Amstrad CPC. It was founded in 1984 by Mr. Michel and his brother, Mr. Majer and Mrs. Armbruster. Vortex now is called ICP (Intelligent Computer Peripherals) an is an Adaptec Company, specialized in RAID-Controllers.

== F1 ==

A 5.25" disc drive. 80 tracks and 708Kb.

* '''F1 - S''' Single 5.25" drive with controller.
* '''F1 - Z''' Single 5.25" drive without controller.
* '''F1 - D''' Double 5.25" drive with controller.

The disc drive also was available as an extended versions :

* '''F1 - XRS''' which also contains a [[RS232]] interface.
* '''F1 - X''' which can be updated with a [[RS232]] interface.

On the F1-S/D Controllers the Disc operation system [[VDOS]] 1.0 on ROM was included.

On the F1-X/XRS Controllers the Disc operation system [[VDOS]] 2.0 on ROM was included.

Manual can be found here [[F1]]

<gallery caption="The Vortex F1 Drives">

Image:F1-x.jpg|F1-Z Disc Drive
Image:FD1.jpg|F1-D Disc Drive

</gallery>

== M1 ==
A 3.5" disc drive. 80 tracks and 708KB Formatted per Disk.

* '''M1 - S''' Single 3.5" drive with controller.
* '''M1 - Z''' Single 3.5" drive without controller.
* '''M1 - D''' Double 3.5" drive with controller.

The disc drive also was available as an extended version:

* '''M1-XRS''' which also contains a [[RS232]] interface.
* '''M1-X''' which can be updated with a [[RS232]] interface.

On the M1-S/D Controllers the Disc operation system VDOS 1.0 on ROM was included.

On the M1-X/XRS Controllers the Disc operation system VDOS 2.0 on ROM was included.

== The Vortex disc drive controller ==

The Vortex disc controler was similar to Amstrads own controller.
It used the same controler chip, the [[FDC|NEC765]].

<gallery caption="The Vortex Disc Drive Controller">

Image:vortex controler 1.jpg|A anonymous box houses the controller
Image:vortex controler 2.jpg|Look inside the controller
Image:vortex controler 3.jpg|Controller with [[VDOS]] mounted

</gallery>

== SP ==

RAM expansion card. Not compatible to the [[dk'tronics]] memory expansion. Sold in different sizes of RAM as '''SP 64''', '''SP 128''', '''SP 256''', '''SP 320''' and '''SP 512''' (resulting in a maximum RAM size of the computer of 576KiB). Usable under [[BASIC]] and [[CP/M]] and offering a RAM disc.

<gallery caption="The Vortex Expansion RAM card">
Image:sp512top.jpg|The Vortex Expansion RAM card
Image:cpc464bf.jpg|CPC 464 before put the Expansion RAM card
Image:cpc464af.jpg|CPC 464 after put the Expansion RAM card
</gallery>

== Vector ==
A maths program to print functions or to find a function which follows given points. Released 1986.

== Para Plus ==

A program to transfer data [[Vortex Para Plus]]
The Vortex Para Plus is the newer Version of Vortex Para which only works under CP/M 2.2
Para and Para plus can transfer data between diffrent CP/M formats. (Kaypro, Osborne etc..)

== VDOS ==

The disc operating system [[VDOS]] for use with Vortex drives

== Weblinks ==
[http://www.vortex.de Vortex/ICP-Homepage]

[http://www.kjthacker.f2s.com/docs/sp512.html Vortex SP512 RAM Card]

[[Category:Peripherals]] [[Category:CPC related companies]]

Vortex Computersysteme

2007-02-20T18:25:03Z

84.151.212.26: /* M1 */

[[Image:Vortex-logo.jpg|thumb|Vortex Logo]]
'''Vortex Computersysteme''' from Neckarsulm, Germany, was a hardware and software manufacturer for the Amstrad CPC. It was founded in 1984 by Mr. Michel and his brother, Mr. Majer and Mrs. Armbruster. Vortex now is called ICP (Intelligent Computer Peripherals) an is an Adaptec Company, specialized in RAID-Controllers.

== F1 ==

A 5.25" disc drive. 80 tracks and 708Kb.

* '''F1 - S''' Single 5.25" drive with controller.
* '''F1 - Z''' Single 5.25" drive without controller.
* '''F1 - D''' Double 5.25" drive with controller.

The disc drive also was available as an extended versions :

* '''F1 - XRS''' which also contains a [[RS232]] interface.
* '''F1 - X''' which can be updated with a [[RS232]] interface.

On the F1-S/D Controllers the Disc operation system [[VDOS]] 1.0 on ROM was included.

On the F1-X/XRS Controllers the Disc operation system [[VDOS]] 2.0 on ROM was included.

Manual can be found here [[F1]]

<gallery caption="The Vortex F1 Drives">

Image:F1-x.jpg|F1-Z Disc Drive
Image:FD1.jpg|F1-D Disc Drive

</gallery>

== M1 ==
A 3.5" disc drive. 80 tracks and 708KB Formatted per Disk.

* '''M1 - S''' Single 3.5" drive with controller.
* '''M1 - Z''' Single 3.5" drive without controller.
* '''M1 - D''' Double 3.5" drive with controller.

The disc drive also was available as an extended version:

* '''M1-XRS''' which also contains a [[RS232]] interface.
* '''M1-X''' which can be updated with a [[RS232]] interface.

On the M1-S/D Controllers the Disc operation system VDOS 1.0 on ROM was included.

On the M1-X/XRS Controllers the Disc operation system VDOS 2.0 on ROM was included.

== The Vortex disc drive controller ==

The Vortex disc controler was similar to Amstrads own controller.
It used the same controler chip, the [[FDC|NEC765]].

<gallery caption="The Vortex Disc Drive Controller">

Image:vortex controler 1.jpg|A anonymous box houses the controller
Image:vortex controler 2.jpg|Look inside the controller
Image:vortex controler 3.jpg|Controller with [[VDOS]] mounted

</gallery>

== SP ==

RAM expansion card. Not compatible to the [[dk'tronics]] memory expansion. Sold in different sizes of RAM as '''SP 64''', '''SP 128''', '''SP 256''', '''SP 320''' and '''SP 512''' (resulting in a maximum RAM size of the computer of 576KiB). Usable under [[BASIC]] and [[CP/M]] and offering a RAM disc.

<gallery caption="The Vortex Expansion RAM card">
Image:sp512top.jpg|The Vortex Expansion RAM card
Image:cpc464bf.jpg|CPC 464 before put the Expansion RAM card
Image:cpc464af.jpg|CPC 464 after put the Expansion RAM card
</gallery>

== Vector ==
A maths program to print functions or to find a function which follows given points. Released 1986.

== Para Plus ==

A program to transfer data [[Vortex Para Plus]]

== VDOS ==

The disc operating system [[VDOS]] for use with Vortex drives

== Weblinks ==
[http://www.vortex.de Vortex/ICP-Homepage]

[http://www.kjthacker.f2s.com/docs/sp512.html Vortex SP512 RAM Card]

[[Category:Peripherals]] [[Category:CPC related companies]]

Vortex Computersysteme

2007-02-20T18:24:17Z

84.151.212.26: /* F1 */

[[Image:Vortex-logo.jpg|thumb|Vortex Logo]]
'''Vortex Computersysteme''' from Neckarsulm, Germany, was a hardware and software manufacturer for the Amstrad CPC. It was founded in 1984 by Mr. Michel and his brother, Mr. Majer and Mrs. Armbruster. Vortex now is called ICP (Intelligent Computer Peripherals) an is an Adaptec Company, specialized in RAID-Controllers.

== F1 ==

A 5.25" disc drive. 80 tracks and 708Kb.

* '''F1 - S''' Single 5.25" drive with controller.
* '''F1 - Z''' Single 5.25" drive without controller.
* '''F1 - D''' Double 5.25" drive with controller.

The disc drive also was available as an extended versions :

* '''F1 - XRS''' which also contains a [[RS232]] interface.
* '''F1 - X''' which can be updated with a [[RS232]] interface.

On the F1-S/D Controllers the Disc operation system [[VDOS]] 1.0 on ROM was included.

On the F1-X/XRS Controllers the Disc operation system [[VDOS]] 2.0 on ROM was included.

Manual can be found here [[F1]]

<gallery caption="The Vortex F1 Drives">

Image:F1-x.jpg|F1-Z Disc Drive
Image:FD1.jpg|F1-D Disc Drive

</gallery>

== M1 ==
A 3.5" disc drive. 80 tracks and 708KB Formatted per Disk.

* '''M1 - S''' Single 3.5" drive with controller.
* '''M1 - Z''' Single 3.5" drive without controller.
* '''M1 - D''' Double 3.5" drive with controller.

The disc drive also was available as an extended version:

* '''M1-XRS''' which also contains a [[RS232]] interface.
* '''M1-X''' which can be updated with a [[RS232]] interface.

Disc operation system [[VDOS]] 2.0 on ROM included.

== The Vortex disc drive controller ==

The Vortex disc controler was similar to Amstrads own controller.
It used the same controler chip, the [[FDC|NEC765]].

<gallery caption="The Vortex Disc Drive Controller">

Image:vortex controler 1.jpg|A anonymous box houses the controller
Image:vortex controler 2.jpg|Look inside the controller
Image:vortex controler 3.jpg|Controller with [[VDOS]] mounted

</gallery>

== SP ==

RAM expansion card. Not compatible to the [[dk'tronics]] memory expansion. Sold in different sizes of RAM as '''SP 64''', '''SP 128''', '''SP 256''', '''SP 320''' and '''SP 512''' (resulting in a maximum RAM size of the computer of 576KiB). Usable under [[BASIC]] and [[CP/M]] and offering a RAM disc.

<gallery caption="The Vortex Expansion RAM card">
Image:sp512top.jpg|The Vortex Expansion RAM card
Image:cpc464bf.jpg|CPC 464 before put the Expansion RAM card
Image:cpc464af.jpg|CPC 464 after put the Expansion RAM card
</gallery>

== Vector ==
A maths program to print functions or to find a function which follows given points. Released 1986.

== Para Plus ==

A program to transfer data [[Vortex Para Plus]]

== VDOS ==

The disc operating system [[VDOS]] for use with Vortex drives

== Weblinks ==
[http://www.vortex.de Vortex/ICP-Homepage]

[http://www.kjthacker.f2s.com/docs/sp512.html Vortex SP512 RAM Card]

[[Category:Peripherals]] [[Category:CPC related companies]]

Vortex Computersysteme

2007-02-20T18:22:55Z

84.151.212.26: /* F1 */

[[Image:Vortex-logo.jpg|thumb|Vortex Logo]]
'''Vortex Computersysteme''' from Neckarsulm, Germany, was a hardware and software manufacturer for the Amstrad CPC. It was founded in 1984 by Mr. Michel and his brother, Mr. Majer and Mrs. Armbruster. Vortex now is called ICP (Intelligent Computer Peripherals) an is an Adaptec Company, specialized in RAID-Controllers.

== F1 ==

A 5.25" disc drive. 80 tracks and 708Kb.

* '''F1 - S''' Single 5.25" drive with controller.
* '''F1 - Z''' Single 5.25" drive without controller.
* '''F1 - D''' Double 5.25" drive with controller.

The disc drive also was available as an extended versions :

* '''F1 - XRS''' which also contains a [[RS232]] interface.
* '''F1 - X''' which can be updated with a [[RS232]] interface.

On the F1-S/D Controllers the Disc operation system [[VDOS]] 1.0 on ROM was included.
On the F1-X/XRS Controllers the Disc operation system [[VDOS]] 2.0 on ROM was included.

Manual can be found here [[F1]]

<gallery caption="The Vortex F1 Drives">

Image:F1-x.jpg|F1-Z Disc Drive
Image:FD1.jpg|F1-D Disc Drive

</gallery>

== M1 ==
A 3.5" disc drive. 80 tracks and 708KB Formatted per Disk.

* '''M1 - S''' Single 3.5" drive with controller.
* '''M1 - Z''' Single 3.5" drive without controller.
* '''M1 - D''' Double 3.5" drive with controller.

The disc drive also was available as an extended version:

* '''M1-XRS''' which also contains a [[RS232]] interface.
* '''M1-X''' which can be updated with a [[RS232]] interface.

Disc operation system [[VDOS]] 2.0 on ROM included.

== The Vortex disc drive controller ==

The Vortex disc controler was similar to Amstrads own controller.
It used the same controler chip, the [[FDC|NEC765]].

<gallery caption="The Vortex Disc Drive Controller">

Image:vortex controler 1.jpg|A anonymous box houses the controller
Image:vortex controler 2.jpg|Look inside the controller
Image:vortex controler 3.jpg|Controller with [[VDOS]] mounted

</gallery>

== SP ==

RAM expansion card. Not compatible to the [[dk'tronics]] memory expansion. Sold in different sizes of RAM as '''SP 64''', '''SP 128''', '''SP 256''', '''SP 320''' and '''SP 512''' (resulting in a maximum RAM size of the computer of 576KiB). Usable under [[BASIC]] and [[CP/M]] and offering a RAM disc.

<gallery caption="The Vortex Expansion RAM card">
Image:sp512top.jpg|The Vortex Expansion RAM card
Image:cpc464bf.jpg|CPC 464 before put the Expansion RAM card
Image:cpc464af.jpg|CPC 464 after put the Expansion RAM card
</gallery>

== Vector ==
A maths program to print functions or to find a function which follows given points. Released 1986.

== Para Plus ==

A program to transfer data [[Vortex Para Plus]]

== VDOS ==

The disc operating system [[VDOS]] for use with Vortex drives

== Weblinks ==
[http://www.vortex.de Vortex/ICP-Homepage]

[http://www.kjthacker.f2s.com/docs/sp512.html Vortex SP512 RAM Card]

[[Category:Peripherals]] [[Category:CPC related companies]]

Vortex Computersysteme

2007-02-20T18:20:00Z

84.151.212.26: /* M1 */

[[Image:Vortex-logo.jpg|thumb|Vortex Logo]]
'''Vortex Computersysteme''' from Neckarsulm, Germany, was a hardware and software manufacturer for the Amstrad CPC. It was founded in 1984 by Mr. Michel and his brother, Mr. Majer and Mrs. Armbruster. Vortex now is called ICP (Intelligent Computer Peripherals) an is an Adaptec Company, specialized in RAID-Controllers.

== F1 ==

A 5.25" disc drive. 80 tracks and 708Kb.

* '''F1 - S''' Single 5.25" drive with controller.
* '''F1 - Z''' Single 5.25" drive without controller.
* '''F1 - D''' Double 5.25" drive with controller.

The disc drive also was available as an extended versions :

* '''F1 - XRS''' which also contains a [[RS232]] interface.
* '''F1 - X''' which can be updated with a [[RS232]] interface.

Disc operation system [[VDOS]] 2.0 on ROM included.

Manual can be found here [[F1]]

<gallery caption="The Vortex F1 Drives">

Image:F1-x.jpg|F1-Z Disc Drive
Image:FD1.jpg|F1-D Disc Drive

</gallery>

== M1 ==
A 3.5" disc drive. 80 tracks and 708KB Formatted per Disk.

* '''M1 - S''' Single 3.5" drive with controller.
* '''M1 - Z''' Single 3.5" drive without controller.
* '''M1 - D''' Double 3.5" drive with controller.

The disc drive also was available as an extended version:

* '''M1-XRS''' which also contains a [[RS232]] interface.
* '''M1-X''' which can be updated with a [[RS232]] interface.

Disc operation system [[VDOS]] 2.0 on ROM included.

== The Vortex disc drive controller ==

The Vortex disc controler was similar to Amstrads own controller.
It used the same controler chip, the [[FDC|NEC765]].

<gallery caption="The Vortex Disc Drive Controller">

Image:vortex controler 1.jpg|A anonymous box houses the controller
Image:vortex controler 2.jpg|Look inside the controller
Image:vortex controler 3.jpg|Controller with [[VDOS]] mounted

</gallery>

== SP ==

RAM expansion card. Not compatible to the [[dk'tronics]] memory expansion. Sold in different sizes of RAM as '''SP 64''', '''SP 128''', '''SP 256''', '''SP 320''' and '''SP 512''' (resulting in a maximum RAM size of the computer of 576KiB). Usable under [[BASIC]] and [[CP/M]] and offering a RAM disc.

<gallery caption="The Vortex Expansion RAM card">
Image:sp512top.jpg|The Vortex Expansion RAM card
Image:cpc464bf.jpg|CPC 464 before put the Expansion RAM card
Image:cpc464af.jpg|CPC 464 after put the Expansion RAM card
</gallery>

== Vector ==
A maths program to print functions or to find a function which follows given points. Released 1986.

== Para Plus ==

A program to transfer data [[Vortex Para Plus]]

== VDOS ==

The disc operating system [[VDOS]] for use with Vortex drives

== Weblinks ==
[http://www.vortex.de Vortex/ICP-Homepage]

[http://www.kjthacker.f2s.com/docs/sp512.html Vortex SP512 RAM Card]

[[Category:Peripherals]] [[Category:CPC related companies]]

SYMBiFACE II

2006-10-26T22:24:28Z

84.151.225.150: TFM was also a member of the team. Thanks to him the CPC-IDE (and the Symbiface too) gets a I/O address, which doesn't interfere with other hardware.

== Introduction ==

[[Image:Cpc-ide.jpg|200px|thumb|Prototype of the CPC-IDE interface]]

In autumn 2004 the "CPC-IDE" was developed by [[Dr.Zed]] with the support of [[Octoate]], [[TFM]] and [[Tolkin]]. It is the first hardware solution ever that allowed connection of IDE-harddrives and CF-cards to the CPC with the maximum possible data transfer speed. Technically the CPC-IDE interface was based on the GIDE IDE interface by Tilmann Reh.

It was fully working, but still had a prototype state, so only 10 pieces have been produced. Some people should write software first, before the final version would be released. So fully IDE-support for [[Disc_format|FAT]]16 and FAT32 harddiscs has been implemented in [[SymbOS]] until Xmas 2004.

After working successfully, [[Dr.Zed]] and [[Prodatron]] made plans for a second version, which includes a lot of more extensions. So the '''SYMBiFACE II''' is not only an IDE interface anymore. It merges the CPC with current PC technology.

== Features ==

[[Image:Symbiface2.gif|400px|thumb|SYMBiFACE II with description]]

CPC SYMBiFACE II contains the optimal solution for connecting a CPC with an IDE harddisc. It provides the maximum - both for the performance and for the simpleness in accessing the harddisc.

''IDE Features''

* Supports IDE-Harddiscs with up to 128GB
* Bigger HDDs or CD/DVD drives support possible with drivers
* Simultaneous operation of two harddiscs (master and slave):for a total of up to 256GB on your CPC!
* Transfer speed of 162KByte/s: That's as fast as copying memory inside the CPC with LDIR. In practice (loading FAT16/32 files) the speed is still about 130KB/s ([[SymbOS]]-FAT-driver).
* External power supply required: no extra load for the CPC's internal PSU
* No timing problems: Interrupts don't need to be disabled during the data transfer with the harddisc. The harddisc can operate while you play sound or doing other things with your CPC (multitasking etc.).
* Traffic activity display via a LED on the board

'' Additional Features''

* 512KB RAM extension, which is fully compatible with the CPC [[6128]] and the [[dk'tronics]] ram extension
* 512KB rewriteable ROM. You can upload up to 32 ROMs, which are persistant. You can also use the ROM space as an additional RAM extension. ROMs can be switched on or off via switches or via software.
* PS/2 mouse connector. This makes it possible to connect wireless and optical mouses to your CPC.
* Realtime clock, which is fully PC compatible and provides additional 128 byte persistant RAM, which can be used to store config data.

== Rom-Manager ==

[[Image:sf2romman.gif|thumb|320px|SYMBiFACE II rom manager]]

SYMBiFACE II includes a rom manager software, which runs under [[SymbOS]]. This tool is needed for displaying, loading, saving and deleting of the 32 x 16K ROMs.

* There is a preview of a software with the same name available for [[FutureOS]]. It allows the complete backup and restoration of all 32 ROMs and loading, saving, testing, copying, shifting, erasing and (un)parking single ROMs. "[[ROManager]]" supports the languages German, English, French and Spanish.

== See also ==

* [[Programming:SYMBiFACE II|SYMBiFACE II documents]]
* [http://www.symbos.de/sf2.htm SYMBiFACE II homepage]

[[Category:Hardware]] [[Category:Peripherals]] [[Category:SymbOS]] [[Category:Memory expansions]]

System software

2006-10-22T19:36:36Z

84.151.244.108: alphabetically ordered

== Disc operating systems ==

* [[400K/S]] ([[SD Microsystems]])
* [[AMSDOS]] ([[Amstrad]])
* [[AMSDOS#BASDOS|BASDOS]]
* [[MagicDOS]] ([[Logon System]])
* [[MS800]] ([[Microstyle]])
* [[ParaDOS]] ([[Quantum Computing]])
* [[RODOS]] ([[Romantic Robot]])
* [[ROMDOS]] and [[RAMDOS]] ([[KDS]]/[[Siren Software]])
* [[S-DOS]] ([[STS]])
* [[SymDOS]] ([[Flynn]])
* [[Vortex Computersysteme|VDOS]] ([[Vortex Computersysteme]])

== Graphical user interfaces / Shells ==

* [[CEUS Desktop 2.0]] ([[Prodatron]])
* [[Desk-Royal]] ([[Crusader Software]])
* [[Desktop]] ([[DW Software]])
* [[Desktop Environment System|DES]] (Desktop Environment System) ([[Campursoft]])
* [[GENO]] ([[GHE]])
* [[Max]] (Advanced Memory Systems)
* [[Mouse Operating System (M.O.S.)]] ([[Star-Division]]) (1987)
* [[SI-BOF]] ([[Bad Error]]) (1992)
* [[Stream2]] ([[Advanced Software Project]])

== Operating Systems ==

* [[Contiki]]
* [[CPC OS]]
* [[CP/M 2.2]]
* [[CP/M 3.1]]
* [[FutureOS]] ([[TFM]] / [[FutureSoft]])
* [[MicroDOS]]
* [[SymbOS]] ([[Prodatron]] / [[SymbiosiS]])

SYMBiFACE II

2006-10-22T19:28:02Z

84.151.244.108: /* Introduction */

== Introduction ==

[[Image:Cpc-ide.jpg|200px|thumb|Prototype of the CPC-IDE interface]]

In autumn 2004 the CPC-IDE was developed by [[Dr.Zed]] with the support of [[Octoate]], [[TFM]] and [[Tolkin]]. It is the first hardware solution ever that allowed connection of IDE-harddrives and CF-cards to the CPC with the maximum possible data transfer speed. Technically the CPC-IDE interface was based on the GIDE IDE interface by Tilmann Reh.

It was fully working, but still had a prototype state, so only 10 pieces have been produced. Some people should write software first, before the final version would be released. So fully IDE-support for FAT16 and FAT32 harddiscs has been implemented in [[SymbOS]] until Xmas 2004.

With all this, CPC SYMBiFACE II is not only an IDE interface anymore. It merges the CPC with current PC technology.

== Features ==

[[Image:Symbiface2.gif|400px|thumb|SYMBiFACE II with description]]

CPC SYMBiFACE II contains the optimal solution for connecting a CPC with an IDE harddisc. It provides the maximum - both for the performance and for the simpleness in accessing the harddisc.

''IDE Features''

* Supports IDE-Harddiscs with up to 128GB
* Bigger HDDs or CD/DVD drives support possible with drivers
* Simultaneous operation of two harddiscs (master and slave):for a total of up to 256GB on your CPC!
* Transfer speed of 162KByte/s: That's as fast as copying memory inside the CPC with LDIR. In practice (loading FAT16/32 files) the speed is still about 130KB/s ([[SymbOS]]-FAT-driver).
* External power supply required: no extra load for the CPC's internal PSU
* No timing problems: Interrupts don't need to be disabled during the data transfer with the harddisc. The harddisc can operate while you play sound or doing other things with your CPC (multitasking etc.).
* Traffic activity display via a LED on the board

'' Additional Features''

* 512KB RAM extension, which is fully compatible with the CPC [[6128]] and the [[dk'tronics]] ram extension
* 512KB rewriteable ROM. You can upload up to 32 ROMs, which are persistant. You can also use the ROM space as an additional RAM extension. ROMs can be switched on or off via switches or via software.
* PS/2 mouse connector. This makes it possible to connect wireless and optical mouses to your CPC.
* Realtime clock, which is fully PC compatible and provides additional 128 byte persistant RAM, which can be used to store config data.

== Rom-Manager ==

[[Image:sf2romman.gif|thumb|320px|SYMBiFACE II rom manager]]

SYMBiFACE II includes a rom manager software, which runs under [[SymbOS]]. This tool is needed for displaying, loading, saving and deleting of the 32 x 16K ROMs.

== ROManager ==
There is a second (Pseudo-)ROM manager which alows the complete backup (and restoration) of all 32 ROMs. You can load, save, test, copy, shift, erase, park and unpark single ROMs. This [[ROManager]] runs under [[FutureOS]]. Its language interface supports German, English, French and Spanish.

== See also ==

* [[Programming:SYMBiFACE II|SYMBiFACE II documents]]
* [http://www.symbos.de/sf2.htm SYMBiFACE II homepage]

[[Category:Hardware]] [[Category:Peripherals]] [[Category:SymbOS]] [[Category:Memory expansions]]

SYMBiFACE II

2006-10-19T18:53:08Z

84.151.205.223: /* Rom-Manager */

== Introduction ==

[[Image:Cpc-ide.jpg|200px|thumb|Prototype of the CPC-IDE interface]]

In autumn 2004 the first CPC SYMBiFACE (also known as "CPC-IDE") was developed by [[Dr.Zed]] with the support of [[Octoate]], [[TFM]] and [[Tolkin]]. It was the first hardware solution ever that allowed connection of IDE-harddrives and CF-cards to the CPC with the maximum possible data transfer speed. Technically the CPC-IDE interface was based on the GIDE IDE interface by Tilmann Reh.

It was fully working, but still had a prototype state, so only 10 pieces have been produced. Some people should write software first, before the final version would be released. So fully IDE-support for FAT16 and FAT32 harddiscs has been implemented in [[SymbOS]] until Xmas 2004.

With all this, CPC SYMBiFACE II is not only an IDE interface anymore. It merges the CPC with current PC technology.

== Features ==

[[Image:Symbiface2.gif|400px|thumb|SYMBiFACE II with description]]

CPC SYMBiFACE II contains the optimal solution for connecting a CPC with an IDE harddisc. It provides the maximum - both for the performance and for the simpleness in accessing the harddisc.

''IDE Features''

* Supports IDE-Harddiscs with up to 128GB
* Bigger HDDs or CD/DVD drives support possible with drivers
* Simultaneous operation of two harddiscs (master and slave):for a total of up to 256GB on your CPC!
* Transfer speed of 162KByte/s: That's as fast as copying memory inside the CPC with LDIR. In practice (loading FAT16/32 files) the speed is still about 130KB/s ([[SymbOS]]-FAT-driver).
* External power supply required: no extra load for the CPC's internal PSU
* No timing problems: Interrupts don't need to be disabled during the data transfer with the harddisc. The harddisc can operate while you play sound or doing other things with your CPC (multitasking etc.).
* Traffic activity display via a LED on the board

'' Additional Features''

* 512KB RAM extension, which is fully compatible with the CPC [[6128]] and the [[dk'tronics]] ram extension
* 512KB rewriteable ROM. You can upload up to 32 ROMs, which are persistant. You can also use the ROM space as an additional RAM extension. ROMs can be switched on or off via switches or via software.
* PS/2 mouse connector. This makes it possible to connect wireless and optical mouses to your CPC.
* Realtime clock, which is fully PC compatible and provides additional 128 byte persistant RAM, which can be used to store config data.

== Rom-Manager ==

[[Image:sf2romman.gif|thumb|320px|SYMBiFACE II rom manager]]

SYMBiFACE II includes a rom manager software, which runs under [[SymbOS]]. This tool is needed for displaying, loading, saving and deleting of the 32 x 16K ROMs.

== ROManager ==
There is a second (Pseudo-)ROM manager which alows the complete backup (and restoration) of all 32 ROMs. You can load, save, test, copy, shift, erase, park and unpark single ROMs. This [[ROManager]] runs under [[FutureOS]]. Its language interface supports German, English, French and Spanish.

== See also ==

* [[Programming:SYMBiFACE II|SYMBiFACE II documents]]
* [http://www.symbos.de/sf2.htm SYMBiFACE II homepage]

[[Category:Hardware]] [[Category:Peripherals]] [[Category:SymbOS]] [[Category:Memory expansions]]

SYMBiFACE II

2006-10-19T18:47:45Z

84.151.205.223: /* Introduction */

== Introduction ==

[[Image:Cpc-ide.jpg|200px|thumb|Prototype of the CPC-IDE interface]]

In autumn 2004 the first CPC SYMBiFACE (also known as "CPC-IDE") was developed by [[Dr.Zed]] with the support of [[Octoate]], [[TFM]] and [[Tolkin]]. It was the first hardware solution ever that allowed connection of IDE-harddrives and CF-cards to the CPC with the maximum possible data transfer speed. Technically the CPC-IDE interface was based on the GIDE IDE interface by Tilmann Reh.

It was fully working, but still had a prototype state, so only 10 pieces have been produced. Some people should write software first, before the final version would be released. So fully IDE-support for FAT16 and FAT32 harddiscs has been implemented in [[SymbOS]] until Xmas 2004.

With all this, CPC SYMBiFACE II is not only an IDE interface anymore. It merges the CPC with current PC technology.

== Features ==

[[Image:Symbiface2.gif|400px|thumb|SYMBiFACE II with description]]

CPC SYMBiFACE II contains the optimal solution for connecting a CPC with an IDE harddisc. It provides the maximum - both for the performance and for the simpleness in accessing the harddisc.

''IDE Features''

* Supports IDE-Harddiscs with up to 128GB
* Bigger HDDs or CD/DVD drives support possible with drivers
* Simultaneous operation of two harddiscs (master and slave):for a total of up to 256GB on your CPC!
* Transfer speed of 162KByte/s: That's as fast as copying memory inside the CPC with LDIR. In practice (loading FAT16/32 files) the speed is still about 130KB/s ([[SymbOS]]-FAT-driver).
* External power supply required: no extra load for the CPC's internal PSU
* No timing problems: Interrupts don't need to be disabled during the data transfer with the harddisc. The harddisc can operate while you play sound or doing other things with your CPC (multitasking etc.).
* Traffic activity display via a LED on the board

'' Additional Features''

* 512KB RAM extension, which is fully compatible with the CPC [[6128]] and the [[dk'tronics]] ram extension
* 512KB rewriteable ROM. You can upload up to 32 ROMs, which are persistant. You can also use the ROM space as an additional RAM extension. ROMs can be switched on or off via switches or via software.
* PS/2 mouse connector. This makes it possible to connect wireless and optical mouses to your CPC.
* Realtime clock, which is fully PC compatible and provides additional 128 byte persistant RAM, which can be used to store config data.

== Rom-Manager ==

[[Image:sf2romman.gif|thumb|320px|SYMBiFACE II rom manager]]

SYMBiFACE II includes a rom manager software, which runs under [[SymbOS]]. This tool is needed for displaying, loading, saving and deleting of the 32 x 16K ROMs.

== See also ==

* [[Programming:SYMBiFACE II|SYMBiFACE II documents]]
* [http://www.symbos.de/sf2.htm SYMBiFACE II homepage]

[[Category:Hardware]] [[Category:Peripherals]] [[Category:SymbOS]] [[Category:Memory expansions]]

Demogroups

2006-10-19T14:57:46Z

84.151.205.223: /* Germany */

''For on overview of the CPC scene members, you can have a look at the''
* [[CPC scene members|List of CPC scene members]]
* [http://www.cpcwiki.eu/index.php/Category:CPC_scene_members Category of CPC scene members]

''You can also check the [http://www.cpcwiki.eu/index.php/Category:Demos Demos category] for productions/releases.''

This is a list of the CPC scene '''demo groups''', which have been or are still active.

== France ==

* [[5KB]]
* [[Arkos]] ([http://www.arkos.cpcscene.com Arkos homepage])
* [[AST System]]
* [[BCAV]]
* [[Contrast]]
* [[Da Boxon Team]]
* [[Fefesse]]
* [[Futur's]] ([http://www.futurs.cpcscene.com Futur's homepage])
* [[GPA]] ([http://tj.gpa.free.fr Tom et Jerry's homepage])
* [[Hard'OS]] ([http://bdciron.cpcscene.com BDC Iron's homepage])
* [http://oppressed-people.info/impact Impact]
* [http://oppressed-people.info/impact/index.php?option=com_mamblog&Itemid=20 Kill or die]
* [[Krad'os Crack'ers]]
* [[Logon System]] ([http://sergio.web.9online.fr/html/demologon.htm Longshot's website])
* [[Malibu Crackers]]
* [[Mortel]]
* [[Nul Part System]] ([http://nulpartsystem.free.fr NPS homepage])
* [[Overlanders]]
* [[Paradox]]
* [[Rebels]]
* [[Revival]]
* [[Les Sucres en Morceaux]] ([http://scampin.chez-alice.fr/cpc Sucres en Morceaux homepage])
* [[Static]]
* [[The Addams Fanz]] ([http://tafcpc.free.fr TAF homepage])

== Germany ==

* [[ALC]]
* [[Armaxess]]
* [[BENG!]] (also international)
* [[Benediction]]
* [[Bollaware]]
* [[Cadjo Clan]]
* [[CBS]]
* [[CGS]]
* [[Commotion]]
* [[CRT]]
* [[Exodus]]
* [[Frankenteam]]
* [[FutureSoft]]
* [[GCS]]
* [[GOS]]
* [[HJT]]
* [[Inicron]]
* [[KKB]]
* [[Merlyn]]
* [[MOPS]]
* [[Necron]]
* [[PDW]]
* [[POW]]
* [[The Rejects]]
* [[SCUG]]
* [[SymbiosiS]]
* [[TGS]]
* [[TTC]]
* [[Wizcat]]

== Greece ==

* [[Dirty Minds]]

== Ireland ==

* [[The Firm]]

== Netherlands ==

* [[Dragonbreed Wetware]]

== Spain ==

* [[Zona Neutra]] ([http://www.zonan.org Zona Neutra website])

== United Kingdom ==

* [[Bitmap Vandals]]
* [[Conspiracy]]
* [[Discovery]]
* [[Donut System]]
* [[Lords of Justice]]
* [[STS]]
* [[Systeme D]]
* [[The Underground]]

and many, many more...

[[Category:Scene group|*]]

Talk:FutureOS

2006-10-17T21:27:33Z

84.151.235.113: /* Flaming */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it? (Forgott to sign.. sorry.. but as i don't fear anything... here i am... [[User:Kangaroo|Kangaroo MusiQue of HJT]] 07:59, 28 August 2006 (CEST)

:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function is. read the manual, the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

:::RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

:::Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

:::Greets
:::TFM

::::Can we please stop hiding behind our finger? We all know what RTFM means, so please drop it. I assume almost everyone here is of at least average IQ... As I said, this languages is NOT permitted on board. What's more, what do you mean about that guy being allowed to vandalise your text? What did he vandalise? What should I stop? I think there might be a big misunderstanding here... Anyhow, about the SIdebar, I don't think it's 'very unfair', as I've explained before. FutureOS may be indeed very, very nice a project and I find myself playing with it the whole time, but SymbOS, with the existing Symbiface, has long ago reached critical mass and is very impressive and popular, that's why it had its own link. This is NOT an issue of 'put my project up there along with the others', it's trying to organise things in a better way. In any case, the Sidebar was changed a lot, I'm going to look into it... [[User:Gryzor|Gryzor]] 08:16, 11 August 2006 (CEST)

:That's something, which came to my mind very often! We should change the "SymbOS" link in the left menu to "Operating Systems". Then we can have a list of OSs for the CPC there. It would be a better entry point! --[[User:Octoate|Octoate]] 20:40, 10 August 2006 (CEST)

::Hm, I don't know. In this case you have to place all categories from the "serious software" articel in the sidebar. -- [[User:Prodatron|Prodatron]] 21:00, 10 August 2006 (CEST)

:::Argh... ;) --[[User:Octoate|Octoate]] 21:24, 10 August 2006 (CEST)

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

The maximum file-size depends on the free space on disc-hard-disc or it is limited by a 24 Bit file-length code. Just look at the manual. You can use routines like TEILA or TEISI to load or save files greater then 576 KB. TFM

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

Thank you for your excellent help. TFM

== Protection ==

This part of the discussion has been deleted; please do not roll back.

The reason I deleted it is because it turned into a flame, and also because some people do not understand how to format their edits by using semi-colons to keep the thread flow easy to understand. As a result it was a flame that was very hard to follow. I will just keep the following:

The article will remain locked for the time being. It's really unfortunate that events are taking such a turn, at a time when the wiki is expanding at a good rate, which means that someone will have to keep an eye on all that is being written. Let's see if the discussion cools down a bit, then decide.

That said, the initial article and subsequent edits were nothing less than shameless plugs for FutureOS. If you want to publish a plug, put it on your Profile page -- '''provided you create one''' and that you do not post anonymously! Why is it so darn hard to understand this??? [[User:Gryzor|Gryzor]] 19:42, 29 August 2006 (CEST)

How to plug for something, which costs no money?

:: I can also get different religions for free, nevertheless I want that someone tells me in a fundamentalistic way why his religion is best. The fact that something is free doesn´t mean that the wiki rules don´t have to be respected.

::: Right! So respect your own rules. Maybe the article wasn't ideal for wiki at first. But better an article that could be corrected than nothing to read. And the comparison about religion is very low under my level.

== Flaming ==

Will it be possible, to stop flaming around that future os thing? I hate it to see people fighting for nothing :D
So maybe it will be the best to protect the whole article and the talk-area to stop annoying and useless posts from both parties [[User:Kangaroo|Kangaroo MusiQue of HJT]] 14:06, 5 September 2006 (CEST)

: Well, but who started the flaming? ;-)) [http://www.cpcwiki.eu/index.php?title=Talk:FutureOS&oldid=2154], [http://www.cpcwiki.eu/index.php?title=Talk:FutureOS&diff=4395&oldid=4393] I think at least the talk page shouldn't be protected, otherwise I am afraid, that it will continue on the general discussion page. -- [[User:Prodatron|Prodatron]] 15:02, 5 September 2006 (CEST)

:: :-) It was just my first reaction on the original-article as i read it. And that where logical questions, after reading an advertisement-text on the wiki for a "ultimate OS" with the best-features around, wich doesnt exist anyway in this form :) [[User:Kangaroo|Kangaroo MusiQue of HJT]] 20:31, 5 September 2006 (CEST)

: Yes the flaming is stupid. That's why the article was locked, but I think that talk pages should really rarely be locked... indeed, if one wants, it's very difficult, if not impossible, to keep them from flaming one way or the other. [[User:Gryzor|Gryzor]] 17:25, 5 September 2006 (CEST)

: You (Kangaroo) and Rode start the flaming. So you BOTH have to stop it. Nobody else is flaming around. TFM
:: So that is NOT true.. i just mentioned, that future os must be a very great thing and much better than other OSses around, cause your text telled me, that FOS supports any device plugged in without needing a driver and so on. As Rode has written, that he has tried to work with FOS and found things out that arent true within your advertisement text, and after his new FOSuggestion-article looks much better than the original from TFM, i personally think, that i shall call you Monster-Marketing-Machinae (MMM) to keep the traditions :-) [[User:Kangaroo|Kangaroo MusiQue of HJT]] 08:02, 8 September 2006 (CEST)
::: Well, what Rode has told here are just lies. Everybody can easiely proove this. I never sayd "any device", I sayd "much devices" - and that is true. Please don't talk about things you have never used. Why? If you ever had used FutureOS, you wouldn't argue that way. And about marketing, I don't want to earn money with FutureOS. Look at your cmo homepage and you see what is MMM! [[TFM]]

== Unlocking the FutureOS article ==

Since many changes have been introcuced in this article, which aren't true, this article should be unlocked again - at least for me, the originatior of FutureOS. [[TFM]]

:: The Problem about that is, that YOU arent telling the truth about the features of your OS and make the article an advertisement. So IMHO its better to let others write about the FOS, so its more near reality :-) Nothing personal against you, but it looks like, that you are a bit to enthusiastic with your own shit :) [[User:Kangaroo|Kangaroo MusiQue of HJT]] 19:25, 5 September 2006 (CEST)
::: Stop! I must admit that the first version of the article was a copy of an article I wrote for an english papermag, because I had not the time to do all the work again. But I NEVER wrote something untrue here. If you don't know FutureOS like me, then you should ask first, instead of flaming around. I'm very sorry that you can't be objective. [[TFM]]

:::: Somehow his stamina is impressive - or lets say very psycho. I think no one else would "fight" so hard for a 15 years old and completely outdated project today even in the retro scene, as it is one of the worst software examples of the old days. Regarding the "truth", even the actual article is not true and the first one was just a cheeky piece of advertisement. Please have a look at the new version, it could be a better base. Sad that this strange guy with his bizarre bunch of routines is the only one, who behaves negative in the CPCWiki. - [[User:Rode]]

Ahh.. and GO get a WIKI-Account instead of posting the shit anonymous its NOT SO HARD, it DOESNT HURT and it will HELP others to see your GOOD WILL (or your willy) [[User:Kangaroo|Kangaroo MusiQue of HJT]] 19:25, 5 September 2006 (CEST)

: Finally he found out, how to create an account. But it seems, that he still has to learn a lot of more things, like the behaviour in talk pages etc. It's interesting, that this is the only problematic article in the whole wiki, but as I could see it was always the same with this person in the CPC history. As we know, that he will rollback the article into its original advertisement form, it shouldn't be unlocked for sure. I wrote a more objective version of the article some days ago, and I will suggest it shortly. [[User:Rode|Rode]]

See [[FutureOS/Suggestion1]]

Dear Rode don't talk about behaviour, because yours is pretty bad. As bad as your suggestion about the FutureOS article.
It is known that you don't like FutureOS, this is the reaseon why this article is problematic. Now we have the same problems here like in german Wikipedia before - thanks to you! I would greatly apprecialte if you could leave us here. Only without you it is possible to make this article better, this would help us all. If you have personal problems with FutureOS (or me) then this here is NOT the place for your personal war. [[TFM]]

Croco Chanel N°4

2006-10-06T14:41:04Z

84.151.251.135:

[[Image:CC4.gif|244px|thumb|by [[Fafa]]]]
''Croco Channel Meeting N°4'' call for attenders !

The fourth edition of the Croco Channel Meeting may be organized next year only if there's enough attenders (minimum 30, to share the location rent and food and having a cheap entrance fee for everyone). The meeting will take place near Paris (60Km) at Laigneville (Oise). You can join the party place by walking 15 minutes from the train station.

Several dates are possible :

* 4,5 & 6 May 2007 (friday 14h to monday 10h),
* 11,12 & 13 May 2007 (friday 14h to monday 10h),

If you are interested to come, drop a mail now to [[Candy]] of [[Overlanders]] to give him what dates are the best for you or ask any further information : ''broudin (dot) sebastien (at) laposte (dot) net''

* Croco Chanel #4 participants list :
** ''France''
*** [http://asphyx0r.deviantart.com Asphyx] of [http://www.acid.org ACiD]
*** [[Ast]] of [[Impact]] and ex-[[Ast System]]
*** [[Barjack]] of [[Futur's]]
*** [[Beb]] of [[Overlanders]]
*** [[Candy]] of [[Overlanders]]
*** [[Cjc]] of [[Croco Computer Club]]
*** [[Cmp]] of [[Impact]] and ex-[[Paradox]]
*** [[Cracky]] of [[Mortel]]
*** Denis
*** [[Digit]] of [[Logon System]]
*** [[Eliot]] of [[Benediction]]
*** [[Epsilon]] of [[Power System]]
*** [[Fenyx Kell]]
*** [[Fred Crazy]] of [[Logon System]]
*** [[Grim]] of [[Arkos]]
*** [[Hermol]]
*** [[Hicks]] of [[Another World]]
*** [[Jamian]]
*** [[Ker]]
*** [[Longshot]] of [[Logon System]]
*** [[Madram]] of [[Overlanders]]
*** [[Overflow]] of [[Logon System]]
*** [[Plissken]] of [[Revival]]
*** [[Poum]] of ex-french magazine [[Amstrad Cent Pour Cent]]
*** [[Power]]
*** [[PulkoMandy]]
*** [[Rainbow Software]]
*** [[Ramlaid]] of [[Arkos]]
*** [[Rubi]] of [[Logon System]]
*** [[Roudoudou]] of Flower Corp.
*** [[Septh]] of ex-french magazine [[Amstrad Cent Pour Cent]]
*** [[Shap]] of [[Overlanders]]
*** [[Sid]] of [[Impact]]
*** [[Slash]] of [[Logon System]]
*** [[Supersly]]
*** [[Targhan]] of [[Arkos]]
*** [[Tenebros]] of [[GPA]]
*** [[Tom et Jerry]] of [[GPA]]
*** [[Toms]] of [[Another World]]
*** [[Tronic]] of [[GPA]]
*** [[Two Mag]] of [[GPA]]
** ''Germany''
*** [[Prodatron]] of [[SymbiosiS]]
*** [[Tolkin]] of [[Future Soft]]

One of the coolest CPC meeting is back ! Be there !

Some pictures of [[Croco Chanel N°1]], [[Croco Chanel N°2]] and [[Croco Chanel N°3]]

== Links ==

* [http://www.zataz.com/news/12140/Croco-Meeting-4-un-meeting-informatique--en-mai-prochain--qui-va-detroner-tout-ce-que-vous-pensiez-connaitre.html ''Croco Chanel n°4'' on the french e-zine Zataz.com]

[[Category:CPC events]]

News:Burgparty 2 will take place in december in Germany

2006-09-27T21:37:01Z

84.151.205.204: /* Expected participants */

[[Image:freusburg.gif|thumb|330px|The Freusburg in Kirchen/Germany]]

'''03. September 2006'''

While the [[Burgparty 1]] was the first german CPC party of 2006, the [[Burgparty 2]] will be the last one of this year.

== Where and When? ==

It will take place...
* Location: '''Kirchen (Sieg)'''
* Start: '''Friday, 01.12.2006'''
* End: '''Sunday, 03.12.2006'''

The location is the '''Freusburg''' in Kirchen, which is an old castle from the middle age. This castle is now used as a youth hostel, which has some very big advantages for beeing a party place. Kirchen itself is close to Siegen (one hour from Cologne in east direction).

== How? ==

Like last time the party will feature a complete all-inclusive-package:
* Breakfast and lunch at saturday and sunday
* Dinner at saturday
* a real bed for the two nights
* and of course a very nice historical environment ;-)
...for the costs of about 48 Euros.

== Costs and Registration ==

Unfortunately that also means, that we have to pay the costs for the youth hostel again in advance. So it is necessary, that all registered persons have to transfer the money even in advance to the organisators
Bankaccount.

As the Internet is a very insecure place, we can not place a Bank-adress inhere public :-/
So please send an eMail to > drzed A T ngi D O T de < if you want to registrate yourself for the Burgparty II.
ASAP after i got your eMail, i'll send you my bank-account, so that you can transfer
the above-mentioned 48 Euro onto it.
Please use "BurgPartyII Registration, %your-name%" as the Subject in your Registration-eMail!

For questions you also may contact Prodatron: mika A T prodatron D O T net

The deadline for the registrations is the 18.09.2006. We can't guarantee to accept later registrations, as the managers of the youth hostel force us to pay one week after the reservation.

== Web links ==

* [http://www.jewa-media.de/kunden/jugend-sommercamp/freusburg.html Information about the Freusburg (German)]
* [http://www.hostelz.com/l/de/hostel/20805-Jugendherberge-Freusburg Information about the Freusburg (English)]
* [http://www.jewa-media.de/kunden/jugend-sommercamp/freusburgweg.html Location plan]

== Expected participants ==

* [[Dr.Zed]]
* [[Prodatron]]
* [[TFM]]
* [[Tolkin]]
* [[Villain]]

[[Category:News 2006-09]]

Vortex Winchester Drive (WD20)

2006-09-13T20:24:26Z

84.151.226.82:

A harddisc solution for the CPC (The first for the CPC) by the German company [[Vortex]]

The Harddisc was build about 1986. It have the same cases like the F1-S and the F1-D. A big Power Supply which have about 1,5 Kilograms gives the power to the Harddrive. The Harddrive was shipped with the Powersupply The Harddrive itself, a built in 5,25" DD Diskdrive with 720KB and a Controller which was used for being the MFM Controller with two ports for two MFM Harddiscs, two DD Floppys and a ROM board which give place for 2 Roms, which held the VDOS 2.0
The Contoller get the Power from the Harddisc.
You can connect up to two 60MB MFM Drives which are supported by the VDOS 2.0.
But the normal setup was with a 20 MB MFM Drive.
A Software Package consists of a few helpful tools: LowLevel Format
Partition tools
Format partitions
Patch for CPM 2.2 and 3.0 (Plus) to support the Drive
File/Disccopy Tools
Diskformat
Hexeditor
and a few more...

[[Category:Hardware]] [[Category:Peripherals]]

Talk:FutureOS

2006-09-05T01:20:48Z

84.151.237.42: /* What's about respecting some rules? */

Talk:FutureOS

2006-09-05T01:10:56Z

84.151.237.42: /* Protection */

News:Burgparty 2 will take place in december in Germany

2006-09-04T22:52:13Z

84.151.237.42: /* Expected participants */

[[Image:freusburg.gif|thumb|330px|The Freusburg in Kirchen/Germany]]

'''03. September 2006'''

While the [[Burgparty 1]] was the first german CPC party of 2006, the [[Burgparty 2]] will be the last one of this year.

== Where and When? ==

It will take place...
* Location: '''Kirchen (Sieg)'''
* Start: '''Friday, 01.12.2006'''
* End: '''Sunday, 03.12.2006'''

The location is the '''Freusburg''' in Kirchen, which is an old castle from the middle age. This castle is now used as a youth hostel, which has some very big advantages for beeing a party place. Kirchen itself is close to Siegen (one hour from Cologne in east direction).

== How? ==

Like last time the party will feature a complete all-inclusive-package:
* Breakfast and lunch at saturday and sunday
* Dinner at saturday
* a real bed for the two nights
* and of course a very nice historical environment ;-)
...for the costs of about 48 Euros.

== Costs and Registration ==

Unfortunately that also means, that we have to pay the costs for the youth hostel again in advance. So it is necessary, that all registered persons have to transfer the money even in advance to the organisators
Bankaccount.

As the Internet is a very insecure place, we can not place a Bank-adress inhere public :-/
So please send an eMail to > drzed A T ngi D O T de < if you want to registrate yourself for the Burgparty II.
ASAP after i got your eMail, i'll send you my bank-account, so that you can transfer
the above-mentioned 48 Euro onto it.
Please use "BurgPartyII Registration, %your-name%" as the Subject in your Registration-eMail!

For questions you also may contact Prodatron: mika A T prodatron D O T net

The deadline for the registrations is the 18.09.2006. We can't guarantee to accept later registrations, as the managers of the youth hostel force us to pay one week after the reservation.

== Web links ==

* [http://www.jewa-media.de/kunden/jugend-sommercamp/freusburg.html Information about the Freusburg (German)]
* [http://www.hostelz.com/l/de/hostel/20805-Jugendherberge-Freusburg Information about the Freusburg (English)]
* [http://www.jewa-media.de/kunden/jugend-sommercamp/freusburgweg.html Location plan]

== Expected participants ==

* [[Dr.Zed]]
* [[Kangaroo MusiQue]] of [[HJT]] near Augsburg!
* [[Prodatron]]
* [[TFM]]
* [[Villain]]

[[Category:News 2006-09]]

Talk:FutureOS

2006-08-29T12:40:42Z

84.151.239.93: /* Protection? */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it? (Forgott to sign.. sorry.. but as i don't fear anything... here i am... [[User:Kangaroo|Kangaroo MusiQue of HJT]] 07:59, 28 August 2006 (CEST)

:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

:::RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

:::Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

:::Greets
:::TFM

::::Can we please stop hiding behind our finger? We all know what RTFM means, so please drop it. I assume almost everyone here is of at least average IQ... As I said, this languages is NOT permitted on board. What's more, what do you mean about that guy being allowed to vandalise your text? What did he vandalise? What should I stop? I think there might be a big misunderstanding here... Anyhow, about the SIdebar, I don't think it's 'very unfair', as I've explained before. FutureOS may be indeed very, very nice a project and I find myself playing with it the whole time, but SymbOS, with the existing Symbiface, has long ago reached critical mass and is very impressive and popular, that's why it had its own link. This is NOT an issue of 'put my project up there along with the others', it's trying to organise things in a better way. In any case, the Sidebar was changed a lot, I'm going to look into it... [[User:Gryzor|Gryzor]] 08:16, 11 August 2006 (CEST)

:That's something, which came to my mind very often! We should change the "SymbOS" link in the left menu to "Operating Systems". Then we can have a list of OSs for the CPC there. It would be a better entry point! --[[User:Octoate|Octoate]] 20:40, 10 August 2006 (CEST)

::Hm, I don't know. In this case you have to place all categories from the "serious software" articel in the sidebar. -- [[User:Prodatron|Prodatron]] 21:00, 10 August 2006 (CEST)

:::Argh... ;) --[[User:Octoate|Octoate]] 21:24, 10 August 2006 (CEST)

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

Thank you for your excellent help. TFM

== Protection? ==

Protection is like censorship in my opinion. Could be ok in this case, this anonymouse user tries to rollback his advertisement every few days. People shouldn't be disinformed and waste time with searching for non-existing stuff like me. Rode

The changes made by Rode are NOT correct. Please remove Rodes changes, because they aren't true. Further protection should be introduced only aginst Rode, who is introducing errors, just to discredit the project FutureOS. TFM

Some headwords:
* with 16 years not new; actual release is 6 years old, next one (next year?) contains 4 new features
* limitation to 512K files, no random access
* no memory management, only a strange table
* every seriose CPC software is written in Z80
* 48K maximum ram usage only by the OS (read your manual) should be mentioned in the "requirements"
* no support for different printers, serial interfaces/CPC booster
* mouse can't be used in own programs, only during file selection (so-called "GUI")
My sources: program itself, rom description, manuals. As you remember I asked you in your mailing list, but you censored my 2nd mail. Bad behaviour and needless misinformation, I invested a lot of time. It's ok, that other people won't be misinformed. Rode

Some true words:
* The actual version (system .8) is 3 months old.
* the length of a file is only limited by the space on disc or harddisc (that means 5 MB for the Dobbertin HD20). Look at routines TEILA/TEILB and TEISI/TEISK. I told that before.
* there is memory management (for example use EFER).
* may be that nearly all serious CPC software is written in Z80 assember, so where is the problem???
* the OS needs only RAM from &A000 to &BFFF. That are 8 KB not 48 KB. Read again. More RAM is only used when DIRectorys have to be buffered. Normally maximal 16 KB more.
* There is support for 7 Bit and 8 Bit printer output (CPC old genereation or CPC-Plus, which use different ways to print 8 Bit characters). Serial interfaces support will be documented after XzentriX 2006, as I wrote before.
* The Desktop can be called as a subroutine, mouses can be used that way. But thank your for the hint, I will provide mouse-support as own routine in the next update. Further see H_JC which enables you to use joysticks and all joystick-compatible medias (also mouses and trackballs).
About your sources: There is NOT written what you talking about, please read again. Or better ask first! If you don't agree please copy and paste the corresponding information.
Your second mail was censored, because in the FutureOS-ML is no place for defamations. I explained you that in detail in the mail I sent you some days ago.
If people get misinformed, then this is just your merit.

So I hope to clear some things here. Greets to all CPC users.
TFM

* ''The actual version (system .8) is 3 months old.''
: The OS is 16years old, not the actual still unfinshed version. In any case this ad-phrase doesn't belong into a Wiki article. Please see other articles.

Actual system .8 (exact that version you can download) is fully functional and working. A part of it is new written. And ok, some just perfect routines are still 16 years old, because the run pretty well, so why they should be changed?

* ''the length of a file is only limited by the space on disc or harddisc (that means 5 MB for the Dobbertin HD20). Look at routines TEILA/TEILB and TEISI/TEISK. I told that before.''
: Bizarre routines. Do you really think, that someone will use it? And what can I do if I want to access the last part of a 4MB file? You even dont use it by yourself in this "filmaker" (or how it is called), as you split the file into 16k ones. Strange.

Please don't use polemics, when you're just wrong again. Filmemacher is NOT the OS.

* ''there is memory management (for example use EFER).''
: Not mentioned. Will you describe it in the "future", too? And please do some improvements on your label naming, believe me, it's very embarrassing.

As I told numerous times before, the documentation will be updated after 9.9.2006.

* ''may be that nearly all serious CPC software is written in Z80 assember, so where is the problem???''
: Advertisement.

That phrase is not from me. Originally there stod that the OS is written in Z80 assembler. So what's your problem? That is just an information, as like that other OSes are written in C for example.

* ''the OS needs only RAM from &A000 to &BFFF. That are 8 KB not 48 KB. Read again. More RAM is only used when DIRectorys have to be buffered. Normally maximal 16 KB more.''
: No comment. I read and experienced something completely different. Read your own manual or rewrite your OS.

Everybode read the same, expect you.

* ''There is support for 7 Bit and 8 Bit printer output (CPC old genereation or CPC-Plus, which use different ways to print 8 Bit characters).''
: Yes, and no printer support. Big difference.

Pfff, that's just your oppinion. Maybe you understand something differecnt as support than me. Maybe the CPC is no PC.

* ''Serial interfaces support will be documented after XzentriX 2006, as I wrote before.''
: Great.
* ''The Desktop can be called as a subroutine, mouses can be used that way. But thank your for the hint, I will provide mouse-support as own routine in the next update.
: Great.
* Further see H_JC which enables you to use joysticks and all joystick-compatible medias (also mouses and trackballs).''
: Keyboard support as usual. I spoke about the mouses, you mentioned.
''Your second mail was censored, because in the FutureOS-ML is no place for defamations. I explained you that in detail in the mail I sent you some days ago.''
: Didn't receive it. If you call questions and facts "defamations" it's not my problem. Unbelieveable behaviour. Good, that you can't censore something here.

Yes, right, your behaviour is really unbeliveable. If you don't like FutureOS, why don't you keep it for yourself. I don't see any help coming from you, just negative stuff.

''So I hope to clear some things here.''
: Not really
''Greets to all CPC users.''
: Greets to all, who are able to create a CPCWiki account.
[[User:Rode|Rode]]

Greets to you, you have learnt to increase your kind of polemics. But you are still no help for cpc-wiki.

:: Please try to finish this discussion. I don't like to unprotect the article until this has been done. It seems, that Rode already tried to program with FutureOS and made some experiences. Did anyone else do it beside TFM and Rode and can participate here? -- [[User:Prodatron|Prodatron]] 13:53, 28 August 2006 (CEST)

It only seems that he tried to program, if he really would have tried it he wouldn't argue that way. He just don't like FutureOS, so he tries to trample on it.

::: As the past has shown the discussion will never be finished. I dont like the idea of unlocking the article because I know what will follow. There should be an objective article that is only changed by administrators if necessary. Sad but true. --[[User:Villain|Villain]] 17:05, 28 August 2006 (CEST)

Yes the article should be protected against users, that only want to discredite the project.

:::: The article will remain locked for the time being. It's really unfortunate that events are taking such a turn, at a time when the wiki is expanding at a good rate, which means that someone will have to keep an eye on all that is being written. Let's see if the discussion cools down a bit, then decide. [[User:Gryzor|Gryzor]] 18:26, 28 August 2006 (CEST)

Talk:FutureOS

2006-08-29T12:39:15Z

84.151.239.93: /* Protection? */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it? (Forgott to sign.. sorry.. but as i don't fear anything... here i am... [[User:Kangaroo|Kangaroo MusiQue of HJT]] 07:59, 28 August 2006 (CEST)

:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

:::RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

:::Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

:::Greets
:::TFM

::::Can we please stop hiding behind our finger? We all know what RTFM means, so please drop it. I assume almost everyone here is of at least average IQ... As I said, this languages is NOT permitted on board. What's more, what do you mean about that guy being allowed to vandalise your text? What did he vandalise? What should I stop? I think there might be a big misunderstanding here... Anyhow, about the SIdebar, I don't think it's 'very unfair', as I've explained before. FutureOS may be indeed very, very nice a project and I find myself playing with it the whole time, but SymbOS, with the existing Symbiface, has long ago reached critical mass and is very impressive and popular, that's why it had its own link. This is NOT an issue of 'put my project up there along with the others', it's trying to organise things in a better way. In any case, the Sidebar was changed a lot, I'm going to look into it... [[User:Gryzor|Gryzor]] 08:16, 11 August 2006 (CEST)

:That's something, which came to my mind very often! We should change the "SymbOS" link in the left menu to "Operating Systems". Then we can have a list of OSs for the CPC there. It would be a better entry point! --[[User:Octoate|Octoate]] 20:40, 10 August 2006 (CEST)

::Hm, I don't know. In this case you have to place all categories from the "serious software" articel in the sidebar. -- [[User:Prodatron|Prodatron]] 21:00, 10 August 2006 (CEST)

:::Argh... ;) --[[User:Octoate|Octoate]] 21:24, 10 August 2006 (CEST)

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

Thank you for your excellent help. TFM

== Protection? ==

Protection is like censorship in my opinion. Could be ok in this case, this anonymouse user tries to rollback his advertisement every few days. People shouldn't be disinformed and waste time with searching for non-existing stuff like me. Rode

The changes made by Rode are NOT correct. Please remove Rodes changes, because they aren't true. Further protection should be introduced only aginst Rode, who is introducing errors, just to discredit the project FutureOS. TFM

Some headwords:
* with 16 years not new; actual release is 6 years old, next one (next year?) contains 4 new features
* limitation to 512K files, no random access
* no memory management, only a strange table
* every seriose CPC software is written in Z80
* 48K maximum ram usage only by the OS (read your manual) should be mentioned in the "requirements"
* no support for different printers, serial interfaces/CPC booster
* mouse can't be used in own programs, only during file selection (so-called "GUI")
My sources: program itself, rom description, manuals. As you remember I asked you in your mailing list, but you censored my 2nd mail. Bad behaviour and needless misinformation, I invested a lot of time. It's ok, that other people won't be misinformed. Rode

Some true words:
* The actual version (system .8) is 3 months old.
* the length of a file is only limited by the space on disc or harddisc (that means 5 MB for the Dobbertin HD20). Look at routines TEILA/TEILB and TEISI/TEISK. I told that before.
* there is memory management (for example use EFER).
* may be that nearly all serious CPC software is written in Z80 assember, so where is the problem???
* the OS needs only RAM from &A000 to &BFFF. That are 8 KB not 48 KB. Read again. More RAM is only used when DIRectorys have to be buffered. Normally maximal 16 KB more.
* There is support for 7 Bit and 8 Bit printer output (CPC old genereation or CPC-Plus, which use different ways to print 8 Bit characters). Serial interfaces support will be documented after XzentriX 2006, as I wrote before.
* The Desktop can be called as a subroutine, mouses can be used that way. But thank your for the hint, I will provide mouse-support as own routine in the next update. Further see H_JC which enables you to use joysticks and all joystick-compatible medias (also mouses and trackballs).
About your sources: There is NOT written what you talking about, please read again. Or better ask first! If you don't agree please copy and paste the corresponding information.
Your second mail was censored, because in the FutureOS-ML is no place for defamations. I explained you that in detail in the mail I sent you some days ago.
If people get misinformed, then this is just your merit.

So I hope to clear some things here. Greets to all CPC users.
TFM

* ''The actual version (system .8) is 3 months old.''
: The OS is 16years old, not the actual still unfinshed version. In any case this ad-phrase doesn't belong into a Wiki article. Please see other articles.

Actual system .8 (exact that version you can download) is fully functional and working. The hald of it is new written. And ok, some just perfect routines are still 16 years old, because the run pretty well, so why they should be changed.

* ''the length of a file is only limited by the space on disc or harddisc (that means 5 MB for the Dobbertin HD20). Look at routines TEILA/TEILB and TEISI/TEISK. I told that before.''
: Bizarre routines. Do you really think, that someone will use it? And what can I do if I want to access the last part of a 4MB file? You even dont use it by yourself in this "filmaker" (or how it is called), as you split the file into 16k ones. Strange.

Please don't use polemics, when you're just wrong again. Filmemacher is NOT the OS.

* ''there is memory management (for example use EFER).''
: Not mentioned. Will you describe it in the "future", too? And please do some improvements on your label naming, believe me, it's very embarrassing.

As I told numerous times before, the documentation will be updated after 9.9.2006.

* ''may be that nearly all serious CPC software is written in Z80 assember, so where is the problem???''
: Advertisement.

That phrase is not from me. Originally there stod that the OS is written in Z80 assembler. So what's your problem? That is just an information, as like that other OSes are written in C for example.

* ''the OS needs only RAM from &A000 to &BFFF. That are 8 KB not 48 KB. Read again. More RAM is only used when DIRectorys have to be buffered. Normally maximal 16 KB more.''
: No comment. I read and experienced something completely different. Read your own manual or rewrite your OS.

Everybode read the same, expect you.

* ''There is support for 7 Bit and 8 Bit printer output (CPC old genereation or CPC-Plus, which use different ways to print 8 Bit characters).''
: Yes, and no printer support. Big difference.

Pfff, that's just your oppinion. Maybe you understand something differecnt as support than me. Maybe the CPC is no PC.

* ''Serial interfaces support will be documented after XzentriX 2006, as I wrote before.''
: Great.
* ''The Desktop can be called as a subroutine, mouses can be used that way. But thank your for the hint, I will provide mouse-support as own routine in the next update.
: Great.
* Further see H_JC which enables you to use joysticks and all joystick-compatible medias (also mouses and trackballs).''
: Keyboard support as usual. I spoke about the mouses, you mentioned.
''Your second mail was censored, because in the FutureOS-ML is no place for defamations. I explained you that in detail in the mail I sent you some days ago.''
: Didn't receive it. If you call questions and facts "defamations" it's not my problem. Unbelieveable behaviour. Good, that you can't censore something here.

Yes, right, your behaviour is really unbeliveable. If you don't like FutureOS, why don't you keep it for yourself. I don't see any help coming from you, just negative stuff.

''So I hope to clear some things here.''
: Not really
''Greets to all CPC users.''
: Greets to all, who are able to create a CPCWiki account.
[[User:Rode|Rode]]

Greets to you, you have learnt to increase your kind of polemics. But you are still no help for cpc-wiki.

:: Please try to finish this discussion. I don't like to unprotect the article until this has been done. It seems, that Rode already tried to program with FutureOS and made some experiences. Did anyone else do it beside TFM and Rode and can participate here? -- [[User:Prodatron|Prodatron]] 13:53, 28 August 2006 (CEST)

It only seems that he tried to program, if he really would have tried it he wouldn't argue that way. He just don't like FutureOS, so he tries to trample on it.

::: As the past has shown the discussion will never be finished. I dont like the idea of unlocking the article because I know what will follow. There should be an objective article that is only changed by administrators if necessary. Sad but true. --[[User:Villain|Villain]] 17:05, 28 August 2006 (CEST)

Yes the article should be protected against users, that only want to discredite the project.

:::: The article will remain locked for the time being. It's really unfortunate that events are taking such a turn, at a time when the wiki is expanding at a good rate, which means that someone will have to keep an eye on all that is being written. Let's see if the discussion cools down a bit, then decide. [[User:Gryzor|Gryzor]] 18:26, 28 August 2006 (CEST)

News and Projects

2006-08-27T17:22:59Z

84.151.229.151: /* Projects */

== News ==

This is an overview of the last CPC related news. You will find a complete list of all news in the [[News:Archive|news archive]].

* 08/01/2006: [[News:CPCE v1.60 has been released|CPCE v1.60 has been released]]
* 08/14/2006: [[WinApe]] moved to it's own domain [http://www.winape.net http://www.winape.net]. Version 2.0 Alpha 9 released.
* 08/15/2006: [[WinCPC]] moved to it´s own domain [http://www.wincpc.ch] and there will be a new version soon featuring [[SYMBiFACE II]] support:

: Harddisc emulation Master/Slave or drive mapping
: Realtimeclock emulation
: PS2 mouse emulation
: Assembler improved
: Disassembler integrated
: fixed some smaller bugs

== Projects ==

This is a list of big CPC related projects, which are currently active. This list does not contain previews of unreleased productions or [[Emulators|CPC emulators]].

''(hard to find a definition here, what to list, and what not to list)''

* [[ANA]]
* [[BOB]]
* [[CPCng]]
* [[CPCMax!]]
* [[FutureOS]]

Talk:FutureOS

2006-08-27T16:27:05Z

84.151.229.151: /* Protection? */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it?

:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

:::RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

:::Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

:::Greets
:::TFM

::::Can we please stop hiding behind our finger? We all know what RTFM means, so please drop it. I assume almost everyone here is of at least average IQ... As I said, this languages is NOT permitted on board. What's more, what do you mean about that guy being allowed to vandalise your text? What did he vandalise? What should I stop? I think there might be a big misunderstanding here... Anyhow, about the SIdebar, I don't think it's 'very unfair', as I've explained before. FutureOS may be indeed very, very nice a project and I find myself playing with it the whole time, but SymbOS, with the existing Symbiface, has long ago reached critical mass and is very impressive and popular, that's why it had its own link. This is NOT an issue of 'put my project up there along with the others', it's trying to organise things in a better way. In any case, the Sidebar was changed a lot, I'm going to look into it... [[User:Gryzor|Gryzor]] 08:16, 11 August 2006 (CEST)

:That's something, which came to my mind very often! We should change the "SymbOS" link in the left menu to "Operating Systems". Then we can have a list of OSs for the CPC there. It would be a better entry point! --[[User:Octoate|Octoate]] 20:40, 10 August 2006 (CEST)

::Hm, I don't know. In this case you have to place all categories from the "serious software" articel in the sidebar. -- [[User:Prodatron|Prodatron]] 21:00, 10 August 2006 (CEST)

:::Argh... ;) --[[User:Octoate|Octoate]] 21:24, 10 August 2006 (CEST)

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

Thank you for your excellent help. TFM

== Protection? ==

Protection is like censorship in my opinion. Could be ok in this case, this anonymouse user tries to rollback his advertisement every few days. People shouldn't be disinformed and waste time with searching for non-existing stuff like me. Rode

The changes made by Rode are NOT correct. Please remove Rodes changes, because they aren't true. Further protection should be introduced only aginst Rode, who is introducing errors, just to discredit the project FutureOS. TFM

Some headwords:
* with 16 years not new; actual release is 6 years old, next one (next year?) contains 4 new features
* limitation to 512K files, no random access
* no memory management, only a strange table
* every seriose CPC software is written in Z80
* 48K maximum ram usage only by the OS (read your manual) should be mentioned in the "requirements"
* no support for different printers, serial interfaces/CPC booster
* mouse can't be used in own programs, only during file selection (so-called "GUI")
My sources: program itself, rom description, manuals. As you remember I asked you in your mailing list, but you censored my 2nd mail. Bad behaviour and needless misinformation, I invested a lot of time. It's ok, that other people won't be misinformed. Rode

Some true words:
* The actual version (system .8) is 3 months old.
* the length of a file is only limited by the space on disc or harddisc (that means 5 MB for the Dobbertin HD20). Look at routines TEILA/TEILB and TEISI/TEISK. I told that before.
* there is memory management (for example use EFER).
* may be that nearly all serious CPC software is written in Z80 assember, so where is the problem???
* the OS needs only RAM from &A000 to &BFFF. That are 8 KB not 48 KB. Read again. More RAM is only used when DIRectorys have to be buffered. Normally maximal 16 KB more.
* There is support for 7 Bit and 8 Bit printer output (CPC old genereation or CPC-Plus, which use different ways to print 8 Bit characters). Serial interfaces support will be documented after XzentriX 2006, as I wrote before.
* The Desktop can be called as a subroutine, mouses can be used that way. But thank your for the hint, I will provide mouse-support as own routine in the next update. Further see H_JC which enables you to use joysticks and all joystick-compatible medias (also mouses and trackballs).
About your sources: There is NOT written what you talking about, please read again. Or better ask first! If you don't agree please copy and paste the corresponding information.
Your second mail was censored, because in the FutureOS-ML is no place for defamations. I explained you that in detail in the mail I sent you some days ago.
If people get misinformed, then this is just your merit.

So I hope to clear some things here. Greets to all CPC users.
TFM

Talk:FutureOS

2006-08-26T12:57:10Z

84.151.210.222: /* Protection? */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it?

:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

:::RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

:::Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

:::Greets
:::TFM

::::Can we please stop hiding behind our finger? We all know what RTFM means, so please drop it. I assume almost everyone here is of at least average IQ... As I said, this languages is NOT permitted on board. What's more, what do you mean about that guy being allowed to vandalise your text? What did he vandalise? What should I stop? I think there might be a big misunderstanding here... Anyhow, about the SIdebar, I don't think it's 'very unfair', as I've explained before. FutureOS may be indeed very, very nice a project and I find myself playing with it the whole time, but SymbOS, with the existing Symbiface, has long ago reached critical mass and is very impressive and popular, that's why it had its own link. This is NOT an issue of 'put my project up there along with the others', it's trying to organise things in a better way. In any case, the Sidebar was changed a lot, I'm going to look into it... [[User:Gryzor|Gryzor]] 08:16, 11 August 2006 (CEST)

:That's something, which came to my mind very often! We should change the "SymbOS" link in the left menu to "Operating Systems". Then we can have a list of OSs for the CPC there. It would be a better entry point! --[[User:Octoate|Octoate]] 20:40, 10 August 2006 (CEST)

::Hm, I don't know. In this case you have to place all categories from the "serious software" articel in the sidebar. -- [[User:Prodatron|Prodatron]] 21:00, 10 August 2006 (CEST)

:::Argh... ;) --[[User:Octoate|Octoate]] 21:24, 10 August 2006 (CEST)

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

Thank you for your excellent help. TFM

== Protection? ==

Protection is like censorship in my opinion. Could be ok in this case, this anonymouse user tries to rollback his advertisement every few days. People shouldn't be disinformed and waste time with searching for non-existing stuff like me. Rode

The changes made by Rode are NOT correct. Please remove Rodes changes, because they aren't true. Further protection should be introduced only aginst Rode, who is introducing errors, just to discredit the project FutureOS. TFM

FutureOS

2006-08-25T13:59:22Z

84.151.232.148:

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. FutureOS provides standard utilities in ROM. Further applications are delivered for disc or hard-disc. FutureOS is written completely in Z80 assembler.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in (Pseudo-)ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management, file-handling and Low/Mid/High-level routines to access the hardware. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[AMSDOS]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including different serial interfaces, real-time-clocks, printers, the Vortex disc drives, several mice & trackballs and the Dobbertin HD20 hard disc. Also newer hardware expansions like the CPC-Booster (rudimentary, since the Booster does all itself) and the Symbiface (RTC, PS/2 mouse) are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

* ''Disc drives and hard discs:'' FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

* ''Plug and Play:'' If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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.

From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

* ''Z80 Assembler:'' You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

* ''Programming in C for FutureOS:'' With [[FIOLIB]] it also possible to use C as a programming language.

== Applications ==
* [[CBM]] (pull down menu library)
* [[FilmeMacher]] (movie player)
* [[FuturePlayer]] (MP3 and WAV player)
* [[FutureView]] (disc mag)
* [[GMSK]] (sprite converter)

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS Downloads & Mailing list]

FutureOS

2006-08-17T13:17:23Z

84.151.218.26: /* Requirements */

FutureOS

2006-08-17T13:14:11Z

84.151.218.26: /* Introduction */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. FutureOS provides standard utilities in ROM. Further applications are delivered for disc or hard-disc. FutureOS is written completely in Z80 assembler.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[AMSDOS]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including different serial interfaces, real-time-clocks, printers, the Vortex disc drives, several mice & trackballs and the Dobbertin HD20 hard disc. Also newer hardware expansions like the CPC-Booster (rudimentary, since the Booster does all itself) and the Symbiface (RTC, PS/2 mouse) are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

* ''Disc drives and hard discs:'' FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

* ''Plug and Play:'' If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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.

From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

* ''Z80 Assembler:'' You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

* ''Programming in C for FutureOS:'' With [[FIOLIB]] it also possible to use C as a programming language.

== Applications ==
* [[CBM]] (pull down menu library)
* [[FilmeMacher]] (movie player)
* [[FuturePlayer]] (MP3 and WAV player)
* [[FutureView]] (disc mag)
* [[GMSK]] (sprite converter)

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS Downloads & Mailing list]

FutureOS

2006-08-11T12:42:36Z

84.151.224.74: /* Web links */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. FutureOS provides standard utilities in ROM. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[AMSDOS]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including different serial interfaces, real-time-clocks, printers, the Vortex disc drives, several mice & trackballs and the Dobbertin HD20 hard disc. Also newer hardware expansions like the CPC-Booster (rudimentary, since the Booster does all itself) and the Symbiface (RTC, PS/2 mouse) are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

* ''Disc drives and hard discs:'' FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

* ''Plug and Play:'' If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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.

From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

* ''Z80 Assembler:'' You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

* ''Programming in C for FutureOS:'' With [[FIOLIB]] it also possible to use C as a programming language.

== Applications ==
* [[CBM]] (pull down menu library)
* [[FilmeMacher]] (movie player)
* [[FuturePlayer]] (MP3 and WAV player)
* [[FutureView]] (disc mag)
* [[GMSK]] (sprite converter)

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS Downloads & Mailing list]

FutureOS

2006-08-11T12:35:36Z

84.151.224.74: /* Hardware */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. FutureOS provides standard utilities in ROM. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[AMSDOS]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including different serial interfaces, real-time-clocks, printers, the Vortex disc drives, several mice & trackballs and the Dobbertin HD20 hard disc. Also newer hardware expansions like the CPC-Booster (rudimentary, since the Booster does all itself) and the Symbiface (RTC, PS/2 mouse) are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

* ''Disc drives and hard discs:'' FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

* ''Plug and Play:'' If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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.

From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

* ''Z80 Assembler:'' You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

* ''Programming in C for FutureOS:'' With [[FIOLIB]] it also possible to use C as a programming language.

== Applications ==
* [[CBM]] (pull down menu library)
* [[FilmeMacher]] (movie player)
* [[FuturePlayer]] (MP3 and WAV player)
* [[FutureView]] (disc mag)
* [[GMSK]] (sprite converter)

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

Talk:FutureOS

2006-08-10T23:28:15Z

84.151.237.128: /* Looks good now */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it?

:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

::Greets
::TFM

:That's something, which came to my mind very often! We should change the "SymbOS" link in the left menu to "Operating Systems". Then we can have a list of OSs for the CPC there. It would be a better entry point! --[[User:Octoate|Octoate]] 20:40, 10 August 2006 (CEST)

::Hm, I don't know. In this case you have to place all categories from the "serious software" articel in the sidebar. -- [[User:Prodatron|Prodatron]] 21:00, 10 August 2006 (CEST)

:::Argh... ;) --[[User:Octoate|Octoate]] 21:24, 10 August 2006 (CEST)

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

Thank you for your excellent help. TFM

Links

2006-08-10T23:23:47Z

84.151.237.128:

==== Software-related ====
*[http://www.cpczone.net CPC Zone]
*[http://tacgr.emuunlim.com/ The Amstrad Computer Game Resource]
*[http://amstrad-esp.com/ Amstrad ESP (ES)]
*[http://www.cpcgamereviews.com/ CPC Game Reviews] - CPC Game Reviews is a website which, as its name suggests, contains reviews of games for the Amstrad CPC computer - hundreds of them, in fact. It also contains a collection of advertisements which have been scanned from Amstrad CPC magazines.
*[http://computeremuzone.com/amstrad/ Amstrad Zone]
*[http://www.prodatron.net/ Prodatron's page]
*[http://bestofcpc.webcindario.com/ Best of CPC] (ES)
*[http://arkos.cpcscene.com/ Arkos Demogroup] - The page of [[Arkos]], with some great demos, diskmags, games and tools.
*[http://www.cpc-hardware.com/ CPC Hardware] - (F) Forum, nice downloads, hardware projects; also an online store for hardware stuff like RS232 interfaces etc.
*[http://www.FutureOS.de/ FutureOS homepage]

----

==== Hardware-related ====
*[http://www.prodatron.net/ Prodatron's page]
*[http://www.pagina.de/amstrad Various Amstrad stuff] - Including instructions on how to fit or connect a 3.5" drive, hot to connect your CPC to your PC and how to transfer files, among others.
*[http://www.cpc-hardware.com/ CPC Hardware] - (F) Forum, nice downloads, hardware projects; also an online store for hardware stuff like RS232 interfaces etc.

----

==== Document resources ====

----

==== FTP sites ====

----

*[ftp://ftp.nvg.unit.no/pub/cpc/ NVG]
*[ftp://ftp.cmo.de/pub/Computer/Amstrad_CPC CMO.de] - Games, Meeting pictures, manuals, etc.
*[ftp://ftp.demon.co.uk/pub/cpm/ CPM] - related Amstrad things

==== Commercial sites ====
----

==== User Groups ====
*[news://comp.sys.amstrad.8bit CSA8]
*[http://www.cpczone.net/boards CPC Zone Forum]
*[http://www.wacci.org.uk/ WACCI] (Worldwide Amstrad Computer Club Incorporated) - WACCI was a UK based user group that supported the Amstrad CPC computer. It was a subscription-only, printed English magazine published bi-monthly and available throughout the world. The current issues of the magazine are now reproduced on this website.
----

==== Emulators ====
* [http://www.arnoldemu.freeserve.co.uk/ Arnold] (WIN | MAC | LINUX)
* [http://www.classicgaming.com/caprice/ Caprice] (WIN)
* [http://copacabana.emuunlim.com/ CoPaCabana] (WIN | PALM)
* [http://www.trans-it.de/cordes/amstrad/cpcemu.html CPCEmu]
* [http://www.amstrad-cpc.de CPC4X]
* [http://cpce.emuunlim.com CPCE]
* [http://icerive.free.fr/cpc Ice Rive]
* [http://jemu.emuunlim.com JEMU] (Multi-System Java)
* [http://amstrad.cpc.free.fr PC-CPC] by Ludovic Deplanque(Demoniak)
* [http://www.winape.net WinApe]

----

==== Others ====
*[http://genesis8.free.fr/index.php Genesis 8] - Genesis 8 is a spartan, but often-updated Amstrad-related news site.
*[http://www.cpcscene.com/ CPC Scene] - Various stuff. Of much interest: The [http://radio.cpcscene.com/ CPC online radio station]!
*[http://cpcrulez.free.fr/ CPC Rules] ([http://cpcrulez.2ya.com/ Alternative Link]) (FR) A great french site, updated frequently, with software reviews, utilities, games, demos, hardware info. A treasure and a must-visit if you speak french (though not necessarily so).
*[http://www.cpc-forever.com/ CPC forever] Community site in german with news, forum and so on.
*[http://www.frappr.com/cpcscene/ CPC scene map]

FutureOS

2006-08-10T23:18:02Z

84.151.237.128: /* Introduction */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. FutureOS provides standard utilities in ROM. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20. Also newer hardware expansions like the CPC-Booster and the Symbiface are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

* ''Disc drives and hard discs:'' FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

* ''Plug and Play:'' If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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.

From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

* ''Z80 Assembler:'' You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

* ''Programming in C for FutureOS:'' With [[FIOLIB]] it also possible to use C as a programming language.

== Applications ==
* [[CBM]] (pull down menu library)
* [[FilmeMacher]] (movie player)
* [[FuturePlayer]] (MP3 and WAV player)
* [[FutureView]] (disc mag)
* [[GMSK]] (sprite converter)

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

Talk:FutureOS

2006-08-10T18:19:14Z

84.151.239.244: /* Questions... */

==Questions...==

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it?

:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
:About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
:That would only be fair.
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

:Greets to all honest CPC sceners,
:TFM

:: Please try to keep your tone down. I'm letting this here as an example of what NOT to say. RTFM is NOT part of the language that will be tolerated here, if we want to keep a flame war out of our wiki; so please keep this in mind. And please don't jump to conclusions - several users still do not know about signing their entries! It seems to me the original poster was more positive than negative, so you could try and calmly answer to his questions, otherwise there's no reason in replying at all. This is NOT a debate room, and fights will NOT ('''NOT!''') be welcome here. You do not need to be apologetic (as you are in a couple of points) about anything that FutureOS may be lacking, since it's a wonderful system anyhow, but also taking it to the other extreme doesn't exactly help things either.

::Best regards,
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)

RTFM means Read The Futureos Manual, so where is the problem? That guy (without name) is allowed to vandalish my text? Why don't you stop him?

Anyhow, and why don't talk about something other very unfair. At the left side, below "the present" there is a line for SymbOS, why not FutueOS. I would like to please you to insert that line.

::Greets
::TFM

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

== Looks good now ==

Thanx to everybodys' effort the article looks a lot better now. I wouldn't call "CPC Booster support" like this, but who cares. What's about summarising some very small sections and maybe removing some user-manual-like sentences? -- [[User:Prodatron|Prodatron]] 17:44, 10 August 2006 (CEST)
:Sumarised all sections which contained only 1 or 2 sentences and removed the FioLib text in its own article. -- [[User:Prodatron|Prodatron]] 19:16, 10 August 2006 (CEST)

FIOLIB

2006-08-10T16:15:39Z

84.151.239.244:

cpcstart()
This function prepares [[FutureOS]] for running Small-C programs. It is only used by FIOLIB.C itself. The user doesn't and shouldn't use that function.

byebye()
This function is used to end a Small-C program under FutureOS. You can use this function or just end the program. Both has the same effect. The function byebye displays the message "Press any key to return to the Desktop." , then it waits for a pressed key and finally jumps back to the Desktop of FutureOS.

oscall(adr,regpack)
int adr;
int *regpack; /* af,hl,de,bc */
This function is used to call a subroutine of the OS. The contents of "regpack" are loaded in the Z80 registers, then the OS-routine "adr" at the address "adr" is called. And then the Z80 registers are written back in "regpack". Beginning at regpack the 16 Bit registers AF, HL, DE and BC follow:
regs[0]=a; /* AF */
regs[1]=b; /* HL */
regs[2]=c; /* DE */
regs[3]=d; /* BC */

mode(n)
int n;
Set the screen MODE to 0, 1, 2 or 3. Mode 0, 1 and 2 are the same as with the MODE command under Basic. Don't use Mode 3! The mode is changed and the screen will be cleared, the cursor is set to the most left, most upper position.

cls()
This is the same as the BASIC command CLS. It clears the screen and the cursor is set to the most left, most upper position.

s80x25()
Sets the format of the screen to 80 columns and 25 lines (in Mode 2), or to 40 columns and 25 lines (in Mode 1). Only the screen format is changed, NO cls!

s64x32()
Sets the format of the screen to 64 columns and 32 lines (screen Mode 2), or 32 columns and 32 lines (in Mode 1). Only the screen format is changed, NO cls!

pen0(n)
int n;
Changes the PEN for MODE 0. This type of PEN selection is needed if you want to paint dots ( with plot(x,y) ) under SCREEN MODE 0. You can use PEN 1 - 15. It's the same like the command PEN in Basic, when using MODE 0. Only the PEN of MODE 0 is changed. The PEN selections of Mode 1 and 2 aren't changed!

pen1(n)
int n;
Changes the PEN for MODE 1. You can use PEN 1, 2 or 3. It's the same like the command PEN in Basic. If you select PEN 0 then the two-color PEN is selected.
Only the PEN of MODE 1 is changed. The PEN's for Mode 0 and 2 aren't changed!

pen2(n)
int n;
Selects character attributes for SCREEN MODE 2. Integer n must be between 0
and 4. So you can use normal, italics, underlined, inverted and streaked out
character attributes.
Only the character-attributes for MODE 2 are changed!!! The PEN's for Mode 0
and 1 aren't changed!

ink(p,c)
int p,c;
The INK function changes the COLOR of a PEN. It's the same like the INK command of Basic. Attention: You can only give ONE colour to the PEN. PEN 16 is BORDER!

locate(x,y)
int x,y;
Function LOCATE is nearly the same like the Basic command LOCATE, you give the column (x) and the line (y) where the cursor should be positioned. You have 80 columns in Mode 2 and 40 columns in Mode 1 (if the screnn has 80x25 format).

plot(x,y)
int x,y;
The function PLOT allows to set a POINT on the screen. You can use SCREEN MODEs 0, 1 or 2. Unter Mode 2, PEN 1 is always used. Under the MODEs 0 and 1 the used PEN depends on the functions pen0(n) and pen1(n), which preselect the PEN. MODE 2 screen format should be 64*32. The screen format (rows, lines) for MODE 0 and 1 can be selected freely. The coordinate position 0,0 is the upper left corner.

move(x,y)
int x,y;
The function MOVE allows to set the graphic cursor (start coordinates of a line for example) to X and Y. The coordinate position 0, 0 is the upper left corner.

draw(x,y)
int x,y;
DRAWs a line form the actual graphic cursor position (use MOVE to set it!) to the coordinates X and Y. The coordinate position 0, 0 is the upper left corner.
You can use this function in all screen-MODEs, -formats and with all PENs.

circle(r)
int r;
CIRCLEs can be created by this routine. The center of the CIRCLE should be set before through the MOVE(X,Y) function, else the actual X and Y coordinates will be used. The variable r contains the RADIUS of the CIRCLE. (Use under Mode 1)!!

lscr(s)
char *s;
Loads a 16 KB screen to address &C000. Do not load pictures with file-header!!!
To define the picture / screen which should be loaded, a string with the format "DUU:filenameEXT" has to be given to the function. "D" is the DRIVE "a".."m" or "A".."M", UU is the USER-number in hexadezimal "00".."FE", "filename" and "EXT" define the name of the file and the extension. You must type in every "space"!!
Between the "filename" and the "EXT" is _NO_ point!!! And _NEVER_ use User &FF!

fopen(name,mode)
char *name,*mode;
Opens a file to read or to write. A file-name must be provided in the format: "DUU:FilenameExt". D ist the Drive-letter (A..M), U is the User-number in a hexadezimal view. Between the Name and the Extension of the file, there is NO Dot! An example: "B00:Role-Play-D". The string "filename" isn't allowed to be located between &4000 and &7FFF, there it can't be read!!!
The File-mode "mode" can be "r"/"R", "w"/"W", "a"/"A". "R" opens a file to be read. "W" opens a file to be written. (("A" appends a file-not finished yet))
You can access every byte of every file everytime. But a file can't be longer than 16 KB. If you need more space, just open another 16 KB file!
If fopen(name,mode) is successfull the number of the file is given back, this number is between 32 and 63 (&20-&3F). Else "EOF" is given back!

fclose(f)
int f;
Close an previously opened file with the File-number "f". Whereas "f" must lie between 32 and 63 (&20-&3F). The file "f" is written back to disc.

sfile(f)
int f;
Select file to read/write from/to. The File-number "f" must lie between 32 and 63 (&20-&3F). The file is selected for all future read/write operations, until sfile(f) is used again or a new file is opened with fopen(name,mode).

sfico(c)
int c;
Set File-Counter of the actual selected File. The File-Couter must be an value between &4000 and &7FFF. The File-Counter defines where to read from, or where to write to (inside the file).

err(s)
char *s;
Returns the message "Error: " and displays an error number. Can be used to give an error-message to the user.

putchar(c)
char c;
Uses putc() to display a character on the screen or write a byte to a file.

putc(c,unit)
char c;
int unit;
Uses putb() to display a character. Adds CR control code after LF control code.

putb(c,unit)
char c;
int unit;
Display a byte on the screen or write a byte to a file.

gets(s)
char *s;
Get a new/empty string from the keyboard, the string is maximal 80 Bytes long.
This function switches the screen MODE to 2, the string is entered at cursor-position.

edst(s)
char *s;
Edit a string at address "s", the string is 80 Bytes long. This function
switches the screen MODE to 2, the string is edited at cursor-position.

basedit(b)
char *b;
Edit a string at address "b", whereby "b" must lie between &4000-&BFFF, the
edited string is 80 Bytes long. This function switches the screen MODE to 2,
the string is edited at the cursor-position.

getkey(n)
int *n;
GETKEY reads the actual pressed key from the keyboard. It waits until a key is pressed. The pressed key is returned in "n".

getchar()
The Function waits until no key is pressed, then it reads the first pressed key from the keyboard. It waits for a pressed key, then returns. Uses getc(stdin);

getc(unit)
int unit;
Get character from keyboard or from file. (LF control codes are deleted?).
Uses getb(unit).

getb(unit)
int unit;
Get byte from keyboard of from file.

puts(buf)
char *buf;
Print a null-terminated string on the screen. Uses putchar(c);

upper(c)
int c;
Converts letter to upper case.

getp(port)
Input a byte from port "port".
Function format: getp(p) where p is a 16 bit port number

putp(value,port)
OUT byte "value" to 16 Bit port "port".
Function format: putp('A',n); or putp(value,n);

rnd(n)
int n;
rnd(n) returns an integer value between 0 and n. If n is 0 the value will lie within + / - 32 kB. Based on suggestions in Hamming's book on Numerical Methods for Scientists and Engineers. A seed is multiplied by a large number causing an overflow.

exit()
Exit the Small-C program, initializes OS and return to the Desktop.
No message is displayed. Jump to Desktop happens immediately.

alloc(b)
int b; /* # bytes desired */
Allocates (b) bytes of memory. Routine returns address of a block of memory.
The heap grows upwards.

free(addr)
int addr;
This routine resets the top of heap pointer (HEAPTOP) to addr*

avail()
avail() returns the number of bytes between top of heap (HEAPTOP) and the end of the TPA (heapend). Remember that this includes the stack!

hex(x)
int x;
Returns hexadezimal byte, uses hexb(x);

hexb(x)
int x;
Uses hexn(x); to display a hexadizimal byte.

hexn(x)
int x;
Uses putchar(); to display hexadezimal characters.

strcmp(str1,str2)
char *str1,*str2;
Compares two strings. This function returns an integer: less than, equal to, or greater than zero depending on whether the string at 'str1' is less than, equal to, or greater than the string at 'str2'.

strncmp(str1,str2,n)
char *str1, *str2; int n;
Works like strcmp, except that a maximum of n characters are compared.

strcpy(tar,src)
char *tar,*src;
Copies the string at 'src' to 'tar'.

strncpy(tar,src,n)
char *src,*tar;
int n;
Copy string of n-bytes from "src" to "tar". Works like strcpy(), except that n characters are transferred - regardless of the length of the source string. If the source string is too long it is truncated and a null character is placed at the end of the destination string.

strlen(s)
char *s;
Returns the length of a given string, the count of the number of characters in the string 's'. The null character at the end of the string is not included in the count.

strcat(dest,sour)
char *dest,*sour;
Function appends the string at 'sour' to the end of the string at 'dest'.
A null character terminates the end of the new 'dest' string. The space
reserved for 'dest' must be long enough to hold the resulting string.
The function returns 'dest'.

strncat(dest,sour,n)
char *dest,*sour; int n;
Function works like strcat(), except that a maximum of n characters from the
source string are transferred to the destination.

strchr(str,c)
char *str,c;
Returns a pointer to the first occurrence of the character 'c' in the string
at 'str'. A NULL pointer is returned if the character is not found.

strrchr(str,c)
char *str,c;
Works like strchr(), except that the rightmost occurrence of the character is searched for.

tolower(s)
char *s;
Convert character to lower case.

toupper(s)
char *s;
Converts character to upper case.

FIOLIB

2006-08-10T16:15:05Z

84.151.239.244:

cpcstart()
This function prepares FutureOS for running Small-C programs. It is only used by FIOLIB.C itself. The user doesn't and shouldn't use that function.

byebye()
This function is used to end a Small-C program under FutureOS. You can use this function or just end the program. Both has the same effect. The function byebye displays the message "Press any key to return to the Desktop." , then it waits for a pressed key and finally jumps back to the Desktop of FutureOS.

oscall(adr,regpack)
int adr;
int *regpack; /* af,hl,de,bc */
This function is used to call a subroutine of the OS. The contents of "regpack" are loaded in the Z80 registers, then the OS-routine "adr" at the address "adr" is called. And then the Z80 registers are written back in "regpack". Beginning at regpack the 16 Bit registers AF, HL, DE and BC follow:
regs[0]=a; /* AF */
regs[1]=b; /* HL */
regs[2]=c; /* DE */
regs[3]=d; /* BC */

mode(n)
int n;
Set the screen MODE to 0, 1, 2 or 3. Mode 0, 1 and 2 are the same as with the MODE command under Basic. Don't use Mode 3! The mode is changed and the screen will be cleared, the cursor is set to the most left, most upper position.

cls()
This is the same as the BASIC command CLS. It clears the screen and the cursor is set to the most left, most upper position.

s80x25()
Sets the format of the screen to 80 columns and 25 lines (in Mode 2), or to 40 columns and 25 lines (in Mode 1). Only the screen format is changed, NO cls!

s64x32()
Sets the format of the screen to 64 columns and 32 lines (screen Mode 2), or 32 columns and 32 lines (in Mode 1). Only the screen format is changed, NO cls!

pen0(n)
int n;
Changes the PEN for MODE 0. This type of PEN selection is needed if you want to paint dots ( with plot(x,y) ) under SCREEN MODE 0. You can use PEN 1 - 15. It's the same like the command PEN in Basic, when using MODE 0. Only the PEN of MODE 0 is changed. The PEN selections of Mode 1 and 2 aren't changed!

pen1(n)
int n;
Changes the PEN for MODE 1. You can use PEN 1, 2 or 3. It's the same like the command PEN in Basic. If you select PEN 0 then the two-color PEN is selected.
Only the PEN of MODE 1 is changed. The PEN's for Mode 0 and 2 aren't changed!

pen2(n)
int n;
Selects character attributes for SCREEN MODE 2. Integer n must be between 0
and 4. So you can use normal, italics, underlined, inverted and streaked out
character attributes.
Only the character-attributes for MODE 2 are changed!!! The PEN's for Mode 0
and 1 aren't changed!

ink(p,c)
int p,c;
The INK function changes the COLOR of a PEN. It's the same like the INK command of Basic. Attention: You can only give ONE colour to the PEN. PEN 16 is BORDER!

locate(x,y)
int x,y;
Function LOCATE is nearly the same like the Basic command LOCATE, you give the column (x) and the line (y) where the cursor should be positioned. You have 80 columns in Mode 2 and 40 columns in Mode 1 (if the screnn has 80x25 format).

plot(x,y)
int x,y;
The function PLOT allows to set a POINT on the screen. You can use SCREEN MODEs 0, 1 or 2. Unter Mode 2, PEN 1 is always used. Under the MODEs 0 and 1 the used PEN depends on the functions pen0(n) and pen1(n), which preselect the PEN. MODE 2 screen format should be 64*32. The screen format (rows, lines) for MODE 0 and 1 can be selected freely. The coordinate position 0,0 is the upper left corner.

move(x,y)
int x,y;
The function MOVE allows to set the graphic cursor (start coordinates of a line for example) to X and Y. The coordinate position 0, 0 is the upper left corner.

draw(x,y)
int x,y;
DRAWs a line form the actual graphic cursor position (use MOVE to set it!) to the coordinates X and Y. The coordinate position 0, 0 is the upper left corner.
You can use this function in all screen-MODEs, -formats and with all PENs.

circle(r)
int r;
CIRCLEs can be created by this routine. The center of the CIRCLE should be set before through the MOVE(X,Y) function, else the actual X and Y coordinates will be used. The variable r contains the RADIUS of the CIRCLE. (Use under Mode 1)!!

lscr(s)
char *s;
Loads a 16 KB screen to address &C000. Do not load pictures with file-header!!!
To define the picture / screen which should be loaded, a string with the format "DUU:filenameEXT" has to be given to the function. "D" is the DRIVE "a".."m" or "A".."M", UU is the USER-number in hexadezimal "00".."FE", "filename" and "EXT" define the name of the file and the extension. You must type in every "space"!!
Between the "filename" and the "EXT" is _NO_ point!!! And _NEVER_ use User &FF!

fopen(name,mode)
char *name,*mode;
Opens a file to read or to write. A file-name must be provided in the format: "DUU:FilenameExt". D ist the Drive-letter (A..M), U is the User-number in a hexadezimal view. Between the Name and the Extension of the file, there is NO Dot! An example: "B00:Role-Play-D". The string "filename" isn't allowed to be located between &4000 and &7FFF, there it can't be read!!!
The File-mode "mode" can be "r"/"R", "w"/"W", "a"/"A". "R" opens a file to be read. "W" opens a file to be written. (("A" appends a file-not finished yet))
You can access every byte of every file everytime. But a file can't be longer than 16 KB. If you need more space, just open another 16 KB file!
If fopen(name,mode) is successfull the number of the file is given back, this number is between 32 and 63 (&20-&3F). Else "EOF" is given back!

fclose(f)
int f;
Close an previously opened file with the File-number "f". Whereas "f" must lie between 32 and 63 (&20-&3F). The file "f" is written back to disc.

sfile(f)
int f;
Select file to read/write from/to. The File-number "f" must lie between 32 and 63 (&20-&3F). The file is selected for all future read/write operations, until sfile(f) is used again or a new file is opened with fopen(name,mode).

sfico(c)
int c;
Set File-Counter of the actual selected File. The File-Couter must be an value between &4000 and &7FFF. The File-Counter defines where to read from, or where to write to (inside the file).

err(s)
char *s;
Returns the message "Error: " and displays an error number. Can be used to give an error-message to the user.

putchar(c)
char c;
Uses putc() to display a character on the screen or write a byte to a file.

putc(c,unit)
char c;
int unit;
Uses putb() to display a character. Adds CR control code after LF control code.

putb(c,unit)
char c;
int unit;
Display a byte on the screen or write a byte to a file.

gets(s)
char *s;
Get a new/empty string from the keyboard, the string is maximal 80 Bytes long.
This function switches the screen MODE to 2, the string is entered at cursor-position.

edst(s)
char *s;
Edit a string at address "s", the string is 80 Bytes long. This function
switches the screen MODE to 2, the string is edited at cursor-position.

basedit(b)
char *b;
Edit a string at address "b", whereby "b" must lie between &4000-&BFFF, the
edited string is 80 Bytes long. This function switches the screen MODE to 2,
the string is edited at the cursor-position.

getkey(n)
int *n;
GETKEY reads the actual pressed key from the keyboard. It waits until a key is pressed. The pressed key is returned in "n".

getchar()
The Function waits until no key is pressed, then it reads the first pressed key from the keyboard. It waits for a pressed key, then returns. Uses getc(stdin);

getc(unit)
int unit;
Get character from keyboard or from file. (LF control codes are deleted?).
Uses getb(unit).

getb(unit)
int unit;
Get byte from keyboard of from file.

puts(buf)
char *buf;
Print a null-terminated string on the screen. Uses putchar(c);

upper(c)
int c;
Converts letter to upper case.

getp(port)
Input a byte from port "port".
Function format: getp(p) where p is a 16 bit port number

putp(value,port)
OUT byte "value" to 16 Bit port "port".
Function format: putp('A',n); or putp(value,n);

rnd(n)
int n;
rnd(n) returns an integer value between 0 and n. If n is 0 the value will lie within + / - 32 kB. Based on suggestions in Hamming's book on Numerical Methods for Scientists and Engineers. A seed is multiplied by a large number causing an overflow.

exit()
Exit the Small-C program, initializes OS and return to the Desktop.
No message is displayed. Jump to Desktop happens immediately.

alloc(b)
int b; /* # bytes desired */
Allocates (b) bytes of memory. Routine returns address of a block of memory.
The heap grows upwards.

free(addr)
int addr;
This routine resets the top of heap pointer (HEAPTOP) to addr*

avail()
avail() returns the number of bytes between top of heap (HEAPTOP) and the end of the TPA (heapend). Remember that this includes the stack!

hex(x)
int x;
Returns hexadezimal byte, uses hexb(x);

hexb(x)
int x;
Uses hexn(x); to display a hexadizimal byte.

hexn(x)
int x;
Uses putchar(); to display hexadezimal characters.

strcmp(str1,str2)
char *str1,*str2;
Compares two strings. This function returns an integer: less than, equal to, or greater than zero depending on whether the string at 'str1' is less than, equal to, or greater than the string at 'str2'.

strncmp(str1,str2,n)
char *str1, *str2; int n;
Works like strcmp, except that a maximum of n characters are compared.

strcpy(tar,src)
char *tar,*src;
Copies the string at 'src' to 'tar'.

strncpy(tar,src,n)
char *src,*tar;
int n;
Copy string of n-bytes from "src" to "tar". Works like strcpy(), except that n characters are transferred - regardless of the length of the source string. If the source string is too long it is truncated and a null character is placed at the end of the destination string.

strlen(s)
char *s;
Returns the length of a given string, the count of the number of characters in the string 's'. The null character at the end of the string is not included in the count.

strcat(dest,sour)
char *dest,*sour;
Function appends the string at 'sour' to the end of the string at 'dest'.
A null character terminates the end of the new 'dest' string. The space
reserved for 'dest' must be long enough to hold the resulting string.
The function returns 'dest'.

strncat(dest,sour,n)
char *dest,*sour; int n;
Function works like strcat(), except that a maximum of n characters from the
source string are transferred to the destination.

strchr(str,c)
char *str,c;
Returns a pointer to the first occurrence of the character 'c' in the string
at 'str'. A NULL pointer is returned if the character is not found.

strrchr(str,c)
char *str,c;
Works like strchr(), except that the rightmost occurrence of the character is searched for.

tolower(s)
char *s;
Convert character to lower case.

toupper(s)
char *s;
Converts character to upper case.

FutureOS

2006-08-10T15:56:24Z

84.151.239.244: /* Programming in C for FutureOS */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20. Also newer hardware expansions like the CPC-Booster and the Symbiface are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use [[FIOLIB]].C instead of IOLIB.C. becase [[FIOLIB]].C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with [[FIOLIB]] (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of [[FIOLIB]]. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T14:18:10Z

84.151.239.244: /* Introduction */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. Files can be as long as the corresponding drive or hard disc partition. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20. Also newer hardware expansions like the CPC-Booster and the Symbiface are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:50:27Z

84.151.239.244: /* Hardware */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20. Also newer hardware expansions like the CPC-Booster and the Symbiface are supported in system .8 beta.

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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:48:59Z

84.151.239.244: /* Plans for the next years */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:48:27Z

84.151.239.244: polemics deleted

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== Conclusion ==
FutureOS was designed as an OS with fast routines. It has specialised file-handling and memory-management that support programs up to 512 KB. The idea is that development of games, graphic tools, word processors, sound (especially MP3), management of big amounts of data, and programming languages should be possible in this environment. Today you can hear MP3 sounds, work with graphic, use C programs, watch movies & demos. But the project FutureOS is still and will ever be under further development.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:44:16Z

84.151.239.244: /* Developing for FutureOS */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== Developing for FutureOS ==
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 48 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== 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.

FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:41:06Z

84.151.239.244: /* Hardware */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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, because the CPC only has few hardware expansions compared to a PC.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off (use ConfigOS utility).

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== 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 existence and type of your own interrupt handler you may use the second Z80 register set when interrupts are enabled.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 64 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== 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.

FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:37:57Z

84.151.239.244: /* File system */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off, if you are able to rewrite the ROM.

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== 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 existence and type of your own interrupt handler you may use the second Z80 register set when interrupts are enabled.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 64 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== 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.

FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:36:01Z

84.151.239.244: /* GUI */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file. FutureOS work with old AmsDOS file-headers.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off, if you are able to rewrite the ROM.

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== 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 existence and type of your own interrupt handler you may use the second Z80 register set when interrupts are enabled.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 64 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== 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.

FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

FutureOS

2006-08-10T12:34:45Z

84.151.239.244: /* Requirements */

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. The free RAM can be used for applications and DIRectory buffering. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 48 KB (not the screen) have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. FutureOS is said to be easy to handle, after learning how to work with it. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file. FutureOS work with old AmsDOS file-headers.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off, if you are able to rewrite the ROM.

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== 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 existence and type of your own interrupt handler you may use the second Z80 register set when interrupts are enabled.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 64 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== 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.

FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

Talk:FutureOS

2006-08-10T12:20:26Z

84.151.239.244:

Hmm.. are there any applications for Future OS?
And can i really add any device and it will be recommended by the system without any device driver?
Unbelievable!! and much better than SymbOS then, isn't it?

== TFMs answer ==
Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.
First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.
Software for FutureOS is availabe in the Yahoo-Group, where you can download it.
And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.
About features: Ok, I haven't finished the new documentation in english. But if I look at other projects, I have to believe, so believe me too.
That would only be fair.
I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.

Greets to all honest CPC sceners,
TFM

== What's about respecting some rules? ==

As this is not Wikipedia but our own scene CPCWiki, I wouldn't like to force the articles to follow strict rules, but at least the following two rules should be respected by everyone:
* no advertisment-like phrases
* no false information

The following parts in this article should be removed and replaced in a section like "possible plans for the future":
* IDE support (mentioned several times, and first I mixed v8 with v9, but as it should only be a possible part of v9 [and now even v8 isn't released], it will not be implemented before 2007 or later, right?)
* CPC Booster support (you can't call an entry in the port monitor "support")
* Multi tasking (I couldn't find any references)
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.

Some other parts should also be removed:
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)
* Advertisment-like phrases (e.g. "FutureOS is for programmers who want to use the CPC at its limits" and other ones; these should be better placed on a homepage but not in a Wiki)
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)

:I sense a scene fight coming on, I'm afraid... I do not wish to take any part in it, especially since I do not know anything about the common history of projects, but I hope it stays off the wiki!
::Well, in general it is quite easy to follow some necessary rules, so I am not afraid about fights. -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:I'll have to agree with some of Prodatron's remarks. The article needs heavy editing (I have altered several points myself, more is needed) so as to not appear as a commercial for FutureOS but more like an objective article. Also, at points it becomes more of a manual than an article on the OS itself.

:That said, even in Symbiface there was the phrase: ''It provides nearly everything you need to change your CPC into a powerful work station!'' which is more of the same :)
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)

:To get back to Prodatron's remarks, if his points are valid the article should be corrected. If ''system .9'', as it is called in the article, indeed refers to FutureOS v9 then I also think that it should be re-written, especially since not even v8 has been released (really looking forward to it!).

:In general, I would urge '''ALL''' contributors who are also developers, to try and keep their usual enthusiasm (read: ego ;) ) at a low, since we are trying to do an objective work and not promote one or the other product... Thanks! [[User:Gryzor|Gryzor]] 09:47, 9 August 2006 (CEST)

I have cleaned up the whole artice, removed advertisment-like phrases, re-wrote sentences that sounded too much like advertising and thigthened the language. Articles should contain no false or biased statements in any form. Keep it clear, true, neutral and objective. This is what I tried to accomplish when editing this article.
- 2006-08-09; Gwildor -
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)

I think the maximum file size currently is 512KB (19bit). I couldn't find any possibilities to load data from files, which are bigger than 512KB. Why is 16MB/24bit mentioned in the article? Also a planned feature for the future? -- [[User:Prodatron|Prodatron]] 17:02, 9 August 2006 (CEST)

FutureOS

2006-08-10T11:59:48Z

84.151.239.244: errors deleted

[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]

== Introduction ==
'''FutureOS''' is new written operating system for the Amstrad CPC6128 and 6128plus developed by [[TFM]]. Its development continues from 1990 up to now. The applications of FutureOS can be up to 512 KB in one piece. FutureOS has a memory management system, which divides RAM into 16 KB blocks. Further the file-system allows accessing files with a size of up to 512 KB. FutureOS provides some standard disc and print utilities. Further applications are delivered for disc or hard-disc. FutureOS is written in assembler like most serious 8 bit software.

== Requirements ==
The core of the OS needs 64 KB ROM. Compatible products are EPROM-cards, the ROM-RAM-BOX, [[SYMBiFACE II]], RAMcard or similar products. If you don't own such a card, you can take a look at FutureOS by using a compatible CPC Emulator (WinCPC, Caprice, WinApe).

The core of the OS itself is executed directly in ROM or EPROM where it is divided in four 16 KB blocks. It jumps between the ROMs with the help of a little common area. Depending on the number of buffered directories it requires between 24KB and 48KB of RAM. The remaining memory can be used for applications and data. Furthermore it contains memory management and file-handling. From AmsDOS/Basic you can start FutureOS with the RSX commands |OS or |FDESK. If you use |FDESK you can leave FutureOS and get back to BASIC where you have stopped before - the first 64KB have been preserved.

FutureOS only runs well on a CPC6128 or 6128plus, because they support the RAM configuration &C3 (which is essential for the mouse arrow of the GUI).

== GUI ==
The Desktop of FutureOS is divided in two sections. First an icon-section, where you can choose your functions. Second there is a section below, where you can browse through directories of discs and hard-disc partitions.

The Desktop can be controlled using a joystick, mouse, trackball or light-pen. There is no command line. The user interface is graphical, you click on icons and files to select them for subsequent actions.

Applications can call the GUI as a subroutine. FutureOS is said to be easy to handle, after learning how to work with it. The icons are fixed, so you will always work with the same desktop.

== File system ==
FutureOS is compatible with the CPCs native data-, file- and format structures (f. e. File-header, Disc-formats). It is not compatible with native [[Amsdos]] or [[CP/M]] programs. FutureOS and compatible applications can be downloaded at: [http://www.FutureOS.de www.FutureOS.de].

Filenames can use all 256 different characters and user numbers from 0 to 254 (except for &E5, which marks a deleted file). Different to Amsdos, a file that is erased under FutureOS will not be shifted to user &E5, but it will be physically removed from the directory. Files can be viewed on-screen (scroll up and down) or printed. You can also view the file-header. When typing a text-file it is possible to set the number of columns and lines of the window the text is displayed in. File-headers are displayed as AmsDOS file or the icon-like file-header of a FutureOS program. An AmsDOS file-header has 128 bytes of which some bytes are unused. FutureOS makes use of those unused bytes so that files have a length definition of 24bit and can have a physical RAM select. Therefore a file can be defined to be loaded everywhere in the external RAM. Also a FutureOS file-header can contain a graphical icon, a textual icon or a short description of the file. FutureOS work with old AmsDOS file-headers.

== Hardware ==
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several 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.

=== Drives, hard-discs and mass storage ===
FutureOS supports up to eight drives and up to four hard-disc partitions. It buffers the directories read from any mass storage device in the expansion RAM.

=== Plug and Play ===
If you connect a hardware expansion to a CPC, FutureOS will automatically detect that expansion, initialise it and make it accessible. The architecture of the OS allows you to add and remove hardware on purpose. An example: You add a trackball, you use it, then you connect and use a joystick and then you use a proportional mouse for example. You can turn external hardware in the configuration-bytes on or off, if you are able to rewrite the ROM.

== 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 ===
From the Desktop you can call a little machine monitor. This monitor provides features like editing of CPU registers and I/O ports, display and edit memory or the content of the ASIC of the 6128plus. Memory blocks can be copied or initialised. It is possible to call a routine with defined CPU registers and memory.

=== CBM - a menu system for FutureOS ===
The Command Bar Menu (CBM) provides an user-interface for own programs. It is not part of the OS itself. The source code is available and it's possible to use CBM for FutureOS programs. An example is the MP3-Player for FutureOS which uses CBM.

== 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 existence and type of your own interrupt handler you may use the second Z80 register set when interrupts are enabled.

=== Z80 Assembler ===
You can use an assembler for AmsDOS or for CP/M. Switching between AmsDOS and FutureOS is fast and using |FDESK allows to come back to AmsDOS with the first 64 KB or RAM remaining untouched.

=== Programming in C for FutureOS ===
It also possible to use C as a programming language. There is a CP/M version of Small-C and also Windows-based cross-compilers of the C language. You have to use FIOLIB.C instead of IOLIB.C. becase FIOLIB.C contains all C functions to use FutureOS system-calls.

You can use a normal C program compile it, assemble it, link the object-code with FIOLIB (an all other needed libraries) and add a header to the *.COM file with COMFU.COM. To start such an C-program under FutureOS you have to start the RUNC-environment. RUNC expands the features of FIOLIB. With RUNC it is possible to store functions in E-RAM, leaving more main memory free for applications.

== Plans for the next years ==
It is planned to support the following hardware during the next years:
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])
* [[CPC Booster]]

== 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.

FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.

== Web links ==
* [http://www.FutureOS.de FutureOS homepage]
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]

CBM

2006-08-10T11:56:17Z

84.151.239.244:

=== CBM - a menu system for FutureOS ===
The Command Bar Menu ([[CBM]]) is a part of [[FutureOS]]. It provides an user-interface for own programs. You can use pull-down menues to select functions. Windows aren't used, because the CPC-screen is little enough.
CBM is not part of the core OS itself. The source code is available and it's possible to use CBM for FutureOS programs. Examples are the MP3-Player and the Sprite Konverter GMSK for [[FutureOS]] which use CBM.

Web link:
http://groups.yahoo.com/group/FutureOS/files/Source%20Codes/

TFM

2006-08-10T11:49:22Z

84.151.239.244: /* Releases */

[[Image:TFM.jpg|thumb|TFM today]]

'''TFM''' or "The Future Man" (Dr. Stefan W. Stumpferl) is a coder of the german CPC scene. Since the early 90s he is working on his project [[FutureOS]].

== Releases ==

* [[FutureOS]]
** [[CBM]] (menu system for [[FutureOS]])
** [[FilmeMacher]] (movie player)
** [[FutureView]] (disc mag)
** [[Gerelakos]] (under construction)
** [[GMSK]] (sprite converter)

== Groups ==

* [[FutureSoft]]

[[Category:CPC scene members]]