From: andyross@infopls.chi.il.us (Andrew Rossmann)
Newsgroups: comp.bbs.waffle
Subject: Re: WafflineMail with Waffle 1.65..does it work?
Date: Sat, 02 Jan 93 11:38:14 CST
Organization: INFOPLUS support, Wheeling, IL

tom@spud.kludge.com (Tom Lemos) writes:

> jerryg@jaiser.rain.com (Jerry Gaiser) writes:
>
> > ranfry@mala.proteus.qc.ca (Ranfry) writes:
> >
> > > In <Bzu9pK.Cp2@eis.calstate.edu> afavela@eis.calstate.edu (Alonso Favela)
> > > > Does wafflinemail 1.0 work with waffle 1.65. In the docs it said
> > > >that it worked with 1.64, and since there are different mailbox
> > > >structures, I wanted to ask before I might mess things up. Does anyone
> > > >have WaffLineMail working with 1.65?
> > >
> > > Speaking for myself, NO.  That is I never was able to make Waffline 1.0
> > > work with Waffle 1.65.  I someone HAS been able, please tell me and Alons
> > > how.
> >
> > Well, I got it to work with 1.65. Unfortunately it doesn't understand 1.65'
> > mailbox concept. I still have it available for those that want it for
> > newsgroups.
> >
> had no problems here.. worked fine with 1.64 and then with 1.65.
> Took me all of five minutes to get it up and running. I guess I'm lucky.

  Wafmail 1.00r works fine here. It works fine under DV with 3 changes:

Add /shell to the extern line. Calling it directly caused lockups.

Use the /S1 swapper. I had problems with the default.

If you batch/unbatch in the background, make sure it generates a 'lock'
file while it's running (mine is c:\spool\UUXQT.RUN.) It appears Waffle
opens the USENET and LOCAL files in 'compatible' mode. Wafmail opens it in
'deny write.' You're OK if it's already unbatching a packet, but when it
tries to start up another one, you get a sharing violation. [BTW, set your
SYSTEM memory for the DVCRON template to 1K.] Waffle should open it in
'deny write' also. I DO have 'multitask : dos desqview' in my STATIC file.

  Here's the WAFMAILB.BAT I use:
@echo off
if not exist c:\spool\uuxqt.run goto runit
xu port:0:on
foutt News and mail batching/unbatching is currently running in the background.
foutt Please try Wafmail again in a few minutes.
xu port:0:off
goto done
:runit
type nul > c:\spool\uuxqt.run
wafmail %&
del c:\spool\uuxqt.run
:done

  This problem really only occurs while Wafmail is scanning. I don't think
it uses the USENET or LOCAL files after that. FOUTT is a program that dumps
text out the fossil port, with a trailing CR/LF. Using redirection to
COM1 often caused the computer to lock up.

PS. I've noticed that I get much higher throughput with the Fossil driver
loaded INSIDE the window. I'm running v32bis, with the ports locked at
38400. I have DV setup to optimize communications. [The redirection lockups
mainly occured when I had it set up the way the Fossil docs recommend. I
haven't tried it lately.] I also have a 16550 UART, and run on a 386DX/25.
I normally have Waffle, Memory Status, and DVCRON running all the time.
Waffle handles all polling, DVCRON handles UUXQT/BATCH, EXPIRE, and
nightly maintenance. Unfortunately, my backups won't run under DV, even
with /HW:0E:L.

--
Andrew Rossmann            | Sysop of Infoplus BBS, +1 708 537 0247
andyross@infopls.chi.il.us | Infoplus Support, latest version available
 uunet!infopls!andyross    | by logging in as infoplus. [v32bis/v42bis]
                      NO new taxes...NO new gambling