HDTenEightyP/NetNews huggingface dataset:
Organization: Johannes Kepler University Linz - Computing Center
Date: Saturday, 4 Apr 1992 14:56:46 CDT
From: <K3006E7@ALIJKU11.BITNET>
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
Subject: Question: installing NCSA

I wish to use the NCSA v2.3.03 FTP and TELNET package on our
IBM PC.  I am having very much trouble getting it to work.
Right now, our hardware is:
           "4-Dimension Quick BROM Version 6.0
            Ether Board 16 V1.31 200-5009A"
which is hooked up to the ethernet.
In the config.sys, IPCUST.SYS and IFCUST.SYS are loaded.  In
the autoexec.bat, the commands:
               NE2000.com 0x60 0x3 0x300
               ETHDRV
I think these are old "FTP Software"  that was put into our
hard-disk when the local administrator hooked up our pc to
the network.  Unfortunatly, he left absolutely no documentation
behind.
In anycase, we use the pc mostly to log onto to the local system
running VM/XA SP release 2.1.  But the trouble starts when I try
to log directly to other machines with the old "FTP Software" TN
command, such as archie at Rutgers or McGill, which do not run
VM-style operating systems.
I therefore would like to install NCSA from scratch, and learn to
configure it correctly.  If anyone could point me in the right
direction as to literature, or installation software, I would
greatly appreciate it|  I need information such as:
     what is this IPCUST.SYS and IFCUST.SYS, is this
     necessary for the NCSA telnet?
     which drivers should I use for our Ether card as
     stated above?  and what are the options I should
     try (interrupt levels, etc.)?
     Is there any software out there that does this
     automatically in regards to installation?
     etc, etc

Any and all information would be greatly appreciated.  I prefer
personal e-mail since I suspect these questions are probably
irritatingly juvenile for most readers.  But if you feel it is
of general interest, I will look forward to your followup posts.
Thank you.
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: gjc@loki.Stanford.edu (George J. Chen)
Subject: NCSA Telnet w/ SLIP8250
Organization: Stanford University
Date: Fri, 10 Apr 92 05:41:16 GMT

Has anyone gotten the above combination of software to work together?
Does anyone know it is impossible?  Thanks!

George

--
George J. Chen
Internet: gjc@loki.stanford.edu    | UUCP:  ..uunet!gjc%loki.stanford.edu
Bitnet:   gjc%loki@forsythe.bitnet | SPAN:  STAR::"gjc@loki.stanford.edu"
From: olle@edvina.se ("Olle E. Johansson")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: SLIP or PPP and modem dialing question
Date: 16 Apr 92 11:02:31 GMT
Reply-To: olle@edvina.se
Organization: The Internet
X-Unparsable-Date: Thu, 16 Apr 92 09:14:58 DST


    The server machine will usually be accessed via telephone.
    The MS-DOS client needs to automatically dial through a
    modem, then start a SLIP or PPP session.
    
    This must be done without human intervention. (It's a
    financial application that will be used by bankers
    and such, not engineers.)
    
...    
    Dean Roth

FTP Software's SLP16550 and PPP16550 packet drivers supports
a yet undocumented feature in the coming packet driver specification,
where you can load the packet driver and the PC/TCP Kernel,
then put the packet driver in raw mode and do the dialing and
login by yourself. The PC/TCP application COMSCRPT can do
this in the PC/TCP generic ethernet product that is shipped
today.

Call FTP Software, tech support, for specifications and help!
Their phone number is 617 246 0900.

Regards,
Olle

-------------------- Olle E. Johansson ---------------------
Edvina Software                        Ph. +46 8 83 61 10
P.O. Box 1513, S-171 29 Solna, Sweden  Fax +46 8 83 61 11
------------------------------------------------------------
May all american PC:s be delivered with a Swedish keyboard!
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: bvs@nrc.com (Bill Versteeg)
Subject: Re: PKTMUX issues
Organization: VerSteeg CodeWorks 
Date: Sun, 5 Apr 1992 22:43:04 GMT

