Topic: Is there an ACTUAL working bitcoin app? (Read 2241 times)

I'm with the OP. What on earth are the devs doing???

I stick with what I call audio OS, or OS's that you can load a plethora of softsynths in without lag etc.. win98se in my opinion is the best audio video OS ever, shame they had to fuck it by adding the ntfs..

And many win98se audio applications are simply the best, fuck all this cloud shit where you store your saved work on someone else's computer.. most dont realise tiat this act gives them your rights to your music, as they recorded (stored) it for you, first, by the simple act of you clickin save.

I have Win98SE too. And for some reason, I've keep MSDOS 6.22 (and Win 3.11).. I've lost my Win 95. Have 2000 somewhere in one of these hard drives at work.

Regardless of OS, you should be fine if it sits behind a modern firewall or router. Nothing from outside will get in. (Not easily anyway.)

My little factory has 20 desktops with XP. The network is more-or-less isolated from the internet.

With regards to XP, and it being a dead os, well, not entirely, see, here in the uk, the gov is paying microsoft to continue with updates for xp. Personally, I never use internet explorer, and un-install it in it's entirety upon installation of said os.. firefox or palemoon, and even these make me wanna puke, so overbloated I wonder why they dont just go back to the origional version, since most anti virus's will pick up any malware/virus's before they do damage.. imagine.. windows 98se.. now there's a lesson on how to get rid of a decent os..

As for linux, haha.. it's a mess.. every possible key combo recorded on a 64 key keyboard before initial release.. now what does this mean I wonder.. hey, it's in the chip.. anything you think you can do on linux was recorded before linux was a viable system.

I am an audio engineer, and have xp, linux (backtrack), and 98se on seperate hard-disks, and simply choose which os to boot from using the f12 key, nae feckin aboot..

But I see no reason to move to an os that requires twice the memory for less than half the performance..

And I never save material made by me online

And I just dumped bitcoin.

Fuck all this update crap.. go plant a tree time..

my sides are in orbit

This is somewhat offtopic, but anyway, hackers have been reverse engineering new security updates for latest versions of Windows to try and find security holes in Windows XP because Microsoft no longer releases security updates for XP (except in one recent case).

There have been some severe security issues patched recently (such as the IE one: http://www.usatoday.com/story/news/usanow/2014/05/01/microsoft-issues-internet-explorer-security-fix/8562737/ ) and all Windows XP users could be easily attacked using these security flaws.

You really should NOT be using XP or you'll be easy pickings for hackers.

Anyway, Bitcoin Core fully supports XP. I would try to help you with whatever issue you're having but I think it'd be a waste of my time.

That's not so bad, you know. I pushed for XP support for Armory (see their sub-forum). I used XP all the way in almost every hardware I got.

XP is officially dead. But, like many corporations, I have it installed in almost all my computers at the factory; about 20 desktops. (I run a small clothing manufacturing thing.)

I don't have the time anymore to try and figure out why I can't do a virgin fresh format XP install on a completely wiped drive that previously had XP on it for the last 4 years; same with the new laptop. For some reason it's not working, even turning off AHCI to IDE, but that shouldn't have been the problem.

Try 7. I usually set my XP to "classic" look, so I did the same with 7. Now I miss the darn "edit" command (64 bit does not have edit!!!)

My brother-in-law has praises for 8.1 ... I installed that on an even older laptop, just to get familiar with it. New look bothers me though.

Yup, the stupidity of the devs.. who'll eventually stop xp support

Ach, more likely there's a stupid isp playing with hindering p2p traffic.. virgins main testbed is where I live, then the usa get it 2 yrs later lol, just like the docsis 3 update. Since 2 months ago, or when the police starte clamping down on torrent sites etc, even web pages are slown to a crawl, I blamed it on ajax scripting once.. then put it down to so many websites looking the same..

Notice how torrents of late are getting slower and slower regardless of the popularity?

This would affect p2p..


Gonna go for a fresh format soon, so will just wait till then, whits a few more days..??

As for re-installing xp, I have never failed to put it on any machine..

stupidity will defeat bitcoin

I agree it's likely if you're doing a lot of audio editing that you probably would have noticed a hardware issue, but it's still possible that there's a hardware issue. The only way to be certain is by testing (e.g. an error scan with HD Tune or a "Scan for and attempt recovery of bad sectors" in Windows...)

From my own personal experience: when my DRAM died, the only applications I had trouble with were Armory and Bitcoin Core. Everything else (for example compilers and games, both of which are hardware-intensive) seemed fine. It was only after I ran Memtest86+ that I was convinced it was my hardware's fault, and not Bitcoin Core's.

Ahhh... XP... Until last month, I preferred to use XP SP3 (with updates until the last one, actually got a slip-streamed iso for doing fresh installs)

But when I had XP SP3 last month, I was also using the latest bitcoin version, 32 bit. That worked for me.

Major reason I switched to 7 is because I got a new laptop and I could not install XP on it, no matter what I tried. Wierd, but I didn't waste too much time. After a week of trying I gave up and installed 7 instead.

Besides, I now have 8 gigs of RAM so it was probably better I switched to a 64 bit OS. (Old laptop had 2 gig of RAM, so I saw no need to upgrade from XP SP3.)

I have a bunch of older laptops and desktops running XP SP3, I'll try and see if bitcoin core works there.

Another possibility is a DRAM memory problem. Memtest86+ can help to rule this out (or in): http://www.memtest.org/#downiso

Also, just FYI, because Bitcoin Core can be both disk and memory intensive at times, it wouldn't be surprising if it were the only app that was having problems. In other words, there might be a hardware problem even if all of your other apps are running just fine.

No guarantees it's a hardware problem, but it's definitely a good thing to check for.

Hard disk is fine, runnin 6 of 12 x 500gig seagate pipeline hd 2's.. and several of my audio apps wont work if there was an hd error..

Oh, we are getting somewhere.

If your hard drive supports SMART (https://en.wikipedia.org/wiki/Self-Monitoring,_Analysis,_and_Reporting_Technology), you could try and run a tool like http://www.hdtune.com/ (there are others). Might be a hard drive problem. How old is it?

Well, I'm on xp sp3, (stayin on it) 50mb cable connection.. - The problem, which I should have stated to start with instead of gettin rid o lamer answers lol, is that since installing latest version, I have been unable to access the app.

It started at first with bad:alloc I tried the usual fix's, including starting blockchain again, then adding wallet after blockchain completed, which worked, kinda.. the app quit once i got my last payment, and I have been unable to get passed the bad:alloc problem.

So uninstalled latest and re-installed previous version, same bad:alloc, so decided to start afresh, re-downloaded blockchain, let it complete, then added wallet, to no avail, only this time, I tried the -r flag, to rebuild the index, and when I tried that, it killed the app, and now the app just wont start period, I got no virus's/malware etc...

Seems everytime a new version is released, the problems increase.. and dont be listening to folks who dont know how to build a major system designed for mega sound recording usage, meaning, my pc is fine..

A copy of the last log only shows the latest after the -r flag, so I cant re-produce the bad:alloc, which I presume is a bad allocation of whatever part of the blockchain?

And thanks for the effort

Log:

file wallet.dat has LSN 1/11488, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/6100
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
wallet.dat: write failed for page 265
wallet.dat: unable to flush page: 265
PANIC: fatal region error detected; run recovery
wallet.dat: write failed for page 267
wallet.dat: unable to flush page: 267
txn_checkpoint: failed to flush the buffer cache: DB_RUNRECOVERY: Fatal error, run database recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\Documents and Settings\-----\Application Data\Bitcoin\wallet.dat
Open file handle: C:\Documents and Settings\-----\Application Data\Bitcoin\database\log.0000000001
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/6727
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/11488, past end of log at 1/6727
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/6727
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/7354
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/11488, past end of log at 1/7354
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/7354
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\Documents and Settings\-----\Application Data\Bitcoin\database\log.0000000001
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/7981
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/11488, past end of log at 1/7981
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/7981
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/8608
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/8608
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/9235
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/9235
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/9862
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/9862
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\Documents and Settings\-----\Application Data\Bitcoin\database\log.0000000001
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/10489
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/11488, past end of log at 1/10489
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/10489
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\Documents and Settings\-----\Application Data\Bitcoin\database\log.0000000001
PANIC: fatal region error detected; run recovery
file wallet.dat has LSN 1/11488, past end of log at 1/11116
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/11488 past current end-of-log of 1/11116
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 7
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
File handles still open at environment close
Open file handle: C:\Documents and Settings\-----\Application Data\Bitcoin\database\log.0000000001
PANIC: fatal region error detected; run recovery
Database handles still open at environment close
Open database handle: wallet.dat/main
Database handles still open at environment close
Open database handle: wallet.dat/main


Running recovery does nothing if the app wont start..

And my db is in the same place it always has been, installed dir..

I'm using bitcoin core, and it's working for me. Something is wrong with your setup, your network, your computer, your internet connection or something.

What OS are you on?

Here's some info from mine on Windows 7 64 bit. I'm on a 3 mbps DSL home connection, in a third-world country. We get typhoons a lot and my roof is leaking, but my internet and my bitcoin core seems to be working fine.

I'm using a laptop too, so that's not exactly a supercomputer. (And if I may mention, it's full drive encrypted and I'm on a regular platter hard drive, not SSD.)

getinfo

{
"version" : 90201,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 32124.11090367,
"blocks" : 322351,
"timeoffset" : 0,
"connections" : 835,
"proxy" : "",
"difficulty" : 29829733124.04041700,
"testnet" : false,
"keypoololdest" : 1364136185,
"keypoolsize" : 46,
"unlocked_until" : 0,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}

Yeah, put a picture of your girlfriend as your avatar in stead of someone else's.. ya fuckin weirdo.. I'd have ya for stalkin

Wow.. so many problems created by flaming trolls..

The app wont sync, period. Tried and tested on 3 computers. Get ready, for there IS a way to defeat bitcoin.

It's funny how google shows more results over the bad allocation of whatever.. something to do with blockchain. Never happened until latest version was installed, meaning problem can be found in latest version. Cunt is, that even after un-installing that version and going to a previous version, same problem.

I'm fed up starting again to find it wont make a difference, I'm fed up downloading some shitty blockchain required before I can spend what I earned, I'm fed up of people messing with the app when there was NEVER anything needing fixed, or bitcoin would have been hacked by now.

Logs, fuck logs, am not the only person to have seen this, and the people who re-write the app KNOW this.

As do those who know how many weeks it may take just to bring wallet up to date, it's more than a farce, it's like handing out paper money before the tree's were chopped down to create it...

I want to spend my bitcoins today, not next fuckin year.

Is there anger in my writings? GOOD.

You think I need a beer? STOP telling me I do and buy me one.

You think I need anger management? Fix the fuckin app, that will work.

What the FUCK is bad:alloc?

I know you are just a bit coin hater troll, but I will reply anyway just for fun.

I have already given you the answer.  There is no problem with bit coin, the problem is user error.  You sir are the problem.

A:  Wrong.  You CAN use the original bitcoin app or block chain.
B: Wrong,  the bitcoin app works on cheap low end PC computers.  Not just Macs.
C:  We know you are not seriously asking a real question.  Bitcoin is less than 10 years old.  So when you troll, you get trolled back.
D:  DDOS will not work on a peer-to-peer system.  DDOS is also illegal.  DDOS is also outdated and not effective on any single server with a Comcast ISP (and others that ignore such lame flood attacks)

Anything else we can help you with?