HDTenEightyP/NetNews huggingface dataset:
From: sveini@mack.uit.no (Svein-Ivar Lillehaug)
Subject: Drivers above 640K in DOS sessions???
Organization: University of Tromsoe
Date: Thu, 23 Jul 1992 10:44:49 GMT

Is it possible to define drivers (devicehigh, load high) and TSR
programs (load high) in the memory above 640k when defining a DOS
session/box? 

It sems to be impossible to do definisions like this in the 
"DOS/session/DOS_device/value" field as this field only allows
statements as "C:\drivers\......". Another option is to define the
drivers in a .BAT file that one can start after the DOS session is 
up running. BUT: this seems to be sort of silly. It must be possible
to do this in some way through OS/2.

The possibility to do the definitions in the config file is not
acceptable as I want thes special drivers to be known only to that
special DOS-session.


Thanks in advance,
Svein-Ivar
 
Newsgroups: comp.os.os2.networking,comp.sys.novell
From: mwh45279@uxa.cso.uiuc.edu (Marc Henkel)
Subject: PD or Shareware FTP software available for OS/2?
Organization: University of Illinois at Urbana
Date: Tue, 21 Jul 1992 21:55:26 GMT

Hello there,

I apologize if this is a FAQ, but here goes....

Is there any FTP software available in the public domain,
whether shareware or freeware, that allows an FTP session
in OS/2?  We are currently running OS/2 v1.3 and Microsoft
LANManager 2.1.  Is there any way to run an FTP daemon so
that we could log into our servers from a UNIX box over 
TCP/IP?  I guess IBM's TCP/IP 1.2.1 is an option, but since
I am cheap, anything PD would be most desireable.  Thanks for
any enlightenment.

Marc Henkel
University of Illinois at Champaign-Urbana
mwh45279@uxa.cso.uiuc.edu

Newsgroups: comp.os.os2.networking
From: mcover@magnus.acs.ohio-state.edu (Mark Coverdill)
Subject: Re: NCSA Telnet
Organization: The Ohio State University
Date: Thu, 30 Jul 1992 13:35:25 GMT

In article <1992Jul28.224323.17395@unixg.ubc.ca> flynn@ucs.ubc.ca (Frank Flynn) writes:
>Keywords:NCSA Telent FTP
>
>This is probably a FAQ, but has anoyone managed to get
>NCSA TELNET and or FTP to work and if so how? 
>

Yes, the way I do it is to load the packet driver upon invocation of
telnet or ftp.  You probably have typically loaded the packet driver
from the autoexec.bat file.  Move this command line to the telnet.bat
and ftp.bat files in the NCSA subdirectory.  Now after opening a DOS
seesion the driver will not be loaded until you actually need it.

The one minor(major?) annoyance with this arrangement is you can only
telnet or ftp in one DOS session at a time.  Any attempt to open
another DOS session and telnet will cause a lockup because the packet
drivers will contend.  Since NCSA telnet allows multiple sessions
itself I don't think its a big deal. Email if need actual copies of
the .bat files.

Mark


-- 
Mark Coverdill                                 The Ohio State University
Internet: markc+@osu.edu                              Columbus, Ohio
Newsgroups: comp.os.os2.networking
From: wse@rio70.snibln.de (Willi Engels)
Subject: os/2 and tcp/ip 1.2.1 wd8003e = system stopped (HELP???)
Summary: system crash
Date: Fri, 31 Jul 1992 15:42:49 GMT
Reply-To: engels.bln@sni.de (Wilhelm Engels)
Organization: Siemens Nixdorf Info.Sys. AG, Paderborn, Germany
Keywords: os2 tcp/ip wd8003e crash

hi,

