Copyright: Copyright ¸ 1995  Novell, Inc.


"Novell ODINSUP" Removal

Do not remove any instances of "Novell ODINSUP" from the "Network" control panel unless you know which one belongs to which ODI adapter.  There is a one-to-one mapping.  You cannot just remove any of them.  "Novell ODINSUP" is automatically removed when the adapter is removed, but not until after the "Network" control panel is closed.  Also, removing "Novell ODINSUP" removes NetWare Client 32 for Windows 95 if there is only one adapter in use.


Adding TCP/IP Support
To add TCP/IP support

IMPORTANT:  You need access to the Windows 95 CAB files to successfully set up TCP/IP.

1. Click here  [image] to display the "Network" control panel.

2  Click "Add."

3  Click "Protocol."

4  Click "Add."

5  Click "Microsoft."

6  Click "TCP/IP."

7  Click "OK."

8  Configure the TCP/IP protocol as necessary for your network.

9  Click "OK."


Administrator Defaults

By specifying default values for configuration settings in an ADMIN.CFG file, you can simplify the installation of NetWare Client 32 for Windows 95 in some situations.

The ADMIN.CFG file

Admin Defaults

Overwrite = false

Version = 0

Open Beta Note:  This function is not available yet.


Automatic Client Upgrade

Automatic Client Upgrade (ACU) allows a network supervisor to centrally locate the NetWare Client 32 for Windows 95 code on a file server.  At login time, the workstation can be updated with the client code the network supervisor has placed on the server.  This includes the ability to update to NetWare Client 32 for Windows 95 from the NETX, the VLM, or the Microsoft NetWare client.

Open Beta Note:  ACU is not available yet.


Cabling Notes

See the network board manufacturer's documentation for cabling requirements.

Token ring network boards require a cable connection to the MAU before running the client software. Otherwise, the token ring LAN driver will not load.


Changing Installation Options
To change the installation options

1  Click "Installation Options."

2  Set as many of the installation options as you want.

3  Click "OK."

Notes

The more options you set at this time, the fewer interactions are required when installing Windows 95 and NetWare Client 32 for Windows 95 from the server.


Checking MSBATCH.INF

Check the keys shown in the following MSBATCH.INF file with the ones generated by the INF Installer.  If any of the highlighted lines differ, click the highlighted line in the help file, read the note explaining the significance of the statement, and adjust your MSBATCH.INF file if necessary.

Notes

For more information about MSBATCH.INF parameters, see the Microsoft Windows 95 Resource Kit.

Example

[Setup]

Express=1

[Network]

Protocols=NWLINK, NOVELLIPX32, NWIP

Clients=NOVELL32

[MSTCP]

[install]

addreg=NWIP.reg, dosreq.reg

[NWIP.reg]

HKLM,"Network\Novell\System Config\NWIP\NWIP_DOMAIN_NAME","0",,"NWIP.NOV.ABC.COM"

HKLM,"Network\Novell\System Config\NWIP\Preferred DSS","0",,"111.22.33.44"

HKLM,"Network\Novell\System Config\NWIP\Nearest NWIP Server","0",,"111.22.33.44"

HKLM,"Network\Novell\System Config\NWIP\AutoRetries","0",,"3"

HKLM,"Network\Novell\System Config\NWIP\AutoRetry_Secs","0",,"10"

HKLM,"Network\Novell\System Config\NWIP\NSQ_BROADCAST","0",,"on"

HKLM,"Network\Novell\System Config\NWIP\NWIP1_1 Compatibility","0",,"on"

[dosreq.reg]

HKLM,"Network\Novell\System Config\NetWare DOS Requester\First Network Drive","0",,"N"

HKLM,"Network\Novell\System Config\NetWare DOS Requester\Name Context","0",,""

HKLM,"Network\Novell\System Config\NetWare DOS Requester\Preferred Server","0",,"SERVER1"

HKLM,"Network\Novell\System Config\NetWare DOS Requester\Preferred Tree","0",,""


Clients=NOVELL32

INF Installer should have added this line.  Remove any other clients.


Configure NetWare Client 32 for Windows 95
To configure NetWare Client 32 for Windows 95

1. (Conditional) If the "Network" control panel is not displayed, click here  [image] to display it.

2  Click "Novell NetWare Client 32."

3  Click "Properties."

4  Ensure the following properties are set correctly.

a  Preferred Server

For a bindery connection to the network, specify the NetWare server you want to attach to first.

b  Preferred Tree

For an NDS connection to the network, specify the Directory tree that you want to connect to.

c  Name Context

For an NDS connection to the network, specify the position, or context, in the Directory tree where you want to be when you start NetWare Client 32 for Windows 95.  For example, to set your name context to the MNGT organizational unit in the MARKETING organization, type

OU=MNGT.O=MARKETING

5  Click "OK" to save any changes to the properties.

6  Click "OK" to exit the "Network" control panel and save your changes.

7. Remove any CAPTURE statements that are in your login script.

To set up network printing, browse the "Network Neighborhood", double-click the print queue you want to use, and go through the "Add Printer" screens.

8. Click here [image] to start the "System Configuration Editor".  Make sure VIPX.386 is not loaded in your SYSTEM.INI file.


Configuring TCP/IP Support
To configure TCP/IP support for NetWare/IP, SNMP, or the Host Resource MIB

1  Click here [image] to display the "Network" control panel.

2  Click "TCP/IP."

3  Click "Properties."

4  Make any necessary changes.

5  Click "OK."

6  Click "OK."

Notes

  Configure the TCP/IP protocol as necessary for your network.  NetWare/IP requires that DNS be configured either manually or via DHCP.


Configuring for a Real Mode (16 bit) NDIS Driver
To configure for using a real mode (16-bit) NDIS driver

1  Click here [image] to edit your AUTOEXEC.BAT file.

2  Ensure that your AUTOEXEC.BAT file executes the "NET START" command.

3  If NetWare Client 32 for Windows 95 hangs, set the value for the "Close Behind Ticks" parameter to 0.

NOTE:  Setting the value of the "Close Behind Ticks" parameter to 0 decreases performance.  Therefore, only do this if you have a 16-bit NDIS driver and NetWare Client 32 for Windows 95 hangs.


Contents
NetWare Client 32 for Windows 95 Help

Open Beta Notes

Installing

Configuring

Troubleshooting

Tips and Tricks

Using the Network

What's New

To Print Help Topics

Trademarks

Disclaimer


Copy INFs from NetWare Client 32 Directory to Windows 95 Source Directories
Copying .INF Files from NetWare Client 32 Directory to Windows 95 Source Directories

Example

If the directory you created in step 2 is C:\C32TEMP and your server install path is F:\WIN95, use the following commands to copy the .INF files.

COPY  C:\C32TEMP\*.INF	F:\WIN95

COPY  C:\C32TEMP\*.INF	F:\WIN95\INF

COPY  C:\C32TEMP\*.INF	F:\WIN95\SUWIN


Copying NETDEF.INF

Examples

If your CD-ROM drive is accessed as drive D: and your server install path is F:\WIN95, use the following commands to copy the NETDEF.INF file.

COPY  D:\INSTALL\ADMIN\BATCH\NETDEF.INF	F:\WIN95\NETDEF.INF

COPY  D:\INSTALL\ADMIN\BATCH\NETDEF.INF	F:\WIN95\INF\NETDEF.INF

COPY  D:\INSTALL\ADMIN\BATCH\NETDEF.INF	F:\WIN95\SUWIN\NETDEF.INF

If you are installing from diskettes using drive A: and your server install path is F:\WIN95, use the following commands to copy the NETDEF.INF file after inserting the Admin disk in drive A:.

COPY  A:\BATCH\NETDEF.INF	F:\WIN95\NETDEF.INF

COPY  A:\BATCH\NETDEF.INF	F:\WIN95\INF\NETDEF.INF

COPY  A:\BATCH\NETDEF.INF	F:\WIN95\SUWIN\NETDEF.INF

Notes

The following are the key changes made to the NETDEF.INF file for NetWare Client 32 for Windows 95:

[NETWARE] Section

Original:

[NETWARE]

00000000=NETWARE3

00032600=NETWARE3

00040000=NETWARE4

Updated:

[NETWARE]

00000000=NOVELL32

00032600=NOVELL32

00040000=NOVELL32

[TYPICAL], [COMPACT], and [PORTABLE] Sections (only changed statements are shown)

Updated:

NetTrans=NWLINK,NOVELLIPX32

NetClient=NOVELL32

For NetWare/IP, NWIP should also be specified for NetTrans:

NetTrans=NWLINK,NOVELLIPX32,NWIP


Copying the INF Files
Copying the .INF Files

Notes

Copy the .INF files from the INSTALL\ADMIN\BATCH directory of the NetWare Client 32 for Windows 95 CD-ROM or from the BATCH directory of the Admin disk.  Copy them to the directory where you put all the files for NetWare Client 32 for Windows 95.

Always copy the following files:

NWCLIENT.INF

NWTRANS.INF

NWLAYOUT.INF

For NetWare/IP support, copy the following file:

NWIP.INF

For SNMP support, copy the following file:

NWSERV.INF


Creating MSBATCH.INF
To create an MSBATCH.INF file

1  Run BATCH.EXE.

2  (Optional) Fill in the "Setup Information."

3  Remove "Network Options."

4  Change the "Installation Options."

5  Click "Done."

6  Save as MSBATCH.INF in the directory that you specified as the server install path during Server-based Setup  (for example, F:\WIN95).

Notes

BATCH.EXE is in the ADMIN\NETTOOLS\NETSETUP folder of the Windows 95 CD-ROM.

