The General Chatter Thread.

[Jonzu95]

There are LOADS of variants of Jerusalem. It stopped being funny when I hit the tenth one. Now it's hilarious

What is wrong with you, Scourge? >_<

I'm researching viruses. It's certainly more entertaining than Finnish 4chan

You know nothing about finnish 4chan, soo...

[Scourge of teh Galaxy]

Two words










Ghost

Balls

[Team 9]

Two words










Ghost

Balls

honk

[Philippa]

Welp, got my hand stuck in a letterbox for 5 minutes delivering leaflets today. And also saw one that read in permanent marker "NO sh**e Pls".

[Velocity EVO]

There are LOADS of variants of Jerusalem. It stopped being funny when I hit the tenth one. Now it's hilarious

What is wrong with you, Scourge? >_<

I'm researching viruses. It's certainly more entertaining than Finnish 4chan

You know nothing about finnish 4chan, soo...

We dont need to know much about things to know they suck. I could go off on a tangent on about a million things like that, but I wont.

[Badger]

Hey guys, do you think I should class the DBase virus under annoying or dangerous?

When DBase is executed, it checks if it is already in memory, and if not, becomes resident. It infects .com and .ovl files.
When a .dbf file (the main file format of the dBase database management system) is written to while the virus is in memory, the information sent to the file will be garbled. When the file is loaded, the virus will show the file as if it were normal. If the virus is removed after the files have been garbled, they will be permenantly garbled. It may do this to other files whose name ends in .dbf, regardless of whether or not they belong to the dBase program.

The virus creates a file named bugs.dat in any directory where .dbf files are stored. This file keeps track of what files were corrupted and what they were corrupted with. When this file has not been written to for 90 days, the virus overwrites the file allocation table and root directory of drives D: to Z:. This section of the virus's code is buggy, and may not

In addition to the damage to .dbf files, programs larger than 63,415 bytes will no longer be loadable.

You need to make a thread about this stuff, I find it highly interesting.

[Scourge of teh Galaxy]

Hey guys, do you think I should class the DBase virus under annoying or dangerous?

When DBase is executed, it checks if it is already in memory, and if not, becomes resident. It infects .com and .ovl files.
When a .dbf file (the main file format of the dBase database management system) is written to while the virus is in memory, the information sent to the file will be garbled. When the file is loaded, the virus will show the file as if it were normal. If the virus is removed after the files have been garbled, they will be permenantly garbled. It may do this to other files whose name ends in .dbf, regardless of whether or not they belong to the dBase program.

The virus creates a file named bugs.dat in any directory where .dbf files are stored. This file keeps track of what files were corrupted and what they were corrupted with. When this file has not been written to for 90 days, the virus overwrites the file allocation table and root directory of drives D: to Z:. This section of the virus's code is buggy, and may not

In addition to the damage to .dbf files, programs larger than 63,415 bytes will no longer be loadable.

You need to make a thread about this stuff, I find it highly interesting.

Where would I even put a thread on viruses? Software and OS?

[NFX]

I'm now trying to put Circus Galop into Guitar Pro 5. I've got the intro part pretty much bang on, I reckon, but I reckon it'll take about three months to get it properly done.

[Philippa]

DJ Blu is done. Some weird sh** happened to her face and now it's browny, orange-y, grey. It used to be green. And brown too.

Anyways. If I find the scanner I'll post it up tomorrow.

[Badger]

Hey guys, do you think I should class the DBase virus under annoying or dangerous?

When DBase is executed, it checks if it is already in memory, and if not, becomes resident. It infects .com and .ovl files.
When a .dbf file (the main file format of the dBase database management system) is written to while the virus is in memory, the information sent to the file will be garbled. When the file is loaded, the virus will show the file as if it were normal. If the virus is removed after the files have been garbled, they will be permenantly garbled. It may do this to other files whose name ends in .dbf, regardless of whether or not they belong to the dBase program.

The virus creates a file named bugs.dat in any directory where .dbf files are stored. This file keeps track of what files were corrupted and what they were corrupted with. When this file has not been written to for 90 days, the virus overwrites the file allocation table and root directory of drives D: to Z:. This section of the virus's code is buggy, and may not

In addition to the damage to .dbf files, programs larger than 63,415 bytes will no longer be loadable.

You need to make a thread about this stuff, I find it highly interesting.

Where would I even put a thread on viruses? Software and OS?

Sounds about right.

[Philippa]

Anyways. If I find the scanner I'll post it up tomorrow.

Ah balls. My Dad says that we don't have a scanner and won't for a while until we get a wireless printer. Sorry about that.

[Enigm@]

Hey guys, do you think I should class the DBase virus under annoying or dangerous?

When DBase is executed, it checks if it is already in memory, and if not, becomes resident. It infects .com and .ovl files.
When a .dbf file (the main file format of the dBase database management system) is written to while the virus is in memory, the information sent to the file will be garbled. When the file is loaded, the virus will show the file as if it were normal. If the virus is removed after the files have been garbled, they will be permenantly garbled. It may do this to other files whose name ends in .dbf, regardless of whether or not they belong to the dBase program.

The virus creates a file named bugs.dat in any directory where .dbf files are stored. This file keeps track of what files were corrupted and what they were corrupted with. When this file has not been written to for 90 days, the virus overwrites the file allocation table and root directory of drives D: to Z:. This section of the virus's code is buggy, and may not

In addition to the damage to .dbf files, programs larger than 63,415 bytes will no longer be loadable.

You need to make a thread about this stuff, I find it highly interesting.

Where would I even put a thread on viruses? Software and OS?

it corrupts your actual database files, so yeah it's dangerous.

[Enigm@]

lol
>be forum faggot
>have a girlfriend in real life
>mfw

[Team 9]

https://gametechmods.com/forums/index.php/topic,9639.msg477813/topicseen.html#msg477813

^EPIC VIRUS THREAD^

[Scrap Daddy]

I bet she's an ogre enigma. Post nudez and I shall be the judge.

[Enigm@]

I bet she's an ogre enigma. Post nudez and I shall be the judge.

uuum no because i don't want to get arrested for child porn ?

[Naryar]

<= change to MANLIER avatar

Also, more helpful sig.

[kill343gs]

<= change to MANLIER avatar

Also, more helpful sig.

you're just mad the people of this forum wont make badass fanart of you

[Naryar]

<= change to MANLIER avatar

Also, more helpful sig.

you're just mad the people of this forum wont make badass fanart of you

They will, in time...

[Scourge of teh Galaxy]

<= change to MANLIER avatar

Also, more helpful sig.

you're just mad the people of this forum wont make badass fanart of you

They will, in time...

The only thing we'll ever draw you as is a stereotypical Frenchie with no hair and red eyes