FM> Of course! But it's the buffer move problem your solving here, not the
FM> move until \n problem. 

Yeah, that's right, separate threads.

PE> memcpy is designed to copy from a buffer to another buffer, for
PE> a length of whatever.  No overrun allowed.  Destination to be
PE> returned to caller.  Parameter order is dest, source, length...

FM> You should also mention that it returns *dest (if I've read that 'C'
FM> code properly).

It returns dest, not *dest.

PE> _DATA   segment dword public use32 "DATA"
PE> _DATA   ends
PE> _BSS    segment dword public use32 "BSS"
PE> _BSS    ends

FM> AAMOI why do specify these segments here?

Basically because I don't really understand segments, but what I
do have is some skeleton code that I use for my assembler 
programs.  BFN.  Paul.
@EOT:

---