
------------------------------------------------------------------
NOV-W951.DOC -- 19951227 -- Email thread on NetWare and Windows 95
------------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Sat, 12 Aug 1995 13:52:54 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: LWP 4.2 & 3.11 & WIn95?

>I upgraded from windows for workgroup, and VLMs v1.2 on a netware
>3.11 network to win95...
---------
	This will appear to be a rather harsh response, but it's intended
to forewarn others at this time of the troubles encountered changing to
Win95, so it's not directed specifically at you.
	Win95 is DIFFERENT. With few exceptions you will need to reinstall
all Windows programs from scratch. One exception seems to be Quattro Pro
for Windows, where it is finally self contained enough to be run with a
single pointer ("shortcut" in Win95-speak).
	I *strongly* recommend printing and reading the Win95 Resource Kit.
If you don't have it then either purchase the book from MS Press (and I
don't know how far out of date that will be) or wait for 24 Aug to get it
on CD-ROM with the release Win95 4.00. You may also glean hints from reading
win95boo.txt in directory misc on netlab2.usu.edu.
	Without doing lots of homework it is foolish to convert a production
server to use Win95. Equally if Win95 isn't at least the build 950 level.
	To run VLMs you need autoexec.bat, and to do decent memory management
and other normal tasks then config.sys is used too. Do not be brainwashed
by Redmond hyperbole; look hard at your client configurations.
	I can add this much. My people have created a Win95 production
delivery system on a production NW 3.12 server, and we've doubled the
number of application directories (one for Win 3.1, one for Win 4.0).
Each is booted differently at this time. We can use VLMs provided we don't
use Ethernet boot ROMs, but if those ROMs are used then we must fall back
to NETX.EXE. The problem is in Win95. We use QEMM/386 for memory management,
but some machines don't work properly unless the feeble DOS memory management
is used; beware. Long name support is NOT present unless one uses Microsoft's
NW client, and I have no desire to do that. Long name support will cost your
server quite a bit of memory and performance, to cache directories and to pay
the penalty of each directory cache block holding only half as many files as
without the extra OS2 namespace. The load stream across the wire for Win95
runs to about 7.5MB here, so be prepared for additional network traffic.
Printing works at both GUI and DOS box levels (to queue, via Capture in login
script, respectively), but it is not yet gotcha-free.
	At this time I am still undecided whether to make Win95 the default or
not for Fall Term, and the choice is mainly one of perceived environment
rather than technical advantage.
	Joe D.

------------------------------

Date: Mon, 28 Aug 1995 13:32:26 -0700
From: Scott Peterson <petersse@SCE.COM>

>>Has anyone found a decent way to admin win95 under netware 3.xx ??

1)  Microsoft had a series of satellite downlinks on Win95 issues.  They
had a 4-hour one on Netware.  You should talk to Microsoft and see if they
can get you a PAL copy of it.

2)  Actually it gets simplified as you can put system policies in the
Netware login directory which will allow you to control access to Win95
facilities that can't be bypassed.

The major problem is that the current support is bindery only.  NDS support
from both Novell and MS lags 60-90 days behind Win95 availablity.

The other major problem, of course, is Microsoft's attitude towards
networking.  ANY problem involving networks will not be handled by the free
MS tech support.  It will be a chargable item unless you have their premium
tech support.

------------------------------

Date: Tue, 5 Sep 1995 14:50:54 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: what 4.1 namespace supports Win95 long file names

>>I was working on a backup program for my laptop, which has win95
>>installed on it. I wanted to back my files from the laptop to the
>>server so that the server would archive them to tape. I set up a
>>batch file with several xcopies in it to copy my datafiles from several
>>directories to my home directory on the server.
>
>>The batch file worked just fine until it came to the directory
>
>>c:\sidekick95\userdata
>
>>where it encountered disk files with long file names like
>>ricks.skcards, or ricks.skcalendar etc. The server just giggled and
>>said that they were invalid DOS filenames and ignored my xcopy
>>request.
>
>Load the OS/2 namespace NLM and add the name space to each affected volume.
----------------
	If that's all one does then the odds are it won't work. Why? Because
the NW shell has to deal with the long filename first, then pass material
to/from the file server in a form masquerading as an OS/2 request. Oh.
	At this moment, the only available shell doing that is Microsoft's.
	You should think hard about long filenames before supporting them.
It's clearly an interesting concept, but one for which there is basically
no support in the DOS/Windows world at this time.
	Adding a namespace to your file server slows down directory searches
because each directory cache buffer now holds DOS + new namespace entries in
the same amount of memory. Backups of the server now must support name
spaces. Memory in the server needs attention to support an adequate number
of directory cache entries for rapid service. Managing files from DOS alone
becomes a pain.
	So far, the only package I've seen which "apparently" requires
long names is MS Office 95. I say apparently because one can install it
with undoc'd switch /F, as in   setup  /F, to suppress long names, but from
floppies I have yet get that to work. More trials remain, however.
	Joe D.

------------------------------

Date: Sat, 30 Sep 1995 17:22:15 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Installing MS Office 95 to NW 3 server (read/only)

							30 Sept 1995
	This is an addendum to the long saga of installing Windows 95
and accessories to NW servers which are read-only and the clients are
diskless.
	MS Office 95 is a real problem to install because it wants to use
long filenames, and that means one would need to employ a MS network shell
and add OS/2 namespace to the server (there go our directory cache buffers).
Further, installation fails completely if we run  setup /F  to a file server,
as instructed by a popup screen during such an attempt. We use VLMs and no
OS/2 namespace.
	Well, there are ways and ways. Rich Blake, my student supervisor
(supervisor of other student consultants) kept banging away on the problem
and we found a solution. It's an install & transfer solution.
	Assume sys:win95 holds Win95, and that all user GUEST's have their
working area within sys:win95\user, and they have only Read/Find access.
	Put a temp hard drive on a client. Install Win95 on it. Copy existing
Win95 files to the client, so the registry and .ini files and all that jazz
are the same. Use SUBST or MAP ROOT to fake NW and DOS/Win95 into thinking
the local hard drive letter is the same as one normally uses on NW (say F:)
to keep the sundry full filenames the same everywhere.
	Now install MS Office 95 to the local drive (F:) using  setup /F.
/F converts long filenames to short ones. When done we do the other steps.
Make a directory on the server of the same name as on the temp hard disk,
F:\msoff95 in my case. Ncopy *.* /s/e from hard to server. Also copy the
\win95\user\msapps directory contents to the server ("user" is the client
particular storage area, and it need not be under \win95). Copy *.ini
files to \win95\user so the extra lines for MS Office 95 are available.
	The last step is to copy system.dat and user.dat registry files
to the server. The safest method is to use regedit, export the hard drive
registry to a simple text file, put that file somewhere on the server.
Then reboot and log into the server, use regedit again and import that
file; the result is a merging of old and new registries. You may want
to clean up the registry by removing old junque.
	Finally, create a shortcut pointing to the MS Office 95 icons,
adjust window sizes and positions, click on every Help (and within that
on each Find) button to create the helper files (see scribe icon work),
and that's that. Remove temp hard drive. It's a clean installation, and
it does not clutter the Start menu.
	Joe D.

	I forgot to mention one step in the installation procedure. About
seven files need to go into sys:win95\system during the process. It's easy
to spot them by doing a directory listing of that directory on both client
(with MS Office 95) and server, and differencing the two. Move the files
by hand; there is no collision with existing files.
	Differencing directory listings is a good idea in general to spot
tiny changes.
	Joe D.

------------------------------

Rich Graves, llurch@networking.stanford.edu
 moderator of the win95netbugs list
 http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html

------------------------------

Microsoft Windows 95 Detailed Questions and Answers

The Microsoft Corporation has placed this 74,000 byte document online to
help alleviate any questions or concerns people may have about the new
operating system.  It covers everything including:
 -  What is Windows 95?
 -  Why Will I Want Windows 95?
 -  Software/Hardware Compatibility
 -  The Microsoft Network - Online Service

	http://www.windows.microsoft.com/windows/qa/qa.htm

Floyd Maxwell

------------------------------

Date: Tue, 17 Oct 1995 19:41:53 +0200
From: Henrik Schack Jensen <SCHACK@PO.IA.DK>
Subject: Microsoft NDS Client is available !!!!!

The Microsoft NDS Client is available at :

	http://www.windows.microsoft.com/windows/software/updates.htm

------------------------------

Date: Fri, 27 Oct 1995 16:48:01 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Word95 filenames in Novell 3.12 Environment - Help!

>One thought would be to use the long filenames feature of Win95.  To do
>this with Novell 3.x you have to add OS/2 namespace support to the
>volumes.  Downside of this is noncompatibility with clients that don't
>have Win95 (or is it Lose95?)
-----------
	I think you may not have tried your advice. Long filenames are
presently a property of the shell and then supported or not by the file
server. While NW can support the needed OS/2 namespace the DOS shells do
NOT. Microsoft's do. In practice you are just as well off without the long
namespace at this time since all the other programs cannot handle it, and
that includes many tape backup programs as well as straight DOS itself.
It's a nice idea, but not ready for production deployment at this time.
	To deal with MS Office 95 on a NetWare file server be aware that
it won't install without long filename support implemented thoughout. The
Install program itself fails. There is a way to get around all of this and
still use a DOS namespace file server with MS Office 95 on the server, and
it's explained in document MSOFF95.TXT in directory misc on NW file server
netlab2.usu.edu. Companion docs in the same place are WIN95BOO.TXT (how to
install Win95 on a NW server for diskless workstations, well worth reading)
and WIN95SAP.TXT (MS' comments on the nasty IPX SAP problem, don't let it
happen at your site).
	Joe D.

------------------------------

Microsoft Windows 95 Detailed Questions and Answers

The Microsoft Corporation has placed this 74,000 byte document online to
help alleviate any questions or concerns people may have about the new
operating system.  It covers everything including:
 -  What is Windows 95?
 -  Why Will I Want Windows 95?
 -  Software/Hardware Compatibility
 -  The Microsoft Network - Online Service

	http://www.windows.microsoft.com/windows/qa/qa.htm

Floyd Maxwell

------------------------------

Date: Sun, 29 Oct 1995
Subject: Fwd: Novell client32, couple of hints

ftp://ftp.coast.net/SimTel/win95/novell/c3295d_a.zip
ftp://ftp.coast.net/SimTel/win95/novell/c3295n_a.zip
ftp://ftp.coast.net/SimTel/win95/novell/c32_tech.zip
ftp://ftp.coast.net/SimTel/win95/novell/sdk.zip

NetWare Client32(TM) for Windows95 Open Beta 1

Novell's NetWare Client 32 for Windows 95 is now available via our Open
Beta program.  This product extends your Windows 95 desktop by fully
integrating with NetWare 2.x, 3.x and 4.x services including NDS.
Novell is committed to enabling client access to NetWare regardless of
workstation platform or release of NetWare.  Early reviews indicate this
product provides the most transparent and full featured integration of
NetWare and NDS with Windows 95 desktops.

