Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!fernwood!portal!cup.portal.com!Howard_Reed_Johnson
From: Howard_Reed_Johnson@cup.portal.com
Newsgroups: comp.sys.novell
Subject: Re: netware 2.10 and windows 3.0
Message-ID: <40212@cup.portal.com>
Date: 16 Mar 91 08:12:01 GMT
References: <5505@media-lab.MEDIA.MIT.EDU>
Organization: The Portal System (TM)
Lines: 20

Question from: castillo@media-lab.MEDIA.MIT.EDU (Brian Anderson)
> I've inherited a system that run Netware 2.10.  Do I have to upgrade to
> 2.15c before I can generate the 3.01 rev B ipx.com files and use the
> netX.com rev E shells?  All this is due to a sudden desire to run
> MS-Windows 3.0 from the server.

All you need to generate your IPX.COM is IPX.OBJ, your lan driver .OBJ,
and NLINK.EXE.  For instance:

     nlink -o1 ne2000.com ipx.obj sne2000.obj

This is what SHGEN executes to build your IPX.  Have NLINK, will travel.
Alternatively, you could temporarily replace the IPX.OBJ used by SHGEN.

The 3.01 Rev B IPX.OBJ and 3.01 Rev E NETx.COM modules should work with
Win 3.0.  I'm not aware of any Windows issues requiring a server upgrade.

-- 
HoJo@cup.portal.com     |     For 20 points, describe the following option:
Howard Reed Johnson     |     DEVICE=DXMC0MOD.SYS Q