Compiled Windows clients - always up to date

HighPressure · 2018-07-27 19:42:23

hey gator long time not seen!

just tried your latest build from google drive.
I have a brand new fresh prox from kickstarter funding.
I recognized that the device first appears as COM3 and after flashing it aligns with your batch files on COM5.
just in case you want to have an extra error routine checking if it failed

very good work thanks a lot!

gator96100 · 2018-07-30 02:08:15

I did update the ProxSpace environment to msys2 and need someone to test it. https://github.com/Gator96100/ProxSpace … /msys2.zip
With msys2 comes a package manager and the ability to easily update all installed packages.
The initial download size will be smaller than before, but after the automatic install of all required packages the size will be about 9GB.

gator96100 · 2018-07-30 17:33:45

I pushed some fixes to the msys2 branch and added support for x86-64 compilation. When compiling with x86-64 gcc 8.2 is required, because of a bug with avx instructions under Windows. I did compile gcc 8.2 and uploaded the packages to https://github.com/Gator96100/ProxSpace-Repo. When ProxSpace is started in x86-64 mode for the first time it will automatic install gcc 8.2. I am pretty sure gcc 8.2 is not officially supported for compilation of the proxmark client, therefore ProxSpace x86-64 is highly experimental.

Last edited by gator96100 (2018-07-30 17:39:04)

gator96100 · 2018-07-31 00:23:16

The new msys2 ProxSpace is almost finished, which means I can create x86-64 builds(hardnested can reach the memory limit for 32 bit applications). Should I separate the uploads for x86-64 and i686 or combine them in one zip and does anyone still need i686 at all?

gator96100 · 2018-08-04 01:44:22

All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.

iceman · 2018-08-04 04:54:13

Awesome!

zhuminggang · 2018-10-30 16:05:07

gator96100 wrote:

All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.

In all precompiled builds,FLASH - All.bat,FLASH - Bootrom.bat,FLASH - fullimage.bat. This three batch files missing 0x0d,Can not run in windows OS,it ought to be 0x0d,0x0a. please check carriage return and line feed, for your OS is Linux.

gator96100 · 2018-10-30 21:31:03

zhuminggang wrote:

gator96100 wrote:
All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.
In all precompiled builds,FLASH - All.bat,FLASH - Bootrom.bat,FLASH - fullimage.bat. This three batch files missing 0x0d,Can not run in windows OS,it ought to be 0x0d,0x0a. please check carriage return and line feed, for your OS is Linux.

I don't get it what you are trying to say. Are saying that the .bat files are missing a carriage return at the line end? On Windows a carriage return is not needed. You would be the first one to have problems with the .bat files.

zhuminggang · 2018-10-31 04:30:00

gator96100 wrote:

zhuminggang wrote:
gator96100 wrote:
All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.
In all precompiled builds,FLASH - All.bat,FLASH - Bootrom.bat,FLASH - fullimage.bat. This three batch files missing 0x0d,Can not run in windows OS,it ought to be 0x0d,0x0a. please check carriage return and line feed, for your OS is Linux.
I don't get it what you are trying to say. Are saying that the .bat files are missing a carriage return at the line end? On Windows a carriage return is not needed. You would be the first one to have problems with the .bat files.

My laptop OS is windows 10(Version 10.0.17763.55),when i run FLASH - All.bat,many error message appear. Edit the batch files and add 0x0d each line, all is ok. Please test!

'0' is not recognized as an internal or external command,
operable program or batch file.
'ho.' is not recognized as an internal or external command,
operable program or batch file.
'!!!!!!!!!!!!!!!!!' is not recognized as an internal or external command,
operable program or batch file.
'│' is not recognized as an internal or external command,
operable program or batch file.
'ULLIMAGE' is not recognized as an internal or external command,
operable program or batch file.
'│' is not recognized as an internal or external command,
operable program or batch file.
'l' is not recognized as an internal or external command,
operable program or batch file.
'ill' is not recognized as an internal or external command,
operable program or batch file.
'will' is not recognized as an internal or external command,
operable program or batch file.
'ou' is not recognized as an internal or external command,
operable program or batch file.
'?' is not recognized as an internal or external command,
operable program or batch file.
'│' is not recognized as an internal or external command,
operable program or batch file.
'│IF' is not recognized as an internal or external command,
operable program or batch file.
'ho' is not recognized as an internal or external command,
operable program or batch file.
  ==========================================================================
Press any key to continue . . .

.

Last edited by zhuminggang (2018-10-31 04:32:52)

