Most here relate god to jesus, this is not the question, and a problem. The question is proof of god, not any character in a book called the bible. Why are there not as many other religions commenting? Cause they dont do your head in with make believe stories from the youngest book in religious history, and prefer to just know without forcing their religious writings on people who simply wish to question for the reason best fits their search..?

Maybe go read the Kybalion or sumat more REAL!

Go to your NIC (network card), right click/properties/configure click advanced, look for network address.. change this to any 12 digit number, click ok, then disable/re-enable NIC after about a minute, voila, should be a new ip, works every time with any isp.

Note no VPN or whatever?


Yeah thanks decks.. any other docsis hacks..? yup..

Ps, Jesus's great great great great great (how many times is it?) ancestor is a whore by the shore over the water, in the kingdom of fife, lol...

Priv Msg in my inbox:

Duke_Charlie
Newbie
*
Offline

Activity: 2



View Profile Personal Message (Offline)
Trust: 0: -0 / +0(0)
   
info on mango j
« Sent to: Decksperiment on: Today at 14:07:22 »
« You have forwarded or responded to this message. »
   Reply with quoteQuote ReplyReply Remove this messageDelete
FYI this is the guy you dealing with who currently has this profile here https://bitcointalk.org/index.php?action=profile;u=79896
The guy who talks and posts such a BS he is a 13 times convicted felon and he uses social media and blogs to target more victims to scam and fraud yes he is Michael S. Prime.Before you post anything have a look at all the links =)



http://btcraven.com/BTCRaven_Escrow.html
https://www.indiegogo.com/projects/zungun-taser-2x-the-range-1-3rd-cost-of-others
http://zunguns.com/Home.html
http://www.okcupid.com/profile/ZunGuns?cf=profile_similar

plus to really know who he is look at this
http://wa.findacase.com/research/wfrmDocViewer.aspx/xq/fac.20110524_0001206.WWA.htm/qx
http://caselaw.findlaw.com/us-9th-circuit/1122829.html
http://www.ripoffreport.com/r/Insanity-Productions-llc/nationwide/Insanity-Productions-llc-owned-by-an-ex-felon-Mike-Stephan-Prime-Stole-Personal-Property-1154717

Pish.. as for the sound, it's that good I can hear the battery run out

And wether we beleive in god or not, it is the devil who instil's fear.

Correct me if I'm wrong, but Israel is NOT in egypt? Neither does a sea part them.

How can it be?

When I was young I thought there was only one bible. Then I heard of the King James bible.. then I read of at least 10 more remix's of the same tune, not one of them has an accurate date.

The problem for me with regards to god is the fact that 'god' denotes a greater or higher intelligence than man, proving life beyond our planet, that not only existed before everything else, but will be, when all is gone into the darkness once the last light fades.

So you either accept that there is indeed life 'out there' beyond our comprehension, but alive, meaning 'alien' of sort's, or we on this wee ball are it, period.

With regards to the parting of the red sea.. there would also be remnants of the tidal surge along the entire coast(s) of the red sea, written of in books far NEWER than the bible, in the form of tsunami etc, like the plethora of roman soldiers remains, the remains of horses.. how many horses would be to a carriage? 1, 2, 3, 4 even. Lets assume it's a time of war, it's safe to assume that if any at all, there would only be a few chariots pulled by 1 or 2 horses, at least one of which, whose remains would still be attached to the carriage, allowing for ANY tests. Of course only the wood was found.. I wont go into how many fishing village's would have been wiped out by the sheer mass of water, (no historical event depicts this) and again, the surge of water as it returned would in itself 'echo' so many times, someone would have written of it in any other way, other than a bible.

I'd like to see proof the bible was written when claimed.

I'd also like the bible bashers who think that ANY story from the bible is a genuine 'proof' for the existance of god, to stop preaching. This is a scientific search, for proof of god, not a lets decide which holy book gets more coverage.

NOTHING in the bible can be proven. (excluding the occult mathematics etc.. )

I'd be more than willing to argue any point within reason.. and of course, carriages could be thrown from any ship.. bet there were'nt an oldish bible.. cause God, if and when he shows himself, will probably kill all christians for claiming everything was cause o him. I mean, if you did sumat wrong and got away with it for infinity, you'd have to admit that that sooner or later, you will get caught, and no-where in the bible does it say that what god did was good, only that his creation was good, when in fact it was an act of pure evil.

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..

Sony MD range.. look for the dj headphones, now there's consideration for sound engineers who work with LOUD audio 24/7 with ZERO ear damage.. the quality is only as good as the equipment, unless of course you use digital.. then you'd be as well keepin the ones you got, cause that base is only good fore hiding the extreme lack of audio quality.. I have an iphone 5s, wish I never bought it, the amount of folks praising the 5s's audio quality is sickening.. fuckin ass kissers who get nowt but screeeeeeeeech.....

Well, it has to be said, that there has been so much written from the 'christian' perspective, that one should wonder how on earth we survived the last 2000 years. So a guy worked miracles, yet there is no proof of these miracles. Christians attribute everything they say, to god, despite having no actual proof of the sucker.. I mean, c'mon, what was the actual point of god being born as Jesus just to show you what I, God, as Jesus, can do.. did he leave any hints that we could part the red sea? NO. Miracles? Prove them. No-one can, period. For if the Red sea was parted, the debris in the water would also be cast with the water to either side of the gap the people of exodus would have used to travel through.. 2000 years later the evidence of the red sea being parted would be VERY visible today, considering there is a mountain of bones from animals who had no 'business' being at the part of the planet where they (apparently) are not indigenous, and thousands of years older than the parting of a sea.. this is bollox

What I think most christians CANT accept, is that every non-christian see's christianity's excuse for everything is blame it on god. How many christians are following that madman obama? All of them.. but he's a muslim no? So America, wake up, you are no longer a christian entity, you are a nation of muslim killers, which is why the only support you have for the bombing of syria is from their local neighbours.

Just when you think christianity rules the world, you realise you are, like all masons and jews, about to be hounded out of existance, just so we (the seekers) dont need to hear about miracles that are impossible to comprehend, never mind prove.

CHRISTIAN churches everywhere with locked doors (no wonder) sitting on pagan ley lines, or intersections, which in turn are best viewed as spiral's. The very reason churches have steeples is to bring this spiral closer to the etheric vehicle known as aurora borealis, which is in fact the MAGNETISM which in turn becomes akasa which flows to the nerves and tissues.. hence the micro/macro-cosm.

I think christians should stop debating the pro's and cons of YOUR RELIGION, and start providing what the op requested, scientific proof, meaning, NO FUCKIN BIBLE SHEITE!!!!!!!!!!!!!!!!!!!

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..

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..

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?

Put that beer on your head, while I blindfold myself before takin a random guess at where the bullet will end up..

Hmm.. not one, 'hey, I know of the badaloc bug, nah, bitcoin app syncs just fine', sorry to burst your bubble, but it has'nt synced in over 8 weeks, including several 'start again by downloading blockchain' crap.

Well, if your all so fuckin expert, answer what the bad alloc problem is then? What no answer?

You didnt think for a second I'd expect anyone here to answer without some bullshit hops we gotta jump through.. nah, as  said in my kill bitcoin thread, leave it to the dev's.. they'll ensure you:

A: cant use the origional bitcoin app or blockchain..

B: You gotta use a bitcoin app made for supercomputers that eat the planet, and make sure the blockchain is compressed for no other reason than it'll save an hour of downloading..

C: Figure out how to stop arseholes replying instead of those who know the ANSWER to the problem..

D: Seriously ddos the blockchain.. will this work?