when clicking on files with spaces inside the name, it will open fasmw, but fasmw will say it cannot open "file.asm", then, it cannot open 'with.asm" and fianlly "space.asm".
it does it under win98.
i don't remember under winXP.

i wonder the origin of the bug...

it doest do it with file/open dialog.

edfed,

Probably in association for .asm (within command) file name (%1) isn't enclosed in double quotes.

hem...
i remember ibt ba libttle, buthow can i correct it exactlly?
can a "patch.reg" file correct it?

edfed,

In Windows Explorer, navigate menu to "Tools/Folder Options".
Switch to "File Types" tab.
Scroll down to ASM entry (you may use quicksearch: type a s m quickly).
Use "Advanced" button to customize. Command in "Application used to perform action" for action "Open" should look like this:
"Z:\flat assembler\FASMW.EXE" "%1"

what is this f****n "%1" for ?

lol. i really wonder why "real" informatician complicates so much their lifes.

edfed,

%1 will be replaced by the name of the file you've selected to open.

I can attach RegEdit script, if you prefer to.

it doesnt answer why the need of %1

by default, it is still the case no? when clicking a document, it will open the corresponding programm, and then, put the document name on the PSP.... why does it need %1 to work in this particular case?

that's why i don't understand the need of such complicated design around %X, %G, %something, etc...
for me it is like a sort of brain masturbation from microsoft "geniuses".



indeed, thanks a lot for the tip.

edfed,

%1 is the shell's way to say "insert file name here". It will be placed in PSP iff it is the parameter to .Com or MZ .Exe program (you may associate extension with anything, for example .Exe's associated command is "%1" %* – it simply runs selected file; I saw one virus that changed this association to run itself).

There are %2, %3 and %4 parameters for printto action, and mysterious %D, %H, %I, %L and %S (mostly for IDLIST passing when explorer namespace object used).

It's just interprocess communication, can you propose better way?

yep.
open the source of windows thazt will allow us to modifiy this kind of strange designs.

then now, i understand better the reason of such unbalanced designs....

edfed,

That's mostly the consequences of so-called "backward compatibility" (probably "awkward" is more correct term). Poor design considerations (early in the development of Windows) that made their way up to the current codebase.

edemko: This thread has the answer above. You need to put quotation marks around the open parameter ("%1") for explorer.exe.

I did it with totalcmd.exe.
Other programs open it.

edemko,

If Windows Explorer opens that file OK (you do associate ".txt" with fasm, don't you?), probably this behavior is related to Total Commander settings (I'm not too familiar with it, associations that are internal to TC?).

Created a *.txt1 data type and assigned it to fasmw.exe through TC dialog - registry: "%1".
Created a *.txt2 data type and assigned it to fasmw.exe through standard dialog - registry: "%1".
*.txt had %1, corrected to "%1" - works.
Who put %1
Thanks for the attention.

i love this board