gator96100 · 2018-11-04 23:45:22

I have tested multiple Windows 10 and Windows 7 installations and all are working. Windows does not care about carriage returns are you using a other than default terminal?

iceman · 2018-11-05 09:34:34

looks like it didn't run the intial first run, where it downloaded / installed everything, and it that case I doubt he has compiled...

gator96100 · 2018-11-05 12:16:00

iceman wrote:

looks like it didn't run the intial first run, where it downloaded / installed everything, and it that case I doubt he has compiled...

It is about the precompiled builds and not ProxSpace, there is not initial setup. The .bat files are not working for zhuminggang because a missing carriage returns, but on Windows there is no need for it. The only reason I can think of what causes this isse is an other than default terminal.

iceman · 2018-11-05 13:56:17

aha, ok, then I stand corrected

Kieths · 2019-01-22 06:56:32

Hi gator,

First, I appreciate your taking time to compile official releases for Windows, as I've run into problems trying to do so.
I recently pulled down the precompiled official-64-20190117, and it appears to be based on v3.01.

Will there be a Windows 64 precompiled based on the newer v3.10 released on October 27, 2018, or has that had problems compiling on Windows?
I ask, as the newest AndProx app specifies this version (though it may accept the prior release).

gator96100 · 2019-01-25 17:58:09

Kieths wrote:

Hi gator,
First, I appreciate your taking time to compile official releases for Windows, as I've run into problems trying to do so.
I recently pulled down the precompiled official-64-20190117, and it appears to be based on v3.01.
Will there be a Windows 64 precompiled based on the newer v3.10 released on October 27, 2018, or has that had problems compiling on Windows?
I ask, as the newest AndProx app specifies this version (though it may accept the prior release).

There was a bug with my git repository, only the version string was affected. Although is said v3.01 it was v3.10.
I did fix the problem, thanks for reporting that bug.

Last edited by gator96100 (2019-01-25 17:58:58)

Kieths · 2019-01-26 06:02:24

Thanks so much!
Looking forward to checking the PM3 with updated firmware on my Android device.

Kieths · 2019-01-26 07:44:32

Issue: One of more commands under PM3UniversalGUI fail to respond / provide expected output.

Steps to reproduce (example 1):
a) Select current COM port
b) Select PM3\lf\read (results: Top panel: "Sending bytes to proxmark failed - offline", other panels blank)
c) Click Run (button on right, center) (results: No change to display. Attempted to scan a card, PM3 device timed out, auto-reset after 35 seconds).

Steps to reproduce (example 2):
a) Select current COM port
b) Select PM3\lf\read (results: Top panel: "Sending bytes to proxmark failed - offline", other panels blank)
c) Click Run (button on right, center) (results: No change to display. Attempted to scan a card, then:
i) Press PM3 device button to reset/stop read. (note: No change to display)
ii) Select PM3\hw\ver, and click Run (button on right, center) (results: Item #2 below, output of "hw ver").

Conclusion: Based on the above results, it appears that:
A) PM3UniversalGUI does not display output directly following the "lf hid read" command, though it does appear to trigger and perform the operation with output to buffers
B) Issuing the "lf hid read" command without manually stopping/resetting the PM3 device after a short period (>20 sec) appears to result in a time out and auto reset of the PM3 device at approx. 35 seconds (note: this behavior is not observed under the proxmark3.exe terminal, which appears not to have any such timeout limitation)

PM3 System Configuration:
=========================
1) Release: official-64-20190125-1511ea28a8cc647a6fc462e9c182622a43df1318

2) Output of "hw ver" (after issuing the command, "lf hid read", scanning several swipes with no output, then pressing button to reset; TAG ID has been obscured):

proxmark3> hw ver
#db# TAG ID: 211cxxxxxx (xxxxx)
#db# TAG ID: 211cxxxxxx (xxxxx)
#db# TAG ID: 211cxxxxxx (xxxxx)
#db# TAG ID: 211cxxxxxx (xxxxx)
#db# Stopped
Prox/RFID mark3 RFID instrument
bootrom: master/v2.2.0-271-g910ad54-dirty-suspect 2016-12-19 18:01:16
os: master/v3.1.0-52-g1511ea2-suspect 2019-01-25 16:37:01
fpga_lf.bit built for 2s30vq100 on 2015/03/06 at 07:38:04
fpga_hf.bit built for 2s30vq100 on 2018/11/28 at 08:33:11
SmartCard Slot: not available

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 202541 bytes (77%). Free: 59603 bytes (23%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

3) Proxmark3 (Original), LF Antenna (GeZhi)