>
>   Is there any inherent reason why it can't be made to work if the
>   different TCP/IP stacks have different IP addresses?  Admittedly that's
>   wasteful of addresses, but would it work?
>
>Interesting question.
>
>I can't think of any other problems - but I haven't given the question
>much thought yet.
>		- john romkey			Epilogue Technology


I am working on something similiar to this in a Unix space.
I am trying to us NIT on a SUN to run a second IP stack to
prototype an embedded systems SNMP agent. (NIT is a way to glom
onto the ethernet driver from a user process)

The only other problems I can think of relate to an incoming
packet on stack1 with stack2s IP address. Depending on whether or
not stack 1 is a router, and whether the code is worth a damn,
it may cause problems.

Some routers will "forward" the packet and send a ICMP redirect. This
"forwarding" would be hairy. I could see a path by which it forwarded
the packet to itself over and over in a tight loop. 

I could also imagine some configurations in which stack1 would send
a ICMP dest unreachable message. This would probably confuse the
originating host mightily.


The host requirements document states that a host that receives a mis-directed
packet should silently ignore it. This would be exactly what was required here.


You also must realize that many of the PC based packages are really
designed to be host-only implementations. Expecting them to conform to
router requirements documents may be asking for trouble.


So, if we talk about PCs as host-only stacks, there is no problem.
When we talk about routers/hosts, we may be hitting some grey areas.

ARP is a no-brainer, both stacks get the packet. They would both get it anyway.

Bill VerSteeg
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re: PKTMUX issues
Organization: University of Waterloo
Date: Mon, 6 Apr 1992 04:02:09 GMT

jrd@cc.usu.edu writes:
>	The ultimate solution to running multiple TCP/IP (generic terminology)
>stacks in parallel over the same board is:
>
>	put a double ended TCP/IP stack between the board and all of the apps.
>
>On the bottom that constitutes one stack talking to the Packet Driver/NDIS/ODI
>multiplexer. On the top packets are rebuild from the incoming ones, port
>numbers are reassigned, checksums fixed etc and then the rebuilt packets are
>sent up to the application as if brand new. Outgoing pkts get the same
>treatment of "re-porting and re-sequencing." This is something like a gateway.

PKTMUX does this when necessary, but only then.  And doing so can be a
cause for software failure. 

There are problems because some protocols first allocate
a port and then send that port number over an existing connection to
say, "hey, use this port".  Examples of this include FTP and BSD
originated stuff such as TALK.  None of these protocols will work if you
start tamperring with the protocols.


Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
From: catone@drachma.wharton.upenn.edu (Tony Catone)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Help with FTP Inc. Libs
Date: 16 Apr 92 20:21:51 GMT
Article-I.D.: drachma.CATONE.92Apr16162151
Organization: University of Pennsylvania
In-reply-to: books@fsunuc.physics.fsu.edu's message of 1 Apr 92 21:02:28 GMT

In article <1992Apr1.160228.27615@mailer.cc.fsu.edu> books@fsunuc.physics.fsu.edu (Roger Books) writes:

This won't help if you are married to the FTP Inc stuff, but we've had
very good success with the WATTCP library and Borland C++ 3.0.  The libs
are free, the doc is $40, it is well worth it.  Very easy to use.


- Tony
  catone@dmark.wharton.upenn.edu
From: jrd@cc.usu.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Problems with Kermit 3.11 & IPX
Date: 14 Apr 92 13:31:54 MDT
Organization: Utah State University

In article <1992Apr14.182459.485@uwm.edu>, aoelked@kirk.msoe.edu writes:
>	<parts removed> 
> It appears that the WD8003E packet driver just clobbers the IPX driver, but
> Kermit can work with it just fine.  The 8003pkdr from SMC works fine with IPX
> and NCSA telnet works, but when Kermit attempts to connect
> to the host, it is able to find the packet driver, 
> but unable to find the host.  
-----------
	I've commented on this a couple of times, so here it is once more:
The SMC "Packet Driver" is not what you think it is. It appears to accept 
only a very narrow range of packet TYPEs. My recommendation has been to
put that item back where you found it and use the Crynwr Collection
Packet Driver for the board (as I do here).
	Joe D.
