Additional Notes -- July 1996
Remoteboot Service for Microsoft(R) Windows NT(TM) Server
---------------------------------------------------------
This document contains information about the Remoteboot service for
Microsoft Windows NT Server that was not available when the
documentation was printed.

1.  Supporting Windows 95 Clients and Windows 95 Service Pack 1
2.  Windows 3.0 and Windows for Workgroups Not Supported
3.  Using RPLCMD to Create a Profile or Workstation Record
4.  Migrating from Microsoft Windows NT 3.5 Remoteboot
5.  Special Considerations for Specific Network Adapters and Windows 95
5.1  Western Digital(TM)/SMC EtherCard(TM) Plus (8000 series)
5.2  Novell NE2000 and Intel EtherExpress PRO
5.3  AMD Series 2100 Ethernet
6.  Troubleshooting Remoteboot Problems
6.1  Troubleshooting Problems Booting MS-DOS
6.2  Troubleshooting Problems Running MS-DOS
6.3  Troubleshooting Problems Running NETSETUP
6.4  Troubleshooting Problems Running Windows 95 Setup
6.5  Troubleshooting Problems Booting a Windows 95 Client
6.6  Troubleshooting Problems on a Windows 95 Client
--------

1.  Supporting Windows 95 Clients and Windows 95 Service Pack 1
---------------------------------
If you have already installed the Remoteboot service for
Windows NT Server, and you wish to add the capability to boot
clients to Windows 95, follow the instructions in the
Remoteboot chapter in the Installation Guide titled "Installing
Windows 95 for Windows 95 Clients."

For information about supporting Windows 95 Service Pack 1 clients,
please consult the Microsoft Windows 95 Service Pack 1
Administrator Guide, in particular the sections regarding
Server-Based Setup.


2.  Windows 3.0 and Windows for Workgroups Not Supported
--------------------------------------------------------
The Remoteboot service does not support Windows 3.0 clients or
Windows for Workgroups clients. Clients can run MS-DOS (version 3.3
or higher), Windows 3.1, or Windows 95.


3. Using RPLCMD to Create a Profile or Workstation Record
---------------------------------------------------------
When RPLCMD is used to create a profile or a workstation record,
the newly created profile or workstation files on the server will
not have proper permissions.  This can be corrected by running
"Fix Security" from Remoteboot Manager.  In general, RPLCMD should
be used only for those tasks that are inaccessible via
Remoteboot Manager.


4. Migrating from Windows NT Server 3.5 Remoteboot
--------------------------------------------------
There are several remoteboot improvements introduced in Windows NT Server
version 3.51:

  (1) New NETWKSTA.* files to improve client behavior when the server is
      running the NTFS file system.
  (2) Support for two additional network adapter types:
        Intel(R) EtherExpress PRO, and
        Madge(R) Smart 16/4 Ringnode (token-ring).
  (3) Support for 3Com(R) EtherLink II(R) cards with new vendor ID 0020AF.
  (4) Support for 3Com 3Stations with new vendor ID 000062.

If you install a fresh copy of the Remoteboot service, you will already
have these improvements.  If you carry over your remoteboot database and
client files from version 3.5, you can add these improvements by using
the RPLUPD.BAT script in the CLIENTS\RPL\UPDATE subdirectory on the
Windows NT Server compact disc.  This will not interfere with your existing
profiles and workstations.  Make sure you have a backup copy of your
remoteboot database files before running RPLUPD.BAT.


5.  Special Considerations for Specific Network Adapters and Windows 95
-----------------------------------------------------------------------
The following sections describe considerations for specific network adapter
types.


5.1  Western Digital(TM)/SMC EtherCard(TM) Plus (8000 series)
-------------------------------------------------------------
In the client's machine directory, add a line of the form
	EMMExclude=CC00-CFFF
(using the appropriate exclusion range for your SMC8000 configuration)
to the [386Enh] section of SYSTEM.INI.


5.2  Novell NE2000 and Intel EtherExpress PRO
---------------------------------------------
The Windows 95 Setup program can fail to autodetect the Novell NE2000
and Intel EtherExpress PRO network adapters in a remoteboot environment.
You may have to add the network adapter information manually.


