Dustin Cook wrote:
> On Feb 25, 12:11 am, "Kadaitcha Man" <nntp.n...@gmail.com> wrote:
> > > </quote> childish code. No wonder they
> > > call it BASIC (read: code for children)
>
> Actually, it's not quiet basic.. See below, as I tear K-man to
> shreds

Well I hope you do a better job of it
than the last time you tore him to bits
(in your mind) *grin* Back in 2005 when
you first ran into KM and AUK I actually
felt sorry for you. I was under the
impression you was being bullied, but
I guess was wrong. You invite trouble
and conflict. I like a bit of malicious
mischief now and a again and I guess
this time I'm going to sit back and enjoy
this... <LOG ON> Set Webpage = 4Q


<snip>

>
> > woefully inefficient code requires values to be moved left, right and
> > centre, then all the way back again before a result is obtained. I use the
>
> Ouch, I don't think you realize how close asic really is to
> assembler... Your loss.
>

*Shrug* You are using it as BASIC
not assembler. One or two Int86 calls
does not make you an assembly language
coder. This is why people like Mandragore
,T2000, MrSandman laugh at you whenever
you open your mouth.

<snip>

>
> You don't actually do much with assembler do you?

*laugh* You clueless ****tard, it's
you that doesn't have a clue about
assembler.


>Well anyways, when
> asic compiles the binary, the resulting assembler code assigns
> 80characters of memory for each string variable I use. Regardless of
> whether or not I use all of the space, the location of the variable is
> known the whole time my code is running. Nothing need be, moved.

You wouldn't be using ASIC's 80characters
if you had a clue about assembler.
You'd be using the _DATA segment in
one of them FAR calls (you clueless
****ing twat).


> Overwritten as you wish, but moved, not unless you want too. If you
> don't like this design, you may wish to take it up with Asics author,
> I'm unable to evade this limitation myself.

You've had 15 ****ing years to solve
this limitation. Now I know you don't
have any .ASM files, you utter code fake.

Hello, McFLY... HELLO!


_DATA segment word public 'DATA'
s@ label byte

db 'Dustin Cook You Stupid Turd'
db 0
_DATA ends



<snip> cut and pasting the ASIC manual
(someone elses work) will not work
as smoke and mirrors you ****ing turd
in a blender.

> converted from
> strings when read. String variables and constants are written
> out as ASCII
> strings terminated by a null character (however, the null can be
> suppressed). Thus, string variables when written to disk, take
> the same
> space byte for byte as string constants.
>
> The reason behind fixed length string variables was avoidance of
> string
> "garbage collection". In addition to slight performance
> advantages, there
> is the added benefit of providing a string memory address which
> never
>
>
> Page - 141
>
>
>
> changes. Thus once VARPTR retrieves the address of a variable,
> you never
> have to worry about it changing.
> EXE File Memory Map
>
> The following describes the structure of the ".EXE" file created
> by ASIC.
> In the COM file format the code, data, and stack are all in the
> same memory
> segment. In an ASIC EXE format file, the code, data, and stack
> each reside
> in their own segment. Addresses are given as offsets from the CS
> (Code
> Segment), DS (Data Segment), or SS (Stack Segment) registers.
>
>
> Description Address Range
> ------------------------------ -------------
> Program Segment Prefix (PSP) CS: minus 00FF
> (Created/Required by DOS, and
> immediately precedes the
> code segment)
> |
> |
> v
> Code Segment (CS
> User Program 0000 +
> |
> |
> v
> System Subroutines Address Varies
> |
> |
> v
> Data Segment (DS
> Program Data Area #1 0000 - 0102
> String Conversion Buffer 0103 - 0109
> Input Buffer 010A - 015B
> Screen Width 015C
> Color/Attribute Byte 015D
> Screen Graphics Mode 015E
> Cursor Position 015F - 0160
> File Control Table 0161 - 0169
> ERROR System Variable 016A - 016B
> System Subroutine Vectors 016C - 017F
> EXTENDED System Variable 0180 - 0181
> RND Seed 0182 - 0185
> Math Work Area 0186 - 018D
> DEFSEG System Variable 018E - 018F
> Start DATA Block Pointer 0190 - 0191
> Current DATA Block Pointer 0192 - 0193
> Reserved for future use 0194 - 0195
> Optional System Sub Vectors 0196+
> and Work Areas (decimal math option)
> Program Data Area #2 Address Varies
> |
> |
> v
> Stack (SS (builds downward) 0000 - 07D0 (0FA0--debug
> mode)
>
>
> Page - 144
>
>
>
> NOTE: The format of an EXE file created using the
> "B/OBJ" option is essentially the same as the one
> produced by the "B/EXE" option, except that the "B/OBJ"
> output file may contain additional code or data
> segments linked in from other OBJ or LIB files
>
> Read it
> 0wned k-man. Full documentation for asic as well as the compiler can
> be found on my site, if your inclined enough to educate yourself.
> follow this link:
> http://bughunter.it-mate.co.uk/asic500.zip

Or he could just get it from a reputable
source where he'd be guaranteed not to
have something nasty installed like a
backdoor BugHunter Trojan.

*Simtel* <-- He could get IBRARY.LIB
as well, you know the one you code ripped

> and if you dont want to touch the problem, but want to see the docs
> alone, go here:
> http://bughunter.it-mate.co.uk/asic.txt
>
> There ya go, enjoy!
>

FOAD! I thought you was dying from AIDS?
How long have you got left? You look
like you are in the advanced stages of
the disease, but just gives us an eta
so we have got a rough idea when you plan
to launch the BugHunter surprise.


4Q