Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!olivea!apple!julius.cs.uiuc.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!uunet!world!goodearl
From: goodearl@world.std.com (Robert Goodearl)
Newsgroups: comp.windows.ms
Subject: Re: Win 3.0, Netware 3.01 and Tiara Problems
Message-ID: <1990Sep13.211736.27219@world.std.com>
Date: 13 Sep 90 21:17:36 GMT
References: <14460@rouge.usl.edu> <1990Sep13.124845.23549@techbook.com>
Organization: The World
Lines: 45

In article <1990Sep13.124845.23549@techbook.com> kenh@techbook.com (Ken Haynes) writes:
>In article <14460@rouge.usl.edu> pcb@gator.cacs.usl.edu (Peter C. Bahrs) writes:
>>Each has tiara network card in them.  We are running Netware 3.01,
>>the newest version and I must say I am very impressed with it.
>
>Are you running the 3.01 SHELLS?.  You must have the latest version of the
>shells (the ipx, netx part of the netware interface).

fyi, the latest versions (as far as I know) are:

Novell IPX/SPX v3.01 Rev. A (900507)
(C) Copyright 1985, 1990 Novell Inc.  All Rights Reserved.

and

NetWare V3.01 rev. C - XMS Workstation Shell for PC DOS V3.x
(C) Copyright 1983, 1988 Novell, Inc.  All Rights Reserved.

(you can check this by running the file and specifying -i as the option.)

>>
>>win /r works fine.  I can connect printer servers and connect drives.
>>Everything behaves (except hp plotter driver which is another story).
>>
>>But in 386 mode:
>>c: ipx
>>c: net3
>
>You should be using either XMSNET3 or EMSNET3 instead of just net3. You will
>need to have an expanded memory manager present (as in MS HIMEM.SYS), or an
>extended memory manager (as in EMM386.SYS), to use these programs. These
>programs will load the XXXnet3 portion of the shell into high memory.  The
>MS Windows 3.0 program will look for these programs when it initializes.
>

EMSNET3 is probably not a good idea with windows, as EMS is not available
until after you have windows running.  Note that I had some problems with
the original version (3.01, no rev) of XMSNET3.  (It would occasionally
cause windows to crash.)  The current version of XMSNET3 seems to work just
fine for me, but because of problems with the previous version, our sys-
admin has asked that it get only limited use.  NET3 (v3.01C) works just fine,
though you do get about 30k more conventional memory available when using
XMSNET3.
-- 
Bob Goodearl -- goodearl@world.std.com