Jump to content

Crashed Forum Data Update


Recommended Posts

Hi all,

Okay, here's an update on the crashed forum data:

After finding out the backups were pooched due to being transferred in ASCII, I tried to repair the .gz files with WinRAR. No go.

I then found an obscure Windows command line program called NOCRLF that fixes self-extracting archive files. My heart was all aflutter when I found out about it in a backwater news group. I was truly leaping for joy when I actually found the program. But alas, it too was unable to fix the file.

So, what do all hackers do with stubborn files, they go to the HEX EDITOR (MUHUHUHUHAHA!).

I like to think of the Hex Editor as the ultimate anal probe for files that vill not talk! So, I took the file into my basement laboratory, turned on the scary little bare 40 Watt lightbulb for effect, strapped the file down most wuffly---you should have heard the file scream...I'll never get that out of my head---and applied the HEX EDITOR (muhuhu...awww forget it!).

Yeah, I got inside that mutha and yes! Yes, by golly! I can see the old posts. Can I ever get them out and restored? Not likely, but the data is there! It's....It's....ALIVE! (now one of you guys has to find that pic of Gene Wilder in Silent Movie).

So, if there is some data that you really, really want (I'm talking to you Gunny, especially about those posts in the squad room) then try your durndest to remember a good phrase from the post and I'll go in with the anal Hex probe and git it out fer ya!

Okay, I'm totally wrung out now, what with all the brainal machinations and psychotic rantings, it sure does take it out of a fella.

Think I'll have a nice bath with my SpongeBob SquarePants' Bikini Bottom Brand Bubble Bath Foam to relax :)

Yep, I'm totally bonkers :D

Link to comment
Share on other sites

Yep! It's official. The backup files are crap.

Here's a little tip to any application programmers out there:

If you offer your clients built-in backup and restore, make sure you write a line of code that alerts your users that the file backup was incomplete rather than popping up a cute dialogue box that prompts the user to download the incomplete file.

Here's what I found on the last line of our Invision Power Board backup file with the use of my hex editor:

<b>Fatal error</b>:  Allo41b494  77 65 64 20 6d 65 6d 6f 72 79 20 73 69 7a 65 20 6f 66 20 38 33 38 38 36 30 38 20 62 79 74 65 73 20 65 78 68 61 75 73  wed memory size of 8388608 bytes exhaus41b4bb  74 65 64 20 28 74 72 69 65 64 20 74 6f 20 61 6c 6c 6f 63 61 74 65 20 31 32 37 37 31 20 62 79 74 65 73 29 20 69 6e 20  ted (tried to allocate 12771 bytes) in41b4e2  3c 62 3e 2f 76 61 72 2f 77 77 77 2f 68 74 6d 6c 2f 31 2f 73 6f 75 72 63 65 73 2f 41 64 6d 69 6e 2f 61 64 5f 6d 7973<b>/var/www/html/1/sources/Admin/ad_mys41b509  71 6c 2e 70 68 70 3c 2f 62 3e 20 6f 6e 20 6c 69 6e 65 20 3c 62 3e 33 33 34 3c 2f 62 3e 3c 62 72 20 2f 3e 0aql.php</b> on line <b>334.
Pull out the hex crap and you get:
Fatal error:  Allowed memory size of 8388608 bytes exhausted (tried to allocate 12771 bytes) in /var/www/html/1/sources/Admin/ad_mysql.php on line 334

Basically, the program offered me an incomplete backup file to download without a peep of an alert that it had run out of memory in that folder, so I assumed (my bad) that the backup was successful. Nice of it to write the error to a file I couldn't open, though!

So yes, the data is well and truly gone for good.

Beer anyone? :)

Link to comment
Share on other sites


  • Create New...