
------------------------------------------------------------------
NOV-W954.DOC -- 19980316 -- 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: Fri, 1 Aug 1997 22:11:42 +0200
From: Renke Hobbie <Renke.Hobbie@CIP.PSYCH.MED.UNI-ERLANGEN.DE>
Subject: Re: Has *anyone* got a Shared networked Windows95 solution ???

>I'd love to know how you got rid of the
>	"<machine-directory>\profiles\<username>" copy.

I have written a small Turbo-Pascal program username.exe
which sets the environment-variable %USERNAME% with the
login-name of the user. A part of the autoexec.bat for
e.g. PC-11 look like this:

...
C:\WINDOWS\net use F: \\BLAUBAER\SYS
C:\WINDOWS\net use G: \\BLAUBAER\SYS\WORKSTAT\PC-11
username
...

The shared windows folder is on drive f:, the machine-directory is g:\win95

And this is the winstart.bat (location: shared windows folder)

@echo off
call g:\win95\delold.bat
if "%USERNAME%!"=="!" goto notset
echo deltree /y G:\win95\profiles\%USERNAME%\*.* >g:\win95\delold.bat
echo cls >>g:\win95\delold.bat
goto end
:notset
del g:\win95\delold.bat
:end

Every time a user logs in, delold.bat deletes the local user profile
of the previous user, and after that, a new delold.bat is created.

In case someone want to use this, I have placed
username.exe is on ftp://131.188.198.11/pub/username/

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

Date: Thu, 7 Aug 1997 16:53:14 +1000
From: Scott Marshall <esmarshall@USA.NET>
Subject: Re: win95 & rprinter ( is there a replacement)?

nptr95.exe: 870530 bytes
Readme for NPTR95.EXE - C32 Win 95 Nprinter -- 8-2-97/21:46p
This file contains the released IntraNetWare Version of NPRINTER for
Windows 95 (NetWare Nprinter Manager) that is compatible with the
NetWare Client 32 for Windows 95.

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

Date: Thu, 7 Aug 1997 08:28:36 +0100
From: "Erik Bos, AMC afd. PC-LAN" <A.H.Bos@AMC.UVA.NL>
Subject: (Fwd) Win 95 and licensed connections

>We're running 13 Netware 4.1 and 4.11 servers and Win 95 with
>Novell's Client 32 on our workstations (around 1600).  We're finding
>that users who should only be authenticated to one server are
>showing up as authenticated to other servers randomly, thus taking
>up a licensed connection.  These people have done nothing to attach
>to these other servers.  I realize now that this was also possible
>with nwuser under Win 3.1, but you had to deliberately browse the
>network with it to authenticate to other servers. This will become a
>major problem once school is back in session.  A server's licensed
>connections could easily be used up when large numbers of users are
>on the network.  Is there anything I can do to curb this?

In client 32 you can fill in a preferred server or a context. Just
fill in both of them and select the context. This will make the (now
grey) preferred server do the login-proces. The server wich does the
login process will have an open connection until the user logs out.
So filling in the server on wich the user will do his/hers work will
cause only one open connection. When no preferred server is given,
the first responding server will do the login process, and keps open
a connection until the user logs out, when this server is not the
server the user works on, there is a connection open on both servers.

Of course there are other things wich can couse more then one open
connection, like something in the container loginscript, user
loginscript, startup folder or batch but I think you have already
checked these.

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

Date: Thu, 14 Aug 1997 09:43:57 +1000
From: Michael Strasser <M.Strasser@MAILBOX.UQ.EDU.AU>
Subject: Re: Client32 for NT/Win95 and login scripts

>We run a number of external programs in our login scripts, which has
>worked well for DOS logins, but not so well for NT and Win95 logins.
>I'm checking ways of combining all of the output from login script
>commands and external programs into a single window. Some questions:
>
>1. Has anyone found a slick way of doing this?

No. I found that only the script processor can write to the
"Login results" window. I have a simple Win32 program that
counts new mail messages (*.CNM in SYS:MAIL/xxxxxxxx) and puts
up an alert. It is very crude and relies on being passed the
user ID as an argument. (This is on NW 4.11 but we still use
Mercury and Pegasus in bindery mode.)

>2. Is there any way to control the size of the window created by the
>   login program?

The size and position is saved in the registry in:

	[HKEY_LOCAL_MACHINE\Network\Novell\System Config\Network
	  Provider\Graphical Login\Results Pos]

so any changes you make are 'remembered' (regardless of the
"Save settings on exiting Login" settings on the Client 32
Properties login tab). I guess you could change them in advance
if you had a registry-poking tool.

>3. Is there any way to control the font used - I want to use
>   a non-proportional font.

Not as far as I know.

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

Date: Fri, 22 Aug 1997 11:43:35 -0400
From: Desmond Irvine <dirvine@YORKU.CA>
Subject: Re: Registry Soup...

>>I found the hives that actually hold the username field. Is there
>>anyway of inserting a "%1" for username and then writing some
>>batch file that will accept a single parameter, which will then
>>expand the %1 to the username supplied at the command line.
>>So that the new username can be merged into the registry. i.e.
>
>>file.bat John
>>some instruction here that will look at file.reg substitute
>>%1 with John and create another file2.reg.
>>regedit /e file2.reg.
>
>>Is there any time or location within the win'95 boot process
>>that a command like running a batch file can be inserted to
>>do the above ? other than the autoexec.bat, to update the registry.
>>This will fully automate the imaging.
>
>An undocumented command that is in Win95 is the START command. If you type
>START /? at a dos prompt you get:
>Runs a Windows program or an MS-DOS program.
>
>START [options] program [arg...]
>START [options] document.ext
>
>/m[inimized] Run the new program minimized (in the background).
>/max[imized] Run the new program maximized (in the foreground).
>/r[estored]  Run the new program restored (in the foreground). [default]
>/w[ait]      Does not return until the other program exits.
>
>You can create a BATCH file and put a shortcut to it in your STARTUP group
>with the commands that you want executed. You can try it with this REGEDIT
>command and see if that will work.

Just to extend this a little further you can use REGEDIT to dump the
registry entries you would like updated to a file by highlighting the
entry and then selecting "Export Registry File" from the "Registry" menu
and making sure "Selected branch" is selected for Export Range.  This will
save the registry entries in a text format file with the extension .reg
You can "start" this file and it will automatically import them into your
registry.   I.E. :

   START PASSWORD.REG

Where PASSWORD.REG is:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Network]
"DisablePwdCaching"=dword:00000001

Will disable password caching on the machine.

Since the files regedit creates are text files you can cut and paste
between them to get information you save from multiple branches to make
one file with all the keys you need.

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

Date: Tue, 02 Sep 1997 09:14:29 -0500
From: George Taylor <GTAYLOR@LHSNET.COM>
To: floyd@DIRECT.CA
Subject: Printer Form Feed Problem in Windows 95/Client32

Symptom:
	Printers send an extra form feed at the end off print jobs for DOS
applications run under Windows 95, Windows applications print fine.
Setting no form feed on the Print Settings Tab under Properties for that
printer makes no change, CAPTURE /SH in a DOS window still show Form
Feed as enabled.

Solution:
	Change the default capture settings on the Novell Client 32
Properties settings to show no form feed.

Steps:
	Right Click the Network Neighborhood
	Choose Properties
	Double Click Novell Netware Client 32
	Click the Default Capture Tab
	Remove the Check from the Form Feed box

These setting are identical to the Printer Settings on the Printer
Properties, however they take precedence when printing from a DOS Window.

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

Date: Thu, 4 Sep 1997 13:56:50 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Client32 and Shared 95 install

>Is it in fact possible to run the Client32 with a shared copy of Windows95
>on a Novell 4.11 server?  I seem to find conflicting information.
-------
	C32 cannot remote boot Win95 (diskless client) at this time.
That's a firm answer.
	I have stated several times that this is a project underway at
Novell at this time. Recall, Win95 starts networking after the GUI has
begun and PNP "analysis" has done its thing, and hence that requires Win95
initially. There is no announced date for release of the capability. If
your situation really needs it then please contact your local Novell Office
and make that need known to Provo. This is not brush-off advice.
	Joe D.

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

Date: Fri, 5 Sep 1997 19:50:17 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: win95 workstations advertising as a server

>>>I am operating in a novell 4.1 environment and we have a few win95
>>>workstations.
>>
>>Please look again at the Networking panel. Turn off
>>file/print sharing over IPX.
>>	Joe D.
>
>Another thought - do you use BackupExec? I believe that any
>workstations that have been set up as agents (i.e., set up to be
>backed up over the network) will show up as servers.
>
>Anybody know if ArcServe works this way?
>
>Michael Leone
----------
	BE and AS client agents use their own IPX SAPs, not Type 4 for
NW server. They don't appear in SLIST/NLIST SERVER /B. Win95 uses Type 4
for sharing files/printers over IPX, and hence the major problems from
them. We have plenty of both tape backup programs in use here.
	To see who advertises what over IPX SAPs go to the server console
and Load IPXCON. Select Services. Open up interesting selections to reveal
the MAC address of the station doing the advertising and how many hops
away it is.
	Joe D.

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

Date: Thu, 18 Sep 1997 21:24:17 -0400
From: Dave Wineman <dw@AVCI.NET>
Subject: Client 32 Security Hole

Does anyone know of a way to plug a Client 32 security hole upon startup
with policies in place and forced login before access to the computer
for the following scenario:

I found another security/program glitch with win95/Client32. You know
that if your at the Novell Client32 logon screen and press CTRL+ESC you
get the task manager. And that you can enter a program to run. If you
enter CONTROL and press enter it DOESN'T bring up the control panel like
you would think, it skips the logon (leaves the logon box there) and
takes you into windows. It appears that you get the local start menu
(including MS-DOS Prompt, Explorer, Etc). Try it and see if it does the
same with the old win95. This is at HB with the Win95B machines

Any ideas on how to force the login without bypassing to windows
(not connected to the network?)?

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

Date: Fri, 19 Sep 1997 06:32:10 -0400
From: Desmond Irvine <dirvine@YORKU.CA>
Subject: Re: Client 32 Security Hole

>Does anyone know of a way to plug a Client 32 security hole upon
>startup with policies in place and forced login before access to the
>computer for the following scenario:
>
>I found another security/program glitch with win95/Client32. You know
>that if your at the Novell Client32 logon screen and press CTRL+ESC you
>get the task manager. And that you can enter a program to run. If you
>enter CONTROL and press enter it DOESN'T bring up the control panel like
>you would think, it skips the logon (leaves the logon box there) and
>takes you into windows. It appears that you get the local start menu
>(including MS-DOS Prompt, Explorer, Etc). Try it and see if it does the
>same with the old win95. This is at HB with the Win95B machines

Delete or rename TASKMAN.EXE and the CTRL+ESC trick will no longer work.

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

Date: Mon, 29 Sep 1997 06:48:17 -0400
From: Philip Reznek <preznek@VISYS.COM>
Subject: Re: Bypassing Login prompt - CLient32 win95

>>Does anyone know if it is possible to bypass the login prompt of
>>Client32 in win95? I have a lab set up with 15 machines. No
>>passwords, and I'd like to have the machines login without a login
>>prompt. This was easy under dos, but I can't figure it out under
>>windows 95. Thanks!

Check the TIDs at www.novell.com or your mirror.  There are two; one of
them gives an example of how to modify the W95 Registry to supress the
login prompt.  The Netware user account may not have a password for this
to work.

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

Date: Wed, 22 Oct 1997 11:53:51 -0400
From: Scott Wiersum <SWIERSUM@SETENV.COM>
Subject: Re: More Client32/W95 problems

>Upgraded a Win 3.1 client to Win95.  Upgraded to client32 v2.2.  Ended
>up formatting hard drive and re-installing Win95 from scratch.  Realtek
>PnP Nic installed by win95.  Removed Client32 v2.2 and opted for v2.12.
>All hardware, i.e. NIC working properly according to device manager.
>Computer boots with Client32 splash screen, no GUI Login.  Double click
>network neighborhood and receive message that network is unavailable.
>Have two clients configured identically, one works, one doesn't.
>Attempts to login  result in "unable to locate preferred server".  This
>makes NO sense.  I KNOW the card is working and that Client32 is
>configured properly.  PLEASE, what could I possibly be overlooking?

I had this exact same problem when I was upgrading several Win 3.1
machines.  I'm going to give you more info than you need, but I
think other subscribers to the list will benefit:

Upgrading Win 3.1 (VLMs) to Win 95 (Client32)
=============================================

1 - Copy files from WIN95 CD to F:\INSTALL\WIN95
    a - Copy 95ENU_N3.EXE (Novell Client32) to F:\INSTALL\WIN95
2 - Check for > 130 Mb free space on the client drive.
3 - Backup CONFIG.SYS, AUTOEXEC.BAT, WIN.INI, SYS.INI to C:\STARTUP
    (Just in case...)