BATCH.EXE can be run under Windows 3.x or Windows 95.

For more information about Batch Setup (BATCH.EXE), see the Microsoft Windows 95 Resource Kit.

You can also create or change the MSBATCH.INF file by hand.  For information on how to do this, see the Microsoft Windows 95 Resource Kit.


Creating a Network Installation Directory

Prerequisites:  These instructions assume that the NetWare Client 32 for Windows 95 self-extracting files have been copied to a single directory and expanded into a structure that can be used to create diskettes.

The installation can be done from either the diskettes or from a network installation directory.  For ease of installation and performance, we recommend that you create an installation directory on the network or on your local drive.

To create a network installation directory

1  Create a directory called INSTALL in the same directory from which the self-extracting files were executed.

2  Copy the contents of each diskette directory to the INSTALL directory using the XCOPY command.  For example:

XCOPY SETUP\*.* INSTALL /S /E

XCOPY DISK2\*.* INSTALL /S /E

XCOPY DISK3\*.* INSTALL /S /E

XCOPY DISK4\*.* INSTALL /S /E

XCOPY ADMIN\*.* INSTALL /S /E

XCOPY LANDRV\*.* INSTALL /S /E

XCOPY UNICODE\*.* INSTALL /S /E

Note:  Several files exist on more than one diskette.  During the XCOPY process, the DOS message "Overwrite <filename> (Yes/No/All)?" is displayed.  Type "Y" to overwrite the specific file listed in the message or type "A" to overwrite any and all duplicate files.

3  To install the client from this INSTALL directory, run SETUP.EXE from a Windows 95 workstation.

Notes

For a network install, always use the INSTALL directory.  The SETUP directory is used for diskette creation.


Customize Notes

After you click "Customize," the "Network" control panel is displayed.  You can use the "Network" control panel to do any of the following that you need to do to customize your workstation.

Configure NetWare Client 32 for Windows 95.

Set up optional features

Change the LAN driver for your network adapter.

Configure for a real mode (16 bit) NDIS driver

When you are finished, click "OK" on the "Network" control panel and restart your computer.


Customizing

Use the "Network" control panel, which should be displayed to your left, to do any of the following:

Configure NetWare Client 32 for Windows 95.

To configure a network component:

1  Click the component name ("Novell NetWare Client 32," for example).

2  Click "Properties."

3  Make any changes.

4  Click "OK."

5  Click "OK" on the "Network" control panel.

6  Restart your computer.

Set up optional features

To add an optional feature:

1  Click "Add."

2  Click "Protocol" (for NetWare/IP) or "Service" (for SNMP, Host Resources MIB, or Network Management Responder).

3  Click "Add."

4  Click "Novell."

5  Click the name of the optional feature (such as "Novell NetWare/IP protocol").

6  Click "OK."

7  Respond to any messages that are displayed.

8  Click "OK" on the "Network" control panel.

9  Restart your computer.

Change the LAN driver for your network adapter.

To change the LAN driver for your network adapter:

1  Click the network adapter that is installed.

2  Click "Remove."

3  (Conditional) If your network adapter is a Plug and Play adapter that Windows 95 detects and installs the software for, click "OK" on the "Network" control panel and restart your computer.

OR

(Conditional) Otherwise, for ISA and MCA network adapters, click "Add," click "Adapter," click "Add," and select the LAN driver that you want.

Notes

You only need to click "OK" on the "Network" control panel and restart your computer once, so you can skip these steps and just do them when you're finished customizing.


Disabling the NetWare Logo Splash Screen

Disabling the NetWare logo splash screen.  If you don't want the NetWare logo to be displayed when you start your workstation, add the following line to your NETWARE.INI file under the [Options] section:

DisableLogo=1

The NETWARE.INI file should be in the Windows folder (typically, C:\WINDOWS).


Disclaimer

Novell, Inc., makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software.

Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of recreating lost data, the cost of any substitute equipment or program, or claims by any party other than you.

Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell.


Documentation Issues

The documentation is not complete.  We're working on comprehensive information about NetWare Client 32 for Windows 95.  Comments and suggestions are welcome.


Express=1

User input is not required or allowed during Setup.


Files: Alphabetical List
Alphabetical List of Files

1252_UNI.001

3C503.COM

3C589.COM

3C5X9.COM

3C5X9.LAN

3C5X9.LDI

3C689.COM

3CTOKEN.COM

ADMIN.CFG

AM2100.COM

APPSNAP.DLL

APPSNAP.HLP

CALWIN16.DLL

CALWIN32.DLL

CEODI.COM

CLIENT32.NLM

CLNWIN16.DLL

CLNWIN32.DLL

CLNWINTH.DLL

CLXWIN16.DLL

CLXWIN32.DLL

CMSM.MSG

CMSM.NLM

CNE1500T.LAN

CNE1500T.MSG

CNE2.LAN

CNE2.MSG

CNE2000.LAN

CNE2000.MSG

CNE2100.LAN

CNE2100.MSG

CNE2_32.LAN

CNE2_32.MSG

CNE3200.LAN

CNE3200.MSG

CNTR2000.LAN

CNTR2000.MSG

DC21040.COM

ETHERTSM.MSG

ETHERTSM.NLM

F70ODI.COM

FDDITSM.MSG

FDDITSM.NLM

HOSTMIB.MSG

HOSTMIB.NLM

HP3AT16P.LAN

HP3AT16P.LDI

HPFEODI.COM

HPISAODI.COM

HPMCAODI.COM

IPX.NLM

LOCWIN16.DLL

LOCWIN32.DLL

LOGIN.DAT

LOGIN.MSG

LOGINW95.EXE

LOGINW95.HLP

LSL.COM

LSLC32.MSG

LSLC32.NLM

MADGEODI.COM

MSBATCH.INF

NAL.EXE

NAL.HLP

NALRES32.DLL

NALW95.EXE

NCPWIN16.DLL

NCPWIN32.DLL

NE1000.COM

NE1000.INF

NE1000.LAN

NE1500T.COM

NE15_21.INF

NE2.COM

NE2.INF

NE2000.COM

NE2000.INF

NE2100.COM

NE2_32.COM

NE2_32.INF

NE3200.COM

NE3200.INF

NESL.COM

NESL.MSG

NETDEF.INF

NETWARE.DRV

NETWIN16.DLL

NETWIN32.DLL

NIOS.VXD

NIOSLIB.DLL

NMR.NLM

NOVELLNP.DLL

NOVELNPR.DLL

NOVPP32.DLL

NTR2000.COM

NTR2000.INF

NWCALLS.DLL

NWCFG95.CNT

NWCFG95.HLP

NWCLIENT.INF

NWGDI.DLL

NWHOSTX.MIB

NWICFG.NLM

NWIP.INF

NWIP95.NLM

NWIPXSPX.DLL

NWLAYOUT.INF

NWLINK2.VXD

NWLOCALE.DLL

NWNET.DLL

NWOVER95.CNT

NWOVER95.HLP

NWPASSWD.DLL

NWPOPUP.EXE

NWPSRV.DLL

NWSERV.INF

NWSETUP.DLL

NWSETUP.INI

NWSHELLX.DLL

NWSIPX32.DLL

NWSIPX32.NLM

NWTIPS95.CNT

NWTIPS95.HLP

NWTRANS.INF

NWTSG95.CNT

NWTSG95.HLP

NWUSE95.CNT

NWUSE95.HLP

OC32T164.LAN

OC32T164.LDI

ODI3COM.INF

ODI3COMT.INF

ODIALLIE.INF

ODIAMD.INF

ODIARC.INF

ODIAST.INF

ODIBOCA.INF

ODICABLE.INF

ODICOGNT.INF

ODICPQ.INF

ODIDCA.INF

ODIDEC.INF

ODIDELL.INF

ODIEXOS.INF

ODIFARA.INF

ODIFLEX.INF

ODIHP.INF

ODIIBMTR.INF

ODIINTEL.INF

ODIKING.INF

ODILNKSY.INF

ODILOAD.VXD

ODIMADGE.INF

ODIMHZ.INF

ODIMICRO.INF

ODIMITRO.INF

ODINCR.INF

ODINSUP.INF

ODINSUP.SYS

ODIOLI.INF

ODIPAGE.DLL

ODIPCN2.INF

ODIPROT.INF

ODIPURE.INF

ODIRACAL.INF

ODISILC.INF

ODISMC.INF

ODISMCTR.INF

ODISMC32.INF

ODISVEC.INF

ODISYS.INF

ODITCC.INF

ODITDKP.INF

ODITOSH.INF

ODITULIP.INF

ODIUB.INF

ODIXIR.INF

ODIZNYX.INF

PC32MLID.LAN

PC32MLID.MSG

PCNTNW.COM

PEDOSODI.COM

PHASERS.WAV

PIDOSODI.COM

PRTWIN16.DLL

PRTWIN95.DLL

README.NAL

README.TXT

ROUTE.COM

RFC1514.MIB

SETUP.CNT

SETUP.EXE

SETUP.HLP

SMC8000.COM

SMC8000.LAN

SMC8000.LDI

SMC80PC.COM

SMC8100.COM

SMC8100.LAN

SMC8100.LDI

SMC8232.COM

SMC8332.COM

SMC9000.COM

SMCPWR.COM

SNMP.MSG

SNMP.NLM

SNMPDLL.DLL

SNMPIPX.EXE

SNMPUDP.EXE

SPX_SKTS.NLM

SROUTE.MSG

SROUTE.NLM

SUPWIN16.DLL

TCCARC.COM

