Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!pikes!udenva!mercury.cair.du.edu!diana.cair.du.edu!mbrookov
From: mbrookov@diana.cair.du.edu (Matthew B. Brookover)
Newsgroups: comp.sys.mac.misc
Subject: Re: System 7.0 vs. Windows 3.0
Keywords: windows, system 7
Message-ID: <1990Jul4.022114.19155@mercury.cair.du.edu>
Date: 4 Jul 90 02:21:14 GMT
References: <2135@esquire.UUCP>
Sender: news@mercury.cair.du.edu (netnews)
Organization: University of Denver
Lines: 24

In article <2135@esquire.UUCP> baumgart@esquire.dpw.com (Steve Baumgarten) writes:
>Someone posted that Windows 3.0 supports all the major networking
>schemes (Novell, etc.).  But what does this really mean?  Under System
>7.0, I can create public folders for others to use without having to
>run network administration programs and the like; can I do this under
>Windows 3.0, or is Windows' network support limited to low-level
>operations?

My undstanding is that windows 3.0 will break unsupported networking
schemes.  They have built in support for novell and etc,  but if you
are using an unsupported package it may not work.

On our novell networks we are running Novell 2.15c with the packet
driver version of the lan driver from BYU, and then using the public
domain packet drivers written by Clarkson.  This allows the us to run
NCSA telnet and Novell concurretly through the same ethernet board.
(this is somthing that the Mac handles much better than MS-DOS)  I have
heard form other sources that the virtural memory in Windows 3.0 will
keep the packetdriver from reading and writeing to and from buffers
that belong to the client applications.  Has anybody tried this out
under windows?

Matthew B. Brookover
mbrookov@diana.cair.du.edu