4 - REM out (disable) any anti-virus software (in BIOS, too)
5 - Remove HIGHSCAN and NOVCPI from EMM386 line in CONFIG.SYS, if present
6 - Run SCANDISK
7 - Run DEFRAG
8 - Copy files from F:\INSTALL\WIN95 to C:\WIN95 (or C:\CABS) or
    whatever you prefer (this is where Win '95 will read the .CAB files
    from whenever you change it's config... great for clients w/o CD-ROMs.)
    Don't forget to copy 95ENU_N3.EXE (Novell Client32) here, or somewhere
    on the client's hard disk.
9 - Backup C:\WINDOWS to C:\WINDOWS.BAK
10 - Verify network card:
     a - Brand
     b - Model
     c - IRQ
     d - I/O Address
     e - Memory space
11 - Reboot
12 - Run WINDOWS
13 - Exit all running programs
14 - Run C:\WIN95\SETUP.EXE
15 - Install "Custom"
16 - Proceed with installation.
17 - At Network setup, delete all network components (client, protocols,
     adapters, etc.)
18 - Win '95 will start up without network support.
19 - Copy your network card's .INF file(s) to C:\WINDOWS\INF.
     Ususally there's a batch file on your network card's installation
     disk that does this.  For SMC, it is A:\W95INST.BAT.
20 - Restart Win '95.
21 - Windows should automatically "detect and install software" for
     the "new" hardware (your network card).  Usually works for PCI
     type cards.
     a - If it doesn't (usually ISA cards), go to Control Panel, System.
	 Click on the Device Manager tab.  Delete the existing network
	 card.  Click on Control Panel, Add new hardware.  Auto-detect.
     b - Windows should find the network card again, but it will use
	 the new .INF file.
22 - Exctract 95ENU_N3.EXE to a C:\32C (or other temporary directory)
     and run C:\32C\SETUP.EXE
23 - Set your preferred server and preferred tree (I leave context
     blank on single server NW4.1.)  If you are running 3.x, just
     enter your server's name.
24 - Reboot when finished and you should get a GUI login screen.

In your case, pay special attention to steps 15-19.  You should try
*really* hard to find the Win '95 drivers (.INF files) for your RealTek
card.

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

Date: Sat, 1 Nov 1997 21:48:24 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: Client 32 locks out next user

In your Windows directory you will find files that start with the users
name and end with .pwd.

I had this problem on a WS and simply erased the problematic users pwd
file and everything worked fine.

---------

Date: Mon, 3 Nov 1997 09:26:54 -0600
From: Tony Chen <TonyChen@BALLFOUNDATION.ORG>
Subject: Re: Client 32 locks out next user

I am just shooting in the dark here.  I found a problem a couple of
times if my users signed out the client32 using the Start --> Shut Down
--> Close all programs and logon as different user.  My advise to my
users are to use Start --> Shut Down --> Restart.  AND, it takes care
of the problem.

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

Date: Tue, 4 Nov 1997 09:39:46 -0600
From: Tom Kustner <tom.kustner@EMJAY.COM>
Subject: Re: Client 32 locks out next user

>What you suggest would help, but in a multi user environment, where time
>is of the essence, it is a pain to have to wait for the puter to totaly
>shutdown and restart all over again.
>
>The "Close all...." option is supposed to support fast relogins, and in
>most cases it does. If it doesn't, then there is a problem that needs to
>be addressed, sometimes going around a problem is fine, but not in every
>case.

We also had minor problems, specifically, when PCs needed to be backed
up by ARCserve.  If they did the "login as a different user", it
didn't work out.

The bottom line is that we created an icon for people to use to reboot
the system.  We're assured that people are rebooting their system on a
regular basis and since they normally do this only when heading out
the door, it doesn't affect them (though Client32 2.20 has a bug where
shutdowns are hanging at various times - Novell is working on it).

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

Date: Thu, 13 Nov 1997 10:21:28 -0700
From: Tim Madden <tmadden@ASPENRES.COM>
Subject: Re: w95 32 bit client

>What are the advantages of using the 32 bit client instead of the
>standard Ms client?

Required for:
	- NAL
	- NWADMIN
	- NDSMGR
	- Pegasus Mail for Windows 32-bit

Also:
	- More configurable
	- More frequently updated with bug patches
	- It's not MS

---------

Date: Thu, 13 Nov 1997 14:46:43 -0500
From: Eddie AFC Evans <eevans@AFC-IT.COM>
Subject: Re: w95 32 bit client - Don't overlook Microsoft

Well, it is not required for Pegasus Mail for Windows
32-bit.  I used Novell's client unhappily for a month or two, it
failed to connect frequently, and ate the registry on Fridays.  I am
fortunate to have had a tape drive connected to workstation, but still
a pain.  I stopped using the Novell client, and use Microsoft's
service for NDS.  While it is true that it is not 'more configurable',
I've not needed to change anything, and found I could not, and I have
the benefit of not having (seemingly) six million things to check.  As
far as 'More frequently updated with bug patches', well, it works!  I
do not claim it to be bug free, but I have no problem with it.  I did
have a bit of work getting NWADMIN to work, I had to install a Novell
client and copy *.dll, etc but having done it, I am quite happy, and
the workstations are very stable, as long as I keep user's from .0
release software!  Some objects are listed as unknown, so I have kept
the HDD with client 32 on it, use it once or twice a year for Lotus
Notes admin stuff.  I think that has more to do with Lotus than Novell
or Microsoft.  Environment is NW 4.10 patched, Landesk, Notes, Office
95, Smartsuite 96, Corel, Adobe, etc on 486/33 through PII 266 client
hardware running DOS 6.2, W3.1, WFW3.11 W95 retail, OSR2, and OSR2.5.

---------

Date: Fri, 14 Nov 1997 10:43:55 +0000
From: Graeme Findlay <gfindlay@INVERESK.CO.UK>
Subject: Re: w95 32 bit client - Don't overlook Microsoft

>Well, it is not required for NWADMIN, or Pegasus Mail for Windows
>32-bit.  I used Novell's client unhappily for a month or two, it
>failed to connect frequently, and ate the registry on Fridays.  I am

<SNIP>

Ermm.. It IS required for Pegasus Mail for Windows 32-bit. It will
not connect to any form of Netware without the Client-32.

The 16-bit version of Pegasus/WIN will run on either netware client
(MS, Novell)..

Extract from WGUIDE.HLP from the Pegasus Mail archive file :
=====
* If running the Win32 version in NetWare mode, please be aware that
it will ONLY work if you are using Novell's Client/32 requester: it
will NOT work with the Microsoft NetWare requester because of
incompatibilities between Microsoft's code and the Novell interface
libraries used by Pegasus Mail. This problem can only be corrected by
either Novell or Microsoft - it is outside our control. This
restriction does NOT apply to the 16-bit version of WinPMail - if you
prefer to use Microsoft's NetWare support modules, we suggest you use
the 16-bit version until either Microsoft or Novell come out with a
correction.

