Hi!
this is template for fast creating file conversion utilities. Contains needed set to parse commandline, open files, read symbol, write symbol, close files. You need mostly just to insert your processing code between read and write.
designed as template for WinAsm, but not depends to IDE.
package has also tab2spaces converter can be used as example
Enjoy!

found few problems:

parsecmdline procedure:
- tab in beginnig of command line not checked
- quoted path should be imho returned without quotes
- you should warn caller that passed command line string will get overwritten
- something like abcd"abcd" is considered as one argument abcd"abcd (without ending quote), and abcd"abcd"1234 becomes two arguments: abcd"abcd and 1234.

so... it's not THAT simple.


combined strings:
- dynamic allocated strings really should have size and buffer size stored and used. More work needed here

thanks!
- tabs in commandline - never met them, but possible to change
- parser returns not pathes, but parameters divided with spaces
- warning - ok
- lost of end quote: bug, will be fixed
i decided to return aaa"bbb" as separate parameter for case like
/o:"c:\my docs\out.txt"

-tabs in commandline: i already forgot check well, there is this code:
to treat tabs as spaces - does not it help?
=======
at the beginning!! understand!! - will be fixed - it is because first time i decided do not check for tabs in commandline, but then decided to check, but forgot to do thia in all places. thanks!
=======
fixed uploaded

vid! have you tested it at all or you just figured it all out?

you can see below how i tried your situation on non-changed template (just messagebox inserted)

what about dinamic strings - it is known to me you can use printf instead, or, say, fasmlib - it is my template - anybody can change it to make own more accustomed

just figured. interesting, from the sources i would swear parameter gets cut behind second doublequote in argument.

My personal opinion just is that in dynamic string, current and max length is a MUST-HAVE.

1.you possibly missguided with "search_end" lablel ^) - it is not end of search, it is search of end of the parameter
2.in dynamic string, current and max length is a MUST-HAVE >
you right. but combstr macros is not universal solution. it is fast solution for cases when you do know what you do. although these macros do not check end of buffer, they can be mixed with checking code when you unsure - edi has current position in buffer, top of stack - pointer to first byte beyound end of buffer, [esp]-edi - free space left. look at cs_test example in shoolib - it is used there.
i've been thinking about checking macros - the matter is free time, possible in future

Updated: rebuilded stage of commandline parsing to make it more handy. If it is not clear, but you are satisfied with two parameters you do not need to touch it at all.

Enjoy!

another added on first page - line-by-line converter. here is example to it: assember comments remover. usage: