HDTenEightyP/NetNews huggingface dataset:
From: wrp@cyclops.micr.Virginia.EDU (Bill Pearson)
Newsgroups: comp.os.os2.networking,comp.os.os2.apps
Subject: running an icon from the command line
Date: 12 Sep 92 01:53:14 GMT
Organization: University of Virginia
Originator: wrp@cyclops.micr.Virginia.EDU


	I now have an icon that starts a dos session that will access
a Novell network and run a program over the network.  I would like to
take advantage of my ability to telnet into OS/2 to run the same
program.  But I don't know how to configure a command line program
that will: 1) run as a dos session and 2) set a bunch of dos
parameters (FILES, VERSION, etc).

	I assume that there must be a command line interface to any
ICON-ed program; how do I access it?


Bill Pearson
Newsgroups: comp.os.os2.networking
From: lohse@desy.de (Frankpeter Lohse)
Subject: Need telnet-client runing in a child process
Organization: Deutsches Elektonen Synchrotron DESY
Date: Wed, 9 Sep 1992 06:36:55 GMT

I would like to have a telnet session running in a child process. The input/
output redirection should be done by pipes. For that I need a telnet client
that uses stdin as input.
All four telnet clients from IBM's TCP/IP 1.2 seem to use direct keyboard 
access (I cannot redirect input with '<' into the session. Redirection 
into command mode works).
Has anyone any idea, how to get the telnet client running in a child 
process and to do input/output from parent process ?

Thanks in advance for help,
Frankpeter
-------------------------------------------------------------------------------
Frankpeter Lohse                      | Disclaimer :
DESY, MKI, Hamburg, FRG               | It's just me, not my organization.
lohse@vxdesy.desy.de                  |
-------------------------------------------------------------------------------
From: lopes@cogsci.ucsd.EDU (alann lopes)
Newsgroups: comp.os.os2.networking
Subject: IBM's TCP/IP 1.2.1 SLIP
Keywords: SLIP tcp/ip
Date: 10 Sep 92 05:10:17 GMT
Organization: University of California, San Diego


  So has any lucky soul been able to get SLIP working.
  The modem connection is made, although there is no
  message confirming the connection (should there be one?),
  but when I try to ftp or telnet it always times out and
  when I ping no one returns it.  Not GOOD!

  Are there any magic words that will get this thing
  going?

  On a different note -- a few days ago I posted a
  message about the horrible performance of a remote
  telnet session when the server's CPU has a high load.

  There were several subsequent posts (THANK YOU ALL!)
  explaining what the problem might be.  All seem to
  miss a couple of points (probably because I was not
  clear in my problem description):

  1) with average CPU load the performance of the remote telnet session is fine
  2) a telnet session from the loaded CPU to the outside world works fine
    
  The problem is when the loaded CPU is handling a remote telnet
  session.  It seems that when the CPU is loaded OS2/TCP/IP (or whatever) 
  does not give enough priority to the remote session resulting
  in a completely unusable remote session.  Is there any way to
  either give the remote session more cycles or limit the priority
  of the task(s) that may be using too much CPU.  Of course, one
  needs to be able to change these priorities remotely.

             Thanks all very much -- alann

   alann lopes:        alopes@ucsd.edu       -- internet
   (619) 534-7417      ALOPES@UCSD           -- bitnet
Newsgroups: comp.os.os2.networking
From: X10017@maccvm.corp.mot.com (Philippe Rameau)
Subject: Re: IBM TCP/IP and RIP protocol.
Organization: Motorola
Date: 8 Sep 1992 05:46:05 CDT


         My PS/2 is defined as a stand alone station on my backbone, I
    had experienced several problems with the TCP/IP sw, for exemple I
    have to define a static  route for each host I  want to access, in
    TCPIP/ETC/GATEWAYS file, or directly  on the command line with the
    ROUTE command. I think something  more efficient can be done, this
    is the reason why I want to share routing informations with RIP.

         And my TCP/IP sw still does not  refresh his routing internal
    table using the RIP one broadcasted by the router !.

         I tried to define my router  as the default router but no
       success, also plaied arround with the default metric in the
       LAN adapter panel (cf ifconfig command) without success, an
       other thing is that we use a subnetting mask of class C for
       class B addresses, if I use  a class B mask, I am  not able
       to reach any host on the LAN or WAN anymore.

         I won't talk about SNMP now, an other pleasant playground
       especially the SNMP traps and SNMPREQD, SNMPD.

         An other thing I am looking for is how to get the internal
      routing table downloaded to a file !!!


   Any help or idea will be wellcome......thank you.

