Hi Guys, Thanks for your replies. As you predicted, the app runs correctly if called by the console version of ccnet.
What are the downsides to not running as a service? I don't really have time to refactor the tool to not open its GUI when running in batch mode :( On Aug 29, 1:01 pm, "Ruben Willems" <[EMAIL PROTECTED]> wrote: > Hi > > are you running CCNet as as service? > if so, try running it as console first and see if this works. > > with kind regards > Ruben Willems > > On Fri, Aug 29, 2008 at 1:26 PM, seffyroff <[EMAIL PROTECTED]> wrote: > > > As part of one of my projects build process I need to call a 3D tool > > which opens and converts files listed in a script passed to it. As > > part of this process it opens a Direct3D window, which displays the > > interface of the tool and some progress bars. > > > In the days before ccnet I had a batch file that executed the tool > > with the commandline parameter, and off it will go. > > > I've set up an Executable block to do the same thing as the batch > > file, and it isn't working. The tool crashes when it starts. > > Attaching to it with a debugger suggests that it is unable to create a > > video driver to display the Direct3D window. > > > Is there something special about the execution environment ccnet's > > <exec> task block runs apps in? Does it somehow not have access to > > Windows XP's normal array of standard I/O such as access to DirectX? > > I've searched around to see if the particular method ccnet uses has > > any peculiarities but my google-fu powers appear to be weak.
