Results 1 to 10 of 133

Thread: Warning: Spyerase intentionally erases BugHunter from your machine

Hybrid View

  1. #1
    Dustin Cook Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    On Feb 18, 11:26 pm, "4Q" <paul_z...@hushmail.com> wrote:
    > Dustin Cook wrote:
    > > "4Q" <paul_z...@hushmail.com> wrote in
    > >news:1171850573.103492.57950@m58g2000cwm.googlegr oups.com:

    >
    > <snip>
    >
    >
    >
    > > > A man of your word, aye ;]]
    > > > No photo. Did you send Laura
    > > > your photo or can she assume your
    > > > words are worthless?

    >
    > > A photo is forthcoming 4Q, and yes, I give you permission to host it
    > > unmodified if you'd like.

    >
    > Stop gas-bagging about sending it and
    > send it. I've been looking forward to
    > a good laugh... I started to suspect
    > you hadn't found a picture off
    > uglymugs.com or trailerpark trash
    > and that was the delay.
    >
    > <snip>
    >
    >
    >
    > > 4Q, can't you find something more recent? eheh... Sheesh.

    >
    > I'm sure it will be posted to ACVSC
    > now that a flag has been raised ;]]
    >
    >
    >
    > > The last one is especially silly, man..

    >
    > > Date: 1997/07/23
    > > Message-ID: <33d6015...@nova.zianet.com>#1/1
    > > X-Deja-AN: 259547767
    > > Organization: Southwest Cyberport
    > > Newsgroups: alt.comp.virus.source.code

    >
    > > I forgot to include the critical error handler which rustybug needs
    > > Its an .obj file, linked in during compile.

    >
    > > It's assembler... Are you going to make fun of my sloppy almost 10 year
    > > old assembler routines too? *grin*

    >
    > Are you sure the original author
    > (Charon Software) of this code is going to mind you taking credit for
    > writing it,,, Mr Coderipper?
    >
    > Anyone wanting to look inside this
    > snippet can boot up something like
    > Knoppix and run uudecode... then use
    > a Hexedit to see if 'Charon Sofware'
    > minds our BugHuckster Raidy taking
    > credit for their work ;]]
    >
    > 4Q (The AV turncoat's official biographer)
    >
    > http://fourq.host.sk/chars/Dustin_Co...sk/chars/Raid/
    >
    > updated!



    Apparently charter's news servers aren't working either, I still don't
    see my reply from last night to this... It's no secret that the
    criterror routine was taken in part from Ibrary v2.0 written by Thomas
    Hanlin (this was years before Charon Software took over); I suspect
    Thomas and Charon are one in the same however. I am a registered user
    of the library and according to it's own documentation, I'm welcome to
    do with it as I wish. I'm a registered user of the now defunct asilib
    library for asic as well, You might find some routines from it present
    in bughunter as well as some routines from ibrary.
    And even more routines purely coded in asm for speed and time. since I
    used tasm for some of it, and microsoft's link.exe and borlands tlib
    utilitiy, you would claim I ripped there code too? <G> Moron.

    That's what, libraries are for. The ibrary criterror handler isn't
    the same as the one I posted however. If you try to call sub to
    theres, your program will never come back. Mine returns from the
    stack. I'll leave it upto you to figure out what code is different
    between them, assuming you can. heh.

    If your going to claim I'm a code ripper, be ready for some major
    disappointment, Any program that has used libraries or source code
    from "tutes" (this pretty much covers, every Vxer except me, haha) is
    a code ripper.... That's a very big brush 4Q. All of your comrades,
    mandragore, vecna, everyone is a bunch of code rippers... *yawn*


    Oh, and in case you missed it, bugHunter isn't a string scanner, it's
    a glorified checksummer, non programming ****wit.

    The only dirt your going to be thrashing about is 10+ year old code,
    way over, done, nobody cares.


    --
    Dustin Cook
    Author of BugHunter - MalWare Removal Tool v2.1
    http://bughunter.it-mate.co.uk


  2. #2
    Laura Fredericks Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On 19 Feb 2007 10:02:25 -0800, "Dustin Cook"
    <bughunter.dustin@gmail.com> wrote in post to 4Q:
    >I am a registered user of the library and according to it's own
    >documentation, I'm welcome to do with it as I wish.


    Didn't Dimbulb say this, too? LMFAO! (Whoops.)

    >If your going to claim I'm a code ripper, be ready for some major
    >disappointment, Any program that has used libraries or source code
    >from "tutes" (this pretty much covers, every Vxer except me, haha)
    >is a code ripper.... That's a very big brush 4Q. All of your
    >comrades,
    >mandragore, vecna, everyone is a bunch of code rippers... *yawn*


    I now expect to see the return of Dimbulb to acv, quoting the above
    as "proof" that if the great Raid, et al can do it, it must be okay.

    (Hey, 4Q! Care to place a bet on when Dimbulb returns?)

    -----BEGIN PGP SIGNATURE-----
    Version: PGP 8.1

    iQA/AwUBRdoSzKRseRzHUwOaEQJZLACgq4uGRJKrsCe+BL6Qm4S3O8 vHG1cAoM2U
    AsLass49VH+eUrMG6qKAuZhN
    =GhOx
    -----END PGP SIGNATURE-----

    --
    Laura Fredericks
    4Q's &quot;wicked evil ***** of satire, parody, humor and trollism&quot;

    PGP key ID - DH/DSS 2048/1024: 0xC753039A

    alt.comp.virus photo gallery:
    http://www.queenofcyberspace.com/acvgallery/

    usenet flamewars:
    http://www.queenofcyberspace.com/usenet/

    Remove CLOTHES to reply.

  3. #3
    4Q Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    Dustin Cook wrote:
    > On Feb 18, 11:26 pm, "4Q" <paul_z...@hushmail.com> wrote:
    > > Dustin Cook wrote:
    > > > "4Q" <paul_z...@hushmail.com> wrote in
    > > >news:1171850573.103492.57950@m58g2000cwm.googlegr oups.com:


    <snip>

    > > > It's assembler... Are you going to make fun of my sloppy almost 10 year
    > > > old assembler routines too? *grin*


    <hold that thought>

    > ...It's no secret that the
    > criterror routine was taken in part from Ibrary v2.0 written by Thomas
    > Hanlin


    *HAHA* One minute it's *your* assembler, next we find out that the
    code belongs to Thomas Hanlin and you mearly tlib'd his work then
    pretended you wrote it. You are a deceptive little AV turd.

    <snip>

    > The only dirt your going to be thrashing about is 10+ year old code,
    > way over, done, nobody cares.


    Now everyone knows you have been
    caught with your pants down, pretending
    you wrote Hanlin's library function.
    Accussing PCButts of ripping then
    calling Mandragore and Vecna code
    rippers (proof please). You ****tard
    turncoat.


    4Q

    http://fourq.host.sk/chars/Dustin_Cook/


  4. #4
    Dustin Cook Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    On Feb 19, 4:17 pm, "4Q" <paul_z...@hushmail.com> wrote:
    > Dustin Cook wrote:
    > > On Feb 18, 11:26 pm, "4Q" <paul_z...@hushmail.com> wrote:
    > > > Dustin Cook wrote:
    > > > > "4Q" <paul_z...@hushmail.com> wrote in
    > > > >news:1171850573.103492.57950@m58g2000cwm.googlegr oups.com:

    >
    > <snip>
    >
    > > > > It's assembler... Are you going to make fun of my sloppy almost 10 year
    > > > > old assembler routines too? *grin*

    >
    > <hold that thought>
    >
    > > ...It's no secret that the
    > > criterror routine was taken in part from Ibrary v2.0 written by Thomas
    > > Hanlin

    >
    > *HAHA* One minute it's *your* assembler, next we find out that the
    > code belongs to Thomas Hanlin and you mearly tlib'd his work then
    > pretended you wrote it. You are a deceptive little AV turd.


    Actually, no. some of the code belongs to thomas, some is mine. This
    is all actually common knowledge, I'm surprised you didn't know. I
    made no effort to hide where the code came from when I was using it
    years ago, writing.. lame self replicating programs that nobody wanted
    then, and nobody wants now.

    Since you didn't bother to show the differences between the original
    and mine, it's a safe bet you really don't have even that little
    amount of coding skill. When you mentioned someone should use a
    debugger, you didn't actually mean you did ya?

    unlike yourself tho, I don't live in the fantasy world that Vx is the
    begin/ending of all, I grew up.... One day, you will too.

    > <snip>
    >
    > > The only dirt your going to be thrashing about is 10+ year old code,
    > > way over, done, nobody cares.

    >
    > Now everyone knows you have been
    > caught with your pants down, pretending
    > you wrote Hanlin's library function.
    > Accussing PCButts of ripping then
    > calling Mandragore and Vecna code
    > rippers (proof please). You ****tard
    > turncoat.


    Caught with my pants down? 4Q, your making a big deal about 10 year
    old code.. 10 years ago man.. hehehe.
    I didn't pretend to write anything, hanlins function isn't the same
    thing that I posted years ago. Their are differences between them.
    more than tlibbing I'm afraid.

    I didn't call vecna or mandragore anything, I used it as a reference
    point. Vecna and mandragore both at some point read others code,
    studied it, modified it, and learned from it. As most programmers do.
    We didn't actually call this code ripping then. And nobody really
    thinks of it as code ripping now, except for.. you apparently. with
    regard to myself, and none of the others.

    You've also been making some assinine claims which painfully tell me
    what little programming skill you actually possess on your own. No
    wonder I never saw anything from you when I was active vx, you
    couldn't code anything then, and you haven't bothered to learn
    anything now?

    1. BugHunter doesn't use string scanning.
    2. I am not antivirus, BugHunter does not search for viruses.
    3. The best you can come at me with is 10 year old code that I didn't
    author entirely by myself. Wow!
    4. Even after telling you the files are different, you couldn't find
    out how. You assumed wrongly, again, that I just tlibbed it. You
    really should take an assembler dump of the file, since the hex editor
    isn't helping you.
    5. You will not find any reference using a hex editor to any Charon
    Software in that object file. What you will find is ibrary code
    comments start and end, which I did preserve. the code however in the
    middle that actually does the work, is not the same as his. His
    routine was originally designed only for the ibrary internal
    functions. It's not even a routine available thru the library that you
    could call. I took that apart, and made a stand alone int24h handler
    out of it, which is what the obj file I posted is. Tom Hanlins is
    integrated into the library, can only be accessed by it's own routines
    and does nothing to help you with crit error handling. Mine does. Yes,
    it's based originally on his code, but it's no longer his design. We
    call this an improvement over the original idea. Read up on patents
    sometime. Same idea.

    If you can still call toms and mine the same thing even after the fact
    one doesn't work outside the librarys own routines and the other
    doesn't work with them, but works independently, then you can call me
    a code ripper, if you like.


    Now, if you really want to play code ripper games, everybody else
    besides the first person who wrote "Hello World" is a code ripper.
    Everybody who uses someone elses library functions, sophos, avg, you
    guys here me? , to 4Q we're all code rippers!



    And before you try tearing me to pieces in usenet, you best brush up
    on programming. String scanners and checksum based scanning are/is two
    entirely different technologies. Offly sad that you couldn't tell the
    difference.

    Oh, btw 4Q, yes, I stalled getting your shell accounts to you, They've
    been online for 2 weeks now. *grin*. I did lose the bet tho, I
    expected you would blow up and switch sides 3 weeks ago. hehehe. You
    are, indeed, predictable. You can understand of course why HHI
    wouldn't want to help you now, right? You can't be trusted with
    anything.




  5. #5
    4Q Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    Dustin Cook wrote:
    > On Feb 19, 4:17 pm, "4Q" <paul_z...@hushmail.com> wrote:
    > > Dustin Cook wrote:
    > > > On Feb 18, 11:26 pm, "4Q" <paul_z...@hushmail.com> wrote:
    > > > > Dustin Cook wrote:
    > > > > > "4Q" <paul_z...@hushmail.com> wrote in
    > > > > >news:1171850573.103492.57950@m58g2000cwm.googlegr oups.com:

    > >
    > > <snip>
    > >
    > > > > > It's assembler... Are you going to make fun of my sloppy almost 10 year
    > > > > > old assembler routines too? *grin*

    > >
    > > <hold that thought>
    > >
    > > > ...It's no secret that the
    > > > criterror routine was taken in part from Ibrary v2.0 written by Thomas
    > > > Hanlin

    > >
    > > *HAHA* One minute it's *your* assembler, next we find out that the
    > > code belongs to Thomas Hanlin and you mearly tlib'd his work then
    > > pretended you wrote it. You are a deceptive little AV turd.

    >
    > Actually, no. some of the code belongs to thomas, some is mine. This
    > is all actually common knowledge, I'm surprised you didn't know.


    And yet anyone reading what you wrote
    would be led to believe you wrote it.
    You obviously didn't expect someone to
    take a quick look at the ASIC l'ibrary.

    >I made no effort to hide where the code came from when I was using it
    > years ago, writing.. lame self replicating programs that nobody wanted
    > then, and nobody wants now.


    You don't want now! It's hard to escape
    your past and for everyone to see that
    you really aren't much of a coder
    beyond simple DOS codes.


    > Since you didn't bother to show the differences between the original
    > and mine, it's a safe bet you really don't have even that little
    > amount of coding skill. When you mentioned someone should use a
    > debugger, you didn't actually mean you did ya?


    Well since I only downloaded IBRARY yesterday and Linux doesn't come
    with a 16bit DOS debugger it's hardly
    surprising I haven't debugged it yet.
    But now that I feel the challenge has
    been laid down, you can expect to see
    Bughunter source code published.


    > unlike yourself tho, I don't live in the fantasy world that Vx is the
    > begin/ending of all, I grew up.... One day, you will too.


    Well let's see what falls out in
    your webpage biography. )

    >
    > > <snip>
    > >
    > > > The only dirt your going to be thrashing about is 10+ year old code,
    > > > way over, done, nobody cares.

    > >
    > > Now everyone knows you have been
    > > caught with your pants down, pretending
    > > you wrote Hanlin's library function.
    > > Accussing PCButts of ripping then
    > > calling Mandragore and Vecna code
    > > rippers (proof please). You ****tard
    > > turncoat.

    >
    > Caught with my pants down? 4Q, your making a big deal about 10 year
    > old code.. 10 years ago man.. hehehe.


    You are taking this 10yr old piece of
    **** coding to heart. I do hope Bughuckster you've improved over a
    10yr
    period... alas I think we will be sadly
    disappointed and see the same old ****
    (which is your level of coding unfortunately).

    > I didn't pretend to write anything, hanlins function isn't the same
    > thing that I posted years ago. Their are differences between them.
    > more than tlibbing I'm afraid.


    You sound rattled. You made some
    remark giving everyone the idea this
    was all your own work and after a few
    hours someone digs up IBRARY off the
    net and sees the code you was claiming
    to be yours full of IBRARY references.


    >
    > I didn't call vecna or mandragore anything, I used it as a reference
    > point. Vecna and mandragore both at some point read others code,
    > studied it, modified it, and learned from it. As most programmers do.
    > We didn't actually call this code ripping then. And nobody really
    > thinks of it as code ripping now, except for.. you apparently. with
    > regard to myself, and none of the others.


    I smell bull**** backpeddling.


    >
    > You've also been making some assinine claims which painfully tell me
    > what little programming skill you actually possess on your own. No
    > wonder I never saw anything from you when I was active vx, you
    > couldn't code anything then, and you haven't bothered to learn
    > anything now?


    Really, you still haven't found
    anything? And yet my work still
    manages to make it into virus
    databases. I take it you never
    grepped any of my A.I. work
    hosted on Coderz.net either
    Ask Guillermito (I know he likes to swap good codes for your lame code
    effort)
    if he'll spare you a copy, I know he
    likes to swap good codes for your
    lamer code efforts). Then weep 16bit
    BASIC boy. ;]]


    > 1. BugHunter doesn't use string scanning.


    *Who ****ing really cares?!* I only
    don't loaded your **** yesterday,
    I've not even opened it with a hex
    editor let alone a debugger.

    > 2. I am not antivirus, BugHunter does not search for viruses.


    Check your database you lying ****.
    And when were worms excluded from
    from the AV prodcts? Arsehole.


    > 3. The best you can come at me with is 10 year old code that I didn't
    > author entirely by myself. Wow!


    You won't release the source code to
    BugHunter because everyone knows it
    will just be more **** by someone who
    can't raise his game above BASIC with
    a couple of Int86 calls.... how many
    years ago should you have stopped using
    this crap, 10-15? really lame and sad.


    > 4. Even after telling you the files are different, you couldn't find
    > out how. You assumed wrongly, again, that I just tlibbed it. You
    > really should take an assembler dump of the file, since the hex editor
    > isn't helping you.


    Sourcer on standby ;]]

    > 5. You will not find any reference using a hex editor to any Charon
    > Software in that object file. What you will find is ibrary code
    > comments start and end, which I did preserve.


    Yeah, and they come back to haunt you.
    You should have removed any trace of
    IBRARY if you wanted to claim it was
    all your own work at the outset (before
    someone bubbled you -- that would be me)


    >the code however in the
    > middle that actually does the work, is not the same as his. His
    > routine was originally designed only for the ibrary internal
    > functions. It's not even a routine available thru the library that you
    > could call. I took that apart, and made a stand alone int24h handler
    > out of it, which is what the obj file I posted is. Tom Hanlins is
    > integrated into the library, can only be accessed by it's own routines
    > and does nothing to help you with crit error handling. Mine does. Yes,
    > it's based originally on his code, but it's no longer his design. We
    > call this an improvement over the original idea. Read up on patents
    > sometime. Same idea.


    **** in hell what a rant! And
    considering you almost had me convinced
    earlier that this 10yrs old stuff was
    of no significance to you. *ROFL*

    >
    > If you can still call toms and mine the same thing even after the fact
    > one doesn't work outside the librarys own routines and the other
    > doesn't work with them, but works independently, then you can call me
    > a code ripper, if you like.


    Plageiarise someone elses library
    then pretend it's all your own work
    then I think the name fits you well,
    you back peddling tard.

    >
    >
    > Now, if you really want to play code ripper games, everybody else
    > besides the first person who wrote "Hello World" is a code ripper.
    > Everybody who uses someone elses library functions, sophos, avg, you
    > guys here me? , to 4Q we're all code rippers!


    *HAHAH* Stupid smoke screen to hide
    your embarrassment.

    >
    >
    >
    > And before you try tearing me to pieces in usenet, you best brush up
    > on programming. String scanners and checksum based scanning are/is two
    > entirely different technologies. Offly sad that you couldn't tell the
    > difference.


    I never gave a flying **** about your
    16bit BugHuckster till yesterday. Now
    I'm up for the challenge.


    >
    > Oh, btw 4Q, yes, I stalled getting your shell accounts to you, They've
    > been online for 2 weeks now. *grin*.


    You are either a liar or playing out
    some kind of sociopathic loser trait.
    I think we will have to get this into
    you biography webpage... maybe I can
    get some clues from Rhonda what it
    feels like to be ****ed around by a
    you a personality disordered mental.

    Btw you weren't the only person I
    asked about shell accounts. I even
    asked MGL if I could run my infobot
    on his server years ago... I even
    sent him the code (ask him if he
    will give you a copy -- real code,
    not 16bit BASIC ****). Incidently I
    can run the infobot via this HOST.SK
    shell... Wasn't it nice of MGL to
    set me up with the fourq site )

    > I did lose the bet tho, I
    > expected you would blow up and switch sides 3 weeks ago. hehehe.


    Listen to yourself loser... Are you
    sniggering in your mum basement
    typing that out?

    >You are, indeed, predictable. You can understand of course why HHI
    > wouldn't want to help you now, right?


    You are playing a little game in your
    head that only you seem to be able to
    understand.


    > You can't be trusted with anything.


    You are mouthing this out infront of
    a mirror aren't you.

    It's been fascinating observing you
    over the years. I hope people will
    appreciate my litle contribution to
    show you off as an twisted exhibit.
    Don't forget I still have the IRC
    logs where you talk about having a
    fantasy shoot out with the FBI,
    telling me they wouldn't take you
    alive. How ****ing childish can a
    lame 16bit BASIC coder be.


    4Q


  6. #6
    Dustin Cook Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    On Feb 19, 6:29 pm, "4Q" <paul_z...@hushmail.com> wrote:

    A dissassembly of the criterr.obj file I posted 10 years ago... I told
    you it was nothing but an int24h handler...


    ; OBJASM version 2.0 released on Jan 3, 1991
    ; (C) Copyright 1988,1989,1990,1991 by Robert F. Day. All rights
    reserved

    TITLE criterr.asm
    .386p ; Enable USE32/USE16 usage
    .387 ; Enable floating point also
    IBRARY_CODE SEGMENT PARA PUBLIC USE16
    IBRARY_CODE ENDS
    ; [005C] ; Linker - Pass two marker


    PUBLIC IBCRITINIT ; Located at 1:0005h Type = 1
    PUBLIC IBCRITERROR ; Located at 1:002Ch Type = 1
    PUBLIC IBCRITDONE ; Located at 1:0043h Type = 1

    IBRARY_CODE SEGMENT
    assume cs: IBRARY_CODE


    $S4 db 000h
    $S1 dw 00000h
    $S2 dw 00000h
    IBCRITINIT:
    push ax
    push ds
    xor ax,ax
    mov ds,ax
    mov ax,ds:[0090h]
    mov cs:$S1,ax
    mov ax,ds:[0092h]
    mov cs:$S2,ax
    mov word ptr ds:[0090h],offset IBRARY_CODE:$S3
    mov word ptr ds:[0092h],cs
    mov byte ptr cs:$S4,00h
    pop ds
    pop ax
    retf
    IBCRITERROR:
    pushf
    cmp byte ptr cs:$S4,00h
    jnz $L5
    popf
    retf
    $L5: or ax,ax
    mov al,cs:$S4
    add ax,+012h
    popf
    stc
    retf
    IBCRITDONE:
    push ax
    push ds
    xor ax,ax
    mov ds,ax
    mov ax,cs:$S1
    mov ds:[0090h],ax
    mov ax,cs:$S2
    mov ds:[0092h],ax
    pop ds
    pop ax
    retf
    $S3: push ax
    mov ax,di
    inc ax
    mov cs:$S4,al
    pop ax
    xor al,al
    iret

    IBRARY_CODE ENDS
    END

    This is the dissassembly of the one I posted, remember, it's different
    than his. And both of them, as everyone can now see, are what I told
    you they were, an int24h handler.. that's it.
    His is ripped from the asic.doc and a dos interrupt list... lemme see,
    Mine is too.

    Can you tell us the difference between the two mr coder expert
    wannabe? Remember, his is internal ONLY to his own routines (the
    handler sets up for the libraries own code, not your applications),
    Mine is called seperatly, does not support his libraries internal
    functions, but does provide an int24h handler for asic v4/5x programs.
    It has limitations, but it does the job well. Mine is based off of
    his, because I didn't see much point in copying the header information
    (see asic.doc) or doing the same damn thing he's already doing, that
    people from the 80s have already been doing. It's an int24h handler,
    nothing more, nothing less. Not something you could actually copyright
    or really claim as 100% your own, whether your me or Thomas.

    Hint: My question above has an answer. <g>



    If you want to know what the beginning 'junk' assembler does, read the
    asic.doc file.



  7. #7
    pcbutts1 Guest

    Re: Warning: Dustin Cook is a thief!

    He steals others codes and claims it as his own.

    --

    Newsgroup Trolls. Read about mine here http://www.pcbutts1.com/downloads
    The list grows. Leythos the stalker http://www.leythosthestalker.com, David
    H. Lipman, Max M Wachtell III aka What's in a Name?, Fitz,
    Rhonda Lea Kirk, Meat Plow, F Kwatu F, George Orwell



    "Dustin Cook" <bughunter.dustin@gmail.com> wrote in message
    news:1171922604.959362.153050@h3g2000cwc.googlegro ups.com...
    > On Feb 19, 4:17 pm, "4Q" <paul_z...@hushmail.com> wrote:
    >> Dustin Cook wrote:
    >> > On Feb 18, 11:26 pm, "4Q" <paul_z...@hushmail.com> wrote:
    >> > > Dustin Cook wrote:
    >> > > > "4Q" <paul_z...@hushmail.com> wrote in
    >> > > >news:1171850573.103492.57950@m58g2000cwm.googlegr oups.com:

    >>
    >> <snip>
    >>
    >> > > > It's assembler... Are you going to make fun of my sloppy almost 10
    >> > > > year
    >> > > > old assembler routines too? *grin*

    >>
    >> <hold that thought>
    >>
    >> > ...It's no secret that the
    >> > criterror routine was taken in part from Ibrary v2.0 written by Thomas
    >> > Hanlin

    >>
    >> *HAHA* One minute it's *your* assembler, next we find out that the
    >> code belongs to Thomas Hanlin and you mearly tlib'd his work then
    >> pretended you wrote it. You are a deceptive little AV turd.

    >
    > Actually, no. some of the code belongs to thomas, some is mine. This
    > is all actually common knowledge, I'm surprised you didn't know. I
    > made no effort to hide where the code came from when I was using it
    > years ago, writing.. lame self replicating programs that nobody wanted
    > then, and nobody wants now.
    >
    > Since you didn't bother to show the differences between the original
    > and mine, it's a safe bet you really don't have even that little
    > amount of coding skill. When you mentioned someone should use a
    > debugger, you didn't actually mean you did ya?
    >
    > unlike yourself tho, I don't live in the fantasy world that Vx is the
    > begin/ending of all, I grew up.... One day, you will too.
    >
    >> <snip>
    >>
    >> > The only dirt your going to be thrashing about is 10+ year old code,
    >> > way over, done, nobody cares.

    >>
    >> Now everyone knows you have been
    >> caught with your pants down, pretending
    >> you wrote Hanlin's library function.
    >> Accussing PCButts of ripping then
    >> calling Mandragore and Vecna code
    >> rippers (proof please). You ****tard
    >> turncoat.

    >
    > Caught with my pants down? 4Q, your making a big deal about 10 year
    > old code.. 10 years ago man.. hehehe.
    > I didn't pretend to write anything, hanlins function isn't the same
    > thing that I posted years ago. Their are differences between them.
    > more than tlibbing I'm afraid.
    >
    > I didn't call vecna or mandragore anything, I used it as a reference
    > point. Vecna and mandragore both at some point read others code,
    > studied it, modified it, and learned from it. As most programmers do.
    > We didn't actually call this code ripping then. And nobody really
    > thinks of it as code ripping now, except for.. you apparently. with
    > regard to myself, and none of the others.
    >
    > You've also been making some assinine claims which painfully tell me
    > what little programming skill you actually possess on your own. No
    > wonder I never saw anything from you when I was active vx, you
    > couldn't code anything then, and you haven't bothered to learn
    > anything now?
    >
    > 1. BugHunter doesn't use string scanning.
    > 2. I am not antivirus, BugHunter does not search for viruses.
    > 3. The best you can come at me with is 10 year old code that I didn't
    > author entirely by myself. Wow!
    > 4. Even after telling you the files are different, you couldn't find
    > out how. You assumed wrongly, again, that I just tlibbed it. You
    > really should take an assembler dump of the file, since the hex editor
    > isn't helping you.
    > 5. You will not find any reference using a hex editor to any Charon
    > Software in that object file. What you will find is ibrary code
    > comments start and end, which I did preserve. the code however in the
    > middle that actually does the work, is not the same as his. His
    > routine was originally designed only for the ibrary internal
    > functions. It's not even a routine available thru the library that you
    > could call. I took that apart, and made a stand alone int24h handler
    > out of it, which is what the obj file I posted is. Tom Hanlins is
    > integrated into the library, can only be accessed by it's own routines
    > and does nothing to help you with crit error handling. Mine does. Yes,
    > it's based originally on his code, but it's no longer his design. We
    > call this an improvement over the original idea. Read up on patents
    > sometime. Same idea.
    >
    > If you can still call toms and mine the same thing even after the fact
    > one doesn't work outside the librarys own routines and the other
    > doesn't work with them, but works independently, then you can call me
    > a code ripper, if you like.
    >
    >
    > Now, if you really want to play code ripper games, everybody else
    > besides the first person who wrote "Hello World" is a code ripper.
    > Everybody who uses someone elses library functions, sophos, avg, you
    > guys here me? , to 4Q we're all code rippers!
    >
    >
    >
    > And before you try tearing me to pieces in usenet, you best brush up
    > on programming. String scanners and checksum based scanning are/is two
    > entirely different technologies. Offly sad that you couldn't tell the
    > difference.
    >
    > Oh, btw 4Q, yes, I stalled getting your shell accounts to you, They've
    > been online for 2 weeks now. *grin*. I did lose the bet tho, I
    > expected you would blow up and switch sides 3 weeks ago. hehehe. You
    > are, indeed, predictable. You can understand of course why HHI
    > wouldn't want to help you now, right? You can't be trusted with
    > anything.
    >
    >
    >




  8. #8
    Rhonda Lea Kirk Guest

    Re: Warning: Spyerase intentionally erases BugHunter from your machine

    Dustin Cook wrote:

    > Oh, btw 4Q, yes, I stalled getting your shell accounts to you, They've
    > been online for 2 weeks now. *grin*. I did lose the bet tho, I
    > expected you would blow up and switch sides 3 weeks ago. hehehe. You
    > are, indeed, predictable. You can understand of course why HHI
    > wouldn't want to help you now, right? You can't be trusted with
    > anything.


    <projection>

    I knew you were in the habit of substituting narcissistic manipulation
    for intelligence, but I never really believed that you are as
    pathetically stupid as you have just made yourself out to be.

    --
    Rhonda Lea Kirk

    Happiness limits the amount of suffering one is
    willing to inflict on others. Phèdre nó Delaunay



Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •