Date: Sat, 16 Jan 93 04:30:13 PST
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 #16
To: tcp-group-digest
TCP-Group Digest Sat, 16 Jan 93 Volume 93 : Issue 16
Today's Topics:
Microsoft 7.0 & WG7J JNOS
mids & bids ??
PMNOS errata
Terminal with NOS???????
TIP etc.
Using Terminal with JNOS 1.07
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: Fri, 15 Jan 93 19:50:17 PST
From: algedi!aa6ed (aa6ed)
Subject: Microsoft 7.0 & WG7J JNOS
To: tcp-group@ucsd.edu
I don't want to get into a debate as to which is the better compiler,
Borland C++ 3.1 or Microsoft 7.0. I'm more concerned with the inability
to compile JNOS or any other NOS version using the Microsoft 7.0
product.
Has NOS/JNOS developed into a compiler/vender specific application,
and no longer has the ANSI standardization needed to transverse
different compiler software platforms?
Has anyone had success compiling WG7J JNOS 1.06++ using Microsoft 7.0???
Once again, I'm not against Borland products, I'm more concerned about
the trend of locking NOS/JNOS into being able to use ONLY Borland
products.
73's
AA6ED
|-----------------------------------------------------------------------|
| Ham : aa6ed.ampr.org [44.24.103.157] William [Bill] Bytheway |
| LLBBS : (206) 271-4657 (300/1200/2400) 11108 SE 184th Place |
| Voice Phone : (206) 271-4476 (w/recorder) Renton, WA 98055 |
|-----------------------------------------------------------------------|
| Return mail from UUCP/Internet should use : algedi!aa6ed@Data-IO.COM |
|-----------------------------------------------------------------------|
------------------------------
Date: 16 Jan 1993 22:53:14 -0500 (Sat)
From: Steve_Wright@kcbbs.gen.nz (Steve Wright)
Subject: mids & bids ??
To: tcp-group@ucsd.edu
Whats MIDs and BIDs got to do with TCP/IP (and tcp-group??) Isn't this an
outdated form of forwarding that doesn't live on top of TCP ? Excuse me if I'm
wrong. No flames to the group please.
Steve - ZL1BHD
------------------------------
Date: Fri, 15 Jan 93 13:03:47 EST
From: kz1f@RELAY.WESTBORO.LEGENT.COM
Subject: PMNOS errata
To: tcp-group@ucsd.edu
Hi all, I have some good news and some bad news!
First the good news, Microsoft announced NT wont ship till '94.
Now the bad new, IBM is helping them.
Actually I have an alledged solution to the Font Mgr problem some of you
have seen. This problem may or may not appear on any given machine
with any particular video adapter. The symptom is selecting file font may
cause PMNOS to crash. I have it on good authority that, depending on ones
version of OS/2 and video drivers that invoking the font mgr takes an
excessively large amt of stack. I give it 10k which is a reasonable amt. I
updated pmnos.def to give it 15k (15340) and fonts seem very solid, they were
almost very solid before I did that. So, if you are in an environment that
allows you to recompile (I didnt ship the objects) and relink, change PMNOS.def
to reflect the larger stack. Also, for those that didnt know it,
1) use nmake -f makefile.ndb - no debug
2) change the compiler invokation line to -G4 if you are running a 486
or -G5 if / when you are running a Pentium.
The makefiles as shipped are for default of 386, 486 specific code will run
on a 386, it will be larger than necessary though.
The makefile.ndb should be fine however, the file makefile may have a -Ss
switch in it, this should be removed. The file makefile.opt is for
experimentation with the optimizer...at your own risk, it works for a little
while than hangs up.
Now the bad new,
For those that dont/cant/wont recompile and re-link PMNOS I attempted to
upload a new executable to UCSD, since today is moving day. In trying to
find them today, I can not. I believe they were eaten by the i-net monster.
(Come on..dont you have kids). Anyways, I put, perhaps inadvertantly, the
source and exe into the main incoming dir at UCSD last night, they are gone
today. I told Jack I had uploaded them so the versions at giskard arent.
Consequently, I will be moving them to UCSD either tonight or tommorrow and
they will hopefully make it to Chowda later this weekend. Walt
------------------------------
Date: Fri, 15 Jan 93 19:50:10 PST
From: algedi!aa6ed (aa6ed)
Subject: Terminal with NOS???????
To: tcp-group@ucsd.edu
>Hello the group
>I am considering NOS for our local ARC maildrop. Now we are running a
>PK-88 mailbox, but have the potential for problems if a user at the
>console changes parameters unwittingly [or otherwise :-( ].
Try running your PK-88 in KISS mode using WG7J JNOS 1.06+, I'll give you
the reasons later.
> I am curious as to whether NOS could support a simple terminal on one
>comm port with the tnc on the other comm port. Then club members can
>use the shack's terminal to 'log in' to the mailbox just as they would
>over the air, with no chance of changing the system setup.
I'm running my JNOS software with three TNC ports (three transceivers)
and one modem port running TipMail. I compiled my JNOS software without
the 'Converse' mode compiled into it because of a problem with entering
a 'TelNet' type session.
My system is running Windows 3.1, I have a telephone BBS written in
Borland Turbo Pascal for Windows, it has a second port connected to a
special NULL modem cable to my JNOS session. By special, I use the
RTS signal from my telephone BBS (wires crossed over to) to simulate
the RLSD (carrier detect) signal.
Callers from my telephone BBS (with appropriate callsign verification)
have access to all three TNC ports, as well as to the BBS feature.
My BBS provides a service to both non-ham and hams, the only difference
is that hams can transmitt over packet radio, non-hams can only read
the bulletins.
Send personal mail to my address below for more information.
73's
AA6ED
|-----------------------------------------------------------------------|
| Ham : aa6ed.ampr.org [44.24.103.157] William [Bill] Bytheway |
| LLBBS : (206) 271-4657 (300/1200/2400) 11108 SE 184th Place |
| Voice Phone : (206) 271-4476 (w/recorder) Renton, WA 98055 |
|-----------------------------------------------------------------------|
| Return mail from UUCP/Internet should use : algedi!aa6ed@Data-IO.COM |
|-----------------------------------------------------------------------|
------------------------------
Date: Fri, 15 Jan 93 11:12:19 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: TIP etc.
To: tcp-group@ucsd.edu
With all this talk of the TIP bbs interface - has anyone ever run
SLIP and TIP on the same modem? This would be useful. I am not sure
how it would work - maybe a priveledged option in the BBS to switch
to slip? This would allow you to use one interface and modem to
support both tasks.
The Phone BBS's option of NOS is one area that does not get very much
press. It seems to me that it would be an excellent way to introduce
new users to TCP/IP without the initial expense of a radio and TNC.
Any ham with a modem and the appropriately configured NOS code could
call into a server. I know we are an Amateur Radio group but some may
prefer this option, especially those who are not near a server or who
have operation/antenna limitations.
Doug
------------------------------
Date: Fri, 15 Jan 1993 09:05:42 -0600
From: miltonm@inetnode.austin.ibm.com (Milton Miller)
Subject: Using Terminal with JNOS 1.07
To: pjb@hss.caltech.edu, tcp-group@ucsd.edu
Jack did find the problem... if ((int) t & CONF_LINK) was being triggered
by the TIP session type passed into t.
However, the fix was wrong. CONF_LINK is defined in labp.h as one of
several bit flags under the jumpstarted field. However, the second
paramtetr of the mbx_incom from the tip mailbox is TIP, which is the
session type number for console to asy outbound.
My "Hack" fix was to change CONF_LINK from 8 to 256. The real fix is to
find all the places mbx_incom is called, and change the argument to be
of the same class. Oh yeah, the constants shouldn't be defined in LAPB.h
either.... I don't want to include lapb.h into my telnet server! Put
them in mailbox where they belong. (Alternatly, determine the session
type, netrom/ax25/telnet(tcp)/tip by looking at the type of the socket).
milton
(I'm sure ben is going to give me the list of changes we made soon, so I
can tell you all about them :-)
------------------------------
End of TCP-Group Digest V93 #16
******************************
******************************