I have a little project (about 22.4Meg of source code, but about half of that is includes and resources) which reports almost immediately even with fasmw set to Memory: 65536.

What can I do?

Read the manual. 65536 means 64 MiB, not a much for serious project.

If you use the console version then more memory is allocated by default.

I did read the manual

I assumed that 65536 meant 64Kb actually... but that is as high as it will let me input.

Happy to use the command line version, and slightly wonder why fasmw.exe doesn't just call that when you ask it to "compile" (assemble and link as far as I'm concerned) in the first place.

I have now found that I can actually just type a number far in excess of those available on the drop down, and things proceed much more satisfactorily.

Perhaps just a note to the project that 65536 being the maximum on the drop down is a little slender.

You're allowed to write your own amount of memory in FASMW, the drop down list is just a set of predefined memory sizes.

Yes, but pretty low defaults IMHO.

I started out with 131072, which was great. Did some Macros to get around basic syntax differences between my old Assembler and FASM, and then found that (and this isn't mentioned in the manual either) if you use the 5Fh style notation of a hex number it only accepts it as a hex number if the most significant nibble is <= 9, otherwise you have to either add another (more significant) 0 or use the 0x or $ notation. Otherwise it considers the constant to be a label.

Couldn't fix that with a macro (that I could think of) so I did some S&R work and am busy cleaning up the mess of any label that happened to have only the letters A-F preceding an H... like, anything with "_char_" in it becoming "_0xcar_" etc... and several FPU instruction got messed up too. :S

Anyway, I've had to increase to 524288 to keep it building and finding S&R corruptions, but other than that, it's still going quite well, all things considered.

Seems pretty quick, and I'm hoping I can add includes which will let me use conditional compilation to target other platforms besides Win32.

Thanks guys.

bobsobol: All numbers start with a numeric character with the exception of the '$' syntax. This is mentioned in the manual.

Something like bach will be always interpreted as a label because it doesn't start with a number. I am curious to know what assembler you used that interpreted bach as a number?

The very early versions of fasm (prior to 1.04 release) were using case-sensitive format for hexadecimal numbers that didn't require a 0-9 digit as first character. Thus with fasm 1.0 "BACh" was interpreted as hexadecimal number, but "bach" was still a label.

Anyway, since the 1.04 release fasm follows the widespread standard that numbers have to start with 0-9 character.

I think if I had come across fasm during the time before 1.04 I would have baulked at the idea of numbers starting with letters! Luckily I came in later and didn't have to suffer such "problems". Well, except for the time when a dot (.) was allowed to start floating point numbers. I remember when .e and .f would be interpreted as numbers.

Yea... well the MASM copy I have accepted it, but a lot of the code comes from a Reverse since the source was "lost"... the DA produced code like this Which compiled okay with a little coaxing on the linking side... but it's been used as source an man handled considerably, and FFFFFFFFh has remained. I prefer the 0xFFFFFFFF form anyway, so I just made a little program to Search and replace them all in the end.

GREP and SED style S&R just gave be too many PUS0xH, 0xADD, FEX0xCG type mis-replaces. XD I'm sure a GREP or SED GURU could fix it, but I program... so I just wrote an exe. lol