Feedbacks are welcome...Add: in the meantime i observed that the key works for installation only, not for activation... but i installed "ULTIMATE" and the activation resonse was "not valid for vista ultimate"... maybe thats the reason it doesn't work for activation : - {
wref wrote:I have 10 official unused microsoft windows vista RC2 (32 bit edition) product keys , each key will run 10 different machines , so its possible to run 100 different machines with these , if your interested in having one then please email me , wrefmail@gmail.com
Windows 7 Ultimate RC1 x86 64 bit
I confirmed this on windows (6.0.0-rc1-dev-949-gc06e53368) using one of the arduino reference designs which I have included for verification. I also confirmed that it crashes using 5.0.1 (downloaded from the website) and HEAD of the 5.0 branch as well so this is a major regression because I've used this eagle project in the past for testing purposes without issues. Here is the really fun part, all of the crashes above were release builds. 64 bit debug builds work fine. 32 bit debug builds crash. I'm not sure if this a bug with kicad or the msys2/mingw build tool chain. Does anyone have a msvc build that we can test to confirm this theory?
I figured out my issue and I suspect it is the same issue for the windows packages. Apparently the msys2 project made a bad binutils release for mingw32 and mingw64 and a bad release of gcc 7.3.0 on mingw32 which they pulled from the packages list once they discovered this issue. Unfortunately, if you upgraded during this should period, you have the broken packages installed. Once I down graded these packages using `pacman -Syuu` and rebuilt kicad, the bug is resolved. Would our windows package dev please check if this is the case for our windows builders? Below is the output from pacman when I performed the downgrade so you should be able to check the builder setup to see if the offending packages are installed on the builder.
The current 5.0.1-3 installer build still crashes. My local builds (32 and 64 bit) of the head of the 5.0 branch work as expected. I know that the windows package builder was recently changed but I'm not sure that it is using the same build tool and dependency library versions that I am so there still could be issues with the 5.0.2 release windows installers. 2ff7e9595c
Comentarios