%WO %WT Parameters
Moderators: Hacker, petermad, Stefan2, white
%WO %WT Parameters
Why not exist %WO %WT Parameters?
-
gdpr deleted 6
- Power Member
- Posts: 872
- Joined: 2013-09-04, 14:07 UTC
Re: %WO %WT Parameters
Uh, i guess for the same reason no %BF parameter exist.
Perhaps start your question with explaining what your idea behind %WO %WT is.
(Unless you want people to engage in sharing their ideas of what you possibly mean by writing %WO %WT.
)
Perhaps start your question with explaining what your idea behind %WO %WT is.
(Unless you want people to engage in sharing their ideas of what you possibly mean by writing %WO %WT.
)Re: %WO %WT Parameters
To a good connoisseur...%O places the current filename without extension into the command line.
%T inserts the current target path. Especially useful for packers.
-
gdpr deleted 6
- Power Member
- Posts: 872
- Joined: 2013-09-04, 14:07 UTC
Re: %WO %WT Parameters
And what should the "W" be about? Do you mean Unicode?
If so, your request is not making much sense, and is based on a misconception how things work in Windows.
When starting a process (running an executable), the command line is usually passed as Unicode. Parsing the command line string and possible conversion from Unicode to local-code page is part of the application start-up code (usually this start-up code is generated by the compiler or linker). In other words: The invoked application deals with the Unicode command line string as it sees fit. It is not the invoker/caller which determines how the called application deals with command line strings. The command line strings (normally) are Unicode to begin with.
If you use a Unicode wmain function (as described here: here: https://docs.microsoft.com/en-us/cpp/c-language/using-wmain?view=vs-2019 ), there will be no conversion from Unicode to local code page taking place, and the problem (which i just speculate about, since i don't really know) should go away...
If so, your request is not making much sense, and is based on a misconception how things work in Windows.
When starting a process (running an executable), the command line is usually passed as Unicode. Parsing the command line string and possible conversion from Unicode to local-code page is part of the application start-up code (usually this start-up code is generated by the compiler or linker). In other words: The invoked application deals with the Unicode command line string as it sees fit. It is not the invoker/caller which determines how the called application deals with command line strings. The command line strings (normally) are Unicode to begin with.
If you use a Unicode wmain function (as described here: here: https://docs.microsoft.com/en-us/cpp/c-language/using-wmain?view=vs-2019 ), there will be no conversion from Unicode to local code page taking place, and the problem (which i just speculate about, since i don't really know) should go away...
Last edited by gdpr deleted 6 on 2020-09-12, 19:57 UTC, edited 1 time in total.
Re: %WO %WT Parameters
but if it were as you say, then why instead exist?
%UL,%UF
like %L and %F, but with UTF-8 Unicode list file (with byte order mark)
%WL,%WF
like %L and %F, but with a UTF-16 Unicode list file (with byte order mark)
-
gdpr deleted 6
- Power Member
- Posts: 872
- Joined: 2013-09-04, 14:07 UTC
Re: %WO %WT Parameters
Read carefully. It says "Unicode list file". The "U"/"W" prefix there is NOT about the command line, but indicating the type of encoding to be used in the list file.
Re: %WO %WT Parameters
I understand, ty.