From: Tim on 9 Mar 2010 17:55 Thanks, Ashish. No, no drivers were installed. For individual image acquisition devices, drivers are installed, but IMAQHWINFO doesn't need any acquisition devices to run - it *should* just come back "empty." To add to the confusion, the error 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\test6_1\toolbox\imaq\imaq\imaqmex.mexw32' refers to a file that I have checked and IS THERE! I can see it in my explorer. This is very similar to errors that other people have had and posted, but there hasn't been an answer posted anywhere I can find. I emailed someone who had the problem fixed, but they cannot recall the answer, only that it did get fixed in the end. I think I've run out of places to look, so once more I appeal to the community for any help :) Thanks, Tim "Ashish Uthama" <first.last(a)mathworks.com> wrote in message <op.u9a0z9paa5ziv5(a)uthamaa.dhcp.mathworks.com>... > On Tue, 09 Mar 2010 03:02:04 -0500, Tim <tim.bate(a)gmail.com> wrote: > > > I have created a VERY simple m file, which is as follows: > > > > a = imaqhwinfo > > display a > > > > Even this doesn't work (works fine on my matlab machine, but no other > > after compiling.) Error is still a mex-file error. Included below: > > > > ??? Error using ==> imaqhwinfo at 61 > > Invalid MEX-file > > 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\test6_1\toolbox\imaq\imaq\imaqmex.mexw32': > > The specified module could not be found. > > > > . > > > > MATLAB:invalidMEXFile > > > > Really could use help :) Imaq is a very expensive toy if I can't deploy > > it! > > > > Thanks, > > Tim > > Tim, you could contact tech support for immediate help: > http://www.mathworks.com/support/contact_us/index.html > > The invalid mex file error is usually thrown when a dependency (dll file) > for that mex file is missing/not on path. I would guess that a required > driver is missing on the deployment machine. Did you have to install any > third party libraries/dlls/drivers on your source machine to enable this > functionality? > > Does the compiled app work fine on the same machine that it was compiled > on? If so, its a good indication of the above.
From: Alex on 1 Apr 2010 18:03
Was this problem ever solved? I've been having the same error. Alex |