Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Hi all!
I installed ProxSpace on the flash drive. I successfully run it on computer 1 from Windows 10 and on computer 2 from Windows 7 x64. However, an error is displayed on my home main computer 3 with Windows 7 x64 when I run the ProxSpace:
Error: Invalid option -Fq
Error: Invalid option -Fq
pm3 ~$
And the further compilation of the proxmark does not work. I tried several times to run a clean installation of ProxSpace on the problem computer, but nothing helped.
As I understand it, the error occurs when executing the file "user_setup.sh" on line "USER_MISSING=$( grep -Fq "$USER_SID" /etc/passwd )$?" and "GROUP_MISSING=$( grep -Fq "$GROUP_SID" /etc/group )$?".
Reinstalling Windows on a problem computer is a big problem for me - too many configured programs are installed. I would appreciate any help. Thanks!
In my opinion, the problem is caused by the incorrect work of "grep". Since even a simple launch of a proxmark fails, because it cannot find a path.
Last edited by sherhannn79 (2019-05-07 08:58:41)
Offline
What is the output of "echo %PATH%"?
Offline
What is the output of "echo %PATH%"?
In ProxSpace:
Error: Invalid option -Fq
Error: Invalid option -Fq
pm3 ~$ echo %PATH%
%PATH%
pm3 ~$
In Windows:
c:\>echo %PATH%
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compil
er;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32\compil
er;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files
(x86)\Common Files\Microsoft Shared\Windows Live;D:\PROGRA~2\Borland\CBUILD~1\Bi
n;D:\PROGRA~2\Borland\CBUILD~1\Projects\Bpl;C:\Program Files (x86)\NVIDIA Corpor
ation\PhysX\Common;C:\PROGRA~2\Borland\CBUILD~1\Bin;C:\PROGRA~2\Borland\CBUILD~1
\Projects\Bpl;C:\Windows\System32\;C:\Program Files\Common Files\Autodesk Shared
\;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\Autodesk
\Backburner\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Fi
les\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\QuickTime\QTSyst
em\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files\Microsoft SQL Se
rver\110\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C
:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;D:\P
rogram Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\;C
:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;C:\Windows\system32\con
fig\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files
\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Windows Kits\10\Win
dows Performance Toolkit\;
Offline
In Proxspace what is the output from "echo $PATH" and "grep --version"?
In Windows cmd what is the output (if any) from "grep --version"?
Offline
In ProxSpace:
pm3 ~$ echo $PATH
/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Wind
ows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl
:/usr/bin/vendor_perl:/usr/bin/core_perl:/gcc-arm-none-eabi/bin
pm3 ~$ grep --version
grep (GNU grep) 3.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Mike Haertel and others, see <http://git.sv.gnu.org/cgit/grep.git/tre
e/AUTHORS>.
pm3 ~$
In WinCMD:
c:\>grep --version
Error: No file sets specified
c:\>
Offline
My guess is that there is a grep executable that is interfering with the grep executable from ProxSpace. Maybe from windows powershell.
What is the output from "where grep" in Windows cmd?
Offline
c:\>where grep
D:\Program Files (x86)\Borland\CBuilder6\Bin\grep.exe
Probably such a stuff only I have installed
Offline
Renamed grep.exe in Borland\CBuilder6\Bin\. Everything worked.
Thank you so much gator96100 !!!
Offline
I am not sure if the order of the directories in PATH does matter.
Try chaning msys2_shell.cmd:19 from "SET PATH=%PATH%;%WD%" to "SET PATH=%WD%;%PATH%" does this error still occure?
Renaming the file should only be a temporary solution
Last edited by gator96100 (2019-05-06 16:28:13)
Offline
c:\>where grep
D:\Program Files (x86)\Borland\CBuilder6\Bin\grep.exeProbably such a stuff only I have installed
I was glad too soon (: :
pm3 ~$ cd ./proxmark3/client
pm3 ~/proxmark3/client$ ./proxmark3 com15
This application failed to start because it could not find or load the Qt platfo
rm plugin "windows"
in "".
Reinstalling the application may fix this problem.
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
pm3 ~/proxmark3/client$
Try chaning msys2_shell.cmd:19 from "SET PATH=%PATH%;%WD%" to "SET PATH=%WD%;%PATH%" does this error still occure?
Did not help...
Offline
Did you try to reinstall ProxSpace? Does compiling work?
Offline
Did you try to reinstall ProxSpace? Does compiling work?
I will try to reinstall the ProxSpace on the problem computer. Maybe it will help because the error "Invalid option -Fq" has disappeared.
Last edited by sherhannn79 (2019-05-06 19:16:50)
Offline
Summary:
After changing msys2_shell.cmd:19 from "SET PATH=%PATH%;%WD%" to "SET PATH=%WD%;%PATH%"
and reinstalling ProxSpace on the problem computer, the issue is solved.
I can run and compile proxmark!
Thanks again gator96100!!!
Last edited by sherhannn79 (2019-05-06 22:02:00)
Offline
The user_setup.sh file is essential to ProxSpace. An improper user setup might damage the ProxSpace environment. That is why a reinstall was needed.
I did push a fix to prioritize the working directory.
I suggest you add the prefix "solved" to the subject line
Offline
I found out some more details:
1. If you rename the ProxSpace folder, the problem will repeat again.
2. As far as I understand that on any computer there should be a directory of working ProxSpace. If not, then any copies of the program (for example, from a flash drive) will not work.
Maybe it should be so. However, the Wiki is told:
All tools will be contained within the ProxSpace folder which means ProxSpace can be moved into a different directory or even a different Windows machine without the need to reinstall anything...
Last edited by sherhannn79 (2019-05-07 01:40:28)
Offline
I suggest you add the prefix "solved" to the subject line
Sorry, but I do not know how to do it
Offline
you edit your first post...
Offline