> I'm a Resource Sharing user (that doesn't work with WIN95) and need
> some better (or worse) alternative? We'd like to try it out.
>
resource sharing a.02.00 works with win95.
we can access shares from win95.
from the
HP Resource Sharing A.02.00 Software Update Notice:
...
The Resource Sharing server previously used a communication method
developed by "Hewlett-Packard". It now uses the industry standard
network communication method for name registration. The NetBIOS name
registration service uses the TCP/IP protocol to provide a mechanism
for a server to register its existence on the network and for a client
to find potential servers.
...
attached i send the complete
HP Resource Sharing A.02.00 Software Update Notice.
wolfgang kinscher
.......................................................................
Item Subject: suna0200.txt
HP Resource Sharing A.02.00
Software Update Notice
Product Update Overview
This document describes the HP Resource Sharing A.02.00 release for
MPE/iX.
Client/Server Networking Changes
The primary enhancement to HP Resource Sharing A.02.00 is a
modification to the server's network communication method.
The Resource Sharing server previously used a communication method
developed by "Hewlett-Packard". It now uses the industry standard
network communication method for name registration. The NetBIOS name
registration service uses the TCP/IP protocol to provide a mechanism
for a server to register its existence on the network and for a client
to find potential servers.
Versions
HP 3000
Use Resource Sharing version A.02.00 with MPE/iX version 4.0, Power
Patch level B.40.07 or later.
To check the version, on the HP 3000 type: PRINT PATCHAUD.PUB.SYS
The Power Patch version is displayed under the PPT TAPE heading.
PC Client
The A.02.00 version of Resource Sharing works with your current
version of PC client software. However, it is highly recommended that
you upgrade your PC client software to a version that uses the
industry standard networking communication method.
The recommended version is Microsoft's LAN Manager client software,
version 2.2 with the 2.2b patch.
To check the version on the PC, at the DOS prompt type:
NET VERSION
This document assumes you have version 2.2b installed.
Windows for WorkGroups
Windows for WorkGroups, version 3.11, does not include the required
TCP/IP protocol. A patch is available from Microsoft.
Product Update Specifics
This section describes the modifications to Resource Sharing.
To install the A.02.00 version of Resource Sharing:
* Follow the procedures for software installation in the
"HP 3000 MPE/iX Installation, Update, and Add-On Manual".
Note: Be sure to stream JCONFJOB.NET.SYS after installation of
Resource Sharing.
Do not start the network until you have verified the network
configuration information. This information is in the Resource
Sharing and Network Configuration topic below.
* Refer to the instructions for installing Resource Sharing in Chapter
1 of the "HP Resource Sharing for MPE/iX" manual.
Note: Be sure to stream JPDINSTL.PPC.SYS.
Network Information
Some network configuration changes are required. If you need
additional information on network configuration, refer to:
* "HP 3000/iX Network Planning and Configuration Guide"
* "Microsoft LAN Manager User's Guide for MS DOS"
Note: Do not start the network services until you have verified the
information in the following section.
Resource Sharing and Network Configuration
Some Resource Sharing and network configuration changes may be
required. After installing Resource Sharing, check the following
items before starting the network:
* PDSERVER
To use the NetBIOS name service, Resource Sharing requires at least
one reserved PDSERVER. PDSERVER is Resource Sharing's Print/Disk
Server. One default reserved PDSERVER is created during Resource
Sharing's initialization.
Please note that you have the option of specifying the number of
reserved PDSERVERs when you start your network. Be sure to check that
you are not starting your network with zero PDSERVERs, as this will
override PDSERVER's initialization.
If you use the following statement when starting your network, be sure
n (the number of reserved PDSERVERS) is at least 1 for correct
operation of Resource Sharing:
NSCONTROL SERVER=PDSERVER,n
* LAN Network Interface Name
The RSCONF.PPC.SYS file is a new Resource Sharing configuration file.
It contains this setting for the LAN network interface name (niname):
LAN Network Interface = LAN1
If you are using a name other than LAN1, you must modify the
RSCONF.PPC.SYS file to use that name.
To check your LAN network interface name, on the HP 3000 type the
following command:
NETCONTROL STATUS
Use an editor to make the necessary modifications to RSCONF.PPC.SYS.
* Ethernet Flag
To use the NetBIOS name service, the Enable Ethernet Flag must be set
to Y.
Use the network configuration utility, NMMGR.PUB.SYS, to set the
ethernet flag. The NMCONFIG.PUB.SYS path is @NETXPORT.NI.niname.
* Subnet Mask
It is recommended that the PC client subnet mask match the server
subnet mask. If you do not have subnet masks configured, the default
values are used. Note that the subnet mask default values are
determined by the IP Address class that you use.
If the subnet mask on the server is the same as the PC client subnet
mask, no additional changes are needed.
For PC clients, check your subnet mask by entering the following
command at the DOS prompt:
TYPE PROTOCOL.INI
For the HP 3000 server, type:
NETCONTROL STATUS; NET=niname
If the subnet mask on the client PC does not match the subnet mask on
the server, you can do the following:
On the PC
You can use the ADDNAME command on your PC to make the connection.
This command lets TCP/IP users access the resources of a LAN Manager
server on a different network.
To use the ADDNAME command, at the DOS prompt type:
ADDNAME servername ipaddress
To save the information, type the command again with the SAVE option:
ADDNAME servername ipaddress /SAVE
On the HP 3000 server
Run the NMMGR.PUB.SYS utility to modify the subnet mask after the
ethernet flag has been set. The path is
@NETXPORT.NI.niname.PROTOCOL.IP.
* Neighbor Gateways
A neighbor, or default, gateway should be configured if you have
clients on different networks who are connected, but who are separated
by gateway routers.
To add or modify neighbor gateways, you can use the NMMGR
NMCONFIG.PUB.SYS path @NETXPORT.NI.niname.
Starting the Network
To start the network, type:
:NETCONTROL START;NET=LOOP
:NETCONTROL START;NET= niname
:NSCONTROL START
New Diagnostic Command
A new command has been added to Resource Sharing's diagnostic program
PPCDIAGC.PPC.SYS. The command gives you status information for
Resource Sharing's NBMON.PPC.SYS monitor process. This monitor
process resolves NetBIOS name service requests.
Run PPCDIAGC.PPC.SYS and enter the following command:
SHOWNBSTATUS
If the NBMON process is running, SHOWNBSTATUS will display the
following message: NBMON.PPC.SYS has been started.
If the NBMON process is not running, the following message will be
displayed:
NBMON.PPC.SYS has not been started.
Documentation
The "HP NewWave Office Resource Sharing for MPE XL" manual has been
reprinted with a new cover, title, and part number. It is now titled
"HP Resource Sharing for MPE/iX".
This addendum, "HP Resource Sharing A.02.00 Software Update Notice",
has been added to the product documentation that you receive.
Part Numbers
Customer
Order Edition
Status Title Number Date
-------- ----------------------------------------------- ----------- -------
Obsolete "HP NewWave Office Resource Sharing for MPE XL" 32597-90082 E0391
Current "HP Resource Sharing for MPE/iX" B1718-90002 E1294
Current "HP Resource Sharing A.02.00 Software
Update Notice" B1718-90004 E1294
How to Get Documentation
Ordering The manuals with the E1294 edition dates can be ordered by
calling HP Parts Direct Ordering "(1-800-227-8164)." "HP Parts" Direct
Ordering has a convenient, electronic method for finding the prices
and for ordering manuals. If you need to talk to an ordering
representative, the electronic message directs you to press a number
so an HP representative can help you.
If you have a customer account number, please have it ready when you
order. If you do not have a customer account number, you can still
place your order using this 800 number.
HP FIRST
Additional information can be obtained from HP FIRST, Hewlett-
Packard's Fax Information Retrieval System Technology. You can dial
in using a touch-tone phone and request documents using a 5-digit
identification number. The documents you select are automatically
faxed to the caller.
To use the HP FIRST system, dial 1-800-333-1917. Document ID # 32412
provides an overview of the available information for Resource
Sharing/iX.
Clarification of Previous Documentation
If you have the previous documentation, "HP NewWave Office Resource
Sharing for MPE XL" , the following terminology or information is no
longer applicable to the A.02.00 release.
* HP NewWave Office. This term was previously used to describe
Hewlett-Packard's integrated client/server office solutions. Although
Hewlett-Packard's client/server solutions are no longer marketed under
this product name, Resource Sharing continues to be a viable solution
for giving PC users access to the "HP 3000" and its peripherals.
HP NewWave Office should not be confused with HP NewWave Desktop. HP
NewWave Desktop is a PC application that provides an easy way to
organize your PC files and applications. It uses an object-oriented
window interface to integrate PC applications and manage information.
* HP OfficeShare. This is Hewlett-Packard's PC client networking
software that was previously used with Resource Sharing. Because the
A.02.00 version of Resource Sharing uses the industry standard
networking on the server side, the PC client software should be
updated to use industry standard networking software. Microsoft's LAN
Manager client software provides the networking functionality
previously supplied by HP OfficeShare.
* PC Applications Tested. When applications were first used in a
networking environment, many of them required special configurations
to make them work. Chapter 4 includes a list of PC Applications that
were originally tested with Resource Sharing. This chapter can be
ignored, since the current versions of most applications are network
compatible and do not require special configurations.
|
