All three types of shared installations can be used on computers that run real-mode network clients such as the Novell-supplied NETX or VLM workstation shells.
When a shared installation is created for a real-mode network, the system startup does not include a transition to 32-bit networking. After the initial connection to the network server, the networking software continues to run in real mode. This means that many performance and feature enhancements for Windows 95 are not available, but it also ensures that you can create shared installations on networks where 32-bit, protected-mode networking solutions are not yet available.
As for local installation of Windows 95, you should make sure that the real-mode networking software is installed and running correctly when you start Windows 95 Setup. Then run Windows 95 Setup, specifying the machine directory and other information required to create a shared installation.
The configuration settings created for shared installations using real-mode network clients does not include snapshot or net commands. Other configuration issues are described in the following notes.
Hard-disk computers with real-mode networking.
For computers that start from the hard disk, the configuration and system startup process are similar to that for computers that use protected-mode clients, except there is no transition to protected mode.
Floppy-disk computers with real-mode networking.
For computers that start from the floppy disk, Setup first asks for the old boot disk for the network, and then copies the information from the root directory on this disk to a temporary directory. Then Setup copies the required Windows 95 components to that directory. Finally, Setup copies the directory contents to the new startup disk for Windows 95. The startup disk still contains the original real-mode network software. This configuration uses setmdir (in the same way as configurations for protected-mode networking) in AUTOEXEC.BAT to find the correct machine directory, but the path is specified on the command line rather than in a MACHINES.INI file.
Remote-boot computers with real-mode networking.
This configuration uses setmdir (in the same way as configurations for protected-mode networking) in AUTOEXEC.BAT to find the correct machine directory, but the path is specified on the command line rather than in a MACHINES.INI file.
To prepare for running a remote-boot workstation using a NETX or VLM client with Windows 95, you must complete the following additional tasks: