On Sat, 22 Nov 2014 23:22:22 +0000 (UTC), Dustin wrote:

> Jax  wrote in
> news:XnsA3EDB2939EC03JAX@127.0.0.1: 
> 
>> Dustin  wrote in
>> news:XnsA3EC879E35625C9X238BHEUFHHI5RJ791@192.254.233.145: 
>> 
>>> ~BD~  wrote in
>>> news:gLWdnZsCc4lu5vLJnZ2dnUVZ7s-dnZ2d@bt.com: 
>>> 
>>>> I've only just noticed this comment!
>>> 
>>> Liar. I've mentioned it numerous times before.
>>>  
>>>> 
>>>> 
>>>> "*The virus has a bug* and it does not supply command line
>>>> options to the host program correctly, so every program that
>>>> operates with command line parameters will work incorrectly
>>>> after infection." 
>>>> 
>>>> 
>>>> 
>>>> So Dustin's not QUITE the wizard he thinks he is! ;-)
>>> 
>>> Wrong again hotshot. No bug. One of several ####ups in the
>>> description. Irok was written in ASIC. ASIC string limit is 80
>>> characters. Any command line options which exceed 80 characters
>>> due to a limitation in the language used, will not be passed
>>> entirely. No bug, though. 
>>>  
>>>> I must add that this activity occurred a very long time ago and
>>>> Dustin is no longer wearing a black hat!
>>> 
>>> Yet you couldn't resist bringing it up, in an effort to smear and
>>> slime again. You're a total loser, david.
>> 
>> Dustin it may not be a bug but it's a shortcoming of ASIC. As you 
>> know it's called ASIC because of it's many shortcomings. It's no 
>> surprise the author doesn't use it any more and has abandoned
>> future development. 
> 
> I'm well aware of the fact that it isn't a bug. I agree, it's a 
> shortcoming (imho) of ASIC. I've discussed this with ASICs creator 
> before though. He didn't think it was a big enough deal to go back and 
> retool the compiler and language itself. Turned out, alot is actually 
> involved in increasing max string limit. 
> 
> It's called ASIC because in some ways, it's almost like BASIC and yet, 
> also bears a close resemblence to assembler in some ways. These aren't 
> necessarily shortcomings, it's just the way the language is written. 
> It's expandable so that you can overcome many of the limitations, 
> though. It was the perfect language to prove my points concerning pooh, 
> though. He wouldn't bite with the assembler sources, but ASIC can give 
> you a very false sense of understanding it. As he clearly demonstrated 
> for us all. It was very funny, so you know.
> 
> Another thing I didn't bother mentioning concerning my decision. The 
> goal of a virus isn't to be the biggest bytesize as you possibly can. 
> The goal is actually to make yourself as small as you can. It made no 
> logical sense to use external routines of any sort, risk possible 
> corruption and make the final footprint larger to support a command 
> line that exceeds 80 characters in length. 
> 
> Another thing that company got completely wrong in the description is 
> the claim that irok trashes files and/or the hard disk. Irok only 
> erases checksum files for various antivirus programs. It never 
> reformatted or corrupted a users hard disk. They weren't the only 
> company to be in a rush and make that claim though. Most of the big 
> players did at one point. 
> 
> Atleast one antivirus company lifted MY description of my virus from 
> alt.comp.virus practically verbatim and passed that off as the work of 
> one of their researchers. They initially claimed on the description 
> that irok erased user data. They revised the description with my own 
> description, changing very little of MY post in the process.
> 
> The antivirus industry wasn't always the great industry it is now, 
> touting the lets protect all the users slogan. They have a semi shady 
> past too. It wasn't uncommon to see some antivirus companies abusing 
> their status to bend the ear of a reporter and talk complete #### about 
> a virus or virus author, either. Graham Cluley was notorious for doing 
> that.
> 
>> Why does a self-proclaimed wonder programmer like you use such 
>> inadequate tools? Your lack of understanding of ASIC's shortcoming
>> caused you to mess up Exevalid. best go find something easier to
>> work with. Just saying!
> 
> self proclaimed wonder programmer? I don't know what you mean by that 
> statement. While I find your spin concerning ASIC and exevalid to be 
> somewhat entertaining, it's still spin and thus, not correct. I asked 
> you if you knew what a failsafe was and you declined to answer numerous 
> times; so it's clear you still don't know. As exevalid has one, your 
> friend pooh disabled it when he removed the abs command. I broke 
> nothing, I understood what ASIC was doing. Pooh did not. Pooh broke the 
> program and tried to deflect from his own failure in showing me up.
> 
> As you're doing now. It's getting old, jax. You need to try something 
> new, and this time, try honesty.

Ignore this hasbeen liar. He was exposed as a two bit sloppy nobody by the
mighty Pooh. 

-- 
p-0.0-h the cat

Internet Terrorist, Mass sock puppeteer, Agent provocateur, Gutter rat,
Devil incarnate, Linux user#666, BaStarD hacker, Resident evil, Monkey Boy,
Certifiable criminal, Spineless cowardly scum, textbook Psychopath, 
the SCOURGE, l33t p00h d3 tr0ll, p00h == lam3r, p00h == tr0ll, troll 
infâme, the OVERCAT [The BEARPAIR are dead, and we are its 
murderers], lowlife troll, shyster [pending approval by STATE_TERROR], 
cripple, sociopath, kook, smug prick, smartarse, arsehole, moron, idiot, 
imbecile, snittish scumbag, liar, total ******* retard, and shill.

Honorary SHYSTER and FRAUD awarded for services to Haberdashery.
By Appointment to God Frank-Lin.

Signature integrity check
md5 Checksum: be0b2a8c486d83ce7db9a459b26c4896
--- NewsGate v1.0 gamma 2