thank you all a million times.
]]>This application failed to start because it could not find or load the Qt platform plugin "windows"
in "".
ntk wrote:6/ run "make clean all flash-all"
7/ finish with compiling, no error. image flashed.Hard to believe. make flash-all would try to flash to /dev/ttyACM0 which should definitely fail on windows. Please check again.
ntk wrote:Oh that modification to COM4 in makefile step I did when install driver. Get the COM4. I don't need to write down every time. if compile with new SW I go there change to COM4.
9/ in c:/pm230/client I run "proxmark3 com4"
after doing "lf se" on a tag or just start proxmark3.exe
then proxmark3 crashed.which of the two is true? I am still missing the output of your commands. Please paste the terminal window contents here.
I feel honored and appreciated very much that you look in to this failure, but your time is much too valuable for this fault.
I still have old working code, compiled code some of you wont believe me but I do have, pls just see below.
Older SW version
Even when we at proxmark have no labeling system for unit test, initial test, pre-release test, release test...because we call it open source code.
I used to know a company with more then 10 groups of SW engineers, and total of over 150 engineers using PVCS, working on layers, once *(even twice in duration of 2 yrs) twice they had to revers the Sw engineering for 3wks 4 wks due to heavy instability in the embedded SW release, it shocked every one by gridlock, debugging not fast enough, that decision must be made high up. "Drop it, going back to the most stabile release, and try to catch up", because some engineers hide instabile SW, still labeling, ignore group test result and push it on PVCS, where test engineer knew but not encouraged to give early warning. By your programing quality I knew you work on SW, you can guess financial loss, and mile stone achievement, motivation drop by such a large group must be also when politic was in the game. Only because people are scared to be critical by wing/group politician.
Here is apropos the logs and pics of Appcrash SW release V2.3.0 compile err free with upgradded proxspace
screenshot of app crash imm. after build
and rebuild flash log & first commadnd log file
Again, I feel honored and appreciated very much that you look in to this failure, but your time is much too valuable for this fault.
EDIT:
Dear all leading Proxmark SW creators
With the latest top of the release tree I only wanted to sound an early warning shot, that something has broken the build with official release and on top tree in the compiling of hitag2 src
I still have working code and I am still using iceman latest version for testing and I am still using PM GUI, because I am lazy while testing.
Yesterday I just find a new lf bug. repeatedly reproducible bug, it would be nice to confirm it is still in the top of tree SW. I like to have the latest top of release tree for that purpose, but I am neither dependent on nor desperate for it. My hunch is that bug is still in the lf SW part.
]]>6/ run "make clean all flash-all"
7/ finish with compiling, no error. image flashed.
Hard to believe. make flash-all would try to flash to /dev/ttyACM0 which should definitely fail on windows. Please check again.
9/ in c:/pm230/client I run "proxmark3 com4"
after doing "lf se" on a tag or just start proxmark3.exe
then proxmark3 crashed.
which of the two is true? I am still missing the output of your commands. Please paste the terminal window contents here.
]]>In step 4 to 9 I run "proxmark3.exe com4" from inside the proxspace.
I also just in case download pre-build from 24/4 and leave inside the c:/pm230 and recompile again.
win32
firmware_win
windows driver
But they should not have affect on proxmark3.exe. makefile determine what proxmark3.exe is. If dependent on those extra files, Proxmark3.exe would fail to be built if those files are missing while compiling or linking process.
After re-build I ran exactly step4 to 9 and it crashes too.
]]>https://www.dropbox.com/s/m8sidnstcwsaxal/Temp.zip?dl=0
]]>which environment you are using to build the executable (ProxSpace? Which version?)
which source you are compiling. Official, Marshmellow, Iceman, which release/commit?
Any warnings during compilation or linking?
Or do you use a precompiled binary? If yes, which?
The command you are typing to start the application
The result you get
still error 07
The program can't start because libwinpthread-1.dll is missing from your computer.
I even copy the libwinpthread-1.dll thing in the same directory where proxmark.exe is, no change
Still not working, Marshmellow.
well I can still dig out older SW. I luckily keep an older proxmark-master-ice.zip , proxmark-master-MM42.zip, every few months, they work with the MinGW environment I still have intact.
]]>"I still can't get the GUI to work"
Right?
]]>I know I previously can following forum discussion and test out latest fork from contributor, suddenly I can not any more and have to use windows pre-compiled build or condamned to use official, with tag release only
I recall in Unix when you ran an application you could call a command to check link dependencies, so that you can list up even half a page version number of all components an application would dependent on to run stablely or when you remotely try to trace a fault you could compare the fine differences between systems.
We need something like that here
I recall: It is not true that I haven't changed anything to my MinGW setup since I started PM3. Compare to what I have originally when starting PM3, last year I did change the environment from windows XP to window7 due to a HW failure, then upgrade some fundamental window library components to use certain different SW I have not got on this system, recently I did upgrade from Window7 home premium basic to Window7 SP1 too.#, etc. It is only luck that I have not faced compiling issue sooner.
Thank you to all your help.
EDIT:
speak, think, search and found https://www.dropbox.com/s/7ogccoza5msa0to/dependency%20walker.png?dl=0
But now I am sinking way over my head in this honey pot ...
]]>https://www.dropbox.com/sh/l13tht26y5w5ew2/AABf2smdvbqhU6DkoJoXjzVda?dl=0
search for libwinpthread-1.dll exist more then 6times on my system?