Microsoft(R) Windows NT(TM) Server RemoteBoot Service for Windows 95(TM) Beta
(Please see instructions below to submit this report)

Name                           :
Company                        :
Area Code & Phone              :
CompuServe ID                  :
Internet Address               :
Country (if outside the U.S.)  :
Language Version               :


***** PROBLEM INFORMATION ******
Problem Title:

Previous OS:

Classify the Problem:

< > Failure to boot DOS 6.x
< > Problem running NETADMIN.EXE
< > Problem running Windows setup from DOS 6.x
< > Problem preparing profile to boot Windows 95 RPL client
< > RPL client does not boot Windows 95 the first time
< > Problem during the first boot of Windows 95
< > RPL client does not boot Windows 95 subsequently
< > Problem while Windows 95 is running on client
< > Other

Problem Description  :





Step by step instructions that will allow us to reproduce the problem here:
  1.
  2.
  3.
  4.
  5.
  6.
  7.
  8.

Work-around:


Reproducible  :< >Always < >Sometimes < >Never < >Didn't try it again


****** WIN95 CLIENT INFORMATION ******

****** NETWORK CONFIGURATION ******
Network card type, IRQ & address:
Boot PROM type / manufacturer   :                 version/date:
Network type                    :
Network protocol                :                 version:
Network cabling                 :


**** BASIC CONFIGURATION ****
Computer brand & model(check all that apply):
 < >ISA < >EISA < >MCA < >VESA < >PCI
 < > PCMCIA (PC CARD) < >Other:
System BIOS (manufacturer & version/date)   :
Memory (RAM)                                :
Mouse model & type (serial/bus) (COM/IRQ)   :
Multimedia hardware (model/address/IRQ)     :
Multimedia drivers                          :
Communications Modem (model/address/IRQ)    :
Serial Adapter (if used)                    :
X.25 Adapter (if used)                      :
Other adapters (scanner/printer/PC CARD)    :



****** WINDOWS NT SERVER INFORMATION ******
(Note - this section is for the server running the remoteboot service.)


Product Release      :
	Type "winver" at the command line while Windows NT is running.

Install Method       : < >CD-ROM < >Floppy
                       < >WINNT.EXE (Over the Network from MS-DOS)
                       < >WINNT32.EXE (Over the Network from Windows NT)

Install Type         : < > Upgrade from Windows NT 3.1
                       < > Upgrade from Windows NT 3.5
                       < > Clean Install

Previous OS          :

Remoteboot service install type:
 < > Clean install
 < > Copied database and client files from earlier NT
 < > Upgraded from LM2.x

Ran RBOOTSRV.BAT to update remoteboot service files:
 < > Yes
 < > No

Ran WIN95SRV.BAT to update Windows 95 server-based-setup tree:
 < > Yes
 < > No

**** BASIC CONFIGURATION ****

Computer brand & model(check all that apply):
 < >ISA < >EISA < >MCA < >VESA < >PCI
 < >RISC < > PCMCIA (PC CARD) < >Other:
System BIOS (manufacturer & version/date)   :
CPU(s) (type, speed and manufacturer)       :
Memory (RAM)                                :
Mouse model & type (serial/bus) (COM/IRQ)   :
Multimedia hardware (model/address/IRQ)     :
Multimedia drivers                          :
Communications Modem (model/address/IRQ)    :
Serial Adapter (if used)                    :
X.25 Adapter (if used)                      :
Other adapters (scanner/printer/PC CARD)    :

****** FILE SYSTEM CONFIGURATION ******

File system of partition for NT remoteboot files:  <> FAT  <> NTFS


****** NETWORK CONFIGURATION ******
Network card type, IRQ & address:
Network type                    :
Network protocol                :       version:
Network cabling                 :
LAN or WAN                      :
If Wide Area Network, please specify all routers or bridges used:


Additional Comments:
(Please include the version number(s) of any software application(s)
referred to this in problem report.)


How To Submit This Report
=========================
Please e-mail this form to rplbug@microsoft.com.  Please send mail to
ntbug@microsoft.com if you require an ftp location, or have any other
questions or comments regarding the problem report process.