https://oldwiki.cpcwiki.eu/api.php?action=feedcontributions&feedformat=atom&user=84.151.239.244CPCWiki - THE Amstrad CPC encyclopedia! - User contributions [en]2026-08-28T07:28:08ZUser contributionsMediaWiki 1.25.1https://oldwiki.cpcwiki.eu/index.php?title=Talk:FutureOS&diff=2685Talk:FutureOS2006-08-10T18:19:14Z<p>84.151.239.244: /* Questions... */</p>
<hr />
<div>==Questions...==<br />
<br />
Hmm.. are there any applications for Future OS?<br />
And can i really add any device and it will be recommended by the system without any device driver? <br />
Unbelievable!! and much better than SymbOS then, isn't it?<br />
<br />
:Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.<br />
:First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.<br />
:Software for FutureOS is availabe in the Yahoo-Group, where you can download it.<br />
:And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.<br />
: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.<br />
:That would only be fair.<br />
:I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.<br />
<br />
:Greets to all honest CPC sceners,<br />
:TFM<br />
<br />
:: 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.<br />
<br />
::Best regards, <br />
::[[User:Gryzor|Gryzor]] 16:02, 10 August 2006 (CEST)<br />
<br />
<br />
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?<br />
<br />
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.<br />
<br />
::Greets<br />
::TFM<br />
<br />
== What's about respecting some rules? ==<br />
<br />
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:<br />
* no advertisment-like phrases<br />
* no false information<br />
<br />
The following parts in this article should be removed and replaced in a section like "possible plans for the future":<br />
* 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?)<br />
* CPC Booster support (you can't call an entry in the port monitor "support")<br />
* Multi tasking (I couldn't find any references)<br />
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.<br />
<br />
Some other parts should also be removed:<br />
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)<br />
* 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)<br />
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)<br />
<br />
: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!<br />
::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)<br />
<br />
: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.<br />
<br />
: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 :)<br />
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)<br />
<br />
: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!).<br />
<br />
: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)<br />
<br />
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.<br />
- 2006-08-09; Gwildor -<br />
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)<br />
<br />
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)<br />
<br />
== Looks good now ==<br />
<br />
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)<br />
: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)</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FIOLIB&diff=2637FIOLIB2006-08-10T16:15:39Z<p>84.151.239.244: </p>
<hr />
<div>cpcstart()<br />
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.<br />
<br />
byebye()<br />
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.<br />
<br />
oscall(adr,regpack)<br />
int adr;<br />
int *regpack; /* af,hl,de,bc */<br />
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:<br />
regs[0]=a; /* AF */<br />
regs[1]=b; /* HL */<br />
regs[2]=c; /* DE */<br />
regs[3]=d; /* BC */<br />
<br />
mode(n)<br />
int n;<br />
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.<br />
<br />
cls()<br />
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.<br />
<br />
s80x25()<br />
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!<br />
<br />
s64x32()<br />
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!<br />
<br />
pen0(n)<br />
int n;<br />
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!<br />
<br />
pen1(n)<br />
int n;<br />
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.<br />
Only the PEN of MODE 1 is changed. The PEN's for Mode 0 and 2 aren't changed!<br />
<br />
pen2(n)<br />
int n;<br />
Selects character attributes for SCREEN MODE 2. Integer n must be between 0<br />
and 4. So you can use normal, italics, underlined, inverted and streaked out<br />
character attributes.<br />
Only the character-attributes for MODE 2 are changed!!! The PEN's for Mode 0<br />
and 1 aren't changed!<br />
<br />
ink(p,c)<br />
int p,c;<br />
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!<br />
<br />
locate(x,y)<br />
int x,y;<br />
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).<br />
<br />
plot(x,y)<br />
int x,y;<br />
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.<br />
<br />
move(x,y)<br />
int x,y;<br />
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.<br />
<br />
draw(x,y)<br />
int x,y;<br />
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.<br />
You can use this function in all screen-MODEs, -formats and with all PENs.<br />
<br />
circle(r)<br />
int r;<br />
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)!!<br />
<br />
lscr(s)<br />
char *s;<br />
Loads a 16 KB screen to address &C000. Do not load pictures with file-header!!!<br />
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"!!<br />
Between the "filename" and the "EXT" is _NO_ point!!! And _NEVER_ use User &FF!<br />
<br />
fopen(name,mode)<br />
char *name,*mode;<br />
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!!!<br />
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))<br />
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!<br />
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!<br />
<br />
fclose(f)<br />
int f;<br />
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.<br />
<br />
sfile(f)<br />
int f;<br />
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).<br />
<br />
sfico(c)<br />
int c;<br />
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).<br />
<br />
err(s)<br />
char *s;<br />
Returns the message "Error: " and displays an error number. Can be used to give an error-message to the user.<br />
<br />
putchar(c)<br />
char c;<br />
Uses putc() to display a character on the screen or write a byte to a file.<br />
<br />
putc(c,unit)<br />
char c;<br />
int unit;<br />
Uses putb() to display a character. Adds CR control code after LF control code.<br />
<br />
putb(c,unit)<br />
char c;<br />
int unit;<br />
Display a byte on the screen or write a byte to a file.<br />
<br />
gets(s)<br />
char *s;<br />
Get a new/empty string from the keyboard, the string is maximal 80 Bytes long.<br />
This function switches the screen MODE to 2, the string is entered at cursor-position.<br />
<br />
edst(s)<br />
char *s;<br />
Edit a string at address "s", the string is 80 Bytes long. This function<br />
switches the screen MODE to 2, the string is edited at cursor-position.<br />
<br />
basedit(b)<br />
char *b;<br />
Edit a string at address "b", whereby "b" must lie between &4000-&BFFF, the<br />
edited string is 80 Bytes long. This function switches the screen MODE to 2,<br />
the string is edited at the cursor-position.<br />
<br />
getkey(n)<br />
int *n;<br />
GETKEY reads the actual pressed key from the keyboard. It waits until a key is pressed. The pressed key is returned in "n".<br />
<br />
getchar()<br />
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);<br />
<br />
getc(unit)<br />
int unit;<br />
Get character from keyboard or from file. (LF control codes are deleted?).<br />
Uses getb(unit).<br />
<br />
getb(unit)<br />
int unit;<br />
Get byte from keyboard of from file.<br />
<br />
puts(buf)<br />
char *buf;<br />
Print a null-terminated string on the screen. Uses putchar(c);<br />
<br />
upper(c)<br />
int c;<br />
Converts letter to upper case.<br />
<br />
getp(port)<br />
Input a byte from port "port".<br />
Function format: getp(p) where p is a 16 bit port number<br />
<br />
putp(value,port)<br />
OUT byte "value" to 16 Bit port "port".<br />
Function format: putp('A',n); or putp(value,n);<br />
<br />
rnd(n)<br />
int n;<br />
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.<br />
<br />
exit()<br />
Exit the Small-C program, initializes OS and return to the Desktop.<br />
No message is displayed. Jump to Desktop happens immediately.<br />
<br />
alloc(b)<br />
int b; /* # bytes desired */<br />
Allocates (b) bytes of memory. Routine returns address of a block of memory.<br />
The heap grows upwards.<br />
<br />
free(addr)<br />
int addr;<br />
This routine resets the top of heap pointer (HEAPTOP) to addr*<br />
<br />
avail()<br />
avail() returns the number of bytes between top of heap (HEAPTOP) and the end of the TPA (heapend). Remember that this includes the stack!<br />
<br />
hex(x)<br />
int x;<br />
Returns hexadezimal byte, uses hexb(x);<br />
<br />
hexb(x)<br />
int x;<br />
Uses hexn(x); to display a hexadizimal byte.<br />
<br />
hexn(x)<br />
int x;<br />
Uses putchar(); to display hexadezimal characters.<br />
<br />
strcmp(str1,str2)<br />
char *str1,*str2;<br />
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'.<br />
<br />
strncmp(str1,str2,n)<br />
char *str1, *str2; int n;<br />
Works like strcmp, except that a maximum of n characters are compared.<br />
<br />
strcpy(tar,src)<br />
char *tar,*src;<br />
Copies the string at 'src' to 'tar'.<br />
<br />
strncpy(tar,src,n)<br />
char *src,*tar;<br />
int n;<br />
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.<br />
<br />
strlen(s)<br />
char *s;<br />
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.<br />
<br />
strcat(dest,sour)<br />
char *dest,*sour;<br />
Function appends the string at 'sour' to the end of the string at 'dest'.<br />
A null character terminates the end of the new 'dest' string. The space<br />
reserved for 'dest' must be long enough to hold the resulting string.<br />
The function returns 'dest'.<br />
<br />
strncat(dest,sour,n)<br />
char *dest,*sour; int n;<br />
Function works like strcat(), except that a maximum of n characters from the<br />
source string are transferred to the destination.<br />
<br />
strchr(str,c)<br />
char *str,c;<br />
Returns a pointer to the first occurrence of the character 'c' in the string<br />
at 'str'. A NULL pointer is returned if the character is not found.<br />
<br />
strrchr(str,c)<br />
char *str,c;<br />
Works like strchr(), except that the rightmost occurrence of the character is searched for.<br />
<br />
tolower(s)<br />
char *s;<br />
Convert character to lower case.<br />
<br />
toupper(s)<br />
char *s;<br />
Converts character to upper case.</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FIOLIB&diff=2636FIOLIB2006-08-10T16:15:05Z<p>84.151.239.244: </p>
<hr />
<div>cpcstart()<br />
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.<br />
<br />
byebye()<br />
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.<br />
<br />
oscall(adr,regpack)<br />
int adr;<br />
int *regpack; /* af,hl,de,bc */<br />
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:<br />
regs[0]=a; /* AF */<br />
regs[1]=b; /* HL */<br />
regs[2]=c; /* DE */<br />
regs[3]=d; /* BC */<br />
<br />
mode(n)<br />
int n;<br />
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.<br />
<br />
cls()<br />
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.<br />
<br />
s80x25()<br />
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!<br />
<br />
s64x32()<br />
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!<br />
<br />
pen0(n)<br />
int n;<br />
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!<br />
<br />
pen1(n)<br />
int n;<br />
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.<br />
Only the PEN of MODE 1 is changed. The PEN's for Mode 0 and 2 aren't changed!<br />
<br />
pen2(n)<br />
int n;<br />
Selects character attributes for SCREEN MODE 2. Integer n must be between 0<br />
and 4. So you can use normal, italics, underlined, inverted and streaked out<br />
character attributes.<br />
Only the character-attributes for MODE 2 are changed!!! The PEN's for Mode 0<br />
and 1 aren't changed!<br />
<br />
ink(p,c)<br />
int p,c;<br />
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!<br />
<br />
locate(x,y)<br />
int x,y;<br />
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).<br />
<br />
plot(x,y)<br />
int x,y;<br />
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.<br />
<br />
move(x,y)<br />
int x,y;<br />
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.<br />
<br />
draw(x,y)<br />
int x,y;<br />
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.<br />
You can use this function in all screen-MODEs, -formats and with all PENs.<br />
<br />
circle(r)<br />
int r;<br />
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)!!<br />
<br />
lscr(s)<br />
char *s;<br />
Loads a 16 KB screen to address &C000. Do not load pictures with file-header!!!<br />
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"!!<br />
Between the "filename" and the "EXT" is _NO_ point!!! And _NEVER_ use User &FF!<br />
<br />
fopen(name,mode)<br />
char *name,*mode;<br />
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!!!<br />
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))<br />
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!<br />
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!<br />
<br />
fclose(f)<br />
int f;<br />
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.<br />
<br />
sfile(f)<br />
int f;<br />
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).<br />
<br />
sfico(c)<br />
int c;<br />
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).<br />
<br />
err(s)<br />
char *s;<br />
Returns the message "Error: " and displays an error number. Can be used to give an error-message to the user.<br />
<br />
putchar(c)<br />
char c;<br />
Uses putc() to display a character on the screen or write a byte to a file.<br />
<br />
putc(c,unit)<br />
char c;<br />
int unit;<br />
Uses putb() to display a character. Adds CR control code after LF control code.<br />
<br />
putb(c,unit)<br />
char c;<br />
int unit;<br />
Display a byte on the screen or write a byte to a file.<br />
<br />
gets(s)<br />
char *s;<br />
Get a new/empty string from the keyboard, the string is maximal 80 Bytes long.<br />
This function switches the screen MODE to 2, the string is entered at cursor-position.<br />
<br />
edst(s)<br />
char *s;<br />
Edit a string at address "s", the string is 80 Bytes long. This function<br />
switches the screen MODE to 2, the string is edited at cursor-position.<br />
<br />
basedit(b)<br />
char *b;<br />
Edit a string at address "b", whereby "b" must lie between &4000-&BFFF, the<br />
edited string is 80 Bytes long. This function switches the screen MODE to 2,<br />
the string is edited at the cursor-position.<br />
<br />
getkey(n)<br />
int *n;<br />
GETKEY reads the actual pressed key from the keyboard. It waits until a key is pressed. The pressed key is returned in "n".<br />
<br />
getchar()<br />
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);<br />
<br />
getc(unit)<br />
int unit;<br />
Get character from keyboard or from file. (LF control codes are deleted?).<br />
Uses getb(unit).<br />
<br />
getb(unit)<br />
int unit;<br />
Get byte from keyboard of from file.<br />
<br />
puts(buf)<br />
char *buf;<br />
Print a null-terminated string on the screen. Uses putchar(c);<br />
<br />
upper(c)<br />
int c;<br />
Converts letter to upper case.<br />
<br />
getp(port)<br />
Input a byte from port "port".<br />
Function format: getp(p) where p is a 16 bit port number<br />
<br />
putp(value,port)<br />
OUT byte "value" to 16 Bit port "port".<br />
Function format: putp('A',n); or putp(value,n);<br />
<br />
rnd(n)<br />
int n;<br />
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.<br />
<br />
exit()<br />
Exit the Small-C program, initializes OS and return to the Desktop.<br />
No message is displayed. Jump to Desktop happens immediately.<br />
<br />
alloc(b)<br />
int b; /* # bytes desired */<br />
Allocates (b) bytes of memory. Routine returns address of a block of memory.<br />
The heap grows upwards.<br />
<br />
free(addr)<br />
int addr;<br />
This routine resets the top of heap pointer (HEAPTOP) to addr*<br />
<br />
avail()<br />
avail() returns the number of bytes between top of heap (HEAPTOP) and the end of the TPA (heapend). Remember that this includes the stack!<br />
<br />
hex(x)<br />
int x;<br />
Returns hexadezimal byte, uses hexb(x);<br />
<br />
hexb(x)<br />
int x;<br />
Uses hexn(x); to display a hexadizimal byte.<br />
<br />
hexn(x)<br />
int x;<br />
Uses putchar(); to display hexadezimal characters.<br />
<br />
strcmp(str1,str2)<br />
char *str1,*str2;<br />
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'.<br />
<br />
strncmp(str1,str2,n)<br />
char *str1, *str2; int n;<br />
Works like strcmp, except that a maximum of n characters are compared.<br />
<br />
strcpy(tar,src)<br />
char *tar,*src;<br />
Copies the string at 'src' to 'tar'.<br />
<br />
strncpy(tar,src,n)<br />
char *src,*tar;<br />
int n;<br />
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.<br />
<br />
strlen(s)<br />
char *s;<br />
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.<br />
<br />
strcat(dest,sour)<br />
char *dest,*sour;<br />
Function appends the string at 'sour' to the end of the string at 'dest'.<br />
A null character terminates the end of the new 'dest' string. The space<br />
reserved for 'dest' must be long enough to hold the resulting string.<br />
The function returns 'dest'.<br />
<br />
strncat(dest,sour,n)<br />
char *dest,*sour; int n;<br />
Function works like strcat(), except that a maximum of n characters from the<br />
source string are transferred to the destination.<br />
<br />
strchr(str,c)<br />
char *str,c;<br />
Returns a pointer to the first occurrence of the character 'c' in the string<br />
at 'str'. A NULL pointer is returned if the character is not found.<br />
<br />
strrchr(str,c)<br />
char *str,c;<br />
Works like strchr(), except that the rightmost occurrence of the character is searched for.<br />
<br />
tolower(s)<br />
char *s;<br />
Convert character to lower case.<br />
<br />
toupper(s)<br />
char *s;<br />
Converts character to upper case.</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2631FutureOS2006-08-10T15:56:24Z<p>84.151.239.244: /* Programming in C for FutureOS */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
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.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2624FutureOS2006-08-10T14:18:10Z<p>84.151.239.244: /* Introduction */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
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.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2618FutureOS2006-08-10T12:50:27Z<p>84.151.239.244: /* Hardware */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
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.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2617FutureOS2006-08-10T12:48:59Z<p>84.151.239.244: /* Plans for the next years */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2616FutureOS2006-08-10T12:48:27Z<p>84.151.239.244: polemics deleted</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2615FutureOS2006-08-10T12:44:16Z<p>84.151.239.244: /* Developing for FutureOS */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
You can developp very freely, even the RST vectors are free usable. Also the second register set of the Z80 is freely usable.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2614FutureOS2006-08-10T12:41:06Z<p>84.151.239.244: /* Hardware */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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).<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
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.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2613FutureOS2006-08-10T12:37:57Z<p>84.151.239.244: /* File system */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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.<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
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.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2612FutureOS2006-08-10T12:36:01Z<p>84.151.239.244: /* GUI */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
Applications can call the GUI as a subroutine. The icons are fixed, so you will always work with the same desktop.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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.<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
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.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2611FutureOS2006-08-10T12:34:45Z<p>84.151.239.244: /* Requirements */</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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.<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
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.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=Talk:FutureOS&diff=2610Talk:FutureOS2006-08-10T12:20:26Z<p>84.151.239.244: </p>
<hr />
<div>Hmm.. are there any applications for Future OS?<br />
And can i really add any device and it will be recommended by the system without any device driver? <br />
Unbelievable!! and much better than SymbOS then, isn't it?<br />
<br />
<br />
== TFMs answer ==<br />
Who are you? What is your name? Fear to sign? You seem not to be serious. But I try to answer serious.<br />
First you can't compare SymbOS and FutureOS. They're too different and therefore I use them both.<br />
Software for FutureOS is availabe in the Yahoo-Group, where you can download it.<br />
And yes, I try to support nearly all hardware for the CPC. Ok, some is still missing, but this will change soon I hope.<br />
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.<br />
That would only be fair.<br />
I have no time to explain the 126th time where some support function ist. RTFM, but the new version coming soon.<br />
<br />
Greets to all honest CPC sceners,<br />
TFM<br />
<br />
<br />
== What's about respecting some rules? ==<br />
<br />
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:<br />
* no advertisment-like phrases<br />
* no false information<br />
<br />
The following parts in this article should be removed and replaced in a section like "possible plans for the future":<br />
* 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?)<br />
* CPC Booster support (you can't call an entry in the port monitor "support")<br />
* Multi tasking (I couldn't find any references)<br />
If I am wrong, and these features are already implemented in FutureOS and ready for download, please provide us a link.<br />
<br />
Some other parts should also be removed:<br />
* One-drive restriction of other OSs (nearly every OS can do this, even Amsdos allows drive letters in a path)<br />
* 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)<br />
-- [[User:Prodatron|Prodatron]] 00:05, 9 August 2006 (CEST)<br />
<br />
: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!<br />
::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)<br />
<br />
: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.<br />
<br />
: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 :)<br />
::Yes, that's right. I think someone just copied & pasted this from the homepage ;) -- [[User:Prodatron|Prodatron]] 10:24, 9 August 2006 (CEST)<br />
<br />
: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!).<br />
<br />
: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)<br />
<br />
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.<br />
- 2006-08-09; Gwildor -<br />
:Thanks for your effort Gwildor! The article looks a bit more polished now. --[[User:Octoate|Octoate]] 14:07, 9 August 2006 (CEST)<br />
<br />
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)</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureOS&diff=2608FutureOS2006-08-10T11:59:48Z<p>84.151.239.244: errors deleted</p>
<hr />
<div>[[Image:Future-os.jpg|400px|thumb|FutureOS main screen]]<br />
<br />
== Introduction ==<br />
'''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.<br />
<br />
== Requirements ==<br />
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).<br />
<br />
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.<br />
<br />
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).<br />
<br />
== GUI ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== File system ==<br />
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].<br />
<br />
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.<br />
<br />
== Hardware ==<br />
The OS supports many of the hardware available for the CPC, including the Vortex disc drives, several mice and the Dobbertin HD20.<br />
<br />
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.<br />
<br />
=== Drives, hard-discs and mass storage ===<br />
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.<br />
<br />
=== Plug and Play ===<br />
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.<br />
<br />
== Utilities ==<br />
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.<br />
<br />
=== Machine monitor ===<br />
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.<br />
<br />
=== CBM - a menu system for FutureOS ===<br />
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.<br />
<br />
== Developing for FutureOS ==<br />
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.<br />
<br />
=== Z80 Assembler ===<br />
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.<br />
<br />
=== Programming in C for FutureOS ===<br />
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.<br />
<br />
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.<br />
<br />
== Plans for the next years ==<br />
It is planned to support the following hardware during the next years:<br />
* IDE interface ([[CPC IDE]] and [[SYMBiFACE II]])<br />
* [[CPC Booster]]<br />
<br />
== Conclusion ==<br />
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.<br />
<br />
FutureOS is also meant to be used as a disc and file copy tool including a machine monitor.<br />
<br />
== Web links ==<br />
* [http://www.FutureOS.de FutureOS homepage]<br />
* [http://groups.yahoo.com/group/FutureOS/ FutureOS mailing list]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=CBM&diff=2606CBM2006-08-10T11:56:17Z<p>84.151.239.244: </p>
<hr />
<div>=== CBM - a menu system for FutureOS ===<br />
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.<br />
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.<br />
<br />
Web link:<br />
http://groups.yahoo.com/group/FutureOS/files/Source%20Codes/</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=TFM&diff=2604TFM2006-08-10T11:49:22Z<p>84.151.239.244: /* Releases */</p>
<hr />
<div>[[Image:TFM.jpg|thumb|TFM today]]<br />
<br />
'''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]].<br />
<br />
== Releases ==<br />
<br />
* [[FutureOS]]<br />
** [[CBM]] (menu system for [[FutureOS]])<br />
** [[FilmeMacher]] (movie player)<br />
** [[FutureView]] (disc mag)<br />
** [[Gerelakos]] (under construction)<br />
** [[GMSK]] (sprite converter)<br />
<br />
== Groups ==<br />
<br />
* [[FutureSoft]]<br />
<br />
[[Category:CPC scene members]]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureView&diff=2603FutureView2006-08-10T11:48:47Z<p>84.151.239.244: </p>
<hr />
<div>[[FutureView]] is a disc mag published by [[TFM]]. It runs under [[FutureOS]].</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=Gerelakos&diff=2602Gerelakos2006-08-10T11:47:28Z<p>84.151.239.244: </p>
<hr />
<div>[[Gerelakos]] is a Role-Play-Game for the [[CPC]]. [[Tolkin]] and [[TFM]] are working since years on it. First Preview will presented at the [[XzentriX]] 2006.</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=Gerelakos&diff=2601Gerelakos2006-08-10T11:45:56Z<p>84.151.239.244: </p>
<hr />
<div>Gerelakos is a Role-Play-Game for the CPC. Tolkin and TFM are working since years on it. First Preview will presented at the XzentriX 2006.</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=TFM&diff=2600TFM2006-08-10T11:44:51Z<p>84.151.239.244: /* Releases */</p>
<hr />
<div>[[Image:TFM.jpg|thumb|TFM today]]<br />
<br />
'''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]].<br />
<br />
== Releases ==<br />
<br />
* [[FutureOS]]<br />
** [[CBM]] ([[menu system for FutureOS]])<br />
** [[FilmeMacher]] (movie player)<br />
** [[FutureView]] (disc mag)<br />
** [[Gerelakos]] (under construction)<br />
** [[GMSK]] (sprite converter)<br />
<br />
== Groups ==<br />
<br />
* [[FutureSoft]]<br />
<br />
[[Category:CPC scene members]]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=Tolkin&diff=2599Tolkin2006-08-10T11:38:55Z<p>84.151.239.244: </p>
<hr />
<div>[[Image:Tolkin.jpg|thumb|Tolkin today]]<br />
<br />
'''Tolkin''' (Jürgen Strobel) is a graphic artist of the german [[CPC]] scene. He is a member of [[FutureSoft]].<br />
<br />
== Weblinks ==<br />
<br />
[http://www.odity.de Tolkin/Odity-Homepage]<br />
<br />
[[Category:CPC scene members]]</div>84.151.239.244https://oldwiki.cpcwiki.eu/index.php?title=FutureSoft&diff=2598FutureSoft2006-08-10T11:37:17Z<p>84.151.239.244: </p>
<hr />
<div>[[FutureSoft]] has the following members: [[TFM]] (founder, coder) and [[Tolkin]] (graphic wizard).</div>84.151.239.244