Left wallet open all day come back to it crash on client and errors. Wish it would be simple lol guessing it don't like Windows 8.1 x64
Problem signature:
Problem Event Name: APPCRASH
Application Name: OrangeCoin-Qt.exe
Application Version: 1.0.7.0
Application Timestamp: 09ef73c0
Fault Module Name: OrangeCoin-Qt.exe
Fault Module Version: 1.0.7.0
Fault Module Timestamp: 09ef73c0
Exception Code: 40000015
Exception Offset: 00d7b0bd
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: b03a
Additional Information 2: b03aa74b0464f520b7193f98a776061d
Additional Information 3: 7be8
Additional Information 4: 7be89ef21c86e5bf7e5deb22b4a95426
Are you using 1.0.7? No am using the latest updated one of the website and new links used and blockchain download deleted everything out other than my wallet.dat file and re did. Current version showing in client running at the moment is v2.0.1.0  I will try to delete everything back up wallet using prive key delete everything and import key in see if that works, as I have not tried this yet. Maybe the wallet or could be am using SSD drive and it does not like ti as I had sort of same problems with Bitcoin qt Ok, keep us posted. I've heard other weird things before about SSD's and crypto. I don't remember exactly what it was though. Ignore my banter.  What do you have in your orangecoin.conf? Little update on the situation.
Deleted everything started fresh took out all wallets started fresh one. Wallets all synced updated no problem. Imported wallet so have new address as well as old still not seeing the coins and says import successful bla bla bla restarted wallet re indexed still nothing on it so I do not get it. My next final step and I no doubt think this is going to be SSD over old scroll Sata being the problem as now been though every possibility.
Daft as it may seem with Bitcoin QT the problem is almost identical SSD being fast and wallet maybe cant keep up with pace of read/wrigt speed or something conflicting my end. Going to delete everything move over to normal SATA drive n see if that works. Is showing all history and chain updated but no balances. Yet I go on old client works fine before patched one but wont sync.
Small option to update feature and option. Next exe release ability to select where you want the app data to go or have freedom to use whatever hard drive locaion you want as theirs currently no option right now and default install is putting c drive app data.
Well after re doing bunch of times and importing again seems to be updating proper now. Stake working and balances their and waiting on stake to come though extra 80.22 or so and 15080.026575 currently staking. Nice to see the coin is back up and operational on Bittrex. I will be providing some ideas in private on irc if any devs about later on  Wow.... Bud YOU did not have to do all of that, first of all the network kind of depends how fast you can either download or upload data ( your pipe that you have subscribed to AKA the internet connection speed ) has really nothing to do with how fast your HDD is, the blocks are like 32KB a chunk as I have ran a packet tracer whiles syncing Orange Coin ( OC ), even watch a bootstrap load and watch the appdata\orangecoin blkindex file grow\build in file size. BUT I honor your perseverance, patience and troubleshooting ability! But also on a side note when we mean MANDATORY update it's because it is, new implications state after 2.0.1 going forward we have implemented Version BANHAMMER ( I LOVE IT!!! ) therefore older versions will no longer sync with the current version/protocol chain thus preventing the 2.0.0 massacre we avoided. AND CONGRATS on the recovery of your coins! Cheers! -Raven PS: I may have sounded stupid due to my basic knowledge of how blocks are transformed or created I have read many, many, many, articles it still confuses me hence why I have stuck to the PR\Marketing side of things, even though I have a degree in networking. HAHA ( What a waste of money! ) |
|
|
|
2.0.1 has successfully synced from scratch. Again, this sync test was done after block 292600 had already passed.
2.0.1 FTW!!!!
Very nice that was fast! |
|
|
|
By the way folks, The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue. I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now. This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy. SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!* We are now at #292613 Everyone! Hope everyone is experiencing the calm bliss of Staking. Warm Regards, ~SoopY~ Thanks for your dedication, soopy. Let's get an OC address from you. Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us. SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK!   Cheers! -Raven Still syncing that client, btw. @ 131000 fork me sideways. lol raven, you're a funny man. Ha, Halo that's your GFs Job! But I will stick it to the MAN! Posted new twat on twitter! RT please! RT'ed and tweeted again, myself. Thank you Buddy! |
|
|
|
By the way folks, The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue. I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now. This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy. SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!* We are now at #292613 Everyone! Hope everyone is experiencing the calm bliss of Staking. Warm Regards, ~SoopY~ Thanks for your dedication, soopy. Let's get an OC address from you. Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us. SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK! Cheers! -Raven Still syncing that client, btw. @ 131000 fork me sideways. lol raven, you're a funny man. Ha, Halo that's your GFs Job! But I will stick it to the MAN! Posted new twat on twitter! RT please! |
|
|
|
By the way folks, The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue. I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now. This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy. SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!* We are now at #292613 Everyone! Hope everyone is experiencing the calm bliss of Staking. Warm Regards, ~SoopY~ Thanks for your dedication, soopy. Let's get an OC address from you. Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us. SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK! Cheers! -Raven |
|
|
|
|
OH YEAH ONE BLOCK TO GO!!!!! BYE BYE 20%!!!!
GONE BABY GONE!
292601
|
|
|
|
|
So about that Soopy fund! I am all for it after this release!
|
|
|
|
Sent pm's to chainz and richie. Website is updated, 265k blockchain download removed, will put up a newer bootstrap when time allows. Going to go tweet, then I'm updating the OP.
Want me to make bootstrap? I can provide dropbox link if needed. Soopy's link does contain the necessary file anyway, just rename blk0001.dat to bootstrap.dat but don't use the other files in the download, except .conf. I understand that but an even more current chain doesn't hurt. |
|
|
|
Sent pm's to chainz and richie. Website is updated, 265k blockchain download removed, will put up a newer bootstrap when time allows. Going to go tweet, then I'm updating the OP.
Want me to make bootstrap? I can provide dropbox link if needed. |
|
|
|
|
I have my Node synced now as well! GREAT FREAKING WORK GUYS!!!!!!!
Connected nodes I have:

[
{
"addr" : "182.161.4.15:18872",
"services" : "00000001",
"lastsend" : 1441895243,
"lastrecv" : 1441895244,
"conntime" : 1441894704,
"version" : 60605,
"subver" : "/OrangeCoin:2.0.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 292514,
"banscore" : 0
},
{
"addr" : "79.23.217.110:22470",
"services" : "00000001",
"lastsend" : 1441895604,
"lastrecv" : 1441895610,
"conntime" : 1441894746,
"version" : 60605,
"subver" : "/OrangeCoin:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 280720,
"banscore" : 0
},
{
"addr" : "80.11.70.97:54635",
"services" : "00000001",
"lastsend" : 1441895243,
"lastrecv" : 1441895013,
"conntime" : 1441895013,
"version" : 60605,
"subver" : "/OrangeCoin:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 288564,
"banscore" : 0
},
{
"addr" : "69.204.247.90:50182",
"services" : "00000001",
"lastsend" : 1441895242,
"lastrecv" : 1441895243,
"conntime" : 1441895139,
"version" : 60605,
"subver" : "/OrangeCoin:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 292517,
"banscore" : 0
},
{
"addr" : "37.5.135.244:63973",
"services" : "00000001",
"lastsend" : 1441895279,
"lastrecv" : 1441895279,
"conntime" : 1441895279,
"version" : 60605,
"subver" : "/OrangeCoin:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 288597,
"banscore" : 0
},
{
"addr" : "69.204.247.90:61204",
"services" : "00000001",
"lastsend" : 1441895455,
"lastrecv" : 1441895455,
"conntime" : 1441895453,
"version" : 60605,
"subver" : "/OrangeCoin:2.0.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 32000,
"banscore" : 0
}
]
|
|
|
|
Anyone with a node up to date please?
I will have one in 3 min, OK maybe 10. Sorry. I will post AS SOON AS IT IS DONE AND VERSION BLOCK WORKS! partner 104.179.213.26:62739 using obsolete version 60604; disconnecting ProcessMessage(version, 111 bytes) FAILED disconnecting node 104.179.213.26:62739 connection timeout trying connection 37.5.135.244:18872 lastseen=2.6hrs connection timeout Flushed 3 addresses to peers.dat 28ms trying connection 37.5.135.244:18872 lastseen=2.6hrs accepted connection 5.196.109.69:37098 partner 5.196.109.69:37098 using obsolete version 60604; disconnecting ProcessMessage(version, 111 bytes) FAILED disconnecting node 5.196.109.69:37098 connection timeout |
|
|
|
HOLY S*** THIS LOADED FAST!!!! And a typo in the version posting: 2.0.1 not 2.0.0. I know you were tired! its okay. |
|
|
|
|
Get Ready For Juicy Features!
|
|
|
|
Hey folks, Soopy has given me another client to test. Syncing from scratch, will keep you all posted. Thank you, soopy. Going out for now, it's syncing anyway. The gf requires food and alcohol. Stay tuned. Thank you Soopy! Hopefully it syncs fast!! We have lots of attention right now! |
|
|
|
Thanks for the refresher! |
|
|
|
|
It's been so long how many posts do we need again?
|
|
|
|
By the way, raven, I trust your link, I took it down in case I violated forum rules for some strange reason. We don't need the OP or my account getting a banhammer for weeks during this fragile time period. I hope you understand where I was coming from.
This 6 minute time limit between any account activity is so aggravating. I need to post more with this account to get to jr member.
I understand, they should give leeway, or allow to connect accounts with some sort association with our actual accounts. Ita probably the .tk domain .... |
|
|
|
|
Show Posts
