Pages:
Author

Topic: [XMR] MoneroX - A cross platform graphical account manager for Monero - page 12. (Read 88593 times)

legendary
Activity: 2968
Merit: 1198
I just noticed that anyone using the "test" versions are no longer going to be able to connect to the network, as per this:

Quote
2014-Sep-10 09:23:34.874223 ERROR C:/msys2/home/mikezackles/work/bitmonero/src/p
2p/net_node.inl:108 Exception at [node_server::init_config], what=unsupported ve
rsion
2014-Sep-10 09:23:34.876223 ERROR C:/msys2/home/mikezackles/work/bitmonero/src/p
2p/net_node.inl:239 Failed to init config.

That's because the test version doesn't have the new binaries yet.

https://bitcointalksearch.org/topic/m.8745440
legendary
Activity: 1540
Merit: 1011
FUD Philanthropist™
A quick update 'v0.38.2' has just been pushed, which changes the bundled binaries 'bitmonerod.exe' and 'simplewallet.exe' in order to mitigate the blockchain attack which happened a little while ago.

Test versions are not yet updated.

Thanks, Jojatekok. I was wondering in the Monero Support thread whether or not the binaries included here were the same as the officially released binaries. Is this the case?

the Monero Support thread should not be cluttered up.. please make a new Monero support thread !
legendary
Activity: 1762
Merit: 1011
I just noticed that anyone using the "test" versions are no longer going to be able to connect to the network, as per this:

Quote
2014-Sep-10 09:23:34.874223 ERROR C:/msys2/home/mikezackles/work/bitmonero/src/p
2p/net_node.inl:108 Exception at [node_server::init_config], what=unsupported ve
rsion
2014-Sep-10 09:23:34.876223 ERROR C:/msys2/home/mikezackles/work/bitmonero/src/p
2p/net_node.inl:239 Failed to init config.
sr. member
Activity: 264
Merit: 250
Is this because the test versions use different binaries? For instance, the official bitmonerod.exe requires typing "exit" to quit the daemon, whereas, the binary included in the test versions uses the command line argument "stop_daemon" to quit it.

I'm sure jojatekok will have a better answer but my guess is yes. There is work in development to make the daemon into a proper daemon (operates in the background not in a window) I would guess he is using the in the test version. 

I don't really have a better answer, because you answered the question perfectly. Wink
legendary
Activity: 2968
Merit: 1198
A quick update 'v0.38.2' has just been pushed, which changes the bundled binaries 'bitmonerod.exe' and 'simplewallet.exe' in order to mitigate the blockchain attack which happened a little while ago.

Test versions are not yet updated.

Thanks, Jojatekok. I was wondering in the Monero Support thread whether or not the binaries included here were the same as the officially released binaries. Is this the case?

Yep, the new binaries are included in v0.38.2 (but not yet in the test versions).

Is this because the test versions use different binaries? For instance, the official bitmonerod.exe requires typing "exit" to quit the daemon, whereas, the binary included in the test versions uses the command line argument "stop_daemon" to quit it.

I'm sure jojatekok will have a better answer but my guess is yes. There is work in development to make the daemon into a proper daemon (operates in the background not in a window) I would guess he is using the in the test version. 
legendary
Activity: 1762
Merit: 1011
A quick update 'v0.38.2' has just been pushed, which changes the bundled binaries 'bitmonerod.exe' and 'simplewallet.exe' in order to mitigate the blockchain attack which happened a little while ago.

Test versions are not yet updated.

Thanks, Jojatekok. I was wondering in the Monero Support thread whether or not the binaries included here were the same as the officially released binaries. Is this the case?

Yep, the new binaries are included in v0.38.2 (but not yet in the test versions).

Is this because the test versions use different binaries? For instance, the official bitmonerod.exe requires typing "exit" to quit the daemon, whereas, the binary included in the test versions uses the command line argument "stop_daemon" to quit it.
sr. member
Activity: 264
Merit: 250
A quick update 'v0.38.2' has just been pushed, which changes the bundled binaries 'bitmonerod.exe' and 'simplewallet.exe' in order to mitigate the blockchain attack which happened a little while ago.

Test versions are not yet updated.

Thanks, Jojatekok. I was wondering in the Monero Support thread whether or not the binaries included here were the same as the officially released binaries. Is this the case?

Yep, the new binaries are included in v0.38.2 (but not yet in the test versions).
legendary
Activity: 1762
Merit: 1011
A quick update 'v0.38.2' has just been pushed, which changes the bundled binaries 'bitmonerod.exe' and 'simplewallet.exe' in order to mitigate the blockchain attack which happened a little while ago.

Test versions are not yet updated.

Thanks, Jojatekok. I was wondering in the Monero Support thread whether or not the binaries included here were the same as the officially released binaries. Is this the case?
sr. member
Activity: 264
Merit: 250
A quick update 'v0.38.2' has just been pushed, which changes the bundled binaries 'bitmonerod.exe' and 'simplewallet.exe' in order to mitigate the blockchain attack which happened a little while ago.

Test versions are not yet updated.
sr. member
Activity: 432
Merit: 251
what now?

Delete your blockchain folder which is - by default - located at '%AppData%\bitmonero', and then download the new 'bitmonerod.exe' from the Monero topic's original post. Replace it with the one found in Monero Client .NET's '\Resources\Software' folder, and then start the application. It may take a while to sync, but you'll be on the right chain.

still have a problem after resync nothing comes to wallet Sad miss last two days mining


Maybe it's a pool's problem, where are you mining?
sr. member
Activity: 264
Merit: 250
what now?

Delete your blockchain folder which is - by default - located at '%AppData%\bitmonero', and then download the new 'bitmonerod.exe' from the Monero topic's original post. Replace it with the one found in Monero Client .NET's '\Resources\Software' folder, and then start the application. It may take a while to sync, but you'll be on the right chain.
newbie
Activity: 38
Merit: 0
helo

i have problepm to sync wallet 0.38.1
from pool was send xmr but nothing come in to wallet:(


There was a blockchain spam attack 2 days ago, thus, the chain has forked, and you may be on the wrong fork. Please open http://localhost:18081/getheight while running the client (waiting about a minute after startup), and tell us what number is its output.

{
  "height": 202659,
  "status": "OK"
}

Yep, you're on the wrong fork.



what now?
legendary
Activity: 1762
Merit: 1011
helo

i have problepm to sync wallet 0.38.1
from pool was send xmr but nothing come in to wallet:(


There was a blockchain spam attack 2 days ago, thus, the chain has forked, and you may be on the wrong fork. Please open http://localhost:18081/getheight while running the client (waiting about a minute after startup), and tell us what number is its output.

{
  "height": 202659,
  "status": "OK"
}

Yep, you're on the wrong fork.
newbie
Activity: 38
Merit: 0
helo

i have problepm to sync wallet 0.38.1
from pool was send xmr but nothing come in to wallet:(


There was a blockchain spam attack 2 days ago, thus, the chain has forked, and you may be on the wrong fork. Please open http://localhost:18081/getheight while running the client (waiting about a minute after startup), and tell us what number is its output.

{
  "height": 202659,
  "status": "OK"
}
sr. member
Activity: 264
Merit: 250
helo

i have problepm to sync wallet 0.38.1
from pool was send xmr but nothing come in to wallet:(


There was a blockchain spam attack 2 days ago, thus, the chain has forked, and you may be on the wrong fork. Please open http://localhost:18081/getheight while running the client (waiting about a minute after startup), and tell us what number is its output.
newbie
Activity: 38
Merit: 0
helo

i have problepm to sync wallet 0.38.1
from pool was send xmr but nothing come in to wallet:(
sr. member
Activity: 264
Merit: 250
Could I install this client on an offline computer and create a wallet without connecting to the internet?

Yes, probably. Or if not, please try running the GUI with the '-noupdate' command line argument specified. Please provide feedback to me whether possible. Wink
sr. member
Activity: 264
Merit: 250
I tried 3 different versions and all of them appear to not have the functionality of having an auto-created XMR address/account.

Is it supposed to be that way? Or am I missing something?

I'll wait until the client is synced with the network first. Looks like it is "initializing" the default XMR address.

Creating a new account requires you to use v0.38.1, and downgrading makes you obeyed to remove the configuration file located at '%LocalAppData%\Jojatekok\MoneroClient.Net\'. Also, upgrading to v0.39.0-rc.2 requires you to remove the config file again because of an upgrade mechanism fail introduced by the new test releases, but that will be fixed in the next Release Candidate.

Otherwise, the application is considerably stable, especially v0.39.0-rc.2 or above (in the future). v0.38.1's account file creator should prompt you for password protection. The "initializing" text should disappear once rpcwallet initializes, so it may not stay like that for more than a minute, but if your 'account.bin' file is not up to date, then it may take an hour or even more.

Feel free to ask questions if you have any problems, I'll be glad to help you. Wink


v0.39.0-rc.2

rpcwallet.exe crash with 0xc000001d .

0xc000001d looked into Google.

I saw that there is a problem with the CPU does not support SSE 4.1

And I use Athlon II neo n36l the processor and it does not support the SSE 4.1.

And I found "/ D__SSE4_1__" a source from cmakelists.txt

This option does not seem to fit me.

It seems like bitmonerod.exe also included in the zip file.

Please modify it.

I just contacted the core developers about this issue, please keep watching this thread for further information!
newbie
Activity: 2
Merit: 0
v0.39.0-rc.2

rpcwallet.exe crash with 0xc000001d .

0xc000001d looked into Google.

I saw that there is a problem with the CPU does not support SSE 4.1

And I use Athlon II neo n36l the processor and it does not support the SSE 4.1.

And I found "/ D__SSE4_1__" a source from cmakelists.txt

This option does not seem to fit me.

It seems like bitmonerod.exe also included in the zip file.

Please modify it.

legendary
Activity: 2968
Merit: 1198
I tried 3 different versions and all of them appear to not have the functionality of having an auto-created XMR address/account.

Is it supposed to be that way? Or am I missing something?

Is there a difference between a wallet and an account? The GUI refers to accounts, specifically with 39.0 RC2 being incapable of creating an account while 38.1 is capable. Where exactly is an account stored?

Wallets are now called accounts in Monero for various reasons. They are the same thing. See my previous post for more details on importing. It would make sense to have them rename simplewallet to simpleaccount, though, right?

Thanks - I'll poke around. Yeah, simplewallet -> simpleaccount would be better. Same thing with the default account creating a wallet, wallet.bin, wallet.bin.keys, etc in the WalletData folder. Unless there's the intention to use both wallets and accounts for different reasons, that is.

No such plan. It is just that the wallet -> account concept was mentioned in the fireside chat as more of a direction than immediate change. So you will see those changes roll out over time.

Looks like it's already happening in RC2. I see AccountData\Account and associated files created instead of WalletData\wallet, etc.

Right, that's the plan!
Pages:
Jump to: