It is a dialogue from which clearly comes out that Jesus Christ is
resurrected.
It has been read by thousands of people all over the world and has
provided to strengthen a lot of people in the Faith, to make the
doubtful people to think it over and to see that the atheists would be
surrendered.

Web site : http://digilander.libero.it/antoniobragadin/inquiry.htm
Email : ricercapap.bra@alice.it

Yep, Americanes Need 'Erbs ??? :)

Yet Another Nerd Experience
You Ain't No Expert
Yonder Assembler Not Easy

;--------------------
; nasm -f elf hw2uyane.asm
; ld -o hw2uyane hw2uyane.o

%%include "yanetut.inc"
putstring "Please tell me your name? "
getstring 79,name
putstring "Hello, "
putstring name
putstring "! Welcome to Linux uhhh... Assembly!", linefeed
putstring "BTW, the answer is "

mov ecx, 42
mov ebx, 1
add ebx, ecx
; HLLp, I can't read this part!!!

On Jun 29, 12:11 am, Frank Kotler verizon.net> wrote:

So far I see no problem to make the dear end users believe
in my logic for a pressed button (shown as inset) as 'active'.

This works fine for both,
single selection, like radio-buttons; list-selectors; color-box,
and multi-selectable (check-box styled) option-flag inputs.

But when it comes to show the status of bits (users wont care anyway)
could this confuse programmers if I'd use it in tools ??

ie: if an EFlags display show clear bits 'outset' and set bits 'inset'.

It wouldn't be much work to change my default setting on this,
but it will be in conflict with the 'other button logic' then.

Sure I could go back and use again Ucase/Lcase indication for bit
status display, or use other button borders. I defined 16 types
this means 8 active/inactive pairs yet.
I like to get a clue about the optimal order of my border-styles,
at the moment I got:

If i have to write a realloc function in C come out somthing like

void* realloc_m(void *p, int nbytes)
{int k;
uns a, r, j, i;
char *p1, *p2;

I was reading through chapter four last night and well got a little
complexed over a small program that should not be that big of a
deal.

program PtrConstDemo;

#include( "stdlib.hhf" );

static

b: byte := 0;
byte 1, 2, 3, 4, 5, 6, 7;

const

pb:= &b + 1;
begin PtrConstDemo;
mov( pb, ebx );
mov( [ebx], al );
stdout.put( "Value at address pb = $", al, nl );

end PtrConstDemo;

I'd like to do a call to a location in memory specified by a location
in memory... this can be done appearantly and would be very useful.
The NASM manual cites:

The CALL FAR mem forms execute a far call by loading the destination
address out of memory. The address loaded consists of 16 or 32 bits of
offset (depending on the operand size), and 16 bits of segment. The
operand size may be overridden using CALL WORD FAR mem or CALL DWORD
FAR mem.

This isn't totally clear for me... should I specify the call as?:

o32 call FAR dword[0x50A]

it does assemble like this, but how is the segment specified for the
address at which the subroutine-address is stored (no segment is
specified, so it must be specified implicitely - by cs - I think).

Further on... how exactly is the address stored there... as 6 bytes in
total? If so - in what order, segment bytes first or offset bytes
first?

Best regards,

Stéphane Thibaud

(Also posted to comp.lang.asm.x86 moderated group.)

Unlike eax, ebx, ecx and edx the other four general purpose registers
do not have an accessible 16-bit half. However, NASM assembles a move
from one of these other four to a segment register as it would a move
from any of the first four. Anyone else seen this and is it known to
work or fail on Intel/AMD chips?

Background follows.

The encoding of

mov , edi

looks as follows for all seg registers (or course, mov cs, ... is not
valid but I've included it to show the encoding). The opcode is 8E
(not shown) followed by one byte shown after the instruction (starting
with C7 in the first row). The byte value is shown in hex and in eight
bits of binary broken down by fields to make it easier to read.

What about qsort on address for make order [order array of 32bit unsigned
int]?
not understand it much... you think is it ok??

Thank you
-------------------
section data public use32 class=DATA

extern Qsort_32u, Malloc_sys
import Qsort_32u radll.dll
import Malloc_sys radll.dll
; 0x401000
m7 dd 2 , 7 , 1 , 4 , 6 , 3 , 5
v7 dd 7 , 6 , 5 , 4 , 3 , 2 , 1
valore2 dd 0

section code public use32 class=CODE

..start:
exestart:
push 7
push m7
call [Qsort_32u]
xor eax, eax
.f:
ret
-----------------------
; void SimpleQsort_32u(u32* lf, u32* rt)
; lf==left, right==right
; NB: TRASH...

Should any one be interested in a few older asm books in th Uk I saw this
seller selling some.

http://shop.ebay.co.uk/merchant/fertcat