* At present, only Bindery mode NetWare support is available for the
Win32 version of Pegasus Mail. NDS-mode support is under development
and will be released early in 1997. If you need to run in NDS mode, we
suggest you use the 16-bit version of Pegasus Mail.
=====

---------

Date: Thu, 13 Nov 1997 17:47:00 -0500
From: David Weaver <daw@DECT.COM>
Subject: Re: w95 32 bit client

>>What are the advantages of using the 32 bit client instead of the
>>standard Ms client?

MS Client does not support NDS.  There could be a performance issue also.

---------

Date: Thu, 13 Nov 1997 18:10:31 -0500
From: Doug Summers <dsummers@SHERIKON.COM>
Subject: Re: w95 32 bit client

There's an update for this client from MS that DOES support NDS. The
main advantage I can see for Client32 is all the new utilities are
requiring it (NAL, NWADMIN95, etc.). What I've found is that Client32
runs great on 4.1x w/o using ODI drivers (at least on our 60 workstation
office).

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

Date: Thu, 13 Nov 1997 13:59:58 -0500
From: Steven Yuen <YUENS@TOWERS.COM>
Subject: Re: LOGIN95.EXE

>We'd like to place the shortcut link to the Login box (ie,
>C:\NOVELL\CLIENT32\LOGINW95.EXE) on the W95/NT desktops to make logging
>on and off easier for our younger users (this is a K-12 setting)
>However, the problem is that when activated from the desktop when the
>INWClient box comes up by default it attempts to log them into the tree
>and not the Preferred Server as is our setting in the control panel.
>
>Does anyone know how to force this?? Note- when shutting down/starting
>up normally (ie, START button) the preferred settings are correct (ie,
>login to SERVER)

Just create a shortcut link to loginw95.exe with the following switches:

	c:\novell\client32\loginw95.exe server_name/

More login command line switches can be found from Novell's Knowledge
Base article #2923763.

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

Date: Wed, 19 Nov 1997 01:11:40 UT
From: Weldon Grant <WeldonGrant@CLASSIC.MSN.COM>
Subject: Client32 v2.2 bug

From Infoworld Nov. 17, 1997 pg. 57...

"Novell has identified a data corruption problem with its Client32 2.2 for
Win95 when it is used to open a large number of DOS files for Microsoft's
FoxPro for DOS.  If you use a FoxPro application that opens up more than 170
files, you are at risk of corrupting your databases.  Novell must totally
redesign the client, which it has plans to in the next release, in order to
fix this problem."

---------

Date: Tue, 18 Nov 1997 23:29:57 -0500
From: Larry Hansford <hansford@ERINET.COM>
Subject: Re: Client32 v2.2 bug

This has been discussed heavily on list servers for Foxpro applications.
I have found that sticking with V2.12 has prevented this problem.  No
reason to load V2.20 until it is corrected.

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

Date: Mon, 24 Nov 1997 09:22:16 +1100
From: "Peckston, Mike MB" <Peckston.Mike.MB@BHP.COM.AU>
Subject: Re: Client 32 2.2 error with Office 97

>Since updating our users to Client 32 2.2, we have experienced a
>strange side effect.  The circumstances are that upon saving a
>document in Office 97 (Word, Excel, etc.) and exiting from the
>application, a message box appears:
>
>	"Novell IntranetWare"
>
>	"This connection must be maintained for Novell Directory
>	 Services use on tree <tree name>.  It can only be removed
>	 after logging out of Directory Services on the tree.
>	 Do you wish to log out of Directory Services on tree
>	 <tree name> now?"
>
>It appears that the Office 97 application is trying to disconnect or
>drop a connection to the network and that Client 32 is throwing up a
>cautionary message box.  Why though, has this only occurred since the
>upgrade of Client 32.  I have tested a machine without the 2.2 release
>but with all other things being equal and there is no problem.
>I subsequently upgraded the client and the problem is present.

I had this occuring when using the exchange client to connect to a
msmail postoffice on a novell server. When i pointed the client to the
novell server using the UNC path the client would log me out of the
server when it was exited. Using a drive mapping (eg r:\maildata) did
not cause this problem. The way i understand things is that recent MS
apps send a "log off server" message which the MS networking client
ignores but the Novel Client 32 v2.2 is obeying (another good MS
strategy to make the competiton look bad ?). I logged a fault with
Novell about this so expect this issue to be fixed in the next version
of the client.

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

Date: Mon, 24 Nov 1997 10:46:06 -0500
From: "Todd M. Wilkinson" <tmwilkin@MAILBOX.SYR.EDU>
Subject: Re: 

>We are connecting Toshiba portables to an Intranetware network, using
>Windows 95 and Novells 32 client. Does anyone know how I can stop a user
>being able to use a modem whilst conected to the network via a base
>station? When the machine is not in the office the user needs to access
>the network.

Right click on my computer and choose Hardward profiles.  From there
create two profiles.  One for the office and one for home. Then reboot
the machine and everytime you reboot you will be given choices to boot
either into the office setup or the home setup, choose the office setup.
While running this config you can choose the Device Manager (again right
click my computer - properties) and disable the modem while in this
configuration.  This won't prevent them from reconfiguring it, but I
am assuming you are just trying to get a few apps to not recognize the
modem, in this case that will work.

NOTE:  If this is a case were applications using TCP/IP keep trying to
dial out you may be able to disable that via the Internet Control panel
under connect the the Internet as needed.  Sometimes this will try to
dial out even though you have an IP connection via a local LAN.

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

Date: Tue, 2 Dec 1997 18:35:12 -0500
From: Don Voss <voss@CASCOMP.ALBANY.EDU>
Subject: Re: Client32 installation problem

>We just upgraded our Netware 3.12 LAN to IntraNetware 4.11 and tried to
>setup Client32 on our Win95 computers. The Client32 setup appeared to work
>alright but when we reboot the computer the system hangs. We turn off the
>PC and reboot in Safe Mode, etc.. Are we being too impatient at this step?
>
>I thought the problem could be in my version of Win95. I have a Compaq PC
>and ran the Win95 setup to re-install the OS. We also have similar
>problems with generic PCs running Win95.

I have found a few things to be helpful when installing client 32
material.

Assuming a network install.

1. make sure win95 is fully patched. [a&b version]

2. make sure the current and correct network driver is installed in
win95.

3. setup MS nw client and tcpip material. Test.

4. if ms networking is being used, make sure its running over TCPIP
net bios. Turn off all bogus protocols [netbeui]

5. If servers are ethernet_II frame type, then set the ms client
material to same. [can be done later but will be picked up if done
before]