Highlights include:
 - Easy installation and upgrade
 - Access to NetWare Application Manager for easier workstation
   management
 - Graphical based login utility
 - NetWare Provider which extends Network Neighborhood and
   Explorer functionality
 - Increased performance and reliability though integrated cache, and
   full Auto-reconnect
 - Integrated NetWare/IP support

The NetWare Client32 Open beta consists of the following files.

c3295d_a.zip - A complete copy of the open beta product which will
extract to a diskette structure.  The client32 can then be installed
with diskettes.

c3295n_a.zip - A complete copy of the open beta product which will
extract to a network structure.  The client32 can then be installed
via the network.

You will need either c3295d_a.zip or c3295n_a.zip to use the product.

c32_tech.zip - A technical description of the product.  The EXE in this
ZIP is is a self-extracting ENVOY(TM) file which is viewed under Windows.
This file is NOT required to use the Client32.

sdk.zip - This file is the Client32 SDK beta and is NOT required to use
the Client32.

Questions or comments about the Client32 product should be sent to
"CLIENT32BETA@NOVELL.COM".  No direct response will be given, however
the most commonly asked questions will be answered in a regularly
updated FAQ.  The FAQ is available on the WWW at
"http://netwire.novell.com/home/client/client32/faq.htm".

Ruth Kazanski
ruth@novell.com

------------------------------

Date: Sun, 29 Oct 1995

It was released today, or tomorrow if you believe the modification dates
on the Web server. Credit Patrick Lynch <lynchp@gort.canisius.edu> for
being the first to point this out. Novell's Client32 is at:

  http://netwire.novell.com/home/client/client32/

It should also be found somewhere on ftp.novell.com, Novell's Compu$erve
support area, and Novell's BBSes.

Pluses v. Microsoft's NetWare Client and NDS Service:

o Works with NetWare/IP
o Full NDS support
o Full support for all applications that expect to find NETX or VLMs
o Supports browsing multiple NDS trees and multiple points within the same
  tree
o Packet burst behavior doesn't cause older NetWare servers to crash
o Doesn't have a bunch of bugs in the login script processor (at least,
  not the same ones)
o Is honest enough to call itself an open beta
o The first minus below could be considered a plus by many people

Minuses:

o Does not support Microsoft's peer file/print sharing over IPX (but
  there's enough problems with this that you should really be sharing over
  NetBEUI or TCP/IP instead anyway).
o Allegedly a little slower
o Doesn't support SNMP over IPX (I don't think)

Any other pluses/minuses to add or subtract?

Question I don't see answered in the FAQ:

Does it support NASI?

Richard Charles Graves

------------------------------

Date: Sun, 29 Oct 1995

UK/European readers may want to know that this software is available
on my ftp server using the URL below:
	ftp://ftp.salford.ac.uk/novell/CLIENT32/win95

Apart from ftp.novell.com the software is on:
	ftp://netlab2.usu.edu/pub/client32

Richard Letts

------------------------------

Date: Sun, 29 Oct 1995

	Beta tests are times to test and report, not just enjoy. You can
help everyone involved by providing a little more specific information.
In particular, it is important to know what board and driver you are
using since there are some hiccups with at least one board (NE3200,
CODI driver CNE3200). If your machine crashes upon a reboot, just when
the GUI interface is to begin, and the crash says bad things about memory
location 000:650... or similar then we'd like to know too.
	The client runs here on an NE2000 and WD8003E, but not on a NE3200.
	Note the new Novell logo (a connect-the-dots graphic).

	Once the dust has settled on the installation process I think
everyone concerned with Win95 will want to compare Novell's to MS' client
material in some detail. Realize that MS is release level and Novell's is
just barely beta (and hence subject to improvement too).
	Joe D.

------------------------------

Date: Sun, 29 Oct 1995 14:12:53 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Novell client32, couple of hints

	As folks have a look at Novell's client32 shell (beta) for Win95
it might be useful to have a couple of alternatives handy for the networking
part of matters. So here are a few hints.
	As shipped the beta client wants to use the new 32-bit ODI driver
for your lan adapter, such as CNE2000.LAN or similar. The "C" prefix means
the C Language, and it's ODI-slang for the 32-bit version of ODI (aka CODI).
If you choose that lan driver then it is loaded when the GUI interface
begins (when you say WIN.COM if you boot to DOS 7 level as I do). Particulars
normally found in NET.CFG are then in the Win95 registry instead. What this
means is the network isn't available until the GUI is loaded, and if things
work then the client32 material will provide a NW login box.
	Don't be fooled by the .NLM extensions on some client files: they
are NOT suitable for use with a NW server (and vice versa).
	Be aware that the lan driver may fail to be copied into the
operating Novell\client32 directory. If that occurs Win95 will complain
about not being able to find it. Just copy it over by hand.

	An alternative is to use the conventional 16-bit ODI driver and LSL
with the 32-bit client. These are loaded before the GUI begins, and a
convenient spot is at the bottom of autoexec.bat, like this:
	C:
	cd \nwclient                c:\nwclient is where regular shells are
	C:\NWCLIENT\lsl.com         startup 16-bit LSL, sees NET.CFG
	C:\NWCLIENT\NE2000.com      startup 16-bit lan driver (MLID)
	D:\WINDOWS\odihlp.exe       startup ODI -> NDIS converter for Win95
	cd \
	...
	win                         start GUI when convenient

	When setting up this second situation we first do the lines above
and start the GUI, and afterward install the 32-bit client. In the
installation part we choose "use existing ODI driver" rather than a
particular board. Please note that if your lan adapter uses IRQ 2 then you
need to beat Win95 into submission: "my computer", right mouse botton for
"properties", go in and reserve IRQ 2 so Win95 won't play with it.

	The second approach can be taken a step further and run the full
ODI/VLM material. Of course, that directly conflicts with the 32-bit shell
so don't use both. VLM/NETX does the network login at autoexec.bat time
before the GUI starts. One reason to keep VLMs/NETX in mind is remote
booting from an Ethernet board ROM. With GUI-only logins you are up the
creek nearly paddle-less. The paddle available is regular ODI/VLM/NETX,
and it works. Another reason is speed, meaning you really should benchmark
copying files with a variety of shell configurations (enough said).

	If you use the MS TCP/IP stack with either approach then you MUST
enable all four Ethernet frame kinds so that the NDIS thing can work. It's
stupid but the thing wants to work that way, so we do it. This is in the
network setup section, adapter properties.
	Happy testing and reporting,
	Joe D.

------------------------------

Date: Sun, 29 Oct 1995 23:01:05 +0000
From: Daryl Banttari <banttari@IX.NETCOM.COM>
Subject: NW Client-32/Win95- tips

A couple of tips for the NW Client-32 for those like me who are too
eager to read the docs before installing...

1)  Run SETUP.EXE, don't try to do a "Have Disk" install from Control
Panels / Network.

2)  Read, specifically, section 9 of the README file re: using .LAN
drivers for Win95.  You actually have to uncomment lines in the
NWSETUP.INI (_Before_ running setup) in order to have your favorite
net card avail in the Add...Adapter list.

3)  Speaking of the Add...Adapter list, the Envoy-format Technical
Overview suggests the .LAN drivers will have entries like, "Novell
32-bit C ODI NE2000", but for me they show up as "NE2000 Compatible
(Microsoft)" and "NE2000 Compatible (Novell)" where the former is the
NDIS3 driver, and the latter is the .LAN driver.

Incidentally, the Envoy docs (on page 46) suggest that the .LAN
drivers for Win95 are 'unmodified NetWare OS-compatible (3.x and 4.x)
LAN adapter drivers.'  I think it was Joe that suggested they were
not actual .LAN drivers, can you clarify?  I'd try it now but it's
late and I'm tired...

------------------------------

Date: Mon, 30 Oct 1995 00:31:18 -0800
From: Ian Dobson <Ian@ZED.CA>
Subject: Re: Novell Client32 for Win95 Released for Open Beta -Reply

Well I had the same problem, I was running the microsoft NDS Client.
Novell's client crashed first time up.

So I hacked the network box and removed all the networking stuff
restarted windows so I only had an ethernet adapter installed (no
clients) then I ran the install and it installed fine.

Numerous tuning has to be done though. when it's up my system seems
way faster than with the Microsoft client, however it seems to go to
outer space for a while when the system boots. I wish I knew what was
happening!

And even though I have the context set correctly it still thinks that
I am logging in from the root.

Well more testing later, I'm going to bed!

Ian D.

------------------------------

Date: Mon, 30 Oct 1995 08:24:56 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NW Client-32/Win95- tips

>Incidentally, the Envoy docs (on page 46) suggest that the .LAN
>drivers for Win95 are 'unmodified NetWare OS-compatible (3.x and 4.x)
>LAN adapter drivers.'  I think it was Joe that suggested they were
>not actual .LAN drivers, can you clarify?
---------

	First, a slightly revised set of files is now coming across the
wire, dated 30 Oct rather than 27 Oct. The archive files are a tiny bit
smaller this time. No, I don't know what's inside since the transfer
is still progressing to my mirror site at this moment.
	Second, the .LAN and .NLM files for the client should not be
confused with those in a server. The docs are a little out of date
and matters are in a state of flux.
	Joe D.

------------------------------

Date: Mon, 30 Oct 1995 19:54:08 +0100
From: Bo Persson <bop@GANDALF.SE>
Subject: Novell Client32 & National character sets

Today I downloaded the Novell Client32 beta
(version 1.1, possibly different from last week?)

It solved my problem with record locking timeouts in a legacy
(but mission critical!) DOS app, however...

Here's something for my fellow europeans, NLS character mapping:

Obviously Novell's and Microsoft's drivers use different mappings for
national characters (which I cannot use here either...) in file names.
In Microsoft's 32 bit driver, there is a setting "Preserve case=no",
to let DOS (and not the Netware server) do a lowercase to uppercase
translation for filenames. (I use a swedish DOS-version, that performs
a proper conversion of national characters, which the server cannot).