------------------------- Original Article -------------------------
From: hamish@waikato.ac.nz
Newsgroups: comp.os.os2.networking
Subject: Re: IBM TCP/IP and RIP protocol.
Date: 8 Sep 92 16:52:49 +1200
Organization: University of Waikato, Hamilton, New Zealand

In article <7941@public.BTR.COM>, car@public.BTR.COM (Carlos Rimola-Sarti  car@b
> In article <1992Sep4.145122.10496@schbbs.mot.com> X10017@maccvm.corp.mot.com (
>>
>>     I currently run TCP/IP 1.2  with OS/2 v1.30.1, my PS/2 is connected
>>  onto an ethernet 802.3 lan with a router to the internet, as my router
>>  provides RIP routing protocol, I would like to share those information
>>  with the ROUTED.EXE which as say the manual uses the RIP protocol.
>>     Thank you for any help.
[Deleted]
>
> You can also enable the automotic starting of ROUTED (in TCPSTART.CMD) by
> runing ICAT, going to the LAN adapter screen and clickin on the box which
> says something about management of routing tables.
>

The Automatic Starting of Services options, Screen #2

> However, unless your PS/2 is acting as a router, I am not sure that ther
> is any benefit to be gained by running ROUTED.  Can anyone else provide more
> info on this?
>

You need to run routed whether you are a router or not. If you are not a
router, it will listen to the RIP info on the net provided by routers, and
re-configure your routing table on the fly. Also, if you don't run routed, the
tcp/ip (At least 1.2 did), will do strange things with respect to replying to
ICMP broadcasts, which it shouldn't do (According to our central networking
people).

--
==============================================================================
|  Hamish Marson   <h.marson@waikato.ac.nz>                             OS/2 |
|  Programmer (n/5), School of Computing and Mathematical Sciences           |
|  University of Waikato,                                                    |
|  Hamilton, New Zealand.                                                    |
|Disclaimer:  Anything said in this message is the personal opinion of the   |
|             finger hitting the keyboard & doesn't represent my employers   |
|             opinion in any way. (ie we probably don't agree)               |
==============================================================================
  Q. If Nuclear Tests are so safe, why don't the French do them under Paris?

Newsgroups: comp.os.os2.networking
From: vu@bsc.no (Nguyen Vu)
Subject: Scroll fields for X-Client (PMX) window ?
Organization: Bergen Scientific Centre, Bergen, NORWAY
Date: Mon, 14 Sep 1992 09:05:48 GMT

Hello!

Does any one know how to get a X-client window (under OS/2 2.0) with scroll
field like aixterm under AIX ?

Thanks for any hints!

Vu
Newsgroups: comp.os.os2.networking
From: backman@vaxeline.ftp.com  (Larry Backman)
Subject: Re: PC/TCP from ftp and printers...
Nntp-Software: PC/TCP NNTP
Organization: FTP Software, Inc., Wakefield, MA
Date: Mon, 14 Sep 1992 17:10:14

In article <1992Sep14.174109.841@debet.nhh.no> si0_tb90020@debet.nhh.no writes:

 >> I am running PC/TCP 1.2 from ftp Software Inc on OS/2 2.0
 >> What I am trying to do is to set up a printer under OS/2 from this piece
 >> of software, and I cannot seem to make it work.
 >> 
 >> I am able to use the lpr command from OS/2 and it works. But I would
 >> like to set up a printer icon. And be able to choose File/Print from my
 >> applications...
 >> 
 >> And if you wonder, I do have and have read TFM.
 >> 
Our product does not currently support print redirection which is the feature 
you are looking for.

This deficiency is being addressed.

Larry Backman
FTP Software
From: wrp@cyclops.micr.Virginia.EDU (Bill Pearson)
Newsgroups: comp.os.os2.networking
Subject: SMC8013 vs Novell ODI & ODINSUP
Date: 12 Sep 92 01:49:59 GMT
Organization: University of Virginia
Originator: wrp@cyclops.micr.Virginia.EDU


	I am now successfully running the OS/2 2.0 Netware requestor
and FTP Software's TCP/IP suite on an SMC8013 Ethernet board using the
SMC NORB211.EXE (version 2.11 beta) ODI drivers, ODINSUP, and the FTP
software.  At the moment, everything works.  I can run applications
off of a Novell server in a DOS window that access files on the
server.  At the same time, I can have telnet sessions and be using tar
to backup my drives.  Getting everything to work was very time
consuming, but it works now.

	I encountered the following problems:

1) The hardest part was getting the ODI drivers to work with the SMC
card.  Using int=2, port=280, mem=0xcc00, the NDIS drivers worked, it
worked under DOS with packet drivers, Netware, and NCSA telnet, but it
would not work with the OS2 netware requestor.  I kept getting the
message:

	NWD0115  Error getting connection ID 0x880F.

Changing int=10, port=340, mem=0xcc00 solved the problem.  The ODI drivers
seem to be more sensitive to something?  As soon as I changed the int/port,
the Netware requestor started working.

2) Somehow, I managed to install the Netware requestor without getting
NETX, which is required for DOS sessions.  Found it on the requestor
disk and copied it to D:\netware.

3) Unfortunately, although the requester was working, I could not get
an F: drive under a DOS session.  Stupid me, DOS_LAST_DRIVE = Z:. That
took a while to find.

3) During the process of testing the configuration, I managed to
crash OS/2 seriously (internal processing error at location ...
contact your service representative). I was able to fix this by
increasing the number of DOS_FILES to 255.

4) I was never able to get the device=dosvipx.sys and
device=dosvshll.sys to work when installed in CONFIG.SYS of a bootable
A: disk, as is described on p. 8-3 and 8-5 of the Novell Requestor
Manual.  They always caused the application to bomb when booted from
the A: drive.  I probably don't understand how they work, but I do not
know how to make a virtual disk image application that can access the
novell network.  There are a lot of errors in the Novell manual.

There it is.  It can be done.  It took me a very long time.

Bill Pearson
Newsgroups: comp.os.os2.networking
From: paula@alf.pec.co.nz (Paul Andrew)
Subject: Re: tar, NFS with IBM TCP/IP 1.2.1 - problems
Organization: Production Engineering (NZ) Ltd.
Date: Sun, 06 Sep 1992 23:30:01 GMT
Followup-To: comp.os.os2.networking
Keywords: TAR, TCPIP, OS2

In article <78934@ut-emx.uucp> dll@ccwf.cc.utexas.edu (Don Loflin) writes:
>>We do our backups by mounting the OS/2 drives on a SCO UNIX machine
>>and running TAR under UNIX.  We found that we had to reduce the buffer
>>sizes to 1024 bytes before it would work.  We didn't need to go as low
>>as 512 bytes.  It's not quick though.  We are hoping to use an OS/2
>>TAR with IBM TCP/IP's rexec or rsh as a better method for the backups.
>
>If you are looking for a TAR to use with the TCP/IP rexec or rsh, get
>the version of Gnu TAR included with the GTAK100.ZOO stuff.  It supports
>long filenames, extended attributes, and comes with a COMPRESS, which it
>can pipe its output through.
>
>The "Other" version of GNU TAR may or may not support EAs, but it does
>support long filenames, I believe.

This sounds great, although preliminary tests have been unable to
redirect the input of OS/2 TCPIP's rsh or rexec.  I try a command
under OS/2 like:

       dir /s \*.* | rsh machine -l user hd

This should display a hex dump of my OS/2 root directory on my OS/2
screen.  It does nothing.  And when I type a whole lot of stuff on the
OS/2 keyboard I get a hex dump of my key presses.  I've tried all the
options on rsh and rexec and nothing allows redirection of the input.
It's most frustrating.  So if that simple example doesn't work, how am
I going to get TAR to work ????

Is this a known bug in IBM's TCPIP ????

-- 
Paul Andrew   PaulA@hal.pec.co.nz    Production Engineering (NZ) Ltd.
Ph. +64 652 8189     (hi mom!)       P.O. Box 308, Marton, New Zealand
Newsgroups: comp.os.os2.networking
From: rovero@oc.nps.navy.mil (Josh Rovero)
Newsgroups: comp.os.os2.networking
Subject: Re: Noveel and TCP/IP together?
Date: 11 Sep 92 03:43:55 GMT
Organization: Naval Postgraduate School, Monterey CA

I run each in separate DOS windows without problems.  Not simultaneously,
but it's simple to switch between them.  Under "real" MS-DOS, you have
to reboot after a netware session to get back to PC/TCP, so OS/2 is a
definite improvement.

-- 
Josh Rovero   (rovero@oc.nps.navy.mil) | or Internet 5346p@cc.nps.navy.mil 
Department of Oceanography, Code OC/Rv |      Bitnet 5346p@NAVPGS 
Naval Postgraduate School              |              
Monterey, CA  93943   (408) 646-2084   |
From: chandoni@husc8.harvard.edu (John-Marc Chandonia, , , )
Newsgroups: comp.os.os2.networking
Subject: Re: Problems with CSD for TCPIP 1.2.1
Date: 15 Sep 92 17:19:07 GMT
Reply-To: chandoni@husc8.harvard.edu
Originator: chandoni@husc8.harvard.edu

ignacij@meishan.animal.uiuc.edu (Ignacy Misztal) writes:
> TCPIP 1.2.1 with CSD recently posted to hobbes still has some annoying
> problems:
> 1. Telnet is still a CPU hog, despite claims on the net to the contrary,

It's a little better than before.  Start pulse, then the old telnet...
you get a solid line across the top of pulse, even when telnet is
just waiting for input.  The telnet from the CSD still takes up a
lot of CPU time when it's doing something like screen updates, but
at least it doesn't suck up CPU when waiting for input.

Having just said that, I notice that this behavior isn't consistent.
In about 1 session in 10, a telnet session WILL suck up CPU time even
when idle.  Doesn't seem to depend on the remote computer, and it doesn't
change behavior after starting (you know right away if there's a problem).

JMC
-- 
chandoni@husc8.harvard.edu    | I will not yell fire in a crowded classroom
John-Marc Chandonia           | I will not yell fire in a crowded classroom
Graduate Biophysics Program   | I will not yell fire in a crowded classroom 
Harvard University            | I will not yell fire ...
Newsgroups: comp.os.os2.networking
From: mitton@dave.enet.dec.com (Dave Mitton)
Subject: Re: Pathworks
Keywords: DEC, VAX, Pathworks
Reply-To: mitton@dave.enet.dec.com (Dave Mitton)
Organization: Digital Equipment Corporation, Littleton MA
Date: Mon, 14 Sep 1992 22:16:20 GMT


In article <#btnhnl.mendi@netcom.com>, mendi@netcom.com (Greg Mendizabal) writes:
>Newsgroups: comp.os.os2.networking
>From: mendi@netcom.com (Greg Mendizabal)
>Subject: Pathworks
>Date: Thu, 10 Sep 92 06:59:55 GMT
>
...
>Anyway, what's my point?  Is anyone out there running the OS/2 version of
>Pathworks?  DEC seems to be clueless:  they don't know OS/2 v.2.0 exists and
>have no intention (apparently) of doing anything about it.  They also 
>indicate that the current version *won't work* (given the first statement,
>does the second make sense?  ;-)  )

[Disclaimer, I don't work on OS/2 network anymore, but I couldn't let
 this misinformed bashing slide, FWIW]

	Hey, why don't you learn something about OS/2 V2.0 yourself!

Digital knows as much about OS/2 as any other OEMs. It knows exactly
what is broken and what it takes to release a new and reliable product.
The changes in the way OS/2 V2.0 was released and the schism between IBM 
and Microsoft have severely hurt the way some of us can release code for
for the platform.

