By default PowerShell doesn't look in the current directory for dependencies, windows wiki might use some tweaks to be more noob friendly.
Long Explanation:
In the windows part of the wiki it says:
You need to download FFmpeg and Node.js and keep them in the same directory as that of this windows binary file.
and:
Hold down the SHIFT key and while holding down the SHIFT key, RIGHT CLICK and select Open Command Prompy Here from the options that show up.
With windows 10, if you shift-click in explorer you have the option to open a PoweShell instead of the old command prompt. And since PoweShell doesn't look in the current directory for dependencies, it will not find node/ffmpeg/mkvmerge. Using the old cmd.exe works just fine.
Some minor changes to the wiki might save windows users some troubles, like:
If you are using PowerShell (and if you are on windows 10 and you open it by shift-right-clicking you are) you must have the dependencies in the path.
If you use the old command prompt you are good to go just by having the dependencies next to the script/binary.
Subject:
By default PowerShell doesn't look in the current directory for dependencies, windows wiki might use some tweaks to be more noob friendly.
Long Explanation:
In the windows part of the wiki it says:
and:
With windows 10, if you shift-click in explorer you have the option to open a PoweShell instead of the old command prompt. And since PoweShell doesn't look in the current directory for dependencies, it will not find node/ffmpeg/mkvmerge. Using the old
cmd.exeworks just fine.Some minor changes to the wiki might save windows users some troubles, like: