"Mickael Pointier" < XXXX@XXXXX.COM > a rit dans le message de
But Jon has to verify his entry, it doesn't seem to work on the different
configurations I tried...
On the other hand, Stephane has also started submitting his 3 entries...
(submitter of the year :-)
I take the occasion to remind every minigame writer that after boot-up, an
Oric comes with an undefined memory state in most of $0000-$02FF
This is mostly important for the minigames, because we all want to use many
zero-page locations, and don't have space to initialize them... But, if you
don't initialize those zero-page variables, you will have an unexpected
behaviour on some Orics, because they don't have the same memory contents at
startup ! Even with virtual Orics you can have a different memory content at
startup, for example Euphoric now comes with 3 different "ram patterns",
giving three known screens at startup (vertical lines, horizontal lines, or
diagonal rectangles). So, if you don't want to test all these memory
patterns, please be sure you initialize your zero-page locations or use
already defined ones (those individually initialized by the Basic rom)...
And be warned that this is also true for page 2...
Recently on this newsgroup, we talked about different behaviors of a program
when run with Euphoric.
You all know that location $02DF holds the ascii-code of the last keystroke
(with bit 7 set).
This location is not initialized when the Oric boots, and thus some Oric
have 0 in it, whilst others have $FF.
$FF means DEL key pressed, so if people launch your program by
double-clicking the tape image under Windows, your program will think the
user has pressed DEL (and so maybe skip an intro screen). You can get rid of
these different behaviors by using a single instruction at the beginning of
your program (3 bytes -penalty) : LSR $02DF.
I wish you all the same... Good luck !
(I'm far from having finished too... and with all the hours I have spent, I
hope it won't be felt too boring :-(