@ ARTRAG:
an Italian boy (me) writes in English to another Italian boy (you) who answers in English and the first boy (me) doesn't understand ('cause it's in English)... really funny
Where is the "Italiano" flag?

Also using openMsx it seems improbable that output file will always have the same size...

This project is growing but its end is still far, being alone...
Grazie comunque, e' raro avere alleati in patria

Sorry for my rusty English...

intendevo:
il compilatore in bluemsx non riesce a scrivere nella directory e non hai nulla da compilare in dos...

You can also use the diskmanipulator in openMSX. There's a special text file with openMSX that explains it, it's in the doc directory.
You can work on a virtual disk and export the files to your PC. You can also import files.

@ manuel: sorry for the delay of my answer but I got some problems configuring openMsx to use hd, Dragon's Lair demo has arrived just in time to help me

Thanks for your idea: diskmanipulator command is really great.
I've "imported" my project disks in hda disk and it works really fine.
The only disadvantage is that openMsx (even if throttle off and fullspeedwhenloading on) is slower than RuMsx 0.28 at full speed...
Probably RuMsx is faster 'cause its emulation is by far less accurate than openMsx but if you only need to reduce compile time RuMsx is the fastest I've found till now

If you really want to reduce compile time, try using a cross-assembler

Quote:

Development requires splitting code in many files and I've reached the limit of 110 files per directory.

You can use libraries with L80 or other linkers. Build one or several of them with your files and link against him. That way you use less files and, possibly more important, less files opened at once by the linker.