Different behaviour when running exe from command prompt than in windows
- by valoukh
Forgive me if I'm not using the correct terminology here but I'll try to explain the issue I'm having as best I can!
We use a program that allows you to view video footage from several cameras, and it works in such a way that when it is opened it then automatically loads several video files within its interface. These video files are stored in a subfolder, e.g. "videos\video1.asf", etc. I didn't create the program so I can't say what method it uses to open the files.
The files are stored on a network server and are being accessed via a share/UNC path.
When the file is run from windows explorer (by navigating to the
network share and double-clicking the exe), it works perfectly.
When the file is run via the (elevated) command prompt (e.g. by
typing the \server\path\to\file.exe) it opens, but the corresponding
video files do not load.
I am trying to create a script that launches the program via the command prompt, so the first step is finding out why the two actions above have different consequences. Any advice on how running executables from the command prompt could produce a different result would be greatly appreciated.
Thanks