First off, this may require windows with an nt kernel depending on how you use it. fasmwide compiler is only for version 1.71.16 of the ide. These macros require at least a version with the postpone directive, excluding fasm.asm.
Separate file, multiple compile macros build code to assemble your source when you compile+run (F9) via different fasm flavors. The source must be a different file, local/global file names should all work. Supports fasm.exe, fa.exe, fasm.dll located in the path INCLUDE,'..\' (located via INCLUDE environment variable in your ide's fasmw.ini file), and your current fasmw ide process via sendmessage fm_compile.
Also supports fasm.asm source code overloading as a compiler, compiles fasm.exe everytime. (single compile only, no ide.init either)

compilerun is used to run the output. Output is ran if compile was successful, except fasm.exe and fa.exe who do not check and will always attempt to run.
Fasm.exe and fa.exe also accept commandline and only take one arg instead if only compiling, 2 if also running output.


Besides compiling there are macros to alter your ide. Specifically code to open up all your source files for you so all you have to is open up the build file and hit F9 to setup your environment. If you place the provided folder in your fasmw include folder, the example file will open up your ide's source and the compiler macro files ready for editing.

some additional info:
Include variable is copied and automatically set for all compilers, found via file directive '..\fasmw.ini' where it is parsed from the include environment variable. Don't test the code i wrote it very quickly but it should work if fasmw.exe built the ini file. It does not seem to effect fasm.dll.
Symbols are always dumped for all compilers if possible (not fasm.dll).
Getting local files, '..\', and globals working for everything took a lot of checking and code altering but everything should work as long as you dont exceed the buffers. All compilers should output symbols and code uniformly to correct paths.
Local files are based off of current directory of the build.asm for compile and ide.init. So compile '..\file1.asm', 'file2.exe' will compile file1.asm in build.asm parent folder and output to the building file folder (current). The symbols file will be dumped to the src folder as 'file1.fas'

There is a good chance this is a security setting that is blocking the reads. Your app will need debug privileges to be able to read another processes memory.

I used NtQueryInformationProcess which returns structure containing the unique process id and calling openprocess on that which did not fail. Following calls to ReadProcessMemory using the openprocess handle also returned successful but did not work only acted as if it read 0's. I think its because the id is not made for openprocess/rpm/wpm but its an undocumented function anyway.
I need to try the official way and see if that id works. process32first etc. or see if I can get the window handles using the unique processid.

Run compiled processes in debug mode and open olly (tested with v1.10 and 2.01) only if and when a breakpoint occurs. Debugger is then detached and olly is automatically started via command line to attach to the debugee process and take over.
Eip is changed back to the int 3 instruction that caused the breakpoint and the thread is resumed when olly is hopefully ready to process and focus on the code for you.

Define debug and olly path to enable debugging:

[edit] Updated generic fix for olly v1 or 2 (Only tested with 110 and 201)
and utilizes checkremotebdeuggerpresent instead of a blind sleep and hope olly attached. Still required but almost no sleep necessary for v2, half a sec for v1 since olly still might not be ready to process the breakpoint.
Also fixed a couple bugs.[/edit]

New version, should work with more versions of fasmw.exe. Symbols are dumped for fasmw.exe and necessary symbols are found so it should work with versions that work similar and use the same symbol names. The info is saved for future reference so it doesn't have to be extracted again.
Also tools can automatically be used on assembled sources' symbols dump. Tools are automatically assembled if they are not already (using fasm.exe).

Define DUMP as ALL to automatically dump all info you can for every source file, or else follow a compile command with dump to dump last source. Prepsrc, listing, and symbols tool dumps will be put in same folder as source file. Define DUMPPATH and they will be saved in the source file folder/DUMPPATH/ directory instead.
All tools work fine for me with fasmwide/fasm.exe as the assembling backends. Fa.exe doesn't work with listing tool...probably just needs a setcurrentdirectory fix.
Extracting the necessary symbols from fasmw.fas for fasmwide and ide hooks tested with 1.71.16, .17, and .19 and everything seems to work fine. You should just be able to throw the folder in your fasm include folder and everything should work.