TCE32ESW.COM

TCE32MCW.COM

TCE32PCW.COM

TCNSW.COM

TCTOKSH.COM

TLI_SPX.DLL

TLI_WIN.DLL

TOKENTSM.MSG

TOKENTSM.NLM

TRXNET.COM

UNI_1252.001

UNI_COL.001

UNI_MON.001

VMLID.NLM


Files: By Folder
List of Files by Folder

\Novell\Client32

\Novell\Client32\Install

\Novell\Client32\Nls\language

\Windows

\Windows\Help

\Windows\Inf

\Windows\Nls\language

\Windows\System

Other


Files: By Function
List of Files By Function

NetWare/IP Files

SNMP Files

Host Resources MIB Files

LAN Driver Files

Help Files

Provider Files

Installation Files


Files: LAN Driver
LAN Driver Files

32-bit LAN Drivers

3C5X9.LAN

CNE1500T.LAN

CNE2.LAN

CNE2000.LAN

CNE2100.LAN

CNE2_32.LAN

CNE3200.LAN

CNTR2000.LAN

HP3AT16P.LAN

MADGEODI.LAN

NE1000.LAN

OC32T164.LAN

SMC8000.LAN

SMC8100.LAN

16-bit LAN Drivers

3C503.COM

3C589.COM

3C5X9.COM

3C689.COM

3CTOKEN.COM

AM2100.COM

CEODI.COM

DC21040.COM

F70ODI.COM

HPFEODI.COM

HPISAODI.COM

HPMCAODI.COM

MADGEODI.COM

NE1000.COM

NE1500T.COM

NE2.COM

NE2000.COM

NE2100.COM

NE2_32.COM

NE3200.COM

NTR2000.COM

PCNTNW.COM

PEDOSODI.COM

PIDOSODI.COM

SMC8000.COM

SMC80PC.COM

SMC8100.COM

SMC8232.COM

SMC8332.COM

SMC9000.COM

SMCPWR.COM

TCCARC.COM

TCE32ESW.COM

TCE32MCW.COM

TCE32PCW.COM

TCNSW.COM

TCTOKSH.COM

TRXNET.COM


Files: Other Folders
List of Files in Other Folders

SNMP management station files:

RFC1514.MIB

NWHOSTX.MIB


Files: Overview
NetWare Client 32 for Windows 95 Files

Open Beta Note:  This information is still being compiled.  It is currently incomplete.  It is also subject to change.

Alphabetical list of files

List of files by folder

List of files by CD-ROM location

List of files by function

List of third-party LAN drivers


Files: \Novell\Client32
List of Files in the \Novell\Client32 Folder

CLIENT32.NLM

CMSM.NLM

CNE2000.LAN

CNE3200.LAN

ETHERTSM.NLM

FDDITSM.NLM

IPX.NLM

LGNW9532.DLL

LOGINW95.EXE

LSLC32.NLM

NMR.NLM (if NMR is installed)

NWIP95.NLM (if NetWare/IP is installed)

NWPOPUP.EXE

NWSIPX32.NLM

PC32MLID.LAN

PHASERS.WAV

README.TXT

SETUP.CNT

SETUP.HLP

SPX_SKTS.NLM

SROUTE.NLM

TOKENTSM.NLM

VMLID.NLM


Files: \Novell\Client32\Install
List of Files in the \Novell\Client32\Install Folder

ADMIN.CFG

NET2REG.LOG


Files: \Novell\Client32\Nls\language
List of Files in the \Novell\Client32\Nls\language Folder

LOGIN.DAT

LOGIN.MSG

Notes

The name of this folder varies depending on the language being used.  For English, the name is "\Novell\Client32\Nls\English."


Files: \Windows
List of Files in the \Windows Folder

LSL.COM


Files: \Windows\Help
List of Files in the \Windows\Help Folder

LOGINW95.HLP

NWCFG95.HLP

NWOVER95.HLP

NWTIPS95.HLP

NWTSG95.HLP

NWUSE95.HLP

Note:  Each of these help files might also have files with the following file types associated with them:

CNT

FTS

GID


Files: \Windows\Inf
List of Files in the \Windows\Inf Folder

NE1000.INF

NE15_21.INF

NE2.INF

NE2000.INF

NE2_32.INF

NE3200.INF

NETDEF.INF

NTR2000.INF

NWCLIENT.INF

NWIP.INF

NWLAYOUT.INF

NWSERV.INF

NWTRANS.INF

ODINSUP.INF


Files: \Windows\Nls\language
List of Files in the \Windows\Nls\language Folder

NOVELNPR.DLL

Notes

The name of this folder varies depending on the language being used.  For English, the name is "\Windows\Nls\English."


Files: \Windows\System
List of Files in the  \Windows\System Folder

CALWIN16.DLL

CALWIN32.DLL

CLNWIN16.DLL

CLNWIN32.DLL

CLNWINTH.DLL

CLXWIN16.DLL

CLXWIN32.DLL

LOCWIN16.DLL

LOCWIN32.DLL

NCPWIN16.DLL

NCPWIN32.DLL

NETWARE.DRV

NETWIN16.DLL

NETWIN32.DLL

NIOS.VXD

NIOSLIB.DLL

NOVELLNP.DLL

NOVPP32.DLL

NWCALLS.DLL

NWDRVLGO.BMP

NWGDI.DLL

NWIPXSPX.DLL

NWLINK2.VXD

NWLOCALE.DLL

NWNET.DLL

NWPASSWD.DLL

NWPSRV.DLL

NWSETUP.DLL

NWSHELLX.DLL

NWSIPX32.DLL

ODILOAD.VXD

ODINSUP.SYS

ODIPAGE.DLL

PRTWIN16.DLL

PRTWIN95.DLL

SUPWIN16.DLL

TLI_SPX.DLL

TLI_WIN.DLL


Future Plans

Planned Beta 2 Updates

Automatic Client Upgrade (ACU):  Will allow a network supervisor to centrally locate the NetWare Client 32 for Windows 95 code on a file server.  At login time, the workstation can be updated with the client code the network supervisor has placed on the server.  This includes the ability to update to NetWare Client 32 for Windows 95 from the NETX, the VLM, or the Microsoft NetWare client.

Browser for Graphical Login:  Will allow users to browse the network for a server or tree at login time.

RAS Support:  Will allow remote dial-in to a RAS server using a local modem, ISDN card, or X.25.  Services available to a typical network user are available by using a RAS connection.

System Policies:  Complete management of NetWare Client 32 for Windows 95 using System Policy Editor (POLEDIT) and system policies will be available.  A template containing client properties that can be specified using the NetWare Client 32 property sheets will be made available for use with POLEDIT.

Multiple tree support:  Will allow the ability to authenticate to and browse multiple NetWare Directory Services (NDS) trees and their resources.

Complete Documentation:  Complete documentation for NetWare Client 32 for Windows 95.  It will include complete online help in native Windows 95 format and quick-reference information in hard copy.

Planned for Future Releases

NetWare Client 32 for Windows 95 does not support running a shared copy of Windows 95 off the network.

NetWare Client 32 for Windows 95 does not support Remote Program Load (RPL).

These capabilities are planned for a later release after NetWare Client 32 for Windows 95 v1.0.  If you currently need to run a shared copy of Windows 95 off the network or if you need RPL support, you should use NetWare Client for DOS and MS Windows.

NetWare Client 32 for Windows 95 does not support Personal NetWare.  (The install program comments out any calls to SERVER.EXE or STARTNET.BAT in the AUTOEXEC.BAT file.)

All drive mappings are global.  Private DOS box support is not available.  Private DOS box support will be in a future release.  See also Requester Issues.

No Support Planned

No support is planned for Windows 95's file and print sharing for NetWare Networks (emulated NCP file and print services).  However, NetWare Client 32 for Windows 95 does support file and printer sharing for Microsoft Networks (peer services) using the [Microsoft] Client for Microsoft Networks, which uses the SMB file-sharing protocol.


General Issues

If receipt of a network message gives you a TEXT MODE "NetWare critical error" message and your system appears to be hung, do the following:

1  If you are unable to regain control of the system, reboot.

2  Copy NWPOPUP.EX_ from DISK 2 to the Windows 95 system directory.

3  Press ctrl-alt-del and end the NWPOPUP.EXE task.

4  Delete the old NWPOPUP.EXE from your Windows 95 system directory.

5  Expand the new NWPOPUP.EXE (that is, EXPAND NWPOPUP.EX_ NWPOPUP.EXE).

6  To activate this new version, shutdown and restart your computer.

To run the GroupWise Client for DOS, use the /da command line switch, which disables the DOS task-switching API support.  NetWare Client 32 for Windows 95 does not support task switchers.

NetWare Client 32 for Windows 95 does not support task-switching features of programs.  For example, the task-switching features of the GroupWise Client for DOS and the MS-DOS Shell (DOSSHELL.EXE) are not supported.

Login script data files and Application object icon data files might be held open if accessed by the graphical (GUI) login or the NetWare Application Launcher for Windows 95.  The problem might manifest itself through access denied messages or by changes not being saved.  To get around this, have all users that have accessed these data files from Windows 95 log out.

Winsock for SPX and IPX.  The WINSOCK.DLL file that supports SPX/IPX connectivity is not shipped with this Open Beta of NetWare Client 32 for Windows 95.  If you want to use Winsock for SPX and IPX, copy the WINSOCK.DLL file from the NetWare Client 32 for DOS and Windows 3.1x release.  The WINSOCK.DLL file will be included with NetWare Client 32 for Windows 95 in our next Beta release.