5.3  AMD Series 2100 Ethernet
-----------------------------
The Windows 95 Setup program can stall for lengthy periods (20 minutes
or more) when the client boots from an AMD Series 2100 Ethernet network
adapter.  Wait for the Setup program to continue.


6.  Troubleshooting Remoteboot Problems
---------------------------------------
The main Remoteboot documentation contains some basic troubleshooting
tips.  The following sections contain more advanced tips, in particular
tips on installing and running Windows 95 on remoteboot clients.  These
suggestions are divided into sections according to when the problem
occurs; for example, if you are having trouble running Windows 95 Setup,
see the section titled "Troubleshooting Problems Running Windows 95 Setup."


6.1 Troubleshooting Problems Booting MS-DOS
-------------------------------------------
PROBLEM: The Remoteboot service displays the following error when starting:
	"Error 0193: %1 is not a valid Windows NT application."
RESPONSE: Check whether you installed the Remoteboot service
binaries for the wrong platform (e.g. you installed Intel
x86 binaries for a MIPS server).

PROBLEM: You see the following error while booting MS-DOS:
	"NetUseAdd() returns 5."
RESPONSE: Run "Fix Security" from Remoteboot Manager.

PROBLEM: You see the following error while booting MS-DOS:
	"NetWkstaSetUID2() returns 5."
RESPONSE: The domain is probably misconfigured.  You may have attempted
to move a server from one domain to another simply by changing the domain
name on the server; you must reinstall Windows NT Server to move a server
to another domain.


6.2 Troubleshooting Problems Running MS-DOS
----------------------------------------
PROBLEM: An MS-DOS command (for example, DELTREE) displays an error on the
MS-DOS client about invalid directory structure.  Or, "." and ".." are
missing from the output of the DIR command.
RESPONSE: This is a known bug in Windows NT 3.51 Service Pack 1 on the
remoteboot server, and in pre-release versions of Service Pack 2.
Upgrade to the released version of Service Pack 2 or higher.


6.3 Troubleshooting Problems Running NETSETUP
-----------------------------------------------------
PROBLEM: NETSETUP fails to set up the SBS share, possibly displaying
an error about failure to write MSBATCH.INF.
RESPONSE: NETSETUP only works properly when run from Windows 95; it will
encounter errors when run from Windows NT.

PROBLEM: While setting up a subsequent Windows 95 client, you see an
error message about creating the machine directory.
RESPONSE: Check that the directory was created and that it contains
several files; if so, then disregard the error message.


6.4 Troubleshooting Problems Running Windows 95 Setup
-----------------------------------------------------
PROBLEM: NET USE displays error 71 while attempting to map a drive letter
to the SBS shared directory or to the shared directory on which you
intend to place the client's machine directory.
RESPONSE: Check that you have enough client licenses on the server
to support the number of clients connecting to the server. Use Licensing
in the Control Panel to see the maximum number of clients. You can see
the number of current clients by clicking Server in the Control Panel
and then clicking Users, or by typing NET SESS at a command prompt.
Remoteboot clients cannot boot from a server with only one concurrent
connection.

PROBLEM: The client doesn't have enough memory to run Windows 95 Setup.
RESPONSE: You may need to load EMM386.EXE in the client's MS-DOS profile
to save enough conventional memory to run Setup.  In the
RPLFILES\PROFILES\<profilename> directory, edit the CONFIG.SYS file
to run EMM386.EXE without any parameters.  You may find that NET START RDR
fails if you include the NOEMS or X=xxxx-9FFF parameters with EMM386.EXE.
See the section "Configuring Memory for Windows" in the Remoteboot chapter
of the Windows NT Server Installation Guide.

PROBLEM: Windows 95 Setup displays the following error message:
	"Cannot create a file in the temporary directory."
RESPONSE: By default, Windows 95 Setup creates a temporary directory in
the PROFILES\[profile] directory on the remoteboot server.  If you are
logged on using an account that does not have write permission in that
directory, you will not have permission to create that directory.  Instead,
run "SETUP /T:<pathname>" to change the location where Setup will create
the temporary directory, where <pathname> is on the mapped drive with the
client's machine directory, or somewhere else where you have write permission.

PROBLEM: Windows 95 Setup hangs while displaying the following message:
	"Please wait while Setup initializes."
RESPONSE: Use the SETUP /T:<pathname> parameter as described above.

PROBLEM: Windows 95 Setup does not present the option of setting up
for a remoteboot client.
RESPONSE: WIN95SRV.BAT should have replaced the MSBATCH.INF file on the
SBS server.  Check that the MSBATCH.INF file contains the lines
"DisplayWorkstationSetup=1" and "RplBootDrv=C".  If it does not, retry
WIN95SRV.BAT.  There are other important changes to MSBATCH.INF besides
these, so make sure you get the entire new file.

PROBLEM: Windows 95 Setup displays the following error message:
	"Windows 95 Setup: Setup Error B1:  Setup has detected
	an 80386 processor that is not compatible with this
	version of Windows."
RESPONSE: The B1 stepping of the 80386 microprocessor is not compatible
with Windows 95, on remoteboot clients or otherwise. You cannot remoteboot
this client with Windows 95.

PROBLEM: Windows 95 Setup displays the following error message:
	"Invalid CONFIG.SYS: Your multi-boot CONFIG.SYS seems to
	be invalid..."
RESPONSE: You have a local hard drive with files that Setup interprets
as boot files.  Ignore this message and continue.

PROBLEM: Windows 95 Setup displays the following error message:
	"Warning SU-0016 Setup has detected OS/2 files on your computer..."
RESPONSE: You have a local hard drive with files that Setup interprets
as OS/2 files.  Ignore this message and continue.

PROBLEM: Windows 95 Setup crashes during network adapter detection.
RESPONSE: This is a known problem with NE2000 and Intel EtherExpress PRO
network adapters.  Retry Windows 95 Setup, and when you trim the list of
devices to be detected, remove all network adapters.  Add the adapter
manually if detection misses your network adapter; be sure to set the IRQ,
I/O etc. settings for your adapter, and be sure to add the NetBEUI
protocol.  You may experience delays of several minutes while adding the
adapter manually in Windows 95 Setup.

PROBLEM: Windows 95 Setup displays a Network Information Required dialog.
RESPONSE: Sometimes Windows 95 Setup does not think it could autodetect
sufficient information about your network adapter, when in fact it did
obtain sufficient information.  You will not be able to boot the client
if you do not set up the adapter. Choose to continue setting up the
network adapter and check the default settings; they are probably correct.


6.5 Troubleshooting Problems Booting a Windows 95 Client
--------------------------------------------------------
PROBLEM: When you try to create a Windows 95 profile in Remoteboot Manager,
no Windows 95 configurations are listed.
RESPONSE: RBOOTSRV.BAT should have created them, so the problem might be:
  1. You did not run RBOOTSRV.BAT.
  2. When you ran RBOOTSRV.BAT, you did not have the Remoteboot
     service running on the remoteboot server.
  3. Something went wrong in RBOOTSRV.BAT so that
     RPLFILES\BINFILES\WIN95\COMMAND.COM was not copied.  Check that
     this file exists.  If it does not, then rerun RBOOTSRV.BAT.
  4. You did not run "Check Configurations" in Remoteboot Manager.

PROBLEM: WIN95CLT.BAT encounters errors.
RESPONSE: Check whether CONFIG.SYS and AUTOEXEC.BAT are present in the
SUBOOT subdirectory of the machine directory.  If not, move the
remoteboot client back to its DOS profile and reboot.  Check the clocks
on the remoteboot client and on the SBS server and the machine directory
server, and see whether they are substantially different. If so,
then synchronize the clocks and rerun Windows 95 Setup. If not,
contact technical support.

PROBLEM: The Windows 95 client fails to boot and displays a "file
creation error."
RESPONSE: Check  whether CONFIG.SYS and AUTOEXEC.BAT are present in
directory RPLFILES\PROFILES\<profile>\SUBOOT.  If not, rerun
WIN95CLT.BAT.  If those files are not in the SUBOOT subdirectory of
the machine directory, see above.

PROBLEM: The Windows 95 client fails to boot while the Windows 95 logo
screen is displayed.
RESPONSE: The logo screen hides the execution of the commands
in AUTOEXEC.BAT and WIN.BAT.  Disable the logo screen by adding
"Logo=0" to the [Options] section of
RPLFILES\PROFILES\<profilename>\SUBOOT\MSDOS.SYS.  Reboot and see which
command is failing, then see the troubleshooting information below.

PROBLEM: WIN.COM displays a message that the client does not have enough
extended memory.
RESPONSE: Check that the MSDOS.SYS file for this profile contains the line
"LoadTop=0" in the [Network] section.  If it does not, you probably did not
run WIN95SRV.BAT, since you failed to update MSBATCH.INF in the SBS directory.
You must run WIN95SRV.BAT and then rerun Windows 95 Setup.  If the LoadTop
line is already present, try adding the option /M:100 to the SNAPSHOT line
in WIN.BAT.  This changes the amount of memory that SNAPSHOT reserves for the
real-mode networking components.  You may have to experiment to find the
right amount of memory.

PROBLEM: The command setmdir /m /r:<path> fails.
RESPONSE: Press CTRL+C after this fails.  WIN95CLT.BAT should have copied
SYSTEM.DAT from <machine_directory>\SUBOOT to
RPLFILES\PROFILES\<profile>\SYSTEM32, and the client's AUTOEXEC.BAT should
have copied it to <RAMdrive>\WINBOOT on the client. If it is not there,
rerun WIN95CLT.BAT.

PROBLEM: You receive the following error message:
	"Error 28: The requested print job was not completed."
RESPONSE: Make sure that the client's WIN.BAT file contains the command
"setmdir /m /r:D:\WINBOOT" (where D: is the client's RAM drive) immediately
after the first "set comspec=" line. If the "setmdir /m /r:D:\WINBOOT"
command is not present, rerun WIN95SRV.BAT and check that it completes
successfully, then rerun Windows 95 Setup.

PROBLEM: The Windows 95 client hangs while running WIN.BAT after displaying
the network adapter type.
RESPONSE: Make sure that the WIN.BAT file contains the command "fixmem"
immediately after the "nwrpltrm" line.   If the "fixmem" command is not
present, rerun WIN95SRV.BAT and check that it completes successfully, then
rerun Windows 95 Setup.  You may also need to add a SNAPSHOT /M:xxx parameter
as described above.

PROBLEM: When WIN.BAT attempts to NET USE to the SBS shared directory, the
following error is displayed:
	"Error 58: This operation cannot be performed
	by the specified server..."
RESPONSE: Check whether the account to which you logged on has an expired
password or is otherwise unusable.

PROBLEM: The command setmdir (no /m or /r:<path>) fails.
RESPONSE: Make sure that the file MACHINES.INI in the SBS shared directory
contains lines like this:
        [02608C8EAA2D]
        SYSDATPATH=g:\client1
        g=\\mach_server\mach_share
where 02608C8EAA2D is the network adapter ID, g:\client1 is the machine
directory you entered while running Windows 95 Setup, and
g=\\mach_server\mach_share is the drive letter you mapped to the
shared directory where the machine directory resides.  You must use the
same drive letter which you used while running Windows 95 Setup.
The syntax must be exactly correct; check that SYSDATPATH is spelled
correctly and that you have not added a colon to "g=\\mach_server\mach_share".

PROBLEM: After AUTOEXEC.BAT and WIN.BAT finish running, the screen goes
blank and displays a message like the following:
	"VFBACKUP: Cannot load <filename>.VXD."
RESPONSE #1: If you added and configured the network adapter manually
during Windows 95 Setup, you should have confirmed the adapter's
resource settings.
To determine whether the adapter configuration is the problem:
1. Boot a Windows 95 client to command-line only (reboot,
   press F8 during the boot process, and choose option 6,
   Command-Line Only).
2. Set up a network connection to the shared directory containing the
   machine directory.
3. Change your current directory to the client's machine directory.
4. At the command prompt, type the following command:
	REGEDIT /L:.\SYSTEM.DAT /E .\SYSTEM.TXT
5. Edit the SYSTEM.TXT file.  Search for the following:
	HKEY_LOCAL_MACHINE\Root\Net\0000
   In this section, look for the ForcedConfig value.  If it is not present,
   rerun Windows 95 Setup and follow the instructions in the "Installing the
   First Windows 95 Client" section of Chapter 8 of the Installation Guide,
   in particular the instructions regarding confirming the resource settings
   for the adapter.
RESPONSE #2: Check that you ran RBOOTSRV.BAT and did not encounter any errors.
You may need to run this script again and then rerun Windows 95 Setup.

PROBLEM: After AUTOEXEC.BAT and WIN.BAT finish running, the screen goes
blank and displays a message like the following:
	"Error loading GDI.EXE.  You must reinstall Windows."
RESPONSE: Check that you are using a network adapter supported by the
Remoteboot service.

PROBLEM: After AUTOEXEC.BAT and WIN.BAT finish running, the screen goes
blank and displays a message like the following:
	"VFAT Device Initialization Failed."
RESPONSE: Check that you are using a network adapter supported by the
Remoteboot service.

PROBLEM: After AUTOEXEC.BAT and WIN.BAT finish running, the screen goes
blank and displays a message like the following:
	"VFAT & DOS volume in drive C: layouts are MISMATCHED."
RESPONSE: Contact technical support.


6.6 Troubleshooting Problems on a Windows 95 Client
---------------------------------------------------
PROBLEM: Windows 95 displays a warning about several files having been
replaced by older versions (possibly including dciman.dll, mcicda.drv, or
WINASPI.DLL).
RESPONSE: The warning is incorrect; the files were not replaced.
This warning may appear if you did not set permissions on the SBS
shared directory to "read only" for the account to which you logged on
for the Windows 95 client; fix the permissions and reboot.  This warning
may also appear for subsequent clients regardless of the shared directory
permissions.

PROBLEM: Windows 95 displays an error message about a sharing violation
accessing a system file.  You may also notice (if you are running
a network sniffer) that Windows 95 tried and failed to delete
COMMCTRL.DLL.
RESPONSE: You did not set permissions on the SBS shared directory to
"read only."  Fix the permissions and reboot.

PROBLEM: Windows 95 displays an error message about failure to access
drive A:.
RESPONSE: This is a known issue with some remoteboot workstation
BIOSes, in particular the HP Windows Client BIOS.  Ignore the error
message.

PROBLEM: Windows 95 displays a warning that the client has a virus.
RESPONSE: See the next item on the System Properties Performance tab.

PROBLEM: The System Properties Performance tab shows problems.
RESPONSE: You may see one of the following messages:

	"Compatibility mode paging reduces overall system performance."
	This is normal for a remoteboot client.

	"Master Boot Record modified -- SEE IMPORTANT DETAILS."
	The concern about a virus is almost certainly a false alarm.

PROBLEM: You want to modify EMM386 parameters but there is no EMM386
line in the client's CONFIG.SYS file.
RESPONSE: EMM386 is loaded in Windows 95 by default.  If you wish to
modify EMM386 parameters, in RPLFILES\PROFILES\<profile>\SUBOOT\CONFIG.SYS,
add a line of the form
	device=c:\win95\emm386.exe Y=e:\emm386.exe
where e: is the drive that will be connected to the SBS shared directory.
Alternatively, to exclude memory ranges for EMM386, you can add a line of
the form
	EMMExclude=CC00-CFFF
(using the appropriate exclusion range for your network adapter
configuration) to the [386Enh] section of SYSTEM.INI in the client's
machine directory.

PROBLEM: You are using the SBS administrative program (NETSETUP.EXE) to
install a subsequent Windows 95 client, and the "Add" button is not enabled.
RESPONSE: You must first click the Set Path button to specify the location
of an SBS Windows 95 shared directory, and this shared directory must contain
the NETSETUP.POL file at the top level (the file may be marked Hidden). You
must have read and write access to the shared directory, since NETSETUP will
want to update NETSETUP.POL.

PROBLEM: You are using the SBS administrative program (NETSETUP.EXE) to
install a subsequent Windows 95 client, and NETSETUP displays the error
	"Error creating the directory."
RESPONSE: If the directory was created and a few files are present in it, then
ignore the error message.

PROBLEM: When you modify the network configuration of a running Windows 95
remoteboot client (for example, adding TCP/IP support), it attempts to copy
files to drive A:.
RESPONSE: Windows 95 Network Setup does not work perfectly with remoteboot
clients.  If you skip the files which Setup is trying to copy to drive A:,
the new component should work.
