发信人: raymud()
整理人: chinesemrfx(2000-08-21 02:08:20), 站内信件
|
windows 95 remote boot from NT server
situation and discussion:
Install Accton's sw7145 generic RPL ROM for windows 95 client booting
from a windows-nt 4.0 server.
solution:
running an ms-dos remote boot client from widnows nt 4.0 server
In the following procedure you install msdos files on the server. for
information about how to install windows95 files , see installing wind
ows 95.
for windows 95 clients later in this chapter.you can't install windows
95
until you have at least one msdos remote boot client running.
Installing the remote boot service (with a new remote boot directory)
1.If they ae not already installed, install the DLC and NETBEUI protoc
ols
on the server. the remote service requires DLC and NETBEUI.
2.in the control panel, choose the network icon.
3.In the network settings dialog box,choose the add software buttor
4.In the add network software dialog box,select the remote boot servic
e.
5.In the remote boot setup dialog box, type the full path and director
y
name where you want to install the remote boot directory.
6.choose ok.
7.complete the dialog boxes that appear.
Installing msdos files for remote boot workstations (to copy msdos fil
es
to the server).
1.check that the \systemroot\rpl\rplfiles directory is being shared
on the Remote boot server. It should have the share name rplfiles.
2.from an msdos client (running a version of msdos that you want to
support on the remote boot server),connect to the remote boot server-s
rplfiles share by typing:
3.copy all the msdos files th the \systemroot\rpl\rplfiles\binfiles\do
sxxx
directory, where xxx is the version number(for example,dos622),by typi
ng:
copy c:\dos\*.* v:\binfiles\dos622
attrib -s -h c:\io.sys
attrib -s -h c:\msdos.sys
copy c:\io.sys v:\binfiles\dos622
copy c:\msdos.sys v:\binfiles\dos622
attrib +s +h c:\io.sys
attrib +s +h c:\msdos.sys
copy files to an existiong dosxxx directory only; do not create a new
directory. for example, any version of msdos 6.2x must be copied to th
e
existing dos622 director.
4.if you copied dos files other than msdos (such as pcdos),you must
rename the following files. from the \systemroot\rpl\rplfiles\binfiles
\dosxx
directory on the remote boot server, type:
rename ibmdos.com msdos.sys
rename ibmbio.com io.sys
starting the remote boot service.
......
1.in the control panel, choose the services icon.
2.in the services dialog box, select the remote boot service. you may
need to scroll down the list of services to reach it.
3.choose the start button.
4.in the services dialog box,choose the close button.
you can also use the net start remote boot command to start the
remote boot service.
starting remote boot manager.
1.on the windows nt server computer,log on to a user account that
belongs to the administrators local group.
2.from the network administration program group,choose the remote
boot manager icon.
checking the remote boot installation.
after you start the remote boot scrvice for the first time,check
the srver_s event log for entries related to the remote boot service.
use even view in the administrative tools group.
to check the remote boot configuration:
1from the configure menu,choose check configurations.
2.choose the yes button.
th check security settings in the remote boot directory choose fix
security form the configure menu, and the select the yes button
creating remote boot configurations for new adapters.
1.go to msdos prompt, run rplcmd.exe to add boot config and vendor.
example:copy adapter driver diskette
a:\ndis\dos\ethne.dos to
c:\winnt\rpl\bblock\ndis directory.
create directory
c:\winnt\rpl\bblock\netbeui\ethne
copy:
a:\bootrom\nt\dosbb.cnf c:\winnt\rpl\bblock\netbeui\ethne
modify protocol.ini osbase and irq parameters to match adapter setting
.
example: use rplcmd utility to add a boot block for the new adapter
c:\winnt\rpl>rplcmd
adapter boot configprofile service vendor wksta [quit]:b
add del enum:a
boot name=dosa
vendorname=0000e8
bbcfile=bblcok\netbeui\ethne\dosbb.cnf
all other parameters are optional
boot comment =ethernet isa
windowssize=0
example:use rplcmd utility to add the new configuration.
c:\winnt\rpl>rplcmd
adapter boot config profile sevice vendor Wksta [quit]:c
add del enum:a
configname=dos622x
bootname=dosa
dirname=dos
dirname2=dos622
fitshared=fits\dos622.fit
fitpersonal=fits\dos622p.fit
all other parameters are optional
configcomment=dos 6.22 &en165x
dirname3=
dirname4=
example:use rplcmd utility to add vendor id.
c:\winnt\rpl> rplcmd
addapter boot config profile service vendor wksta [quit]:v
add del enum:a
vendorname=0000e8
vendorconnent=accton en165x/en166x
going to windows remote boot manager to add new profiles,new
workstation or convert adapter.
create a profile:
1.from the remote boot menu in the remote boot manager,choose new
profile.
2.from the profile name, type a name for the profile,(for example
dos622)
3.in the configuration box,choose a configuration.
4.from the description, type a connent for the profile.
convert the adapter:
1.in remote boot manager on the server, from the view menu, choose
refresh.
2.in remote boot manager,select the adapter recore that has appeare
with the network adapter id number in place of the workstation name.
from the remote boot menu,choose convert adapters.
3.in the wksta name box,type a name for the workstation.(this name
is necessary).
4.choose add.
Installing client stations:
1.put generic boot rom to adapter boot rom socket.
2.run setup program or 1 step program to enable boot rom.
example:roltocol.ini
[protman]
drivername = protman$
dynamic = yes
priority = netbeui
[netbeui_xif]
drivername = netbeui$
bindings = ethne_nif
names = 6
ncbs = 12
packets = 20
pipeline = 10
sessions = 6
stacksize = 512
lanabase = 0
[xnsnb_xif]
drivername = xnsnb$
bindings = ethne_nif
load = xnsnb[cbr]
lanabase = 1
[xnstp_xif]
drivername = xnstp$
bindings = ethne_nif
load = xnstp[ub]
lanabase = 1
[tcpip_xif]
drivername = TCPIP$
disabledhcp = (TCPIP_NO_DHCP)
ipaddress0 = (TCPIP_ADDRESS)
subnetmask0 = (TCPIP_SUBMASK)
defaultgateway0 = (TCPIP_GATEWAY)
tcpsegmentsize = 1450
tcpwindowsize = 1450
nbsessions = 6
load = tcptsr[c],tinyrfc[c],emsbfr[cr]
unload = "unloadt /notsr[dc]"
bindings = ethne_nif
lanabase = 1
[ipx_xif]
drivername = ipx$
load = ipxmark[u],ipx[u]
unload = ipxrel[c]
bindings = ethne_nif
lanabase = 1
[msdlc_xif]
drivername = msdlc$
bindings = ethne_nif
load = msdlc[ub]
unload = msdlc[u]
[ms2000_nif]
drivername = ethne$
iobase=0x300
irq=3
installing windows 95 for windows 95 cllients
......
to support windows 95 remote boot clients,you must install server-
based setup (sbs) on a server, install the first windows 95 clients,
and then install subsequent clients.
installing sbs for windows 95 clients
when you setup an sbs server you can use the sbs server for windows
95 remote boot.you will need a windows 95 installaton compact disc(not
floppies) and a windows 95 client computer.
to install an sbs server:
1.on the server(for example, use windows nt 4.0 as sbs server) that
will contain sbs files, create a shared directory with 90mb space avai
lable.
the shared directory can have any name (for example, use sbsfiles as
the shared name).
as you share the directory, asign red-only permission for regular
and full acess for administrators,for example, use server manager to f
orcus
on he shared directory and set readonly permission for the users group
and
full permission for the administrators group. in file manager,use the
share
command from the disk menu rather than the permissions command form th
e
security menu.
2.install one regular windows 95 client on the network or use an exist
ing
one.you will use this client to configure the sbs server.
3.log on to the windows 95 client using an account that has write acce
ss
to the shared directory on the sbs server.
4.put the windows 95 compact disc in the windows 95 clent-s cdrom. in
windows explorer,switch to the admin\nettools\netsetup directory.
5.double click netsetup.exe
note you must run netsetup.exe at a windows 95 client, and connect to
nt server.
6.in the server-based setup dialog box,click the set path (or change p
ath)
button, and then specify the path to sbs server. then click ok.
you can type a drive letter for a mapped drive a network name for a se
rver
(for example, \\tts\sbsfiles),
the button name becomes change paht if a server was defined previous.
7.click install .server based setup presents a series of dialog box ca
n
install windows 95 from the server. if you support other sbs functions
as well,
choose userls choice,do not choose local hard drive.
set the source path for windows 95 files.this is the path to the compa
ct
disc on the client.
if asked, specify that you do not want to create a default setup scrip
t.
setup scripts for widnows nt remote boot installation require special
settings.
provide a cd key number for produt identification.
server-based setup copies windows 95 files to the sbs shared directory
.
8.at the remote boot server, put the windows nt4.0 compact dic into a
drive.
change to the dirve and then change to the update\win95 directory.
run win95srv.bat to update the windows 95 files for remote booting.
for example:
d:
cd \update\win95
win95srv.bat
where is the shared dictory on the sbs server
for example:
win95srv.bat \\ts\sbsfiles
9.at the romote boot srver, start remote boot manager,from the configu
re
menu,choose check configurations to activate the new configurations,
installing the first windows 95 client requires booting that client fi
rst to
msdos6.2x running windows 95 setup on the client ,and then copying sel
ected
files from the clients machine directory to the remote boot server.
once you have installed this first client, you can easily install subs
equent
clients by using sbs to make a modified copy of the original machine d
irectory
withouthaving to run windows 95 setup again.
each reote boot client has a machine directory. this is a directory on
a
server theat contains client specific configuration information and da
ta.
for example the machine directory contains the following:
appropriate initialization and donfiguration files (including win.ini
an system.ini)
system.dat and user.dat(the registry)
files that define the diestop ,start menu directories,and other progra
ms
the spool directory for printing
the swap file and temp directory
amchine directories can reside on the remote boot server,on the sbs se
rver,
or on any designated server on the network, you may want to spred the
load of machine directories across servers, the only qualifications fo
r a machine
directory server are sufficient diak space and running the netbeui pro
tocol
to create a location for machine directories,simply make a shared dire
ctory
on a server and share it with a name tha does not contain space.for ex
ample.
on a computer running windows nt server that will contain manchine dir
ectories,
type:
mkdir c:\rplmachines
net share machines:c:\rplmachines
for example:
mkdir c:\machine
net share machine=c:\machine
note: the machine directories may not be subdirectories of the sbs dir
ectory.
assign permissions to a machine directory so that only the users or a
administrators who will use the client have read and write permissions
in the
directory. if the machine directory is on an ntfs partition, assign pe
rmissions
directly to the machine directories,if the machine directory is on a f
at
partition, assign permissions to the shared directory containing the m
achine
directories.
installing the first windows 95 client
......
1.boot the new client to msdos 6.2x, using procedures in running a msd
os remote
boot client from windows nt4.0 server earlier in this chapter.you will
need to
run windows 95 setup while the client is booted from the remote boot s
ervice
rather than when the client is booted form a flopy disk or hard drive.
2.use the netlogon command to log on using an accout that has read acc
ess to the
sbs server and write access to the shared directory that well contain
this
clients machine directory. a good example is the accout of someone who
will
use this client,as they will need this access anyway.
3.syncronize the time and date setting of tha client,the sbs server,an
d the remote
boot server.differing setting can interfere whith windows 95 setup.
4.use the net use command to map drive letters to the sbs server and m
achine
directory location.determine the highest drive letter in use on the co
mputer.
c: is a virtual hard drive mapped to parts of the remote boot server.e
ach local
hard drive partition (if any)takes another drive letter after c:(for e
xample,
d: and e: for two partitions). one more drive letter is reserved for u
se as a
ram drive during the windows 95 boot process.drive letters after that
are
available for use. for example, if you have a local hard drive with pa
rtition,
c:will be mapped to the remote boot server,d:will be the local hard dr
ive,
e: is reserved for use as a ram dirve,and f: and higher are available
for use.
you would type :
net use f:\sbs-server\win95_share
uet use g:\mach_server\mach_share
an example:
net use f: \\ts\sbsfiles
net use g: \\ts\machine
5.chage to the dirve letter mapped to the sbs directory.
6.run the windows 95 setup program by typing
setup /t:temppath
where /t: is required and temppath is a path to a directory in which t
o store
temporary files during installation.for example if g: is mapped to the
shared
directory containing the clients machine directory,you could type
setup /t: g:\client1.tmp to store temporary files on that server.
do not delte the t:\temppath directory until you have completed step12
.
if you are installing two windows95 clients simultaneously (for exampl
e,to
support clients with diferent network adapters),choose separate tempor
ary
directories for each client.
make the following decisions during setup:
.in the server-based setup dialog box,choose setup windows from a netw
ork server
.in the startup metod dialog box chooose start windows form the networ
k
(remote boot server)
.in the machine directory dialog box ,when asked where to install wind
ows95,
type the path of the machine directory(using the dirve letter specifie
d in step4,
for example, g:\client1)
.in the setup options dialog box,choose custom setup.
.in the analyzing your computer dialog box ,choose no, I want to me di
fy the
hardware llist.
exclude as many hardware types and items from autodetection as possibl
e. if autodetection crashes,ren setup again and exculde more items fro
m autodetection.
one problem could be that your network adapter is on irq2 or irq3;this
conflicts
with serial port detection with some network adapters.
.in teh select components dialog box,clear the checkbox for commuricat
ions
(unliss the client has a modem and you intend to use dial-up networkin
g)
.in the network configuration dialog box.check that your network adapt
er and
desired protocols are present and configured correctly. if there are n
o network
adapters shwn,you must add and configure your network adapter.
if you add your network adapter, you must confirm the resource setting
s for the
adapter. select the adapter name in the network configuration dialog b
ox ,click
properties, and then click the resources tab.check that the settings d
isplayed
are correct (for example, the interrupt level).then,click ok to force
the setup
program to acept the settings; do not click cancel.
for details ablut protocols on windws 95 renote boot clients,see suppo
rting
other protocols.later in this chapter.
in the inedtificatiog dialog box ,make sure that the workgroup for thi
s client
is the same as the workgroup or damain of the sbs server and machine d
irectory
server.
when the windows 95 setup program is done reboot the cllient ,the clie
nt will
not yet boot to windows 95,however,you must complete more steps first.
7.at hte remote boot server(or a client running remote boot manager fo
cused on
the remote boot server),start remote boot manager.
8.cherate a profile for the windows 95 client .in the configuration bo
x choose
the windows 95 configuration corresponding to the clients network adap
ter type.
if you are not sure which configuration to choose,check the profile th
at is
currently associated with this client for booting msdos, and use the e
quivalent
windows 95 profile.
the following is the procedure to create the proflie for the windows 9
5 remote
boot client:
.go to msdos prompt ,run rplcmd.exe to add boot config. and vendor.
.go to windows remote boot manager to add new profiles and new worksta
tion or
convert adapter if remote boot stations have started booting function.
to create a profile:
a.from the remote boot menu in the remote boot manager, choose new pro
file.
b.from the profile name ,type a name for this profile.(for example,win
95pro)
c.in the configuration box,choose a configuration.
d.from the description, type a comment for the profile.
to convert adapter;
a.in remote boot manager on the server, from the view menu,choose refr
esh.
b.in remote boot manager, select the adapter record that has appeare w
ith
the network adapter id number in place of the workstation name.
from the remote boot menu,choose convert adapters.
c.in the wksta name box,type a name for the workstation.
make sure this wksta name ust same with the machine name that you typi
ng
in the setup.
win95 process.
d.choose add.
9.edit the clients workstation record to assign the client to the wind
ws 95
profile.
10. at the remote boot server(or a client with write access to the rem
ote boot
servers rpl driectory),run the rpl\bin win95clt.bat program
11 at the sbs server (or a client with write access to the sbs driecto
ry),edit
the machines.in files in the sbs directory.add the following lines for
the new chient:
[adapter id]
sysdatpath=g:\amchine_dir
g=\\mach_server\mach_share
--
※ 来源:．月光软件站 http://www.moon-soft.com．[FROM: 202.94.2.205]
|
|