Page 2 of 2

Re: TOS startup sequence.

Posted: Tue Sep 18, 2018 7:16 pm
by troed
exxos wrote:
Mon Sep 17, 2018 11:05 pm
It sparked my interest as if 50Hz is being set, but not the palette data (still black screen) what actually goes on in the code between those 2 things ?
Actually a white border and black screen would indicate all 1s being read from RAM, I think.

Re: TOS startup sequence.

Posted: Tue Sep 18, 2018 7:17 pm
by exxos
troed wrote:
Tue Sep 18, 2018 7:16 pm
Actually a white border and black screen would indicate all 1s being read from RAM, I think.
Would be all zeros for black though wouldn't it ?

Re: TOS startup sequence.

Posted: Tue Sep 18, 2018 7:19 pm
by troed
exxos wrote:
Tue Sep 18, 2018 7:17 pm
Would be all zeros for black though wouldn't it ?
No, think palette. Color 0 is white (border color) and color 15 (low res) is black. So, if all bitplanes are 1s the "graphics" is an image of all palette color 15 = black.

Unless I'm not thinking straight. Have a fever.

Re: TOS startup sequence.

Posted: Tue Sep 18, 2018 7:27 pm
by exxos
troed wrote:
Tue Sep 18, 2018 7:19 pm
No, think palette. Color 0 is white (border color) and color 15 (low res) is black. So, if all bitplanes are 1s the "graphics" is an image of all palette color 15 = black.
Makes sense..

Re: TOS startup sequence.

Posted: Fri Nov 09, 2018 9:32 am
by Petari
Something I noticed during latest TOS 1.04 improving (faster boot, GEM state saves) :
Stays for 1.04 and 1.62.
RAM test executes very fast - under half sec, even with 4 MB RAM. Not real test, more just check for how much ST RAM is inserted/present.
After it comes clear of complete RAM, and code for it is not fastest, strangely in 1.62 even slower than in 1.04. Of course, most time will take with 4 MB RAM. I replaced it with faster one, and it can be that no real need to clear whole RAM - only screen and system area. Probably best to clear lower 512KB because some bootable games which expect it to be clean (all zeros). Regular SW normally starts so, that program's workspace (BSS) is cleared by TOS, unless fastload flag is set (rare case), so not clean RAM will make no problems with it.

More time takes floppy check and initialization even if there is floppy in drive. I think that people with mass storage should have TOS version with skipped complete floppy access - will not need it in most cases. When need, can switch to some regular TOS, with normal floppy access.

Re: TOS startup sequence.

Posted: Fri Nov 09, 2018 10:47 am
by exxos
Sounds like a good idea! :thumbup:

Re: TOS startup sequence.

Posted: Fri Nov 09, 2018 1:51 pm
by TheNameOfTheGame
Well I would like the fast option with no floppy check also, but maybe with the option to hold down a key to check and autoboot from floppy? I still have a few disks to load that way.

Re: TOS startup sequence.

Posted: Fri Nov 09, 2018 2:19 pm
by JezC
TheNameOfTheGame wrote:
Fri Nov 09, 2018 1:51 pm
Well I would like the fast option with no floppy check also, but maybe with the option to hold down a key to check and autoboot from floppy? I still have a few disks to load that way.
Sounds like a good idea to me! :D

(Though the other changes are brilliant anyway...more great work - please keep it up.) :)