Îò: Marc Murczak Òåìà: Remote Booting for DOS and Win95 Äàòà: 20 îêòÿáðÿ 1999 ã. 13:14 Model: DE-220 Rev: Additional Models: DE-220C, DE-220CAT, DE-220CT, DE-220CT/6L, DE-220CT/50L, DE-220C/6L, DE-220ECT, DE-220ECT/50L, DE-220ECT/6L, DE-220ET, DE-220ET/50L, DE-220PCAT, DE-220ET/6L, DE-220PCT, DE-220PCTFREE, DE-220PCT/50L, DE-220PCT/6L, DE-220PT, DE-220PT/50L, DE-220PT/6L, DE-220T, DE-220TP, DE-220T/50L, DE-220T/6L, DE-224B, DE-224C Summary: Remote Booting for DOS and Win95 Details: Setup Remote boot Service on NT4 Server for DOS and Windows 95 workstations with D-Link network adapters D-Link ISA family cards can support remoteboot on NT server for DOS/Windows with either-D-link driver or NE2000 driver and for Windows 95 with NE2000 driver. D-Link PCI family adapter can support remoteboot on NT server for DOS/Windows. NT cannot support remoteboot for Windows 95 workstation with PCI adapter. Following is the setup procedures for DE-220 family adapters to remoteboot Windows 95(The following text is based on Microsoft Windows NT 4 Network Resource Kit): o set up the Remoteboot service (summary) 1. Prepare the D-Link network adapter for remoteboot. 2. Create a boot block on NT server for that family of network adapters. 3. Install Windows NT Server on a computer that will be the remoteboot server. There are three special considerations for the Remoteboot service: · The server's computer name must not have spaces in it. · It is strongly recommended that you install remoteboot files on a disk partition formatted with NT File System (NTFS) so that permissions are correctly set. Users will be able to read and write their own files in the remoteboot directory but not write to shared files or system configuration files. Also, the File Allocation Table (FAT) file system does not support more than approximately 100 remoteboot clients. Install the Data Link Control (DLC) and NetBIOS Extended User Interface (NetBEUI) protocols and ensure that clients can communicate with the server using these protocols (arrange proper routing, bridging, etc.). 4. Install the Remoteboot service on the remoteboot server. Or, convert an existing Microsoft LAN Manager for OS/2 remoteboot installation to run on Windows NT Server, and then install the Remoteboot service. Note Windows NT Server does not support remote booting of OS/2 clients, Windows for Workgroups clients, Windows NT Workstation clients, or Windows NT Server clients. 5. Install MS-DOS and/or Windows 3.1 operating system files on the remoteboot server. If you are converting from LAN Manager remoteboot, this may not be necessary. 6. If you will have Windows 95 remoteboot clients, install Windows 95 real-mode (also identified as MS-DOS 7.0) files on the remoteboot server. 7. Start the Remoteboot service. 8. Check the installation for errors, including checking the Event Viewer log. 9. Create profiles (these define the working environment shared by one or more clients). 10. If you will have Windows 95 remoteboot clients, install a Server-Based Setup (SBS) server. This can be the same computer as the remoteboot server or it can be a separate server on the network. The SBS server must run the NetBEUI protocol. 11. If you will have Windows 95 remoteboot clients, create a location for machine directories. This can be on the same computer as the remoteboot server or SBS server, or it can be on a separate server on the network. The server containing machine directories must run the NetBEUI protocol. This section provides step-by-step instructions for these actions. For instructions on managing remoteboot clients, see "Managing Remoteboot Clients" later in this chapter. To Prepare the D-Link network adapter for remoteboot. 1. Install DE-224C BootRom on DE-220 family adapter. 2. Run setup program from the driver diskette of the card to setup the card as: IO=300, Memory address = D000, IRQ=3, or 5, or 10 (If using NE2000 driver, use 3) To create a new boot block record for a supported network adapter type · Use the rplcmd utility to add boot block records for the adapter and vendor ID. For details about the rplcmd utility, see the preceding section, "Using the Remoteboot Command Utility (RPLCMD.EXE)." For BootName, use the name of an existing boot block record that boots clients with network adapters of this type (but with a different vendor ID). For example, the following sequence of commands creates sample boot block records for MS-DOS and Windows 95: C:\winnt\rpl> rplcmd Adapter Boot Config Profile Service Vendor Wksta [Quit]: b Add Del Enum: a BootName=DOSV VendorName=0080C8 (for D-Link cards ) BbcFile=BBLOCK\NETBEUI\NE2000\DOSBB.CNF All other parameters are optional BootComment=DE-220-DOS WindowSize=0 Adapter Boot Config Profile Service Vendor Wksta [Quit]: b Add Del Enum: a BootName=W95V VendorName=0080C8 BbcFile=BBLOCK\NETBEUI\NE2000\W95BB.CNF All other parameters are optional BootComment=DE-220-Win95 WindowSize=0 To install the Remoteboot service (with a new remoteboot directory) 1. If they are not already installed, install the DLC and NetBEUI protocols on the server. The Remoteboot service requires DLC and NetBEUI. 2. Click Start, point to Settings, and click Control Panel. 3. Double-click Network. 4. In the Network Settings dialog box, click Add Software. 5. In the Add Network Software dialog box, select the Remoteboot Service. 6. In the Remoteboot Setup dialog box, type the full path and directory name where you want to install the remoteboot directory. The default value is \Rpl. This is the directory shown in descriptions and examples. 7. Click OK. 8. Complete the dialog boxes that appear. For help with any dialog box, press F1. See the post-installation information after the next procedure. To copy MS-DOS 6.2x files to the server 1. Check that the \Rpl\Rplfiles directory is being shared on the remoteboot server. It should have the share name Rplfiles. 2. From an MS-DOS client (running a version of MS-DOS 6.2x that you want to support on the remoteboot server), connect to the remoteboot server's Rplfiles share by typing: net use v: \\server\rplfiles where server is the name of the remoteboot server. 3. Copy all the MS-DOS files to the \Rpl\Rplfiles\Binfiles\Dosxxx directory, where xxx is the version number (for example, Dos622), by typing: 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 As shown, you may need to remove the hidden file attribute in order to copy these files and then reset the attribute after copying. You can do this with the MS-DOS attrib command. Note Do not set the hidden or system file attributes on the new copies of the files in the \Rpl\Rplfiles\Binfiles\Dosxxx directory. Copy files to an existing Dosxxx directory only; do not create a new directory. For example, any version of MS-DOS 6.2x must be copied to the existing Dos622 directory. 4. If you copied DOS files other than MS-DOS (such as PC-DOS), you must rename the following files. From the \Rpl\Rplfiles\Binfiles\Dosxxx directory on the remoteboot server, type: rename ibmdos.com msdos.sys rename ibmbio.com io.sys The Remoteboot service is installed as a manual service, meaning that you must start it intentionally each time you want it to run. If you want it to start automatically each time the server starts, see the instructions in online Help for the Services icon in Control Panel. To start or stop the Remoteboot service 1. Click Start, point to Settings, and then click Control Panel. 2. Double-click Services. 3. Click the Remoteboot service. You may need to scroll down the list of services to reach it. 4. Click Start or Stop. Pause and Continue have no effect on the Remoteboot service. 5. In the Services dialog box, click Close. You can also use the net start remoteboot command to start the Remoteboot service and net stop remoteboot to stop it. Remoteboot Manager is an administrative tool for controlling the remoteboot process and managing remoteboot clients. To start Remoteboot Manager 1. At 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, click the Remoteboot Manager icon. 3. If you want to administer a remoteboot server other than the local computer, click Set Focus on the Remoteboot menu. Type the name of the remoteboot server, or choose the name from the Select Computer box. Or, from the command line, type rplmgr (or rplmgr \\server, where server is the name of a Windows NT Server computer). After you start the Remoteboot service for the first time, check the server's event log for entries related to the Remoteboot service. Use Event Viewer in the Administrative Tools group. You should also use Remoteboot Manager's configuration and security checking features after installation and after you add or remove support for an operating system. To check the remoteboot configuration 1. On the Configure menu, click Check Configurations. 2. Click Yes. This checks which operating systems are available for remoteboot clients. Remoteboot Manager offers these as choices for profiles. To check security settings in the remoteboot directory 1. On the Configure menu, click Fix Security. 2. Click Yes. This overwrites permissions throughout the \Rpl directory, creates accounts for remoteboot clients and the RPLUSER local account (if they don't already exist), and updates the domain entry in Lanman.ini files for remoteboot clients to match the server's own domain/workgroup. When you use Remoteboot Manager for the first time, you must decide which profiles you need. A profile is the working environment shared by one or more clients. It consists of the operating system, the client computer and architecture type, the network adapter type, and all the other information needed to boot a client. Note Remoteboot profiles are completely different from user profiles, which are used elsewhere in Windows NT Server. To establish and name profiles, you choose from a list of configurations. A configuration is actually a template profile; a profile is created as a copy of one of the base configurations. Generally, you can find a configuration for any profile you want to create. Once the profiles are defined, it's easy to add clients. Clients use profiles in either of two ways: sharing a profile or using a personal copy of a profile. The profile is the same in either case; the difference is in how the client uses it. A profile can be shared by a group of similar client computers that use the same startup information. (All of the clients have the same Config.sys, Lanman.ini, and other configuration files, and those files are read-only.) For example, you may want to have a common profile that is shared by accounting, and another profile for sales and marketing. Or, you may want to create a profile shared by all Windows 3.1 users. Keep in mind, however, that the client computer architecture must be similar enough that the clients can share startup files. Clients that share profiles get their environment from a \Rpl\Rplfiles\Profiles\profile directory (where profile is the name of the profile). Sharing profiles is not practical in all cases. For example, a client may need customized system configuration files (like Config.sys). In this case, the client should use a personal copy of a profile. Changes to the startup information affect only the single client. Clients that have a personal copy of a profile get their environment from a \Rpl\Rplfiles\Machines\cname\profile\Pro directory (where cname is the computer name and profile is the name of the profile). Users can edit any of the files in that directory, such as Config.sys. When you upgrade operating systems and make software changes, you need to install them separately to each profile and copy of a profile. To create a profile 1. On the Remoteboot Manager Remoteboot menu, click New Profile. 2. In Profile Name, type a name for this profile [no more than 16 characters, with no spaces or backslashes(\)]. 3. In Configuration, enter a configuration. If the configuration you want is not present, you must install the appropriate operating system (see "Installing MS-DOS Files on the Remoteboot Server" earlier in this chapter) and check the configuration (on the Configure menu, click Check Configurations). 4. In Description, type a comment for the profile. The description should summarize the profile for easy recognition, such as MS-DOS 6.22 VGA & 3Com 503 EtherLink II adapter. 5. Click OK. To change a profile 1. Select an existing profile in Remoteboot Manager. 2. On the Remoteboot menu, click Properties. 3. Change the description of the profile, and then click OK. You can change only the description. To change any other settings, you must create a new profile. To delete a profile 1. Select an existing profile in Remoteboot Manager. 2. On the Remoteboot menu, click Delete. 3. If a message appears telling you that clients (workstation records) are still assigned to this profile, you can delete or reassign all of the clients at one time: · In the error message dialog box, click OK. · Select the profile. · On the View menu, click Workstations In Profile. · Select all of the workstation records (press CTRL and click all of the workstation records). · On the Remoteboot menu, click Delete. Or, on the Remoteboot menu, click Properties. Choose a new profile for all of the clients, and then click OK. 4. In the Confirmation dialog box, click OK. Once you have profiles set up, most remoteboot administration consists of managing the individual clients. As described earlier in "Setting Up and Starting the Remoteboot Service," you created profiles for clients. You can add a new remoteboot client in two ways: · Create a new remoteboot database record for the client and manually fill in the necessary data, including the client's network adapter ID number and the profile you want this client to use. This is only recommended when you know the network adapter ID number and you are copying an existing workstation record. When you copy an existing workstation record, you also copy the personal configuration information. For example, if the original workstation record uses a personal copy of a profile and has a customized installation of Windows 3.1, the profile and the Windows installation will be copied for the new client. · Boot the client remotely with no special preparation on the server. This creates an adapter record on the server, which you can then convert to a workstation record by adding the client's name and profile. This is easier because you don't need to know the client's network adapter ID number. When you boot the client, a remoteboot logon prompt appears: Type Remoteboot username, or press enter if it is : This asks for the account name and password associated with the client itself, not for the user's own account name and password. Once the boot is complete, the user should type a net logon command to log on with his or her own username and password. When the client has completed a remote boot, the current directory is C:\, and the C drive is a virtual hard drive, parts of which are mapped to various places on the remoteboot server by the FIT file. For information about FIT files and translation pairs, see "Directory, File Index, and Configuration File Details" later in this chapter. The C:\Wksta directory contains client-specific and profile-specific configuration files (such as Win.ini) and is different for each profile to which the client is joined. The C:\Data directory will always be the same, regardless of the profile used; the user can create files and directories there. The C:\Dos and C:\Lanman.dos directories provide access to MS-DOS and network utilities. The C:\Binr directory provides access to shared real-mode utilities. Local hard disks, if present, are assigned drive letters starting with D, unlike the local boot case, where the drive letters start with C. Note If the server uses NTFS, a client assigned to a profile (rather than to a personal copy of a profile) can add or modify files only in certain directories on its virtual C drive. It cannot affect directories on the C drive that are shared with other clients (unless you explicitly grant permission to do so on the server). A remoteboot client always runs the NetBEUI protocol. To run other protocols as well, see "Supporting Multiple Network Adapters and Protocols" later in this chapter. To support Windows 95 remoteboot clients, you must install Server-Based Setup (SBS) on a server, install the first Windows 95 client, and then install subsequent clients. You will need a Windows 95 installation compact disc (not floppies) and a Windows 95 client computer. To install an SBS server 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. As you share the directory, assign read-only permission for regular users and full access for administrators. For example, use Server Manager to focus on the shared directory and set read-only permission for the Users group and full permission for the Administrators group. In File Manager, click Share As on the Disk menu, not Permissions on the Security menu. 2. Install one regular Windows 95 client on the network or use an existing 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 access to the shared directory on the SBS server. 4. Put the Windows 95 compact disc in the client's CD-ROM drive. In Windows Explorer, switch to the Admin\Nettools\Netsetup directory. 5. Double-click Netsetup.exe. Note that you must run Netsetup.exe at a Windows 95 client. It will encounter errors on a computer running Windows NT. 6. In the Server-Based Setup dialog box, click Set Path, and specify the path to the SBS server; then click OK. You can type a drive letter for a mapped drive, a network name for a server (for example, \\server1\sharedir), or a network path to a specific directory (for example, \\server1\sharedir\rpl\win95). The button name becomes Change Path if a server was defined previously. 7. Click Install. Server-Based Setup presents a series of dialog boxes so that you can complete these actions: ·Specify an "install policy" for how users can install Windows 95 from the server. If you support only remoteboot clients, click Server. If you support other SBS functions as well, click User's choice. Do not click Local hard drive. · Set the source path for Windows 95 files. This is the path to the compact disc on the client. · If asked, specify that you do not want to create a default setup script. Setup scripts for Windows NT remoteboot installation require special settings. · Provide a CD Key number for product identification. Server-Based Setup copies Windows 95 files to the SBS shared directory. 8. At the remoteboot server, put the compact disc or floppy disk containing the Windows NT remoteboot for Windows 95 files into a drive. Change to the drive and then change to the Update\Win95 directory. Run win95srv.bat to update the Windows 95 files for remotebooting. For example: d: cd \update\win95 win95srv.bat where is the shared directory on the SBS server. 9. If you are updating from version 3.51 or earlier of the Remoteboot service, start the Remoteboot service at the remoteboot server if it is not already started. Then, run the rbootsrv.bat program to update the remoteboot files and database for Windows 95 remotebooting. At the server's command prompt, type: d: cd \update\win95 rbootsrv.bat [\\servername] where: · is the path to the installed SBS server's Windows 95 files. · is the path to the remoteboot directory. · \\servername is the name of the remoteboot server ; you can omit this if you are typing at the remoteboot server. 10. At the remoteboot server, start Remoteboot Manager. 11. On the Configure menu, click Check Configurations to activate the new configurations. Installing the first Windows 95 client requires booting that client first to MS-DOS 6.2x, running Windows 95 Setup on the client, and then copying selected files from the client's machine directory to the remoteboot server. Once you have installed this first client, you can easily install subsequent clients by using SBS to make a modified copy of the original machine directory without having to run Windows 95 Setup again. Each remoteboot client has a "machine directory," a directory on a server that contains client-specific configuration information and data. For example, the machine directory contains the following: · Appropriate initialization and configuration files (including Win.ini and System.ini) · System.dat and User.dat (the Registry) · Files that define the Desktop, Start menu directories, and other programs · The spool directory for printing · The swap file and Temp directory Machine directories can reside on the remoteboot server, on the SBS server, or on any designated server on the network. You may want to spread the load of machine directories across servers. The only qualifications for a machine directory server are sufficient disk space and running the NetBEUI protocol. To create a location for machine directories, simply make a shared directory on a server and share it with a name that does not contain spaces. For example, on a computer running Windows NT Server that will contain machine directories, type: mkdir c:\rplmachines net share machines=c:\rplmachines Note The machine directories may not be subdirectories of the SBS directory. Assign permissions to a machine directory so that only the users or administrators who will use the client have read and write permissions in the directory. If the machine directory is on an NTFS partition, assign permissions directly to the machine directories. If the machine directory is on a FAT partition, assign permissions to the shared directory containing the machine directories. To install the first Windows 95 client 1. Boot the new client to MS-DOS 6.2x, using procedures in "Adding a New Client" earlier in this chapter. You will need to run Windows 95 Setup while the client is booted from the Remoteboot service rather than when the client is booted from a floppy disk or hard drive. 2. 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's machine directory. A good example is the account of someone who will use this client because they will need this access anyway. 3. Synchronize the time and date settings of the client, the SBS server, and the remoteboot server. Differing settings can interfere with Windows 95 Setup. 4. Use the net use command to map drive letters to the SBS server and machine directory location, and then determine the highest drive letter in use on the computer. C: is a virtual hard drive mapped to parts of the remoteboot server. Each local hard drive partition (if any) takes another drive letter after C: (for example, D: and E: for two partitions). One more drive letter is reserved for use 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 one partition, C: will be mapped to the remoteboot server, D: will be the local hard drive, E: is reserved for use as a RAM drive, and F: and higher are available for use. You would type: net use f: \\sbs_server\win95_share net use g: \\mach_server\mach_share 5. Change to the drive 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 to store temporary files during installation. For example, if G: is mapped to the shared directory containing the client's machine directory, you could type: setup /t:g:\client1.tmp to store temporary files on that server. Do not delete the t:\temppath directory until you have completed Step 12. Also, if you are installing two Window 95 clients simultaneously (for example, to support clients with different network adapters), choose separate temporary directories for each client. Make the following decisions during setup: · In the Server-based Setup dialog box, click Set up Windows to run from a network server if asked. · In the Startup Method dialog box, click Start Windows from the network (remote boot server). · In the Machine Directory dialog box, when asked where to install Windows 95, type the path of the machine directory (using the drive letter specified in Step 4, for example, g:\client1). · In the Setup Options dialog box, click Custom setup. · In the Analyzing Your Computer dialog box, click No, I want to modify the hardware list. Exclude as many hardware types and items from autodetection as possible. If autodetection crashes, run Setup again and exclude more items from 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 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). · In the Network Configuration dialog box, check that your network adapter and desired protocols are present and configured correctly. If there are no network adapters shown, you must add and configure your network adapter. If you add your network adapter, you must confirm the resource settings for the adapter. Select the adapter name in the Network Configuration dialog box, click Properties, and then click the Resources tab. Check that the settings displayed are correct (for example, the interrupt level). Then, click OK to force the Setup program to accept the settings; do not click Cancel. For details about protocols on Windows 95 remoteboot clients, see "Supporting Multiple Network Adapters and Protocols" later in this chapter. · 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. 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. 7. At the remoteboot server (or a client running Remoteboot Manager focused on the remoteboot server), start Remoteboot Manager. 8. Create a profile for the Windows 95 client. In Configuration, click the Windows 95 configuration corresponding to the client's network adapter type. If you are not sure which configuration to choose, check the profile that is currently associated with this client for booting MS-DOS and use the equivalent Windows 95 profile. 9. Edit the client's workstation record to assign the client to the Windows 95 profile. 10. At the remoteboot server (or a client with write access to the remoteboot server's Rpl directory), run the Rpl\Bin\Win95clt.bat program by typing: cd \rpl\bin win95clt mach_directory \\rpl_server profile_name where: · mach_directory is the path to the client's machine directory. · \\rpl_server is the name of the remoteboot server. · profile_name is the name of the Windows 95 profile associated with the client. For example, you could type: cd \winnt\rpl\bin win95clt \\mach_server\mach_share\client1 \\rpl_server win95elnk2 The Win95clt program copies client-specific Windows 95 real-mode (also identified as MS-DOS 7.0) boot files from the client's machine directory to the Rpl\Rplfiles\Profiles\ directory on the remoteboot server. 11. At the SBS server (or a client with write access to the SBS directory), edit the Machines.ini file in the SBS directory and add the following lines for the new client: [adapter id] SYSDATPATH=g:\machine_dir g=\\mach_server\mach_share where: · adapter id is the network adapter ID, specified in the remoteboot workstation record for this client. · g:\machine_dir is the location of the client's machine directory on a server; g is the drive letter assigned on the next line to the shared directory where the client's machine directory is located. · g=\\mach_server\mach_share identifies the drive letter assigned to the shared directory where the machine directory resides. You must use the same drive letter and share name established in Step 4. For example, you might add the following lines to Machines.ini: [008C88EAA2D] SYSDATPATH=g:\client1 g=\\mach_server\mach_share 1. Reboot the Windows 95 client. The client will now boot to Windows 95 and complete the Windows 95 Setup program. Once you have installed a single client, subsequent clients of the same type will be much easier to install. These subsequent clients do not have to be exactly the same as the first, but they must use the same type of network adapter and the same adapter settings (IRQ, I/O address, etc.). If you need to install a Windows 95 client that does have different configuration settings, you must treat the installation as a fresh installation; see "Installing the First Windows 95 Client" earlier in this section. To install subsequent Windows 95 clients 1. Boot the new client to MS-DOS 6.2x, using procedures in "Adding a New Client" earlier in this chapter. 2. Log on to a regular Windows 95 client (for example, the one you used to run netsetup when you established the SBS server). Use an account that has write access to the shared directory on the SBS server and to the shared directory containing machine directories. 3. Put the Windows 95 compact disc in the client's CD-ROM drive. In Windows Explorer, switch to the Admin\Nettools\Netsetup directory. 4. Double-click Netsetup.exe. 5. In the Server-Based Setup dialog box, click Set Path, and specify the path to the SBS server; then click OK. You can type a drive letter for a mapped drive, a network name for a server (for example, \\server1\sharedir), or a network path to a specific directory (for example, \\server1\sharedir\rpl\win95). The button name becomes Change Path if a server was defined previously. 6. Click Add. 7. In the Set Up Machine dialog box, click Set Up One Machine and then type the following information: · Computer name: type a computer name of the client (you must create a unique name). · Path to machine directory: type a network pathname for the machine directory you want to create for the client. · Existing machine directory: type the network pathname for an existing machine directory of a client similar to this one. For example, you might type the following values: · Computer name: client2 · Path to machine directory: \\mach_server\mach_share\client2 · Existing machine directory: \\mach_server\mach_share\client1 8. Click OK. You may see an error message about creating the machine directory. Check that the directory was created and that it contains several files; if so, then disregard the error message. 9. At the remoteboot server (or a client running Remoteboot Manager focused on the remoteboot server), start Remoteboot Manager. 10. Edit the client's workstation record to assign the client to the same Windows 95 profile as the first client. 11. Edit the Machines.ini file in the SBS directory. Add the following lines for the new client: [adapter id] SYSDATPATH=g:\machine_dir g=\\mach_server\mach_share where: · adapter id is the network adapter ID, specified in the remoteboot workstation record for this client. · g:\machine_dir is the location of the client's machine directory on a server; g is the drive letter assigned on the next line to the shared directory where the machine directory is located. · g=\\mach_server\mach_share assigns a drive letter to the shared directory where the machine directory resides. Use the same drive letter used by the original Windows 95 remoteboot client. For example, you might add the following lines to Machines.ini: [0080C88EAA2E] SYSDATPATH=g:\client2 g=\\mach_server\mach_share 12. Reboot the Windows 95 client. The client will now boot to Windows 95 and complete the Windows 95 Setup program. When you boot the client, a remoteboot logon prompt appears: Type Remoteboot username, or press enter if it is : This asks for the account name and password associated with the client computer itself, not for your own user account name and password. Windows 95 then prompts you twice for your username and password: once from a command prompt and again in a dialog box. At both of these prompts, enter your user account name and password. Once Windows 95 has started, the C: drive is unassigned; it was assigned during the remoteboot process and is no longer needed. Each local hard drive partition takes another drive letter after C: (for example, D: and E: for two partitions). One more drive letter was used as a RAM drive during the Windows 95 boot process; you can now use it as a RAM drive for your own purposes. Two more drive letters, usually the next two drive letters in sequence, are mapped to the SBS server and to the shared directory containing the client's machine directory. When setting up the client, you choose exactly which two drive letters to map and they will always be the same for this client. Do not unmap or remap these drives elsewhere. For example, if you have a local hard drive with one partition, C: is unmapped, D: is the local hard drive, E: is a RAM drive, F: is mapped to the SBS server, and G: is mapped to the shared directory containing the client's machine directory.