Re: [Usbpicprog-technical] win7 testing

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

Hi,

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.

> Did you use the libusb-1.0.dll compiled by me? that one was built using mingw, not MSVC++.
no, I initially had some problems with the stuff which was in
libusb1_win32 folder so I recompiled everything (except pthread whose
precompiled versions were provided by Pete Batard on the win backend
homepage) with MSVC++, made sure to enable release mode and to have
the switch /MD used coherently everywhere....

> Backtrace:
> =>0 0x7b866ffc InterlockedCompareExchange+0xc() in kernel32 (0x0032fc2c)
>   1 0x00333358 in pthreadvc2 (+0x3358) (0x0032fc4c)
>   2 0x10001e22 in libusb-1.0 (+0x1e22) (0x00845a78)
>   3 0x00000000 (0x006020b4)
>   4 0x004188d0 in usbpicprog (+0x188d0) (0x004ab910)
>
it looks to be a problem in pthreadvc2 then.
Maybe I should build a debug version for now so that the EXE which
gets installed can be easily debugged with MSVC++.
Anyway probably in few days the pthread dependency willb e completely
removed from libusb, for the windows backend.

>> I've fixed this now and uploaded corrected installers at:
>> http://usbpicprog.org/downloads/UsbPicProg-amd64-0.3.0.exe
>> http://usbpicprog.org/downloads/UsbPicProg-x86-0.3.0.exe
>
> I guess you didn't build the 0.3.0 version from tags, but the latest trunk
> version. Shouldn't we call it 819 in stead of 0.3.0?
indeed. Will fix it.

>> note however that you cannot run a 64bit OS in a virtual machine
>> hosted on a 32bit OS (only the viceversa is possible)...
>
> Yes you can with virtualbox, as long as you have a 64 bit processor.
interesting, I didn't know...

> But
> anyway, I do run ubuntu amd64 so I won't have a problem.
if the problem persists I can setup a virtual machine, too (in the weekend)..

Francesco