On Sat, 22 Nov 2014 00:29:51 +0000 (UTC), Dustin 
wrote:

>"p-0''0-h the cat (ES)"  wrote in
>news:kkjv6atjven1t13joodtt809e0l92626fa@4ax.com: 
>
>> On Fri, 21 Nov 2014 23:39:52 +0000 (UTC), Dustin
>>  wrote:
>> 
>>>"p-0''0-h the cat (ES)"  wrote
>>>in news:076v6a515t939fcvadqfd7h494b1u1pkpm@4ax.com: 
>>>
>>>> On Fri, 21 Nov 2014 18:16:21 +0000 (UTC), Dustin
>>>>  wrote:
>>>> 
>>>>>~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. 
>>>> 
>>>> Hey, ASIC kiddy, are you telling us that the great Dustin Cook
>>>> couldn't work around that one? LOL.
>>>
>>>*laugh* Sure I could. switch over to pure assembler/outright
>>>machine code. Pull the exec environment (including command line
>>>parameters) do alot of parsing, string manipulation outside of my
>>>main program, pass control to host using pure assembler, so that I
>>>can keeep all the work from the string parsing. 
>>>
>>>Risk something stomping on me, since i'm going outside of the asic
>>>environment, nothing knows what I've been doing, I run a very real
>>>risk of the next piece of asic code stomping all over me (which is
>>>going to happen regardless, ASIC has no idea i'm still running
>>>machine code over here.) 
>>>
>>>In other words, I chose stability and the limitation over risk of 
>>>unstable code and no command line limitation.
>>>
>>>Didn't really consider that question before posting it.. eh?
>>>So... how much experience do you actually have writing low level 
>>>software? I'mma thinking, not going out on a limb here, that it's
>>>ehh, not much.. yea?
>> 
>> Too difficult for you eh? Nice bit of bull####. Didn't fool me
>> though. 
>
>So that's your way of admitting you don't know WTF I was even writing 
>about eh? That'll work too, I suppose.

I can spot a loser looking for excuses a mile away. 

Sent from my iFurryUnderbelly.

-- 
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, shill, pooh-seur, scouringerer, and furball.

NewsGroups Numbrer One Terrorist

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