The reason that PATHWORKS for OS/2 was broken by OS/2 V2.0 is that
internal interfaces have changed, and what Digital needs is a new
OEM version of LAN Manager from (guess) Microsoft (who does NOT seem to be
in any hurry).

Digital has recently released a PATHWORKS for OS/2 V2.0a release with
LAN Manager V2.1 on it.  From this you can build a client, but not a
server.   I believe, you can build a server using IBM's newest LAN Server 
kit, but I'm out of my expertise area here.  

If you need information on PATHWORKS contact your local PC support
specialist, or ask on the Compuserve DECPCI forum.
Also the VMSNET.NETWORKS.DESKTOP.PATHWORKS newsgroup is monitored by a 
number of PCSG engineers.

	Dave Mitton
	Networks and Communications
	Digital Equipment Corp.

Newsgroups: comp.os.os2.networking
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: running an icon from the command line
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Tue, 15 Sep 1992 00:06:19 GMT

In article <1992Sep12.015314.9577@murdoch.acc.Virginia.EDU> wrp@cyclops.micr.Virginia.EDU (Bill Pearson) writes:
>	I now have an icon that starts a dos session that will access
>a Novell network and run a program over the network.  I would like to
>take advantage of my ability to telnet into OS/2 to run the same
>program.  But I don't know how to configure a command line program
>that will: 1) run as a dos session and 2) set a bunch of dos
>parameters (FILES, VERSION, etc).

Try the STARTD (or similar) utility, available via anonymous ftp from
ftp-os2.nmsu.edu.

-- 
Timothy F. Sipples      | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
Dept. of Econ., Univ.   | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
of Chicago, 60637       | Family Values Means a Job
Newsgroups: comp.os.os2.networking
From: vu@bsc.no (Nguyen Vu)
Subject: PMX 1.2.1.3 Fix!!
Organization: Bergen Scientific Centre, Bergen, NORWAY
Date: Mon, 14 Sep 1992 07:35:55 GMT

Hi all netters!

I've received the fixed-package for TCP/IP 1.2.1.3 (NFS, PMX included). It works
OK now, no problems with focusing or whatever on PMX.
I would like to put the PMX 1.2.1.3 to a ftp'able site since many aske for it..
Please let me know if it (the fixed-package) can be distributted freely, I'll
put it in ftp-os2......RIGHT AWAY!!


Cheers

Vu. e-mail: vu@reefe.bsc.no
Newsgroups: comp.os.os2.networking
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: Lanmanager and Lantastic
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Tue, 15 Sep 1992 00:24:30 GMT

In article <68068@hydra.gatech.EDU> bob@comlab.gatech.edu (Bob Baggerman) writes:
>>Is it possible to run Lanmanager over Lantastic ARCNet cards?
>Really the only thing necessary to run LanMan over the Lantastic ARCnet 
>cards would be an NDIS driver.  My guess would be, however, that the
>chances of that would be slim.  I don't see any incentive for Artisoft
>to do it.

I think LANtastic cards are Novell compatible -- anyone have details
on this?

-- 
Timothy F. Sipples      | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
Dept. of Econ., Univ.   | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
of Chicago, 60637       | Family Values Means a Job
Newsgroups: comp.os.os2.networking,comp.os.os2.misc
From: zxmkx01@mailserv.zdv.uni-tuebingen.de (Andreas Kerger)
Subject: OS2/2.0 & Novell
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Mon, 7 Sep 1992 14:13:21 GMT

Hi,
i'am in trouble with OS2/2.0 and Novell.
trying to connect to the file-server every
thing works fine. if i want make a login
i cannot access the login-drive. this is
because everey dos session contains (due to dossettings)
an entry for last drive. net3/5 do not allow this
and therefore no access is possible.
has anobody an idea how to avoid or solve the problem ?

thank very much
andreas
--
------------------------------------------
Andreas Kerger  | Engelfriedshalde 22    |
7400 Tuebingen  | Germany                |
From: dbs@hprnd.rose.hp.com (Dave Sheehy)
Date: Fri, 11 Sep 1992 23:37:51 GMT
Subject: Re: OS/2 2.0 + IBM TCP/IP 1.2.1 + EISA + ethernet = possible?
Organization: HP Roseville Networks Division
Newsgroups: comp.os.os2.networking



