BV> :) I've got a Z-Modem DLL and a few other things now so I'm
BV> almost ready to write a proper Windoze Point system. All I need
BV> now is the time :(
BL> I've just finished rep2pkt, so all that's left is the bit in the
BL> middle - Zmodem. There a nice freeware one (fwz). What I mean to do
BL> next, is fiddle with someone else's Zmodem (maybe Paul's if he ever
BL> finishes it), and instead of using Telix and salt files, I'll do the
BL> comms in VB. I haven't done anything about the editor yet.

Oh! Did I mention that I also have a full-blown text editor ?

BL>  This is just for my own edification. I have no faith in Shareware
BL> as a money earner,

ROFL..I'm with you. It's pseudo public domain if you ask me.

BL> and I'm using VB/DOS because it fits better as a replacement for
BL> TinyPoint as it stands. I agree that a Windows TPoint would be nice,
BL> and it would not be hard to convert to VB/WIN (there is an automatic
BL> converter). If I do it manually, I'll end up rewriting the whole
BL> thing - it's the way I am!

It's a problem. I'd probably do the same. Use your original as a
basis but basically rewrite it.

BL>  The only bit missing is the MKS$ converter for the ndx files. VB/DOS
BL> has the function on tap. I've written some code for that, but it needs
BL> to be done in ASM because it's a bit slow and it gets used a lot. I
BL> might make that my first foray into the weird and wonderful world of
BL> TASM.

You could always tell Frank it is a new Keno algorithm :)

BL> I've been sending commands to the modem and ringing myself up, and
BL> it seems to work rather easily. This comms crap is a packet of piss 
BL> but it seems to spend most of its time waiting for something to happen.
BL> I fill up the output buffer and send it, and then I keep looking in
BL> the input until somethoing appears, and I read it. Is there another
BL> way to wait without being in a loop?

Yes. In Windows they are called call-backs.
In DOS it is called hooking an Interrupt. It's a little involved and
I don't really have the time to explain it properly so I won't even
try. Sorry. Perhaps someone else may have more time. Try Rod.

Regards, Brenton
@EOT:

---