Are all your binaries (setup.exe, InstallUSBDriver.exe, co-installer DLL,
etc...) built for the architecture (x86 or x64) you are installing on?
-Mike
"SEAN.N" <> wrote in message
news:4A9E42DA-8D0D-4AF9-9233-...
> I'm trying to install Android phone's driver on 64bit machines (Vista &
> Windows7), calling SetupCopyOemInf() from my setup.exe. (To be more
> specific,
> my setup.exe is calling something like InstallUSBDriver.exe after all of
> the
> files are installed.
> And this InstallUSBDriver.exe (VC++ App) is calling SetupCopyOemInf() in
> it.)
> On 32bit machines, everything works fine, but somehow on 64bit machines,
> the
> catalog file is not copied by setupcopyoeminf properly.
>
> Comparing the setupapi.dev.log of 32bit and 64bit, 64bit one is missing
> the
> following line.
>
> inf: Installing Catalog C:\Program Files\***\USB Drivers\androidusb*.cat
> as: oem*.CAT
>
>
> If I go to the "Found New Hardware" wizard and point out the correct path
> to
> the driver files, it works completely fine.
>
> To test this function, I tried another driver on the 64bit machine, but it
> worked totaly fine...
> The difference between these two drivers is only Android driver contains
> co-installer, WdfCoInstaller01005.dll, so I'm kind of guessing
> setupcopyoeminf isn't handling co-installer if OS is 64bit or
> somethiong...
> However, on 32bit machines everything works fine...
>
> Does anyone have this kind of issue?
>
> I don't know whether this is a right place to ask this question, but when
> I
> posted this question to MSDN forum, one of the guy suggested me to post
> this
> over here...
> Any help would be appreciated.
>
> Thanks in advance.
|