>Please reply ASAP if you know of a card which will work!

The HP27248 EISA card will work. It's not a bus master tho'. You need the
latest and greatest driver too. Call Kittur Nagesh at (916) 785-5165.

Dave Sheehy
-- 
Newsgroups: comp.os.os2,comp.os.os2.misc,comp.os.os2.apps,comp.os.os2.programmer,comp.os.os2.advocacy
From: ctwilson@rock.concert.net (Charles T Wilson -- Personal Account)
Subject: Re: IS IBM UK STILL IN THE STONE AGE???
Summary: none intended, just commenting on above
Organization: CONCERT-CONNECT -- Public Access UNIX
Date: Tue, 8 Sep 1992 02:19:53 GMT

I've just started reading this group, and find that I'm not alone with my
OS/2 2.0 problems.  I too had the video problems on an AST with SVGA..IBM
tech support sent the same hand-labled fix to me.  I must say that I am 
much happier with the AST's native capabilities (IBM suggested first that I 
change all references to svga to vga in config.sys...blechhhh!!!).  I was
unable, however, to get any assurances that the new bhsvga.dll would be
standard in OS/2 (sigh).  Like an earlier poster, I have also had OS/2 just
seemingly decide it can't find anything any more (the os2char.dll paradox)
even though all config files are in seemingly perfect order.  To the posters
who suggested more than chkdsk: no reported errors from both.  To whoever 
suggested HPFS:  not exactly sure, but I don't think that would help me. 
I have to have at least one FAT partition for reasons I can't explain here.
I also have problems with NETWARE (might be NW's fault) communicating as
it should during shutdown..that is to say, unless NETWARE times out, trying
shutdown has no effect.  It's close 'em all down by hand time usually.  

Now, before all of the blowtorches come out, I want to say that I am making
an honest effort to live with this stuff, and that IBM did come clean with
the driver patch.  I do, however, think that it's a shame that a product 
heralded by IBM so loudly should come unglued in the ways that it does (I'm
mainly referring to the boot failures).  I hope this problem gets at least
*some* attention from IBM.

Oh yeah, to the poster who said that NT was originally going to be named 
OS/2 3.0, I think MS owns the rights to the name "OS/2 3.0".  This is 
further supported by a reply from good (?!?) ole bgates@microsoft.com
to a fellow employee that NT will be renamed OS/2 3.0 at some point 
(not exactly how he put it, but this is the gist).

Tom Wilson
ctwilson@rock.concert.net
sasctw@duckhead.unx.sas.com   (certainly *NOT* a SAS spokesperson)

Newsgroups: comp.os.os2,comp.os.os2.misc,comp.os.os2.networking
From: Zak.Smith <Zak.Smith@mixcom.mixcom.com>
Subject: Lantastic/Z Dos Box under OS/2
Organization: Milwaukee Internet Xchange BBS, Milwaukee, WI U.S.A.
Distribution: usa
Date: Mon, 07 Sep 1992 02:13:12 GMT


 Hello..

 I am trying to get Lantastic/Z working in a VDM under OS/2 2.0... I have
tried the Parallel port setup with no success, but I thought I would be able
to get the serial port version working..  I have it set on COM3 on the OS2
machine..  here is my COM.SYS line ..
device=d:\os2\com.sys (3,3E8,5,I,)
When I load the drivers for lantastic/Z, everything appears to be going OK
until I try NET LOGIN \\franks_at user
where it says "invalid function number"

I have tried both the COM_HW and COM_HOLD settings, and HW_TIMER settings.. 
I realize that I will probably only be able to run one of these VDMs if any,
and that is ok..
 
 BTW- I'm using a 386-sx-16, 8 megs..  performance doesn't seem to be a
problem..
 
 Please respond by mail..
 
 Thanks, 
          Zak Smith
 zak.smith@mixcom.com

-- 
Xref: sparky comp.os.os2:328 comp.os.os2.misc:30021