Which version of FASM? Personally i think you aren't passing argument properly:

i speak about openning asm and inc and other fasmw dependent programms, directlly, without openning fasmw first.
all versions, it fails constantlly, so i shall first open fasmw to play with source.

one precision, i only use the ide versions of fasm, command line is not for me.

how exactly FASMW fails?

win98:
if i click on an ASM file from a path with spaces ' ', normally, the register base points to FASMW, and it's OKAY.
but, the message fasmW sends me is:

could not open file.

then i click on file/open/ => c:\fdjln c ejion n\hui\hrjonrez\erer.asm and it's okay.

that's all.

yep, finally, ithink it's a winbug, cause sometimes it works, like you show, and sometimes it don't.

win$ don't know the memory management.
and i have an other error.

interpret.asm and some other codes are opened with a msdos 8.3 name.
interp~1.asm
sorry for little pollution.
and OZZY, good job, really, i'm sure tomasz will include it in one of the next packages.

FASMINSTALLERUPDATE.EXE, good! can you add an option as save the new .ZIP file? just in case?

I've split this from Ozzy's project so this particular topic can get more attention from others Win98 users that could have the same problem that you.

good.
this problem is strange, as it's not always there. and the problem of dos 8.3 is boring, fasmw don't want to compile if files are in LFN, in win$ and in m$do$.



the next timle i have this bug, i try to make a memory dump, and see with a debugger where it acts. and a screen shot, to proove it of course.

there the bug.

Set up your filetype association properly? Instead of having c:\path\to\fasmw.exe %1 in the registry value, try adding quotes - c:\path\to\fasmw.exe "%1".

If this solves it, it's neither a windows nor a fasm bug, it's a user error

it don't works, then, it can be a shell error. the file name is not well interpreted. it can be in fasmw too. it is amazing.