Date: Thu,  8 Apr 93 04:30:10 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #92
To: tcp-group-digest


TCP-Group Digest            Thu,  8 Apr 93       Volume 93 : Issue   92

Today's Topics:
                         DOS 6.0 and stat cmd
                      DOS 6.0 FIX - CORRECTION!
                            IBUFS in JNOS
                            JNOS108e !!??
                        MORE DOS6 changes JNOS
                       PacComm Tiny-2 KISS Bug
               Returned mail: unknown mailer error 176
            Returned mail: unknown mailer error 176 (fwd)
                           uploads to UCSD
                        WAMPES patch available

Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Thu, 08 Apr 93 02:16:25 CDT
From: ed@wa9yyf.ampr.org (Ed Curran)
Subject: DOS 6.0 and stat cmd
To: tcp-group@ucsd.edu

Hi,

I upgraded to the new 6.0 version of DOS last weekend, and now the
status command is not working properly. I added the case 6 as Doug
said in his message, but either get no listing of open files or
garbage. I know it must have something to do with the entrylen, but
I don't know what the magic number is. I am using PA0GRI 20.p version
of nos.

Can anyone tell me what I am doing wrong or what else I have to change
to make it work. I am sure this question is going to come up alot.

Thanks, Ed wa9yyf

------------------------------

Date: Thu, 8 Apr 93 00:04:59 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: DOS 6.0 FIX - CORRECTION!
To: nos-bbs@hydra.carleton.CA

Sorry for this screwup.....

Don't know what I was thinking but this is the correct logic
also the change to ksubr.c - text labeling does not apply.
I had been looking at an old version.

If you have the following in ksubr.c it is correct - 108d (df)

static char *Taskers[] = {
        "",
        "DoubleDos",
        "DesqView",
        "Windows",
        "DOS 5.x",
        "OS/2 2.0 DOS emulation",
        "OS/2 2.0 virtual boot machine or other DPMI environment"
};

You may want to change the DOS 5.x to DOS5/6.x or something like that.

CORRECTION to earlier pcgen.asm fix for dos 6.0 -

@@5:    cmp     bl, 5           ;DOS 5.x
; START CHANGE        
        je      @@5a
        cmp     bl,6  ;DOS 6.x
        jne     @@6
@@5a:   mov     mtasker, DOS5STYLE      ;Release time same way as Win 3.x
        ret
; END CHANGE        
        ; Handle OS/2 Virtual Boot Machine (N1BEE)
@@6:    mov     ax, 1687h       ;Check DPMI installed state



Doug

------------------------------

Date: Wed, 7 Apr 93 14:42:57 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: IBUFS in JNOS
To: nos-bbs@hydra.carleton.CA

Ok here is what I have done about the intq stuff after hearing Phil's
and other comments.

I replaced the JNOS mbuf.c in entirety with Phil's Net version.
I removed all references to refiq() from config.c
I commented out all references to donibufs and doibufsize in alloc.c
I replaced a portion of the network function in config.c with a
portion of the network function from Phil's code (iface.c)

This eliminates the Nibufs entirely. I don't know if that is good
or bad but it is easy enough to find out!

I may have missed one thing in that description but it will show up
very quiclkly in a compile. The bottom line is that it took about
15 minutes and was rather easy. Now I have to see what the impact
is!!

If anyone wants to try it (108d/df) I could supply the modules I changed.

Doug

------------------------------

Date: Thu, 8 Apr 93 02:20:41 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: JNOS108e !!??
To: nos-bbs@hydra.carleton.CA

No I am now issuing another NOS version but I had to call it something
here!

As per Phil's advice I added alloc.c in entirety to JNOS along with
the earlier changes. This brought about a problem with the availmem
function that required changes in a number of modules.

Availmen() in JNOS returned an unsigned long of memory bytes, in Phil's
code he changed that to an int return - 0 if OK - so all of the
instances of  'if (availmem > memthresh)'  had to be changed to
'if (availmem())'  and of course other logic in some places.

