I don't know if I should post this or not. Maybe it doesn't belong here.
Sometimes when I do FASM for DOS in Windows "virtual DOS" if my program has errors FASM crashes or displays random stuff on the screen. This is obviously a Windows problem, not a FASM problem. Therefore, I am not reporting a error.
Sometimes it says "Page Fault" or something like that, and sometimes it displays a hex dump on the screen. This usually happens when I forgot to put a closing ' around a string or something like that.
Why does it do this? This is a weird error with Windows, since it should do what it does in DOS: display an error message and quit.

I should probably use the Windows FASM to avoid this error, and I will do this in the future.

It actually might be some bug in the DPMI-based fasm's interface module. I will try to do some tests to see when it happens.

Well it works perfectly as it's supposed to in plain DOS with no Windows.

Might be some stack misalignment - Windows doesn't like it.

Odd... I don't know much about DPMI, but generally if a DOS program works in DOS but not in the Windows emulator, I would think it's Windows' fault, not the programs fault. BTW, If it helps any, I'm using Windows 95 on a 486 with 16MB memory (I know, it's primitive- I'm planning on getting a MUCH better computer soon).

All this sounds to me like a push-ed single word on stack which is not poped before a jump to some fasm fatal/assembler error handler, where at some point the stack (esp) is simply restored from original esp on entry, and windows doesn't seem to like things like that. Even if the actual ESP is correct. I had similar problems when coding with delphi (integrated assembler) about 3 years ago, but can't find the file right now

wow 486......yikes Stop using that about 9 years ago

lol I have no money but I plan to buy a new one in a couple months