Main Menu

pls help

Started by Crossover, November 13, 2014, 09:51:08 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Crossover

#5
Quote from: xeroc on November 13, 2014, 10:29:53 AM
Quote from: Crossover on November 13, 2014, 10:28:00 AM
Quote from: xeroc on November 13, 2014, 10:22:10 AM
1) make sure you have the latest version installed
2) go to "%APPDATA%/Roaming/Bitshares/" and remove all folders EXCEPT(!!!!!) the 'wallets' folder
3) start over and resynchronize with the blockchain
deleting of roaming/bitsharesx not help, same error

The new wallet does not use the "bitsharesx" folder but a "bitshares" folder .. if you do not have that folder then you are running a old version
problem solved by renaming of C:\users\%%%% to latin name
Thank you for help.

xeroc

Quote from: Crossover on November 13, 2014, 10:28:00 AM
Quote from: xeroc on November 13, 2014, 10:22:10 AM
1) make sure you have the latest version installed
2) go to "%APPDATA%/Roaming/Bitshares/" and remove all folders EXCEPT(!!!!!) the 'wallets' folder
3) start over and resynchronize with the blockchain
deleting of roaming/bitsharesx not help, same error

The new wallet does not use the "bitsharesx" folder but a "bitshares" folder .. if you do not have that folder then you are running a old version

Crossover

Quote from: xeroc on November 13, 2014, 10:22:10 AM
1) make sure you have the latest version installed
2) go to "%APPDATA%/Roaming/Bitshares/" and remove all folders EXCEPT(!!!!!) the 'wallets' folder
3) start over and resynchronize with the blockchain
deleting of roaming/bitsharesx not help, same error

xeroc

1) make sure you have the latest version installed
2) go to "%APPDATA%/Roaming/Bitshares/" and remove all folders EXCEPT(!!!!!) the 'wallets' folder
3) start over and resynchronize with the blockchain

Crossover

#1
i cant use BitShares since ver 0.4.23
i dont know what happened, but looks like i missed something, or some libraries needed, bTS gui just wont start and pop-out this message:

wIn7 x32

ver 0.4.24 shows the same error