
------------------------------------------------------------------
NOV-W952.DOC -- 19961029 -- 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: Thu, 18 Jan 1996 13:23:41 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Netware 4.1, Windows 95, and OS/2 Name Space

>I checked the FAQ and did not find anything on this. Basically, our
>situation is this, in the next couple of weeks we will be upgrading
>our 3.12 250 user server to Netware 4.1 500 user. Currently, we do
>not have any type of name space loaded on any of our volumes. Past
>experience with a server that had NFS name space loaded was not very
>good, since it took significantly longer to mount the volumes.
>Therefore, we have generally avoided name spaces. (Granted past
>experience was with a SystemPro with a 386 processor, and our
>4.1 server will be a Proliant with a Pentium, lots of memory, and
>a fast disk system, so maybe the mounting thing is less of an issue.)
>
>My question is this:
>We have a few Windows 95 clients. In general we have discouraged the use
>of Long file names and will probably continue to do so as long as we
>have a preponderance of 16-bit applications around. I am aware that
>Novell's solution for long file names is to use OS/2 name space.
>I am sure over time we will get people trying to save long file
>names to the server drives. I had thought that if something happens
>the worst case is their file loses it's long file name and it reverts
>to an 8.3 name. No big problem - we told you not to use long file names
>anyway.
>
>However, our vendor is telling us that if you have files with long file
>names on your server and do not have OS/2 name space, and your server
>crashes such that you are required to do a VREPAIR, you can have your
>volume trashed such that you have to recreate your volume and reload
>it from your backups. Is this true? I don't like the idea that someone
>could cause that kind of problem on my server, just by saving a file
>out there.
------------
	I too have forbidden long filenames on my public servers, and
have not regretted it.
	The last paragraph makes little sense. Vrepair deals with files on
the server, not with what a client application wants to pass to the server
as a filename string. Long names simply will not exist on the server if
you provide no OS/2 name space support. Use NDIR /LONG to see namespace
renditions of filenames. I have Win95 running just.about.everything on
NW 3.12 with no long filename support and so far no problems.
	However, installing MS lead programs runs into problems with setup.exe
insisting upon converting us heathens to LFN or die. The solution is to
install on a local disk and then DOS COPY to the server, as indicated in
MSOFF95.TXT in directory misc on netlab2.usu.edu for MS Office 95.
	Maybe your vendor should also spread the rumor that Win95 is
really the "green screen" virus which is guaranteed to eat your machine.
Makes as much sense, maybe more because it really does eat your machine.
	Joe D.

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

Date: Fri, 26 Jan 1996 14:37:13 -0800
From: Donovan Bray <DBRAY@BASS.CUESTA.CC.CA.US>
Subject: File Handles with Client 32

We are installing RecWare Pro, a Registration Management system on a
Netware 4.1 file server.  It appears to use a FoxPro for Windows database
structure.

The installation instructions say that workstations need at least 100 file
handles to operate, and indeed they do.  The problem is I cannot seem to
get enough file handles when I am using Client 32.

According to Novell Technical Information it works thusly:

Q: How does the Client32 for Windows 95 deal with file handles and how can
they be increased?

A: Windows 95 uses the number of files indicated by the FILES= parameter
in the CONFIG.SYS. The default and minumum required value is 60 files. The
remaining maximum of 195 file handles are then available for use by
Client32 (255 files is still a limitation for each individual PC). Thus to
maximize the number of files available for Client32, the FILES= parameter
should be left at the default value of 60. Due to limitations in the
current open beta client, a maximum of only 153 files can currently be
used. This limitation will be addressed in the next refresh of Client32.

I've tried setting the files=60, and RecWare still reports not enough file
handles.  I've also tried setting files=100, which should leave 155 files
for netware, of which netware can only use 153. RecWare still reports not
enough file handles.

Is it that the 153 limitation is on ALL file handles. Meaning setting the
file=100 would only leave 53 file handles available to the network?

The people who make RecWare, don't have any knowledge of Client 32, or even
Win95 for that matter, so they were'nt much help.

And isn't 100 file handles for a single application a little excessive??

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

Date: Wed, 31 Jan 1996 13:23:27 -0600
From: TIM W CARTER <B4IMRTWC@SMTP.LMK.USACE.ARMY.MIL>
Subject: Rprinter with Windows 95 -Reply

RPRINTER works fine with the VLMs(1.2).  You have to run control
panel and delete your network setup.  Reboot in MS-DOS mode.  Run
install routine for VLMs.  Start Win95 backup and from control panel set
your network to Shell 4.0.  Add RPRINTER to the AUTOEXEC.BAT and it
should start working.

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

Date: Thu, 8 Feb 1996 19:08:38 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Rprinter with Windows 95

>> Windows 95 is incompatible with rprinter.  You can NOT host a printer
>> at your PCs anymore. You need to purchase dedicated print servers in
>> order to print via Novell and Windoze '95!
>
>RPRINTER does not work with Win 95.  I don't think Novell has
>written NPRINTER for Win 95 yet.
>
>BUT, Microsoft provides "print agent for NetWare networks" on
>the Win 95 CD in \ADMIN\NETTOOLS which can take jobs assigned
>to a NetWare printer and put them into one of its internal
>queues.
>
>THE CATCH:  You can specify via Print Manager which NW server
>and which NW print server BUT NOT which printer.  The MS print
>agent always prints jobs for printer 0.  So you can have only
>one Win 95 PC per NW print server.
>
>Michael Strasser
--------------------

	Just a big word of CAUTION here. If you let Win95 advertize file
and print services over IPX you are in big trouble on the network. *Don't*.
The Win95 machine will advertize itself as a NetWare File Server, and it
isn't. This matter occuppied the trade press for months late last spring
and this summer, with me doing the public speaking and a lot of people
in the background sharing the worrying.
	You can read the best statement available from Microsoft on the
matter by getting file win95sap.txt from directory misc on netlab2.usu.edu.
It is a reply to me from one of the MS engineers writing that part of Win95,
and he was gracious enough to go into detail and let the material be available
publically. I've removed the personal comments and left the public part in
the above file.
	My site has strictly forbidden IPX advertizing by Win95, and we are
glad we did. The Novell Client32 for Win95 has also removed that capability,
thank goodness.

	The message again is never let MS Win95 advertize file/print services
over IPX.

	Now, what do you do about r/nprinter? I dunno. I avoid both (Ok Jon,
nprinter is signficantly better; it's the protocol that is very weak). The
common recommendation is acquire an old 286 and up. Much much better is to
get one of the cute tiny multiprotocol printer boxes, and set that up near
the people wanting the printer at hand. Those tiny boxes are not very
expensive and they work well with NetWare. There are such boxes now coming
on the market with NW 4 NDS support too.
	Joe D.

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

Date: Tue, 13 Feb 1996 18:26:36 GMT
From: "Arthur B. Delos Santos" <artdls@COMMUNITY.NET>
Subject: Rprinter with Win95

Q. Does Windows 95 support the NetWare RPrinter tool?

A. Windows 95 does not support the RPrinter tool. However, Windows
   95 does include a tool called Microsoft Print Agent for NetWare
   Networks. This tool is similar to the RPrinter tool and allows
   computers running Windows 95 to spool print jobs from a NetWare
   print server to its local printer. Instructions for installing
   this tool are contained in the Prtagent.txt file. This file is
   located in the Admin\NetTools\PRTAgent folder on the Windows 95
   CD-ROM.

But, the OEM version of Windows 95 does not contain this directory.
You will need a resource kit. You are welcome to call Microsoft
at 800 426-9400 foror information.

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

Date: Wed, 14 Feb 1996 16:31:47 GMT
From: Mischa Melis <vincent@A1.NL>
Subject: Re: Personal Netware

>Does anyone have Windows 95 INF files for Personal Novell or know where
>I can obtain them?

Q. How to login with Windows 95 on a Personal Network Server

1. Load Windows 95;

2. Click Start, Settings, Control Panel;

3. Dubbel-click on Network;

4. The Network Control Panel should not have any network
components installed. If there are Network components installed,
remove them. You can install them back if Windows 95 is running as an
Client of the Server;

5. Click Add;

6. Click Client;

7. Click on Novell. You will see two options under Network Clients;

8. Click Novell Netware ( Workstation Shell 4.0 and above [VLM] );

9. Click OK;

10. Click on the Identification Tab. If the names for your
Computer and Workgroup are blank, you will need to fill them in at
this time. You must also type a short description of your Computer.

11. Click OK. Windows 95 will setup to run with the VLM's.A System
Settings Change dialog box will be displayed when the
configurationprocess is complete. If there is asked for the
Installdisks of Personal Netware or Netware you must click OK and then
stop the        installation. Click NO to restart the Computer. There
are a few more steps that need to be performed;

12. From a Dos box edit the next files : C:\Autoexec.bat and
C:\Nwclient\Startnet.bat

They must Contain the following Commands :

	Autoexec.bat :

	@Echo Off
	Path    C:\Nwclient;C:\Windows;C:\Windows\Command;C:\Dos;
	Set Temp=C:\Dos
	C:\Nwclient\Startnet.bat


	Startnet.bat :

	@Echo Off
	Set Nwlanguage=English
	C:\
	Cd Nwclient
	Lh C:\Dos\Share
	Lh C:\Nwclient\Lsl.com
	Lh C:\Nwclient\Ne2000.com ( Or Appropriate MLID Driver )
	Lh C:\Nwclient\Ipxodi.com
	C:\Nwclient\Vlm
	C:\Nwclient\Net Login [ Username ]
	C:\Nwclient\Net Map [Drive-letter] [Workgroup] [Sever-name]
	C:\Nwclient\Net Capture [Port] [Printer-name] [Server-name] S=
	C:\Win

NOTE :  In some cases, Windows 95 will insert lines in the
Autoexec.bat to load the Novell Odi Drivers even though these files
are being loaded from Startnet.bat. Check your Autoexec.bat and remove
them.

13. Unpacking Installation-files from the Install-disks :

Copy Punpack.exe off the First Installation Disk of Personal Netware
to a Tempory Diretory of your Harddisk. Copy the next Files ( Disk 5
of the Installationdisks ) to the same Tempory Directory :
netware.38_, Netware.dr_, Netware.hl_. Then you have to Unpack those
files. Type Punpack Vnetware.38_, Punpack Netware.dr_, Punpack
Netware.hl_. If the Files are Unpacked copythe Unpacked Files to your
Windows System Direcory.

14. The System.ini file also needs edited before rebooting. In the
[386Enh] section make the following modifications :

Change:                                        To:

TimerCriticalSection = 10000            TimerCriticalSection = 500
ReflectDosInt2A = 0                     ReflectDosInt2A = True

15. To Print to a Personal Netware Printer the following steps
need to be completed :

- Click Start;
- Click Settings;
- Double Click on Printers;
- Double Click on your Printer Icon ( If there are not any
Printers, you will need to add one at this time );
- Select Printers from the pull-down menu, Select Properties
and then click on the Details tab;
- Once in the Details Screen Select Add Port. Select the
other radio button and highlight local Port. Click OK;
- In the Port Name entry box, type LPT1.Dos and Click OK;
- This should take you back to the Printers Property Screen.
Be sure the Print to the following Port: has Lpt1.Dos
(Unknown Local Port) in it. Click on Apply and then OK;

16. You will now have to Reboot your Computer. If there is an
error message that a file could not be found or the registery or the
System.ini Point to that file. You have to search to that file on the
Installationdisks of Personal Netware, Unpack it as descripe at point
13 and copy it to your Windows System Directory.

17. Now you can login with Windows 95 ( as a Client ) to a
personal Netware Server.

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

Date: Fri, 16 Feb 1996 09:30:14 -0800
From: Ken Nakagama <nakagama@ix.netcom.com>
To: netw4-l@bgu.edu
Subject: Tylenol for WIN95

The win95 Service Pack 1 is available for download at:

http://www.microsoft.com/windows/software/servpak1/complete.htm

The server very busy.

Note: the service pack is larger than the origial Win95.  14 disks.

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

Date: Tue, 20 Feb 1996 22:12:58 -0600
From: Tim Winders <twinders@SPC.CC.TX.US>
Subject: Re: Help w/Client32 and Dial-up to ISP

>I have a 5 user Novell 3.11 network, all stations using DOS 6.22 w/ IPX & NETX
>except for me -- I wanted to upgrade to win95.  I am pleased with most of what
>I see and do with win95 but I am still VERY baffled in getting both the win95
>workstation (mine) to connect to the novell lan and also connect via dial-up
>to a local ISP.  I was told to upgrade to Client32.  I did.  I finially got
>this to connect to the novell server (I had an old SMC 3016 lan card - got the
>drivers and finially got it cook'n).  But when I attempt the dial-up, the
>script connects me to the ISP but I do not get any communication, i.e,
>Netscape, eudora, telnet, etc. does not respond.
>
>Before I installed Client32, I was able to use my old Trumpet winsock to
>connect to my ISP -- I can't even do that now!

WHAT!  With Netware 3.11 you DO NOT need Client 32.  The MS Netware Client
works VERY well.  Here's the deal.

Start over.  Get rid of Client32.
Install Dial Up Networking.
Make sure you have the Dial Up Adapter Installed.
Check your Network Control Panel.  You should have Client for Novell
Netware, IPX/SPX, TCP/IP, DialUp Adapter, and SMC 3016 drivers.  If not,
install them.  You do NOT need the Client for Microsoft Networks or NetBUI
unless you are talking to NT, WFW/Win95 peer-to-peer or another NetBios
server.

Make sure the IPX/SPX is bound to the SMC3016 and that TCP/IP is bound to
the Dial up adapter.  You do not need both protocols on both adapters.

When you restart your should see the server in the Network Neighborhood icon.

Open My Computer.  Open Dial-Up Networking.  Open Add Connection.  This
will walk you through creating a connection for your ISP.  If they use PPP
then you can select PPP as the choice for connection.  If you are limited
to SLIP you will need to install that (on the Upgrade CD).  You can enter
your Name and Password if your ISP does PAP authentication.  Make sure you
go into TCP/IP settings and enter DNS and IP information if appropriate.

Make sure you don't have any old winsock.dll files laying around.  That can
bite you.

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

Date: Wed, 21 Feb 1996 18:05:26 UT
From: Dave Kearns <DKearns@MSN.COM>
Subject: Re: Long names under netware

>I read somewhere, thought it was in NSEPRO but can't find it now!,
>that a patche with the salubrious name os os2opnfx.??? needed to be
>loaded as well to get LFN to run. We have OS2 namespace running on two
>servers with no problems ( apart from one or two prog's which complain
>but don't abend ) HTH

NW 3.11 needs the OS2OPNFX patch (its in 311PTD.EXE patch file).

With all versions of NetWare (3.11 and above) LFN's are only supported by
using Novell's Client32, Microsoft's Client for NetWare or Microsoft's
Client for Netware Directory Services.

In addition, NW 3.11, using either Microsoft client (but not Client32)
needs two changes made on the Win95 workstations:

 The First is located in the Windows 95 REgistry:
Hkey_local_machine\System\CurrenControlSet\Services\Vxd\Nwredir
 and set SupportLFN=2

 Likewise add the [NWREDIR] section to SYSTEM.INI and add the same key:
 SupportLFN=2.

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

Date: Wed, 21 Feb 1996 20:51:04 +0100
From: Bo Persson <bop@GANDALF.SE>
Subject: Re: Long names under netware

Joe D. wrote:
>	Taking another risk (it's a dangerous week on the list!), here is
>my memory working sluggishly again on the long filename problem.
>	The long filename stuff needs to be communicated between client
>and server. VLMs don't do that because they are designed and built for
>DOS filename conventions (8.3, case insensitive, no embedded spaces, etc)
>and thus they don't say "lfn"-speak to the server. Novell Client32 and
>the MS shells can "lfn"-speak to the server. NDIR under regular DOS knows
>how to recognize non-DOS filenames (NDIR pattern /LONG) in server
>directories but that doesn't mean normal file access operations do so.
>	I dimmly recall trying this last spring. I put OS/2 namespace
>on a NW 3.12 server and got nowhere with long names while using VLMs.
>I have Unix namespace on netlab2.usu.edu, can see long.Unix.filenames.tar.Z
>via NDIR /LONG, can do nothing about Unix style filenames when operating
>via DOS/Windows + VLMs.
>	If the above is correct then please use Client32 and OS/2 namespace
>to achieve long filename support. If the above is incorrect then let's get
>the proper information on the list from folks who have this operational.

I have a 3.12 server and OS/2 name space working fine with the MS shell
(Windows 95 default).

I tried the first Client32 beta which supported long file names, but I
couldn't get it to handle our national characters (another problem :-( ).
I haven't used later versions.

Here's a twist for Joe D. and others, who don't see the use of long file
names:  Non-english versions of Windows 95 have not only the programs,
but also file and directory names translated. In Swedish (my language)
the Desktop directory is called Skrivbord. Unfortunately this is 9
characters, so if you want to save your configuration on the server,
you MUST have long file name support!

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

Date: Wed, 21 Feb 1996 16:03:35 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Win95 long filenames, summary todate

	Given the flurry/storm of questions on Win95 long filename
support this week I put together three messages (two from the list,
one added here) on what we know so far. Corrections and enhancments
are welcomed.
	Joe D.
-------------------
Joe Doupnik writes:
	The long filename stuff needs to be communicated between client
and server. VLMs don't do that because they are designed and built for
DOS filename conventions (8.3, case insensitive, no embedded spaces, etc)
and thus they don't say "lfn"-speak to the server. Novell Client32 and
the MS shells can "lfn"-speak to the server. NDIR under regular DOS knows
how to recognize non-DOS filenames (NDIR pattern /LONG) in server directories
but that doesn't mean normal file access operations do so.
	Joe D.
================
David Kerns writes -

NW 3.11 needs the OS2OPNFX patch (its in 311PTD.EXE patch file).

With all versions of NetWare (3.11 and above) LFN's are only supported by
using Novell's Client32, Microsoft's Client for NetWare or Microsoft's Client
for Netware Directory Services.

In addition, NW 3.11, using either Microsoft client (but not Client32) needs
two changes made on the Win95 workstations:

 The First is located in the Windows 95 REgistry:
Hkey_local_machine\System\CurrenControlSet\Services\Vxd\Nwredir
 and set SupportLFN=2

 Likewise add the [NWREDIR] section to SYSTEM.INI and add the same key:
 SupportLFN=2.

=============
Joe Doupnik adds -
	To add long filename support to a server, load OS2.NAM in
startup.ncf, then one-time-only say ADD NAME SPACE OS2 <volume-name>
at the console prompt. To remove long filename support use VREPAIR
on a dismounted volume and choose the remove name space option.
Note that Vrepair requires name space helpers such as V_OS2.NLM.
To see which name spaces are assigned to volumes type VOLUME at the
system prompt.
	Joe D.

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

Date: Thu, 22 Feb 1996 01:18:01 +0200
From: "Frank R. Turi" <Frank.Turi@SAMISKHS.NO>
Subject: Long filenames - Windows '95

In the Jan/96 issue of "Inside NetWare" was an article called
'Using Windows 95 long filenames'.  Here is what they wrote:


OS2.NLM fully support Win '95 naming conventions in NW3.12 and NW4.1.

STEP 1:
-------

Move to your file server and access the command console prompt.

Now type:       load os2.nlm

and press[enter] to load NetWare HPFS name space support module.


STEP 2:
-------

Now you have to add OS/2 name space support to any of the volumes
attached to your file server. To do so, type:

		add name space os2 [volumename]

and press[enter]. After a while you will receive a message;

OS2 name space support successfully added to volume [volumename]


STEP 3:
-------

Return to your workstation. Modify your SYSTEM.INI in the
\WINDOWS\ subdirectory. Add the following 2 lines in SYSTEM.INI:

[Nwredir]

SupportLFN=2


Save your changes and restart Windows '95.

When you restart Windows '95, you should have complete support for
long-name-space filenames on your Netware file server(s).

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

Date: Thu, 22 Feb 1996 12:08:00 CST
From: kbaker@PURCHASING-PO.REQS.UIOWA.EDU
Subject: Re: Long names under Netware

    Here at our shop, we're running OS/2 clients with long file name
support.  we're running 3.11 with the following patches:
EAINFIX.NLM          12/30/93       2250k
EXTATTFX.NLM          1/19/94       2442k
These patches have fixed any problems that we have had.
    When accessing the long file names we've had no problems from the
OS//2 side, but when trying to access them from a windows session or a Dos
session, the long file name is truncated.  Because of this I'm led to
believe that long file name support cannot be had on Dos/windoze due to
the inherent design limitations of Dos.
    I'm including part of Dave's response because he neglected to mention
the obvious client that can support LFNs, that being the OS/2 client!

Kenneth E Baker

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

Date: Thu, 22 Feb 1996 17:52:45 CST
From: Josh Buysse <BUYSSE@DAILY.UMN.EDU>
Subject: Re: Long filenames - Windows '95

>Here is what they write:
>
>OS2.NLM fully support Win '95 naming conventions in NW3.12 and NW4.1.

OS2.NAM, maybe?  It is an NLM, but it's extension is .nam.

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

Date: Fri, 23 Feb 1996 22:10:55 GMT
From: Jeff Tabian <103106.3273@COMPUSERVE.COM>
Subject: Re: Long Name Support with win95 under Netware 4.x

Regarding Long Name Support with Win95:

You have to do more than just LOAD OS2.NAM

you also have to execute for each volume you wish to add the name
space to the following command:

ADD NAME SPACE OS2 TO SYS
ADD NAME SPACE OS2 TO ACCOUNTING

etc

use the VOLUMES command to confirm that the name space modules are
loaded for the appropriate volumes...

JEFF TABIAN

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

Date: Wed, 28 Feb 1996 08:19:47 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Win95 IPX SAP problem

>There has been a story about this subject by Joe Doepnik on sept 22
>1995.
>Maybe Joe can send you this again, if  he is monitoring this list he
>will see you question.
>Joop
-------
	The story ought to be pretty well known by now. It started late
last spring when several people discovered that Win95 sharing of file/print
services over IPX made the Win95 machine appear to be a NetWare file server.
The same SAP ident (4) was used by Win95. Very bad news. The problem was
pursued at length with Microsoft and finally I revealed it to the trade press.
The you-know-what hit the fan during the summer. Novell specifically removed
that capability with Client32, thank goodness. Microsoft has yet to back away,
according to the latest PC Week.
	You can read the open commentary on this by one of the Microsoft
IPX SAP engineers: file win95sap.txt in directory misc on netlab2.usu.edu.
	In a nutshell: Do not permit MS to advertize anything over IPX;
they cannot be relied upon to stay clear of NetWare services. Such adverts
are very strictly forbidden at my site (we will cut the wire of offenders).
	Claims by MS that they have a separate NW server forwarding agent are
not helpful because that is a optional item, user controlled and configured,
and that makes our networks subject to the whims of stray individuals. Whims
of individual users must not be allowed to block network usage by everyone.
	NetBEUI (non-routable) and RFC-NetBIOS (NetBIOS over TCP/IP, routable)
are available for peer to peer folks. Both work fine.
	Joe D.

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

Date: Wed, 6 Mar 1996 14:57:38 -0500
From: John Bazeley <johnb@JSB.CO.UK>
Subject: Re: Win95 client: "dir *." doesn't work anymore!

>Since I have Windows 95 on my workstation and loaded the "os/2 name
>space" on our Netware 3.11 file server (to support long file names) I
>experience strange things...
>
>One of them concerns the "dir *." command. This does not seem to work
>anymore. The system just returns a screen that you normal get, when
>there are no subdirectories. This only occurs on the Netware servers
>and not on the clients. Who has an idea and a solution? Am I using an
>old version of OS/2 name space or should I load fixes? Tell me!

Use 'dir /a:d' (if you were using '*.' as a quick way of getting
just directories) or 'ndir *.'.

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

Date: Tue, 19 Mar 1996 13:25:04 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: how to share printers under windows 95?

>We have a user here who wants to set up his printer to be serviced as a
>novell remote printer from a novell queue. I tried setting up nprinter
>(we're using netware 4.1), but it won't even load after windows 95 has
>started. I also tried Printer Assist but it doesn't seem to work either,
>although it does load. I tried loading the Microsoft print services for
>Netware from the \admin\nettools\ptragent directory on the win95 cdrom,
>but it does not seem to work as described. I think if I could get it
>working it would be suitable. Is there anyone out there using the win95
>printer agent, or something else that actually works? Any suggestions
>would be appreciated...
-------------
	The feeling here is such attempts are doomed from the start.
The much preferrable solution is to install a tiny printer box on the net
beneath the person's desk and let it service queues. Such boxes are
controllable via Pserver.exe, Telnet, etc. Desktop machines are notoriously
unreliable, doing comms under any form of Windows is absolutely terrible,
and the system manager can't readily bring sanity to wacko printing problems.
	Joe D.

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

Date: Fri, 22 Mar 1996 06:51:53 -0500
From: Rick Troha <rickt@NWSUP.NORTH-OLMSTED.OH.US>
Subject: <No subject given>

>I run a 4.1 server and have some problems with win95 and client 32.
>When i try to explore my network neighborhood i only see
>a tree, the sys volume, and the printers which are directly under
>the tree.
>
>I c'ant see the O.U which are under and the printer which belongs to
>these O.U.  When using Microsoft nds client i can see every object!

Here's something directly from the text file that came with the Client 32.
Could this be your problem?

7.3 NDS Print Queues

   NDS print queues are not displayed in the browse dialog boxes
   for the Add Printer Wizard. To install a printer from an NDS
   print queue, find the queue using Network Neighborhood or
   Explorer. Double-click the print queue icon and use the Add
   Printer Wizard to install the printer on your computer.

   Microsoft offers a file (SHELLUPD.EXE) that displays NDS
   print queues in Windows 95 browse dialog boxes. You can
   download the file from these Internet sites:

   http://www.microsoft.com/windows/software/shellupd.htm
   ftp://ftp.microsoft.com/peropsys/Win_News/FreeSoftware/shellupd.exe

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

Date: Sun, 24 Mar 1996 09:11:59 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Win95 installation to NW server, installation bug removal

	A number of people have commented/complained that when they
install Win95 on their NetWare file server for access by diskless clients
that they encounter a fatal error: "SU995014 invalid file (0x1396)."

	Reference: win95boo.txt in directory misc on netlab2.usu.edu
(aka dir pub/mirror/misc on netlab1.usu.edu, and win95boo.doc, same file,
in the www form of the list's expanded FAQ).

	The problem seems to be in Win95 installation software, and
fortunately the solution is easy. When the list of client machine components
is displayed before the drum roll screen please turn each component into
simple minded form, particularly the display adapter. If you choose simple
VGA rather than what you have then the error should disappear. The idea is
to use components which only a dumb PC would have, and hence avoid fatal
searches for vendor-specific files which Win95 does not know how to find
at this step.
	Correcting Win95 to use your real hardware is done after the
client is able to remote boot Win95. Those changes go into the registry
files system.dat and user.dat.
	The floppy disk that Win95 produces at the end of this sequence
is of no value nor interest, and the contents are held on the server in
\win95\USER\SULOGIN (my directory structure). Directory sulogin can be
deleted later at your convenience.
	Please do remember than *any* hint of a drive C: during the
installation causes Win95 to insist upon treating it as your local hard
disk and dumping things there rather than into server dir \win95\user.
	At this time only VLMs/NETX can be used with remote boot clients.
Novell has on its to-do list supporting remote boot with Client32. Reports
from others (and my tests last summer) indicate that MS can't remote boot
with their current networking software.
	Joe D.

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

Date: Sun, 21 Apr 1996 14:20:00 MDT
From: "John L. Stevens" <stevens@KIMBERLY.ARS.PN.USBR.GOV>
Subject: Re: Windows 95 client?

>We've recently moved from NW3.1 to NW4.10, and we're (hopefully)
>going to install Win95 very soon. I don't recall many references to WIn95
>in the NW documentations, though. What Win95 client software should I use?

If you are bound and determined to install Win95 then:

1.  Remember to to use ROOT in your map insert statement in the
system login script.

2.  I use the latest (gold -as Novell calls it) release of Client32
for Win95.  If you reinstall windows at any time, rerun the client
software.

3.  Get the Win95 version for you backup tape drive on the ws.
DOS/Window version just seem to loose the long file names (for good
reason)

4. Try the Client32 DOS/Win (beta) version.  So far it is working
nicely on the non Win95 machines.

5. It can be a great headache if you get more than a few pcs running
Win95 and you start having problems.  I can soakup vast amounts of
time getting it to work.  ( Ihave a disaster recovery plan in the
event of major problems.  I keep my resume off site.)

6. You may find as I did, that it is easier to totally remove the old
Windows and start over.  I have a copy of the the Win95 disk on the
network, install the VLM if I don't have them already on the ws, and
do the installation from the network at the dos prompt. You will need
to reinstall the windows programs.

7. Any way you cut it, it can be a very interesting experience.

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

Date: Wed, 24 Apr 1996 08:10:42 -0600
From: Brian Scott <BSCOTT@SYSTEMA.WESTARK.EDU>
Subject: Re: Receiving SEND messages in Win 95

>What needs to be done to get Windows 95 to display broadcast messages.

Install either VLM's or Client32.  The MS client does not accept
broadcasts and I don't miss them.

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

Date: Wed, 24 Apr 1996 14:48:36 -0500
From: John Bazeley <johnb@JSB.CO.UK>
Subject: Re: Receiving SEND messages in Win 95

>>What needs to be done to get Windows 95 to display broadcast messages.
>
>Install either VLM's or Client32.  The MS client does not accept
>broadcasts and I don't miss them.

Run winpopup. You'll get NetWare broadcasts, but I don't think
you can send NetWare messages.

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

Date: Mon, 29 Apr 1996 19:06:28 -0700
From: Mike Wallendahl <mikew@WSU.EDU>
Subject: Printing Under Win95 -- Solution

Situation:
----------
Netware 4.1
Novell Win95 Client
HP LaserJet IIISi PostScript
HP Vectra P90 w/Win95.

The critical option that I had to set was under the Properties for my
Printer, Postscript, Advanced, Check Send CTRL+D after job.

I used the printer driver for the HP LJ III Si PS that came on the Win95
CD-ROM.

BTW, I think this works even when I have a CAPTURE command in the login
script.

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

Date: Fri, 3 May 1996 12:59:29 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client 32 for Win. 95 & NIOS problem.

>I am trying to install the Client 32 onto a workstation running Windows 95
>that ran properly with the Microsoft Client for Netware networks.  (I have
>Netware 3.12)  After the setup is complete, I attempt to reboot the
>workstation so the network settings can take effect, and upon boot up my
>system gives the following message:
>Error initializing device NIOS:
>Windows protection error.  You must restart your system.
------------
	The most common problem is management of upper memory blocks, or
putting it not so gently, the lack of skill by DOS/Windows in this matter.
You must control where memory is to be excluded, both in config.sys and
again in system.ini. Trust not to automatic Redmond techniques. Yes, you
can have full regular config.sys and autoexec.bat files with Win95; use
them effectively.
	Joe D.

---------

Date: Fri, 3 May 1996 16:29:04 +0000
From: "Rodney F. Clay" <rodney@VASQUEZ.CSD.SC.EDU>
Subject: Re: Client 32 for Win. 95 & NIOS problem.

<snip>
Another thing that may help is to enable the NetWare Client 32
logging feature.  In the SYSTEM.INI file, add the following in the
386Enhance section:

	NWEnableLogging=True

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

Date: Fri, 10 May 1996 12:12:13 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Win31&Win95 Multiconfig

>I have several instructors that wish to run Win95 and  Win3.1 on
>classroom machines. Most classrooms are ok for hardware support
>(P75+, 500+Meg HD's) and it should be easy to keep them on separate
>partitions (We're looking @ System Commander to manage the boot
>partition).
>
>I have a couple labs that are a different story... Machines are 486/66
>with 100-150 Meg HD's. Getting everything on these guys is going to be
>a squeeze, and I may end up having to put part of either 3.1 or 95 on a
>server (NW 3.12).
>
>Anyone have any experiences setting up a lab/office/organization full of
>machines to run both 3.1 & 95?
---------
	My suggestion is forget Win95. It's pretty, it's big, it's shoddy.
Win 3.1 delivers the goods quite nicely (ok, as well as can be expected
from crash to crash).
	Secondly, local hard drives are not required to run DOS or either
version of Windows.
	Third, you can run Win 3.1 from DOS 7, and you can run all the apps
of Win 3.1 under Win95 (but not vice versa). Thus one installation of nearly
all apps is needed, not two copies of each.
	Fourth, don't mess with the server while school is running. Wait
til summer break, and make really good backups before fiddling.
	Fifth, and the punch line. I thought just about everyone knew by
now about my directions on how to install Win95 on a read-only NW server
for use by diskless clients. The directions written up last July (yes,
that's July) are in files win95boo.txt and msoff95.txt in directory misc
on netlab2.usu.edu. Those directions are being rewritten, illustrated,
expanded, based on deeper digging going on now, but I will not have a new
public doc available until next month. Big hint: the commercial release of
Win95 will not install client directories beneath \win95; clients have to be
located elsewhere (anywhere). Beta Win95's (such as 950R6 cited in the doc)
do not have that problem. The Resource Kit is handy, but believe only a tiny
fraction of what you read on installation.
	To repeat, I won't have a new public doc until next month because
I'm much too busy right now. So please also don't come to me for private
tutorial on the matter since that takes even more time to handle. Hang in
there until summer break.
	Joe D.

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

Date: Sat, 11 May 1996 12:38:46 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Win95 Registry Please

>I know this is a strange thing to ask for, but can someone please, please
>send me a copy of their SYSTEM.DAT and USER.DAT registry files.
>I am looking for a set which uses the "Existing ODI" network card.
>A WIN.INI & SYSTEM.INI would be nice, too...
>
>I have spent over 20 hours (even with the win95boo.txt) working on getting
>mine to run and my registry
>constantly gets corrupt or my PnP network card gets control before the ODI
>driver can be detected. If I can get hold of a working registry, i can
>edit it and adapt it to my servers.
>
>I realize the UNC path is embedded into the registry, but I dont mind
>renaming a practice server just to get Win95 running properly!
----------
	Don't bother, it's fruitless.
	Instead, go into My Computer, Properties, and reserve the IRQ/port
address of the board bothering you. That tells Win95 to keep the heck off
those values. Please see my "Win95 falls flat with IRQ 2" discussion
(not by that title of course) in win95boo.txt.

	Some commentary the wider situation (a refresher): while win95boo.txt
is correct in what it says, it does not go into the side effects now known
here (we didn't recognize them last July). Win95's setup.exe program (which
really means suwin.exe) is stupid beyond belief, which will trip up us since
we are too smart. Tell setup as little as possible, and what it does know
should be as generic (vendor independent) as possible. In the case of
installing network drivers for diskless clients, either remove all networking
from the choice panel during installation, or:
	remove all selections,
	ADD network adapter, choose "found adapter" (or similar words), NEVER
a vendor's model, and "existing ODI driver."
	remove all sections again but keep "existing ODI driver",
	ADD client, NW 4 VLMs
	expect and disregard the warning box that VLM needs reinstalltion
to finish the job (for netware.drv and similar Windows components),
	see final choices of Novell, existing ODI driver, Novell.

	This last, network, installation step tells setup.exe to not look
for vendor-specific files, because if it tries it will fail. Ditto your
video adapter on many (not all) machines; try generic VGA during installation.
	Again, I'll have an expanded illustrated win95boo.txt, version 2,
next month when I get a break. Until then it is probably wise to let Win95
rest in peace and let your students/clients work interruptedly with Win3.1
through the end of the term/quarter/fiscal year.
	Joe D.

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

Date: Tue, 21 May 1996 08:23:16 CST
From: "Eric M. Niewoehner" <Eric_M._Niewoehner@MUCCMAIL.MISSOURI.EDU>
Subject: Re: Logout in WIN 95

Yes, I recall well the days of Windows 3.1 when things were so simple
and predictable.

The information you provided is somewhat sketchy, but maybe this
checklist will help:

1. Make sure you are utilizing the Netware client as your primary
   client.  I utilize the client provided by Microsoft.

2. Remove NETBUI

3. Make sure the Netware client box "Enable Login Script Processing"
   is checked.

4. Bring up Explorer, Tools, Map Network Drive.  Make sure that the
   mappings match what you designed and make sure that the Re-connect
   at Logon box is checked.

If there is one thing fundamentally different with Windows 95 and
Windows 3.1 it is that mappings are not automatically "inherited."  I
recall that with the WIN 3.1 File Manager I could easily determine a
drive mapping as "permanent."

WIN 95's Explorer does not make it very easy.  I noted quickly that
Windows 95 did not accurately inherit all my mappings.  So I had to
manually update each user's mapping and indicate that the mappings
were permanent.  I noted that Windows 95 accurately mapped "root
mappings" but did not accurately describe searchable mappings.

If you are losing mappings while actively engaged, that may be a
problem with the 32-bit NIC setting.  When mapping is an issue, I slow
down to 16-bit ODI.  This issue has remained, apparently, for myself
and other WIN 95 networkers and may be resolved by this summer.

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

Date: Fri, 24 May 1996 10:29:14 -0400
From: "John B. Holland" <jholland@DELPHI.UMD.EDU>
Subject: Re: Client 32 printing

Although the installation of printers when using Client32 is still a
little flaky for me sometimes, I'm getting good results (happy users) for
DOS printing. I'm following the following steps, which may not ALL be
necessary...

1. Install 95
2. Install Client32
3. change default capture settings in StartMenu->Settings->Control Panel->
Network->Client 32  to eliminate banner, etc but most important to DOS
printing is the timeout which I set to 10.
4. When installing a printer, make sure to enter the path of the print queue
(ie \\server\queue ) in the port capture.
5. I install printers with the Add Printer wizard and tell it I do
print from MS-DOS programs.
6. "capture show" in a DOS box should show something like this...

>>>
Microsoft(R) Windows 95
   (C)Copyright Microsoft Corp 1981-1995.

C:\WIN95>capture show

LPT1:  Capturing data to server ENTERPRISE queue LASER1104.
       User will not be notified after the files are printed.
       Capture Defaults:Enabled        Automatic Endcap:Enabled
       Banner :(None)                  Form Feed     :No
       Copies :1                       Tabs          :No conversion
       Form   :0                       Timeout Count :10 seconds

LPT2:  Capturing Is Not Currently Active.

LPT3:  Capturing Is Not Currently Active.

C:\WIN95>

<<<

I've had really good results as far as printing. The machines would
hang when installing printers but once we rebooted and somehow got through
that results were good. the update patch (is it 3295c.exe or something?)
seems to help with that.

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

Date: Tue, 28 May 1996 10:29:33 CDT
From: "Dan Creagan" <DCREAGAN@scholars.bellevue.edu>
To: netw4-l@bgu.edu
Subject: Re: MS Client32 & NWADMIN.EXE

>When I try to run NWADMIN using the MS Client32, with the NDS service,
>I get a message that NWADMIN requires nwipxspx.dll to run.  Well, it
>requires more than one file because it dies, even after I copy in the
>other 3 files it requests.  Does MS Client32 support running NWADMIN
>in any way, shape, or form?

This sounds similar to the Win95 problem.  When you haven't
installed a normal client into the Windows directory, NWADMIN will
die because it can't find all the .dlls.  The solution that we use
is to just copy all the .dlls from the CLIENT\DOSWIN directory on
your system CD (uncompress them with the Novell utility) to the
WINDOWS\SYSTEM directory.  If you are going to access any of the
other utilities (such as the documentation), then be sure to set the
NWLANGUAGE=<your language> environment variable.

PS:  I haven't tried this with the 32 bit client, but, hey, it sounds
like it might work!

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

Date: Tue, 28 May 1996 15:51:18 -0400
From: Todd Cox <CoxT@gwgate.nhlbi.nih.gov>
To: netw4-l@bgu.edu
Subject: By-passing initial netware login prompt. -Reply

>I have just switched to Windows 95 and I am using the Novell 32-bit client
>software to communicate with my 4.1 server.  Everything works great but I
>want to be able to bypass the Netware login dialog box that appears as
>Windows 95 is booting without clicking on Cancel. Does anyone know how
>this might be accomplished?  Any help or insight will be appreciated.

From Settings | Control Panel | Network, choose Windows Logo as your
primary login.  It should say "Novell Netware Client 32" rights now.
The box is right below the Add button.

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

Date: Fri, 7 Jun 1996 18:22:30 -0400
From: Alan Rowe <ALAN@TORAHAURA.COM>
Subject: Printing from win95 -Reply

>We are running Novell 4.1 win windows95 on several of our machines.
>Since we use CC:Mail we are not ready to go to the Novell 32 bit
>client software yet.  We know that we can turn off oppertunistic
>locking, packet burst etc,,, and make the 32bit client safe for win95
>but unless I can convince my boss otherwise, the client32 is not an
>option right now.
>
>Finally, here's the question.  How can I have a windows or dos machine
>print across the network to a printer attached to a win95 workstation?
>Like nprinter on the normal dos/windows workstation?
>
>We have the NDS patch loaded on the win95 machines, which make you
>remove the print agent for novell.

Just found on compuserve beta 2 of the client32 nprinter. Working here.

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

Date: Wed, 12 Jun 1996 06:25:31 CDT
From: Elbert LaGrew <lagrew@SUNNY.HEALTH.STATE.MN.US>
Subject: Re: Broadcast msg;s under Win95

>Ok guys, maybe I've gone blind recently but I can't seem to find a
>setting under Client32 for Windows95 to disable broadcast messages
>from Netware.

Here is the only way I have found so far.

1> CONTROL+ALT+DEL Then select 'end task' nwpopup
2> Go to a DOS prompt and type the CASTOFF command

It's a kludge.  I would prefer that Novell had but a
simple checkbox in their Client32 setup, but this works
reasonably well, even if it is a bother.

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

Date: Fri, 14 Jun 1996 09:48:29 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Win95 installation to NW servers, new revised instructions

	If you are considering installing Windows 95 on a NetWare file
server then you may be interested in reading my updated, illustrated,
more detailed document on how to accomplish that goal. Last summer I
published doc win95boo.txt as a set of working notes on the task. That
doc was correct but far from indicating all the great many difficulties
one encounters. The new document covers these and more.
	You may wish to read the doc even if your clients are not diskless.

	This time I decided to illustrate the instructions with screen
captures. To combine the pictures with text I used Microsoft's Powerpoint
version 7 (the Win95 edition). Since not everyone has that product I have
also produced a Postscript printer version (color included). At this time
I do not have a straight text doc. My screen is 1024x768, my printers are
an HP 4M and HP 1200C (color inkjet), paper size is US letter.
	The  D R A F T  document (subject to editorial change to improve
language and make it look nicer) is on netlab2.usu.edu in directory misc,
which is the same as directory pub/mirror/misc on netlab1.usu.edu. There
are two .ZIP files:

	w95inst7.zip	- full Powerpoint v7 slide show
	w95insps.zip	- postscript printer versions of slides and notes

	I recommend readers first look carefully at all the slides and
read the extensive notes accompanying each slide, and only then undertake
an installation.

	In the process of rewriting the instructions I clarified many items
that we had either taken for granted or overlooked as unimportant last year,
but which setup.exe reacts to very strongly. Initial conditions turn out to
be vital, minor choices of things here and there are vital, the MS Win95
Resource Kit is well meant but has nothing much to do with reality (they
wrote it well before the code guys sort of did their job).
	The new instructions have worked here time and again, all the
way through the process. That is not a 100% guarantee they will work on
your particular clients, but with some minor tweaking you should succeed.

	Remember, this is a DRAFT document which I typically change slightly
every day. I won't post a new edition until its finished. The draft is only
to help folks asking me about the matter every day of the week.
	Joe D.

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

Date: Thu, 20 Jun 1996 11:50:18 -0600
From: James Federline <federlin@CHEM.UMN.EDU>
Subject: Client32 4 Win95 and ARCserve agent service

I've solved a problem between Client32 (Win95) and the ARCserve Agent
Service provided with the Windows 95 distribution that I could not
find documented in Novell's Technical Information db nor Cheyenne's
Technical info db, nor MS' Knowledge Base.

If you run Client32 for Win95 in conjunction with the Win95 ARCserve
Agent service, the stock configuration of Client32 may cause your
workstation to completely lock up during the remote backup procedure.
This ocurred to me with the open beta of Client32 and with the final
release. My desktop would lock up at a different point in the remote
backup each night.

I read a message on the novell@listserv.syr.edu mailing list that if
you have "Cache Writes" in the "Advanced Settings" tab of the
Client32 section of the Network Control Panel set to ON, "all bets
are off as far as data integrity goes." Well, I took that to heart
and flipped this switch to off in Client32, and all the locking up
stopped.

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

Date: Fri, 21 Jun 1996 10:50:33 -0400
From: "J. Darren Lofthouse" <DarrenMail@AOL.COM>
Subject: Re: Drive Mapping in Login Script for Client32(95)

>I've just try the client32 for win95 on netware 4.10 and it seems that
>all our drive mapping done in the system login scripts do not work.
>I can only map the drive in win95 itself.  Any way to make the login
>script work?

First, go into Control Panel / Networks and select Novell Netware Client32
/ Properties. You should have a tab named "Login". Select this tab and make
sure that the "Display Script Page", "Close Script Results Automatically",
and "Run Scripts" options are all checked.

Second, shut down windows 95 and restart. Make sure it works. If not then I
would check the login script and make sure you aren't using any variables
in your drive mappings. I haven't had any luck using them with Windows 95
logins. Good Luck.

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

Date: Fri, 21 Jun 1996 15:09:42 -0600
From: Brian Scott <BSCOTT@SYSTEMA.WESTARK.EDU>
Subject: Re: Win95 & Client 32

>I have a question for y'all.  We are running a Novell 3.12
>network.  I have Windows 95 running, and have the Netware
>Client 32 installed.  We have several lines in the system login
>script that look something like this:
>
>#COMMAND /C IF NOT EXIST K:\EXCEL MD K:\EXCEL > NUL
>
>That checks to see if there is an EXCEL directory on the user's K:
>drive (which is their personal, or users drive).  If the directory
>doesn't exist, the system login script creates it.
>
>What I'm running in to (and it's not really a "problem", per se,
>it's just annoying) is that when I login, and the system login
>script gets to this section (there are probably 10-15 lines like
>the above...for different applications), the screen flashes to a
>black screen, like it is jumping to DOS for a second.  It does this on
>every line like that.  Does anyone know WHY it does this? Or, better
>yet, what I can do to make it stop?  We are going to be upgrading
>several computers to Win95 eventually, and this kind of thing would
>freak some of our users out.  Hehehehe, what can I say, some of them
>just aren't that bright!  <grin!>

One solution that will also speed up your login script is to put all
those dos commands in a batch file and call that batch file from the
login script.  This will only create one "flash" to the dos prompt. It
will speed things up since you don't have to shell to dos 10-15 times.

One other consideration: When I tested this the "IF NOT EXIST
K:\SOMEDIR" was always true.  This only worked on files, not
directories.  In this case you could also remove the if statments
and just have a bunch of md commands.  What I ended up doing since
the directories were on the users harddrive, was the following:

if exist c:\data\wpwin\wpwin.dir goto ok
md c:\data\wpwin
echo plese don't delete me! > c:\data\wpwin\wpwin.dir
:ok

This is probably more inefficient then just attempting to create the
directory, but it got rid of the "Directory already exists" message
(which I can't seem to redirect to nul for some aggravating reason).

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

Date:	Tue, 25 Jun 1996 10:18:41 +0100 (GMT Daylight Time)
From:	John Bazeley <johnb@jsb.co.uk>
Subject: Maybe a FAQ - Win95 messages

To get Win95 with the MS client to display NetWare broadcast messages,
run WINPOPUP.EXE, which lives in c:\windows. This will also cause you
to receive regular Windows messages. WINPOPUP lets you send Windows
messages, but not NetWare ones.

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

Date: Wed, 26 Jun 1996 09:05:48 GMT-5
From: "David Pifer" <ccdave@amber.indstate.edu>
To: netw4-l@bgu.edu
Subject: Re: Long File Names

The largest ramification seen is that this is another Name Space on
the volume. The way I understand the issue is (and those that know I
am wrong will correct me, that's email) that there is a physical
limit on the number of files on a volume 2,000,000 you then divide
this by the number of name spaces loaded. In our case DOS, MAC and
OS/2 this brings the number of files down to 666,666 etc.... We have
a netware 4 server with 550,000+ files on a volume already (mostly
mail). Also each name space requires more ram, this is were I give
up on trying to do this, there is a program that is available with
NDSCAN.EXE (I think) called SMEM.EXE that walks you through
calculations. Netware 4.1 supports os/2, 3.12 does too, 3.11 does not
officially support it but can be patched to do it.

---------

Date: Wed, 26 Jun 1996 21:21:33 -0400
From: Joe Thompson <JST604@aol.com>
To: netw4-l@bgu.edu
Subject: Re: Long File Names

>The largest ramification seen is that this is another Name Space on
>the volume. The way I understand the issue is (and those that know I
>am wrong will correct me, that's email) that there is a physical
>limit on the number of files on a volume 2,000,000 you then divide
>this by the number of name spaces loaded. In our case DOS, MAC and
>OS/2 this brings the number of files down to 666,666 etc.... We have
>a netware 4 server with 550,000+ files on a volume already (mostly
>mail). Also each name space requires more ram, this is were I give
>up on trying to do this, there is a program that is available with

One extra little thought here...according to novell (and my experience
confirms this!) directory entries are dealt out to subdirectories in
blocks of 32.  So on initial creation of a subdirectory 32 entries are
reserved. Once you pass 32 files in that subdirectory another 32 are
reserved and so on.

I was setting up Lotus Suites and placed the users workstation setup in
the users Home directory.   basically this consisted of 20 or so
directories with 2 or 3 files in each plus a few empty ones for data.
After installing 450 users I got the error "Unable to create subdirectory".
I had 3 gigs left on the volume, what I hadn't taken into account was that
I had NFS name space loaded on this volume.

A hard lesson indeed.

BTW  Netware 4.11 is supposed to finally fix this....it goes up to 16
million.

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

Date: Sun, 30 Jun 1996 21:26:48 -0700
From: Henry Unger <hunger@HITECH.COM>
Subject: Re: Win95/Lfn on 3.11 doesnt seem to work??

>I have Win95 running great and Long FileNames work on 3.12 great (using
>OS2.NAM).
>
>Now, on my 3.11 servers it doesnt work; 8.3 is all I get.
>I loaded OS2.NAM, and the 2 patches with patchman, then added os2
>namespace to a brand new SYS volume... no luck...(i got the instructions
>from several of novells readme's about the patches)
>
>I can log the same exact workstation into 3.12 servers and works great,
>but the same machine on 3.11 gets me 8.3 filenames.

Check out http://www.microsoft.com/kb/peropsys/win95/q137275.htm
for more info.

You need a registry entry called SupportLFN with a binary value
of 2 in:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\Nwredir

---------

Date: Mon, 1 Jul 1996 08:37:44 +0000
From: "John R. LaPrad" <jrl@TARDIS.SVSU.EDU>
Subject: Re: Win95/Lfn on 3.11 doesnt seem to work??

>I have Win95 running great and Long FileNames work on 3.12 great
>(using OS2.NAM).
>
>Now, on my 3.11 servers it doesnt work; 8.3 is all I get.

Win95 by default will not support LFNs on 3.11 servers.  To enable
this you must make a change in the registory or add a 2 lines to the
system.ini

in the registry
delete this key, then recreate it with a BINARY value of 2
Hkey_Local_Machine\System|CurrentControlSet\Services\VxD\Nwredir

or

in system.ini
[nwredir]
supportlfn=2

or use Novel's client32 -- it does not require the fix.

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

Date: Mon, 1 Jul 1996 13:19:15 -0500
From: Lloyd Petrey <PETREY@IMDR.COM>
Subject: Re: Client32 advantages -Reply

>Can someone tell me what is the advantage in using Novell's
>Client32 for Win95?

1.  Client32 vs VLM's--performance & stability of 32bit drivers vs 16
bit.  More available conventional memory for DOS applications.

2.  Client32 vs MS Netware client plus MS Service for NDS--Client32
solved a number of network related issues that exist when using MS
Netware client:
	- Properly passes Netware USERID to GroupWise so that
	  GroupWise  password entry is not required.
	- Password changes are properly synchronized to our NW 3.12 server.
	- It is compatible with the 32 bit NPRINTER from Novell.  (The
	  Microsoft equivalent of NPRINTER for MS Netware client
	  doesn't work properly and has not been patched yet.)
	- ATTACH.EXE works properly from a .BAT file.  Using MS
	  Service for NDS ATTACH.EXE did not behave properly for a
	  3.12 server.
	- WINPOPUP.EXE with CLIENT32 is better than the one with
	  MS Netware Client.
	- In general everything related to Netware & NDS work much
	  better with CLIENT32.

Downside:  CLIENT32 does not support File & Printer sharing so
peer services are not available.   Therefore it does not support the
neat stuff that requires file & printer sharing:  remote registration,
remote administration, etc, etc.

It also seems to me that performance is a bit slower with Client32 vs
MS Netware client.

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

Date: Mon, 8 Jul 1996 08:27:00 -0500
From: "Leone, Michael" <mleone@RICHARDSONCO.COM>
Subject: Re: Client32.NLM not remaining resident

>I have been having trouble installing Client32. I have installed it a
>couple of times but keep on getting:
>
>Pseudo module Print did not free one or more resources before being
>destroyed.
>
>and
>
>C:\Novell\CLIENT32\CLIENT32.NLM did not remain resident
>
>when I boot up Win95.

Check the Novell website knowledge base (or is that the TID base?).  In
short, you need to edit the Win95 registry, and remove a couple of the
keys.

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

Date: Fri, 12 Jul 1996 15:23:43 +0000
From: "Rodney F. Clay" <rodney@VASQUEZ.CSD.SC.EDU>
Subject: Re: NPRINT32, CLIENT32, WIN95

>I am testing the beta of 32 bit NPRINTER for Win95 using
>CLIENT32.
>
>Before NPRINTER loads the user has to either logon to the computer
>or else cancel the login.  This is at best an inconvenience.  What good
>is this thing if it can't load without intervention.
>
>Is there any way to get a program to load into memory prior to the
>LOGIN?
>
>LOAD=  and RUN= lines in WIN.INI don't take affect until after
>login either.
>
>I tried putting it in the WINSTART.BAT file but got a message to the
>affect that 32bit programs will not load from there.

Please set your browser to the following URL:

	<URL:http://support.novell.com/home/nwpul/nprinter/index.htm>

There is an FAQ that addresses this.

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

Date: Fri, 19 Jul 1996 15:34:53 -0500
From: Jeff DeFord <deford@WHY.NET>
Subject: Re: Duplicating a Win95 workstation?

>Since I am not able to run Win95 from the server (I have proprietary cards
>which dont allow "run from server" configurations) I have set up Win95 on
>my workstations. It works great from the workstation and the policies are
>great. Here's my problem:
>
>Its only a matter of time before one of the workstations gets screwed up
>(users changing preferences, deleting a necessary DLL, etc..)...
>
>Is there an easy way to "clone" 95 workstations? Its not as simple as
>NCOPYing the files back to the hard drive since it has lfn... has anyone
>been able to clone a win95 workstation completely with registry intact?

If you are using one server as the primary location for your policies
then I have a sollution. Create a 'template' workstation.  Compress
the disk drive.  Adjust the free space to approximately 10 MB.
attrib the compressed drive so that all files are - r -s -h.
Copy the files to the server!  Now if a machine goes ka-boom, you can
go to the box, boot from a floppy, format and sys the drive with a
95 boot disk, log onto the server and copy the files down.  Once they
are copied, change any required settings (IP address, computer name,
workgroup, etc). Copy the file mini.cab to the windows95 directory, then
un-compress the hard drive.  Viola.

---------

Date: Sat, 20 Jul 1996 12:14:55 +0200
From: Peter Jansen <PJansen@USER.DIVA.NL>
Subject: Re: Duplicating a Win95 workstation?

Yes, I have just done it for about 80 workstations which all needed
WIN95 and MS-Office.

One-time:
- Install a workstation with all software needed on the other
workstations.
- Backup you long file names with the utility form Microsoft: LFNBK.exe
(It's on the CD)
- Reboot with a floppy and make a real-mode connection to the server.
- Use a backup program (such as MSBACKUP)to copy all files (incl. system
& hidden & lfnbk.exe & lfnbk.dat) to the server.

All workstations:
- Boot your new workstation from floppy and make a real-mode connection
to the server.
- Restore the backup to the local harddisk
- Reboot the workstation (Win95 boots)
- From a dos box restore the long file names (lfnbk /r)
- If neccesary change your computername to avoid conflicts

Takes about 10 min per workstation.

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

Date: Wed, 31 Jul 1996 23:19:13 -0400
From: Clay Gibney <gibney@WOODSROGERS.COM>
Subject: Netware client32 problems -Reply

Which client32 are you referring to?  Windows95 or DOS/Win?  On the
Windows 95 client32, we had to increase the number of SPX connections
value in our network settings in the control panel for some of our
software to work right.  I think it defaults to only 15 spx connections,
and we increased it to 60.

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

Date: Wed, 31 Jul 1996 23:26:17 -0400
From: Clay Gibney <gibney@WOODSROGERS.COM>
Subject: automatic netware login in win95 -Reply

>One of my user wants connect to our novell 4.1 server automatically.
>He doesn't want to type the password.

Try embedding or typing a TAB (Ctrl-I) into your text file after
the user name and before the password.

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

Date: Thu, 1 Aug 1996 08:33:58 +0200
From: Henno Keers <Mailbox@ICE.NL>
Subject: Re: NPrinter

>I have a question with regards to NPrinter which must be used when
>the Printer is in  remote location (not direct to the print server).
>I'm using Windows 95 and I'm getting an error that "Windows is running
>in enhanced mode so Nprinter must be loaded before loading Windows."

Win95 does not support Nprinter (or rprinter) very well, especially
when using 32 bit clients from M$ or Novell.
I would recommed to do the following:
-   Check what king of NIC you have in the workstation. See
    if you have a NetWare 3.12/4.x compatible server .LAN driver
    NLM for it.
-   Get Novell Client32 for Windows95 with patch c3295d.exe
-   Get Novell Nprinter for Windows95
-   Install Client32 with the 32 bit ODI driver
-   Install Nprinter

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

Date: Thu, 1 Aug 1996 09:35:57 -0400
From: Rob Albertson <albertson@VAXA.CIS.SUNYCGCC.EDU>
Subject: Re: automatic netware login in win95

>One of my user wants connect to our novell 4.1 server automaticaly. He
>doesn't want to type the password. He is using the novell win95 client
>32. I created a a sortcut in the startup group with which says loginw95
><c:\password.txt . But it doesn't work. It puts the password.txt word in
>the username box.

NOTE:  This workaround involves using regedit in Win 95.  You have been
warned!!!

First, create or move the LOGINW95 icon into the STARTUP group of the Win95
Start Menu.  Edit the properties of the icon, and add the client's USERNAME
and also /cont to the command line.  Be sure to separate the USERNAME and
the /cont with a space.  Your new command line should look something like:
c:\novell\client32\LOGINW95 USERNAME /cont

Next, run REGEDIT.

expand(click on the +):  HKEY_LOCAL_MACHINE
expand:  SOFTWARE
expand:  Microsoft
expand:  Windows
expand:  CurrentVersion
expand:  Network

Click on Real Mode Net.  When the items in the right side frame become
visible, right click below the bottom item.  (On mine it's 'transport')
Choose New> Binary Value.   Type AutoLogon for the name and press Enter.
Now right click on the AutoLogon item.  Choose Modify.  Enter 00 into the
dialog box and press enter.  That's it.  Exit regedit.

Now, set the client's account to not require a password to login.  When you
next restart your computer, it will login and never prompt for anything.  I
am thinking here that since your client doesn't want to type the password to
login to the server, then he is not too worried about security, thus he
should not be too worried about not having a password on his account.  If he
does want the password, then this exact work around does not work, and it
will prompt for password anyway.

On the Novell Web site there is the exact technical information that will
help perform this if you were not able to use my instructions.  It works well.

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

Date: Mon, 19 Aug 1996 21:36:03 -0700
From: Randy Grein <rgrein@halcyon.com>
To: "NetWare 4 list" <netw4-l@bgu.edu>
Subject: Re: Losing drive mappings in DOS Window

>If he opens another DOS window when this happens, he cannot get to
>the mapped drive.  I can re-map the drive from within the window then
>things are fine for a while.  It's getting so frequent now he can pretty
>much duplicate it without a hitch.  I've checked NSEPro and Novell's web
>page using the most obvious key words and can't find anything on this.
>I've had it happen to me, and several other people have seen it happen,
>just not as often as this guy.

Yes; usually with win95 it means time to reformat and re-install. This is
not normal, healthy behaviour, but seems to be related to registry
problems. I'm convinced that this is still beta software.

---------

Date: 20 Aug 96 10:12:03 EDT
From: RBO  Rainer Bohm <RBO@dancall.dk>
To: netw4-l@bgu.edu
Subject: RE: Losing drive mappings in DOS Window

I have seen something like this with WIN95, the
problem was that we had Microsoft Network and
NetBEUI along with Netware. When we removed
NetBEUI and Microsoft Network it worked fine.

---------

Date: Tue, 20 Aug 1996 08:39:46 -0400
From: Scott Nanni <ZNAMGR01@AMERICAII.COM>
To: netw4-l@bgu.edu
Subject: Re: client32 connections -Reply

Just to throw in my two cents.....I've done alot
ineroperabilty between Windows NT and Netware 4 using the
Windows for Workgroups platform and Microsoft TCP/IP,
microsoft network, vlms, etc.  Some in 95 but not much.
There was an advanced option in WFW using the Microsoft
network, advanced settings, which was the ghosted
connections option.  We found that ghosted connections meant
do not restore the network drive connection until the
resource is called upon.  We had alot of problems clear up
by disabling ghosted connections, causing the connection to
take place and stay in place through the whole network
session.  I haven't digged through 95 much yet, but most of
what I've seen is similar to the WFW Microsoft network
options.  I would imagine there is a way to disable ghosted
connection under 95.

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

From:	"Peter Stromblad" <Ps@msek.lth.se>
Date:	Tue, 20 Aug 1996 16:13:57 +0100
Subject: Disabling Win95 Automatic Login

By a mistake we found a flag in the registry that makes it possible to
boot a Win95 client without having to Log In at boot. This feases the
possibility of implementing Carbon Copy (or similar) on your Windows 95
desktop that can execute when the Win95 boot process (which Client32 is
part of and thus inhibits due to AutoLogon) is finished.

Start RegEdit
Insert binary key: autologon
at \HKEY_LOCAL_MACHINE\SOFTWARE\
   Microsoft\Windows\CurrentVersion\Network\Real Mode Net\

-> to disable, Insert value 00
-> to enable, Insert value 01, or remove key.

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

Date: Mon, 26 Aug 1996 23:42:24 -0400
From: Debbie Becker <dbecker@clark.net>
Subject: Re: Win 95 and DLL Files

>I have about 6 NWCALLS.DLL file in different directory in Win 95 PC, with
>all different versions.  Isn't there supposed to be only one file, in
>windows/system?
>
>Using Client 32 and service pack, I still can not browse the network using
>Network Neighborhood. I wonder this duplicate dll files has something to do
>with it!

I don't know about the duplicate DLL files, but I had problems getting my
laptop to work with Client32 as well.  I'll give you the same advice I was
given:

* If your Registry is completely "messed up" (technical term <g>) it's easier
to start from scratch -- get rid of Windows 95 and do a fresh install.

* Load your network card and see if you can get it to work with MS network
client for NetWare first.

* Once it's working well with MS's NetWare client, try loading the 32-bit
Client.

In my case, it turned out that, even though Win95 said the board was
installed with no conflicts, it appeared to need specific I/O and IRQ
settings (I was told that "sometimes the 3Com cards (PCMCIA card) need to
have specific numbers..") -- in this case an 340/5...

Incidentally, my NWCALLS.DLL if dated 7/26/95 and was in my windows SYSTEM
subdirectory...

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

Date: Tue, 10 Sep 1996 14:53:03 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: server mirages

>We have about 9 NetWare servers.  They are a mixture of 3.11, 3.12,
>and 4.1.  We are experiencing the following problem:  when issuing
>the command slist for a 3.11/3.12 attachment, we do not see all the
>servers although they are all up and running.
>Also even when we see all of them and login to a 3.11 server, and
>then issue an slist command, some of them disappear, although
>they are still up and running.  What is puzzling is it is not
>always the same servers that disappear.  I have not been able to
>spot a pattern to this.  What is most problematic is that some
>3.11 servers do not show up.  Any ideas?
----------
	Not enough info to be terribly helpful, but let's try a couple of
things.
	Destroy every Win95 and NT station advertizing file and/or print
services over IPX. Never let them do that because they proclaim themselves
to be NW file servers and the are not by any stretch of the imagine.
	If you are running IPX over multiple frame kinds then try to
standardize on Ethernet_II throughout.
	If a router box is between servers check that it is not filtering
out SAP traffic.
	Apply all the updates and patches to all servers and clients.
	Joe D.

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

Date: Mon, 16 Sep 1996 16:33:43 -0400
From: Rick Troha <rickt@NWSUP.COM>
Subject: Here's the Fix for Client 32/Internet Explorer 3.0 Problems

If you have been experiencing erratic behavior from MS Internet
Explorer 3.0 and you are running Novell's Client 32, the fix is
documented at:

	http://207.68.137.43/kb/peropsys/win95/q154860.htm

This drove me crazy for the last few weeks. Apparently, there is some
weird interaction between Client 32 and MS-IE 3.0. The fix involves
adding an entry to the registry.

My thanks to Jeff Smith for pointing me in the right direction.

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

Date: Thu, 19 Sep 1996 21:32:17 -0500
From: David Buckwalter <david@ACRC.UAMS.EDU>
Subject: Re: Mac and Win95 Filenames

>I'm having trouble getting a Windows95 machine to read Mac filenames off
>our NW 4.1 server.  I work for a school system where each school creates
>their own web pages on a Macintosh.  They then send these pages to us to
>place on our WinNT webserver.  I planned on using a Mac we have attached
>to our network to copy the pages to our NW Server where the web pages are
>stored. The problem is that the WindowsNT/95 machines only see 8.3 filenames.  I
>have both MAC and OS2 name space added to this volume.  Any suggestions?

The following needs to be added to the Windows95 system.ini file. I
don't remember where I found this tip but I think from redmond's www.

[NWRedir]
SupportLFN=2

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

Date: Mon, 30 Sep 1996 17:27:42 -0400
From: PowrTekSys@aol.com (Kevin McIntosh)
To: netw4-l@bgu.edu
Subject: Re: Win 95 PC does not prompt for Netware Login dialogue box

>The PC is connected in Netware 4. All the necessary network protocol
>drivers & services such as : TCP/IP, Netbeui, Novel Netware 32 bit
>client, MS client were intact.

Make sure you are not running both the Microsoft and Novell client32 for
Netware Networks.  It won't work.  The problem lies in the registry and the
easiest way to solve it, that I know of, is to reinstall the Novell C32
with the setup.exe /ACU switch.  This will remove the MS client, first.
Make sure you have a copy of the netware client on diskettes.  It's rare,
but if the automatic client update procedure fails, it blows the Win 95 PC
off the network.

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

Date: Tue, 1 Oct 1996 20:23:41 -0400
From: ATL1DDJ@aol.com
To: netw4-l@bgu.edu
Subject: Re: Win 95 PC does not prompt for Netware Login dialogue box

>>It seem that the problem lies with Win 95 ! As upon the SECOND
>>attempt to login, the users can view the whole network & perform
>>normal function. Just that it require TWO time to logon properly !!!
>>
>>I would appreciate if anyone out there can help me to solve the
>>problem. I think the last resort will be REFORMAT the entire harddisk
>
>That would be a good idea. Just in case - when you deleted and installed
>Win95 did you delete the entire directory, or just the files? The
>user.dat and system.dat (the two files that make up the registry) are
>hidden, system and read-only, so it's easy to miss them unless you delete
>the entire directroy structure.

One thing you might want to try before you format the entire drive is the
infamous REGEDIT.  Simply search on "ProcessLoginScript" and if it
is "00", change it to "01".  I am not sure how it happens but I have
performed it on several PC's and no side effects.  (And I'm scared of
regedit).

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

Date: Wed, 2 Oct 1996 19:11:38 GMT+0800
From: LIMCT@csdc.fujitsu.com.sg (Lim Chin Thiam)
To: netw4-l@bgu.edu
Subject: Win 95 didn't prompt for Netware 4.1 login >>Solution

Through your help, i managed to solve the above-mentioned problem by:

1. Deleting entirely the Win 95 software.

2. Reinstalling Win 95

3. Reinstalling Netware client 32. Selecting <Ndis.vxd> file from the
   network interface card mfger.

4. In control panel>network, adding in the relevant network protocols
    & clients (MS client for Netware, NetBeui, Tcp/IP..etc)

5. Rebooting the PC

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

Date: Thu, 3 Oct 1996 18:37:04 -0700
From: Mike Wallendahl <mikew@WSU.EDU>
Subject: Re: Client 32 for 95 not clearing connections.

>Often on our NetWare 4.1 server, connections are not being cleared
>after users log out from Windows 95 machines.  A user will log out,
>not show up on an nlist or on the Monitor console screen, but when
>they try to log in again, they are told they are attempting to login
>to too many stations simultaneously.  Presently, all accounts are
>restricted to 2 concurrent logins.  This problem only appears to be
>happening on Windows 95 workstations running Client32.  We have not
>yet installed the latest patches (which I hope to do today), and I'm
>hoping this problem will be corrected when we do so.

I had the same exact problem at my shop.  The patches don't fix it.
Check out:
	http://support.novell.com/
Search for:  "2909833"
	    ( ^-- that's the TID number for a revalent problem)

The fix I used was the drop the watchdog timeouts to the lowest amount of
time possible.

From the server console:
 o load servman
 o Server Paramters
 o Communications
 o Scroll to the bottom of the list, and set all the Watchdog parameters
     to the lowest number possible.

Making those changes forces to server to check MUCH more often if the
station is still logged in.  With the lowest settings extra connections
should be dropped every 2 mins or so.  My problems with extra connections
are mostly gone now.

I don't know the drawbacks of setting the watchdog params to such a low
number.  Perhaps Randy can set us all straight on this. :)

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

Date: Sun, 6 Oct 1996 23:22:36 -0700
From: Dave Quecke <djQuecke@WORLDNET.ATT.NET>
Subject: Win95 & PCI NIC

>Just went throught the win95 install program on a pc connected to
>a N 4.1 network.  It appears that win95 does not recognize the NIC
>which is a PCI nic using a AMD chip set.  This machine was working
>fine under windows 3.1 using the vlm's and running pcntnw.com
>
>Anyone running this card under win95 using the 32bit client for
>win95?  Some help would be appreciated.  Don't know where to go
>from here.

Just athought but check your setup one more time.  Go bare bones.  Go the
Network applet in the Win95 control panel.  Get rid of any Dial-up
networking items.  Make sure your server's name etc is entered on the
property sheet.  Get rid of file and printer sharing.  Most important check
the property sheets for the nic.  I think its the advanced tab.  Where it's
looking for protocol don't use auto.  Lots of folks having trouble here.
Select the protocol your running i.e.; 802.2, 802.3, ethernet II whatever.
Go to the password applet and make sure you require a password to logon.
When it says do youe want to restart after the network applet closes tell it
no.  Go to your windows directory and delete the *.pwl files.  This is where
the passwords are cached.  If your password is cached Win95 may not ask for
it on restart.  No password needed won't cause netware to enable.  Then shut
it all down and restart.  I apologize for lousy grammer etc but I'm on the
run.  I had a bear of time twice with Win95, hang in there it can be done.
If Win95 recognized your nic and installed drivers great, but this could
also be an interupt/port problem.  I had one act just like this.  Make sure
Win95 is configured to same interrupt and memory location that your card is.
Win95 will happily show you the card set on an interrupt with no conflicts
but not responding.  Because the card is on a different interrupt. Use the
System Device manager to check on this one.  Once you get that up and
running you can add in what you want.

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

Date: Wed, 9 Oct 1996 12:25:13 +0000
From: "Emmanuel CHILAUD" <manu@math-appli-uco.fr>
To: netw4-l@bgu.edu
Subject: Re: Netware Beta Client...

>>I'm running this Netware Beta client for NT. It works. I've only one
>>problem -- I can't run "nwuser" to send popup messages...
>
>I have the same problem with Client32 for Windows 95.

For WIN95, you must make a netware.ini in your windows directory and
put in the following lines:

[restrict]
Win95AllowDRVUI=1

Then you'll can execute NWUSER.

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

Date: Thu, 10 Oct 1996 12:03:15 -0400
From: Bob Dopher <rcd@EE.UMR.EDU>
Subject: (Fwd) Client32 and generic logins

>>Anyone found a way to do generic logins from a win95 station using
>>client32? Up to now, under DOS, we've just been relogging in GUEST
>>as usr%station. However, that now means trying to run a DOS login
>>from a GUI and/or vice versa. Kind of a catch 22. I would really
>>hate to have to make 400 guest type directories writeable by all 400
>>guests....
>
>The problem that I am facing now is that the entire campus
>uses the user GUEST as a generic login. In order to provide the user
>with a specific home directory, we then login them back in as
>usr_%station. This ALMOST works under client32 except that all
>drives are mapped as non-search drives rather than search. At this
>point, since we now know the connection, we can login back in from
>the GUI as usr%station & everything works as it should.
>
> The login goes something like the following:
>
> If member of "GUEST" and "%LOGIN_NAME" <> "USR_%STATION THEN BEGIN
>
> #LOGIN USR_%STATION ...

Just a follow up on the problem & solution. The solution had to be
implemented from the client side and involved doing a first login as
GUEST then a subsequent login as usr_%station. After the first
login, windows knew what connection he was on, so the second login
was a simple matter of hitting enter once the GUI popped up. Voila!
All drives are mapped correctly, and we have managed to maintain the
capability of restricting usr_%station's rights to his assigned home
directory without giving him/her rights to all other generic user
home dirs.

The trick was to find a way of automating this so that the average
user could set down at the computer and login as GUEST without having
to manually perform the second login. Winbatch to the rescue. It's a
slick little product.

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

Date:	Thu, 10 Oct 1996 08:52:22 -0700
To:	netw4-l@bgu.edu
From:	Floyd Maxwell <floyd@direct.ca>
Subject: Re: Windows 95 on diskless workstations -Reply

>>Who on earth still has PC's with a need to run diskless win95?
>
>That's a good question. The resources required to run Windows 95 from
>the server would undoubtedly drop your performance to such a level
>that the gain in performance from NOT running Windows 95 from the
>server would far outweigh any benefits perceived or otherwise. Also,
>the amount of storage required just for the Windows 95 CD would be
>prohibitive on most servers. <snip>

I think sys admins realize that we are all going to Win95 because
it is a forced march...not better, just "new", "improved" and
defacto "the only game in town".

So given that we are stuck with Win95, (at least until Win97 falls
from the sky) what is the best way to manage the beast?

Prior to Win95 I was in the "install Windows on the C drive" camp.
I regard Win95 as the ultimate monster demo app...install it for
a while, play with it for a while, watch it crash and burn for a
while and then spend quite a while cleaning up the mess.

Well, this situation can be substantially improved with a read-only
server installation that does not commit one's local C drive to
the battle...

As to disk space for the CD-ROM...under 100 MB gives you everything
on the CD but the "expo" marketing rubbish.  If you just want the
Win95 .CAB files, then you only need 34 MB.  Expanded and installed
you are probably looking at 100 MB needed.

By comparison, my local install of Windows 3.11 is taking up 54 MB
in \Windows and \Windows\System alone and I have installed very few
applications indeed.  Our server install of Windows 3.11 is taking
up 51 MB in the root directory alone.

As to performance, this is a non-issue provided "the system" (server,
cabling, NICs, local machines, settings) is *engineered*.  And
speaking of engineers, there happens to be a mighty competent one,
a Professor of Electrical and Computer Engineering at the state of
Utah, who has worked with a team of others for over a year on this
very problem and created a very helpful document, available by FTP
from  netlab2.usu.edu,  sub-directory /misc,  file:  w95insps.zip

_that's_ who on earth!

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

Date: Mon, 14 Oct 1996 11:24:26 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Re[2]: Doubleheader

>I think you're really way off base on this one. LFNs have been
>around for many, many years on UNIX boxes. 95/NT are just now finally
>getting their act together. Here's our mission essential, justifiable
>reason for LFNs. Some of the hardware development tools run only on
>NT, and these programs are developed to be placed on a server platform
>of some kind -- either NT or Netware. The way I have created the
>driectory and filenaming standards for engineers, relies heavily on
>LFNs. There are many consumer products under development, all
>involving software, hardware and mechanical engineers sharing data,
>collaborating on projects or even on different projects, etc. LFNs
>make it very nice and easy for them to find the data they need
>throughout the project lifecycle. The flipside of all of this, since I
>have to admin these folks, I also need to be able to manage all of
>this data, most of which I have no idea what it is. The most important
>function is recovering from a partial meltdown of the directory
>structure. Total loss of a volume is fairly easy to recover from if
>you have a good backup. Essentially, the directory and filenaming
>standards are an extension of the UTAHSTD.DOC available on
>netlab2.usu.edu. Essentially, LFNs are not a toy, but can be used to
>enhance network administration and useage.
------------
	<omitting the rest of the discussion>
	These things turn into near-religous affairs if we aren't careful.
Long filenames do have their place and benefits, without question. And
that's not the issue today. What is the issue is the range of applicability
of such names to the general work environment. And right now that range is
very small indeed, alas. Even Win95 itself is not fully lfn compliant, so
I recall.
	Thus managers have to make decisions about the environment in which
people work and how to make things perform smoothly; it's a systems problem.
Send files outside the local nitch and see what happens with incompatible
formats.
	As times change the environment changes too, and usually we try to
stay near the center of gravity.
	Joe D.

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

Date: Thu, 17 Oct 1996 10:44:00 -0400
From: "QUIBELL: MARC" <txh8205@TEXCOM-HOOD.ARMY.MIL>
Subject: Re: Client32 printing

>Hi All, I have installed Novell Client 32 on a working MS Win95
>workstation.  The install went fine and everything worked except the
>printing....Win95 said the printer was off line, and the printer icon
>was greyed.  Joe D. suggested I NOT let Win95 control printing, soooo I
>put the capture commands in my login in script and Client 32 could not
>run the script.  The script that runs is the <DEFAULT> script....if I
>select the system login script Client 32 does not login correctly.  I
>tried to put the capture commands in the Winstart.bat file with no luck
>there either.  Is there a soultion to this?....how do I NOT let Win95
>control the printing?  All thoughts and suggestions will be appreciated,
>thanks....JWS.

Capturing in Win95, Client 32 in Netware 4.x is a little tricky indeed. You
did not specify your Netware version, so I guess it is 4.x, since Win95 is
having a hard time finding the print queue (greyed out). In order to capture
a printer in Netware 4.x and Client32/Win95 not in your bindery context, you
must find the print queue using the Network Neighborhood. Double click on
down the tree to your context where the print queue objects reside and right
click on the print queue object and select "Capture printer port". Hope this
helps...

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

Date: Mon, 21 Oct 1996 16:45:47 -0400
From: Justin Wright <Mail2Jus@AOL.COM>
Subject: client 32 auto login

I don't remember who was asking this, but I came across this doc:

Start RegEdit
Insert binary key: autologon
   at
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Network\Real
Mode Net\

  to disable, Insert value 00
  to enable , Insert value 01, or remove key

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

Date: Wed, 23 Oct 1996 15:32:26 -0500
From: ???
Subject: Auto Login for Win 95

1. Copy the LoginW95 icon into the Startup group and change it's
properties so that the command line reads :

c:\novell\client32\login\loginw95 <username> /cont.

Make sure that there is a space between the user's name and /cont.

2. Hit the Start Button and Run REGEDIT.EXE
expand the HKEY_LOCAL_MACHINE then
     SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Network

then click on the Real Mode Net.  When the items on the right hand side
become visible right click below the bottom item (eg transport). Choose
New Binary Value and type AutoLogon for the name and press Enter. Right
Click on the new AutoLogon item, choose modify and enter 00 into the
dialog box.

As long as this account doesn't need a login password (SYSCON) then the
login won't stop and wait for user intervention. If using this facility
put a Station restriction on the account so that it can't be used from
any other computer, limit the number of logins to one, and limit the
user's rights to the minimum needed to carry out the job.

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

Date: Thu, 24 Oct 1996 19:01:40 -0600
From: Kevin Pidd <KEVIN_PIDD@novell.com>
To: netw4-l@bgu.edu
Subject: Re: installing win95 from an image -Reply

>A while back someone asked about duplicating win95 installations to
>ease the process for doing a large # of machines. Well, I just got my
>hands on a wonderful app called Ghost that'll do just that.  It's at
>www.ghostsoft.com and you can use a server to store the image, a CD,
>or go from PC to PC via netbios or a parrallel cable. Cheap easy & fast...

I downloaded and tested this and I was quite impressed.  You can copy
the image to a netware server over IPX and then restore it with a boot
floppy with enough vlms to connect to the server.  It took seven minutes
to install win95.

As I have to install a Win95 workstation nearly everyday to do testing on
which takes nearly an hour, using this method takes less time than it
used to take formatting the hard disk.  What I like with ghost is that no
disk preparation is required.  It can be unformatted, formatted with a
different O/S and a different size from the original disk the image was
copied from.

The only feature I found missing was that it writes over the whole
physical hard disk, removing any existing partitions.  It would be great if
you could just restore to a nominated partition.  The Ghost support people
said they would add this in a future release but i wondered if any similar
product were avaiable that do that now.

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

Date: Thu, 24 Oct 1996 20:45:37 -0500
From: Darwin Collins <dcollins@fastlane.net>
To: netw4-l@bgu.edu
Subject: Re: installing win95 from an image -Reply

>I downloaded and tested this and I was quite impressed.  You can copy
>the image to a netware server over IPX and then restore it with a boot
>floppy with enough vlms to connect to the server.  It took seven minutes
>to install win95.
>
>As I have to install a Win95 workstation nearly everyday to do testing on
>which takes nearly an hour, using this method takes less time than it
>used to take formatting the hard disk.  What I like with ghost is that no
>disk preparation is required.  It can be unformatted, formatted with a
>different O/S and a different size from the original disk the image was
>copied from.

Sounds most excellant!

>The only feature I found missing was that it writes over the whole
>physical hard disk, removing any existing partitions.  It would be great if

Bummer.

>you could just restore to a nominated partition.  The Ghost support people
>said they would add this in a future release but i wondered if any similar
>product were avaiable that do that now.

I just ran across a file called doslfn16.zip.  See:
	http://www.fastlane.net/homepages/dcollins/rollout.shtml
which illustrates how we use it.

It's a bit of whinning, but, I'll clean it up with sample batch files
from our sites. It's not as quick as your case, but, it may be useful
for those 'co-existence' deals.

---------

Date: Fri, 25 Oct 1996 10:54:32 -0800
From: Darren Rogers <DJLIST@foursquare.org>
To: netw4-l@bgu.edu
Subject: Re: installing win95 from an image -Reply -Reply

I also just burned a 'bare-bones' Win95 image onto a CD.  Now I boot on a
floppy that has my cdrom drivers on it and access the CD which has a
copy of ghost, and the image.  Fire it up and blammo!  New win95
installation.

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

