🚀 go-pugleaf

I got much of the same, ONLY the ORIGINAL program, I suspect, knew
about the -d spec on the command line.  I now have a split of
/net/spool for the NOS stuff and /spool for the elm-bm stuff.  None of
the original autoexec.bat environment variables seem to be read by the
mail code.  Strings elm.exe ( few strings in bm ) suggest that
/spool/{mail,mqueue,..} are hard coded.

Follows a brief compendium of our FAQs, without the answers.  Any one
with a flame thrower, on low, wish to help, answers or where to look
for them ?

  maybe the QEMM5.0/ DV2.3 is useable here and will bail us out of the
space problems.  Either that or try separate invocation of bm.  bm
seems to call elm or else nos calls elm to check out the bm work, or
both like with /bin/sendmail in unix seems to get called for
everything by everyone.  ideas ?

  any idea how to make me forward mail between my 2 ports? 

  have you seen version of ka9q code straight from Phil?  Wonder if
the dialer there behaves as advertised?

  noted that my v 1.6 won't run mail ("abnormal program termination"
followed by "net>" prompt) whereas v 1.4 seems to run mail ok.

  using nos here telnetted and the <backspace> key kills a word; using
ncsa telnet, backspace just kills a character.

  as a consequence of reading the docs (Net User Reference Manual,
3/7/91, by Bill Simpson, ca 50+ pages) .. moved the root files to
\nos.  My mailer is inop.  moved the \spool stuff to \nos\spool, but
that gave another error msg.  will work on it more... [[ Believe this
was in concert with nos -d /nos.  Only seems to work for NOS and NOT
for bm-elm, whichever is really running. or both? ]]

  tried dialer.  It doesn't behave as advertised in the doc.  There's
one less parameter (number of pings) than the doc says there are.
When i start dialer, it just sits and pings forever, (at least the
g1emm v1.4 did, will try the v1.6 here (office) since i just brought
it in.

  do you have the maildoc that's mentioned in the doc you sent?  

  also tried some route stuff at home hoping to make it route your
packets but no good.  just succeeded in making my machine call itself
over the air.  somehow, the concepts of arp and route haven't quite
soaked in yet, but i'm getting there....

  maybe someone out here in ka9-g1emm land has been able to use a 386
with Waffle or another uucp to gateway their internet / Unix mail into
their PC without having to reboot, change config.sys files for X00 or
what ever and has a seamless way to do ampr stuff as well as their
Unix land related stuff ?  NO I am not quite ready for the great train
robbery to do Unix PC and DOS windowed PC on a Sun or the like ...

Any ANSWERS TO THESE and other questions greatfully accepted.  Either
reply to the tcp-list@ucsd.edu or if our questions are all recently
answered then email to our local list will help a lot of hams here in
town (Ventura County).  If such compended questions give any of the
readers gas I would be willing to post multiple readers questions ONE
AT A TIME.

Locally we are nswses-tcp-group@suned1.nswses.navy.mil or @suned1.UUCP
and we are in the maps.

WONDER, would it further overburden the list keeper to retain in the
mail archives for tcp-group a list of File names and Subjects for each
V90 V91 major group of archives .. like in csh, by

  foreach i ( V91*.Z )
    zcat $i | egrep '^Subj|^Date' >> V91.list
  end

Unless you already have such a beast and I just dont know where it is .. 

Tnx and 73's /Ev/

-- 
 +  efb@suned1.nswses.Navy.MIL  efb@gcpacix.uucp  efb@gcpacix.cotdazr.org +
 +  efb@nosc.mil   WA6CRE    Gold Coast Sun Users   Vta-SB-SLO DECUS  gnu +
 +  Opinions, MINE, NOT Uncle Sam_s | b-news postmaster xntp dns  WAFFLE  +