Docsity
Docsity

Prepare-se para as provas
Prepare-se para as provas

Estude fácil! Tem muito documento disponível na Docsity


Ganhe pontos para baixar
Ganhe pontos para baixar

Ganhe pontos ajudando outros esrudantes ou compre um plano Premium


Guias e Dicas
Guias e Dicas


Configuração de Serviço Boot Remoto para Windows 95, Notas de estudo de Informática

Este documento mostra como configurar o serviço boot remoto para um cliente windows 95. Ele abrange as etapas de instalação do serviço remoteboot no servidor nt, configuração do cliente windows 95 e adição de um perfil de boot no servidor remoteboot manager. Além disso, ele fornece informações sobre a instalação do driver ndis3 e configuração do diretório compartilhado.

Tipologia: Notas de estudo

Antes de 2010

Compartilhado em 18/03/2008

thiago-germano-7
thiago-germano-7 🇧🇷

45 documentos

1 / 10

Toggle sidebar

Esta página não é visível na pré-visualização

Não perca as partes importantes!

bg1
**
**
** VIA Rhine Family Fast Ethernet Adapter
**
** RPL BOOTROM for remote-booting Windows 95
**
** v4.36 Feb 2005
**
**
Introduction:
=============
This document shows you how to congure the Remote-Boot service in
Windows
NT Server 3.5, 3.51, 4.0 for remote-booting Windows 95 client.
Contents of the Subdirectory:
=============================
RPLWIN95.TXT This le.
RPL.LOM The bootrom binary le for Lan On Motherboard..
RPL.32 The 32K bootrom binary le for Network Interface Card.
RPL.64 The 64K bootrom binary le for Network Interface Card.
FETND.DOS The NDIS2 driver require for remote boot.
W95BB.CNF The conguration le require for remote boot win95.
PROTOCOL.INI The conguration le require for remote boot.
FETND3.INF The NDIS3 driver INF le require for remote boot
Windows 95 from NT server.
FETND3R.SYS The NDIS3 driver require for remote boot
Windows 95 from NT server.
Requirement:
============
* A Windows NT 4.0 server with the Remoteboot Service installed and
congured. Earlier versions of NT do not support Windows 95 clients.
* A workstation running Windows 95 with connections to the NT server.
This workstation should have a CD-ROM drive. If not, the NT server
must have a CD-ROM drive installed and congured for sharing.
* Windows 95 on CD-ROM. Make sure the CD-ROM contains the
NETSETUP.EXE
program. You must purchase the correct licensed copy of Windows 95
for
network installation.
* An Rhine Family Fast Ethernet adapter with bootROM. You must be able
to
remoteboot from the NT server with this bootROM.
pf3
pf4
pf5
pf8
pf9
pfa

Pré-visualização parcial do texto

Baixe Configuração de Serviço Boot Remoto para Windows 95 e outras Notas de estudo em PDF para Informática, somente na Docsity!

** VIA Rhine Family Fast Ethernet Adapter ** ** RPL BOOTROM for remote-booting Windows 95 ** ** v4.36 Feb 2005 ** **

Introduction:

This document shows you how to configure the Remote-Boot service in Windows NT Server 3.5, 3.51, 4.0 for remote-booting Windows 95 client.

Contents of the Subdirectory:

RPLWIN95.TXT This file. RPL.LOM The bootrom binary file for Lan On Motherboard.. RPL.32 The 32K bootrom binary file for Network Interface Card. RPL.64 The 64K bootrom binary file for Network Interface Card. FETND.DOS The NDIS2 driver require for remote boot. W95BB.CNF The configuration file require for remote boot win95. PROTOCOL.INI The configuration file require for remote boot. FETND3.INF The NDIS3 driver INF file require for remote boot Windows 95 from NT server. FETND3R.SYS The NDIS3 driver require for remote boot Windows 95 from NT server.

Requirement:

  • A Windows NT 4.0 server with the Remoteboot Service installed and configured. Earlier versions of NT do not support Windows 95 clients.
  • A workstation running Windows 95 with connections to the NT server. This workstation should have a CD-ROM drive. If not, the NT server must have a CD-ROM drive installed and configured for sharing.
  • Windows 95 on CD-ROM. Make sure the CD-ROM contains the NETSETUP.EXE program. You must purchase the correct licensed copy of Windows 95 for network installation.
  • An Rhine Family Fast Ethernet adapter with bootROM. You must be able to remoteboot from the NT server with this bootROM.

Installation:

Before starting the installation process, make sure that the adapter is properly installed and configured. You can use the diagnostic program (A:\DIAG.EXE) to make sure your connection with the network is correct.

Setup Procedure for DOS

  1. The BOOTROM installation procedures are identical in Windows NT Server 3.5, 3.51, 4.0. First, install the Remoteboot Service on the NT Server:

Choose "Control Panel\Network\Add Software" and select "Remoteboot Service", follow the screen instruction to install.

  1. Use "File Manager" in NT Server 3.5, 3.51 or "Windows Explorer" in NT Server 4.0 to share the following directory:

\windows\rpl\rpl\rplfiles, suppose \windows is your Windows NT directory.

  1. Copy all the MS-DOS 6.22 files as follow:

attrib -s -h -r c:\io.sys attrib -s -h -r c:\msdos.sys copy c:\io.sys c:\windows\rpl\rplfiles\binfiles\dos copy c:\msdos.sys c:\windows\rpl\rplfiles\binfiles\dos copy c:\dos622*.* c:\windows\rpl\rplfiles\binfiles\dos attrib +s +h +r c:\io.sys attrib +s +h +r c:\msdos.sys

  1. Copy the NDIS2 driver for "PCI Fast Ethernet Adapter" as follow:

copy a:\bootrom\fetnd.dos c:\windows\rpl\bblock\ndis md c:\windows\rpl\bblock\netbeui\fetnd copy a:\bootrom\fetnd.cnf c:\windows\rpl\bblock\netbeui\fetnd copy a:\bootrom\protocol.ini c:\windows\rpl\bblock\netbeui\fetnd

  1. Run RPLCMD to add a bblock record for the adapter as follow:

net start remoteboot ;run in MSDOS prompt rplcmd ;Follow the example below to enter data

Adapter Boot Config Profile Service Vendor Wksta [Quit] V Add Del Enum: A

1.Installing SBS for Windows 95 Clients

(1) On the server that will contain SBS files, create a shared directory with 90 MB of space available. The shared directory can have any name. (for example, \server direcotry\sharedir as \NT4S\SBS).

(2) As you share the directory, assign read-only permission for regular users and full access for administrators.

(3) Install one regular Windows 95 client on the network or use an existing one. You will use this client to configure the SBS server.

(4) Log on to the Windows 95 client using an account that has wirte access to the shared directory on the SBS server.

(5) Make sure you use Windows 95 UPGRADE Version. Put the Windows 95 compact disc in the client CD-ROM dirve. In Windows Explorer, switch to the Admin\Nettools\netsetup directory.

(6) Double-click Netsetup.exe

(7) In the Server-Based Setup dialog box, click Set Path, and specify the path to the SBS server; then click OK, A network name for a server (for example, \server1\sharedir as \NT4S\SBS).

(8) Click Install

a. Set the source path for Windows 95 files. b. This is the path to the compact disc on the client. c. If asked, specify that you do not want to create a default setup script. d. Provide a CD Key number for product identification. e. If you support only remoteboot clients, click Server. f. If you support other SBS functions as well, click User choice. g. Do not click Local hard drive. h. Server-Based Setup copies Windows 95 files to the SBS shared directory.

(9) Copy driver file fetnd3r.sys from diskette to shared directory on SBS server. For example: copy [boot win95 by rpl]\fetnd3r.sys \NT4S\system

(10) At the remoteboot server, put the compact disc containing the Windows NT remoteboot for Windows 95 files into a drive. Run win95srv.bat to update the Windows 95 files for remotebooting.

For example: E: cd \client\rpl\update win95srv.bat is the shared directory on the SBS server as \NT4S\SBS

(11) At the remoteboot server, start Remoteboot Manager.

(12) On the Configure Menu, click Check Configuration to activate the new configurations.

  1. Installing the First Windows 95 Client

(1) Installing the first Windows 95 client requires booting that client first to MS-DOS 6.2.x (Refer the section "Setup up procedure for DOS").

(2) Machines directories can reside on the remoteboot server. Mkdir c:\rplmachines Net share machines=c:\rplmachines

(3) Use the net logon command to log on using an account that has read access to the SBS server and write access to the shared directory that will contain this client machine directory.

(4) Synchronize the time and date settings of the client, the SBS server, and the remoteboot server. Differing settings can interfere with Windows 95 Setup. The format of this command is

net time /domain:server /set

for example : net time /domain:NT4S /set

Note: We sugget exeluding serial port detection. It conflicts your network adapter easily.

  1. In the Select Components dialog box, click to clear the Communications check box (unless the client has a modem and you intend to use dial-up networking).
  2. In the Network Configuration dialog box, check that your network adapter and desired.

Note: Don't remove Diup-Up adapter in installation procedure.

  1. If there are no network adapters shown, you must add and configure your network adapter.

Note: Make sure your adapter driver is for boot rom, not for Windows 95. You can get these files in this folder.

  1. In the Identification dialog box, make sure that the workgroup for this client is the same as the workgroup or domain of the SBS server and machine directory server.
  2. When the Windows 95 Setup program is done, reboot the client. The client will not yet boot to Windows 95; however you must complete more steps first.
  3. Create a profile for the Windows 95 client

At the remoteboot server (or a client running Remoteboot manager focused on the remoteboot, start Remoteboot manager)

(1) Boot the client to MS-DOS 6.2x to confirm that the MS-DOS configuration is correct. For details, see adding a New Clientt earlier in this chapter.

(2) Copy w95bb.cnf to \NT4S\RPL\BBLOCK\NETBEUI\FETND

(3) Use the rplcmd utility to add a boot block record for the new adapter

C:\NT4S\RPL>rplcmd Adapter Boot Config Profile Service Vendor Wksta [Quit]: B Add Del Enum: A BootName=W95V VendorName= BbcFile=BBLOCK\NETBEUI\FETND\W95ND.CNF All other parameters are optional BootComment=Name of the adapter WindowSize=

Adapter Boot Config Profile Service Vendor Wksta[Quit]:C Add Del Enum: A ConfigName=Win95V BootName=W95V DirName=DOS DirName2=Win FitShared=FITS\WIN95.FIT FitPersonal=FITS\WIN95P.FIT All other parameters are optional ConfigComment=Windows 95 DirName3= DirName4=

(4) Edit the client workstation record to assign the client to the Widnows 95 profile.

(5) You must also copy \protocol.ini and \fetnd.dos NDIS driver to c:\machine0\client1\suboot directory. copy \fetnd3r.sys file to c:\sbsfiles\system directory.

note: if you lost fetnd3r.sys file that win95 system will show the message "you can now safely turn off your computer.if you want to restart your computer"

(6) Next, you must manually edit the following files found in the C:\machine0\client1\SUBOOT directory

  • AUTOEXEC.BAT
  • MSDOS.SYS
  • PROTOCOL.INI --- this folder
  • FETND.DOS --- this folder
  • SYSTEM.DAT

the new information.

regedit /L:system.dat /C registry.txt

(12) Remove the hidden, system, and read only attributes from SYSTEM.DAT by entering:

attrib -r -s -h system.dat

(13) copy new system.dat to c:\machine0\client3\suboot directory.

(14) At the remoteboot server run the Rpl\Bin\win95clt.bat program by typing:

cd \rpl\bin win95clt mach_directory \rpl_server profile_name For example: win95clt \NT4S\machines\client1 \NT4S w95rhine

(15) At the SBS server, edit machines.ini file in the SBS directory and add the following lines for the new client:

[adapter id] SYSDATPATH=g:\machine_dir g=\machine_dir\mach_share

For example, you might add the following lines to machines.ini:

[004064003021] SYSDATPATH=j:\client j=\NT4S\machines

(16) Reboot the Widnows 95 client.

The client will now boot to Windows 95 and complete the Windows 95 Setup program.