The Novell Client32 does not seem to have such a setting (at least
I can't find it). Right now I have even got different translations
in the Explorer and in DOS-boxes...

Could someone more lucky (or more clever :-) please give me a hint on
how to solve this mess?

------------------------------

Date: Mon, 30 Oct 1995 19:47:27 -0500
From: Wally McClure <wmcclure@NAMESERVER.1STRESOURCE.COM>
Subject: Review of Client32 for Win95

For those who are interested, there is a review of Novell's client32
for Windows95 in PCWeek.  The online version is at:

	http://www.zdnet.com/~pcweek/netweek/1030/tnwc32.html.

------------------------------

Date: Tue, 31 Oct 1995 10:10:07 -0400
From: "A.J. Sheehan" <ajs@CLIO.ARTS.QUB.AC.UK>
Subject: Re: NWPOPUP for WIN95

>How do I get NWpopup.exe to work under 95?

You need to install the Novell client32. Alternatively, the winpopup.exe
program supplied with Win95 will do the same for the Microsoft client for
Novell (and its NDS addition.)

------------------------------

Date: Tue, 31 Oct 1995 23:36:23 GMT
From: me (Guy Yardeni) <234134@PSI.COM>
Subject: Re: Novell Client32 for Win95 Released for Open Beta -Reply

I am writing to offer my experience with client32

I installed it today on 3 computers over a lan.
One laptop Dell Latitude p75 running an SMC adapter.
The other two are dell optiplex p75 running intel and 3com cards.

These installations work pretty well although there seem to be
problems with the upgrade routine (sometimes you crash after you lose
the previous client. Maybe novell should not delete the old client
until the new one is completely installed).

The client is running on a netware 4.1 LAN with a 3.12 server and has
full access to networked applications, gateways, server CD rom
jukebox, and a shared modem pool.  Still not tested is the new
winsock.dll, also having some problems with the new beta Lotus Notes
R4.

If anyone has any information about the client that they are
willing to share (info that's not included in the tech pack that comes
with the client), or questions please e mail me at   Yardeni@kkl.com

Good luck folks, it's a great client, and the best PC workstation
operating system by far.

------------------------------

Date: Tue, 31 Oct 1995 22:38:10 -0800
From: Ian Dobson <Ian@ZED.CA>
Subject: Client32/Win95 Questions

Cool Beta, could have got rid of the major bugs first before calling
it a Beta though, blows up if it encounters a MAP change command in a
login script.

Anyways I have a bunch of questions that I need help with.

With the Client32, how do I set up a remote printer on that station?
How do I print to printers not on that station? under dos I can no
problem, but under windows it says the printer is offline, what
gives?

And the big questions.

I will be setting up a shared network install of Win95, the workstations
boot from proms.  What client would I use? (can I use the 32 bit client?)
and If I used a DOS ODI stack would I be able to get long filename
support, and would I be able to log into the server as another user
without a reboot?  This kind of stuff keeps me up nights!

Ian D..

------------------------------

Date: Wed, 1 Nov 1995 09:22:46 GMT+1
From: Laurence Asquith <LJ.Asquith@ULST.AC.UK>
Subject: Win95/Novell 32 bit client

I downloaded the network 32 bit client - removed all network stuff
from a test Win95 system and fired up the install - near the end of
the install it started asking for 'disk1-desc' for the following files
WINSOCK.DLL, NWLINK.VXD, RPCLTC6.DLL, RPCLTS6.DLL, WSASSRV.EXE,
WSIPX.VXD, and WSOCK.VXD - of course I had no disk1 - so skipped the
files and finished install. Everything seems to work fine, login to
4.1 etc. Can anyone tell me why this happened and what all these
files are for?

Laurence Asquith

------------------------------

Date: Wed, 1 Nov 1995 08:04:31 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client32/Win95 Questions

>Cool Beta, could have got rid of the major bugs first before calling
>it a Beta though, blows up if it encounters a MAP change command in a
>login script.

	A MAP "Change"? What's the "change" part?

>Anyways I have a bunch of questions that I need help with.
<snip>

	I think you would benefit by reading the README.TXT file in the
novell\client32 directory. Remote printing is only partly possible,
remote booting is on the list of future features.
	For remote booting I recommend using VLMs. They do the job nicely
and are a heck of a lot faster than the current client32 material. You
won't get long name support though, and in actuality that turns out to
be not a loss at all in my estimation. See file win95boo.txt in directory
misc on netlab2.usu.edu for help on remote booting Win95, and companion
files win95sap.txt and msoff95.txt.
	Joe D.

------------------------------

Date: Wed, 1 Nov 1995 17:09:51 +0000
From: John Walker <jewalker@SOUND.NET>
Subject: Novell Client32 for Win95 Released for Open Beta

I setup Client 32 today on a couple of our workstations.  Had one
problem with the installation.  We use CNET nic cards.  The drivers
did not work with the client 32.  When I went to NE2000 compatible
drivers, it worked fine.

I love the way it runs and looks.  Have had no trouble upto this
point.  Have not tried to use the Dial-up adapter yet for our
Internet access.  Will let you all know if we have any problems.

John Walker

------------------------------

Date: Thu, 2 Nov 1995 15:05:08 +0100
From: Henno Keers <Mailbox@ICE.NL>
Subject: Re: Novell Client32 for Win95 Released for Open Beta

>I setup Client 32 today on a couple of our workstations.  Had one
>problem with the installation.  We use CNET nic cards.  The drivers
>did not work with the client 32.  When I went to NE2000 compatible
>drivers, it worked fine.

John, you should be able to use the NetWare 4.x compatible .LAN
driver, the one that needs ETHERTSM and MSM.
Iam not a great fan of trusting the compatibility of a card if the
manufacturer supplies drivers by themself.
You might have to make/modify a .INF file so that the install program
knows about the driver.

Another source might be http://www.cnet.co.tw

------------------------------

Date: Thu, 2 Nov 1995 08:00:00 WST
From: Ped Ristic <RISTIC@COMMERCE.MURDOCH.EDU.AU>
Subject: Re: WINDOWS ON THE LAN (even '95)

A few years ago we moved to having Windows totally on the lan, ie
with boot ROMS.  We did this because of the constant problems with
having local hard disks, ie viruses, junk being left, people removing
important files etc.  Now we have a consistant interface to every
machine and we don't even go into some labs because without a hard
disk, there is not much to fail in the pc.  (the occasional floppy)

We have given each pc a virtual hard disk, that is their node address
is mapped to a directory on the server in the login script (which is
huge but is created only once and rarely changed).  That gives them a
'c' drive (during login the 'c' drive portion is cleared so that no
junk can accumulate).  Of course all applications are on the server
and we have very little problem running any of them in this
configuration.  Occasionally we may need to modify the login script
if some legacy dos app requires it.  The win swap file can also be
set to reside on the 'c' drive.

From the management side though it is fantastic.  One installation of
the software onto the server and it is available to all.  There is
no chance it can be corrupted modified or tampered and thus never a
need to re-install anything.  Of course the appropriate rights need
to be set, but these are self-evident.  The advantage to students is
that windows loads very quickly as it is almost always cached on the
server.

We even have Win-95 running in a boot ROMed environment although the
problem with it is the load time.  Where as 3.1 takes 15 seconds to
load, '95 may take up to 2min which is too long.  The solution would
be to go to a faster net, say 100M/bits as opposed to the 10M/bits we
have.

From our experience, Win on the lan with boot roms is great.  Hope
this has helped.

------------------------------

Date: Thu, 2 Nov 1995 15:35:59 +0000
From: "S.J.Phethean" <S.J.Phethean@SOTON.AC.UK>
Subject: NW Client32 problem

When I start WIN95 with the new NW Client32 login it is by default set to
login to a NDS tree and a prefered NW4 server. If I want to perform a
bindery-login to a NW3.12 server which is NOT in the NDS tree, I go to
the "Connections" option, select the NW3.12 server, click "Bindery
Connection" at which point the NDS part becomes greyed-out (but you can
never delete the default tree as far as I can make out). Fine so far.

Go back to LOGIN screen and login as the user/password etc etc and yes, I
am logged-in to the NW312 (bindery) server as my primary server, with
correct drive mappings etc. HOWEVER, if I right-click on Network
Neighborhood" and display "Network Connections" I find that I am still
NDS authenticated onto my default tree and prefered NW4 server.

The MS 32 Client does not do this - I get NDS or Bindery login but not
both!

Any solution to this? ( In a way it seems quite useful in that I get the
best/worst of both worlds!)

Also, is there anyway of stopping a user by-passing the Novell Client32
login screen and then being able to start WIN95 as a stand-alone copy? I
seem to be able to do this. We have managed to prevent this with the
standard WIN95 network login and would certainly want to prevent our
students getting into (under?) the system without a login verification.

Stuart Phethean

------------------------------

Date: Thu, 2 Nov 1995 00:21:32 -0700
From: Rich Graves <llurch@NETWORKING.STANFORD.EDU>
Subject: Re: HELP!! Win 95 and Novell Netware 4 - Dial Up Connection

>My work computer has Win 95.  It is also part of a network which runs
>on Novell Netware.
>
>My home computer has Win 95.  I want to be able to dial up my work
>computer from home and access files on the shared network drives
>attached to my work computer.  (like I used to be able to do under
>3.11, using Laplink)
>
>I have installed a Dial Up Adapter, Client for MS Networks, Client for
>Netware Networks, IPX/SPX, TCP/IP, Service for Netware Directory
>Services etc etc.
>
>I can connect to my work computer OK but I can only access the local
>drive.  The shared drives are simply not there!!

I think this vexing behaviour is caused by a recently disclosed bug in the
Win95 PPP client and server -- with CIPX, the packet length field is put
into the packet in incorrect byte order.

Try turning off IPX header compression. I believe you can do this on
either the server or the client. The connection will be perhaps 50%
slower, but I think you should be able to see both local and network
drives.

Had you installed Novell's Client32 on your home computer, you would have
found that you could access the network drives, but not the local drive.

Shiva, which developed the PPP client and server for Microsoft, appears to
have made a little oopsie.

rich
moderator of the win95netbugs list
http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html

------------------------------

Date: Fri, 3 Nov 1995 09:53:00 EST
From: Christopher Diebold <cdiebold@ENGLEWOOD.LIB.CO.US>
Subject: Re: Win95 and Novell

>This is not a bug report for the new 32 bit shell because the same
>problem appears for other shells.  Obviously, it's me:
>
>I am baffled.  I loaded the Novell 32 bit Win 95 client on a Win 95
>station which was working with the VLM DOS requester.  SETUP chugged away,
>decided to use the existing adapter and seemed to be OK.
>
>The Novell splash screen came up, but it would not connect to the
>server, so I checked that the frame agreed with the server (I had switched it
>from Auto to 802.3, just to be sure).  The frame type w
>as the only change I made to the network configuration.  The AUTOEXEC
>runs like this:
>
>	CD\NWCLIENT
>	LSL
>	NIC2000
>	\WINDOWS\ODIHLP
>
>I exited to DOS, switched to \NWCLIENT and typed in IPXODI, VLM and
>connected right away.
>
>Switching to the Microsoft Netware Client got me the same results: no
>connection inside Windows, but at the DOS prompt everything was OK.
>
>Removing all network components, rebooting, and trying the Novell 32
>bit client again got me no further.

Have a similar problem.  I am using Intel Ether Pro/10 ISA cards (NDIS
driver).  Installed Client32 and I get the splash screen and no login
prompt.  Tried changing the frame types, but still the same at boot.
I finally gave up and went back to the MS NDS client.  Only problem is
that NWADMIN no longer runs.  I think that the problem could be the
NIC driver and am thinking about figuring out how to modify the .INF
file to include the 32bit ODI driver.

------------------------------

Date: Thu, 2 Nov 1995 15:23:00 PST
From: Sam Linse <SamL@HUMONGOUS.COM>
Subject: Novell Client32 and no Exchange email.

I am testing the Novell Client32 beta and all appears fine during and
after install, but my Exchange will not send or recieve email no matter
what tweaking I do.  Yet another guinea pig here is using it with no
problem.  What gives.  I have worked with MS Mail for some time and have
been using Exchange successfully up to this point.  After I remove the 32
bit client and reinstall the client from Microsoft (NDS or otherwise) I
get my email going again.  Thanks for any help you can give me.

------------------------------

Date: Fri, 3 Nov 1995 00:37:17 GMT
From: "Mr. Mango-Grove" <Yow@OOGLE.ORG>
Subject: Re: Win 95 works like a charm

>I don't know what other problems people are having, but I set up my first
>Win95 client, and it upgraded fine.  I had it logged into my 3.11 server
>and in windows.  I did the upgrade and it rebooted and came up fine.  It
>sees all my mapped drive from the SYSTEM LOGIN script.  I then popped it
>off the net and re-booted and it created a new profile that didn't include
>the network.  So far it works great.
>
>I am so pleased I can't stand it.
>
>I think the key was having the most current VLM upgrade which I did from
>the VLMKT disks and the last ver of DOS 6.22.

Unfortunately, it works like a dog with 4.1.  MicroSoft just released
their 32 bit requester, but who knows whether its bug-free enough to
actually use in production (I know for sure it's not completely
bug-free...)

------------------------------

Date: Fri, 3 Nov 1995 18:43:16 +0000
From: Joao Gunther Amaral <jamaral@ADI.PT>
Subject: Re: NOVELL Digest - 1 Nov 1995 to 2 Nov 1995 - Special issue

I've just installed the Client32 for windows 95, which I downloaded today.

I'm having the following problems:

i) where is the nwuser? doesn't it exist anymore?
ii) everytime the login script executes an external command (#), such as
capturing a new printer, a new dos window opens. Should this work like this?

------------------------------

Date: Fri, 3 Nov 1995 09:43:59 -0600
From: Chad McWilliams <cpi@THOR.NET>
Subject: Re: Client32/Win95 Questions

Ian,

According to Novell, the ability to set up a remote printer on the Win95
station will be addressed in the next beta release of Client32. They will
include a new 32-bit Win95 version of nprinter to accomplish this. Also,
you will be able to use Client32 with a network install Win95, but not
until a later beta (I believe the next also). The only thing about it is
the Client must reside on the local machine (at least as I read it). So
I'm not sure how that will work in the case of using the proms.

To get the long filename support, you must set up a OS/2 name space on the
server. This will enable netware (along with Client32) to support the long
file name support.

And yes, you should be able to log in as another user without a reboot
(just like the Windows client).

------------------------------

Date: Fri, 3 Nov 1995 20:26:15 -0500
From: Archie Spangler <archie@MAILHOST.MNSINC.COM>
Subject: NW Client32 problem

I installed the Novell Client32 with no problems.  I do however have a
problem when I drop to a DOS box and try to change directories on a network
drive.  I cannot change to a directory or cd.. or cd\. When I do try to cd
I get the error "invalid directory".  I can go into the Windows95 explorer
and go all through the directory structure with no problems.  I really
don't understand this problem, I have installed and reinstalled  with no
luck. I am using a 3com 10/100 PCI NIC in a 16MB P5-90.  I am in a mix of
3.11, 3.12, and 4.1.  I login and run the profile script of a 4.1 server.
 I have had to go back to the Microsoft Client for Netware becuse I have
batch files that I cannot even run becuse they might be calling m:\ccadmin
and I am mapped to m:.  If there is a fix to this I would love to be
running the Client32 but until then I do have a job to do so I am going
back to the MS Client.

------------------------------

Date: Fri, 3 Nov 1995 17:37:23 GMT
From: Cameron Myers <cmyers@WDC.NET>
Subject: Client 32 - No Login

I am really stuck.  I installed Client 32 from the network.  It installed
fine, but after I did the reboot, it wouldn't login at all.

It says "can't find Net directory or prefered server"

It also takes forever to open "My Computer" with the flashlight going all
the time.

I'm really in a bind now.  I knew this would happen.

All I wanted to fix was the Form 0 my Win95 kept sending to the printer
even though I had selected Form 1.  I got no response on that post before.

------------------------------

Date: Sat, 4 Nov 1995 05:32:10 GMT
From: "Jeff G." <jeff@TRANSOURCE.COM>
Subject: Re: Novell Client32 for Win95 Released for Open Beta

>Pluses v. Microsoft's NetWare Client and NDS Service:
<snip>

Novell's client32 will support Microsoft's peer to peer file and
printer sharring.  It will not work using printer and file sharing via
netware client, but will work using file and printer sharing via
client for Microsoft Networks.  Client32 can coexist with client for
Microsoft Networks.  Client for Microsoft networks can be configured
to use IPX/SPX protocol.  Hence file and printer sharing will exist
over IPX.

I have been using the client32 for several days and it has been
working succesfully with NASI.  Also has the benifit of working with a
wider range of applications that the Microsoft client for Netware
wouldn't work with.

Client32 also fully supports user profiles and system policies.  Also
supports long file names on Netware servers.

The biggest draw back that I have noticed with client32 is that it
consumes a large amount of memory.  On a machine using 16MB,
everything is runs nicely, but with 8MB, things slow down extremely
compared to using the VLM's or the Microsoft client for Netware.  In
fact, Novell states a min. of 8MB to use their client32.

------------------------------

Date: Sat, 4 Nov 1995 16:45:20 UT
From: Dave Kearns <DKearns@MSN.COM>
Subject: Re: Client32 problems (Me Three)

>>I recently installed Client32 on my Dell P75 computer.  I have a SMC
>>EtherPower PCI network card, and previously had the Microsoft client
>>for NetWare networks installed.  I am using the standard 32 bit NDIS
>>driver for this card that came with Windows95.
>>
>>When I tried sending email using Pegasus mail, I got the following
>>message:
>>
>>Fatal exception 0E has occurred at 0028:C004711F in VXD NDIS(01) +
>>0000417F

<snip>

>I have been getting the exact same Fatal Exception on my computer.

<Snip>

>If you folks are all getting the same error (a fatal error in the NDIS
VXD) wouldn't it make sense to switch to ODI drivers instead?

------------------------------

Date: Thu, 2 Nov 1995 22:20:59 GMT
From: Reg Eberle <rre@THOR.CCA.ROCKWELL.COM>
Subject: Problem Installing Office95 from an NT server with Client32
	 Software Loaded

I have a problem installing MS Office 95 package with Client 32 for Netware
and Client for Microsoft Networks.  The Office 95 package is located on an
NT application server.  When running setup the system slows to a crawl
taking over an hour to get to the custom installation screen.  This problem
dissappears the minute the Client 32 for Netware is uninstalled.

We ran test on other Windows setup programs, all were the 16-bit version of
windows application, these all ran with now problem.  This so far appears
to be a problem with the WIN95 setup programs.  I currently can not prove
or disprove this since Office 95 is the only Win95 package I've got
available.

------------------------------

Date: Thu, 2 Nov 1995 21:30:17 +0100
From: Diego Caravana <canale2@IBM.NET>
Subject: Re: Win95/Novell 32 bit client

>I downloaded the network 32 bit client - removed all network stuff
>from a test Win95 system and fired up the install - near the end of
>the install it started asking for 'disk1-desc' for the following files
>WINSOCK.DLL, NWLINK.VXD, RPCLTC6.DLL, RPCLTS6.DLL, WSASSRV.EXE,
>WSIPX.VXD, and WSOCK.VXD - of course I had no disk1 - so skipped the
>files and finished install. Everything seems to work fine, login to
>4.1 etc. Can anyone tell me why this happened and what all these
>files are for?

These are Microsoft files (found probably in a server directory).
Some (or all) are part of Microsoft Netware Client, so Novell
CLient32 can continue to work.

BTW: I can't remove Microsoft IPX/SPX compatible protocol when I
install Novell Client32. When I remove it, Novell 32bit IPX get
removed, too. So I am stuck with the two protocols and I beat it
that this is the cause of Information System DOS application
malfunctioning (which does'n function properly with M$ Client).
Has anyone this problem?  What do you think about it (i.e. beta
problem) ?

------------------------------

Date: Thu, 2 Nov 1995 22:42:08 GMT-5
From: Martin Kopser <MJK9082@SOO.BWI.WEC.COM>
Subject: Win95 and Novell

This is not a bug report for the new 32 bit shell because the same
problem appears for other shells.  Obviously, it's me:

I am baffled.  I loaded the Novell 32 bit Win 95 client on a Win 95
station which was working with the VLM DOS requester.  SETUP chugged
away, decided to use the existing adapter and seemed to be OK.

The Novell splash screen came up, but it would not connect to the
server, so I checked that the frame agreed with the server (I had
switched it from Auto to 802.3, just to be sure).  The frame type
was the only change I made to the network configuration.  The AUTOEXEC
runs like this:

	CD\NWCLIENT
	LSL
	NIC2000
	\WINDOWS\ODIHLP

I exited to DOS, switched to \NWCLIENT and typed in IPXODI, VLM and
connected right away.

Switching to the Microsoft Netware Client got me the same results: no
connection inside Windows, but at the DOS prompt everything was OK.

Removing all network components, rebooting, and trying the Novell 32
bit client again got me no further.

I'm sure it's something dumb...

------------------------------

Date: Mon, 6 Nov 1995 20:43:33 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Setting Up Windows95 On NetWare???

>Has anyone setup Windows 95 to work along with NetWare 3.12?  I have a test
>server setup where I installed 95 as instructed from the Resource Manual to
>the server.  Now that its on the server I seem to have a problem setting up a
>workstation running VLM to run 95 for the first time after installing it from
>the server.  I get error messages during the first time run of files being
>looked for in the C:\vmm32 directory.  When is this directory supposedly
>created with these files?  What about another resource book on installing a
>client for NetWare using 95?  Is there another book that will give you better
>documentation or if not, please tell me what chapters you used from the
>manual.
---------------
	Please see my message on Win95 in this morning's list traffic. It
references WIN95BOO.TXT in directory misc on netlab2.usu.edu, and that
explains what is what in this area. The MS Win95 Resource Kit is certainly
required reading, but it is not the whole story by any means.
	Here is a Win95 boot floppy, working to a Read-Only NW 3.12 file
server. The client has no hard disk, only a RAM drive C: and a floppy
drive A:.

DOS attrib listing (yes, a tiny cleanup would be nice too) -

  SHR   A:\IO.SYS
	A:\SYSTEM.DAT
  SHR   A:\MSDOS.SYS
    R   A:\COMMAND.COM
	A:\437_UNI.001
	A:\850_UNI.001
	A:\ANSI.SYS
	A:\AUTO.VLM
	A:\BIND.VLM
	A:\CONN.VLM
	A:\DOSRQSTR.MSG
	A:\FIO.VLM
	A:\GENERAL.VLM
	A:\IPXNCP.VLM
	A:\IPXODI.COM
	A:\IPXODI.MES
	A:\IPXODI.MSG
	A:\LOADHI.COM
	A:\LOADHI.SYS
	A:\LSL.COM
	A:\NDS.VLM
	A:\NE2000.COM
	A:\NET.CFG
	A:\NETX.VLM
	A:\NMR.VLM
	A:\NWP.VLM
	A:\ODIPKT30.COM
	A:\PRINT.VLM
	A:\QEMM386.SYS
	A:\QEMMREG.COM
	A:\RAMDRIVE.SYS
	A:\REDIR.VLM
	A:\SECURITY.VLM
	A:\TRAN.VLM
	A:\UNI_437.001
	A:\UNI_850.001
	A:\UNI_COL.001
	A:\UNI_MON.001
	A:\VLM.EXE
	A:\WINPKT.COM
	A:\AUTOEXEC.BAT
	A:\DBLBUFF.SYS
	A:\IFSHLP.SYS
	A:\NET.001
	A:\CONFIG.SYS

content of msdos.sys -

[Paths]
WinDir=f:\win95\user
WinBootDir=c:\

[Options]
BootMulti=0
BootDelay=0
BootGUI=0
Network=1
LoadTop=0
logo=0

section (end) of system login script dealing with Win95 -

if OS_VERSION >= "V7.00" then
	map del s5:
	map ins s2:=f:\win95
	map ins s3:=f:\win95\command
	map ins s4:=f:\win95\user
	#sys:\win95\command\attrib +r c:\command.com
	#sys:\win95\command\attrib +r c:\net.cfg
	#sys:\win95\command.com /c copy f:\win95\user\system.dat c:\
	#sys:\win95\command.com /c copy f:\win95\user\user.dat c:\
	#sys:\win95\command\attrib +r +s +h c:\system.dat
	#sys:\win95\command\attrib +r +s +h c:\user.dat
else
	#sys:\dos\attrib +r c:\command.com
	#sys:\dos\attrib +r +h c:\net.cfg
endif
drive c:


On the boot floppy we also have
config.sys of (first line broken into two for mailing) -

DEVICE=a:\QEMM386.SYS x=a000-b7ff aram=c000-c7ff FR=c800 RAM ROM  NR NX
  vxddir=f:\tools\qemm ext=256 emb=40960
DEVICE=a:\loadhi.sys /r:1 a:\ifshlp.sys
break=on
files=100
buffers=20
dos high
DEVICE=a:\loadhi.sys /r:1 a:\ansi.sys
DEVICE=a:\loadhi.sys /r:1 a:\ramdrive.sys 9000 512 256 /A
shell=a:\command.com /p /e:800

and autoexec.bat of -

@echo off
echo -
set NWLANGUAGE=ENGLISH >nul
copy command.com c:\  >nul
copy net.cfg c:\  >nul
set comspec=c:\command.com >nul
a:\loadhi /r:1 a:\lsl.com /c=c:\net.cfg  >nul
a:\loadhi /r:1 a:\ne2000.com  >nul
a:\loadhi /r:1 a:\ipxodi /d  >nul
a:\vlm.exe /Mx /v0 /c=c:\net.cfg /ps=edu-usu-engrlab  >nul
a:\loadhi /r:1 a:\odipkt30 0 99  >nul
a:\loadhi /r:1 a:\winpkt 0x60 0x63 >nul
f:
login guest
@echo on

	Joe D.

------------------------------

Date: Mon, 6 Nov 1995 15:42:37 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client32 cannot see my server!!

>I installed the Client32 software on my workstation (I am
>using an Intel EtherPro card with the 32-bit NDIS drivers, and
>the MS Client for Netware.)

	Then you do NOT have the Novell client32 material. You
have only Microsoft material.

>The install went fine, however after rebooting, I get a generic
>login message which gets me knowhere. The client does not find
>my server at all.
>
>The NIOS.LOG file states "IPX was not able to bind to any board."

	Once again. Remove ALL networking material from Win95. Then
start fresh and run the setup.exe program from the Novell client32
distribution. If you can, use ODI board material rather than NDIS
drivers. Novell's client32 files will add ODINSUP to fake NDIS
on top of ODI so that MS networking applications will still function.

	Joe D.

>I have tried making some changes to the "Advanced IPX" tab in
>the network panel, to specify frame types and such,
>but nothing seems to make any difference.

------------------------------

Date: Tue, 7 Nov 1995 16:40:08 -0000
From: Pete Wiggins <petew@NDL.CO.UK>
Subject: NetWare Client32 & environment space

I've spent many an (happy) hour wrestling with the Client32 stuff and am
left with the following problem :-

The Novell Login corrupts my environment settings. This looks like the
old known Novell problem - BUT how do I get around it now?  The problem
can have quite severe implications as it tends to trash things like the
WINDIR=3D settings as well as the PATH=3D setting.  ( One of the
side-effects of trashing WINDIR is that the famous DNS problems appear
since the registry settings rely on %windir% !).

------------------------------

Date: Tue, 7 Nov 1995 15:00:34 GMT
From: Ben Stevens <ludd@VBN.COM>
Subject: Client 32 eats up connections, weekends

I'm having slight trouble with Novell's Client 32 (for Win95)

After installing Client 32, I've noticed that one session occupies
more than one seat on the server.  Not necessarily a problem for
the 50 user 4.1 server, but it is devistating for our 5 user 3.12 server.
Has anyone noticed this symptom? Any pointers for resolving this?

------------------------------

Date: Wed, 8 Nov 1995 12:27:18 GMT
From: Phil Williams <jaws@FWB.GULF.NET>
Subject: Re: more client32 probs

>In addition to my prior problems I thought I might add the error codes
>that i am recieving when trying to create a print queue or print server
>thru nwadmin and windows 95 client 32. They are as follows:
>
>NWDS-4.0-612
>
>NEW OBJECT COULD NOT BE CREATED
>
>RETURN CODE 104:-303
>
>PS: I am admin and I have all the sufficient rights and I am able to use
>Pconsole to create the q's and print servers and then when i pull up the
>nwadmin again they are there and I can manipulate them. Also I am not
>seeing the new Application classes that were supposed to have been added
>to the create picklist (win 3.1, win 95, etc...). Is there a newer
>version of Nwadmin, because I did not find one in the Client 32 zip
>file, only a newer nwadmin.ini.

I get the same error.  You can use PCONSOLE from a DOS windows to
create the print objects.  Be aware that if you use NWADMIN and look
at the PRINT LAYOUT under your print server object,  it will show that
the is no print queue assigned.  Even though PRINT LAYOUT  shows that
there's a problem, I can can send print jobs to the queue and the will
be service by the printer.

------------------------------

Date: Wed, 8 Nov 1995 11:43:15 EST
From: Helge_Tengstedt@STRONGLINE-CPH.CCMAIL.COMPUSERVE.COM
Subject: WIN95/NW32 Client Login problem!

This problem might be explained before, but I must admit that I
haven't been monitoring the list very closely the last month or so,
due to below mentioned project.

At our firm, we are currently running a Windows 95/Novell 3.12
pilot-project. So far so good, we have only encountered one small
problem, small - but annoying.

When we login to our Novell 3.12 network, we get some errors executing
our login-script, the errors are as follows:

"LOGIN-4.20.b2c-740: This utility could not execute external program
admi\sys:public\castoff"

Same thing happens with our printer-captures.

Captures and castoff works fine in a dos-prompt, once logged into the
network, so why not in the login-script.

We have looked at various ways to solve the problem, including logging
in via a Bindery connection or just using BIND (in stead of NDS BIND).

Is there someone, who could (probably starting with a deep sigh :-))
briefly sketch what is going wrong, and what could be done to correct
this problem ?

------------------------------

Date: Wed, 8 Nov 1995 14:51:54 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: LZFW / WIN95 /CLIENT32

>Has anyone setup LZFW on a WIN95 station using the 32bit client from
>Novell?  I know that Novell now implements a 32bit ODI stack, but
>LZFW's DI.COM wants to 'link' to a LSL.COM.  The new client doesn't
>load this.
---------
	Last week I put a long message on the listserver about a related
item: how to run the 32-bit client over several low level handlers.
	You can select "use existing ODI driver" in the Win 95 networks
panel, and ensure it's the 16 bit kind when you are done. This will cause
LSL and ODIHLP to be loaded at DOS time (pre-GUI) in autoexec.bat. Be sure
you personally add the ODI board driver (the MLID) between them, and that
NET.CFG is proper and accessible to the LSL. Do not load IPXODI et al.
	For LZFW, run DI.COM after these and before GUI startup.
	The Novell 32 bit client is more than a single piece of code.
The client proper is one section, and it can run over a variety of drivers
including MS' NDIS stuff. The board handler material is another part, and
one can use regular 16 bit MLIDs (with LSL etc), the new CODI 32 bit drivers
(with the LSLC32.NLM equivalent which starts only as the GUI comes up), or
even MS' NDIS drivers. You can also use straight VLMs at DOS level, but not
with the 32 bit client; VLMs are not board drivers.
	Joe D.

------------------------------

>Is there a reliable resource somewhere that describes the process of
>installing Win95 on the server and creating network boot images for
>diskless machines?
----------
	About once every week the same question occurs and the answer
is go to netlab2.usu.edu, cd misc, get three files: win95boo.txt,
win95sap.txt, msoff95.txt. Take it from there.
	Joe D.

------------------------------

Date: Thu, 9 Nov 1995 09:39:18 -0700
From: Bryan Smith <BRYANSMITH@ATK.COM>
Subject: Windows 95 and Netware 3.11

I have WIN 95 connected to a Novell 3.11 server, Netware
Client as default login protocol.

After I enter my password, the Netware Login Script
Processor comes up only half sized with the text running off
the right side of the screen.  I must hit a key (space bar or
any key) on this half sized window to login

Also my Netware Login Script Processor is on top one
minute then the NWLSCON box is on top.  They flip back
and forth till I'm logged all the way in.   I then key-in a
CTRL-C to close this whole mess.

Please....some help us out!

Second WIndows 95 Question:
My Novell server detects what DOS version I am running and
maps all DOS requests to that version already installed on
the Network.  This setup for those folks who do not have a
local hard drive that has DOS installed.   Novell determines
this with the Long Machine Type that is my local
SHELL.CFG file.

What version do I tell Novell?? When we told it WIN95, it
gets ignored.  Same with DOS 7.

I have the Netware Login script to exclude me from this
mapping operation, but I do not want to do this for very user.
Any Advice or suggestions???

3rd Question

I have several WIN NT 3.51 Workstations connected to a
Novell 3.11 server, Netware Client as default login protocol.

I am soon working on getting Win 95 up and running also.

What I would like to know is how to change a complete
Netware volume from 16bit FAT to NTFS??
I am wanting get NT and 95 to read and write to the same
volume.

I understand that I need a NLM driver for both NT and 95.
Could someone tell where to get these drivers, but more
basic than that...could some one explain the mechanics
involved in making all of this work??

------------------------------

Date: Thu, 9 Nov 1995 08:10:21 PST
From: Rob Koper <robkoper@PI.NET>
Subject: Where has my ".." directory gone to ?

I'm using Win95 now with the 32 bits netware drivers. When I go to DOS or
a simple DOS programm, I can't see my ".." directory anymore. Where has
it gone to and how do I get it back ? In the early days of the 16 bits ODI
drivers, the only thing I had to do was putting "show dots is on" in my
net.cfg, but now I can't find such a confiruration file.
Can you help me out. It's annoying me.

------------------------------

Date: Wed, 8 Nov 1995 16:47:45 GMT
From: Cameron Myers <cmyers@WDC.NET>
Subject: Re: Client32 cannot see my server!!

Good God, I have the exact same setup and problem.  If you get an answer,
please forward it to me.  I am dying.  My boss has no net connect now and
I can't seem to get back to the VLM setup.

Brett Gordon <bgordon@gate.net> wrote:
>I installed the Client32 software on my workstation (I am
>using an Intel EtherPro card with the 32-bit NDIS drivers, and
>the MS Client for Netware.)
>
>The install went fine, however after rebooting, I get a generic
>login message which gets me knowhere. The client does not find
>my server at all.
>
>The NIOS.LOG file states "IPX was not able to bind to any board."
>
>I have tried making some changes to the "Advanced IPX" tab in
>the network panel, to specify frame types and such,
>but nothing seems to make any difference.

------------------------------

Date: Fri, 10 Nov 1995 02:23:02 GMT
From: "Albert H. Gilmore" <gilmore@IADFW.NET>
Subject: Re: Client32 cannot see my server!!

Do we have a trend started here with this particular NIC. I beat my head
on the wall all after noon trying to get mine to see the network. If any
one has had success please share.

cmyers@wdc.net (Cameron Myers) wrote:
>Good God, I have the exact same setup and problem.  If you get an answer,
>please forward it to me.  I am dying.  My boss has no net connect now and I

<snip>

------------------------------

Date: Fri, 10 Nov 1995 09:22:48 GMT
From: Tony Nicholls <t.nicholls@NCS.NERC.AC.UK>
Subject: Re: Novell Client32 for Win95 Released for Open Beta

The Novell 32-bit client does not allow user level security via
a Netware authentication server. I'm not worried about not
being able to set up a machine as a novell server, but the lack
of user level security impinges upon the remote admin features
of Windows 95. Of course you can set up the security to
authenticate via an NT server...

------------------------------

Date: Thu, 9 Nov 1995 11:14:39 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Windows 95 and Netware 3.11

>I have WIN 95 connected to a Novell 3.11 server, Netware
>Client as default login protocol.
>
>After I enter my password, the Netware Login Script
>Processor comes up only half sized with the text running off
>the right side of the screen.  I must hit a key (space bar or
>any key) on this half sized window to login

	Appears as if your Win95 installation is a bit peculiar.
Video driver configuration maybe?

>Also my Netware Login Script Processor is on top one
>minute then the NWLSCON box is on top.  They flip back
>and forth till I'm logged all the way in.   I then key-in a
>CTRL-C to close this whole mess.

	Hmmm. Ditto.
	No such problems here of this kind.

>Please....some help us out!
>Second WIndows 95 Question:
>My Novell server detects what DOS version I am running and
>maps all DOS requests to that version already installed on
>the Network.  This setup for those folks who do not have a
>local hard drive that has DOS installed.   Novell determines
>this with the Long Machine Type that is my local
>SHELL.CFG file.
>What version do I tell Novell?? When we told it WIN95, it
>gets ignored.  Same with DOS 7.
>I have the Netware Login script to exclude me from this
>mapping operation, but I do not want to do this for very user.
>Any Advice or suggestions???

	Use OS_VERSION in scripts, not Long Machine Type, for
this purpose. Write the results as part of the script during
testing. Realize that the current NW client32 has a problem and
reports 0.0 rather than DOS7.00.
	Joe D.

------------------------------

Date: Fri, 10 Nov 1995 09:21:28 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Getting SList to ignore Win95 File Sharing

>    With Win95 file sharing, novell thinks that each machine is
>like a file server.  Going into slist show all the computers
>who have Win95 file sharing on it.  Does anyone know of a way
>to block out just the names of the Win95 machines in slist on
>our novell 3.11 network?
----------
	You block them by forbidding people to use Win95 IPX SAP
broadcasts. Not the other way around. Tell customers to use NetBEUI
or RFC-NetBIOS (NetBIOS over TCP/IP), and that's all (and enough).
	Joe D.

------------------------------

Date: Sat, 11 Nov 1995 08:00:00 WST
From: Ped Ristic <RISTIC@COMMERCE.MURDOCH.EDU.AU>
Subject: Re: win 95 remote boot

We have win '95 booting from boot roms.  It is a little complicated
and is not worth starting unless you have more than 10Mbits
bandwidth.  We are running twelve lab machines on one coax segment
which is running at 10Mbits and it typically takes two minutes
to start.

Second, '95 moves away from .ini files altogether and uses
the 'registry' which contains settings for almost everything.
Consequently, each machine will need a registry file and so you'll
need a way to identify each workstation.  They must have their own
read/write copy and you cannot have a central one (although if you
find a way I would be v.interested to know about it).  However, since
you can't boot '95 from dos, you can't use the login script (as we
used to for Win3.1)  So what is used is a file called machines.ini,
(last of the ini's) which is on the boot image, in which is listed the
node addresses and then the paths your remote boot machine needs,
such as the directory of the server installed '95 copy and the
directory of the resgistry file for that node.

We played a lot with these files until we got a feel for it, then
kept on trying until it worked.  There is a lot of playing involved,
but you can make it work well and save on local hard disk
requirements/difficulties.  A nice feature was that '95 can make its
own boot image for you which is great, but in going through their
wizard which detects the type of machine you are running, it kept on
crashing due to some I/O port address conflict, so after contless
retry's we told it to skip that part and it was fine.

Our experience has been that it can be done with a little patience,
understanding and lots of play.  Our users are happy about everything
except the long start up times (which we *hope* to fix with 100Vg or
Fast Ethernet whichever has bootroms).  We also run Office 95 to
complinent '95 which also suffers due the bandwidth limitations.
Overall, '95 is a winner for you users *IF* you have enough
bandwidth.

------------------------------

Date: Mon, 13 Nov 1995 20:49:23 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Win95/NetWare headaches!

>I am trying to setup Win95 on a NetWare 3.11 network.   I managed to
>complete the initial stand-alone intallation after a mere 3 crashes.
>Setting up the shared files/directories on the server went without a
>hitch.   But I have spent about a week (so far) trying to complete
>the workstation installation.
>
>Our workstations are Teco boxes containing:
>	- Intel 486DX2-66
>	- 8MB RAM
>	- No HDD
>	- 1.44MB FDD
>	- SVGA card and VDU
>	- D-Link DE220 network cards
>
>When running ODI drivers, we are using NetWare Shell 3.32.
>
>Initially, when I was following the suggestions made by Joe Doupnik,
>I would get almost through the entire installation.   Just as the
>installation was completing, it would give me this error:
>	Error SU995014
>	Invalid file
>	(0x1396)
>
>After getting that about a dozen times while trying various things, I
>redid the server setup and tried a different approach based on
>instructions in the various help files and the resource kit manual.
>I then started getting a different error:
>	SUWIN   Application error
>	General Protection Fault in module SETUPX.DLL
>	at location 001F:21E2
>
>... And that's where I am at now.
------------
	Punt?
	No, that's too easy.
	We can't tell much from that description, and the whole installation
muddle is so complicated that speculation has to be very brief. Experience
here says when the Plug and Play part arrives let Win95 do full inspection
rather than us picking and choosing components, and select vanilla VGA for
the initial video. Plug and Play is one of the big handicaps; boy is it ever.
The initial memory management can be nothing at all, to let Win95 capture
the machine as much as it wants, and it does want. I did it with QEMM/386.
	Don't let it know about networking during installation. If necessary
protect IRQ 2 from Windows or temporarily use another value until the
installation has finished (then doctor via My Computer, Preferences).
	My msbatch.inf file looks like this:
[SETUP]
InstallType=3
CCP=0
ProductID=Win95-950R6
ProductType=1
Uninstall=0

[NETWORK]
WorkstationSetup=1
DisplayWorkstationSetup=0
HDBoot=0
RPLSetup=0
display=1

[NameAndOrg]
Display=1
Name="Engineering Student Lab"
Org="Utah State University"

	Finally, some error messages are misleading. For example, unable
to write a file because of space limitations can yield another error msg.
	You probably know by now that the SUBOOT directory holds the image
of what will be written to the boot floppy, and thus you can salvage many
items manually for experimenting. Keep an eye peeled for those system and
hidden files.
	Only a few tries at the original system manager's installation is
much better than average, and only a week's complete waste of time is hardly
worth counting, sigh. I say this while showing scars of wasted months. But
keep at it and eventually the green screen will emerge.
	Joe D.

------------------------------

Date: Mon, 20 Nov 1995 20:01:11 GMT
From: acua <acua@IX.NETCOM.COM>
Subject: Re: W95: MS Print Agent for N

>>I've just discovered Microsoft Print Agent for NetWare Networks
>>that is on the Windows 95 CD.  It is supposed to work with their
>>NetWare Client software as an RPRINTER replacement.
>>
>>1. How can I tell it which print queue to poll?  Its properties
>>include settings for NetWare server and print server, but not
>>queue name or number.  Surely it's not configured for only one
>>queue per print server!

>As far as I can see, yes it is!

>>2. How should the printer be configured using PCONSOLE (we have
>>NetWare 3.12)?  Should the type be "Remote Other/Unknown" (as
>>used by OS/2 NPRINTER) or "Defined elsewhere"?

>LPT1: local.

>>Has anyone had success with the Print Agent?  Thanks in advance
>>for any help.

>Yes, I had to set up a print server just for the one printer which is
>defined as being local.  Also you must not capture the Windows95 pc's
>printer port.

This also means that if you use local print servers, Windows 95
installation will disable those servers thereby rendering other from
being able to print to your printer anymore!!!  I know, I've tried
Windows '95 on our Network and that was the only "GOTCHA" that is
keeping us from allowing Windows '95 on our 2 Networks!!!

------------------------------

Date: Wed, 22 Nov 1995 16:05:47 GMT
From: acua@IX.NETCOM.COM
Subject: Re: Printing and Directory problems using Client32

>Ever since I installed the Novell Client32 I can't change directories
>in a DOS [snip]   Also, I can no longer print to a printer that has a
>jetdirect board in it.

If you are using shared printers (i.e. logging in a printer first,
followed by the user in a login script or without a script as in
"rprinter"), you CAN NOT use Windows 95!  It will not work!  This is
why Windows 95 has been banned County wide, in my State!!!!   People
are using printers at their workstation that MUST be available for
others to use via Print Queues and Windows 95 is incompatible to
letting the printer login first - followed by the user.

On changing drives, you have to remap them via "My Computer".

------------------------------

Date: Fri, 24 Nov 1995 09:34:06 MDT
From: "John L. Stevens" <STEVENS@KIMBERLY.ARS.PN.USBR.GOV>
Subject: Re: Novell Client32 "invalid directory"

>I installed the Novell Client32 with no problems.  I do however have a
>problem when I drop to a DOS box & try to change directories on a network
>drive.  I cannot change to a directory or cd.. or cd\. When I do try to cd
>I get the error "invalid directory".  I can go into the Windows95 explorer
>and go all through the directory structure with no problems.  I really
>don't understand this problem, I have installed and reinstalled  with no
>luck. I am using a 3com 10/100 PCI NIC in a 16MB P5-90.  I am in a mix of
>3.11, 3.12, and 4.1.  I login and run the profile script of a 4.1 server.
>
>I have had to go back to the Microsoft Client for Netware becuse I have
>batch files that I cannot even run becuse they might be calling m:\ccadmin
>and I am mapped to m:.  If there is a fix to this I would love to be
>running it.

I have run into the same situation.  While in a DOS session,  if you
use md \test  to create the test subdirectory ( note lower case) and
then try to copy something into it - your get invalid directory.  If
the subdirectory is created using MD \TEST  (caps) and try to copy
into TEST - it works.  Go figure.  There is a missing UCASE$ or
equilivalent in the 95 code.  The subdirectory displays at the prompt
in either lower or upper case depending on how it was originally
entered. The standard DOS prompt is always in CAPS.

------------------------------

Date: Tue, 28 Nov 1995 07:13:10 -0600
From: Steve Selaya <sselaya@KUMC.EDU>
Subject: Re: Client32 problems -Reply -Reply

Novell has posted the problem in their FAQ, although they have not
posted any solutions.  The only way I got it to work is by using the ODI
drivers.  If you look at the readme file that came with the 32 bit client,
it will tell you how to do it.  Basically, you have to take the comment out
next to the odismc.inf line in the nwsetup.ini.  You will have to provide
the smcpwr.lan file which is on the SMC disk that came with your card or
you might want to download the latest one from the SMC site.   You should
also remove all of the network drivers from the network option in Control
Panels and reboot your computer (that way the setup program wont try
to use the current network settings) and then run the Novell 32 bit client
setup program.  The ODI drivers seemed to slow network access up
some though compared to the NDIS drivers.   You may just have to wait
until Novell or SMC fixes the problem or use the Microsoft 32 bit service
until the next beta comes out.  Another solution (I suppose) is to replace
the SMC with another brand.  Also, if you access programs off of an NT
server as well, access is very, very slow.  Novell also knows about that
and says that they will fix the problem in the next release.

The following is from Novells FAQ:
http://netwire.novell.com/home/client/client32/faq.htm

Q: I am getting the error of :
"An exception 0E has occurred at 0028:C37AB5DB in VxD---. This was
called from 0028:C13F5980 in VxD---. It may be possible to continue
normally.A fatal exception 0E has occurred at 0028:C37AB669. The
current application will be terminated."
Why am I getting this error and what can I do to prevent it?

A: Novell has isolated the problem to a limited number of NICs and the
corresponding NDIS driver. The exception error only occurs when you
are running with one of these specific cards and using the corresponding
NDIS driver. The solution to the problem is to add an ODI driver in the
Network Control Panel and remove the NDIS driver. For instructions on
installing ODI drivers, refer to the readme.txt that is provided with the
open beta client. This information is detailed in section 9.0 - ODI and
NDIS Support.

------------------------------

Date: 05 Dec 95 08:37:03 PST
From: (Jay McSweeney) McSweeJ%62SVS.MCCHORD@mhs-gw.mcchord.af.mil
To: netw4-l%bgu.edu@mhs-gw.mcchord.af.mil
Subject: Re: NETWARE CLIENT 32

<various problem symptoms deleted>

Did you de-install the Microsoft NDS Client first and go back to VLMs?
If you didn't you're hosed...  Go back and reinstall VLMs then make
sure all your Clients can be seen by Win95, and so forth.  Once you sure
your VLMs work right, then do the Client32 install and follow the
instructions to the letter.  I had the misfortune you have experienced in
your situation and learned the above from trying it.  Works perfect.

------------------------------

Date: Thu, 14 Dec 1995 14:41:43 -0500
From: Kevin Hodgson <kevin@CASEWARE.COM>
Subject: MicroSoft Enhanced Password Cache Security Update for Windows 95

This update is an enhanced security component that substantially
strengthens the encryption used for the Microsoft Windows 95
password cache. The new component uses a 128-bit key, increased
from a 32-bit key in the previous version. The new component also
includes enhancements to the way passwords are stored in the PWL
file.

     The previous PWL file will be automatically upgraded to the
     new format.  This component replaces the MSPWL32.DLL and NET.EXE
     files.  NET.EXE, which is usually used from the command line, will
     no longer use the password cache=97users will be prompted for
     passwords while using NET.EXE.=20

By using the new component, customers will have a PWL file that is
very secure. In fact, with the new 128-bit security, the new
component is 2^96 (2 to the 96th power) times harder to decrypt.

Background

Windows 95 uses an optional caching mechanism to store network
passwords on a user's machine. When a user first types and saves a
password while connecting to a password protected resource, the
user can choose to store the password in a local password list file.
Subsequent logins with a Windows 95 password unlocks the list and
associates those stored passwords with the Windows 95 password.
If the user does not choose to use password caching, they must type
the passwords each time they connect to a password protected
resource.

Recently, an algorithm was posted on the Internet which could be
used to compromise the security used in the previous version of the
password list file. If someone had access to the password list file on
the hard disk of a Windows 95 machine and the decryption algorithm,
they may have been able to perform operations on the file that could
generate the unencrypted password(s).

After installing this new component, the password file will be well
protected against security violations.

The address for the upgrade is:
	http://www.microsoft.com/windows/software/mspwlupd.htm

------------------------------

Date: Mon, 18 Dec 1995 19:00:23 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Client32 beta, update is here

	Rev B of Novell's Client32 software for Win95 is coming over the
wires at this time. You can distinguish it by filenames ending in "_b"
rather than "_a" for the first open beta. Files for disk and network
installation are in directory client32\win95, which on netlab2.usu.edu
appears under the "netwire" heading.
	These files are about 5MB each so choose one and hang in there
while the Internet chips away at them. If you go to ftp.novell.com and
relatives expect throughput around 0.6KB/sec or so, and thus you may
want to contact a nearby mirror for speedier transfers. The Internet is
not getting in better shape with time.
	Unpacking... I think you may want to make a clean reinstallation
of the Client32 distribution files for the network installation method
because the directory structure is different this time; everything shows
up under subdirectory English.
	Joe D.

------------------------------

Date: Tue, 19 Dec 1995 06:26:51 -0500
From: "Thomas E. Costigan Jr." <costigante@INTERRAMP.COM>
Subject: Seek Feedback on Client32: Oportunistic Locking Problem.

Back in early October, when I got my grubby paws on a pre-beta of the Novell
Client32 for Windows 95, it worked fine but cause one *little* problem: when
things got busy on our five-server, 700 user LAN (NW 3.11), when reading cc:
Mail, the client cause a "fault protection error" (or something like that)
and this more-or-less hosed the cc:Mail database, requiring a restoration
from backup.  Being a jerk, I allowed this to happen twice (just to make
sure that the Client32 was the culprit), much to the consternation of my
colleagues.  Note well: this was with the pre-beta client.

When the "official" beta client came out, we had already evaluated the
Microsoft Service for NDS which appeared to work well, supporting both the
proper reading of Novell 3.11 login scripts and the traversing of our
prototype NetWare 4.1 tree.  So, we decided to cast our fate with the MS
client for the roll out of Windows 95 for the masses.   (Besides, when the
"official" came out, I had to go on duty travel to Trinidad and Barbados,
tough job, I know).

Well, we have since discovered that the MS Service causes two significant
problems for us: 1) it does not support TTS file locking in our in-house
FoxPro 2.6 application: a Windows 95 client cannot gain access to a file(s)
that have been locked by TTS, all kinds of silly errors are returned such as
"file read error" and "file does not exist" even after the TTS transaction
has ended on the other workstation; 2) the MS Service did not support a
series of Novell print queue routines that we had developed: when you
selected the routine, the DOS session would just hang.

Well, in desperation, we took a look at the "official" Novell Client32 beta.
 Somewhat to our surprise, both of the problems described above disappeared!
!  No problem with TTS locking; no problem with print queue management.

The problem is, if we switch now to the Novell Client32, what will happen to
our cc:Mail database??

In reading the FAQ that came with the product, it mentions something about
the problem that we experienced and that the possible solution was to turn
off the "Opportunistic Locking" option under the Advanced features.  I have
noted, while using the Novell Client32 in "quiet" times on the LAN to read
my cc:Mail, that it is definitely faster and snappier than the MS
Client/Service.

I am curious, naturally, if any of you have any experience and/or opinion
with the Novell Client 32 (I've now upgraded to the 15 December 1995
revision) with cc:Mail and/or have an experience or opinion regarding this
"Opportunistic Locking" problem.  Perhaps the only was to prove, one way or
another, is to use the client on the LAN.  Thursday morning, after our
Wednesday night back of the cc:Mail databases, seems like a likely candidate
now (hey, if I hose the system again, it was backed up last night and being
close to Christmas, not many people are here now anyway).

---------

Date: Tue, 19 Dec 1995 07:20:52 PST
From: "Ferrell, Bruce" <bferrell@SMTPGATE.LEVEL1.COM>
Subject: Re: Seek Feedback on Client32: Oportunistic Locking Problem.