subject nearly tell's the whole story.
i have installed the new kernel, new filesystem, got the new ndis 
driver from the ibm bbs, checked my config.sys 10 times and still.
os/2 is coming up, configuration for tcp/ip is successfull,
startup starts the tcp/ip processes (none).
and then i start ping.
ping own system works fine 
but ping (rest of the world):
(i've a german version, so i have to translate back to english)
there was a internal processing error at
memoryaddress ##0160:ff64ae0 - 000d:aae0
60002,9084

048600b4
internal revision 6.307 92/03/01
system stopped. blah blah

i`ve tried to get help via our distributor but ...
ibm helpdesk in germany was nice but ...

any idea what i`m doing wrong ???

more information needed:

system is a 486 25 mhz, 16 mb, esdi drive, vga, 2 coms, 1lpt, 
wd8003e irq 5, ioaddr 0x240, membase 0xc8000
(works fine under dos and unix)

any help (even a flame(rtfm)) is welcome.

thanx 1e6
willi
--
Wilhelm Engels       | S iemens             | EUnet: engels.bln@sni.de
Gustav-Meyer Allee 1 | N ixdorf             | USA  : engels.bln@sni-usa.com 
FRG 1 Berlin 65      | I nformation Systems | Compuserve: 100064,644
-----------------------------------------------------------------------------
Newsgroups: comp.os.os2.networking
From: cro@socrates.ed.asu.edu (C. R. Oldham)
Subject: Good TP ethernet card for use w/IBM TCP/IP 1.2.1?
Keywords: ethernet os/2 ibm tcp/ip 1.2.1 card
Organization: North Central Association, Commission on Schools
Date: Wed, 22 Jul 1992 16:02:58 GMT

Just got IBM's TCP/IP 1.2.1 up and running and I'm quite pleased so far.
There are nits to pick--hopefully they will be fixed soon.

I'm getting new machines in a couple of days, however, and I'd like
recommendations regarding ethernet cards.  I've got a 3com 3c503 TP
in my 386 right now--throughput seems very slow.  Is this normal?  For now
I was chalking it up to the fact that I've only got 8 Mb of Ram.

IBM's TCP/IP distribution contains drivers only for a few cards.  Is it
reasonable to expect that vendors will have NDIS drivers for OS/2 by now?
Are they hard to get?  Are they buggy?

When I select a new card should I choose an 8 bit or a 16 bit?  I've
heard people say that it makes a world of difference, and it makes no
difference.  Which is true?

Net.wisdom on these topics is appreciated.

Thanks!

Charles R. (C. R.) Oldham | North Central Association, Commission on Schools
cro@socrates.ed.asu.edu or| Arizona State University, Tempe, AZ 85287-3011
aocro@acvax.inre.asu.edu  | 602/965-8700:800/525-9517 | #include <disclaimer.h>
"For the Lord is a great God, and a great King above all gods..." Psalm 95:3
From: brabo@busadm1.cba.hawaii.edu (Jan De Ryck)
Newsgroups: comp.os.os2.networking
Subject: odi in dos session
Summary: bnetx reports wrong dos version
Keywords: odi, bnetx
Date: 22 Jul 92 22:58:15 GMT
Organization: College Business Administration, University of Hawaii

I'm trying to get the ODI shells to run in a full screen DOS session under 
OS2. The machine is an IBM model 56 SLC. The adapter is an SMC Elite Ethernet
/A. Everything loads fine, except for bnetx, which reports 
- not running on dos 3.0 through 5.0.

Is there a way to find out which version of dos is being reported by OS2?
I tried setting the version for bnetx explicitly to 5 in the DOS session 
setup, but to no avail.

If this is a stupid question, I'm sorry. I'm brand new to OS2, and the 
written documentation is not exactly great.

/Jan DE RYCK
Systems Engineer, College of Business Administration, Univ. of Hawaii
Newsgroups: comp.os.os2.networking
From: thyerj@uncg.edu (Jonathan S. Thyer)
Subject: OS/2, Western Digital Card and Novell Net..
Organization: University of North Carolina at Greensboro
Date: Thu, 30 Jul 1992 21:40:07 GMT

I have just installed OS/2 on a 486 machine here.  The system is connected 
to a Novell net running Ethernet.  From what my OS/2 docs say, this 
operating system is supposed to be network aware?!  How do I get it to talk 
to the net?  Do Novell supply some standard drivers or do I have to get them 
elsewhere?  Please be kind as I am new to OS/2.
Reply by email if possible.
--
Jonathan S. Thyer, Programmer/Consultant
IRC Dept, UNC-Greensboro
Internet: thyerj@alice.uncg.edu

Newsgroups: comp.os.os2.networking
From: MLONG@isucard.card.iastate.edu
Subject: Re: OS2 SQLServer connections
Organization: CARD
Date: Wed, 22 Jul 1992 20:34:25 GMT

In article <5134@krafla.rhi.hi.is>                                              
yngvib@rhi.hi.is (Yngvi Bjornsson) writes:                                      
                                                                                
>                                                                               
>                                                                               
>                                                                               
>I am running Microsoft SQLServer on a OS/2 server. I have Windows clients      
>on a net  connected with  LANManager 2.1 and that works fine.                  
>I also need to run my Windows application on a standalone OS/2 computer,       
>but I am having problems connecting to the database from the WIN-OS2 box.      
>Is this possible at all?  Any suggestions ?                                    
>                                                                               
I think you will need to create a Virtual Booted Real DOS box, run the MS-Net   
software (DOS) in that box, start up WINOS2, and make sure that WINOS2's        
network is set to LAN Man.  Then the Windows Network stuff should work.         
Sorry if this messes up your news reader                                        
Mike Long                                                                       
Iowa State University                                                           
Newsgroups: comp.os.os2.networking
From: digiuser@endor.byu.edu (Robert Perkins)
Subject: Re: Cant get global session map to work - help pls.
Reply-To: Rob_Perkins@byu.edu
Organization: Brigham Young University -- Mathematics Department
Date: Thu, 23 Jul 92 08:16:48 GMT

In article <1992Jul17.212352.29438@ccu1.aukuni.ac.nz>  writes:
> I sat down for 3 hrs with my Netware administrator trying to get
> Netware Requester for OS2 2.0 to think globally. This is the first
> [etc...]

Certain commands , such as MAP.EXE, FILER.EXE and others don't work in a global  
network DOS session.

What global access means: Drives, printers, and other shared resources are the  
same in every global DOS session as they are in the OS/2 session.  When the  
mappings are changed in either session, the results are felt throughout the  
system, EXCEPT in the private DOS sessions, which retain absolute identity with  
an actual DOS kernel running alone on a PC.

Be sure to change the DOS settings (in the settings notebook for a DOS session  
object) in every VDM that you want the network software to work with. For a  
GLOBAL session:
FILES=255
LASTDRIVE=whatever the highest lettered drive is on your machine
NETWARE_RESOURCES=GLOBAL
VIPX_ENABLED=yes

And for a PRIVATE session, same settings, except that LASTDRIVE can be set to  
whatever value you want above your last drive, and to capture printers  
correctly, the device LPTDD.SYS (found in OS2\MDOS\) should be added to the  
DOS_DEVICE parameter. Also, you will have to manually load \NETWARE\NETX.COM  
once the session is opened, or, alternatively, include the argument  
/Kd:\NETWARE\NETX.COM in the arguments field in the settings window.  It is not  
recommended to put the NETX.COM statement in the AUTOEXEC.BAT file, because  
then global sessions will also attempt to excecute it.

I _hope_ this helps a little...
--
Rob Perkins
BYU Systems Software Support Technician
Hi! I'm a .signature Virus! Copy me into your .signature and join the fun!
"My opinions are sick and can't come to work"
:) 
-----------------
Newsgroups: comp.os.os2.networking
From: meyer@ux1.cso.uiuc.edu (Don Meyer)
Subject: Re: IBMToken packet driver
Organization: UIUC College of Agriculture
Date: Thu, 23 Jul 1992 19:57:01 GMT

