Foenix F256 / Wildbits/K2 Wiki - User contributions [en]

Tools & Scripts

2024-04-17T06:37:46Z

201.137.102.68: /* Sprite Creation Tools & Scripts */

== F256 Machines Game Development Tools ==

=== Sprite Creation Tools & Scripts ===

{| class="wikitable"
! Tool !! Link !! Notes
|-
| style="white-space:nowrap;"| Aseprite
| style="white-space:nowrap;"| https://www.aseprite.org/
| style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
|-
|f256_sprite_cutter
|https://gist.github.com/digarok/57b096236a7fb1c76efef6cbb9f73a83
|Sprite cutter that cuts a PNG according to line-by-line instructions in a text file. Requires python and the PIL library, install with:
python -m pip install --upgrade pip

python -m pip install --upgrade Pillow
Run with:
python f256_sprite_cutter.py myimage.png mylist.txt sprites.s
where mylist.txt contains a series of lines containing x, y offset, width, name, where it's assumed the width is the same as the height since it's for square sprites supported for the F256xx, such as 8,16, or 32.

The output (named sprites.s in this above example) is a series of hex instructions with a list of hex values of a color picked from the CLUT.

In order to make it compatible with 64tass, I search replaced hex-> .byte and replaced every value I could find by swapping in a $ in front (ie 00 -> $00 and 01 -> $01, etc.)
|-
|Foenix Graphics Toolkit
|https://github.com/econtrerasd/F256-GraphicToolkit
|The Sprite Editor module in the Graphics Toolkit can help you draw sprites of different sizes in the F256 platform and save them as Spr files. The file format is documented in the manual
|}

==== Scripts ====

=== Sprite & Tile Creation Tools & Scripts ===
If you use Aseprite, you can convert your tile drawings to tilesets and tilemaps using the following scripts:

* [[Export Aseprite Tilemap]]
* [[Export Aseprite Tileset]]
* [[Export Aseprite Sprites]] - Will convert sprites to 64tass compatible text file.

Tools & Scripts

2024-04-17T06:36:55Z

201.137.102.68: /* Sprite Creation Tools & Scripts */

== F256 Machines Game Development Tools ==

=== Sprite Creation Tools & Scripts ===

{| class="wikitable"
! Tool !! Link
! --- !! Notes
|-
| style="white-space:nowrap;"| Aseprite
| style="white-space:nowrap;"| https://www.aseprite.org/
|
| style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
|-
|f256_sprite_cutter
|https://gist.github.com/digarok/57b096236a7fb1c76efef6cbb9f73a83
|
|Sprite cutter that cuts a PNG according to line-by-line instructions in a text file. Requires python and the PIL library, install with:
python -m pip install --upgrade pip

python -m pip install --upgrade Pillow
Run with:
python f256_sprite_cutter.py myimage.png mylist.txt sprites.s
where mylist.txt contains a series of lines containing x, y offset, width, name, where it's assumed the width is the same as the height since it's for square sprites supported for the F256xx, such as 8,16, or 32.

The output (named sprites.s in this above example) is a series of hex instructions with a list of hex values of a color picked from the CLUT.

In order to make it compatible with 64tass, I search replaced hex-> .byte and replaced every value I could find by swapping in a $ in front (ie 00 -> $00 and 01 -> $01, etc.)
|-
|Foenix Graphics Toolkit
|
|
|The Sprite Editor module in the Graphics Toolkit can help you draw sprites of different sizes in the F256 platform and save them as Spr files. The file format is documented in the manual
|}

==== Scripts ====

=== Sprite & Tile Creation Tools & Scripts ===
If you use Aseprite, you can convert your tile drawings to tilesets and tilemaps using the following scripts:

* [[Export Aseprite Tilemap]]
* [[Export Aseprite Tileset]]
* [[Export Aseprite Sprites]] - Will convert sprites to 64tass compatible text file.

SuperBASIC

2024-04-01T06:17:24Z

201.137.102.68: /* Ealuating multiple conditions in IF statements */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Evaluating multiple conditions in IF statements =====
SUPERBASIC doesn't have the dedicated keywords AND , OR so you have to use the bitwise operators to evaluate multiple conditions, please consider the following examples:

* AND <code>if (a=1)&(b=2) then c=1</code>
* OR <code>if (a=1)^(b=2) then c=1</code>