For users of Symantec's The Norton Utilities' NDOS command shell, NetWare Client 32 for Windows 95 is compatible only with NDOS versions distributed with The Norton Utilities v7.00 and later.


Graphical (GUI) Login Issues

There is an advanced screen available for the graphical login utility.  There is a property on the "Login" tab of "Novell NetWare Client 32 Properties" to control whether the advanced or simple login screen is displayed.

If the login script being used contains a #command (such as #CAPTURE), you might have to manually close the associated MS-DOS Prompt window.

To have the MS-DOS Prompt window close automatically, do the following:

1  Click the icon in the upper-left corner of the MS-DOS Prompt window.

2  Click "Properties."

3  Click "Close on exit," which is on the "Program" tab.

The box next to "Close on exit" should now have a checkmark in it.

4  Click "OK."

The fix for this will be in a future update of this Beta product.

Removing old LOGIN.DAT files.  If the graphical login (LOGINW95.EXE) is displaying an illegal instruction error, check for LOGIN.DAT files outside the \Novell\Client32\Nls\English folder.

To search for LOGIN.DAT files, at an MS-DOS Prompt enter:

C:

CD \

DIR LOGIN.DAT /S

Remove all instances of the file except the one in \Novell\Client32\Nls\English.

Note: This only applies to users who have installed an Alpha or Beta 1 release of NetWare Client 32 for Windows 95.

Additional login parameters.  The "Additional login parameters" field on the Login tab is not functional and will be removed in the future.


HOSTMIB.NLM File

This file implements the standard Host Resources MIB as defined by the Internet Engineering Task Force (IETF) and Novell's NetWare Host Resources Extensions MIB.  Its basic purpose is to allow SNMP management software to manage the physical resources of a client workstation.


Installation Complete

To use NetWare Client 32 for Windows 95, click "Reboot."  When your workstation reboots, NetWare Client 32 for Windows 95 starts automatically.

To use Windows 95 before restarting your workstation, click "Return to Windows."  When you're ready to use NetWare Client 32 for Windows 95, shut down Windows 95 and restart your workstation.

To add optional features to your configuration or to change Novell NetWare Client 32 properties, click "Customize."  Use the "Network" control panel to "Add" the protocols or services or to change the "Properties" that you want, then click "OK" and restart your workstation.

To view this help topic, click "Help."  You can view instructions about adding NetWare/IP, SNMP, NMR, or the Host Resources MIB or configuring NetWare Client 32 for Windows 95 by using this help file.


Installation Issues

Upgrading from the VLM client.  If you are upgrading from the VLM NetWare client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 cabinet (CAB) files available when you install NetWare Client 32 for Windows 95.

Upgrading from the NETX client.  If you are upgrading from the NETX NetWare client, edit your CONFIG.SYS file and remove the LASTDRIVE statement or change it to LASTDRIVE=Z.

Upgrading from the Microsoft clients to the NetWare Client 32 for Windows 95.

If Microsoft's Client for Microsoft Networks and Client for NetWare Networks are currently installed on your Windows 95 workstation and you are upgrading to NetWare Client 32 for Windows 95, you might need to configure "Preferred server," "Preferred tree," "Name context," and "First network drive."

To set the above properties:

1  In the "Network" control panel, click "Novell NetWare Client 32."

2  Click "Properties."

3  In the "Login" tab, enter the values you want for "Preferred server," "Preferred tree," "Name context," and "First network drive."

If you were an alpha tester and have NetWare Client 32 for Windows 95 installed on your workstation, remove ODINSUP and your adapter from the "Network" control panel before setting up NetWare Client 32 for Windows 95 to get the latest ODI LAN driver for your network adapter.

When you remove ODINSUP and your adapter from the "Network" control panel, the client is also removed.  All the properties are preserved, however, so you don't have to redo the "Preferred server," "Preferred tree," "Name context," and any other properties you might have set.

File and printer sharing for Microsoft Networks:  If a copy of NetWare Client 32 for Windows 95 that is older than the Open Beta software is installed on your workstation, and "File and printer sharing for Microsoft Networks" is also installed, do the following:

1  Remove "File and printer sharing for Microsoft Networks" from the "Network" control panel.

2  Install NetWare Client 32 for Windows 95.

3  Reinstall "File and printer sharing for Microsoft Networks."

TCP/IP configuration settings.  NetWare Client 32 for Windows 95 does not include its own TCP/IP protocol stack.  Therefore, any existing TCP/IP parameters are not moved from the NET.CFG file to the registry.

Building driver information database.  You might see this message four or five times during installation.  This is normal.  The installation program does not display this message, but has Windows 95 rebuild the driver information database to ensure that the driver index is correct.

"Network" control panel.  It's been observed that a lot of changes in succession on the "Network" control panel without clicking "OK" tends to result in registry corruption.  We recommend that you click "OK" between changes.


Installation Overview

There are four methods of installing NetWare Client 32 for Windows 95.

Setting up a server with the Windows 95 and NetWare Client 32 for Windows 95 files, so that they can be installed at the same time from the server.

Installing interactively at the workstation after Windows 95 has been installed.

Installing using the Custom Setup Option of Windows 95 Setup.

Using the Automatic Client Upgrade.feature.  Open Beta Note:  This feature is not available yet.


Installation Screen

To install NetWare Client 32 for Windows 95, click "Start."  Any existing NetWare clients are removed and NetWare Client 32 for Windows 95 is added.

IMPORTANT:  If you are upgrading from the NetWare DOS Requester (VLM) client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 CAB files.

To quit the installation, click "Cancel."

To see this help topic, click "Help."  There are also many other help topics available about installing and configuring NetWare Client 32 for Windows 95.

To see README information, click "View Readme."


Installing (Contents)
Installing NetWare Client 32 for Windows 95

Overview

Preparing for Installation

Option 1:  Installing Using a Server-Based Windows 95 Install

Option 2:  Installing on a Workstation that Already Has Windows 95 Installed

Option 3:  Installing Using Custom Windows 95 Setup

Automatic Client Upgrade

Installing Additional Protocols and Optional Features

Removing


Installing Interactively
To set up NetWare Client 32 for Windows 95

IMPORTANT:  If you are upgrading from the NetWare DOS Requester (VLM) client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 CAB files.

1  Run the installation program, SETUP.EXE.

2  Click "Yes" or "No" to respond to the "Non-Disclosure Agreement."

3  Click "Start" to install NetWare Client 32 for Windows 95.

4  (Conditional)  If you are prompted to select a network adapter, choose the one that matches your hardware.

5  (Conditional) If you don't need to customize your installation, click "Reboot."

OR

(Conditional) If you want optional features or need to configure your workstation, click "Customize."


Installing Using a Server-based Windows 95 Install
To install NetWare Client 32 for Windows 95 using the Windows 95 Server-based Setup

1  Run Server-based Setup (NETSETUP.EXE).

2  Put all the files for NetWare Client 32 for Windows 95 into a directory.

3  Remove all the .INF files from the directory in step 2.

4  Copy the .INF files from the BATCH directory to the directory in step 2.

5  Create an MSBATCH.INF file.

6  Run the INF Installer (INFINST.EXE) to add NetWare Client 32 for Windows 95 to the MSBATCH.INF file.

7  Check the MSBATCH.INF file.

8  Copy the NETDEF.INF file from the BATCH directory to the Windows 95 source directory on the NetWare server and its INF and SUWIN subdirectories.

9  Run Windows 95 Setup (SETUP.EXE MSBATCH.INF).

Notes

This procedure is ideally suited for sites that are updating multiple workstations with both Windows 95 and NetWare Client 32 for Windows 95.


International Issues

Unicode tables not found:  On some international versions of Windows 95, you might see the following message during startup.

NWDRV-3.00.30: Initialization of the Unicode tables failed

Country id = XXX and code page = YYY

All NetWare Directory Services functions are disabled.

To work around this problem, add a code page override in your WIN.INI file.  Use the [NetWare] section in your WIN.INI file to set the NWCodepage override value.  If the [NetWare] section does not already exist, create it.  You can edit the WIN.INI file using SYSEDIT or NOTEPAD.  After you make this change, restart your system for the change to take effect.

Also, be sure that the iCountry= setting in the [intl] section of the WIN.INI file is correct for your locale.

For example, on a traditional Chinese system in Taiwan, you might need to have the following sections in the WIN.INI file:

[NetWare]

NWCodepage=950

[intl]

iCountry=88

The following are example country code and code page values.

Country		Code
Code	Country	Page
81	Japan	932
82	Korea	949
86	China	936
88	Taiwan	950
If you find this problem in other countries, please let us know by sending Internet E-mail to client32beta@novell.com.

This problem will be corrected in future updates of this Beta product.

Unicode tables for text-mode utilities.  If you have difficulties running NetWare text-mode utilities (such as FILER, PCONSOLE, NETADMIN, and so forth) at a Windows 95 MS-DOS Prompt, copy the Unicode mapping tables to the following directories:

SYS:LOGIN\NLS

SYS:PUBLIC\NLS

SYS:SYSTEM\NLS

For example, for running a traditional Chinese system in Taiwan attached to a Novell NetWare 4.1 server, you could do the following:

MAP  T:=SYS:

CD  C:\WINDOWS\NLS

COPY  *.088  T:\LOGIN\NLS

COPY  *.088  T:\PUBLIC\NLS

COPY  *.088  T:\SYSTEM\NLS

Notes

You must have the appropriate trustee rights in order to copy the files.

NetWare 2 and NetWare 3 servers do not use Unicode files.  Therefore, this procedure is not applicable.

Text-mode utilities might not display correctly.  Text-mode utilities (such as FILER, PCONSOLE, NETADMIN, and so forth) might not display correctly for Korea, China, and Taiwan.  The overlay files that are needed to correct this problem will be provided in the future.

People's Republic of China  The Unicode mapping files for PRC, country code 86, are not available in this Open Beta.  If you are using PRC Windows 95, please send Internet E-mail directly to Novell at client32beta@novell.com for information on receiving these files.

Other International Issues  If you have any other difficulties, please report the problem by sending Internet E-mail to client32beta@novell.com.  Preface your message with "Attention: Novell International Development."


Miscellaneous Notes

We support the Windows 95 built-in implementations of Server Messenger Blocks (SMB), Winsock, Named Pipes, and NetBIOS.

The NetWare for Windows 95 IPX protocol stack works with the WSOCK32.DLL that comes with Windows 95.

If you check "Reconnect at logon" when you map network drives, you can have the same drive mappings each time you log in even without login script processing.

NetWare Client 32 for Windows 95 can coexist with the [Microsoft] Client for Microsoft Networks.


NETWARE.DRV File

The NetWare Device Driver, which is provided for backward compatibility with 16-bit Windows applications that are NetWare aware.


NWHOSTX.MIB File

This Management Information Base (MIB) defines extensions to the Host Resources MIB -- for Novell NetWare servers.

Source location:  ADMIN disk, NMS subdirectory.

Destination location:  SNMP management station.  See the instructions for your SNMP management software for details.

Notes

Must be manually copied to the appropriate destination.


NWSHELLX.DLL File

Provides shell extensions for Windows 95.


NetWare 2.2 Compatibility Issues

There are known issues using Briefcase, Windows Explorer, and Network Neighborhood.  These issues will be resolved in the future.

Basic login and utilities are supported.


NetWare 3.x Compatibility Issues
NetWare 3 Compatibility Issues

For information about long filename support, see Requester Issues.


NetWare Application Manager

The NetWare Application Manager allows users to run applications that were previously configured by a network supervisor, and whose setup information is stored as an Application object in the NetWare Directory tree.

For more information about the NetWare Application Manager, see the README.NAL file in the NAL directory of the ADMIN disk.


Network Board Installation Notes

For information on installing the network board, see the manufacturer's documentation.

NetWare Client 32 for Windows 95 supports both Open Data-Link Interface (ODI) and Network Driver Interface Specification (NDIS) drivers.


No: Non-Disclosure Agreement
No

If you click "No," that's the end.  Ignore all the rest of the instructions.  You can't use NetWare Client 32 for Windows 95.


ODI and NDIS Support Issues

Updating LAN drivers:  If you have newer versions of third-party ODI LAN drivers than those that ship with this open beta of NetWare Client 32 for Windows 95, it is possible to update them by copying the .LAN or .COM file to the NOVELL\CLIENT32 folder for 32-bit .LAN drivers or the NOVELL\NWCLIENT folder for 16-bit .COM drivers.

Third-Party ODI .INF Files:  If you want to use an ODI LAN driver for your network adapter, do the following before running SETUP.EXE:

1  Edit the NWSETUP.INI file.

NWSETUP.INI is in the Install directory of the NetWare Client 32 for Windows 95 file set.  For diskettes, it is on the Setup disk.

2  Uncomment the .INF file for the ODI LAN driver that you want.

The .INF files are listed in the [INF Files] section of the NWSETUP.INI file.

The .INF files for third-party LAN drivers are named ODIxxx.INF (for example, ODI3COMT.INF), where xxx is the manufacturer of the network adapter.

To uncomment a .INF file, delete the semicolon (;) in front of it.

If you want to use NDIS drivers, comment out the corresponding .INF file in the NWSETUP.INI file.

Alpha Third-Party ODI .INF Files:  If you have installed the alpha versions of NetWare Client 32 for Windows 95, you might need to delete the third-party ODI .INF files from the Windows INF directory (typically, C:\WINDOWS\INF).

Procedure

1  Open an MS-DOS Prompt and change to the Windows INF directory.

2  Create a backup directory (for example, INFBKUP).

3  Copy all of the ODI .INF files to the backup directory.

4  Delete the ODI .INF files from the \WINDOWS\INF directory.

5  Restore the ODINSUP.INF file from the INF backup directory.

Example

CD C:\WINDOWS\INF

MD INFBKUP

COPY ODI*.INF INFBKUP

DEL ODI*.INF

COPY INFBKUP\ODINSUP.INF

List of LAN drivers:  A list of ODI LAN drivers that are shipped with NetWare Client 32 for WIndows 95 is included in the SETUP.HLP file.  Additional LAN drivers will be added as they are developed and tested.

Generally, you should not remove "Novell ODINSUP" from the "Network" control panel.

16-bit ODI Driver Limitations

The following issues are apparent only if there are multiple adapters using 16-bit drivers in the machine.  There are no known problems having two adapters using 32-bit drivers or with one adapter using a 32-bit driver and the other using a 16-bit driver.  The problems occur when both adapters are set to use 16-bit drivers at the same time.

 If two or more adapters are set to use 16-bit DOS ODI drivers and later one of the drivers is switched to be a 32-bit ODI driver, the Windows 95 installation process (which is utilized by the driver .INF files) removes the LSL.COM and NESL.COM files from the AUTOEXEC.BAT file.  This leaves the remaining 16-bit DOS ODI driver without LSL.COM and NESL.COM in the AUTOEXEC.BAT file.  The removal occurs because there is no usage count associate with the LSL.COM or NESL.COM files.

To correct this problem, edit the AUTOEXEC.BAT file  and add lines for LSL.COM and NESL.COM.  Add these lines before the 16-bit driver.

If there are two or more adapters of the same type that specify the same 16-bit DOS ODI driver, the Windows 95 installation process adds the driver to the AUTOEXEC.BAT file only once.

To correct this problem, edit the AUTOEXEC.BAT file and copy the driver statement so that each adapter has a driver loaded for it by the AUTOEXEC.BAT file.

If there are two or more adapters of the same type and both are using 16-bit DOS ODI drivers, switching one adapter to use a 32-bit ODI driver or removing the driver altogether removes the one instance of the 16-bit driver from the AUTOEXEC.BAT file.  The adapter left using the 16-bit driver is not in the AUTOEXEC.BAT file.

To correct this problem, edit the AUTOEXEC.BAT file and add the driver statement.

If there are two or more adapters of the same type and both are using 16-bit DOS ODI drivers, changing the first adapter to use the second adapter’s configuration, and then changing the second adapter’s configuration to a nonconflicting configuration, removes the first driver from the NET.CFG file (which used to be the second driver’s old configuration) if the second driver is processed first during the install process.  If the first driver is processed first, then both drivers are removed from the NET.CFG file.

This condition occurs because when updating the NET.CFG file, the process tries to remove an adapter’s old configuration and then add the new configuration.  If the old configuration matches a different driver’s current configuration, the configuration is removed.  There is no easy way to know that the configuration belongs to a different adapter.

Limitations when there is more than one driver available for a network board.

The following problems generally occur when a driver choice for an adapter is between ODI and NDIS, but they also occur if there are two ODI drivers or two NDIS drivers that can be used on the same adapter.  The term "same adapter" refers to adapters that have the same Plug and Play ID.  The adapters might be manufactured by different venders, but if they are compatible, they will have the same Plug and Play ID.

Installing a hardware-detectable adapter, such as an EISA adapter.

The Windows 95 hardware detection routine installs all network software when it detects a new adapter in the system.  An adapter is new if there is no information about it in the registry.  (Either the adapter was in the system but the existing driver was removed, or an adapter was put in the machine and powered on).  When the adapter is detected, the first driver in the list of drivers is installed.  If the desired driver for that adapter is further down in the list, the first driver found is still installed.

Switching back and forth between the 16- and 32-bit ODI drivers.

If the driver for the selected adapter has a Plug and Play ID in an .INF file that appears before the .INF file containing the selected driver in the driver index list, the install and remove sections in the selected driver’s .INF file are not executed by the Windows 95 install process.  Without the install and remove sections executing, the AUTOEXEC.BAT file is not maintained correctly and the driver files are not copied.

If either of the two previous problems manifests itself, rename the .INF file that is not desired, so that the information from the desired .INF is always used.  To find the .INF file to rename, search each .INF file for the one that the system is currently using, which is the .INF file that matches the LAN driver's provider, manufacturer, and device ID.

NetWare server drivers written to the NetWare 3 driver specification cannot be used on a workstation that is running NetWare Client 32 for Windows 95.

Source routing:  The source route NLM program is designed to work with ODI drivers.  NDIS LAN drivers are not supported by the source route NLM program.  NDIS drivers support source routing through the NDIS protocol stack.


Open Beta Notes

Welcome

Creating a Network Installation Directory

Installation Issues

Graphical (GUI) Login Issues

NetWare Application Manager

Requester Issues

Printing Issues

ODI and NDIS Support Issues

NetWare 3 Compatibility Issues

NetWare 2.2 Compatibility Issues

SNMP Issues

General Issues

International Issues

Documentation Issues

Future Plans


Option 3:  Installing Via Custom Windows 95 Setup
To install NetWare Client 32 for Windows 95 using Windows 95 Custom Setup

1  Run Windows 95 Setup.

2  Select "Custom" when the Windows 95 Setup Wizard displays the "Setup Options."

When presented with your "Network Configuration:"

1  (Conditional) If you have a NetWare client installed, remove it.

2  Add NetWare Client 32 for Windows 95.

a  Click "Add."

b  Click "Client."