From: u251016@hnykun11.urc.kun.nl (Niek Veldhuis)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Reverse Video and CUTCP Telnet
Date: 15 Apr 92 08:30:33 GMT
Organization: Department of Theology. Catholic University of Nijmegen, The Netherlands

This week I tried to contact the KUBgids (Campus Information System
of the Catholic University Brabant, The Netherlands), using Clarkson
University Telnet. Everything works fine, except for the 'reverse
video mode' which is used by this system in the main menu, to indicate 
the place of the cursor. The system manager of KUBgids wrote me that they
use another Telnet (by FTPinc.), and he suggested that my Clarkson's Telnet
probably filters out the pertinent escape sequence (ECS[7m). The escape
sequence for 'bold,' however, functions all right.
Can anybody tell me what is going on, and how I can handle this?

Thanks!

Niek Veldhuis
Department of Theology
Catholic University of Nijmegen (The Netherlands)
u251016@hnykun11.urc.kun.nl
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: pfarrell@gmuvax2.gmu.edu (Pat Farrell)
Subject: Re: Win 3.1 and FTP Softwares progs
Organization: George Mason University, Fairfax, Va.
Date: Sat, 11 Apr 1992 14:43:02 GMT

In <4884@naucse.cse.nau.edu> wew@naucse.cse.nau.edu (Bill Wilson) writes:
>Has anyone tried running FTP Software's programs under Windows 3.1
>with FTP's 386 enhanced mode setup?

I've successfully used FTP's PCTCP 2.04 under Win3.1.
I even got a Gupta SQLWindows application to call an Oracle
database using FTP's software over token ring. (don't ask why
:-)!

No problems so far, but I only got 3.1 last monday (retail,
shrink wrapped.)


Pat Farrell,      Grad Student                       pfarrell@cs.gmu.edu
Department of Computer Science, George Mason University, Fairfax, VA
#include standard.disclaimer
From: glazer@ohstpy.mps.ohio-state.edu (Jon Glazer)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NCSA TCP/IP Serious Errors
Date: 16 Apr 92 15:27:08 GMT

We are using a variety of NCSA based programs (WINQVT/NET, CUTCP, FTPBIN etc..)
and are having a problem connecting to SUN boxes.  When trying to connect with
anything but WINQVT, we get a blank screen for a few minutes then it finally
connects.  With WINQVT, there is still a delay but the server window reports

"Packet Recieved for Invalid Port - Reset Send"

After this message, we are able to connect to that sun box without any
problems.

We have no problems connecting to HPs, SCO, XINIX, AIX or most any other
flavors of unix out there (also ULTRIX and VMS with TCP/IP).

Does anyone have any solutions to this?  I have no problems with the suns when
telneting from one sun to another or from another box to a sun or from a
different PC application using a different protocol stack (Lan Workplace or FTP
etc...).

Thanks,
Jon
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: anthony@csd4.csd.uwm.edu (Anthony J Stieber)
Subject: Re: AHHK! Wattcp and Cutcp questions
Organization: Computing Services Division, University of Wisconsin - Milwaukee
Date: Fri, 17 Apr 1992 05:01:21 GMT

In article <1992Apr16.043608.20876@muddcs.claremont.edu> ileicht@jarthur.claremont.edu (Spiff) writes:
>The disadvantage to FTPing it first to my unix account then to my
>hard disk is that 1. I have a limited quota on the UNIX system..
>and two.. that doubles the transfer time. Then again.. no system is

Or you could use proxy ftp.  This allows files to be transfered
from one system to another, while the ftp client runs on a
third system.  See the ftp man page.

