run .exe on remote computer

[saudrey]

I have the following problem:

I have written an .exe file with visual c ++ which is supposed to run
on 3 different computers simultaniously (one computer is the host
computer and the other 3 computers are used for a 3d suround demo).
I have written a .bat file which copies the .exe file to the computers
via

xcopy Program.exe \\ip\sharedFolder\ /Y

the problem is now that i can not use

\\ip\\sharedFolder\Program.exe

The console seems to be doing something, since the cursor jumps to the
next line and blinks until I quit the program with <control>c but the
program does not start on the desired computer.

also when i try to change to that directory with

cd \\ip\\sharedFolder

the command promt tells me that

CMD does not support UNC paths as current directory.

Can anybody tell me an easy way to solve this problem?

Thanks in advance

 

[Pegasus \(MVP\)]

I have the following problem:

I have written an .exe file with visual c ++ which is supposed to run
on 3 different computers simultaniously (one computer is the host
computer and the other 3 computers are used for a 3d suround demo).
I have written a .bat file which copies the .exe file to the computers
via

xcopy Program.exe \\ip\sharedFolder\ /Y

the problem is now that i can not use

\\ip\\sharedFolder\Program.exe

The console seems to be doing something, since the cursor jumps to the
next line and blinks until I quit the program with <control>c but the
program does not start on the desired computer.

also when i try to change to that directory with

cd \\ip\\sharedFolder

the command promt tells me that

CMD does not support UNC paths as current directory.

Can anybody tell me an easy way to solve this problem?

Thanks in advance

The "CD" command requires a mapped drive letter. It won't
work on a UNC path.

You should try a system exectuable file on your shared
folder, e.g. xcopy.exe. You will probably find that it
works perfectly well. This puts the focus on your own
executable. It probably expects something that it does not
find when invoked via a UNC path. Add some diagnostics
to your code, then recompile it - you're in an ideal position
to do so!