Guillaume Tello
2011-01-19 17:23:25 UTC
Hi again,
Here are two more things:
1) I disassembled and rewrote a part of NOVACAL (the screen driver for
Calamus originally for NOVA graphic cards). It was mostly necessary when
running in 16 bits mode on the CT60+CTPCI because there, Calamus used to
display weird things.
So, Calamus can now run on every 16 bits mode (either 15 or 16 bits
used) and every endian (Big or Little).
NOVACAL can also be used in 24 or 32 bits if the encoding is not the
Calamus native one.
2) Once NOVACAL ready, I experienced problems with Calamus at startup
when loading modules, always the same problem with the instruction cache
not updated. I was about to patch Calamus when the idea of a universal
launcher came: I called it RUNME1ST.
With it, you can run any program and it flushes the caches each time a
file is loaded by the program (supposing it can be an executable module).
I added a delay option: after this delay, the caches are not modified
anymore (better performances) supposing that modules are generaly loaded
at start.
Well, it's the same idea as the "5s" delay with the CPX CT60 but it only
slows one program when this one loads one file, and not the whole system.
I'll add this tonight on my page.
Guillaume.
Here are two more things:
1) I disassembled and rewrote a part of NOVACAL (the screen driver for
Calamus originally for NOVA graphic cards). It was mostly necessary when
running in 16 bits mode on the CT60+CTPCI because there, Calamus used to
display weird things.
So, Calamus can now run on every 16 bits mode (either 15 or 16 bits
used) and every endian (Big or Little).
NOVACAL can also be used in 24 or 32 bits if the encoding is not the
Calamus native one.
2) Once NOVACAL ready, I experienced problems with Calamus at startup
when loading modules, always the same problem with the instruction cache
not updated. I was about to patch Calamus when the idea of a universal
launcher came: I called it RUNME1ST.
With it, you can run any program and it flushes the caches each time a
file is loaded by the program (supposing it can be an executable module).
I added a delay option: after this delay, the caches are not modified
anymore (better performances) supposing that modules are generaly loaded
at start.
Well, it's the same idea as the "5s" delay with the CPX CT60 but it only
slows one program when this one loads one file, and not the whole system.
I'll add this tonight on my page.
Guillaume.