Anyhow after a few hours of chasing all of that stuff it is RUNNING!!
and it seems stable - I have run ethernet and asy and at least ethernet
seems about 10% faster - but that is not a scientific test.

So no more intq and Phil's new memory alloc updates are running in JNOS.

I also added - coreleft - to the memory status display - Phil had left
it out in his code - I am use to seeing it.

So will run it here on my server and let you know the results - so far
good. I will be outta town tomorrow - back Thurs. night.

The changes are NUMEROUS so I would probably have to supply a number of 
modules. I can get them together and ship them to ucsd if anyone wants
to try this. 

Not sure where Johan is on the update but if he wants to include or try
this I could get something to him early Friday.

Doug

------------------------------

Date: Wed, 7 Apr 93 14:38:56 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: MORE DOS6 changes JNOS
To: nos-bbs@hydra.carleton.CA

The following is a fix to add to JNOS108D or Df. It is needed for DOS 6.0.
Also previously no text was defined for some of the tasks and when 
doing a PS the "running under" would give garbage.

Change this function in ksubr.c

static char *Taskers[] = {
        "",
        "DoubleDos",
        "DesqView",
        "Windows",
        "DOS",
        "OS2",
        "DPMI"
};

Add the marked lines in pcgen.asm        

        ; Check for DOS 5.0 or OS/2 2.0 (N1BEE)
@@3:    mov     ax, 3306h       ;Get true DOS version
        xor     bx,bx
        int     21h
        cmp     bl, 20          ;DOS 20.x (OS/2 2.0 DOS emulation)
        jne     @@5
        mov     mtasker, OS2STYLE
        ret

@@5:    cmp     bl, 5           ;DOS 5.x
;START ADD        
        jne     @@5A
@@5A:   cmp     bl, 6           ;DOS 6.x
;END ADD        
        jne     @@6
        mov     mtasker, DOS5STYLE      ;Release time same way as Win 3.x
        ret
        
        ; Handle OS/2 Virtual Boot Machine (N1BEE)
@@6:    mov     ax, 1687h       ;Check DPMI installed state


Johan - Please add this to the code

Doug

------------------------------

Date: 07 Apr 1993 23:26:00 -0400 (EDT)
From: "Brian A. Lantz" <BRIANLANTZ@delphi.com>
Subject: PacComm Tiny-2 KISS Bug
To: TCP-Group@ucsd.edu

I posted this once last week, but I think it went into that great bit-bucket
in the sky, since a copy never got back here. Oh, well.... One More TIME!
 
> The latest info from NX2P (about one month ago) is that PacComm fixed the
> bug in a beta version of the firmware, but that the fix hasn't been
> incorporated in their released version.  Last summer, they had promised me
> a formal release by the end of September 1992, but it apparently never
> happened.
 
Good news and bad news! The good news is that PacComm has recently hired a
Manager of Software Development, who has the responsibility of (among other
things) straightening this thing out.
 
The bad news is that I am that person, and it will take a week or so to get
worked out. I will be working on getting a new OFFICIAL release locked down,
getting it documented, and out the door.
 
> He also said that PacComm *may* post the fixed code somewhere, someday,
> and allow people to download it and burn their own EPROMs.
 
I also will be determining policies for bug fixes and bug reporting.
 
73 from Brian A. Lantz      KO4KS@KO4KS.#TPAFL.FL.USA.NA    3100813105
                  Internet: brianlantz@delphi.com
                   Amprnet: ko4ks@ko4ks.ampr.org         [44.98.0.167]

------------------------------

Date: Fri, 2 Apr 93 19:01:36 +0100
From: Mail Delivery Subsystem <Postmaster>
Subject: Returned mail: unknown mailer error 176
   ----- Transcript of session follows -----
554 <local.tcp-group@mars-edg.prime.com>... unknown mailer error 176

  ----- Message header follows -----
