TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Paul Edwards
from: Frank Malcolm
date: 1995-02-08 06:38:10
subject: bink delays

Hi, Paul.

PE>  PE>> Rod Speed, Brenton Vettoretti and Frank Malcolm, you are sending
PE>  PE>> me a 00000000.PKT, when you could instead be sending me a
PE>  PE>> 00000000.MO0 which is compressed.  In the name of not being
PE>  PE>> inconsiderate arsewipes, why don't you add a

PE>  FM> Now back when I first became a point, *you* suggested that this was
PE> not
PE>  FM> going to be a problem because the up message packets are so small.
PE>  FM> Cripes, the whole upload only takes a few seconds.

PE> I don't remember saying that.  I certainly doubt that I said it
PE> voice, so it had to be a message here.  Care to give me a clue
PE> as to what was in the message?

Not particularly, I'd rather just change it to what you want.

PE> Perhaps I overemphasised the "inconsiderate arsewipes"?  :-)
PE> I was just thinking that now that things are starting to settle
PE> down, we should start trying to rev it up a few notches.

Fine.

PE>  PE>> "zip -9k 00000000.MO0 00000000.PKT" to your
batch files?  You
PE>  PE>> can change the 9k to 9km if you want to automatically delete
PE>  PE>> the PKT file after compression is successful.

PE>  FM> And what's this "zip", and "-9k" stuff?
I use PKZIP which doesn't know
PE>  FM> about those options. If -9k means max compression, I should be using
PE> -ex
PE>  FM> - is that what you meant?

PE> Why don't you use "zip"?  It's freeware instead of shareware, it's
PE> available on practically every environment you care to name, it
PE> comes with complete source code.  The "-9" is maximal compression,
PE> the "-k" is make it PKZIP compatible (which I think just means
PE> uppercase all file names), as it's normally pkzip compatible
PE> anyway as far as I can tell.

OK. What version of PKZIP is it compatible with? I use 1.93 alpha for
zipping because at one time some BBSs hadn't upgraded past there, and
2.04g for unzipping to cater for those who send me stuff. The earlier
2.nn versions had *bad* bugs.

Is it on your board? Called what? I'm not going to search FILES for it,
'cos when I look for ZIP I get nearly every line .

PE>  PE>> Now that things are back to normal, I have taken the liberty
PE>  PE>> of removing that 3 second delay again.  I have also taken a
PE>  PE>> look at the tinypoint script, and it appears that it has a
PE>  PE>> 1-second delay in it before sending out the yoohoo.  Why don't
PE>  PE>> you try seeing what happens if you drop the 1 second delay?

PE>  FM> Done, we'll see how it goes. There's another delay after the ACK, and
PE>  FM> another after everything's done - remove them too?

PE> Yeah, can't hurt.  I checked your call this morning, and
PE> unfortunately it is taking a long time for you to send the
PE> YOOHOO in the first place.  After my modem returns a CONNECT,
PE> it takes 5 seconds before I receive your Yoohoo.  Compared
PE> with Brenton, who is taking about 2 seconds.  Bob is taking
PE> 6 seconds, and I thought he had the same modem as Brenton.

I have noticed the delay at this point, too and I dunno why - AFAIK my
telix script is now exactly as I got it from Brenton (restored after
those earlier fuckups with multiple sends) except for the directories
and, now, that delay commented out.

I'll take out those other 2 delays, and watch it carefully on the next
transmission to see if I can see where in the script the delay is coming
from.

PE> Dieter is 5 seconds.  Brenton is connecting with MNP5, if that
PE> has anything to do with it (hey Brenton, it's a dumb idea to
PE> connect with MNP5, why not try MNP4 instead?).

PE> BTW, I recall you asked about ITUG or something, I didn't get
PE> around to replying.  All nodes are equal (more or less).  ie
PE> I don't know any more about why ITUG started flowing than you
PE> do.  If a message in ITUG is being sent from 5 systems upstream
PE> of me, it just gets passed from him to the next guy to the next
PE> guy to the next guy to the next guy to the next guy to the
PE> next guy, where you are the last "next guy", and I am the second
PE> last "next guy".  There's no special facility I have here that
PE> you don't.  How would you solve the problem from your end, and
PE> I'll tell you whether I can do the same thing from my end, and
PE> then I will probably ask you to do it your end to save me from
PE> having to do it my end.  Unless you know something I don't, e.g.

I thought you might have heard something in the secret sysop society.
There has since been a message from someone else which suggests to me
that it was Bernard himself who just didn't send that November stuff
until January. Or some system close to him.

PE> what price we ended up getting Email at.  BFN.  Paul.

What? Email is free! Oh, you mean EML. :-) 377, as you now know.

Regards, FIM.

 * * A:  I don't know  and I don't care.
@EOT:

---
* Origin: Pedants Inc. (3:711/934.24)
SEEN-BY: 711/934
@PATH: 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.