To: Paul Edwards

 BL> I put a proper message in \spool but it didn't get sent. Where
 BL> do you put it so that UUCICO recognises it? 

 PE> fxuucico you mean.
 
  I meant what I wrote. fxuucico second-sources uucico, so it would be
the same. I know you have uuxico, so that was why I used the name. You
are so busy being a fucked-in-the-head smartarse who knows everything,
you never answer questions.

 PE>  That is up to fxuucico, I have no idea.

  I know you have no idea, but I harboured a vague hope that you might
look it up in the UUCICO documentation for me.

 PE> Surely they documented something like that? 

  No they didn't, which explains why I'm wasting my time asking you
questions you never answer. So... I tried the three possibilities,
wasted 75 cents calling you, and discovered that you have to put the
uploads in the spool\scorpio directory.

 PE> And you'd need two/three files as well, not just one, right?

  Yes. The message is in the 0001.DAT file (with header), the 0001.XQT
file contains data on the DAT file for *your* end of things (totally
unnecessary, btw), and the 0001.CMD file tells uucico (or fxuucico)
what to do with them at my end.

  What I'll try next, is a single .CMD file for two DATs and XQTs.

  Is your uucico in Taylor UUPC set up to negotiate packet size?
fxuucico in g format can use packets up to 4096 bytes (the default is
64 bytes). I've been gettting 1300 cps transfers, so tonight I'll try
a 2048 packet maximum and see if your end goes up from 64. fxuucico is
a lovely little program! And gzip's not bad either.

... Later

  Well! I used 2048 as the packet size with 7 windows and got 1644
cps!

Regards,
Bob




 
___ Blue Wave/QWK v2.12
@EOT:

---