HDTenEightyP/NetNews huggingface dataset:
From: jrd@cc.usu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Subnets and host addresses
Date: 25 Aug 92 16:45:16 MDT
Organization: Utah State University

In article <1992Aug25.183830.16123@nlm.nih.gov>, ivor@occs (Ivor D'Souza) writes:
> I have a supposedly simple question.  If I have a Class B address 
> 130.14.0.0 and use a netmask of 255.255.255.0, I realize that I could
> have hosts from 130.14.1.1 through 130.14.254.254 (purposefully
> avoiding all 0's and 255's).  If, however, I were to use a netmask
> of 255.255.192.0 (2 bit subnet), how would I be able to make use of
> the leftover bits of the third octet to get the additional hosts I need?
> Any attempts to explain this gruesome scenario will be deeply 
> appreciated.  Thanks.
> 
> -Ivor D'Souza
> ivor@occs.nlm.nih.gov
-------------
	The 6+8 bits left (actually right) over are for host idents. Think
of the IP address as a full 32 bit binary field. 2**14 (-2) hosts is slightly
more than most folks put on a wire (plus repeaters/bridges). A host is on
"this network" if, after exclusive-ORing the source and destination IP bits
(32 operations) and then ANDing the result with the subnet mask (32 more
operations), the result is 32 zeros. Thus the subnet mask discards the "host"
portion when deciding if the IP addresses are on same or different networks.
In your case you have 14 right most bits of "host part."
	Unless there is a strong reason otherwise I suggest using more subnet
bits to allow for future routers and less upheaval when they arrive. 
	Might I recommend some interesting reading material: the book 
"Internetworking with TCP/IP", vol 1, by Douglas Comer. This is a classic and 
in-print gold mine of useful infomation on this and many other TCP/IP topics.
Also acquire volume 2 if you have the interest because it is full of nifty 
things we need to know.
        Joe D.
Xref: sparky comp.protocols.tcp-ip.ibmpc:4981 comp.protocols.tcp-ip.domains:604
From: starrenb@ptt-iat (John Starrenburg)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip.domains
Subject: Automatic reload/reboot of PC BIND server
Keywords: BIND, DNS
Date: 1 Sep 92 09:27:02 GMT
Followup-To: poster
Organization: PTT Telecom B.V. I&AT NWDS-DS-OOTA , Groningen The Netherlands

Is there a way to have FTP's PC BIND (a Name Server) reload/reboot
automatically or through a remote system after the name configuration
has been changed ?
Appreciate any clues.
___
John

-- 
---------------------------------------
John Starrenburg    I&AT    PTT Telecom
Internet: starrenb%ptt-iat@nluug.nl
From: root@nike.rz.uni-konstanz.de. (Z. Horvat)
Subject: Re: ka9q
Reply-To: root@nike.rz.uni-konstanz.de.
Organization: Rechenzentrum Universitaet Konstanz
Date: Wed, 26 Aug 1992 15:31:25 GMT

In article 13834@NICAD3.NIC.BC.CA, broughton@NICAD3.NIC.BC.CA (Simeon Broughton) writes:
>Sorry if this is a FAQ but I can't find an answer. I have 100+
>PC's using CUTCP,  and I would like them to use a dynamic pool
>of say 30-40 IP numbers.  I have ka9q installed on a PC and
>at the end of the autoexec.net I have:-
>
>bootpd start
>bootpd dns nnn.nnn.nnn.4 nnn.nnn.nnn.5
>bootpd dynip sl0 nnn.nnn.nnn.200 nnn.nnn.nnn.249
>
>When I fire up my client I get the first available IP number and
>the dns entries ok, but I can't seem to get the subnet mask or
>default gateway to be passed. As I understand it the bootptab
>file doesn't enter into this as that is only for static entries.
>Any help or pointers appreciated.
>
>      Simeon Broughton, Manager, Computer Services. (604)334-5254
>   North Island College, 2300 Ryan Road, Courtenay, B.C. V9N 8N6. CANADA
>                  broughton@nicad3.nic.bc.ca
>

You should have default entries for the subnet mask in your master bootptab file (/etc/bootptab), something like :

.......................
#Default Entry :

default.def:\
	:sm=255.255.255.0:\  # subnet mask
	:ht=ethernet:\		# ...strange, but it looks like this matters somehow
	:ds=xxx.yyy.zzz.xxx aaa.bbb.cc.dd:\ # Your favorite DNS goes here
	:ts=ccc.sss.iii.ddd:	# Thats for the time server, if there is one
.... etc etc

As far as i remember, the gateway adress should be passed automatically by the gateway which receives/routes the bootp-request.	

---
------------------------------------
Z. Horvat
Rechenzentrum Universitaet Konstanz
7750 Konstanz
+49(0)7531-88-2405

root@nike.rz.uni-konstanz.de
rzhorv@nyx.uni-konstanz.de
------------------------------------

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: hoffman@tsla.noava.lisc.lockheed.com (John Hoffman)
Subject: Re: Sun <=> PC Transfer Rate
Organization: LISC Noava
Date: Fri, 4 Sep 92 00:01:00 GMT

tgl@ssd.kodak.com writes:
: I would like to find a fast way to transfer large files from a Sun
: to a 486 PC. Currently we're using Sun PC-NFS over Ethernet, but we're
: not locked into that. Something like FTP, or writing our own custom
: program using sockets, would be acceptable. The files are tens or
: hundreds of megabytes. Transfers are mostly one-at-a time, on a dedicated
: network (essentially no other network traffic). Any suggestions would be
: appreciated.
:
For speed don't use NFS.  Both FTP and RCP are MUCH faster.

John
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Good TCP/IP package for NFS and with SCO ansi emulation.
Date: 2 Sep 92 19:42:55 GMT
Reply-To: jbvb@ftp.com
Organization: The Internet


    TNGLASS handles the colors, but not the line drawing, and VT100 sequences
    don't appear to map completely to just ANSI.SYS.

I don't know if it's still available, but there used to be a shareware program
called FANSI Console, which was a greatly-improved ANSI.SYS.  You could also
use a 3rd party commercial terminal emulator which supported both the
VT100-style escape sequences and ANSI.SYS colors, but I don't know of one
off-hand.

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488
From: s861298@minyos.xx.rmit.oz.au (Marc A. Boschma)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: ODI TCPIP stack configuration...
Summary: Is it possible to configure TCPIP stack for ODI to use RARP/Bootp
Keywords: ODI TCPIP RARP BOOTP
Date: 2 Sep 92 17:19:36 GMT
Organization: img Consultants

Is it possible to configure the TCPIP.EXE program in the net.cfg file
to use RARP or BOOTP to determin its ip address and network mask ?


--------------------------------------------------------------------------------
Student of R.M.I.T. also a founding member of APANA and :
Marc A. Boschma                                ACSnet: s861298@minyos.rmit.oz.au
img Consultants,				       marcb@img.com.au
GPO Box 3304GG, Melbourne 3001
Australia                                       Phone: +61 3 284 4858    (work)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: I NEED DG EMULATION FOR NCSA TELNET
From: dave@vax2.winona.msus.edu (David Gresham)
Date: 3 Sep 92 12:46:37 -0600
Followup-To: comp.protocols.tcp-ip.ibmpc
Distribution: world
Organization: Winona State University

Howdy,

I am looking for a Data General Emulator that works with NCSA telnet. 
DG410
emulation would be best but anything will be preferable to what I,ve got 
which is nothing.  Also, does anyone know how to get NCSA telnet to coexist
with PC Support and Novell Netware 3.11 using ODI drivers.  Telnet will not
work with this other stuff loaded.   

An answer on E-mail would be prefferable but here is fine too.

Thanks

Dave
From: ronm@slc.slac.stanford.edu (Ron MacKenzie)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Whats Pathworks/TCP max # connections?
Date: 2 Sep 92 22:03:25 GMT
Organization: Stanford Linear Accelerator Center

Hello friends in network land,

I'm programming tcp/ip socket calls on my PC under Pathworks V4.1.
I was wondering what the max. number of connections I can establish is.
Is it 64 since the Pathworks for DOS(TCP/IP) Programmer's reference manual
says MAX_SOCKETS is 64???

Thanks in advance.
Ron



-- 
 
============================================================================
Ron MacKenzie
Stanford Linear Accelerator Center                    Phone: (415)926-2490
P.O. Box 4349                                         Fax:   (415)926-3515
Stanford, Ca. 94309
                                      Internet: ronm@slc.slac.stanford.edu
============================================================================

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: trier@odin.ins.cwru.edu (Stephen C. Trier)
Subject: Re: Two questions -- ethernet and scanner, second warmboot
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Sun, 23 Aug 92 22:22:23 GMT

Problems that appear on cold boots but disappear after a second (warm) boot
are usually caused by not excluding an expansion card's memory area from
a memory manager's load line.

Make sure you tell EMM386/QEMM/whatever you're running to "exclude" the
scanner and network card address space from its memory manipulations.

If you run Windows, you should also tell it about the problem by using an
Exclude= line in win.ini.

-- 
Stephen Trier                      "I am not a lawyer, though I play one
Network Services Engineering        on the net."
CWRU IRIS/INS/Telecom                  Chris Torek, torek@horse.ee.lbl.gov
trier@ins.cwru.edu
Xref: sparky comp.protocols.tcp-ip.ibmpc:5030 comp.protocols.nfs:2211
Organization: K.U.Leuven - Academic Computing Center
Date: Thursday, 3 Sep 1992 09:40:41 +02
From: VAN UYTVEN HERMAN <SYSTHVU@cc1.kuleuven.ac.be>
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Telnet from MS-DOS to UNIX and use VI on UNIX

Hello,

I have a PS/2 running MS-DOS (with Clarkson packet driver and NCSA
telnet and tn3270 installed).
Is it possible to telnet to UNIX and use VI on UNIX ?

Thanks,

-Herman-
From: zlsiimw@mcchpc.mcc.ac.uk (Mark Whidby)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NCSA ftp query - .netrc
Date: 26 Aug 92 10:11:56 GMT
Reply-To: M.Whidby@mcc.ac.uk
Organization: Manchester Computing Centre

In chapter 4 of the documentation that comes with NCSA telnet it says (in
the section on ftp) for the -n option:

-n
Does not attempt auto-login upon initial connection. If autologin is
enabled, ftp checks the .netrc file in the user's home directory for
an entry describing an account on the remote machine. If no entry
exists, ftp will prompt for the login name of the account on the
remote machine (the default is the login name on the local
machine), and, if necessary, prompts for a password and an
account with which to login.

I (and the person I'm asking on behalf of) don't understand this. DOS doesn't
have the concept of a home directory and .netrc is an illegal DOS filename.
Can somebody explain this please?

-- 
_____________________________________________________________
Mark Whidby, Distributed Systems, Manchester Computing Centre
From: AJ@IB.RL.AC.UK (Andrew Jessett)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: INT14 tsr in PC/TCP (FTP)
Date: 28 Aug 92 09:16:55 GMT
Distribution: world
Organization: The Internet

Page 2-117 of the Command Reference



   TNGLASS hostname -e emulator


  Andrew Jessett                           aj@uk.ac.rl.ib

  Rutherford Appleton Laboratory
  Central Computing Department
  Software and Devlopment Division
  Communications & Small Systems Group

  Didcot, Oxfordshire, England.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: skl@wimsey.bc.ca (Samuel Lam)
Subject: Re: LPD for IBM PCs
Reply-To: skl@wimsey.bc.ca (Samuel Lam)
Date: Mon, 31 Aug 1992 00:40:38 GMT

In article <16851C670.PA9690@utkvm1.utk.edu>, PA9690@utkvm1.utk.edu
 (Alan Luchuk) wrote:
>... LPD programs for IBM PC's or PS2's?   We prefer for-sale
>vendor-supported products.

FTP Software Inc. has such a product (PC-LPD).  Contact 
<info@ftp.com> for details.

>Are special purpose devices available that do LPD?  Something
>that plugs into an Ethernet on one side and a printer on the
>other and doesn't require additional software/hardware.

Microplex Ltd. has such a product (M200/M201).  Contact
<info@microplex.com> for details.

...Sam
-- 
<skl@wimsey.bc.ca>
Xref: sparky comp.protocols.tcp-ip.ibmpc:4989 comp.os.ms-windows.apps:2373
From: thoeny@kocrsv01.delcoelect.com (Mike Thoeny)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.os.ms-windows.apps
Subject: Novell 3.11, WinQVT/Net, AST 486/33 problem solved!
Date: 1 Sep 92 17:39:01 GMT
Organization: Delco Electronics Corp.
Originator: thoeny@koadsy06



On August 14, I asked a friend to post a question asking how
I could get WinQVT/Net to coexist with Novell Netware 3.11 on
my AST 486/33 PC.  Thanks to those who replied, I'm up and
running.  I had been trying to get winpkt to work with my setup,
and it was not necessary for what I was trying to do.  The following
added to my autoexec file does the trick!

    lh lsl         link support layer
    lh 3c507       ODI driver.  ethernet 802.3 and ethernet_II frames 
                   selected in net.cfg file
    lh odipkt 1    packet driver interface to ODI driver 
    lh pktint
    lh ipxodi
    lh netx

Thanks again to those who replied! 

--------------------------------------------------------------------------
Mike Thoeny                       Internet: thoeny@kocrsv01.delcoelect.com
Project Engineer, Advanced Development                   
Delco Electronics Corporation           GM: c22mbt (clipcva)
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Named Pipes
Date: 2 Sep 92 15:56:15 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    .... Still, this leaves the question, where are the RFC 1001/2 equivalents
    for doing Named Pipes on TCP/UDP? Not worth the effort??

My personal opinion (which may be from way out in left field, since I've
not done any actual named-pipes applications) is based on my understanding
that Microsoft based named pipes on a Netbios-style flat namespace, with
broadcast name defense implied.  This works badly in an internetworking
environment, just like Netbios.  I think you can run at least some
named-pipes applications with a glue layer that thranslates to Netbios calls,
and that appears to be satisfying whatever demand there is...

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: Any PD based NSLOOKUPs around?
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Thu, 27 Aug 1992 02:54:36 GMT

In article <9208251609.AA29345@ftp.com> jbvb@ftp.com writes:
>
>    Does anyone know of any NSLOOKUP (Domain name server lookup command line 
>    program) that works with Packet drivers.  I'd like to spare myself (and 
>    others) the trouble of logging into a *nix system everytime I need to
>    check out MX record problems.
>
>PC/TCP for DOS (not free) includes HOST.EXE, which can generate any kind
>of DNS query, including HESOID...
>
>James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
>FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

	BW-TCP from Beame & Whiteside Software (Not free) has a complete
NSLOOKUP program. I'm also sure there are many comercial vendors which
supply an equivalent NSLOOKUP program.

Carl Beame
Beame & Whiteside Software Ltd.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: skl@wimsey.bc.ca (Samuel Lam)
Subject: Re: Anyone using Crynwr packet driver with PhoneNET
Reply-To: skl@wimsey.bc.ca (Samuel Lam)
Date: Thu, 3 Sep 1992 21:13:12 GMT

In article <Btywvq.DL2@news.larc.nasa.gov> (Daniel Koppen) writes:
>I have yet to find a way to allow the PhoneNET product and 
>NCSA's Telnet to use the same 3c503 card.

Farallon's PC PhoneNET product uses ODI drivers to drive the
network card, so if you run the ODI_PKT shim on top of this ODI
configuration you can get a concurrent Packet Driver interface
out of the ODI driver.  Then you would be able to run NCSA Telnet,
and other Packet Driver based software, concurrent with your
AppleTalk software on the same Ethernet card.

...Sam
-- 
<skl@wimsey.bc.ca>
Xref: sparky comp.protocols.tcp-ip.ibmpc:4904 news.software.readers:1707
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.protocols.tcp-ip.ibmpc,news.software.readers
Subject: Re: Trumpet Shell for FTP Software TCP stack.
Date: 26 Aug 92 16:22:24 GMT
Organization: Naval Medical Research & Development Command

In article <kemp.714325546@convex.convex.com> kemp@convex.com (Phil Kemp) writes:
>In <seant.45.0@sunfish.ratsys.com> seant@sunfish.ratsys.com (Sean D. True) writes:
>
>>In article <kemp.713806943@convex.convex.com> kemp@convex.com (Phil Kemp) writes:
>>... 
>
>[stuff deleted]
>
>
>I was going to guess that maybe the latencies are a problem except
>that I have tried your wrapper from DOS only with the PC/TCP kernel loaded
>and it doesn't work for me. I still get '599 Command Timed Out' when
>the Trumpet program goes out to the nntp host. This does not happen
>when I use the etherslip packet driver and the regular version of
>trumpet.
>
I had the same problem when I first set it up.  What solved it for me was
to use the IP number for the NNTP server instead of the FQDN.  Seems the
wrapper can't access our local DNS box because it's on a different subnet.
I do have both the DNS and the gateway IPs set in IPCUST.SYS.  I haven't
checked to see if adding gateway=xxx.xxx.xx.xx to NEWS.PRM helps or not.

>The only thing I can think of is that loading the network high is
>causing a problem. I'll try with it low and let you know what's
>happenning. 
>
My whole network is loaded high.

Mike

-- 
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@steam.uwaterloo.ca (Erick Engelke)
Subject: Re: tcp-ip library nonblocking I/O (Berkeley compatible)?
Organization: University of Waterloo
Date: Tue, 1 Sep 1992 21:40:16 GMT


I wrote:
>>Yes, with one exception.  I believe FTP's PC/TCP does not support the
>>use of select to asynchronously detect the establishment of a connection
>>on a listenning socket.  Someone will surely correct me if I'm wrong.

and James (jbvb@ftp.com) corrected it with:
>Unless the code is buggy (and inspection doesn't reveal anything obvious),
>we should report a listening socket with connections available for accept()
>as readable.

My confusion came from the fact that FTP's PC/TCP supplies two inteface
layers, one is pretty BSD-ish, the other is certainly more homegrown.
The latter has the select limitation while the BSD-ish one does not.

Before anyone interprets this apparently dual API as being a kludge,
let me explain why it exists.  Every DOS based TCP implementation has 
had to deal with the seemingly innumerable problems of fitting everything
into a TSR and dealing with DOS's memory/file services and the lack
thereof.  What does that mean?  They cannot allocate buffers on the
fly, they cannot necessarily do DOS i/o due to the re-entrancy of DOS,
and mapping tcp/ip i/o directly into the filespace (like unix does) 
is possible in part, but not fully.

So all the popular TCP systems use a low-level homegrown API to do the
real communication between user applications and the TCP/IP kernel,
but they hide this layer underneath a BSD 4.1 or 4.3-ish set of function
calls.

Many products only provide the BSD-ish layer for external developers, 
that encourages them to use only documented facilities and makes the
product look nice so the TCP author doesn't look like he had to make
the kludges that are actually so necessary.  

But in doing so, these products force TSR developers to link in 
extra bulky functions, and in the case of at least one library, 
use a malloc(), a definate no-no in tsr development!

The solution?  FTP provides their BSD environment (with source which
maps it to their internal api)  and documents their internal API too.  
That tries to make everyone happy.  

Their internal API can be called practically any time.  
Compeditors systems which only provide the BSD-ish interface 
can rarely be called during DOS i/o, and sometimes have difficulty
when called during interrupt calls.  

I've done TSRs with many of the network stacks, using BSD and
internal APIs.  Here's my advice:

	If you are developing a non-TSR: stick to the BSD interface,
	it buys you compatibility.

	If you are doing a TSR: use the lowest level interface you
	can find for each vendor's product, and be prepared to do
	a lot of debugging.  Or hire someone else to do the dirty
	work... 

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Question:  using QEMM and packet drivers simultaneously
From: hippo@sonoma.edu (Michel Davidoff)
Date: 2 Sep 92 12:57:09 PDT
Organization: Sonoma state university

In article <1992Sep2.135723.2437@tamsun.tamu.edu> sam3103@tamsun.tamu.edu (Stan McClellan) writes:
>Subject: Question:  using QEMM and packet drivers simultaneously
>From: sam3103@tamsun.tamu.edu (Stan McClellan)
>Date: 2 Sep 92 13:57:23 GMT
>
>I hope this isn't a FAQ  8}
>
>
>I am trying to configure a PC using QEMM and a packet driver (for NCSA
>Telnet).
>
>Whenever I specify the RAM command line switch for QEMM (which is supposed
>to make hi RAM available for loading TSRs, etc) I can't load the packet 
>driver properly ... the keyboard locks up.
>
>I tried loading the packet driver high, to no avail.
>
>Am I missing something here, or is it not possible to use these two
>things at the same time????
What card are you using ?
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Trumpet Shell for FTP Software TCP stack.
From: heffron@falstaff.css.beckman.com (Matt Heffron)
Date: 26 Aug 92 18:11:40 GMT
Reply-To: heffron@falstaff.css.beckman.com
Organization: Scientific Services, Beckman Instruments, Inc.

In <ADA.92Aug19160709@zip.larc.nasa.gov> ada@zip.larc.nasa.gov (Anthony Arviola) writes:

>Being a user of the 3c503 kernel of PC/TCP, I'm curious to know if the
>shell is supposed to work with that.

>As far as the generic kernel goes, I still can't get the newsx.exe to 
>work at standard dos using the bat file suggested.  What I get is a
>statement that the device is loading.  Then finally, I get a message that
>says, that the driver has been unloaded, and I'm back at the dos prompt
>again.

I've tried newsx with both the generic (ethdrv) and 3c503 board-specific
kernels.  I can read news ok under both, but, under the generic kernel when I
post I get the message:
    bsd_recv: net_read: Network unreachable: Dest. Unreachable
3 times but the post actually works.  Under the 3c503 board specific kernel
I get the same message once, then trumpet seems to hang. (The clock in upper
left of the screen stops, but mouse still tracks. 3-finger salute necessary to
reboot and get out...)

Any Ideas why the behavior is different for the different kernels??

--
Matt Heffron                      heffron@falstaff.css.beckman.com
Beckman Instruments, Inc.         voice: (714) 961-3128
2500 N. Harbor Blvd. MS X-11, Fullerton, CA 92634-3100
I don't speak for Beckman Instruments unless they say so.
Newsgroups: comp.protocols.tcp-ip.ibmpc