c  Click "Add."

d  Click "Have Disk."

e  Specify the path for the NetWare Client 32 for Windows 95 files.

f  Click "OK."

3  Configure NetWare Client 32 for Windows 95.

a  Click "Novell NetWare Client 32."

b  Click "Properties."

c  Make sure the information for "Preferred server," "Preferred tree," "Name context," and "First network drive" are correct.

d  Do any other configuration.


PC32MLID.LAN File

The PC32MLID.LAN file is a shim between the 16-bit DOS ODI specification and the 32-bit C-ODI specification.  It acts like a 32-bit LAN driver, but it uses 16-bit LAN drivers to transmit and receive network data.  It must be used if you are using 16-bit DOS ODI LAN drivers with NetWare Client 32 for Windows 95.

The PC32MLID.LAN driver must be loaded after LSL.NLM and before IPX.NLM.


Preparing Your Workstation Hardware

The following checklist can help you prepare your workstation for installing NetWare Client 32 for Windows 95.

Prerequisites

PC with an Intel (or compatible) 80386 or above processor

A hard disk with 2 MB of free storage space

6 MB or more of RAM

A network board installed in your workstation

A cable connection to the network


Preparing Your Workstation Software

The following checklist can help you prepare your workstation software for installing NetWare Client 32 for Windows 95.  If you are installing the client on a new workstation, first prepare your workstation hardware, and then return to this section.

Prerequisites

You must be running Windows 95, final release.

The NetWare Client 32 for Windows 95 CD-ROM or diskettes.

If you are upgrading from the NetWare DOS Requester (VLM) client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 CAB files.

Notes

The following network components are not compatible with NetWare Client 32 for Windows 95::

[Microsoft] Client for NetWare Networks

[Microsoft] File and printer sharing for NetWare Networks

[Microsoft] Service for NetWare Directory Services

Novell NetWare (Workstation Shell 3.x [NETX])

Novell NetWare (Workstation Shell 4.0 and above [VLM])

Novell IPX ODI Protocol

Note:  This is the 16-bit module for the NETX and VLM clients.  The "Novell NetWare 32-bit IPX protocol" is used for NetWare Client 32 for Windows 95.

These network components conflict with NetWare Client 32 for Windows 95.  If any of these network components is installed, the NetWare Client 32 for Windows 95 installation program detects the conflict and removes the conflicting network component.


Preparing for Installation

This section explains what you need to do before installing NetWare Client 32 for Windows 95 on your workstation.  This section assumes that you are familiar with the following hardware and software:

NetWare compatible network boards

LAN drivers (to support your network board)

Preparing Your Workstation Hardware

Preparing Your Workstation Software


Printing Issues

NPRINTER:  Workstations cannot run the NetWare 4 NPRINTER or NetWare 3 RPRINTER terminate-and-stay-resident (TSR) programs under Windows 95.  A 32-bit NPRINTER.EXE will be available in the future.

Windows 95 applications do not use captured printer ports.

A capture redirects the output from an LPT device to a network printer.  Under Windows 95, GUI applications do not send data to an LPT device.  Instead, they send the data directly to a Windows 95 printer device, which points to a network printer.

If you do a capture at an MS-DOS prompt, any writes to LPT1 are directed to the network printer specified in the capture, as long as you are at the MS-DOS prompt.

However, any flags set up under a DOS capture cannot be translated into the GUI world.  There's no way to associate a Windows 95 printer device with an LPT port.

Here's an example of the problem.  You have a printer device under Windows 95 called HP_PRINTER, which is set to print to NETWORK_HP_PRINTER.  The flags for HP_PRINTER are set up such that there is no banner or form feed.  At an MS-DOS prompt, you now do two captures (LPT1 and LPT2) to NETWORK_HP_PRINTER.  The first capture specifies a banner and a form feed.  The second capture specifies a banner and no form feed.  Now you attempt to print a document in the GUI environment to HP_PRINTER.  How can the provider associate one of the captured LPTs with HP_PRINTER?  Which LPT capture information should it associate with HP_PRINTER?

In summary:

A capture has meaning only when printing to an LPT port.

Captures are global.  If you do a capture at an MS-DOS prompt, the capture exists under GUI; if you do a capture in the GUI world, it exists for MS-DOS prompts.  However, the settings that are used when printing from a GUI application to a Windows 95 printer device are not the same as the settings in the capture.

NDS print queues not always displayed.  NDS print queues are displayed in the Network Neighborhood and the Windows Explorer.  To add a printer for an NDS print queue, find the print queue using the Network Neighborhood or the Windows Explorer.  Then, double-click the print queue icon [image] and use the "Add Printer Wizard."

The problem occurs if you go through "My Computer," "Printers," and "Add Printer" to get to the "Add Printer Wizard."  In this case, no NDS print queues are displayed in the "Browse for Printer" window.

The fix for this is available as SHELLUPD.EXE at these Internet sites:

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

ftp://ftp.microsoft.com/peropsys/Win_News/FreeSoftware/shellupd.exe

SHELLUPD.EXE updates the SHELL32.DLL in the Windows System folder.


Protocols=NWLINK, NOVELLIPX32, NWIP

INF Installer should have added this line.  Remove any other protocols.

NWIP is only needed for NetWare/IP.

For NetWare/IP, make sure the MSTCP protocol is not listed because NetWare/IP automatically loads the MSTCP protocol.


Putting Files in a Directory

Notes

This directory can be on the local hard disk, the NetWare server, or any other location that is accessible to the INF installer (INFINST.EXE).

The files must not be compressed.

The files in the INSTALL\ADMIN directory of the NetWare Client 32 for Windows 95 CD-ROM or on the Admin disk should not be copied to the directory at this point.


RFC1514.MIB File

Definitions for the Host Resources Management Information Base (MIB).

Source location:  ADMIN disk, NMS subdirectory.

Destination location:  SNMP management station.  See the instructions for your SNMP management software for details.

Notes

Must be manually copied to the appropriate destination.


Reboot Notes

When your workstation reboots, NetWare Client 32 for Windows 95 starts automatically.


Remove NetWare Client
To remove a NetWare client

1  Click the name of the client.

The name should be one of the following:

Client for NetWare Networks

Novell NetWare (Workstation Shell 3.X (NETX))

Novell NetWare (Workstation Shell 4.0 and above (VLM))

2  Click "Remove."

Note

You do not need to exit the "Network" control panel or restart your computer at this point.


Remove NetWare Client 32 for Windows 95
To remove NetWare Client 32 for Windows 95

1  Click here  [image] to display the "Network" control panel.

2  Click "Novell NetWare Client 32."

3  Click "Remove."

4  Remove any other Novell networking components (such as the "Novell NDIS Support Module" and the "Novell NetWare 32-bit IPX protocol") in the same way.

5  Click "OK."

6  Click "No."


Removing (Contents)
Removing

Removing NetWare Client 32 for Windows 95

Overview

Removing Client Components


Removing INF Files
Removing .INF Files

Notes

Rename or erase all the files with an extension of .INF in the directory where you put all the files for NetWare Client 32 for Windows 95.


Removing Network Options
To remove network options

1  Click "Network Options."

2  Click any protocols, services, clients, or other options that are checked.

3  Click "OK."

Notes

The "IPX/SPX compatible protocol" can be installed with NetWare Client 32 for Windows 95 without causing a conflict.  NetWare Client 32 for Windows 95 does not use this protocol, however.


Requester Issues

Network status messages.  NetWare Client 32 might display a "Network Status" message on networks that are experiencing abnormal delays.  It is recommended that you not cancel this message.  The client is retrying the operation in the background.

If you click "Cancel," there is a possibility that your workstation will hang.  If you wait, the client closes the "Network Status" message when it gets a response from the server.

Global drive mappings.  All drives (including search drives) are viewed globally with the client.  That means that anytime a drive is mapped anywhere in Windows (for example, File Manager, MS-DOS Prompt, or Windows Explorer), the drive is accessible and visible in every other part of Windows.

Locations or directory paths are private to each area.  Whenever a drive is changed to a different directory, the directory change affects only that specific instance of the drive.  For example, if the drive is changed to the PUBLIC directory at an MS-DOS Prompt, no other MS-DOS Prompt or Windows application (such as File Manager) displays this change.

If a drive is mapped to a location on a volume, the following things happen in the case of a nonrooted drive:

The drive is mapped to the volume level on the server.

The drive is then changed to the directory specified.

This means that all areas of Windows see the drive as new, but every location sees the drive mapped to the volume level except the MS-DOS Prompt or Windows application where the drive was originally mapped.

If a drive is mapped using the map root syntax of the MAP utility, the following occurs:

The drive is mapped to the location (volume:directory) specified.

In this case, all locations of Windows see the drive as mapped to the same directory.

Running Out of Server Disk Space:  NetWare Client 32 for Windows 95 behaves differently than previous NetWare clients with respect to running out of server disk space.  The difference is that NetWare Client 32 for Windows 95 caches file write data in memory and then actually writes this data out later.  This makes an application think that its writes completed successfully, but in the case of running out of disk space, the following happens:

1  An application writes file data and receives a success return code.

2  The file data resides in cache until a background process writes the data to the server across the network.

3  The server returns an OUT_OF_DISK_SPACE error code to the client.

4  The client pops up a critical error box with the following message:

"Out of disk space writing file <filename> to server <server name>."

"Try deleting some files before continuing."

"Warning:  You will lose data if you hit 'Cancel'."

5  If the user clicks "Retry" after deleting some files to make room, the file is written to disk.  If the user clicks "Cancel," that file's write data is lost but the application may still indicate that the file was saved successfully, potentially confusing the user.