Received: from cvedg by mars-edg.Prime.COM; Fri, 2 Apr 93 19:01:36 +0100
Resent-From: tcp-group-request@cvedg.Prime.COM
Resent-Message-Id: <9066.9304021803@cvedg.Prime.COM>
Resent-Date: Fri, 2 Apr 93 19:03:22 +0100
Resent-Sender: tcp-group-request@cvedg.Prime.COM
Received: from ucsd.edu by cvedg.Prime.COM (5.65b/UK-2.1.CV) with SMTP
 id AA09060; Fri, 2 Apr 93 19:03:15 +0100
Received: by ucsd.edu; id AA20046
 sendmail 5.67/UCSD-2.2-sun
 Fri, 2 Apr 93 05:17:22 -0800
Sender: tcp-group-relay@ucsd.edu
Received: from bds.bds.com by ucsd.edu; id AA20036
 sendmail 5.67/UCSD-2.2-sun via SMTP
 Fri, 2 Apr 93 05:17:16 -0800 for /usr/mail/listhandler tcp-group
Received: by bds.bds.com (5.61/1.34)
 id AA20304; Fri, 2 Apr 93 08:17:28 -0500
Date: Fri, 2 Apr 93 8:17:28 EST
From: Mike Gallaher <mg@bds.bds.com>
To: tcp-group.@bds.bds.com;
Subject: gangrenous NOS bits
Message-Id: <CMM-RU.1.0.733756648.mg@bds>
Precedence: bulk

------------------------------

Date: Wed, 7 Apr 93 13:43:32 BST
From: root@cvedg.Prime.COM (System Admin {CVEDG})
Subject: Returned mail: unknown mailer error 176 (fwd)
To: tcp-group@ucsd.edu

Forwarded message:

------------------------------

Date: Wed, 7 Apr 93 16:55:10 -0700
From: brian (Brian Kantor)
Subject: uploads to UCSD
To: tcp-group

UCSD ran out of space - all 300+ megabytes of it - last night whilst some
people were uploading new stuff to the incoming directory.  Since a large
number of FTP servers don't notice when that occurs, I'll betcha there are
some damaged files there.

I blew away all the files that looked incomplete to me, and did a bit of
cleanup.

If you uploaded a file to UCSD in the past few days, please go check it and
send a fresh version if the one there is damaged.  Just put it in incoming;
that directory was empty when I finished.

Oh, and that's   hamradio/packet/tcpip/incoming  - not /incoming.
 - Brian

------------------------------

Date: Wed, 7 Apr 93 10:13:00 MDT
From: Dieter Deyke <deyke@mdddhd.fc.hp.com>
Subject: WAMPES patch available
To: tcp-group@ucsd.edu

I   have    uploaded    wampes-930402.patch01.Z    to   UCSD.EDU    into
"/hamradio/packet/tcpip/incoming".  This  will  bring   WAMPES   version
930402 up to version  930406.  This  patch  solves all  386BSD  problems
known to me.

This is the README file:

------------------------------------------------------------------------

wampes-xxxxxx.tar.Z  is a compressed  tar archive of WAMPES,  which is a
NET/NOS  port to HP-UX.  It currently  supports HP 9000 series 300, 400,
700, and 800 computers, running HP-UX 08.xx or HP-UX 09.xx.

I also ported the  software to SunOS 4.1.2 and to 386BSD  0.1.34, and it
compiles  there,  but I do not  have  enough  time to  really  test  it.
Feedback is welcome.

WAMPES  was also  ported to Linux  running on a 386 by Olaf Erb,  dc1ik.
Comments  and  questions  about the Linux port of WAMPES  please to Olaf
Erb, <erb@insu1.etec.uni-karlsruhe.de>

To unpack this archive you should  create the  directory  /tcp and cd to
it.  After unpacking please read the file /tcp/doc/intro.txt.

wampes-xxxxxx.tar.Z     and    all    followups     should    go    into
/hamradio/packet/tcpip/wampes on UCSD.EDU.

73,
Dieter Deyke, DK5SG / N0PRA, <deyke@fc.hp.com>

------------------------------

End of TCP-Group Digest V93 #92
******************************
******************************