jhopkins@cbacc.cba.uga.edu (John Hopkins) writes:

>In article <rkohlbus.2@dining.umd.edu> rkohlbus@dining.umd.edu (Robert Kohlbus) writes:
>>        Ok, I'm currently on an IBM Token ring network that has been broken 
>>and connected to the internet.  Now that I have update my machine to OS/2 and
>>using Novell's Lan Requester for OS/2v2.0 my IBMToken packet driver no 
>>longer works because the TRA adapter files are not being loaded.  Does 
>>anyone have a suggestion on a new Packet driver that would fix my problem?

>Man, have you ever bitten off a chunk here!!  If you find a way to get this 
>working, I would sure like to know what it is, but I fear that you will not. 
>I only know of one way to use packet-driver-expecting software even under 
>DOS, and that is to use IBMTOKEN, which I loathe!!!!  Since IBMTOKEN won't 
>work under OS/2, I really think we are both out of luck.

Well, something to keep in mind for those of you trying to run packet drivers
on Token Ring, you might want to try setting up an NDIS layer, and then running
the DIS_PKT.DOS driver, which is a PD packet driver <-> NDIS shim.

Now under OS/2, this will probably not work, as for some *STRANGE* reason,
an OS/2 NDIS stack is not accessible from DOS VDMs.  If running OS/2 Netware
Requestor, if ODI services are provided to DOS VDMs, one could more than
likely use the ODIPKT.xxx driver to provide the packet driver interface. 
(Another shim)  I suspect that the situation is the same for ODI services
in DOS VDMs as with NDIS, but if it is possible, I'd love to hear about it.

