Compiled Windows clients - always up to date

seanedu · 2017-04-16 18:56:13

Hi,ntk,I did not quite understand the procedures you taught me last time,I hope you can teach me step by step to update gui again,I actually found marshmellow 42 and copy the folder and copied to a proxspace folder and from runme.bat i did make clean && make all,no luck to me...
I will appreciate it,if you show me again step by step..

Thanks in advance

ntk · 2017-04-16 20:41:46

1/ You have setup Proxspace or MingGW correctly

2/ You did run make clean all flash-all.

It is important to run the same proxmark client of the same SW version you want to flash the full image in PM3 check the time stamps

3/ Goto ... /proxmark_SW/client/
4/ Archive settings.xml (just in case one day you miss the nostalgy) and delete it. Why? For making sure you start the right client (on some PC there are several different SW versions). Start the proxmark client. Client must complain no file found
5/ Download settings.xml from my dropbox, to the client directory and start the proxmark client again, wait for successful loading.
6/ Now you are ready to go.

seanedu · 2017-04-16 21:38:47

Hi,ntk,thanks for your help again,but I got little confused your procedure,first /go to ../proxmark_sw/client/,i don't know where I can find the place,secondly 4/archive settings.xml and delete it,5/I could not locate the settings.xml from your drop box,when I click download button,it only downloaded picture of your gui interface...you did not mean to download "pyramid_command_menu.png"from your drop box,I am not good at using drop box at all,so far that is all I can find to download from drop box..any tips can you give me to find settings.xml from your drop box...

Thanks again

Last edited by seanedu (2017-04-16 22:05:40)

ntk · 2017-04-16 22:15:22

OK, only pics, no file. I understand.

Just checked. On some free spaces for file sharing, links expired over time, so links died.

This one should be alive for everyone interested alternative settings.xml v1.0

seanedu · 2017-04-16 22:27:50

I will try with that and let you know if i get it done.

Thanks again

seanedu · 2017-04-16 22:39:33

Hi,ntk,thanks a million for your time,It works like a charm,I really appreciate for your precious time to let me run new gui interface from now on..

Thanks again

Last edited by seanedu (2017-04-16 22:39:58)

Danz · 2017-04-17 09:13:44

