PE> Thanks, I've made those mods.  I presume the code was PD.

r> My few modifications of your code? Certainly. 

Thanks, I just wanted to be sure you knew what I was doing
with your mods.

PE> That code that that guy on the internet posted was pretty
PE> tricky, eh?  I might do something about using that when I
PE> figure out how I'm going to incorporate assembler into C.
PE> I'll have to write my own version though, since he didn't
PE> put a PD notice on his.  BFN.  Paul.

Actually, I don't suppose it's possible to get him to confirm
PDness of his code?

r> Quick terminology:

r> dword   4 bytes  (you call this a "fullword"?)
r> word    2 bytes  (and this a "halfword"?)

It's not unreasonable terminology.  A "word" is a machine's
native size.  The 386 is a 32-bit processor, hence a word 
*should* be 32 bits.

On the IBM mainframes, which are also 32-bits, a word is of
course 32 bits.  A 16-bit size is a half-word, and a 64-bit
value is a double-word.  A fullword is another name for 
"word".  

On the PC the terminology is different thanks to the 16-bit
history.  It's bloody annoying.  Not nearly as annoying as
people going "void main" though.  BFN.  Paul.
@EOT:

---