Thomas,

We have a few systems running the Novell 32 bit client for '95.  It
seems to work well with cc:Mail for Windows v2.01/2.22... So far.

I got a good laugh over Microsofts client not working with a Microsoft
product. :-)

------------------------------

Date: Tue, 19 Dec 1995 22:39:13 -0600
From: John Walker <John.Walker@SOUND.NET>
Subject: Re: Seek Feedback on Client32: Oportunistic Locking Problem

<large omission>
>I am curious, naturally, if any of you have any experience and/or
>opinion with the Novell Client 32 (I've now upgraded to the 15
>December 1995 revision) with cc:Mail and/or have an experience or
>opinion regarding this "Opportunistic Locking" problem.  Perhaps the
>only was to prove, one way or another, is to use the client on the
>LAN.  Thursday morning, after our Wednesday night back of the cc:Mail
>databases, seems like a likely candidate now (hey, if I hose the
>system again, it was backed up last night and being close to
>Christmas, not many people are here now anyway).
>
>Thomas E. Costigan Jr.
-------
I have about a dozen workstations up and running with client 32.  I
expect to put 35 more on by 10 Jan.  It seems to be working great.
No problems of locking files or anything of that sort.  (sorry we do
not run cc:mail, we use groupwise)

Server 1: Pentium 133 with 32 megs running Netware 4.10
	Buslogic PCI controller
	3Com  PCI 590 cards
	2  2gig harddrives mirrored

