Win7/32 - TC9.0a
In all cases the dll-file has not been found, but only in the case of commando line window (also über TCMD: Befehle-> "Kommandozeilenfenster öffnen") there is no error message window (what dalai already has mentioned).
Windows Command Prompt cm_ExecuteDOS WinExec() ShellExecute
Moderators: white, Hacker, petermad, Stefan2
That's why I said in both cases that you need to change directory to the program's directory in the CMD window.ghisler(Author) wrote:Command line sets current directory to the directory of the active panel.
This has nothing to do with the program that would complain - Windows does complain because it can't find a required DLL that is part of the EXE's import table; Stefan2 posted the error message.If the program only looks in current directory for the dll, then it will not find it.
I had hoped that my description would be accurate enough now. Can you not just try it with VLC, GIMP, Inkscape or any other program that has been mentioned, and see for yourself?
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
- ghisler(Author)
- Site Admin
- Posts: 48097
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
OK, I have checked it in the debugger now - "Open command prompt" is a very old functions from the beginning of Windows Commander - it uses WinExec() to open %COMSPEC%. After changing that to ShellExecuteExW, it seems to work fine, I get the complaints from cmd.exe when trying to launch vlc with missing dll. No idea why it doesn't work with WinExec...
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
2lucatrv
From my experience: yes, that's exactly what you can expect. And I understand Ghisler's post the same way. It's a pity that this bug has been in TC for so long - maybe you've found the oldest bug in TC.
2ghisler(Author)
Maybe it's time to look through TC's code and replace any other WinExec calls with ShellExecute(Ex). I remember there was a different issue I reported many years ago (regarding files on CD/DVD), although this was caused by missing quotes TC's call of WinExec.
Regards
Dalai
From my experience: yes, that's exactly what you can expect. And I understand Ghisler's post the same way. It's a pity that this bug has been in TC for so long - maybe you've found the oldest bug in TC.
2ghisler(Author)
Maybe it's time to look through TC's code and replace any other WinExec calls with ShellExecute(Ex). I remember there was a different issue I reported many years ago (regarding files on CD/DVD), although this was caused by missing quotes TC's call of WinExec.
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror