I checked and trying to call an x64 dll does indeed produce a file not found error. So that's definitely the leading explanation now if you're not positive it's x86.

No worries though, we've all wasted many an hour missing something obvious