Re: [Usbpicprog-technical] win7 testing

[Francesco <f18...@ya...>]

Hi,

2010/2/16 Francesco <f18...@ya...>:
> 2010/2/16 Frans Schreuder <fra...@gm...>:
>>> I've tried the x86 version on Win XP, but no success (it causes an
>>> exception with something like kernel32.dll and then libusb-1.0.dll)
>> very strange. Is it a WinXP without Service Packs installed?
>> Tomorrow (evening) I'll have a chance to test the installer on a
>> relatively vanilla WinXP installation (so far I've tested only on the
>> machine I use for programming and where I did miscellaneous driver
>> tests). I'll let you know what I get.
>>
>> I have tried different XP machines (all SP3) and even wine. They all get the
>> same error.
> I don't know if it could be the source of problems but the machine
> where I tested it is a WinXP SP2 pc.
> Unfortunately today I didn't manage to test on a vanilla XP. I'll test
> it tomorrow.
I've tested it on a WinXP SP3. The installation apparently was ok but
the installer asked me to reboot the machine.
After rebooting however I started upp_wx (with the upp hw not
connected) and I got an unhandled exception with a backtrace identical
to yours. Ouch.
Then I plugged in the upp hw. Windows didn't find the drivers (which
the installer should have installed in the driver store!) and asked me
for one.
I pointed it to C:\Program Files\UsbPicProg\driver and the
installation proceeded smoothly.
I restarted upp_wx and it worked.

This highlighted two problems:
1) libusb/libpthread seems buggy and if the driver is not installed it crashes;
2) dpinst seem not to have installed the driver correctly.

For #1 I think that it is a matter of re-compiling everything in debug
mode and run the app in MSVC and then make a proper bug report to
libusb/libpthread guys with a proper backtrace (with function names).
For #2 the problem is more on our shoulders.
I checked and this is the C:\windows\dpinst.log portion relative to
the installation of the upp driver:

INFO:   ****************************************
INFO:   02/16/2010 17:17:25
INFO:   Product Version 2.1.0.0.
INFO:   Version: 5.1.2600 Service Pack 3
INFO:   Platform ID: 2 (NT)
INFO:   Service Pack: 3.0
INFO:   Suite: 0x0100, Product Type: 1
INFO:   Architecture: X86.
INFO:   Interactive Windows Station
INFO:   Command Line: '"C:\Programmi\UsbPicProg\driver\dpinst.exe"'
INFO:   DPInst is a multi-lingual binary.
INFO:   ****************************************
INFO:   Current working directory: 'C:\Programmi\UsbPicProg\driver'
INFO:   Running on path 'C:\Programmi\UsbPicProg\driver'
INFO:   DPInst.xml does not list the current UI language.
INFO:   User UI Language is 0x410.
INFO:   Install option set: Suppressing Wizard but no OS popups.
INFO:   Install option set: Running in quiet mode. Suppressing Wizard
and OS popups.
INFO:   Install option set: legacy mode on.
INFO:   Install option set: Suppress Add or Remove Programs entries.
INFO:   Install option set: Install all driver packages or none.
INFO:   Found driver package: 'C:\Programmi\UsbPicProg\driver\bootloader.inf'.
INFO:   Found driver package: 'C:\Programmi\UsbPicProg\driver\upp.inf'.
INFO:   Preinstalling 'c:\programmi\usbpicprog\driver\bootloader.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
WARNING:Driver Package 'bootloader.inf' references Catalog file
'c:\programmi\usbpicprog\driver\libusb_device.cat' that cannot be
found.
INFO:   Copied 'bootloader.inf' to driver store...
INFO:   Commiting queue...
INFO:   Copied file:
'c:\programmi\usbpicprog\driver\x86\WinUSBCoInstaller2.dll' ->
'C:\WINDOWS\system32\DRVSTORE\bootloader_F389A405038599F0F7494EC02C7E9AE68D9598EF\x86\WinUSBCoInstaller2.dll'.
INFO:   Copied file:
'c:\programmi\usbpicprog\driver\x86\WdfCoInstaller01009.dll' ->
'C:\WINDOWS\system32\DRVSTORE\bootloader_F389A405038599F0F7494EC02C7E9AE68D9598EF\x86\WdfCoInstaller01009.dll'.
INFO:   Removed driver package from store.
INFO:   RETURN: DriverPackagePreinstallW  (0xE000022F)
INFO:   Returning with code 0x80020000
INFO:   02/16/2010 17:17:28

the warning about the cat shouldn't be a problem (it's a real problem
only if <legacyMode> is not used in the dpinst.xml file).
The problem is that the return code indicates (see
http://msdn.microsoft.com/en-us/library/ms791066.aspx) that
1) a driver package could not be installed
2) the number of driver packages that could not be installed is 2
Now, I realized that there is indeed a bug in the parsing of the
dpinst return code. I should have fixed it now.
However I still don't understand why dpinst failed the installation
and the log above doesn't help (looking at it, except for the return
code, everything seems ok). I need to do some search about this.

Francesco