This should work as long as you use parenthesis in all evaluated expressions (Since parenthesis makes bitwise operators behave like logical operators).

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
!Colour code
!Colour
|-
|0
|Black
|8
|Dark grey
|-
|1
|Grey
|9
|Light grey (default foreground)
|-
|2
|Dark blue (default background colour)
|10
|Blue
|-
|3
|Green
|11
|Light green
|-
|4
|Purple
|12
|Light purple
|-
|5
|Brown
|13
|Red
|-
|6
|Orange
|14
|Yellow
|-
|7
|Light blue
|15
|White
|}

SuperBASIC

2024-04-01T06:17:06Z

201.137.102.68: /* Ealuating multiple conditions in IF statements */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Ealuating multiple conditions in IF statements =====
SUPERBASIC doesn't have the dedicated keywords AND , OR so you have to use the bitwise operators to evaluate multiple conditions, please consider the following examples:

* AND <code>if (a=1)&(b=2) then c=1</code>
* OR <code>if (a=1)^(b=2) then c=1</code>

This should work as long as you use parenthesis in all evaluated expressions (Since parenthesis makes bitwise operators behave like logical operators).

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
!Colour code
!Colour
|-
|0
|Black
|8
|Dark grey
|-
|1
|Grey
|9
|Light grey (default foreground)
|-
|2
|Dark blue (default background colour)
|10
|Blue
|-
|3
|Green
|11
|Light green
|-
|4
|Purple
|12
|Light purple
|-
|5
|Brown
|13
|Red
|-
|6
|Orange
|14
|Yellow
|-
|7
|Light blue
|15
|White
|}

SuperBASIC

2024-04-01T06:16:06Z

201.137.102.68: /* Ealuating multiple conditions in IF statements */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Ealuating multiple conditions in IF statements =====
SUPERBASIC doesn't have the dedicated keywords AND , OR so you have to use the bitwise operators to evaluate multiple conditions, please consider the following examples:

* AND <code>if (a=1)&(b=2) then c=1</code>
* OR <code>if (a=1)^(b=2) then c=1</code>

These should work as long as you use parenthesis in all evaluated expressions (makes bitwise operators behave like logical).

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
!Colour code
!Colour
|-
|0
|Black
|8
|Dark grey
|-
|1
|Grey
|9
|Light grey (default foreground)
|-
|2
|Dark blue (default background colour)
|10
|Blue
|-
|3
|Green
|11
|Light green
|-
|4
|Purple
|12
|Light purple
|-
|5
|Brown
|13
|Red
|-
|6
|Orange
|14
|Yellow
|-
|7
|Light blue
|15
|White
|}

SuperBASIC

2024-04-01T06:15:24Z

201.137.102.68: Adding how to use OR | AND in IF statements

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Ealuating multiple conditions in IF statements =====
SUPERBASIC don't have the dedicated keywords AND , OR so you have to use the bitwise operators to evaluate multiple conditions, please consider the following examples:

* AND if (a=1)&(b=2) then c=1
* OR if (a=1)^(b=2) then c=1

These should work as long as you use parenthesis in all evaluated expressions (makes bitwise operators behave like logical).

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
!Colour code
!Colour
|-
|0
|Black
|8
|Dark grey
|-
|1
|Grey
|9
|Light grey (default foreground)
|-
|2
|Dark blue (default background colour)
|10
|Blue
|-
|3
|Green
|11
|Light green
|-
|4
|Purple
|12
|Light purple
|-
|5
|Brown
|13
|Red
|-
|6
|Orange
|14
|Yellow
|-
|7
|Light blue
|15
|White
|}

SuperBASIC

2024-03-30T19:13:34Z

201.137.102.68: Better colour table fit

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
!Colour code
!Colour
|-
|0
|Black
|8
|Dark grey
|-
|1
|Grey
|9
|Light grey (default foreground)
|-
|2
|Dark blue (default background colour)
|10
|Blue
|-
|3
|Green
|11
|Light green
|-
|4
|Purple
|12
|Light purple
|-
|5
|Brown
|13
|Red
|-
|6
|Orange
|14
|Yellow
|-
|7
|Light blue
|15
|White
|}

SuperBASIC

2024-03-30T17:41:12Z

201.137.102.68: /* Behaviour of load and bload */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
|-
|0
|Black
|-
|1
|Grey
|-
|2
|Dark blue (default background colour)
|-
|3
|Green
|-
|4
|Purple
|-
|5
|Brown
|-
|6
|Orange
|-
|7
|Light blue
|-
|8
|Dark grey
|-
|9
|Light grey (default foreground colour)
|-
|10
|Blue
|-
|11
|Light green
|-
|12
|Light purple
|-
|13
|Red
|-
|14
|Yellow
|-
|15
|White
|}

