search

Gator96100 / ProxSpace

Proxmark III develoment environment for Windows
269 stars 70 forks source link

About copying proxspace folder to new computer running error #22

Closed ewangsoft closed 4 years ago

ewangsoft commented 4 years ago

I changed my computer, copied the "proxspace" folder to the new computer, ran "runme64", and prompted "unknown + user @ desktop-bdf7vmj mingw64" error. What should I do?

digitalentropy commented 4 years ago

Is the folder path the same on the new computer?

Per the instructions, once you set up ProxSpace for the first time you cannot change the path without breaking functionality.

ewangsoft commented 4 years ago

Is the folder path the same on the new computer?

Per the instructions, once you set up ProxSpace for the first time you cannot change the path without breaking functionality.

The original folder is in partition D, now in partition E. That's not OK?

digitalentropy commented 4 years ago

To my knowledge it must be the same exact path.

You can probably manually change the path in the configuration files but I haven’t dug into it to see what needs to be adjusted.

From: ewangsoft notifications@github.com Sent: Thursday, October 17, 2019 10:40 PM To: Gator96100/ProxSpace ProxSpace@noreply.github.com Cc: Babak Javadi omikron@brokenpixel.net; Comment comment@noreply.github.com Subject: Re: [Gator96100/ProxSpace] About copying proxspace folder to new computer running error (#22)

Is the folder path the same on the new computer?

Per the instructions, once you set up ProxSpace for the first time you cannot change the path without breaking functionality.

The original folder is in partition D, now in partition E. That's not OK?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Gator96100/ProxSpace/issues/22?email_source=notifications&email_token=AAKYZPSR7ENYHMTKUIOOATTQPFDZHA5CNFSM4JCAQLWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBSXCZI#issuecomment-543519077, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAKYZPQIR3WM2ZPMZMUYUOTQPFDZHANCNFSM4JCAQLWA.

ewangsoft commented 4 years ago

To my knowledge it must be the same exact path. You can probably manually change the path in the configuration files but I haven’t dug into it to see what needs to be adjusted. From: ewangsoft notifications@github.com Sent: Thursday, October 17, 2019 10:40 PM To: Gator96100/ProxSpace ProxSpace@noreply.github.com Cc: Babak Javadi omikron@brokenpixel.net; Comment comment@noreply.github.com Subject: Re: [Gator96100/ProxSpace] About copying proxspace folder to new computer running error (#22) Is the folder path the same on the new computer? Per the instructions, once you set up ProxSpace for the first time you cannot change the path without breaking functionality. The original folder is in partition D, now in partition E. That's not OK? — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#22?email_source=notifications&email_token=AAKYZPSR7ENYHMTKUIOOATTQPFDZHA5CNFSM4JCAQLWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBSXCZI#issuecomment-543519077>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAKYZPQIR3WM2ZPMZMUYUOTQPFDZHANCNFSM4JCAQLWA.

I put it back in the previous position and still prompt "unknown + user @ desktop-bdf7vmj mingw64 ~"

iceman1001 commented 4 years ago

...proxspace is quite allergic to spaces in the folderpath leading to it. Make sure you don't have any..

this will error...
c:\program data\myuser\proxspace
Gator96100 commented 4 years ago

ProxSpace/msys2 is not suited for path changes, however it can be done. The unknown user problem is a result of an error in msys2/user_setup.sh most likely because a space or special character in the path and not because you moved ProxSpace. When ProxSpace is moved, every package needs to be reinstalled (although you might get away with just reinstalling qt5, not tested!!!). For reinstalling every package, a script like this can be used: 

#! /bin/sh

for pkg in $(pacman -Q | cut -d' ' -f1); do
    pacman -S --noconfirm $pkg
done

As you need to reinstall everything you should only do it if there is a good reason to use an existing ProxSpace setup. The reinstallation will most likely take longer and use more bandwidth than a new installation of ProxSpace. The package cache is cleared after the first installation and pacman needs to download every package again.

ewangsoft commented 4 years ago

ProxSpace/msys2 is not suited for path changes, however it can be done. The unknown user problem is a result of an error in msys2/user_setup.sh most likely because a space or special character in the path and not because you moved ProxSpace. When ProxSpace is moved, every package needs to be reinstalled (although you might get away with just reinstalling qt5, not tested!!!). For reinstalling every package, a script like this can be used:

#! /bin/sh

for pkg in $(pacman -Q | cut -d' ' -f1); do
    pacman -S --noconfirm $pkg
done

As you need to reinstall everything you should only do it if there is a good reason to use an existing ProxSpace setup. The reinstallation will most likely take longer and use more bandwidth than a new installation of ProxSpace. The package cache is cleared after the first installation and pacman needs to download every package again.

Thank you. The whole package has been downloaded and reinstalled. It may take less time than repairing the installation.