🚀 go-pugleaf

 This is a general thanx message to those who helped me.

 SACIA:

 I finally got around to reading the eliminator docs and found that
bit about the DTR remaining active when the device was
uninitialized.  I have assumed that the reason iniz fixed the
problem was because the device never got uninitialized, so the
problem never came up.
 In any case, I fixed the problem permanently by setting up my
descriptors with CTS/RTS enabled and a 15-page buffer with normal
DTR (off when port not in use).

 UNZIP:

 After reading a couple of messages, I grabbed v 4.5c, and while I
haven't actually tested it on a  L O N G  archive, I have tested it
on a few, and it is MUCH faster, and doesn't appear to have the same
problem.

 INIZ:

 Thanx for explaining what the reason for this was!  I had had some
problems (as described) with the development system ramdisk, mainly
because I hadn't INIZed it first!
 In the end, I've INIZed all my drives in startup, and it's gotten
rid of an intermittent and unexplained problem I was having with my
B&B:  when using the hard disk and receiving at high speeds before,
the HD would sometimes  lock up in what appeared to be an unending
seek loop, and I would have to reset.  Now, the problem doesn't
happen, and I've successfully unZIPed a 700k ZIPfile while
downloading on one port and sending on another without a lockup
(never would have happened before).  If anyone wants to elaborate on
this, I'm all ears, as this is an odd problem I'd not heard about.
 In any case, since I've used INIZ, it's fixed, so thanx to those who
explained what INIZ DID exactly (I looked up the init subroutines in
the tech section, that helped some, too!)

 Anyway, thanx again to all for help on my latest barrage of
questions!

 - A. Hsiao

--
via Fortress Gateway at uumind.mind.ORG