Date: Wed, 1 Sep 93 04:30:09 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 #224
To: tcp-group-digest
TCP-Group Digest Wed, 1 Sep 93 Volume 93 : Issue 224
Today's Topics:
how can I get started?
NOS in NT VDM (4 msgs)
Subscribe (2 msgs)
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: Tue, 31 Aug 93 14:46:30 PDT
From: William.Dorsey@Corp.Sun.COM (Bill Dorsey)
Subject: how can I get started?
To: tcp-group@ucsd.edu
I have a Kantronics KPC-3 connected to one of the serial ports of my
Sun Sparcstation. I'd like to be able to handle TCP packets as well as
AX.25 packets. Can someone recommend some software that will run under
SunOS 4.1.3 and enable me to do this? Also, since my Sun is connected
to the net, it would be nice if it allowed gateway operation.
--
Bill Dorsey william.dorsey@corp.sun.com
PGP 2.X public key N3LMF
available on request N3LMF@N0ARY.#NOCAL.CA.US.NA
------------------------------
Date: Tue, 31 Aug 1993 07:17:52 -0400 (EDT)
From: "David J. Trulli" <nn2z@nn2z.UCSD.EDU>
Subject: NOS in NT VDM
To: "D.Crompton" (D.Crompton) <rutgers!nadc.navy.mil!crompton%kb2ear@princeton.edu>
Has anyone tried to have a verison of NOS attact to the system com
driver buy opening the device COMX: ?
Since NT and OS have serial driver this maybe better than going
thru the hardware uart emulation.
Any thoughts ?
Dave
>
> I tried running KA9Q - 01/18 under NT and got the same type of message. I seleceted
> ignore the warning and it did not respond to any keyboard input. I was able to close
> it without any problems though.
>
> I have not tried JNOS yet. This may be related to the (lack of) a PIF file. I will
> fool with it some more in that regard and let you know.
>
> Doug
>
--
Dave Trulli internet: nn2z@nn2z.ampr.org, david.trulli@att.com
packet: nn2z@nn2z.nj.usa.na
------------------------------
Date: Tue, 31 Aug 93 11:43:12 CDT
From: Jack Spitznagel <spitznagel@utmem1.utmem.edu>
Subject: NOS in NT VDM
To: tcp-group@UCSD.EDU
Hi Dave, All...
David asks:
>Since NT and OS have serial driver this maybe better than going
>thru the hardware uart emulation.
>
>Any thoughts ?
Just one.... does NT now provide a "DOS-compatible" (whatever that is??)
virtual hardware interface? The COM driver in OS/2 provides one that behaves
like a 16550AFN/16450 (depends on what is actually there!) for each VDM. This
interface should be accessable from the NOS VDM without any problem providing
you are not trying to:
Share Interrupts between ports (without specialized hdwe and drivers)
Use a port already owned by another process.
Additional suggestion... (don't remember if you were doing this...) Try
bringing NOS up as serial port only first... then try to figger out the packet
driver problems.... The Crynwr packet drivers load "high" very well in the OS/2
VDM so I imagine they could also in NT unless the virtual hardware hooks
provided for the VDM are as limited as they were in the beta .
73... jack
kd4iz
John Spitznagel D.D.S. | #1. Check the fuse!
College of Dentistry | #2. Turn it on.
UT-Memphis | #3. Kick it.
875 Union Avenue | #4. Drop it.
Memphis, TN 38163 | #5. Call the company.
(901) 528-6441 | #6. Read the Manual.
------------------------------
Date: Tue, 31 Aug 1993 15:17:30 -0400
From: goldstein@carafe.tay2.dec.com (k1io, FN42jk)
Subject: NOS in NT VDM
To: tcp-group@ucsd.edu
Before anyone even wastes time trying...
Remember that NT does NOT allow DOS device drivers to run, period.
This is not OS/2, which does. OS/2 allows DOS boxes to have access to
real hardware devices, so a packet driver will load. This has the
slight risk that a driver will muck with physical address space and
corrupt the system, but once you get it running right it's usually okay.
NT is designed to be a notch or two more secure. It hides the real
hardare through a Hardware Abstraction Layer (HAL) and only allows NT
native drivers to see it. So if NOS is looking for a 16450 or 16550,
it won't find it.
DOS programs can, I suspect, access COM ports in NT, by making the
appropriate calls. But the old DOS tradtion is to avoid the O/S as
much as possible. In NT, you have a real operating system which owns
all the hardware, and you have to play by its rules. Note that NT
doesn't claim to run as many DOS programs as OS/2 does; too many DOS
programs don't play by its rules.
fred k1io
------------------------------
Date: Tue, 31 Aug 93 16:44:01 EDT
From: crompton@NADC.NAVY.MIL (D. Crompton)
Subject: NOS in NT VDM
To: djt@hoccny.ho.att.com, tcp-group@ucsd.edu
I got further this morning using JN110x9. Its runs but I am not
getting data from the serial ports yet. I can transmit.
BPQ and FBB runs. So does telix a terminal emulator.
Dave
Dave,
I would suspect that you must use comm ports other than those
that NT knows about, since NOS does direct I/O. That is assign
the comm port to other than 3f8,2f8 if you have a com1/2. The other
problem though is the interrupts. It might be easier to run a simple
com I/O program where you can assign an address and interrupt and
play around.
WINNT will run OS/2 text mode programs - maybe try running the OS/2
version of NOS under NT??
Doug
------------------------------
Date: Tue, 31 Aug 93 08:21:27 CDT
From: mfoster@amoco.com (Michael H. Foster)
Subject: Subscribe
To: tcp-group@ucsd.edu
Subscribe
------------------------------
Date: Tue, 31 Aug 93 10:06:14 -0500
From: Terry Hubbard <hubbard@convex.csd.uwm.edu>
Subject: Subscribe
To: tcp-group@ucsd.edu
I hope I am directing this message to the right place. I would like to
subscribe to a newsgroup for tcp on amatuer radio and was told this is
the place to be. I have a question on ka9q 386 net relating to getting
ax25 to recognize kiss headers from my pk232. It works on previous
releases of nos but not the version I ftp'd from ucsd. If this is not
the right place, my appoligies. If you could help on this it would
be very much appreciated.
Terry, KF9HI
KF9HI@wa9kec.wi.usa 44.92.1.53
hubbard@convex.csd.uwm.edu
------------------------------------------------------------------------
------------------------------
End of TCP-Group Digest V93 #224
******************************
******************************