How I can translate sources for MASM/ArrowSoft Asm to FASM?

EDIT by DOS386 : corrected subject to match post content

Why do you want to? Do you absolutely need to use FASM?

JWasm is intended to be MASM v6 compatible (or v5 if you use -Zm):

http://www.japheth.de/JWasm.html

I'm not saying it isn't possible with some macros for FASM, but you'll have to be more specific which parts you want to translate.

P.S. FASM does not support OMF/OBJ.

Yes , I absolutely need to use FASM.
I have the files MASM.exe and LINK.exe but I prefer to use FASM.
I want to translate the files created with BASM286 (Basic2MSAsm translator by Kevin Diggins, you can found it at the bottom of this page http://www.bcxgurus.com/ )

No Answers?

There are several threads on this subject, distributed around all subforums here. There is no 100% automatic converter (yet ?), the 2 are simply ways too different. One thing is NOMYSO - it reportedly converts from MASM (or TASM ?) to NASM, and it's PEARL, not an executable, and it didn't work for me If you post some offending code, you might get some help (as happened in the past). Drop "assume" "offset" "ptr" "addr" "proton" , put prefixes into the brackets [es:bp-4] , drop all the offending directives, ... There are also some MASM emulation macro's (HLL, proc, proc16 ? , assume ? , struct ?), but they are part of Win32 includes, not necessarily/well usable for 16-bit real mode code.

I have done large translations of masm code to fasm and I find it easy to take the disassembled dump from Ollydbg (in IDEAL mode) and then paired it with the sources in a spreadsheet in order to recover labels and variable names. It also have the advantages of get rid of those high level constructions that I dislike and to get some optimizations that the assembler does.
Unfortunately, this process is not suitable for automation.

Using this approach, it's about 2 hours per 1000 lines of masm code (depending on the quality of masm sources)

Thanks for the answers.
I think that the best solution is translate the code templates of BASM286 from MASM to FASM and compile again the Compiler/Translator again.

Besides just wanting it, why would you need to use FASM here? I'm not just whining or picking on you, it's just that FASM isn't really intended to be 100% MASM compatible and especially doesn't support 16-bit OBJ linkable output. Besides, if you want a 386+ BASIC, try FreeBASIC, it's probably easier to use!

There is nothing like the right tool for the right job.

And this is nothing like the right tool for the right job.