Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!hayes.ims.alaska.edu!acad3.alaska.edu!jsdph
From: jsdph@acad3.alaska.edu (HARRIS DENNIS P)
Newsgroups: comp.sys.novell
Subject: Re: netware 2.2 and windows
Keywords: netware, windows
Message-ID: <1991Apr17.095314.17836@ims.alaska.edu>
Date: 17 Apr 91 09:53:14 GMT
References: <1046@opus.NMSU.Edu>
Sender: usenet@ims.alaska.edu (J Random USENET)
Reply-To: jsdph@alaska.edu
Organization: University of Alaska Southeast
Lines: 26
News-Software: VAX/VMS VNEWS 1.3-4
Nntp-Posting-Host: acad3.alaska.edu

In article <1046@opus.NMSU.Edu>, rocks@nmsu.edu (Dave Rocks) writes...
> 
>	I have an office on campus that wants to set up a small, 3 machine
>	network. I apparently have a choice between netware 2.2 and 2.15.
>	The user wants to run the server in non-dedicated mode, and he also
>	wants to be able to run Windows apps on the server. Is this 
>	possible? 

the short answer is no.  both windows and netware want to have 
control over memory, and will inevitably conflict.  when windows 
hangs, the user will have to reboot, and *poof* goes the server.


i would select netware 2.2 (mucho easier installation) and run it 
in dedicated mode.  the grief and hassle factor soon outweighs 
the cost of an extra machine to use as a dedicated server.  if 
the network will be used for light duty with only 3 or 4 users, i 
would suggest an inexpensive 12 mhz at clone with an esdi drive, 
4 mb of ram, and a 16 bit network card.  save the model 70's 
power for running windows as a workstation, where it will shine.

================================================================================
dennis p. harris					bitnet: jsdph@alaska.edu

  "The nation that controls magnetism controls the Universe." --- Diet Smith
================================================================================