And I wish IBM would provide a solution - I've been told that the Virtual 802.2
drivers (for 802.2 access from DOS VDMs) will solve this problem, but I 
can't see how.  Anyone caring to take a shot at explaining to me how this will
solve the lack of packet driver access in a DOS VDM with OS/2 LAN Software 
running?

Don
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Don Meyer			dlmeyer@uiuc.edu
	 Network Manager, UIUC College of Ag Microcomputer Facility

"Fiscal Responsibility + Personal Freedom = Libertarian"     Marrou/Lord in 92!

member: NRA, ISSC, IL Farm Bureau	"Don't blame me, I voted Libertarian!"
From: matt@bss1.umd.edu (Matthew Piermarini)
Newsgroups: comp.os.os2.networking
Subject: IBM TCP/IP 1.2.1 w/ODINSUP.SYS
Date: 23 Jul 92 20:26:23 GMT
Organization: College of Behavioral and Social Sciences, U of Maryland

I have the dist. copy of the Netware Requestor for 2.0 (which works fine), 
and am now installing IBM TCP/IP 1.2.1.   I have configured everything (the 
config.sys, net.cfg, protocol.ini) and the machine boots fine with both the 
Netware and TCP/IP connections working properly.  The problem is that about 
after 5-10 minutes of TCP/IP use, all the running TCP/IP applications lockup 
and any new TCP/IP application won't run (returns host unknown or connection 
invalid, etc).   The Novell links are still fine.   It almost seems like 
another computer is using the same IP address as this machine, but I can 
guarantee that is not the case.  Any clues would be helpful.

Thanks,
Matt Piermarini
U. of Maryland
matt@bss1.umd.edu
(301)
405-1669
Newsgroups: comp.os.os2.networking
From: chris@quay.ie (Christopher Davey)
Subject: rsh hangs - is this a known bug
Date: Tue, 28 Jul 1992 07:44:43 GMT
Organization: Quay Financial Software

I am running TCPIP 1.2.0 on OS2/2 GA.  Sometimes, for no obvious reason, an 
rsh from our RS6000 hangs the machine.  The rsh call on the RS6000 does not 
return, and the OS2 machine freezes.  The interesting thing is, is that it
will respond to pings, and will run other rshs successfully - eg 
"rsh idlewild dir" will work.  Nothing else (telnet / trying to drag a 
window ) works though.  Any hints / idea / have you been through this 
too ?  Are there any APARs that I should have ( I loaded one lot, none
of which affected the rpc stuff, as far as I can see )


Any help or hints appreciated,
Chris

