[ Post removed by author. ]

sigh .... 1 years worth jeez. You should keep backups

Well, the PocketPC is not an x86 device - so that is the problem. FASM doesn't generate ARM code ...

Different pocket devices have different processors. SHARC, ARM and others. You need to make many versions of your software to allow it to run on many pocket platforms.

Funny you should mention that, I have almost completed my ARM code module for FASM. When I get it working nicely I'll post it on this board somewhere.

Oh, I'll definitely be interested! I would like to make Reva (my Forth code) run on an ARM-based PocketPC...

[ Post removed by author. ]

[ Post removed by author. ]

FASM's current support is only for x86 (including its 64-bit variant) but the macros are powerful enough to translate any code, the only problem remaining, someone needs to code it.
When people program for different architectures, they usually use C (or variants) which has a LOT of include files so the output can be any processor and any operating system. Of course all this is possible with FASM, but like I said said before someone's gotta make the includes/macros that support it.

Be careful what you claim, FASM macros are good but to say that any code can be translated is going too far, some code cannot be translated with macros. The normal ARM code uses the "#" to encode literals, FASM will happily concatenate when it sees "#". Another example is labels beginning with a digit are not supported.

I didn't claim you can use any syntax rather you may use FASM-like syntax to assemble ARM. You just need to make the includes or macros that mimic the way one expects. C being an example doesn't change its syntax when coding for different architectures - why should FASM?!

Becuase programs in C are compiled on different processors. When compiled on ARM, the libc with opcodes for ARM will be used, and so on. Using FASM is using only one and specific opcodes already, not dependencies to some library

Okay, sorry about that, I misunderstood. In that case I think you are correct. But that macros needed would be quite large and cumbersome.

You may want to look a the Compact Framework. Here's a link to an opensource group supporting the Compact Framework: http://www.opennetcf.org/forums/

if someone still hits this thread, working WinCE executable can be found here: http://board.flatassembler.net/topic.php?t=4191

also here is interesting article on winCE drivers: http://www.embedded.com/story/OEG20010618S0083