tried both builds, Iceman built (can't flash firmwares , error on nack response) , official build (flash correctly) , pm software after flashing software is not working but older pm2.4 software works with current firmware, but shows that I have unusable antenna on hw tune !.
Only for testing purposes, if anyone have latest Iceman compiled build that can share to confirm the issue (my device version, my windows, the build , etc..) , that will be appreciated.

ntk · 2017-04-17 12:29:58

Danz wrote:

tried both builds, Iceman built (can't flash firmwares , error on nack response) , official build (flash correctly) , pm software after flashing software is not working but older pm2.4 software works with current firmware, but shows that I have unusable antenna on hw tune !.
Only for testing purposes, if anyone have latest Iceman compiled build that can share to confirm the issue (my device version, my windows, the build , etc..) , that will be appreciated.

"Iceman built (can't flash firmwares , error on nack response" that fault is related to 256k 512k memory size fault is solved/discussed on forum

@Danz I think you hint on IDTEK found issue, I use PSK2 configuration, in case you have missed. should have left post there

Last edited by ntk (2017-04-17 12:34:42)

Danz · 2017-04-17 21:35:58

Exactly bro, after I rewrote the t55 with your config , I couldn't see it as idteck so I wanted to update my firmware , now all went South , I did notice that you used psk2 for the data but it didn't give out same trace as the original!,
I can't find the thread about the memory issue on Iceman build! But I had my suspicion on that but I didn't think bottom have memory block to be affected on the flashing process therefore I asked for another precompiled build. Anyhow I appreciate your help as always.

gator96100 · 2017-04-22 00:37:53

I did some tests and it seems the problem with the iceman builds crashing on amd systems is not caused by my proxspace environment or a missing library. This problem does seem to exist under linux as well (just slightly different behaviour, client crashes on start with the error illegal instruction), meaning that somewhere in the iceman fork is a bug that causes this strange behaviour. As of now I don’t have time to find the bug and fix it.
Edit: Removing -march=native from the COMMON_FLAGS in the Makefile fixes the problem.

Last edited by gator96100 (2017-04-22 11:32:01)

gator96100 · 2017-04-23 17:08:09

The iceman builds should now work on all CPUs that support the x86-64 instruction set.

Last edited by gator96100 (2017-04-23 17:16:49)

MaBi · 2017-04-25 18:35:31

gator96100 wrote:

The iceman builds should now work on all CPUs that support the x86-64 instruction set.

I have tried both version in your old post.
I have got a AMD Phenom(tm) 2 X4 965 processor and Win 7 32 bit version. Only your AMD version doesn't crash.

Then I have read your last post and tried your last build of iceman version 2017_04_23 and it works well

jramb0 · 2017-05-14 04:18:55

hey guys not sure if it is related to the apps or windows 10 but when running proxmark3.exe if i type hw tune or lf search or other commands like this, it crashes saying "proxmark3.exe has stopped working" "A problem caused the program to stop working correctly." Then I am presented the option to debug or close it

I've been trying the latest unofficial build from 2017 04 30 an unofficial 2017 04 23

Anyone experienced this too?

Last edited by jramb0 (2017-05-14 04:19:36)

iceman · 2017-05-18 10:10:13

@gator96100 I think you should add the dictionary file ( *.dic ) to your distros. Hard to run checks without it.

phiber · 2017-05-30 13:06:06

jramb0 wrote:

hey guys not sure if it is related to the apps or windows 10 but when running proxmark3.exe if i type hw tune or lf search or other commands like this, it crashes saying "proxmark3.exe has stopped working" "A problem caused the program to stop working correctly." Then I am presented the option to debug or close it
I've been trying the latest unofficial build from 2017 04 30 an unofficial 2017 04 23
Anyone experienced this too?

i'm facing the same issue with iceman's image and the windows .exe and the mingw .exe..
so in the end i flashed the official firmware and all works well.

probably something with's iceman's code?

iceman · 2017-05-30 13:32:36

that would be the compilation directive used for Hardnesed BF solver... Should be better now since @gator9600 changed it to fit better.
Have not tried it myself but it would be nice if you would test it out @phiber

phiber · 2017-05-31 02:08:52

iceman wrote:

that would be the compilation directive used for Hardnesed BF solver... Should be better now since @gator9600 changed it to fit better.
Have not tried it myself but it would be nice if you would test it out @phiber

Hi Iceman,

i tried the latest 0529 exe from @Gator and the latest windows mingw git pull from your github on your latest firmware..

crashes the moment i do LF SE..

i have since switched the latest official firmware and all works now though.

ntk · 2017-05-31 02:51:46

could you send up the pm3.log when PM3 app crashed.

I have win7 and kali and iceman's fork is quite stable, although mine is from end of April

Last edited by ntk (2017-05-31 02:53:45)

phiber · 2017-05-31 08:22:51

ntk wrote:

could you send up the pm3.log when PM3 app crashed.
I have win7 and kali and iceman's fork is quite stable, although mine is from end of April

i started a new thread at http://www.proxmark.org/forum/viewtopic … 925#p27925

pasted the pm3.log there when it crashed..

Last edited by phiber (2017-05-31 08:48:05)

seanedu · 2017-06-29 16:11:12

@gator96100

Hi,I need your help to update precompiled window client either official or iceman,I am currently using two different version of bootrom and os,so far I don't have any problem at all,but I like to update to newer version of compiled window client,but I have a problem to flash both bootrom and os files,I even hold the button but proxmark3 got no reponse at all.Do I miss any files in order to flash?

marshmellow · 2017-06-29 16:21:12

see http://www.proxmark.org/forum/viewtopic.php?id=4904

gator96100 · 2017-06-29 16:40:22

@seanedu you might need to reinstall the driver, because the vid and pid were changed.

seanedu · 2017-06-29 21:25:45

Thanks a lot for both @marshmellow and @gator,sorry for late respond,I will try what you suggested to me,but how do I get the latest driver or where can I find the latest driver?

gator96100 · 2017-06-30 00:01:05

The driver is always included in the precompiled build in the folder "Windows Driver" or it can be downloaded directly from the git repository in the "driver" folder.

seanedu · 2017-06-30 00:26:45

@gator

Thanks a lot,I will give a shot,I will let you know if it works.

seanedu · 2017-06-30 01:02:11

@gator

I found windows driver from precompiled build but I can't install from driver seemed like it was read only
file..also on githup I could not locate the driver file,any other solution?

seanedu · 2017-06-30 01:19:59

@gator
Just want to show you my version of proxmark3

C:\Users\French Quarters\Desktop\updated pr3>proxmark3 COM12
Prox/RFID mark3 RFID instrument
bootrom: iceman/master/v1.1.0-1757-g0ecec53 2017-01-08 10:18:20
os: master/v2.2.0-404-g9331855-suspect 2017-03-27 11:16:45
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 190480 bytes (73%). Free: 716
64 bytes (27%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3> data save
couldn't open ''
proxmark3> hw ver
[[[ Cached information ]]]

Prox/RFID mark3 RFID instrument
bootrom: iceman/master/v1.1.0-1757-g0ecec53 2017-01-08 10:18:20
os: master/v2.2.0-404-g9331855-suspect 2017-03-27 11:16:45
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 190480 bytes (73%). Free: 716
64 bytes (27%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Me

gator96100 · 2017-06-30 01:40:34

@seanedu you need to flash the newest bootrom and firmware. After flashing the bootrom you might need to reinstall the driver using the device manager. You are currently using an outdated version of the bootrom as well as the firmware.

seanedu · 2017-06-30 03:18:35

@gator

I've tried to flash bootrom and firmware with using precompiled build both on iceman's and official build
but always failed to flash,is there any easiest way to flash bootrom and firmware,It was so complicated for me to compile myself so I ended up using precompiled build some how I did flashed bootrom and os file but just recently found out that my bootrom and os file ware different version,so I decided to flash again to up to date the file,but again I am stuck here and need your help to update..

gator96100 · 2017-06-30 12:03:06

What is the problem during flashing?
Send the output of the flasher.

abdo79 · 2017-06-30 13:46:01

hi;
i tried the new official update (30/6/2017) the command for (HW Tune ) and (HID simulate) doesn't work in a right way.please reply back to me with the way to fix it

Prox/RFID mark3 RFID instrument
bootrom: master/v2.2.0-532-g82e8eee-suspect 2017-06-30 09:27:56
os: master/v2.2.0-532-g82e8eee-suspect 2017-06-30 09:28:01
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26
uC: AT91SAM7S256 Rev D
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 192561 bytes (73%). Free: 69583 bytes (27%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3> hw tune
Measuring antenna characteristics, please wait...
# LF antenna: 0.00 V @ 125.00 kHz
# LF antenna: 0.00 V @ 134.00 kHz
# LF optimal: 0.00 V @ 12000.00 kHz
# HF antenna: 0.00 V @ 13.56 MHz
# Your LF antenna is unusable.
# Your HF antenna is unusable.
proxmark3>
proxmark3> hw tune
Measuring antenna characteristics, please wait...
# LF antenna: 0.00 V @ 125.00 kHz
# LF antenna: 0.00 V @ 134.00 kHz
# LF optimal: 0.00 V @ 12000.00 kHz
# HF antenna: 0.00 V @ 13.56 MHz
# Your LF antenna is unusable.
# Your HF antenna is unusable.
proxmark3>
proxmark3> lf hid sim 20065a92b6
Emulating tag with ID 20 65a92b6
Press pm3-button to abort simulation
proxmark3>
proxmark3> #db# Stopped

thanks

seanedu · 2017-06-30 14:47:11

@gator

This is what I get when I try to flash from either precompiled build iceman's or official build,I even reinstall the driver before flashing the bootrom,still no luck,any help will be appreciated.

====================================
FLASHING bootrom.elf, please wait...
====================================

Loading ELF file '..\firmware_win\bootrom\bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000c18->0x00000c18) [RWX] @0x298

Waiting for Proxmark to appear on com12.... Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on com12.......................................
................................................................................
................................................................................
.................................................

platinium gsm · 2017-06-30 15:24:16

unplug your proxmark and push button and leave it pushed . plug your proxmark and wait your proxmarks reappear!

be sure using note pad {right click with your mouse open with notepad] that PORt COM use is com 12

iceman · 2017-06-30 15:38:21

also make sure your device "reconnects" as com12.. Look at "devices and printers", when you run the flash command first.
If it changes, just ctrl-c and rerun the command with the new comport.

seanedu · 2017-06-30 15:46:59

@platinum and Iceman,Thanks both of you,I should have mentioned that I pressed button while I flashing,@iceman,also I ensured com port is correct matching on notepad and device manager,still problem continued...

marshmellow · 2017-06-30 15:48:57

During the flash the com port can change.. did you verify during?

seanedu · 2017-06-30 16:04:24

I should apologize to Iceman,when |I double check device manager it did change com12 to com8,in that @marshmellow what should I do,Iceman told me to ctrl+c and return with new command with new port,I don't quite get it what that mean....

marshmellow · 2017-06-30 16:05:55

Follow the instructions in the link from my first post to you...

seanedu · 2017-06-30 16:10:56

@marshmellow

I check that link and let you know how it goes,many thanks for your help...

seanedu · 2017-06-30 16:35:48

@marshmellow

This is what happened,while flashing,waiting and pressed ctrl+c and asked me terminate the bat. file
press no and changed to new command prompt and \I typed command/like/

./client/flasher -b com8./bootrom/obj/bootrom.elf

still no luck,could help me what I did wrong...

seanedu · 2017-06-30 16:48:57

====================================
FLASHING bootrom.elf, please wait...
====================================

Loading ELF file '..\firmware_win\bootrom\bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000cc0->0x00000cc0) [RWX] @0x298

Waiting for Proxmark to appear on com12. Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on com12.......................................
...........^CTerminate batch job (Y/N)?

@marshmellow

Can you tell me what to do next from this point?

seanedu · 2017-06-30 17:07:17

@marshmellow

I thank you so much,finally I got it work,thanks again...

C:\Users\French Quarters\Desktop\20170627-2a7861ef0a3039e7fae2833c309f93a65b2aec
31 (1)\win32>proxmark3 COM8
Prox/RFID mark3 RFID instrument
bootrom: master/v2.2.0-528-g2a7861e-suspect 2017-06-27 09:17:15
os: master/v2.2.0-528-g2a7861e-suspect 2017-06-27 09:17:19
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/05/17 at 17:48:26

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 192561 bytes (73%). Free: 695
83 bytes (27%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3> hw tune

Measuring antenna characteristics, please wait.......
# LF antenna: 27.64 V @ 125.00 kHz
# LF antenna: 31.90 V @ 134.00 kHz
# LF optimal: 35.20 V @ 130.43 kHz
# HF antenna: 25.56 V @ 13.56 MHz
Displaying LF tuning graph. Divisor 89 is 134khz, 95 is 125khz.

proxmark3>

iceman · 2017-06-30 18:18:10

In order to keep this thread clean, I urge all ppl who wants to ask questions to @gator96100 about his binary distros to start new threads That will enable @gator96100 to keep track of the solutions and easier searching for newcomers.

Thanks,

seanedu · 2017-06-30 20:56:40

C:\Users\French Quarters\Desktop\official compiled apr 17 - Copy (2)\win32>prox
ark3 COM12
Prox/RFID mark3 RFID instrument
bootrom: iceman/master/v1.1.0-2055-g4d189095 2017-06-27 11:15:40
os: iceman/master/v1.1.0-2055-g4d189095 2017-06-27 11:15:46
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 216690 bytes (83%). Free: 454
54 bytes (17%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type
proxmark3> lf sea
NOTE: some demods output possible binary
if it finds something that looks like a tag
False Positives ARE possible

Checking for known tags:

HID Prox TAG ID: 036608bdf (17903) - Format Len: 37bit - FC: 870 - Card: 17903

Valid HID Prox ID Found!
proxmark3> lf hid cl 036608bdf
Cloning tag with ID 036608bdf
proxmark3> lf sea
NOTE: some demods output possible binary
if it finds something that looks like a tag
False Positives ARE possible

Checking for known tags:

No Known Tags Found!

proxmark3>

@marshmellow and @iceman @gator

I need help again,I just updated my bootrom and firmware through your instruction,my pm3

behave strage,when I read awid tag,and clone to t5577,and when I read the copied tag turned out to
hid tag,also when I copied hid tag and when I read copied tag it read no tag found...

is there any way to fix or I like to down grade to a old version...please help...

seanedu · 2017-06-30 21:01:41

Checking for known tags:

AWID Found - BitLength: 37, FC: 2600, Card: 86076 - Wiegand: 5142a0786, Raw: 01224484824817d1d1111111

Valid AWID ID Found!
Enables cloning of AWID card with specified facility-code and card number onto T55x7.
The T55x7 must be on the antenna when issuing this command. T55x7 blocks are calculated and printed in the process.

Usage: lf awid clone <format> <facility-code> <card-number>
Options:
h : This help
<format> : format length 26|34|37|50
<facility-code> : 8|16bit value facility code
<card number> : 16|32-bit value card number
Q5 : optional - clone to Q5 (T5555) instead of T55x7 chip

Samples:
lf awid clone 26 224 1337
lf awid clone 50 2001 13371337
Preparing to clone AWID 37 to T55x7 with FC: 2600, CN: 86076
Blk | Data
----+------------
00 | 0x00107060
01 | 0x01227484
02 | 0x824817d4
03 | 0x11111111
Reading 30000 bytes from device memory

Data fetched
Samples @ 8 bits/smpl, decimation 1:1
NOTE: some demods output possible binary
if it finds something that looks like a tag
False Positives ARE possible

Checking for known tags:

No Known Tags Found!

seanedu · 2017-06-30 21:38:42

@marshmellow

I have now downgraded the firmware to the older version of Mar17/precompiled official build,now it works fine..

Thank you all for your help

ntk · 2017-07-02 10:22:25

@seanedu,
you should come off this threads. Check that You have right how to open new topics right.
We better let this topic being concentrated only on proxspace's and/or pre-built version anouncement

gator96100 · 2018-01-01 23:04:23

I did update mingw in my Proxspace environment, this should allow AVX-512 optimizations for hardnested. Could someone with a supported CPU test it(Skylake-X/Xeon Phi x200)? https://github.com/Gator96100/ProxSpace/tree/NewGCC

I'll need to do some more work before I can merge it into master.

Last edited by gator96100 (2018-01-01 23:12:01)

gator96100 · 2018-01-18 20:19:19

I am sorry for the long delay of precompiled builds.
All builds are now compiled with the updated Proxspace environment.

gator96100 · 2018-07-25 21:32:27

I did test the precompiled builds on the new RDV40 (flashing bootrom and fullimage + some hf & lf tests) everything seems to work properly.
I will add the future RDV40 repo when it is updated.

Proxmark3 community

Announcement

#51 2017-04-16 18:56:13

Re: Compiled Windows clients - always up to date

#52 2017-04-16 20:41:46

Re: Compiled Windows clients - always up to date

#53 2017-04-16 21:38:47

Re: Compiled Windows clients - always up to date

#54 2017-04-16 22:15:22

Re: Compiled Windows clients - always up to date

#55 2017-04-16 22:27:50

Re: Compiled Windows clients - always up to date

#56 2017-04-16 22:39:33

Re: Compiled Windows clients - always up to date

#57 2017-04-17 09:13:44

Re: Compiled Windows clients - always up to date

#58 2017-04-17 12:29:58

Re: Compiled Windows clients - always up to date

#59 2017-04-17 21:35:58

Re: Compiled Windows clients - always up to date

#60 2017-04-22 00:37:53

Re: Compiled Windows clients - always up to date

#61 2017-04-23 17:08:09

Re: Compiled Windows clients - always up to date

#62 2017-04-25 18:35:31

Re: Compiled Windows clients - always up to date

#63 2017-05-14 04:18:55

Re: Compiled Windows clients - always up to date

#64 2017-05-18 10:10:13

Re: Compiled Windows clients - always up to date

#65 2017-05-30 13:06:06

Re: Compiled Windows clients - always up to date

#66 2017-05-30 13:32:36

Re: Compiled Windows clients - always up to date

#67 2017-05-31 02:08:52

Re: Compiled Windows clients - always up to date

#68 2017-05-31 02:51:46

Re: Compiled Windows clients - always up to date

#69 2017-05-31 08:22:51

Re: Compiled Windows clients - always up to date

#70 2017-06-29 16:11:12

Re: Compiled Windows clients - always up to date

#71 2017-06-29 16:21:12

Re: Compiled Windows clients - always up to date

#72 2017-06-29 16:40:22

Re: Compiled Windows clients - always up to date

#73 2017-06-29 21:25:45

Re: Compiled Windows clients - always up to date

#74 2017-06-30 00:01:05

Re: Compiled Windows clients - always up to date

#75 2017-06-30 00:26:45

Re: Compiled Windows clients - always up to date

#76 2017-06-30 01:02:11

Re: Compiled Windows clients - always up to date

#77 2017-06-30 01:19:59

Re: Compiled Windows clients - always up to date

#78 2017-06-30 01:40:34

Re: Compiled Windows clients - always up to date

#79 2017-06-30 03:18:35

Re: Compiled Windows clients - always up to date

#80 2017-06-30 12:03:06

Re: Compiled Windows clients - always up to date

#81 2017-06-30 13:46:01

Re: Compiled Windows clients - always up to date

#82 2017-06-30 14:47:11

Re: Compiled Windows clients - always up to date

#83 2017-06-30 15:24:16

Re: Compiled Windows clients - always up to date

#84 2017-06-30 15:38:21

Re: Compiled Windows clients - always up to date

#85 2017-06-30 15:46:59

Re: Compiled Windows clients - always up to date

#86 2017-06-30 15:48:57

Re: Compiled Windows clients - always up to date

#87 2017-06-30 16:04:24

Re: Compiled Windows clients - always up to date

#88 2017-06-30 16:05:55

Re: Compiled Windows clients - always up to date

#89 2017-06-30 16:10:56

Re: Compiled Windows clients - always up to date