6. copy down the client32 uninstall utility as a backdoor. [save it
in a dir.] I dropit into the local created novell client32 tree after
sucessful conversion.

7.  make sure the correct 32 ODI driver is in or added to the network
client 32 install archive. [there are modifications to be done to
nwsetup.ini under [inf] heading regarding NIC being used and other
NIC related material to be dropped in client32 install point ..see
novell client32 help files and there usually are readme.txt's  in
your NIC client32 upgrade material]

8. put current cab files in client32 install point.

9. nows a good time to read the docs ....

10. use the current client 32, not the default client32 material from
4.11 install. [download from www.novell.com]

11 fire off setup.

11. configure details from defaults during setup phase, [option
near end of install]. We stop all client side caching. Force one
frame type. Dir sort option, add logical printers, etc.

12. No compaqs here but I would not be surprised if they had a step
or two of their own to check on.

Members of the list have mentioned trouble when converting to odi
material and have mentioned using the ndis stack. I have not seen
that here. Troubles I have seen are win95 installs using wrong NIC
material [ see #2,  here it was gateways with installed DEC chip
drivers on SMC NICs .., run client32 uninstall, SMC material
upgraded ..client32 install rerun, resolved]

---------

Date: Tue, 2 Dec 1997 18:23:44 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Client32 installation problem

>8. put current cab files in client32 install point.

One point:  The .CAB files from Microsoft should be
placed in the following directory:

	C:\Windows\Options\CABs\

This is the standard location of these files throughout the
industry, you'll find it this way on ASTs, Compaqs, IBMs, etc.

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

Date: Thu, 11 Dec 1997 15:57:33 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Really easy VLM question

>Could someone please tell me how to install VLM's on a Windows95
>machine to use on a INW 4.11 network?  I have tried and tried and
>can't get it to work.
----------
	I put this into the category of "have disk." That is, in Control
Panel, Network section, choose to add a client from Novell, and choose
"have disk" to grab the VLM material from a convenient directory (rather
than a real floppy).
	If you are using VLMs to get to the net already then I strongly
recommend selecting the lan driver component as "Existing ODI Driver"
and not a driver by specific name or vendor. To get this to work smoothly
I remove all networking components in the Network panel and then add the
lan driver (existing ODI) and the NW client (have disk). Selecting Existing
means use the driver already loaded and inform the system that Win95 is not
to try loading one; it also prevents stumbling over NDIS drivers shipped
with Win95. A clean start also removes extra copies of ODINSUP if they are
present.
	Joe D.

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

Date: Wed, 17 Dec 1997 15:08:05 -0500
From: "Deborah J. Becker" <dbecker@CLARK.NET>
Subject: Re: IE 4.0 Active Desktop and Netware 3.12

>>I recently installed Internet Explorer 4.0, including the Active
>>Desktop options.  Now everytime I bring up the Windows Explorer and
>>access a network drive, I get a General Protection Fault (GPF) in
>>the KRNL386 DLL.  I did a search on the Novell Knowledgebase and on
>>Microsoft's Knowledgebase, but I couldn't find anything.  It works
>>fine if I access the local drives, or if I access the network drives
>>through the File Open dialog box in an application.  I uninstalled
>>the Active Desktop, keeping the IE 4.0 browser, and everything works
>>fine again.

Well . . . recently I had a new system with Win95B, IE 4.0 (no Desktop
options enabled) and an older version of Client32 (which one escapes me
at present) and had the same problem. Couldn't find a reference to this
anywhere and it was driving me crazy.

Installed Client32 v2.2 and it disappeared...

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

Date: Mon, 29 Dec 1997 11:55:53 -0700
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: win 95 network config

>>I am interested in others experiences in configuring Windows 95 in a
>>Netware 4.11 environment. Till now, our users have Windows 3.11 with
>>a shared system directory in an network directory  and the windows
>>directory in their homedirectory.
>>
>>Because all applications are also stored on the server the current
>>environment let's users switch from PC's very easily without loosing
>>their desktop layouts and applications. This is considered very
>>important by the management and I agree with that, also
>>administration can mostly be done central.
>>
>>I understood from a paper by Joe Doepnik that Windows 95
>>(win95boo.txt) under certain circumstances can also be run in this
>>mode but only when you use vlm's. However, I want to use long
>>filenames which  is not possible to use with vlm's.
>>
>>To make a long story short, I'd like to know if it is possible to
>>create a windows 95/intranetware environment in which the following
>>is possible:
>>
>>1. Central management of all user's applications/desktop
>>2. Users can login from any PC and get their Win95 desktop and
>>   applications within reasable time
>>3. User can store files with long filenames
>>
>>I read something about a product Novell is working on, called ZEN,
>>anyone knows more about that?
>
>Some comments:

	There are too many categorical statements below which simply are
not true, so I am adding this enhancement.

>*  Do not try to run Win95 from the network.  I evaluated this config and
>there are too many limitations, especially with the real-mode login.
>You must run Win95 from the local drive, and don't use VLMs.  (I
>don't understand your reference to the 8.3 name problem and VLMs.)

	The person can indeed run Win95 from the network. Lots of people
do so. One can run it from diskless clients remote booting to the server,
but the cost right now is no long filenames (not a loss by my standards).
	For those still in the dark on filenames, long filenames are a
kludge pasted into Win95 and later. VLMs don't support long filenames,
99% of the non-Win95/NT software does not either, so beware. Novell's long
filename support (os2.nam for NW 3.x, long.nam for NW 4.x) does not
completely agree with MS' usage either. Hacks upon hacks in the MS stuff,
where the rules are never clear nor stable and which are best avoided when
possible.

>*  You can still run your applications from the network.
>
>*  I believe you can setup roaming profiles that will do *most* of what you
>need. I don't have much experience with this, so I will let others comment.

	Please be careful here. MS Profiles are another hack. NW security
is good, MS security is an oxymoron. One does not have to use MS Profile
stuff, but of course you can if you wish.

>*  I don't know if application INI files are conveyed with the roaming
>profile.
>
>*  Consider using WinInstall to distribute your applications.  This is a
>very useful program for capturing Windows applications installations,
>especially now that we have the complex Registry to deal with.
>
>*  You can try to lock down the desktop by using system policies, but it
>can be very difficult to find the right balance where the user has enough
>rights to do what they need, but not enough for them to cause trouble.

	To put it mildly.

>*  If you don't have the Win95 Resource Kit yet, buy it.  It has a lot of
>information you will need.

	It does, and lots of it is inapplicable. The MS Resource Kit was
written well before Win95 was released, and Win95 has never been stable
enough to nail down in hard copy format. I read the preliminary stuff when
Win95 was in the beta stages and the comparison was humorous. Just because
it is written doesn't mean...
	Joe D.