Also consider trying out the latest version of NCSA Telnet, available
at ftp.ncsa.uiuc.edu
--
<-:(= Anthony Stieber	anthony@csd4.csd.uwm.edu   uwm!uwmcsd4!anthony
Xref: sparky comp.protocols.tcp-ip.ibmpc:3022 comp.protocols.tcp-ip:2544
From: catone@drachma.wharton.upenn.edu (Tony Catone)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
Subject: Re: Question: installing NCSA
Date: 16 Apr 92 20:05:02 GMT
Article-I.D.: drachma.CATONE.92Apr16160502
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: University of Pennsylvania
In-reply-to: K3006E7@ALIJKU11.BITNET's message of 4 Apr 92 19:56:46 GMT

In article <92095.145647K3006E7@ALIJKU11.BITNET> K3006E7@ALIJKU11.BITNET writes:
   In the config.sys, IPCUST.SYS and IFCUST.SYS are loaded.  In
   the autoexec.bat, the commands:
		  NE2000.com 0x60 0x3 0x300
		  ETHDRV
   I think these are old "FTP Software"  that was put into our
   hard-disk when the local administrator hooked up our pc to
   the network.  Unfortunatly, he left absolutely no documentation
   behind.

You can order the doc from FTP Inc if you want it.  Ipcust.sys and
ifcust.sys are two device drivers that FTP Inc's PC/TCP package (and
Interdrive) use to hold IP numbers and other site configuration.
Ethdrv is the generic ethernet kernel for PC/TCP.  You can buy
versions of PC/TCP either for use with a specific ethernet card, or
for any ethernet card that supports a packet driver (FTP Inc created
and maintains the packet driver spec).  The latter version requires
ethdrv to be loaded before PC/TCP will successfully run.  The
advantage is that one can unload ethdrv and free memory for other
applications with the "inet unload" command.

If you get the documentation, you will find that PC/TCP does vt100,
vt2xx, vt3xx and tn3270 emulation.  If you are having problems, you
are using the wrong commands.  There is a lot not to like about
PC/TCP, but it certainly does connect up to archie systems, standard
unix boxes, etc.  with very little difficulty.

That said, we used to use PC/TCP almost exclusively, but now have
switched to NCSA Telnet as our standard telnet/ftp application.  NCSA
has a nicer interface, more flexibility, and new versions and features
appear with more speed than PC/TCP.  In addition, the advantages of
having source code available are obvious.  There are several versions
of the NCSA doc for 2.3, but none are really great (though all are
much better than the 2.2 doc).  I have been working in my spare time
to clean up the doc and fix some of its errors, give it a real table
of contents and an index, etc (amusingly enough, I use the same
editor/formatter package FTP Inc used to create their 2.05 doc).  If
anyone is interested in this, drop me a note and I will post to the
group when it is done (give it two to three weeks, I think, the end of
the semester is pretty busy).

