ive tried to work a bit with sjasm,
but I'm uncomfortable with the way it works.
I write my programm in a notepad in windows,
save the file,
asm it with sjasm and then use diskmanager to put
the file in a .dsk file and then insert it into Bluemsx
and then run it.

It seems like a hassle......
To complex...

I love the simplicity in wbass2.....

write the program
save state
run program (simple and fast)
if there is an error and the comp. hangs, you simply load state.....
other wise no problem,

it seems I have not found the right way to use Sjasm (or Triasm)

how do you use Sjasm?? do you use windows, a notepad, bluemsx,
and what else???

I use Windows, Kladblok (Notepad), ConTEXT, openMSX, NO$MSX and blueMSX with SjASM. And a batchfile like this:

sjasm -l bigfile.asm
@echo off
if errorlevel 1 goto error
@echo on
dsx a rf2.dsk rf2.com realfun4.msx
c:\emulator\msx\openmsx\openmsx -ext moonsound -diska rf2.dsk
goto end
:error
pause
:end

Or maybe you can try this one that works both for ROM & DSK distributions. To achieve that you only need to name your output (example: output dummy.bin) as .rom or .bin respectively :

@echo off
set name=%~n1
if exist %name%.bin del %name%.bin
if exist %name%.rom del %name%.rom
sjasm -ql %name%.asm
if exist %name%.bin goto :dsk
if exist %name%.rom goto :rom
goto :end

:dsk
if exist %name%.dsk del %name%.dsk
echo 10 CLEAR 0,57343 >AUTOEXEC.BAS
echo 20 BLOAD"%name%.bin",r >>AUTOEXEC.BAS
wrdsk %name%.dsk AUTOEXEC.BAS %name%.bin
openmsx.exe -machine Philips_VG_8020 -ext Sony_HBD-F1 -diska %name%.dsk

:rom
openmsx.exe -machine Philips_VG_8020 -carta %name%.rom

:end

You only need to invoke the script with the name of the program to compile (with or without .asm extension) and let the code work.

About the text editor, I'm using right now ConTEXT, a programmer's free editor and I'm happy with it. I can send you a SJASM highlightning syntax if you want to give a try...

I added tniASM to the Windows context menu for .asm files. It'll run a batch file that will compile the source and output errors and warnings to an error file and then rename the symbol file and delete temporary and other unnecessary (read size=0) files that were created during compile.