wimlib-imagex.exe cannot find libwim-15.dll in path with ;
Posted: Wed Nov 06, 2019 1:09 pm
Hello,
i don't know if this is a known/intended behavior, or unknown bug
if wimlib-imagex.exe (and libwim-15.dll) exist in a directory path name that contain path separator character ;
in this case:
- executing wimlib-imagex.exe directly referencing the full path = fail to load libwim-15.dll
- changing current directory (cmd location) to that path and executing wimlib-imagex.exe = success
- if wimlib-imagex.exe exist in subdirectory in that path (e.g. .\bin\), changing current directory to that path and executing bin\wimlib-imagex.exe = fail to load libwim-15.dll
- adding the subdirectory to PATH environment and executing wimlib-imagex.exe = success
i know this is a very special condition and such paths should not be used, specially with command line tools, but i just accidentally ran into that scenario when i was testing something else
and not to sound ungrateful, but i then used Process Monitor Procmon to test the scenario situations for both wimlib-imagex.exe and 7z.exe
7z.exe always worked, and judging by the captured events, it seems to use a little different steps to locate 7z.dll
i can attach the filtered events for reference if you need
Best regards, and thanks for the great tool.
i don't know if this is a known/intended behavior, or unknown bug
if wimlib-imagex.exe (and libwim-15.dll) exist in a directory path name that contain path separator character ;
in this case:
- executing wimlib-imagex.exe directly referencing the full path = fail to load libwim-15.dll
- changing current directory (cmd location) to that path and executing wimlib-imagex.exe = success
- if wimlib-imagex.exe exist in subdirectory in that path (e.g. .\bin\), changing current directory to that path and executing bin\wimlib-imagex.exe = fail to load libwim-15.dll
- adding the subdirectory to PATH environment and executing wimlib-imagex.exe = success
i know this is a very special condition and such paths should not be used, specially with command line tools, but i just accidentally ran into that scenario when i was testing something else
and not to sound ungrateful, but i then used Process Monitor Procmon to test the scenario situations for both wimlib-imagex.exe and 7z.exe
7z.exe always worked, and judging by the captured events, it seems to use a little different steps to locate 7z.dll
i can attach the filtered events for reference if you need
Best regards, and thanks for the great tool.