I have written a batch file that seems to hang when run remotely via the "system" command or via CMD <batchfilename>.
My batch file uses command line winzip to compress a load of files, then calls winzip self extractor via command line to change the zip into a .exe.
When this batch file is run from a normal cmd window it runs perfectly, no gui is ever shown, all quick and proper.
When invoked remotely (from oracle to a C dll that runs the system command with the batch file name), it runs until it gets to the winzip self extractor bit then stops and hangs.
To put another way: if i write another batch file with one line in it "cmd <old batch file name>" and run that, then it hangs also ie puts an entry in the processes list and never finishes.
Does this point to an environmental difference between going into a normal cmd window and running a batch file (and it working) and doing it via the CMD method (and it not working)????