Server 2:  Pentium 133 with 32 megs running Netware 3.12
	Buslogic PCI controller
	3Com PCI 590 cards
	2 1gig harddrives mirrored and duplexed

Setup is server installed from server 1 with only the shared files and
the files needed to start windows95 loaded onto workstations.  Everything
else is loaded from the server.  I have had no problems to speak of.  The
biggest headache was getting it all setup.

Now if Novell would hurry up and release the update for remote
printer and or nprinter..

------------------------------

Date: Wed, 20 Dec 1995 06:43:35 GMT
From: Ron Wilson <Ron@IHUG.CO.NZ>
Subject: Re: Seek Feedback on Client32: Oportunistic Locking Problem.

Novell Client is definetly superior to MS Client. It also allows
things like selecting login scripts or not and other goodies in the
advanced options.
It does not like Faxserve but I guess Cheyenne will solve that. Other
than that it is great

>Thomas E. Costigan Jr. wrote:

[Floyd: see above]

------------------------------

Date: Wed, 20 Dec 1995 02:07:15 GMT
From: Buddy Shipley <buddy@VAIL.NET>
Subject: Re: Is Novell healthy?

>The serious technical competition is Banyan Vines and DEC Pathworks.
>MS is hardly a networking company, despite the intense brainwashing that
>occurs, but they are likely to grab lots of dollars anyway.

I agree that Novell's NOS is technically superior to the competition
and that Banyan Vines has always been that real competition --
although Banyan Vines is slow and its client s/w is a pig.

 MS history with networking has been less than stellar, yet they keep
trying -- relative to NetWare, 3+ Share was junk -- (a mere DOS
application), LAN Damager was junk (which required OS/2 which until
recently was junk), and now we have Windows NT Workstation and NT
Server.

NT, while still wedded to LAN Damager, is a very good product. It
seems to require more computer resources than NetWare to accomplish
the same thing, but it's quite nice. The downside is that the keys to
the kingdom of all MS Networking are inextricably bound to
NetBIOS/NetBEUI -- a non-routable toy protocol. MS does support IPX or
TCP/IP as alternative transport protocols, but portions of  NetBogus
are still encapsulated within the IPX or TCP/IP protocol.

And then there's DEC Pathworks.  Why even mention this?
This system has been referred to -- how you say? A Dog?
The intent is to employ a VAX as a file server?!  Not the best use of
a VAX and a decent NetWare server will run circles around a VAX acting
as a  file server.  A VAX is a multiuser host -- let it do what it
does best. There are just so many other better options.

Back to Novell vs Microsoft.
Novell is unfortunately in retreat mode.
They are selling off pieces of the company in what appears to be an
attempt to make Novell appear more appealing to IBM.  When (or if) the
Big Red buyout happens, IBM may either become a true competitor to MS
with a complete product line from OS, to NOS, to App Suite, to
distributed management & workgroup facilities. Or IBM could blow it
completely, in which case we will all be sending our bucks to Captain
Bill.

