🚀 go-pugleaf

From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Date: Wed, 12 Jun 91 11:43:43 EDT
Subject: Re: New NOS from PA0GRI

Gerard,

   I have been running NOS (G1EMM etc) under DOS 5.0 for many months and
others are starting to now with no problems. I see no reason why anything
that runs under an earlier version of DOS would not run under 5.0 - if so
I would think that Microsoft would want to know about it, that is if you
are not doing something out of the ordinary.

 Anyhow the problem is only in the 'stat' command. It looks at the DOS
version and does not know about anything higher than DOS 4.x - It retruns
an error message that as I said can be ignored. It would be nice to not
have that error returned. DOS 5.0 has some significant improvements and
many users will be switching to it over the next year.

Doug


----
From: Antonio Querubin <tony@mpg.phys.hawaii.edu>
Date: Wed, 12 Jun 91 7:15:21 HST
Subject: Re: New NOS from PA0GRI

> Please note that with a vew sessions active you soon are bound to get memory
> problems and " a lot of things stop working as advertized".

Thanks for all the work.  The stuff looks good as long as we don't
over load it but I wonder, just how many sessions can it handle before
it goes crazy?  We run an active gateway here using the packet driver
and running the NNTP client as well.  Also, some of the entries in the
alias file have more than 20 aliases.  Send a message to one of those
and you can see where we'll get memory problems.

Tony
AH6BW


----
From: Antonio Querubin <tony@mpg.phys.hawaii.edu>
Date: Wed, 12 Jun 91 7:47:54 HST
Subject: nntp in NOS

Our NNTP server administrators have suggested that it might be better to get
a manual feed from the news server rather than have NOS query the server
periodically (currently the timer is set to one hour).

Doesn't NOS have to be running as an NNTP server also for this to work?  I've
scanned through the code and it looks like NOS runs as an NNTP client only. 
Am I right/wrong, half-right?...

If it will work, will NOS still be able to query the server for
newsgroups that aren't on the normal forward list?

Antonio Querubin  
tony@mpg.phys.hawaii.edu / ah6bw@uhm.ampr.org / querubin@uhunix.bitnet


----
From: Brian Roode <brian@pluto.nts.uci.edu>
Date: Wed, 12 Jun 91 14:34:36 -0700
Subject: Tiara ARCNET packet driver

Hello,

Does anyone know where I might find a packet driver for a Tiara ARCNET 
card?  Will this card work with NOS?  I've tried the driver that's in 
the clarkson archive with no luck... 

Thanks,

Brian
KA6CCF



----
From: Antonio Querubin <tony@mpg.phys.hawaii.edu>
Date: Thu, 13 Jun 91 2:47:01 HST
Subject: mbox forwarding to wa7mbl bbs

Looking for anyone who has experience forwarding from NOS to a wa7mbl bbs.
I'm running into what looks like a corrupted header problem when NOS tries to
deliver a message to the other system.

The message looks ok when read on the NOS system but when it reaches
it's destination things look very very weird.
The problem usually shows up as the TO or FROM header containing only a
number.  Sometimes, another header may also be bad (if there is it's usually
the subject field containing parts of an SP command line).  I haven't
been able to find a pattern to this.  As far as I know, NOS is putting
out a correctly generated SP command line.  Could there be a problem
with wa7mbl's ability to parse that command line?

Tony
AH6BW


----
From: jmd@Emperor.HandHeld.com
Date: Thu, 13 Jun 91 10:06:21 UTC
Subject: Re: New NOS from PA0GRI

Gerald,
If you want to remove the stat error that you get under MS DOS 5.0, use
the SETVER command under dos to add net.exe (or NOS.exe, etc) with a dos 
version to be returned, such as 3.3.  SETVER is included in 5.0 for just 
such problems as you report!  5.0 is really the next version after 3.3, ALL
of 4.xx can be ignored as a bad tangent!  I HIGHLY recommend 5.0, if just
for the fact that it puts most of it's code in the HMA which is just above
the 1 meg boundry, so for those us us who cram tsrs into the 640-1000
area with QEMM, the gain in memory is still real!  5.0 will use QEMM,
or it will supply it's own version, complete with commands to LOADHIGH like 
QEMM's LOADHI!

73 Jim

----------------------------------------------------------------
| Applelink : HHPRIC.JIM      | The opinions expressed herein  |
| Internet : JMD@HandHeld.Com | are NOT the official position  |
| (804) 784-3090 Voice        | of Hand Held Products, Inc,    |
| (804) 784-3147 FAX          | and may not even be my own.    |
----------------------------------------------------------------


----
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Date: Thu, 13 Jun 91 10:04:01 EDT
Subject: Re: New NOS from PA0GRI

Tony,

  The size of NOS is certainly getting to be a problem in many systems.
There are a few things that you can do to help. 

  One is to limit the number of smtp sessions - 'smtp max' - this will
help with your large mail list built thru the alias. Another is to
maximize the memory that is available to NOS at startup. If you are
not using a 386 system or above than using DOS 3.2 would give you about
590K (no tsr's) to start with. If you have a 386(sx) or above and more 
than 640K ram you can use DOS 5.0 (or DRDOS) to give you as much as 638K
available to NOS.

  The real answer (if there is one) is to pick up the source code and
change 'config.h' to suit your needs. Don't compile the modules that you
do not need. For instance many do not use RIP and/or RSPF, also PPP and
the drivers can be tailored to your liking. 

 It is getting to the point where you must pick and choose what features
you most want. It is to bad that some of these features (nntp etc.) cannot
work as standalone programs, say in another DesqView window. NOS should
just be the TCP/IP router, handing this info to other programs. That is all
it was suppose to be anyway I guess. I know Phil, go to UNIX! I will be doing
that real soon, but unfortunately many won't, so the decision of what to
include in NOS will continue to be a problem.

Doug


----
-- 
*****************************************************************
   ___  ____  ___    _  _ ___ ___   ___ ___ ___     ___ _  _
  /__/ / / /   /    /\ / /__   /   /__//__//   /__//__ /\ /
 / \  /   / __/_   /  / /__   /   /  //  //__ /  //__ /  /