SuperBASIC

2024-03-30T17:38:44Z

201.137.102.68: /* Using procedures */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====
The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
|-
|0
|Black
|-
|1
|Grey
|-
|2
|Dark blue (default background colour)
|-
|3
|Green
|-
|4
|Purple
|-
|5
|Brown
|-
|6
|Orange
|-
|7
|Light blue
|-
|8
|Dark grey
|-
|9
|Light grey (default foreground colour)
|-
|10
|Blue
|-
|11
|Light green
|-
|12
|Light purple
|-
|13
|Red
|-
|14
|Yellow
|-
|15
|White
|}

SuperBASIC

2024-03-30T17:37:27Z

201.137.102.68: /* Using procedures */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When executing a <code>proc</code> use the name followed by parenthesis (), even if the proc has no parameters
* Avoid any space between the proc name and the parenthesis, else it will produce an error

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====
The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
|-
|0
|Black
|-
|1
|Grey
|-
|2
|Dark blue (default background colour)
|-
|3
|Green
|-
|4
|Purple
|-
|5
|Brown
|-
|6
|Orange
|-
|7
|Light blue
|-
|8
|Dark grey
|-
|9
|Light grey (default foreground colour)
|-
|10
|Blue
|-
|11
|Light green
|-
|12
|Light purple
|-
|13
|Red
|-
|14
|Yellow
|-
|15
|White
|}

SuperBASIC

2024-03-30T17:37:01Z

201.137.102.68: /* Using procedures */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Using procedures =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* When executing a proc use the name followed by parenthesis (), even if the proc has no parameters
* Avoid any space between the proc name and the parenthesis, else it will produce an error

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====
The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
|-
|0
|Black
|-
|1
|Grey
|-
|2
|Dark blue (default background colour)
|-
|3
|Green
|-
|4
|Purple
|-
|5
|Brown
|-
|6
|Orange
|-
|7
|Light blue
|-
|8
|Dark grey
|-
|9
|Light grey (default foreground colour)
|-
|10
|Blue
|-
|11
|Light green
|-
|12
|Light purple
|-
|13
|Red
|-
|14
|Yellow
|-
|15
|White
|}

SuperBASIC

2024-03-30T17:33:34Z

201.137.102.68:

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
<code>10 if a=0 then x=10</code>
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
<code>10 if a=0<br />
20 x=1<br />
30 else<br />
40 x=2<br />
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />
20 x=1 <br />
30 else <br />
40 x=2 <br />
50 endif</code>

''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Using procedures =====
The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|}

===== Behaviour of load and bload =====
The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
|-
|0
|Black
|-
|1
|Grey
|-
|2
|Dark blue (default background colour)
|-
|3
|Green
|-
|4
|Purple
|-
|5
|Brown
|-
|6
|Orange
|-
|7
|Light blue
|-
|8
|Dark grey
|-
|9
|Light grey (default foreground colour)
|-
|10
|Blue
|-
|11
|Light green
|-
|12
|Light purple
|-
|13
|Red
|-
|14
|Yellow
|-
|15
|White
|}

Main Page

2024-03-30T17:27:42Z

201.137.102.68: Added Utility Software Section, with page for f/manager

<div id="mainpage"></div> __NOTOC__ __NOEDITSECTION__


<div style="margin: 0 0 15px 0; padding: 1px; border: 1px solid #CCCCCC;">
{| style="width: 100%; margin: 0; padding: 0; border: 0; background-color: #FCFCFC; color: #000000; border-collapse: collapse;"
| align="center" style="vertical-align: top;"|
<div style="font-size: 150%;">Welcome to the Foenix Retro Systems' F256x series Wiki</div>
<div style="font-size: 100%; margin-top: 0.7em; line-height: 130%;">Dedicated to the WDC65C02/WDC65C816 or FNX6809 based F256x series.</div>
|}
</div>


