Is there something that I'm not doing right? Did I miss something in the docs?
I tried to compile it with both fasm (win32 ver) and fasmw, and they caused a stack fault in the kernel. Then I downloaded the DOS release of fasm and tried to compile it with that - it still didn't work - it crashed due to an unspecified error. (I confess I haven't tried in Linux yet). Has anybody got any ideas? (I'll go thru the docs once again now... maybe it needs special reqs...)

post code you can't compile please

or does it happen on any code (in that case - wish u much luck privalov)

I can't tell on what code it crashes because Win98SE is so kind as to warn me that fasm caused a stack fault in the kernel, then blue-screens about an exception in the kernel, after which I say grace and press Reset as nothing else will work anymore.
I still haven't tried to compile it on Linux, but I tried to compile it at school on Win2kSP4 using fasmw and... it worked. So either my computer's gone rebel on me or Win98SE hates compiling fasm for DOS. I tend to believe it's the first one (maybe Win98SE can't provide the compatible DOS 2.0 environment mentioned in fasm.txt, which I skipped at first when the docs as I thought it was the plain-text version of the .pdf).

i bet it some bug / incompatibility in windoze. Privalov should install that version and fix it

I have tested it on Win98SE and I haven't got any problems. Perhaps the origin of the problem is somewhere else.

I'm planning to 'format c:' one of these days, and when I do so I'll try to compile it again and post results if it continues to do crash and I won't be the only one having this problem (maybe it's just my comp that has a problem with fasm).

Hi, Rookie:
I think that you don't need to format your machine and it will waste more and more time on install system. I guest that the issue maybe affort by the below reason:
1.The win98se system files have been inflected by virus.
2.Your machine maybe install some of anti-virus tools. Because fasm will complier the source file and builded a pe format executive file. Some of stupid anti-virus tool maybe block it.
3. Some of system VXDs maybe bad.

So you can strike "F8" key when system reboot period, Then you can select "safe mode" to use fasm. Retry it. It maybe ...OK.

i don't agree with kevin. i think it is always good idea to format drive with windoze on it (check free space before and after)

1) My stupid AV is NAV 2003 (well, until May, when the subscription exipres).
2) I already tried safe mode, i even tried command prompt and safe mode command prompt only
3) A 'format c:' is recommended about once every 4 month if you are a heavy windoze user (c:\windows is twice the size it initially was, even though it was a heavily tweaked custom install, and no components were added since, plus the temp folders are external)
4) I intended repartitioning anyway (I want bigger EXT2 for Linux), so a format cannot be avoided (in my opinion it's safer this way than using Partition Magic or other related software that I can't afford anyway - the AV was won at a competition)
5) The F8 trick is quite difficult under win98 and up (including 2k/XP), as there is no 'starting windoze...' msg. Pressing Ctrl while booting is the prefered method now

Win98SE has DOS in it.
You can alter your boot files and boot to straight DOS.
Not DOS in a BOX or the other DOS options in WIN.
I copied my c:\win\command\
files to C:\DOSWIN\
and made the DOS version of MSDOS.SYS CONFIG.SYS AUTOEXEC.BAT
& made a batch file that alters ATTRIButes & RENames the files for me.
http://bitdog.home.att.net/files/nasmenv.zip
or maybe the latest version of
http://bitdog.home.att.net/files/fasmenv.zip
has the info & batch file.

Straight DOS has many advantages over Win DOS,
for one, straight DOS can alter/move/delete all Win files.........