Forums

Help

cmd.exe launched upon ComputeProgram.Build()

I'm just getting started with Cloo (very useful so far!) trying to integrate some OpenCL into a program. However, I'm finding that every time ComputeProgram.Build(null, null, null, InPtr.Zero) is executed, a command window (cmd.exe) flashes open and closed. There doesn't appear to be any text in the window. This is of course undesirable.

I wondering if I'm doing something wrong that's causing cmd.exe to be opened and closed.

I am indeed. Thank you for that information. Not the best news, but good to know that it's a known issue. If you have a link to a thread on the ATI forums regarding this issue, that would be much appreciated.

That's odd. I just confirmed that the Clootils samples work with v2.01 but not 2.2. Could you run the tests with the new release, please? I'd really like to find out what's going on. Where I'm sitting, ATI Stream v2.2 makes Clootils crash in such a way that all the catch blocks are ignored. It jumps right into the OS. For the record: bugs like these cannot be caused by Cloo (i think). It is almost always buggy drivers.

As I pointed out before, Clootils hacked its way around this problem by preallocating a console. But with this Stream release, it seems they've changed some internal bits and the workaround is now broken. That's my bet.

Well, you're either lucky or the SDK without the Catalysts is useless because even the simplest example fails. This piece (which runs fine on a previous version) just blows regardless of being run as a console app or not:

yes the console problem is there since a long time and it's still there, maybe they don't see it as a big problem. many other issues have been solved so we should wait for the next version and maybe they will solve this issue too.
about the issue with the new sdk i am not completely surprised that you have problems using the ati stream sdk on a system without an ati video card. i've tried that too on my notebook (with a geforce 8800m gtx) without much success. I think that there's a problem with opencl.dll being overwritten or something similar.
do you have an nvidia card? why don't you use the nvidia sdk?

What struggles me is that code like this used to work on a previous version of Stream and the same HW. Another interesting thing is a complex example (raytracing), which works regardless. Oh well, I'll just wait for v2.3 or so. I only hope it won't make me hold back Cloo 0.8.0.

Yes I do. But I won't have access to my regular dev machine until next week. So I'm using an old notebook (and ranting :) ATM.