{| style="width: 100%; margin: 0; padding: 0; border: 0; border-collapse: collapse;"
| style="padding: 0; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Getting Started|page=Main2/Getting_Started}}
{{NocatBox|subject=Technical Overview|page=Main2/Technical_Overview}}
{{NocatBox|subject=System Maintenance|page=Main2/System_Maintenance}}

| style="padding: 0 0 0 10px; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Software Development|page=Main2/Software_Development}}
{{NocatBox|subject=Utility Software|page=Main2/UtilitiesPage}}
{{NocatBox|subject=W65C816 Processor|page=Main2/65816_Processor}}
{{NocatBox|subject=FNX6809 Processor|page=Main2/FNX6809_Processor}}
{{NocatBox|subject=Game Development|page=Main2/Game_Development}}
|}

Template:Main2/UtilitiesPage

2024-03-30T17:26:10Z

201.137.102.68:

'''Utility Software'''
* [[F/Manager|f/Manager]]

Template:Main2/UtilitiesPage

2024-03-30T17:24:23Z

201.137.102.68: Created Utilities Index Page

'''Utilities'''
* [[F/Manager|f/Manager]]

Template:Main2/UtilitiesPage

2024-03-30T17:23:25Z

201.137.102.68:

'''Utilities''
* [[F/Manager|f/Manager]]

Template:Main2/UtilitiesPage

2024-03-30T17:21:02Z

201.137.102.68:

■[[F/Manager|f/Manager]]

Template:Main2/UtilitiesPage

2024-03-30T17:19:20Z

201.137.102.68: Created page with "f/Manager"

[[F/Manager|f/Manager]]

Main Page

2024-03-30T17:18:00Z

201.137.102.68:

<div id="mainpage"></div> __NOTOC__ __NOEDITSECTION__


<div style="margin: 0 0 15px 0; padding: 1px; border: 1px solid #CCCCCC;">
{| style="width: 100%; margin: 0; padding: 0; border: 0; background-color: #FCFCFC; color: #000000; border-collapse: collapse;"
| align="center" style="vertical-align: top;"|
<div style="font-size: 150%;">Welcome to the Foenix Retro Systems' F256x series Wiki</div>
<div style="font-size: 100%; margin-top: 0.7em; line-height: 130%;">Dedicated to the WDC65C02/WDC65C816 or FNX6809 based F256x series.</div>
|}
</div>


{| style="width: 100%; margin: 0; padding: 0; border: 0; border-collapse: collapse;"
| style="padding: 0; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Getting Started|page=Main2/Getting_Started}}
{{NocatBox|subject=Technical Overview|page=Main2/Technical_Overview}}
{{NocatBox|subject=System Maintenance|page=Main2/System_Maintenance}}

| style="padding: 0 0 0 10px; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Software Development|page=Main2/Software_Development}}
{{NocatBox|subject=Utilities|page=Main2/UtilitiesPage}}
{{NocatBox|subject=W65C816 Processor|page=Main2/65816_Processor}}
{{NocatBox|subject=FNX6809 Processor|page=Main2/FNX6809_Processor}}
{{NocatBox|subject=Game Development|page=Main2/Game_Development}}
|}

Main Page

2024-03-30T17:17:12Z

201.137.102.68: Added Utilities Box

<div id="mainpage"></div> __NOTOC__ __NOEDITSECTION__


<div style="margin: 0 0 15px 0; padding: 1px; border: 1px solid #CCCCCC;">
{| style="width: 100%; margin: 0; padding: 0; border: 0; background-color: #FCFCFC; color: #000000; border-collapse: collapse;"
| align="center" style="vertical-align: top;"|
<div style="font-size: 150%;">Welcome to the Foenix Retro Systems' F256x series Wiki</div>
<div style="font-size: 100%; margin-top: 0.7em; line-height: 130%;">Dedicated to the WDC65C02/WDC65C816 or FNX6809 based F256x series.</div>
|}
</div>


{| style="width: 100%; margin: 0; padding: 0; border: 0; border-collapse: collapse;"
| style="padding: 0; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Getting Started|page=Main2/Getting_Started}}
{{NocatBox|subject=Technical Overview|page=Main2/Technical_Overview}}
{{NocatBox|subject=System Maintenance|page=Main2/System_Maintenance}}

| style="padding: 0 0 0 10px; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Software Development|page=Main2/Software_Development}}{{NocatBox|subject=Utilities|page=Main2/UtilitiesPage}}{{NocatBox|subject=W65C816 Processor|page=Main2/65816_Processor}}
{{NocatBox|subject=FNX6809 Processor|page=Main2/FNX6809_Processor}}
{{NocatBox|subject=Game Development|page=Main2/Game_Development}}
|}