CA> DG> a program to chat between the computers. So I read the win32 sdk
CA> DG> and thought, gee, pipes look good. So I did that for two hours
CA> DG> wondering why it wouldn't work. Found out it's cause pipes are only 
n
CA> DG> nt, not 95.
CA>I've been down that alley to :-(
Hit the brick wall at the end?
CA> DG>         1. Why does it get it twice?
CA>dont know!
I thought maybe it was some kind of wierdo error checking stuff.
CA> DG>         2. Will it _always_ get it twice?
CA>I think so.
Good.
CA>After reading your message i made a small program to see if
CA>it was true  - and it was. Maybe it is a bug in the windows
CA>SDK, or maybe there is a reason for it - not really obvious
CA>to me though.
Probably a bug, there's a couple in it. Or just an undocumented feature.
We all know how Microsoft loves them. :)
CA>I dont know which compiler you're using. I'm using MS
CA>Visual C++ 4.0. If you're using the same compiler, it could
CA>be a problem with the compiler.
Nope, using Watcom 10.6.
CA>The short of the long is, that I  found a way to get by it.
CA>Not in a very elegant way, but it works: The basic idea is
CA>to only take every 2 messages from the mailslot, when you
CA>are reading it, using the MODULUS (%) function.
CA>The next few lines of code shows the functions I'm using (do not get 
confuse
Few? It was a bit more. SLMR wasn't able to handle the size of the
message. I had to read it with all the pie's in it.
Thanks for the info. It was very helpful, though I'm going to wonder
_why_ they did it that way for a long time.
Danial.
___
 X SLMR 2.1a X 
--- Maximus/2 3.00
---------------