4) Windows 10 Pro x64

Last edited by Kieths (2019-01-26 07:58:31)

iceman · 2019-01-26 07:57:45

Please don't hijack threads. This thread is about the compiled pm3 client, create a new thread instead.

Kieths · 2019-01-26 08:14:08

I apologize for misinterpreting.

I was providing a report for an error found in use of the precompiled build, which included PM3UniversalGUI, based upon the first post in this thread. I am uncertain where the error rests, in the compilation, or in the included PM3UniversalGUI utility

gator96100 wrote:

If you ran into an error during the usage of a precompiled build please post following information...

I will create a new thread. Thank you.
Feel free to remove the report, and our responses thereafter, as appropriate.

Last edited by Kieths (2019-01-26 08:17:08)

iceman · 2019-01-26 08:30:39

Don't worry. Just trying to keep the forum clean and easy to follow. Usually many subjects overbridges eachother.

Kieths · 2019-01-27 04:12:44

Hi Gator,

In the newest compiled collection, the GUI utility: PM3UniversalGUI.exe (no version # under Properties/Details) does not open/run under Win10 x64.
Compilation version: official-64-20190126-1511ea28a8cc647a6fc462e9c182622a43df1318

Previous compilation version "official-64-20190117-d3c606574f90881daab8585659c18223a7a3c2c3" included PM3UniversalGUI.exe (file version 1.1.1.0), which ran, but seemed to have some parsing issues.

I've downloaded the utility author's latest release bin (circa 15/Sep/2018), and it also does not run (file version 1.1.2.0).
This version also does not run, but has a very different error. I will advise the GUI utility writer of the test results, along with my OS version.

Will advise any updates to help with future compilations.
Thanks for your efforts in providing the compilation!

Last edited by Kieths (2019-01-27 08:14:18)

Petrolhead · 2019-01-29 23:19:29

Same here as Kieths.
I have two pc's, home and a pro edition x64 version 1803 build 17134,556 intel i7 cores.
Both official and iceman's compiled collection. (latest two releases dont start on PM3UniversalGUI.exe)

*Thank you gator96100 for the fix *

Last edited by Petrolhead (2019-02-09 07:15:34)

gator96100 · 2019-02-08 18:04:59

The autobuild script did download the PM3UniversalGUI.exe in some sort of HTML format, I did fix it.
I also had to upgrade my google drive account, because I ran out of space and the latest builds could not be uploaded.

Kieths · 2019-02-08 20:55:51

I look forward to testing tonight, thank you!

Petrolhead · 2019-05-01 16:48:03

Tried the few of the latest (rdv40-64-2019****) but getting variuos problem with each version.
after version rdv40-64-20190302 it happens
Some of them the window dont start (getting a cmd and window) other it just shut down direct after start.
rdv40-64-20190501 I cant check version or ping the proxmark and tune check (gets loop problem) but reading mifare does work (strange)

Im sorry that Im not giving you exakt the fault (but each version has it own problem)

Im back on rdv40-64-20190302 and it works great, all others after dont.
Sorry for my poor troubleshooting. (on win10 1809 and got panic that I did brick my pm3)

Last edited by Petrolhead (2019-05-01 16:56:48)

gator96100 · 2019-05-01 19:31:50

I am sorry, but I do not understand the problem.
Please describe the exact step you have done.
Adding the line "pause" in Go.bat should prevent instant closing of the cmd and maybe there is an error message.

Petrolhead · 2019-05-01 21:21:39

Appreciate that you read and answerd

After rdv40-64-20190302 non of the versions works correct here for me. (diffrent problems in every version)

Ill just run that version untill a bigger upgrade is avaible (so never mind my problem) maybe anyone else wanna try it? I cant be the only one.

Im a lossy explainer, sorry

gator96100 · 2019-08-10 20:29:04

After the first delivery attempt for my Blue Shark Add-on failed and the package was send back to China, I finally received it.

I did add precompiled builds with the Bluetooth Add-on for x86/x64. During testing, I did have some issues related to the Bluetooth driver for my cheap USB Bluetooth dongle. If you have problems connecting to the Bluetooth COM port you might need another dongle.

iceman · 2019-08-12 19:54:41

Nice! Precompiled BTADDON for RDV4 platform. Ppl will be happy.

ps
Send mail an email about what your blue shark did ?

gator96100 · 2019-08-12 21:44:20

iceman wrote:

Nice! Precompiled BTADDON for RDV4 platform. Ppl will be happy.
ps
Send mail an email about what your blue shark did ?

Blue Shark did everything right and did not make any problem. My problem was Windows/Bluetooth driver related. By the way, is there supposed to be two COM ports for the Blue Shark Add-on? I have an incoming COM port and an outgoing COM port and just one of them seems to work.

iceman · 2019-08-12 21:54:10

yeah. i noticed that aswell. the B one works for me. strange but client sends first. ie outgoing.

fabiuzz · 2019-09-12 07:46:01

@gator96100

Could you check teh pre-compiled release for RDV40 dedicated with Bluetooth addon x64?
The batch for flash it does't work.

thanks

gator96100 · 2019-09-12 12:56:19

Thank you for noticing. It seems the flasher does no longer exist on the RDV40 dedicated fork and it is now part of the client. Expect a fix soon.

gator96100 · 2019-09-12 14:54:14

The batch files for flashing should work now. There were many changes in the RDV40 dedicated fork since I last tested the pre-compiled builds and it seems that there might be a bug with the $HOME variable. I will have a look into it in the coming days.

iceman · 2019-09-12 20:37:13

progress is lovely!

mwalker · 2019-09-13 03:09:48

RRG RDV4

gator96100 wrote:

... it seems that there might be a bug with the $HOME variable...

I have already raised an issue for this one.
The latest build (that I tested) seems to have fixed this.

update: All working fine with the latest download from rrg

Last edited by mwalker (2019-09-13 09:18:41)

raptor · 2019-12-10 10:14:28

Is the iceman fork pre compiled downloads the RRG/Iceman version?

gator96100 · 2019-12-10 23:29:45

Iceman=iceman1001/proxmark3
RDV40 dedicated=RfidResearchGroup/proxmark3

iceman · 2019-12-11 09:56:12

Hm, a bit confusing I see. How about we edit that first post and use the same nomenklatur?
I mean for me I understand the difference but it might not be the same for new users.

- Iceman (deprecated)
- RRG/Iceman RDV4
- RRG/Iceman RDV4 w blueshark

gator96100 · 2019-12-11 14:52:09

Agreed it might be confusing for some users, hope it is clear now. I also added precompiled builds for the RRG / Iceman repo with non-RDV4 Proxmark3 platforms.

raptor · 2019-12-11 22:39:11

Thanks to both of you.
I understand a little more now.

edit:
Clicking these links:

RRG / Iceman repository (Proxmark3 generic):
RRG / Iceman repository x86: Precompiled builds for RRG / Iceman repository x86
RRG / Iceman repository x64: Precompiled builds for RRG / Iceman repository x64

I see the files are called RDV40....

Is RRG/Iceman available for RDV2 (elechouse)?

Last edited by raptor (2019-12-11 22:47:56)

gator96100 · 2019-12-12 00:10:56

Oops wrong name, should be called rrg_other-32/rrg_other-64. Yes, they can be used for the RDV2.

yukihama · 2019-12-12 07:16:35

gator96100 wrote:

Oops wrong name, should be called rrg_other-32/rrg_other-64. Yes, they can be used for the RDV2.

Hi gator96100

thanks for your endless effort for these repo files. They are so wonderful to have on carlendar basis.

Is it possible to have similar carlender repo files on Linux system?

You are a genuis! I am gratefu ^_^

raptor · 2019-12-12 14:40:03

gator96100 wrote:

Oops wrong name, should be called rrg_other-32/rrg_other-64. Yes, they can be used for the RDV2.

Magnificent
Thanks!

Last edited by raptor (2019-12-12 14:40:24)

zhuminggang · 2020-01-08 09:46:16

gator96100 wrote:

I have tested multiple Windows 10 and Windows 7 installations and all are working. Windows does not care about carriage returns are you using a other than default terminal?

more test...

Last edited by zhuminggang (2020-01-08 10:01:03)

zhuminggang · 2020-01-08 10:00:38

gator96100 wrote:

iceman wrote:
looks like it didn't run the intial first run, where it downloaded / installed everything, and it that case I doubt he has compiled...
It is about the precompiled builds and not ProxSpace, there is not initial setup. The .bat files are not working for zhuminggang because a missing carriage returns, but on Windows there is no need for it. The only reason I can think of what causes this isse is an other than default terminal.

I just download your latest release every month at google drive and flash my rdv40 bt and do some test.

My laptop use windows 10 1909(18363.535) ,has no ProxSpace installed, terminal is windows default,
just use rdv40_bt-64, after 20190830 no flasher.exe,
FLASH - All.bat must edit the batch files and add 0x0d each line!

please test use windows 10 without ProxSpace!

Last edited by zhuminggang (2020-01-08 10:06:21)

w106 · 2020-04-16 03:14:39

Your work helps me a lot.
Thanks!

NIXIEGeek · 2020-05-15 01:10:32

hi,
I tried the "official Proxmark x64" w/ my PM3-RDV4 and seems to have worked w/o any issues and was able to test a few commands.

I then tried the latest "RDV40 dedicated x64" build, after the install, I ran the "proxmark3 <com port>" and it fails to recognize / read the PM3 on the port. Any ideas why ?

Running W10 Pro w/ latest updates.

thanks

gator96100 · 2020-05-15 02:35:31

Did you flash the bootrom as well? Is the proxmark com port visible in the device manager? The com port might change when switching between firmwares.

wh201906 · 2020-05-26 11:52:39

Can I import your compiled PM3 client in my GUI release? I will mention your name in my repository.

Proxmark3 community

Announcement

#101 2018-07-27 19:42:23

Re: Compiled Windows clients - always up to date

#102 2018-07-30 02:08:15

Re: Compiled Windows clients - always up to date

#103 2018-07-30 17:33:45

Re: Compiled Windows clients - always up to date

#104 2018-07-31 00:23:16

Re: Compiled Windows clients - always up to date

#105 2018-08-04 01:44:22

Re: Compiled Windows clients - always up to date

#106 2018-08-04 04:54:13

Re: Compiled Windows clients - always up to date

#107 2018-10-30 16:05:07

Re: Compiled Windows clients - always up to date

#108 2018-10-30 21:31:03

Re: Compiled Windows clients - always up to date

#109 2018-10-31 04:30:00

Re: Compiled Windows clients - always up to date

#110 2018-11-04 23:45:22

Re: Compiled Windows clients - always up to date

#111 2018-11-05 09:34:34

Re: Compiled Windows clients - always up to date

#112 2018-11-05 12:16:00

Re: Compiled Windows clients - always up to date

#113 2018-11-05 13:56:17

Re: Compiled Windows clients - always up to date

#114 2019-01-22 06:56:32

Re: Compiled Windows clients - always up to date

#115 2019-01-25 17:58:09

Re: Compiled Windows clients - always up to date

#116 2019-01-26 06:02:24

Re: Compiled Windows clients - always up to date

#117 2019-01-26 07:44:32

Re: Compiled Windows clients - always up to date

#118 2019-01-26 07:57:45

Re: Compiled Windows clients - always up to date

#119 2019-01-26 08:14:08

Re: Compiled Windows clients - always up to date

#120 2019-01-26 08:30:39

Re: Compiled Windows clients - always up to date

#121 2019-01-27 04:12:44

Re: Compiled Windows clients - always up to date

#122 2019-01-29 23:19:29

Re: Compiled Windows clients - always up to date

#123 2019-02-08 18:04:59

Re: Compiled Windows clients - always up to date

#124 2019-02-08 20:55:51

Re: Compiled Windows clients - always up to date

#125 2019-05-01 16:48:03

Re: Compiled Windows clients - always up to date

#126 2019-05-01 19:31:50

Re: Compiled Windows clients - always up to date

#127 2019-05-01 21:21:39

Re: Compiled Windows clients - always up to date

#128 2019-08-10 20:29:04

Re: Compiled Windows clients - always up to date

#129 2019-08-12 19:54:41

Re: Compiled Windows clients - always up to date

#130 2019-08-12 21:44:20

Re: Compiled Windows clients - always up to date

#131 2019-08-12 21:54:10

Re: Compiled Windows clients - always up to date

#132 2019-09-12 07:46:01

Re: Compiled Windows clients - always up to date

#133 2019-09-12 12:56:19

Re: Compiled Windows clients - always up to date

#134 2019-09-12 14:54:14

Re: Compiled Windows clients - always up to date

#135 2019-09-12 20:37:13

Re: Compiled Windows clients - always up to date

#136 2019-09-13 03:09:48

Re: Compiled Windows clients - always up to date

#137 2019-12-10 10:14:28

Re: Compiled Windows clients - always up to date

#138 2019-12-10 23:29:45

Re: Compiled Windows clients - always up to date

#139 2019-12-11 09:56:12

Re: Compiled Windows clients - always up to date