Started by TFM, 07:12, 01 October 10
0 Members and 2 Guests are viewing this topic.
Quote from: Gryzor on 12:37, 01 October 10Nah - my Plus machines are packed and away, while my 6128 is on show...
Quote from: ukmarkh on 09:59, 01 October 10I think FutureOS needs a bit of a makeover... and take advantage of the Plus hardware?
Quote from: ukmarkh on 15:24, 01 October 10Yep, I'm talking Hardware sprites, mixed with the 4096 pallette. Image and presentation is everything? I think
Quote from: Ygdrazil on 13:19, 01 October 10***Better documentation***A list of the the system calls, In a common modern format! (I want to program not making weird file conversions)
Quote from: Ygdrazil on 13:19, 01 October 10Programming examples: A hello world program would be nice!Also small programs showing how to use the system calls...
ORG &8000 ;Hello World - File HELLO.MAX WRITE"HW.64K" ;SAVE assembled file to disc, Autostart at &8000 ;The extension 64K tells, that the program runs in first 64K RAM ;Prints "Hello World" in the files section of the screen;Doesn't disrupt the icon section HELLO LD BC,(&FF01) ;BC contains &DF00 + ROM_select of FutureOS ROM A OUT (C),C ;Switch FutureOS ROM A on between &C000 and &FFFF LD BC,&7F82 ;Selects MODE 2 and Lower ROM = ROM character set OUT (C),C ;Switch it on! LD (RAMCHAR),BC ;SAVE MODE and ROM configuration to OS system variable LD HL,TXT ;Pointer to text, that shall be shown on screen CALL TERM_2 ;PRINT text on screen LD HL,KLICK ;OS call KLICK is used to return to FutureOS with intact icons JP ROM_D ;Switches ON the ROM D and then jumps to HL (here to KLICK) ;Text TXT DB &1E,21,26 ;Control Code &1E works as LOCATE, using 64 x 32 screen mode ;The Y position is line 21, and the X pos. is column 26 DB "Hello World!",0 ;The string is terminated by a 0 byte (or by &1A) ;EQUates of OS variables RAMCHAR EQU &B847 ;located in first 64 KB RAM ;EQUates of System Calls TERM_2 EQU &D48C ;located in ROM AKLICK EQU &FE9A ;located in ROM DROM_D EQU &FF12 ;located in all ROMs
Quote from: CP/M User on 01:27, 02 October 10PDF would be more desirable because it guarantees everyone can view it.
Quote from: CP/M User on 01:27, 02 October 10I guess it's a fair point to say your doing documentation so it works on a CPC - after all it's a CPC Operating System. Perhaps Both is an option?? What I was trying to say is having at least something avilable is better than nothing. I'm sort of banging my head around a bit because I'm Programming Blind by not knowing what I can and can't do in CP/M 2.2. There is some Documentation of CPCWiki, though it's incomplete and I'm not sure if there's stuff on those missing pages which might assist me in understanding what the OS can provide!
Quote from: CP/M User on 23:57, 03 October 10TFM/FS wrote:But back to the roots It was a very good idea from Ygdrazil do ask for source code. Now we got our Hello world. So tell me now which other sources would be interresting for you. Just ask and I will try to provide an example.Something graphical. I posted that routine which draws a sequence of lines from a loop, how would that go in FutureOS? I relies on a few Firmware instructions which I'm presuming FutureOS has it's own set of routines, so how about applying those routines to it?
Quote from: Xyphoe on 01:24, 03 January 11This may be a silly question ... but is it possible to test and play with FutureOS in an emulator? Like WinApe?
Quote from: Xyphoe on 10:25, 05 January 11So do I just need the .ROM or .cpr file - put this in the "ROM" folder in the WinApe install location on my hard disk, then on the "Memory" tab in WinApe settings select it there? And which ROM to select in WinApe Memory tab (eg Upper 0, Upper 1, Upper 2, etc)?
Quote from: Xyphoe on 10:25, 05 January 11If so .... where can I get the .ROM file as I can only find the zipped .dsk file that installs it to a ram-rom box?
Quote from: TFM/FS on 21:58, 05 January 11Ok, I'll create an download, will update this answer here asap.
Page created in 0.086 seconds with 50 queries.