---------

Date: Mon, 29 Dec 1997 14:17:53 -0500
From: CHENGD1 <CHENGD1@WESTAT.COM>
Subject: Re: win 95 network config

By the way, Microsoft doesn't support Win95 shared on the network.
I couldn't believe it when the network support engineer told me that,
but they wouldn't answer my questions about machine directories and
they refunded me the $35 charge for the call.  That was 1 1/2 years
ago, so perhaps their policy has changed.

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

Date: Mon, 29 Dec 1997 16:13:38 -0600
From: Brian Scott <bscott@SYSTEMA.WESTARK.EDU>
Subject: Windows95 "finding" things

Windows95 will search for the target of a shortcut if it cannot find
it.  This sounds nice ( I'm not sure what use that would be ), except
what it finds may or may not have any relation to the original
application.  When a volume is unavailable for a while and the drive
does not get mapped, 95 will find the closest thing and change the
icon.  Now because of a drive failure ( which is not a big deal,
problem fixed in an hour ), several dozen people have
i:\public\wsupdate.exe in place of there k:\pegasus\winpmail.exe
icon.  I spend the rest of the day fixing icons.

Someone please tell me that there is a registry setting to turn of
this searching "feature".
HKEY_LOCAL_MACHINE:Leave\My\Icons\Alone (dword) = 1

This time I was lucky, school was out and I just had a few dozen
icons to fix.  Any other time I could have had a few hundred, and I
would have been very angry at microsoft (again).

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

Date: Thu, 8 Jan 1998 11:06:28 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: client 32 doesn't automaticly logon at startup

>I have a problem with some new workstations (IBM PC 300 GL) with
>win95 OSR2:
>the workstation doesn't automaticly logon to network at startup ( the
>logon dialog box doesn't show up), so user must manualy click Novell
>Client icon to log on.
>
>This problem is the same with microsoft (win95 default) NW client.

This is an OEM problem.  You need Novell's TID #2906454.  Go to the
Novell KnowledgeBase online, and search for "2906454" then click on
the following title:

	C32WIN95 - No GUI Login Prompt upon Startup

The OEMs use this registry entry to automate the Windows 95
installation, and so it doesn't get reset properly.  This is the
cause of the problem.  This TID explains how to fix the offending
registry entry.

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

Date: Fri, 9 Jan 1998 10:16:24 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Win95 and TCPIP with Netware 4.11

>I setup some computers to boot remotely from Netware and
>using Win95.
>
>My problem is with TCPIP.  I can not setup TCPIP with this configuration
>because when I setup TCPIP it adds the ODIHLP.EXE, and this means that
>the name of the PC must be unique.....but as I use the same fields for
>all PC's, the PC name is the same for all PC's.
>
>So my question is if there is another way of installing TCPIP
>in a Windows95 than using Microsoft TCPIP?

Yes.  Use Novell's IPX/IP gateway.  It's very easy to configure, you
only need one parameter on the client - the name of the IPX/IP
gateway server.  This will solve your problem.

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

Date: Fri, 9 Jan 1998 19:10:09 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Client32 v2.20 - How to make diskettes

>>>>Does anyone know where I can purchase the latest version of
>>>>Client 32.  I have tried downloading it but there is no makedisk
>>>>utility.  Thanks.
>>>
>>>Go to the following URL with Netscape Navigator:
>>>
>>>	http://www.novell.com/novellsw/platform.html
>>>
>>>You will find Client32 v2.20 (or newer) for all platforms.
>>
>>The client software is there, but there's still no way to create
>>installation diskettes.  Even the download files are larger than
>>will fit on a diskette.
>
>I always connect a new client with Microsoft's 32 bit client.  Then
>install the Novell client across the network.

Expand all the Client32 self-extracting archives to a subdirectory
on your hard drive, or somewhere on the server, get a copy of
Arj.Exe, then use the following DOS commands while in the Client32
directory:

	Copy  <full path to Arj>\Arj.Exe  A:\
	Arj  a  -va  -r  A:\Client32

You will be prompted to insert more diskettes.

When you get to a Windows 95 workstation, type the following
DOS commands:

	MD C:\Windows\Options
	MD C:\Windows\Options\Novell
	MD C:\Windows\Options\Novell\Client32
	C:
	CD \Windows\Options\Novell\Client32
	A:\Arj  x  -v  -y  A:\Client32

You will be prompted to insert each diskette.

When you return to the DOS prompt, remove the last diskette, and
proceed with the installation by typing "Setup" (remember to switch
back to this DOS window and type "Exit" to close it).

The reason I use the "C:\Windows\Options\" directory is that it's
an industry standard.  The manufacturers have been copying all the
Windows .CAB files to the "C:\Windows\Options\CABs\" directory to
speed up the installation.

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

Date: Thu, 22 Jan 1998 17:46:33 -0700
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Office 97 admin installation   *license*

>If your install CD lacks an ADMIN subdirectory you may think about
>obtaining the Resource Kit for the product involved. If I remember
>correctly it contains tools for Administrators. If not you can still
>benefit from the book.
>
>Furthermore. To know about the valid options for SETUP type: SETUP /?.
----------
	Yes, web browser to MS and look in the "ork" area for Office Resource
Kit. It's full location is in the documentation file of MS Office 97. No
money needed, all the stuff is there.
	One important option not listed (I believe) is /F to not use long
filenames. It must be the last item on a command line.
	Joe D.

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

Date: Thu, 29 Jan 1998 15:20:16 -0400
From: Jon Dustin <jdustin@USM.MAINE.EDU>
Subject: A good 'easter-egg' from the Novell programmers...

While 'sniffing' our lab network yesterday afternoon, I came across a
frame that had some peculiar contents...

The sender was a WIN95 machine, running client32 v2.2, and the server
was a NW v4.1 server. Near the beginning of the whole login process,
the client sends a 'Create Service Connection' frame to the server,
with some seemingly arbitrary data inside.

Shortly into the 'NCP' portion of the packet, the phrase:

	Client32 reigns supreme!!!

appears, right after 'LIP Echo Data'. It seems Novell programmers
do have a sense of humor...

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

Date: Thu, 5 Feb 1998 13:10:20 -0500
From: Rex <rex.henderson@SANTAFE.CC.FL.US>
Subject: Finding netsetup.exe on win95 cd

have you looked in the CAB files in the win95 directory of the cd-rom.
These are the compressed OS files.In DOS, use the EXTRACT.EXE utility in
that
directory to obtain a list of all the files:
cd cdrom:\win95
for %x in (*.cab) do extract /d %x >> c:\temp\dirlist.txt

next, edit dirlist.txt and perform a search for "netsetup.exe"
find the cab file it is in then extract it from that cab file:
extract win95_xx.cab netsetup.exe /Lc:\temp
Rex

I am looking for the program netsetup.exe , I guessed it would be on
my win95 cd; but no it was not. There is a directory called admin
with a sub directory called nettools, but  no directry called
nettsetup & no file called netsetup.exe. Please some one where can I
find this file.?? Do only certain versuions of the win95 cd have this
program, & if so which ones?

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

Date: Sun, 8 Feb 1998 10:08:55 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: NDS error -631, issue and solution - long

<huge snip>

The only position I could take, was that the error message was false,
and that there was some problem accessing the Master replica for
information, and that I was somehow getting erroneous information when
I used Nwadmin95 and NdsManager. I called up my guru and he sent me a
patch for the registry which fixed the issue immediately.

There is a bug/enhancement in both programs, where they will access
the closest replica of a partition in order to get info about it.
There is a lot of logic in this, especially when regarding replicas
spread around, but there can also be problems if the sync takes a
long time, or if there are problmes reading the replicas.

The patch to the registry which is as follows : (copy to a file called
whatever-you-want.reg and double click it to have the info updated into
your registry).

[HKEY_CURRENT_USER\Software\NetWare\Parameters\NetWare
Administrator\User Creation]
"Use Master"="True"

This tells the programs to always use the Master of a partition as
default.

the moment I performed this change to my registry, the error went away,
and has not returned since. As well as, access to my Nds via Nwadmin95
and NdsManager is faster than it was before.

So, as you can see, sometimes errors we get have nothing to do with the
actuall problem. In this case, the error was in a bug in the programs
and had nothing to do with bindery contexts.

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

Date: Sat, 14 Feb 1998 14:07:49 EST
From: joe flowers <Novell@HCL.CHASS.NCSU.EDU>
Subject: Source code for a Windows 95/98 Login Program

I put the complete source code of my Windows 95/98
login program at

	http://hcl.chass.ncsu.edu/joe/joenp/

Fundamentally, the program is a shaved down "Network Provider"
DLL as described in Microsoft's Windows 95 DDK.

Basically, the program provides:

1. A completely customizable login GUI interface, of course.

2. Contextless NDS logins.

3. Sets the Windows 95 machine's date & time to the same date & time
returned by the "primary" NetWare server connection.

4. Runs NDS login scripts.

5. In my case, maps a drive letter to a user's Unix AFS "home
directory" file space via clusters of SAMBA servers.

6. Sets the Windows 95 "system logon" username and password, and
passes the username and password back to be used by all other
installed Network Clients for "network wide" logins.

I hope it is helpful, and please let me know of any bugs.

joe_flowers@ncsu.edu

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

Date: Sat, 14 Feb 1998 16:18:56 -0500
From: Ali Makooie <ali@YORKU.CA>
Subject: Re: Login...MANDATORY (win95)

>We have the newest versions of Win95 and Client32, want to know
>how we can make login Mandatory to users, so that people can't
>just skip by the log process and have access to the computer.

You may wish to use WINU program to create your own desktop. This is a
very advance program and traps all WIN95 functions and keys. Fully
password protected. I used a single copy of WINU and I am planning to use
this program in student computer lab. The developer is ready to negotiate
pricing for mass usage.

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

Date: Wed, 18 Feb 1998 02:08:34 -0800
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Freedows OS and Novell

Has anyone connected the new Freedows 98 (the replacement for
Windows 95) to a Novell network, specifically NDS?

	http://www.geocities.com/SiliconValley/7519/

I'm wondering if anyone has run into any compatibility issues with
Client32 running on this OS.

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

Date: Thu, 19 Feb 1998 11:58:32 -0700
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Office 97 on diskless Win95 stations...

>I'm working in a community college trying to figure out how
>to convert our existing diskless Win 3.11 stations into diskless
>Win95 stations remote-booting from NW 3.1.  I've completed the
>remote-booting part (thanx to Joe D's "win95boo.txt"), the problem I'm
>having is how to install Office 97 on these diskless clients.
>
>I've researched over the web and on Microsoft's site,
>I've also looked at the "netwrk8.txt" file on the CD.  I've tried
>to follow properly the instructions from my researched sources but
>I can't quite get it right - keep getting errors when "setup" is
>trying to "update the system".  It would greatly be appreciated if
>someone could give us some guidelines on how to properly install
>Office 97.  Are there some docs we haven't looked at?
----------
	I believe you should think twice before proceeding. MS Office 97
is a monster and loaded with problems.
	My file win95boo.txt is boldly marked as obsolete. Use w95inst7.zip
instead to create a remote booting diskless client Win95 environment. See
netlab1.usu.edu with a web browser for files.
	There is no doc on how to install MS Office 97, even though I have
accomplished the task. It's not simple, by rotten design of the product. Put
a hard disk of any kind on a workstation and think of that as the manager's
machine during installation. From the Office CD-ROM run setup /F (do not use
icons). Setup fails if no local hard disk exists. /F is to use regular
filenames. A great many files will be shown as unavailable to be changed
during installation because they will be locked open by Windows. Yes, this
is part of the insanity of recent MS material. Note names, do copies by hand,
restart installation, repeat and repeat until done. Massive changes to Win95
will be done by installing MS Office 97.
	Things will go a lot faster if you perform an administrative
installation first to the server. Put that in say \msoff97i so following
stages can read from the server rather from the slow CD-ROM. The final
material can go into say \msoff97, and when done deltree \msoff97i. Don't
bother with the "shared network" approach, but instead create what appears
to be a local installation with all needed files held locally (even though
"local" happens to be on the server's volumes).
	Be aware that stray directory progra~1 will be created at the root
of the server's volume. That's yet another blunder by the installation folks.
Move the contents beneath the existing progra~1 and use regedit to fix
references accordingly.
	Forget ClipArt, but try it anyway to get a skeleton version going.
ClipArt is pretty badly broken.
	When installing components do so only one at a time. The installation
script breaks otherwise. You can hand edit the script if you feel brave, and
finally that's what I did to save time.
	As I mentioned on this list six weeks ago (were you reading then?)
this project took me ten solid days of intensive effort and finally things
worked. I have no interest in trying to recreate the steps in detail because
I don't have the notes nor the time, and I would rather not spend even more
time repeating the experience to folks (no good deed...). No, I am not willing
to answer lots of questions on the matter, for the reasons just given.
	Joe D.

---------

Date: Thu, 19 Feb 1998 14:09:15 EST5EDT
From: Michael Peckman <PEC@STAFF.CIRC.GWU.EDU>
Subject: Re: Office 97 on diskless Win95 stations...

>	Forget ClipArt, but try it anyway to get a skeleton version going.
>ClipArt is pretty badly broken.

I just wanted to add that Wizards (Excel if I remember) are just as
screwed up.  These can not be used concurrently by multiple users in
a shared environment.  hello?!?

---------

Date: Thu, 19 Feb 1998 14:48:43 -0700
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Office 97 on diskless Win95 stations...

>##I just wanted to add that Wizards (Excel if I remember) are just as screwed
>##up.  These can not be used concurrently by multiple users in a shared
>##environment.  hello?!?
>
>  Yes they can if you allow RWCEMF rights to the \workdir directory off
>of the main office directory.  Or, you can do what I did which was to copy
>these files to the local hard drive and change all of the registry entries
>referencing this directory to point to the local hard disk.

	No, sorry. Concurrent use is blocked. That is very well known in
the business. It's an aspect of total ignorance of networked usage that
permeates a large amount of MS software. Public posturing and reality are
different.

>  I currently use Seagate WinInstall to install our college's software
>and it works quite well.  I just did a search and replace in the office 97
>reg file and it worked fine.

	We are talking apples and oranges here. Diskless client installation
is a very different animal than installing on diskful-with-Win95 clients.
Take my word for it, if you will.

>  As far as I can tell, the only way to get the complete collection of MS
>clipart is to have the cd mounted in a local cd-rom though.

	Ok, here is a another data point for you. Full ClipArt can be installed
for diskless clients, because I have done so. I did minor rewrites of the
installation script to overcome design blunders. The cutsy paperclip etc,
Office Assistance, installs that way too.

>  Obviously though, the above does NOT apply to diskless workstations.
>All of my clients have hard disks with windows 95 loaded locally, but all
>public-access software is served from our Novell IntranetWare Network.

	That's the apples and oranges item, making discussion about diskful
clients a different topic than what's in this thread. If it's all the same
to the rest of you maybe we can dispense with the situation of installation
to a local hard disk and stick with facts on the diskless situation.
	Joe D.

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

Date: Sat, 28 Feb 1998 22:18:10 -0500
From: Larry Hansford <hansford@erinet.com>
Subject: FAQ on Client 32 For Windows 95

If you do not know which version of Netware Client for Windows 95
you are running, here is the process to determine the version:

The best way to do this is to look at the Client32.NLM that is in the
Novell\Client32 directory on the workstation.

  Client32.nlm 1/26/96 - C3295N.EXE - Original shipping version 2.1
  Client32.nlm 7/1/96 - C3295D.EXE update
  Client32.nlm 8/21/96 - 95ENU_N2.EXE - 2.11 release client.
  Client32.nlm 12/11/96 - 95ENU_N3.EXE - 2.12 release client
  Client32.nlm 2/27/97 - W95IT2A.EXE - Interim release update
  Client32.nlm 6/30/97 - Novell IntranetWare Client for Windows 95, v2.20

As part of the Novell IntranetWare Client for Windows 95 version 2.20 you
can determine the client version by looking in the network control panel
under the Novell IntranetWare Client properties. (2.2.0.0)

NOTE: This option is not present in versions prior to 2.20.

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

Date: Fri, 27 Feb 1998 08:13:29 -0800
From: Donovan Bray <dbray@BASS.CUESTA.CC.CA.US>
Subject: Re: Auto-Close 95 DOS Boxes

>How can I force a "Close on Exit" to occur for all my Windows 95 users
>when I use a DOS-based application from the login script??

Load the command interpreter first, then windows will automatically close
the DOS box.

	#command /c capture l=1 q=queue_name ...etc blah blah blah
instead of
	#capture ....blah blah blah

I also find it best to create a batch file with all the dos commands you
want to run so that all the dos apps only open one dos-box during the
login, but that is certainly optional.

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

Date: Fri, 6 Mar 1998 09:12:53 -0800
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: *Win95 licensing* - What Microsoft says

>I suspect it's okay since the serial numbers from OSR0 and OSR1 also
>work with OSR2, and vice versa, but I'll telephone Microsoft on
>Monday to confirm (the SEARCH button on www.microsoft.com generates
>JavaScript errors and isn't working).

I'm not representing Microsoft, I'm just passing on what they've
told me over the telephone.  I strongly recommend you call them to
confirm this yourself.

I called Microsoft at 1-800-325-1233, and they told me the
following:

OSR2 and OSR2.5 are not patches, and cannot be used to update
existing systems that legally own an older version of Windows 95
(OSR0 or OSR1).  Since they are OEM products, at least a hard drive
or complete system must be ordered with it.

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

Date: Wed, 11 Mar 1998 10:21:43 +0000
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: Re: IP Address Conflicts

>Once again, we're experiencing several IP address conflicts with
>our Windows 95 users.  We've tried the standard winipcfg workaround,
>releasing the address, rebooting, and trying for a new one.  Only
>problem is that this doesn't always work.  We've run across a few
>workstations where the ONLY way to get it to acquire an address is by
>changing the network address through the control panel.  Since we try to
>have a standard for addressing, this isn't the best solution.  Has
>anyone seen this before, and if so how did you get around it?

Here are a few tips which should help:

1: Install MSDUN12 onto the workstations (which has the latest
   vdhcp.386) and then remove dial-up networking, leaving the updated
   drivers.

2:  Use long lease times in your DHCP server to minimise the problem.

---------

Date: Wed, 11 Mar 1998 13:58:49 +0000
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: Re: IP Address Conflicts

>1: Install MSDUN12 onto the workstations (which has the latest
>   vdhcp.386) and then remove dial-up networking, leaving the updated
>   drivers.
>
>2:  Use long lease times in your DHCP server to minimise the problem.

You might try this instead of item 1.   As luck has it, I found
this after I posted the above.

Go to http://www.microsoft.com/windows95/info/ws2.htm for the new
Winsock2 update and install that.  I haven't tried it yet, though.

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

Date: Mon, 16 Mar 1998 23:59:34 +0100
From: "Arthur B." <arthur-b@ZEELANDNET.NL>
Subject: Re: Users cannot change their password

>When users try to change their password, they get a message similar to:
>
>	SETPASS 4.1-470 User NWFIN1/SARAH password could not
	be changed - user access denied
>
>Has anyone experienced this problem before?

Yes. Strange thing was that opening up a DOS-box and typing SETPASS
*without* any parameters worked fine. At the moment that you specified
a servername there was a 'network problem'. It wasn't a problem with
the ACL.

The workaround was removing all parameters from the shortcut of the
SETPASS command. Didn't have time back then to determine the cause of
this feature.

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