This behavior can be disabled by turning off the caching of write data.  To do so, change the value of "Cache Writes" to "off."  For more information, see the Cache Writes topic in the NWCFG95.HLP help file.

Note:  When users exceed their volume space limit (as specified in their volume space restrictions), they should delete some files and click "Retry" the same as if the server ran out of disk space.

Long filename support:  To enable long filename support on NetWare 4.1:

1  Copy PM410.NLM and NSWILDFX.NLM from the Patches\Nw410 directory on the Admin diskette to the SYS:\SYSTEM directory on the server.

2  Load the OS/2 name space.

At the server console prompt, enter

LOAD OS2.NAM

3  Load the patches.

At the server console prompt, enter

LOAD PM410

LOAD NSWILDFX

4  Add the OS/2 name space to the server volumes.

At the server console prompt, enter

ADD NAME SPACE OS2 TO VOLUME <volume>

5  Add the load commands for the OS/2 name space to the STARTUP.NCF file and the patches to the AUTOEXEC.NCF file.

To enable long filename support on NetWare 3.11:

1  Copy PATCHMAN.NLM, SHORTAFX.NLM, and OS2OPNFX.NLM from the Patches\Nw311 directory on the Admin diskette to the SYS:\SYSTEM directory on the server.

2  Load the OS/2 name space.

At the server console prompt, enter

LOAD OS2.NAM

3  Load the patches.

At the server console prompt, enter

LOAD PATCHMAN

LOAD SHORTAFX

LOAD OS2OPNFX

4  Add the OS/2 name space to the server volumes.

At the server console prompt, enter

ADD NAME SPACE OS2 TO VOLUME <volume>

5  Add the load commands for the 0S/2 name space to the STARTUP.NCF file and the patches to the AUTOEXEC.NCF file.

Notes

PM410.NLM and PATCHMAN.NLM are the server patch managers.

The OS/2 name space provides long filename support at the server.

You won't be able to delete a long filename using wildcards if the mask is longer than 8.3.  For example, ERASE ThisIsALong*.TXT won't work, but ERASE This*.TXT works (and includes ThisIsALong*.TXT).

Under Windows 95, the Borland C++ make utility version 4.5 does not work correctly when the Borland executable files are located on a network search drive.

For example:

map ins s1:=server/sys:tools/bc45/bin

The make utility is building an invalid path for the other Borland utilities called in the makefile.  The workaround is to map the search drive as a root, similar to the following example:

map ins r s1:=server/sys:tools/bc45/bin

After Windows 95 is loaded, loading and unloading NLM programs is not supported.


Restart Your Computer
To restart your computer