-- 
Chris Davey                       Internet:  chris@quay.ie
Quay Financial Software           Phone   :  +353 1 612377  Fax: +353 1 607592
From: 01calvin@ac.dal.ca
Newsgroups: comp.os.os2.networking
Subject: <None>
Date: 31 Jul 92 00:25:02 -0300
Organization: Dalhousie University, Halifax, Nova Scotia, Canada



	Hi,

	I'm not an OS/2 user, but I've been put in charge of putting
	together an office at my university that has just bought 3 
	machines bundled with OS/2 on the hard drives.

	They have also said that they will be wanting to incorporate 
	file and printer sharing.  I suggested some form of Peer to Peer 
	network allowing them to access the same databases, etc, etc.

	Now it starts to get tricky.  One of the machines is to be used
	by an administrator (not in the office) whos involvement in that 
	office's daily business is negligable.  The odd print job to the 
	laser may occur but that is all.  (As of now she is sticking with 
	sneakernet.)  She has stated however that since the campus is going
	fiber optic (that is just about every building is being connected 
	to the back bone) she would like to have access to that if for 
	nothing else than for E-mail.

	One of the machines in the office will have the same requirements
	as the above machine as well as file and printer sharing.

	Now I figured that machine A and B would be connected to the
	backbone and be able to utilize telnet and ftp and whatever.
	This is good.  Also I thought that machines B and C would be
	connect as a peer to peer network and do their thing.  This is 
	also good.  

	What I want to know is...  Will machine B need two ethernet 
	cards?  Will there be a problem connecting it in this way?

	Upon further consideration, I thought that a hub off the backbone
	connecting all the machines and perhaps a print server or
	something to that effect may be better.  I started looking at
	prices and found that a 12 connector hub for 10base T ethernet
	(twisted pair) runs around $2300 dollars.  Even with university
	funding, it's a little out of their range.  This of course 
	would satisfy any expansion that may occur as well, providing
	it can be implimented in this way.

	Can anyone tell me if there is a better solution?
	Better = less expensive, more effective.
	Will the hub idea work?  I'm sure some arrangement could be made
	to overcome the cost of the hub.  Renting or whatever.
	Is there a problem with OS/2 and networking of any form?
	Networking in this way?  Each machine will have it's own copy
	of OS/2.  All they need to share are X number of files and one
	printer so a client-server network is not really necessary.
	Not that they could afford a dedicated server anyway, but you 
	get the idea.

	You can E-mail me or post a reply.  I'm sure that others may
	find something of interest in it as well.  Flames?  Well, only
	if I screwed up on netiquette.

	PS. In case you were wondering, my summer job is hardware and
	software support at the university computer lab.

Spiff
    _l\l\l\      01calvin@ac.dal.ca      "We are free to go where we
    Oc O   )     Vanguard@ac.dal.ca       wish and to be what we are."
     \_/  /      Goldrick@ug.cs.dal.ca   - Jonathan Livingston Seagull
Newsgroups: comp.os.os2.networking
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: Good TP ethernet card for use w/IBM TCP/IP 1.2.1?
Keywords: ethernet os/2 ibm tcp/ip 1.2.1 card
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Wed, 22 Jul 1992 16:27:35 GMT

In article <cro.711820978@ennews!socrates.ed.asu.edu> cro@socrates.ed.asu.edu (C. R. Oldham) writes:
>Just got IBM's TCP/IP 1.2.1 up and running and I'm quite pleased so far.
>There are nits to pick--hopefully they will be fixed soon.
>I'm getting new machines in a couple of days, however, and I'd like
>recommendations regarding ethernet cards.  I've got a 3com 3c503 TP
>in my 386 right now--throughput seems very slow.  Is this normal?  For now
>I was chalking it up to the fact that I've only got 8 Mb of Ram.

It depends on how many daemons you have running, but TCP/IP is a
little sluggish in 8 MB, yes.

>IBM's TCP/IP distribution contains drivers only for a few cards.  Is it
>reasonable to expect that vendors will have NDIS drivers for OS/2 by now?
>Are they hard to get?  Are they buggy?

Not hard to get.  I would stick with a "mainstream" adapter -- the
3Com ones are fine.  You can take a look at the full list of NDIS
drivers by ftp'ing over to ftp-os2.nmsu.edu.  There are some in
/pub/downloads at the moment, some elsewhere.

>When I select a new card should I choose an 8 bit or a 16 bit?  I've
>heard people say that it makes a world of difference, and it makes no
>difference.  Which is true?

I suggest 16-bit.  The price differential is usually not that great,
and you free up one of those valuable lower interrupts (assuming the
card supports higher order interrupts).

-- 
Get the OS/2 FREQ. ASKED QUESTIONS LIST | Timothy F. Sipples
from 128.123.35.151, anonymous ftp,     | Internet: sip1@ellis.uchicago.edu
directory pub/os2/all/faq, or from      | Dept. of Econ., U. Chicago, 60637
LISTSERV@BLEKUL11.BITNET (send "HELP"). | Tsongas > Perot > Clinton.  Yay.
From: daves@vtucs.cc.vt.edu (Dave Sisson)
Newsgroups: comp.os.os2.networking
Subject: Re: Thinking of getting TCP/IP 1.2.1, how's NE2000 support?
Date: 23 Jul 92 13:31:37 GMT
Organization: Virginia Tech, Blacksburg, VA

In article <1992Jul23.075720.2798@hamblin.math.byu.edu> Rob_Perkins@byu.edu writes:
>In article <4926@vtserf.cc.vt.edu> daves@vtucs.cc.vt.edu (Dave Sisson) writes:
>> 
>>      I am currently using OS/2's TCP 1.2 with the NE2000 drivers I nabbed
>> with anonymous FTP from somewhere.  I haven't noticed any problems.
>
>Where can these drivers be found?  Where is the ftp site?


        Try vax.ftp.com in the /ndis directory for the files NE2000D.ZIP and
    NE2000O.ZIP.  One is the NDIS driver for DOS, the other OS2.
From: hanzheng@acf3.NYU.EDU (James Han,Meyer 827,998-7758,(212)260-4530)
Newsgroups: comp.os.os2.networking
Subject: Problem to install Netware OS/2 requestor
Date: 27 Jul 92 01:32:00 GMT
Organization: New York University

Newsgroups: comp.os.os2.networking
Summary: 
Expires: 
Followup-To: 
Distribution: 
Organization: Courant Institute, New York University
Keywords: OS/2, Netware Requestor 

Does anyone have trouble to install OS/2 requestor? I recieved a
strange error when I tried.
"NWD0115: Error getting connection ID: 0x880f" and later OS/2 give me
"SYS0059: An unexpected network error occured".

The Installed machines are 
    1. IBM PS/2 70-A21 with 6M RAM, Math-processor, IBM Token-Ring
       16/4 Card.
    2. IBM PS/2 57SLC w/ 4M RAM, IBM Token-Ring 16/4 Card.

they are all connected to the Novell Netware 2.15c.

Thanks for any helps!!!!!
From: Mahoney@emdisle.FIDONET.ORG (Mike Mahoney)
Newsgroups: comp.os.os2.networking
Subject: DNS and IBM's TCPIP, nslookup failure !
Date: Thu, 23 Jul 92 19:22:09 PDT
Organization: The Emerald Isle BBS, Tucson, AZ (602) 749-8638

In a message of <Jul 23 18:03> (Operator) writes to All:

 O>I want to use a domain nameserver with IBMs TCPIP !
 O>I installed a nameserver in our network. From our unix
 O>workstations there is no problem to use this nameserver!
 O>But if I want to start nslookup on my OS2 PC I get the message:

   I'm not familiar with nslookup, but I'm also not sure why you need it.

 O>Can't find server name for address 192.9.210.60: Server failed!
 O>Default Servers are not available 

 O>Now the resolv file of my OS2 PC:
 O>domain          edag.de
 O>nameserver      192.9.210.60

   What you have above is what I use. Well, close to it. |-)

 O>Is anyone using DNS with IBMs TCPIP
 O>for OS2. Is this a known bug? Any hints?

   If you use the host command with the resolv file that you show it should work. You should also be able to use FQDN's for things like rexec, FTP and whatever variant of telnet that you use. Within the local domain a simple host name will suffice.

    I'm using a common nameserver between AIX machines and OS/2 machines running TCP/IP for OS/2 (Version 1.2.1, but it worked the same with all the prior releases too). I don't use nslookup, but all the other functions involving nameserving work as I expected them to. I'll have to look in the documentation and see what this program is supposed to do, but life has been fine without it.

    We also have our nameserver setup to pass on anything it doesn't recognize to a higher level name server so that we can find any host address anywhere in our network. This works fine from an OS/2 machine as well as from any of the AIX machines.

--- msgedsq/2 2.1
 * Origin: The Emerald Isle * Tucson, AZ. (602) 749-8638 (1:300/14)
--  
Mike Mahoney - via FidoNet node 1:300/14
UUCP: uunet...!noao!coyote!emdisle!Mahoney
INTERNET: Mahoney@emdisle.FIDONET.ORG
Newsgroups: comp.os.os2.networking