Re: Cannot install catalog file with SetupCopyOemInf() on 64bit OS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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" <SEANN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4A9E42DA-8D0D-4AF9-9233-8824163A5883@xxxxxxxxxxxxxxxx
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.

.

Relevant Pages

  • [origin tree SLAB corruption] BUG kmalloc-64: Poison overwritten, INFO: Allocated in bdi_alloc_w
    ... Bus #0 is PCI ... Performance Counters: AMD PMU driver. ... initcall migration_init+0x0/0x69 returned 0 after 3255 usecs ... calling spawn_ksoftirqd+0x0/0x69 @ 1 ...
    (Linux-Kernel)
  • Re: Alerting - Malicious software removal tool
    ... the proper tool to use when removing malware? ... How many machines were not cleaned by the MS provided tool? ... I have NO connection to any vendors products or tools, ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.security.virus)
  • Re: How to call function from driver in inline assembler
    ... It seems that in calling by this way must be prepared ebx register? ... Or not possible to call other functions than are part of calling driver? ... Yes I agree with you that using inline _asm is not very effective ... push 0x48c ...
    (microsoft.public.development.device.drivers)
  • Re: Button click event handler not called.
    ... so the calling must be marshaled to the ... have you tried your application on other machines? ... For me, I will place a breakpoint in normal Button.Click event handler, ... stack methods one-by-one to see when clicking the button, ...
    (microsoft.public.dotnet.framework.windowsforms.controls)
  • Re: HijackThis Log Help
    ... The point is that if we teach people that we can mostly clean their ... machines, that it's good enough, and they don't feel the "pain", not ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (microsoft.public.windows.server.sbs)