sachaemery@hotmail.com (sash) wrote in message news:...
> Hi all,
> wondering if anyone else has come across this.
> We have a project in CVI 5.0.1 PDS run on WinNT 4.0 sp 6.
> We've received a new third party driver for an interface card.
> The .lib file required for cvi came separate to the install.
> We built the project with the new driver installed, and called
> on the development machine. We can run the .exe fine. The
> driver .dll is called busapi32.dll.
> We transfer the new .exe across to the target machine to replace the
> old .exe (which this morning, with the old driver worked fine), and
> installed the new third party driver.
> On trying to run this new .exe on the target machine, we receive the
> can't f
ind .dll error, but with a slight twist. Instead of saying
> "can't find busapi32.dll" it says "can't find busapi32_cvi.dll"
> Where did the _cvi bit come from?
> We renamed the busapi32.dll to busapi32_cvi.dll and the .exe
> works fine.
> So the question is, why is the run-time engine looking for a different
> filename, when the development machine runs fine with the same setup
> but a develoment version of cvi on it?
>
> Any clues??
>
> Thanks
>
> Sacha
Hi guys,
we've sorted out the problem - it was mis-information and missing
information. Looks like our vendor of the third party .dll built it as
busapi32_cvi.dll, but then re-named the .lib file when they sent it to
us. Our development machine was pointing to the old .exe, hence it ran
OK.
Please ignore this whole thread. Didn't think cvi was a problem
anyway....
Thanks
Sash.