Commenting out the line in the autoexec.bat that loads ethdrv will
solve your problem.  You can leave the ipcust.sys and ifcust.sys lines
in the config.sys if you want to be able to run PC/TCP also (just load
and unload the generic kernel as you need), but they take up a few K
of memory and you may as well remove them if you just want NCSA
(that's what we do).  Drop a line if you need more specifics.


- Tony
  catone@dmark.wharton.upenn.edu
Xref: sparky comp.protocols.tcp-ip.ibmpc:2950 comp.sys.ibm.pc.hardware:13619
From: keithl@loop.uucp (Keith Lofstrom;;;520-1993)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc.hardware
Subject: Flakey WD8003 detects nonexistent collisions
Date: 11 Apr 92 06:00:38 GMT
Article-I.D.: loop.1992Apr11.060038.12275
Organization: KLIC

I just replaced a WD8003 board - the card got slower and slower moving data;
the oscilloscope I had on the cable was showing the packets further and further
apart.  The replacement card works fine.  My suspicion is that the threshold
level for "collision detect" on the transceiver chip was going flakey, and
indicating collisions where none were really happening, and the backoff
algorithm was kicking in inappropriately.

Since I'm using cheapernet, another possible explanation is oxidation on the
inner conductor of the BNC connector - cheap plating.  I did an ohmmeter
check to show this wasn't the case for me, but if it had been that way, the
extra resistance might have raised the apparent transmit signal level and
the card would detect collision voltage levels.

Why bother you folks with it?   Well, a little while back someone else posted
a message about a similar problem with a WD8003, which was attributed to
software.  I might suggest trying a different card.  The date code on the
National DP8392AN transceiver chip on the card is 8824, just in case this
is a problem with the lot. 

-- 
Keith Lofstrom       keithl@loop.klic.rain.com     Voice (503)-520-1993
KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon"
Design Contracting in Bipolar and CMOS - Analog, Digital, and Power ICs
From: Z00EJR01@AWIUNI11.BITNET (Ewald Jenisch)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: NOS <-> Cisco with PPP -- anyone got it running?
Date: 16 Apr 92 21:42:03 GMT
Organization: Vienna University Computer Center
X-Unparsable-Date: Thu, 16 Apr 92 17:24:11 MEZ

Hi folks,

Has anybody out there successfully connected a KA9Q-nos to a cisco box
using PPP? (or even SLIP)

Which version of NOS do you use?
Where did you get it from?
Pre-compiled?

and of course

how does your autoexec.net look like for this to work?


Thanks in advance for any hints,

-ewald


Ewald Jenisch                      |  E-mail: jenisch@univie.ac.at (Internet)
Vienna University Computer Center  |          z00ejr01@awiuni11.bitnet (Bitnet)
Universitaetsstrasse 7             |  Tel: +43 (222) 43-61-11 x251  Fax x170
A-1010 Vienna, Austria             |  NIC-Handle: EJ63
From: detlev@tpki.toppoint.de (Detlev Habicht)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: WANTED: Packet Driver for ACER 5220A
Summary: Packet Driver for ACER 5220A
Keywords: packet driver, acer, 5220a
Date: 6 Apr 92 11:35:29 GMT
Organization: Toppoint Mailbox e.V.

Hi,
a need a packet driver for a ACER 5220A ethernet card.
Any ideas?
Thanx
Detlev
-- 
+----------------------------------------------------------+
|   Detlev Habicht                 detlev@tpki.toppoint.de |
|   OFFICE: Neuwirth & Bick GmbH   VOICE: +49 5042 80331   |
|           Kommunikationstechnik  FAX:   +49 5042 80354   |
From: chee@UHUNIX.UHCC.HAWAII.EDU (Brian Chee)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: WinQVTnet & 3.1 No Worky!
Date: 7 Apr 92 20:45:18 GMT
Organization: The Internet

Try setting up windows 3.1 with the "setup/a" option to get into the admin
mode....also you need the newest version of the shell, 3.26 I think it was.
I found it on ftp.is.sandy.novell.com

/brian chee

~~~~~THESE ARE MY OPINIONS ONLY, an answer is only a good guess
University of Hawaii, Manoa              Microcomputer Services 
Brian Chee CNE/CNI, MicroComputer Lan Specialist
chee@uhunix.uhcc.hawaii.edu                      (808) 956-8316
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: fealon@nadia.stgt.sub.org (Frank Fuchs)
Subject: Re: IBM LAN Services over TCP/IP (was Pathworks for OS/2 v2, for OS/2
Organization: Foxware Systemhaus GmbH
Date: Tue, 14 Apr 1992 08:57:52 GMT

In article <53895@hydra.gatech.EDU> bob@comlab.gatech.edu (Bob Baggerman) writes:
>>>I was wondering if it is possible to get IBM's LAN services to use IBM's
>>>TCP/IP package to send out LAN Manager requests using the TCP/IP protocol
>>>as a transport.
>
>I'm not particularly glib when it comes to IBM LAN Server but if I remember
>correctly it is derived from MS LAN Manager.  If LAN Server also operates
>over a NetBIOS driver you ought to be choose from a number of different 
>NetBIOS protocols and install it on your server and clients.  In this case
>there is no need for tunneling.  LAN Manager calls this transport protocol
>independence.  8-)

MS Lan Manager 2.1 can be used with TCP/IP protocoll. Runs fine on my
OS/2 1.30.2 machine.
Maybe you should try this protocoll on top of LAN Server. The problem is,
LAN Man 2.1 doesn't run on top of OS/2 2.0 (because of HPFS386).
-- Frank

-- 
Frank Fuchs, fealon@fealon.stgt.sub.org
Foxware Systemhaus GmbH, Kolumbusstr. 2, 7032 Sindelfingen
phone: 49 7031 875005, fax: 49 7031 83180 (both change in May/June '92)
From: diro@edison.phone.North.DE (Dirk Rode)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Problems with Interactive UNIX and WD8013EBT
Date: 9 Apr 92 18:35:48 +0200

Shalom,

 we use a 386 with the new AMI BIOS and an 33 Mhz AMD Prozessor.
Then we have a Western Digital WD8013 EBT Card inside. I have the
following problem:

 - on the Net (shown by etherfind on a SUN) I get packages with
   Type 86b <Ethernet Adapter Address in Hex> -> ff:1:ff:1:ff:1
or X.75 Internet

 - the system makes a kernel Panic after about 5 minutes ...

 The problem comes up only with this configuration. Can somebody help me?

Thanks in advance
          Dirk

-- 
*  Dipl.Inform. Dirk Rode * diro@edison.Phone.North.DE                 *
*  Zwischenahner Str. 64  *                                            *
*  2910 Howiek            * Tel: ????? ????  ask me if you want to know*
*   ... Ein ganzer Kerl ...                                            *
*                       ... Dank Chappi :-))                           *
From: gts@MICA.BERKELEY.EDU (Greg Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re:  IBM LAN Services over TCP/IP (was Pathworks for OS/2 v2, for OS/2
Date: 10 Apr 92 22:05:41 GMT
Distribution: world
Organization: The Internet

= From pcip-request@louie.udel.edu Thu Apr  9 16:48:49 1992
= From: Satish Movva <micro-heart-of-gold.mit.edu!news.bbn.com!usc!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!uicvm.uic.edu!u37127@bloom-beacon.mit.edu>
= Organization: University of Illinois at Chicago
= Subject: IBM LAN Services over TCP/IP
= The technology is available, as Novell Netware 3.11 already does it.
= Under novell the IPX packet is enclosed in IP packets to be sent across a
= pure IP network.  Novell calls this IPTUNNELing.  It supports both
= server to server (peer) tunneling as well as client to server tunelling.
= I dont know if they have IP tunneling for OS/2 clients yet.

There is no need for new technology here.   Netbios over TCP/IP has existed
since 1986 and was standardized as RFC 1001/1002 in 1987 (?).  Several vendors
have it for OS/2.  We do not have much OS/2 here (yet?) but we have been using
Netbios (PC LAN) over TCP/IP since 1986.

Gregory T Small                                      1-510-642-5979
Personal Computer Networking & Communications        gts@violet.Berkeley.EDU
Workstation Software Support Group, IST/WSS          216 Evans Hall
University of California, Berkeley, Ca 94720         1-510-643-5385 (Fax)

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ileicht@jarthur.claremont.edu (Spiff)
Subject: Re: AHHK! Wattcp and Cutcp questions
Organization: Harvey Mudd College, Claremont, CA 91711
Date: Thu, 16 Apr 1992 04:36:08 GMT

KA9Q Disadvantages... as I recall it did handle ANSI correctly.. but
it had some problems with the arrow keys.. etc... more so debilitating
was its lack of a scroll back buffer.. and I don't think that Ka9q
handled 50 line mode. The Cutcp also has techtronix emulation which is
nice along with a number of other things.

The disadvantage to FTPing it first to my unix account then to my
hard disk is that 1. I have a limited quota on the UNIX system..
and two.. that doubles the transfer time. Then again.. no system is
perfect.

My greatest concern with cutcps FTP is the fact that once a user has
logged into my site they could either on purpose or inadvertently delete
most of my hard disk.

Is it possible through cutcp or some other program to restrict 
read/write access on my hard disk? I am using norton's disk monitor
but, if a person tries to overwrite a file or delete a file.. even
if it is legit... then it pops up a box asking me if I want to allow
the disk operation. If I am not there this has the unfortuanate
consequence of effectively locking up the system till I return.

Newsgroups: comp.protocols.tcp-ip.ibmpc