1  Remove any diskettes from the diskette drive (if you haven't already).

2. Click "Yes" on the "System Settings Change" window.

Notes

The "System Settings Change" window asks you if you want to restart your computer now.  Occassionally, this pop-up might be partially or totally hidden.  If you don't see it, minimize or close windows until you do.

If the "System Settings Change" window is not displayed, restart your computer by doing the following:

1  Click "Start" on the taskbar.

2. Click "Shut Down."

3. Click "Restart the computer?"

4. Click "Yes."

The following error might be displayed when trying to map a search drive during login.

Insufficient memory is available to add the variable to the path environment in the mapping: [INS S16: SERVER\VOLUME\PATH

This is a known problem, and it is being addressed.


Running NETSETUP.EXE
To set up Windows 95 source files on a NetWare server

1  Run NETSETUP.EXE under Windows 95.

2  Set the server install path to the directory on the NetWare server where you want the Windows 95 source files to be--F:\WIN95, for example.

3  Install the Windows 95 source files to the server install path.

a  Select "Local hard drive" as the location of the shared files.

b  Enter the path that has the Windows 95 cabinet files (*.CAB) as the "Path to install from"--F:\WIN95CAB, for example.

c  Respond to the "Create Default" prompt.  Choose either option.

d  Follow the instructions for responding to any other prompts that are displayed.

Notes

NETSETUP.EXE is in the ADMIN\NETTOOLS\NETSETUP folder of the Windows 95 CD-ROM.

Server-based Setup (NETSETUP.EXE) must be run under Windows 95.  It cannot be run successfully under any other workstation operating system.

Server-based Setup (NETSETUP.EXE) extracts the Windows 95 source files from the cabinet (*.CAB) files in the source directory ("Path to install from") and places the source files into the destination directory ("Path to install to").

Running Server-based Setup might take several minutes.

For more information about Server-based Setup (NETSETUP.EXE), see the Microsoft Windows 95 Resource Kit.


Running Windows 95 Setup
To install Windows 95 and NetWare Client 32 for Windows 95

Run SETUP.EXE with MSBATCH.INF as the first parameter.

For example:  SETUP F:\WIN95\MSBATCH.INF

Notes

Specify the complete path of the MSBATCH.INF file.

Use the SETUP.EXE program that ships with Windows 95.

For more information about Windows 95 Setup (SETUP.EXE), see the Microsoft Windows 95 Resource Kit.


Running the INF Installer
To create a custom script for installing NetWare Client 32 for Windows 95 with Windows 95

1  Run the INF Installer (INFINST.EXE).

2  Set the path, specifying the directory on the server where the Windows 95 files are located (for example, F:\WIN95).

3  Select the NWCLIENT.INF file as the INF to install into the server installation of Windows 95

4  Respond to any messages that are displayed as the INF Installer runs.

Notes

INFINST.EXE is in the ADMIN\NETTOOLS\NETSETUP folder of the Windows 95 CD-ROM.

The NWCLIENT.INF file should be in the directory where you put all the files for NetWare Client 32 for Windows 95.  You should have copied it there from the INSTALL\ADMIN\BATCH directory on the NetWare Client 32 for Windows 95 CD-ROM or from the BATCH directory on the Admin disk.

The INF Installer installs all the .INF files that are in the same directory as the .INF file you specify.  Only the .INF files that you want installed should be in that directory.

Do not keep the existing NETWARE.DRV file even if it is newer than the NETWARE.DRV file that is shipped with NetWare Client 32 for Windows 95.  Click "NO" in response to the "Version Conflict" message

The INF Installer (INFINST.EXE) must be run under Windows 95.  It cannot be run successfully under any other workstation operating system.

If the INF Installer cannot find a file, specify the path where you think the file should be.


SNMP Issues

Currently, printers, modems, and tape drives are not shown in the Host Resources MIB Device Table.


Selecting a Network Adapter
To select a network adapter

1  Click "Novell."

2  Click the 16- or 32-bit ODI driver that matches your network board.

For example, click "NE2000 Compatible" if you have an NE2000-compatible network board.

3  Click "OK."

Notes

The "Novell IPX Monolithic Driver" is not supported.

There should be a matching "Novell ODINSUP" component for each ODI LAN driver.  Normally, you do not need to select "Novell ODINSUP."  It is installed automatically.  It is only needed if you install the Client for Microsoft Networks.

Generally, you should not remove "Novell ODINSUP" from the "Network" control panel.


Setting Up NMR
To set up NMR

IMPORTANT:  You need access to the Windows 95 CAB files and the NetWare Client 32 for Windows 95 files to successfully set up the Network Management Responder (NMR).

1. Click here  [image] to display the "Network" control panel.

2  Click "Add."

3  Click "Service."

4  Click "Add."

5  Click "Novell."

6  Click "NetWare Network Mangement Responder for Novell Client 32."

7  Click "OK."

Notes

NMR is an optional feature of NetWare Client 32 for Windows 95.


Setting Up NetWare/IP
To set up NetWare/IP

IMPORTANT:  You need access to the Windows 95 CAB files and the NetWare Client 32 for Windows 95 files to successfully set up NetWare/IP.

1. Click here  [image] to display the "Network" control panel.

2  Click "Add."

3  Click "Protocol."

4  Click "Add."

5  Click "Novell."

6  Click "Novell NetWare/IP protocol."

7  Click "OK."

8  Configure NetWare/IP.

9  (Conditional) If TCP/IP isn't already configured, configure it.

Notes

NetWare/IP requires that the TCP/IP protocol stack be Transport Driver Interface (TDI)-compliant.


Setting Up Optional Features
To see installation instructions for the following optional features, click the name of the feature.

Host Resources MIB

 NetWare/IP

NMR

SNMP


Setting Up SNMP
To set up SNMP

IMPORTANT:  You need access to the Windows 95 CAB files and the NetWare Client 32 for Windows 95 files to successfully set up SNMP.

1. Click here  [image] to display the "Network" control panel.

2  Click "Add."

3  Click "Service."

4  Click "Add."

5  Click "Novell."

6  Click "Novell SNMP Agent."

7  Click "OK."

8  (Optional) Configure SNMP.

9  (Conditional) If TCP/IP isn't already installed, add it.


Setting Up the Host Resources MIB
To set up the Host Resources MIB

IMPORTANT:  You need access to the NetWare Client 32 for Windows 95 files to successfully set up the Host Resources MIB.

1. Click here  [image] to display the "Network" control panel.

2  Click "Add."

3  Click "Service."

4  Click "Add."

5  Click "Novell."

6  Click "Host Resources MIB for Novell Client 32."

7  Click "OK."

8  (Optional) Configure the Host Resources MIB.

9  (Conditional) If you haven’t already installed TCP/IP, install it.

Notes

There are two MIB files that need to be copied to the network management station:

NWHOSTX.MIB

HOSTMIB.MIB

The Host Resources MIB is an optional feature of NetWare Client 32 for Windows 95.

The "Host Resources MIB for Novell Client 32" is only compatible with the "Novell SNMP Agent"  It is not compatible with any other SNMP agent


Smart Defaults

During the installation of NetWare Client 32 for Windows 95, the following settings are checked and used if applicable.

If Microsoft's Client for NetWare Networks is installed, any values that have been specified for settings that are applicable to NetWare Client 32 for Windows 95 are preserved.

If there is a NET.CFG file, all applicable NET.CFG entries are preserved by moving them to the registry.  Some parameters are not used or needed for NetWare Client 32 for Windows 95, so they are not moved to the registry.  In other words, a subset of all NET.CFG parameters are moved to the registry.

NetWare Client 32 for WIndows 95 does not include its own TCP/IP protocol stack.  Therefore, any existing TCP/IP parameters are not moved from the NET.CFG file to the registry.


Source Folder Notes

If you click "Browse" on the "Install From Disk" pop-up window, the "Open" pop-up window displays .INF filenames as well as folders.  The .INF file for NetWare Client 32 for Windows 95 is NWCLIENT.INF.  Select the folder that has the NWCLIENT.INF file using the "Open" pop-up and click "OK."  The path of the folder that contains the NWCLIENT.INF file is displayed on the "Install From Disk" pop-up.  Do not add NWCLIENT.INF to the path.  Just specify the path.


Start Installation Notes

Any existing NetWare client is removed.  Specifically, the following NetWare clients are removed if found:

Novell NetWare (Workstation Shell 3.X (NETX))

Novell NetWare (Workstation Shell 4.0 and above (VLM))

Novell NetWare Client 32

[Microsoft] Client for NetWare Networks

[Microsoft] Service for NetWare Directory Services

NetWare Client 32 for Windows 95 is installed.

The NetWare Client 32 for Windows 95 files are copied to your hard disk.

Insert the NetWare Client 32 for Windows 95 diskettes as you are prompted for them.

Specify the path for the Windows 95 CAB files or for the NetWare Client 32 for Windows 95 diskettes as necessary.

The folder for NetWare Client 32 for Windows 95 is \Novell\Client32 on your workstation's Windows drive.  Some of the NetWare Client 32 for Windows 95 files are copied to this folder.  Other files are copied to the appropriate Windows 95 folder, such as the \Windows\System, \Windows\Inf, and \Windows\Help folders.

The system registry is updated with the information needed to start NetWare Client 32 for Windows 95 automatically each time Windows 95 starts.

Generally, the STARTNET.BAT, NET.CFG, and AUTOEXEC.BAT files are not created, modified, or used by NetWare Client 32 for Windows 95.  If you are using 16-bit ODI LAN drivers, the AUTOEXEC.BAT and NET.CFG files are still used but only by the 16-bit ODI LAN drivers.

Install checks for existing settings in the system registry and the NET.CFG file.  Any applicable settings found are moved to the registry.  For details, see Smart Defaults.

The installation program (SETUP.EXE) does not show up on the task bar.  You can use the Alt+Tab key combination, however, to quickly return to the installation program.  The Windows logo is used as its icon.


Third-Party LAN Drivers

The following third-party LAN drivers are included in this Open Beta.

3C5X9.LAN

HP3AT16P.LAN

MADGEODI.LAN

SMC8000.LAN

SMC8100.LAN

OC32T164.LAN


To Change Your LAN Driver
To change the LAN driver for your network adapter

1  (Conditional) If you have not already run the install program (SETUP.EXE), run it.

2. (Conditional) If the "Network" control panel is not displayed, click here  [image] to display it.

3  Click the network adapter that is installed.

4  Click "Remove."

5  (Conditional) If your network adapter is a Plug and Play adapter that Windows 95 detects and installs the software for, click "OK" on the "Network" control panel and restart your computer.

OR

(Conditional) Otherwise, for ISA and MCA network adapters, click "Add," click "Adapter," click "Add," and select the LAN driver that you want.

Notes

After installing NetWare Client 32 for Windows 95, when Windows 95 detects a Plug and Play adapter, it automatically installs an ODI LAN driver for the network adapter.

For Plug and Play adapters that Windows 95 detects and installs the software for, if you add a network adapter using the "Network" control panel, you might get two LAN drivers installed.  Therefore, you should let Windows 95 detect the network adapter and install the software for it, rather than doing it manually.

The new LAN driver is not used until after you restart your computer.

If a LAN driver for your network adapter already exists when you install NetWare Client 32 for Windows 95, that LAN driver is used unless you change it.


To Print Help
To print help topics

1  Click "Help Topics."

2  (Conditional) If the "Contents" tab isn't already displayed, click "Contents."

3  Click the book that you want to print.

4  Click "Print."

5  Make sure the printer information is correct.

6  Click "OK."

Open Beta Note

For example, in step 3, click "Open Beta Notes" to print the information in it.


To Remove ODINSUP
To remove ODINSUP and your adapter

1. Click here  [image] to display the "Network" control panel.

2  Click "Novell ODINSUP."

3  Click "Remove."

4  Click on the name of your network adapter (for example, "NE2000 Compatible").

5  Click "Remove."

6  Click "OK."

7  (Conditional)  If the NetWare Client 32 for Windows 95 files or the Windows 95 CAB files are on a network drive, click "No."  Do not restart your computer, so you can access these files that are needed for installing NetWare Client 32 for Windows 95.

OR

(Conditional)  Otherwise, click "Yes" to restart your computer.


To run SETUP.EXE

1  (Conditional) If you are installing from diskette, insert the Setup disk.

OR

(Conditional) If you are installing from CD-ROM, insert the NetWare Client 32 for Windows 95 CD-ROM.

2  (Conditional) If you are installing from a diskette in drive A:, click here [image] to run the installation program (SETUP.EXE).

OR

(Conditional) If you are not installing from a diskette in drive A:, run the SETUP.EXE program from the folder that has the NetWare Client 32 for Windows 95 files.


Trademarks

Copyright © 1995, Novell, Inc.  All rights reserved.

Novell Trademarks

Novell, NetWare, DR DOS, and LANalyzer are registered trademarks of Novell, Inc. in the United States and other countries.

GroupWise, Internetwork Packet Exchange and IPX, IPX/SPX, NetWare 3, NetWare 4, NetWare Client, NetWare Core Protocol and NCP, NetWare Directory Services and NDS, NetWare DOS Requester, NetWare Loadable Module and NLM, NetWare Management System, NetWare Requester, NetWare/IP, NMS, Open Data-Link Interface and ODI, Packet Burst, Personal NetWare, Sequential Packet Exchange and SPX, and Virtual Loadable Module and VLM are trademarks of Novell, Inc.

Novell Authorized Reseller is a service mark of Novell, Inc.

Third-Party Trademarks

AST is a registered trademark of AST Research, Inc.  Borland is a registered trademark of Borland International, Inc.  Compaq is a registered trademark of Compaq Computer Corporation.  CompuServe is a registered trademark of CompuServe Incorporated.  HP is a registered trademark of Hewlett-Packard Company.  IBM and OS/2 are registered trademarks of International Business Machines Corporation.  Intel is a registered trademark of Intel Corporation.  Microsoft, MS, MS-DOS, and Windows are registered trademarks of Microsoft Corporation.  Symantec and The Norton Utilities are registered trademarks of Symantec Corporation.  Unicode is a registered trademark of Transoft Ltd.


Unicode Files

All objects and their attributes in the NetWare 4 Directory database are stored in their Unicode (16-bit) representation.  However,clients use 256-character code pages (using 8-bit character codes).  The Unicode files are a set of Unicode translation tables needed to run NetWare utilities and manage the Directory database.

Notes

The appropriate Unicode files need to be in the Windows NLS folder (typically, C:\WINDOWS\NLS) or the Novell NetWare Client 32 NLS folder (typically, C:\NOVELL\CLIENT32\NLS).

The three-character extension for the Unicode files matches the DOS country code.

The Unicode files include the Windows code page file, the Windows code page to Unicode file, the Unicode monocasing file, and the Unicode collating file for your locale.

For example, the following Unicode files are for Germany:

1252_UNI.049 is used to translate code page 1252 to Unicode

UNI_1252.049 is used to translate Unicode to code page 1252

UNI_MON.049 is the monocasing file, which handles the proper alphabetization of upper- and lower-case letters

UNI_COL.049 is the collating file, which handles collation and sorted lists

For different code pages and locales, you need Unicode tables with corresponding code page numbers and country codes.


Welcome

Welcome to the NetWare Client 32 for Windows 95 open beta.  We are excited about this product and appreciate your support in testing this beta software.

This help file contains information about NetWare Client 32 for Windows 95, which is currently beta-level software.  For information on how to print the Open Beta Notes section, see To Print Help.

Support

Open Beta:  While Novell is supporting beta customers already enrolled in the NetWare Client 32 Beta program, Novell will not provide technical support for new Open Beta customers.  However, customers may submit enhancement requests to ENHCLIENT@NOVELL.COM and other feedback to CLIENT32BETA@NOVELL.COM during the Open Beta phase of development.  Answers to FAQs will be posted to CompuServe and the WWW.

Final Release:  Technical support for the final release of NetWare Client 32 for Windows 95 will be the same as for all other NetWare products. Novell and its partners will provide full technical support, including technical assistance, enhancements and fixes.


[MSTCP]

The properties (such as IPAddress) for the Microsoft TCP/IP protocol are specified in the [MSTCP] section.  This protocol (and hence this section) is needed for the NetWare/IP and SNMP features of NetWare Client 32 for Windows 95.


[install]

The rest of this example shows how to add settings to the system registry.