nedoPC.org

Hmm, the lines shouldn't be showing through. Anyways, I think I might have fixed the scrolling. Try the latest CVS.

No, everything looks the same

Try disabling -O-flags in the makefile, see if that does anything...

Yes, it helped

How far can you optimize without it acting up? There's a pretty big performance jump between -O0 and -O1. But there is very limited performance gain between -O1 and -O2, -O3.

--edit-- I just revamped the scroll function to use the AGDP. Atleast on my computer, it scrolls as fast as xterm =D

Something strange on CVS now - I got segmentation fault in g++

It sounds like it's a bug in g++. What version are you using?

Could you post the output of "g++ -v". Also, when is it crashing? During compilation or linking? If compilation, what file?

Reading specs from /usr/lib/gcc/i486-slackware-linux/3.4.6/specs
Configured with: ../gcc-3.4.6/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux
Thread model: posix
gcc version 3.4.6


Now it's compiled successfully

Another "unofficial" build for Windows is ready:

http://nedopc.org/ternary/tunguska/tung ... _2-win.zip (1.2M)

It includes alternative assembler RASM and some examples for it (including separate program BOOT.A)

I've made a few (backward compatible) changes to the assembler. It now allows uppercase labels and variables, and both the old
@EQU foo bar
syntax, as well as
foo @EQU bar
for defining variables.

What does author think about GPL v3 ?

I know there has been some controversy on the subject, but not actually read up on it. I figured I'll stick with v2 until I get some clarity on the actual differences between the two (I'm fairly certain none of them really apply with Tunguska, but I prefer to be on the safe side)

I'm also still using v2 ...

If this possible to add something like transparrent colour value to graphics mode with 729 colours ? I think this could be very handy for graphics programming.

I don't think there's any benefit from implementing it with hardware, you could simply add a few lines to the painting function, something like

LDA .color
CMP #transparentvalue
JNE $$+4
RST