I've set up a user-defined tool for which I want to capture the output. I've added a 'DOS Command' type tool and checked the 'capture output' checkbox. Everything works well when I run the tool for a file on a local drive or on a mapped drive.
The problem is when I run the tool for a file with a UNC path(\machinename\share\folder\file). When I do this the tool just hangs. This happens regardless of whether $file has been included as a parameter and regardless of whether an initial folder is specified. This even happens if I specify no parameter - just Command.com as the command.
If I just close the 'Command Results' window no other tools can be run as they are all greyed out on the menu. TextPad must be closed and then opened again to run other tools.
This sort of thing doesn't happen when calling javac.exe to compile a java program with a UNC path.
Has anyone else encountered this? Is this a bug or a system limitation? Any ideas for a work around?
Thanks
capturing output on network file
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard