Date: Fri, 13 Aug 93 04:30:04 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 #207
To: tcp-group-digest


TCP-Group Digest            Fri, 13 Aug 93       Volume 93 : Issue  207

Today's Topics:
                            Compiling NOS
                     convers + wampes info please
                              NT is out

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: Wed, 11 Aug 93 23:17:35 CST
From: jimh%kd4ldo.tcman.ampr.org@skeggi.vware.mn.org (Jim Henderson)
Subject: Compiling NOS
To: tcpgroup@kd4ldo.tcman.ampr.org

Hi all:

A while back, I posted a message to the group asking for assistance in
compiling the latest RCS distribution; I didn't see it come back in the
group, so I have to assume it didn't make it....Gonna try it again:

I'm attempting to compile the latest RCS sources (from ucsd.edu) using
Borland C++ 3.1, but having some problems.  When I compile, I get error
messages in reference to a function called "dodebug".  In addition to
this, there's a few references to files that don't exist (all of which
fall under CDMA in the makefile); I saw that I need to leave qfax2.obj
out of the list, but a few other files came up as not existing as well.


I removed references to those files, and commented out the lines that
referred to dodebug(), and the compile ran smoothly and created the
executable file.  However, upon trying to run the program, the machine
locked; interrupts were still enabled, but the machine just sat there.

The first time I ran it was on a workstation on a Netware 4.0 network; I
saw the file TEMP.000 open just before the program locked up.  I tried
running without the Netware requester, thinking that the VLM drivers
may have been causing the lockup.  I booted a completely clean system,
but still had the program lock up on me.

Can someone help me with these problems?

Thanks in advance.

Jim
----
Jim Henderson, KD4LDO/W0 jimh@kd4ldo.ampr.org [44.94.249.38] on 144.99 MHz
Crystal, MN                     Internet:  jimh%kd4ldo@skeggi.vware.mn.org
CIS:  71321,1461                Alt. Internet:  hendersj@alpha.db.erau.edu

"Don't ask me how it works or I'll start to whimper!" - Arthur Dent

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

Date: Fri, 13 Aug 93 09:51:12 CET
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: convers + wampes info please
To: TCP-GROUP <TCP-GROUP@ucsd.edu>,

In your latest install.txt file, you make a mention of haveing
the source for wampes 9307xx   the most recent version release
to public on ucsd.edu:.../incoming  is wampes-930623
where can we find a newer version.? or is the 9307xx a typo.?
thanks Barry.

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

Date: Thu, 12 Aug 1993 10:00:55 -0500 (EDT)
From: djt@hoccny.ho.att.com (David J.Trulli)
Subject: NT is out
To: tcp-group@ucsd.edu

I just installed windows NT this week and this weekend I will get some
time to see of NOS runs under NT. Has anyone done anywork in this area
yet.  NT has some potiential to be a useful NOS system.
Some things we may want to do in steps.

1. get NOS TCP/IP to talk to windows built in TCP/IP with some
   kind of tunnel driver.

2. Figure out how to use the Microsoft mail interface for NOS mail.


3. Then work on integrating NOS into the WIN32 system. Like PMNOS in OS2


4. Get new applications.


-- 
Dave Trulli   djt@hogpa.att.com or David.J.Trulli@att.com
AT&T Bell Laboratories  908-949-3185
101 Crawford Corner Road
Room 3L-410
Holmdel NJ. 07733

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

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