------------------------------

Date: Tue, 26 Dec 1995 16:10:36 EST
From: Christopher Diebold <cdiebold@ENGLEWOOD.LIB.CO.US>
Subject: Re: (no subject)

>I recently added a Windows 95 client (using Novells 32 bit beta client)
>to our 4.1 network.  Everything seems fine except the user has to login
>using the full context login name.  It seems that the net.cfg file is
>not being utilized to put in the specified name context.  If anyone has
>an idea on what is happening, I would appreciate it.

Yep, the net.cfg file is not used.  Go to start--settings--control
pannel--network.  Check the properties for Novell Netware Client32.
You will be able to specify the preferred server, default context, etc.

------------------------------

Date: Wed, 27 Dec 1995 08:58:30 -0800
From: WinNews@Microsoft.com
Subject: WinNews - Vol. 2, #22 - Canadian Edition

For the latest, tips, techniques, bug fixes, and advice
that will help you get the most out of Windows 95, check
out IDG's WINSURFER on-line newsletter.  Published monthly
on the world-wide-web, WINSURFER features solutions to
various issues.  For example, the December WINSURFER
features articles that include helping you:

* take full advantage of the Windows 95 Dial-up Server
* use Hardware Profiles to change your hardware
   configuration on the fly
* back up the Windows 95 Registry
* uncover the many uses of setup switches in Windows 95
* deal with CD-ROM drives
* configure Windows 95 to work properly with removable
    hard drives
* explore Windows 95 3-D animation software
* run DOS applications not designed to run under Windows
* figure out if you need to upgrade your hard disk utilities

To check out a free issue of WINSURFER, go to the
WINSURFER site on the World Wide Web at:
    http://www.idgnews.com/win95

------------------------------

Date: Wed, 27 Dec 1995 20:44:45 -0800
From: tracy pillsbury <tracy@TECH-REF.MV.COM>
Subject: Win 95' Mapping

>I recently added a new workstation running Win95 to my NW 3.11 server.  I
>added Netware Client 32 today and I appear to have no problems accessing my
>server.  I opened a DOS box and ran my usual batch files (from my previous
>DOS configuration) to map the drives to run both my Foxbase database
>application and WordPerfect 6.0a - both DOS applications.  The mappings appear
>correct however when both applications started but either locked up or
>wouldn't run correctly.
>
>Is there a new way to map the drives from Win95?  These applications are
>running fine from my other workstations.  Any suggestions or good sources for
>help.

Throw away the DOS boxes.

Go to "My Computer" or "Network Neighborhood" and click on the
disk drive icon.

click on the Path Box and then type the path to the Resource you want.

or...

Create a shortcut to this item and go into properties by clicking once on
the icon and then, with the pointer on the icon,
click the right Mouse button once, Select PROPERTIES.
Go to Program, then go to Advanced.

If this program needs to be run in DOS then select MS DOS MODE.

If this program needs special sets and drivers then select "specify new
MSDOS configuration and type in what is needed.

If you still have a problem, write to me direct as this is NOT an Netware
problem and should not be on this list.

------------------------------

Date: Thu, 28 Dec 1995 23:12:42 +0300
From: "Alexander E. Arm" <alarm@MODULE.VYMPEL.MSK.RU>
Subject: Re: Win95 vs NW4.1 Usertools

>The Usertools utility provided a function to send a short message to a
>user.  However Usertools does not function in Win95 due to it's functions
>being replaced by "Network Neiborhood".  I have not been able to find out
>how to send a note or message to a user.  WHere has this function been
>moved to ?

You still can use NWUser if you place

Win95AllowDRVUI=1

line in [Restrict] section of NETWARE.INI in your Win95 directory.

------------------------------

Date: Wed, 3 Jan 1996 18:44:53 +0300
From: "Alexander E. Arm" <alarm@MODULE.VYMPEL.MSK.RU>
Subject: Re: Client 32 & RCONSOLE problem

>>After I installed the 32 bit Client, I haven't been able to use the
>>RCONSOLE program, all I get is an empty server list. Is this a known
>>problem ?
>
>Yes, the same problem here. All I got was an empty server list. That was
>with the latest beta version of 32 bit client, the one before that I had
>no problems with. Also I can't watch remotely other workstations anymore.
>I use a program that works only over IPX and not uses Netbios. That too
>worked fine with the beta before.

Have you tried what Client32 FAQ suggests (below)?

Q: Why are Rconsole and other 16bit IPX/SPX applications unable to connect
to or display all servers?
A: Rconsole and other 16bit IPX/SPX applications will send packets or
communicate using the primary board. Client32 can bind IPX to more than one
frame type. By default Client32 will Auto detect the IPX frame type to be
used for the primary board. If this primary Board Frame type is not the one
needed for Rconsole or other 16bit IPX/SPX applications problems may occur
in finding or connecting to servers. These issues can be resolved clicking
on the Network Icon in Control Panel and going to the "Novell NetWare 32-bit
IPX Protocol Properties" and selecting "Advanced IPX ". Then use "Primary
Logical Board" and change "Frame type:" to the correct one needed for your
application. (ie. Ethernet_803.3 , Ethernet_802.2, Ethernet_II or
Ethernet_snap)

---------

Date: Wed, 3 Jan 1996 07:40:07 -0800
From: Mike Donelson <mdonelso@TRMX3.DOT.CA.GOV>
Subject: Rconsole and Win95

Set the primary protocol to the correct frame type.

This can be set in CONTROL PANEL:IPX 32-BIT PROTOCOL FOR NOVELL
NETWARE CLIENT 32:ADVANCED IPX:PRIMARY LOGICAL BOARD.

This will also fix any 16 bit app problems in regards to frame type.

------------------------------

Date: Fri, 5 Jan 1996 22:10:58 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Novell 2.2 and Win95

>Does anyone know if there is a patch that will allow Novell 2.2 to work
>with Win95?
----------
	I don't think you mean quite what you wrote. First, it's "NetWare"
the product, not Novell the company. Second, NW 2.x will work with Win95
clients. Third, I suspect what you intended was the long filename stuff
from SOME Win95 programs, and to that the answer is no way (no OS/2
namespace on NW 2.x). But you don't have to use long filenames with Win95
and pgms, as I demonstrate daily in a large student lab. MS would rather
force you to lfn, but you don't have to cooperate. To see how to subdue
MS Office 95 have a look at file msoff95.txt in directory misc on
netlab2.usu.edu.
	Finally, that graceful MS term "patch" is brainwashing. There is no
patch involved. They mean load OS/2 namespace, and that is hardly a patch.
	Joe D.

------------------------------

Date: Thu, 11 Jan 1996 00:37:11 -0800
From: rgrein@halcyon.com (Randy Grein)
To: netw4-l@bgu.edu
Subject: Re: Drive mapping connection software

>Does anyone know of some software that, when inserted in the startup
>folder of windows 3.1 or 3.11 will reconnect logins and map drives.

Hold tight for the 32 bit client from Novell. The Win95 version is slated
for release 2/2/96 with the DOS/WIN version out about a month later. I
guarentee you'll like the results!

A brief list (I've got a 9:30am ECNE/Master CNE update test) of features:
 - Runs login scripts (if desired)
 - Multiple simultaneous tree logins
 - Contains the new application DS objects - A single DS object that can
   be used to run applications, and provides the slickest software
   distribution I've ever seen!
 - Uses 32 bit software - NLMs, LAN drivers, etc. at the client.

The beta is available now on NetWire, web and ftp and is very clean.

There's only supposed to be 2-3 very minor alterations made before the
release.

------------------------------

