Table of Contents
   I)    Patch ID
   II)   Warnings and Caveats
   III)  What's new
   IV)   Patch Installation Instruction
   V)    Gigabit Ethernet Support Notes
   VI)   SAN Support Notes
   VII)  Defects Resolved

----------------------------------------------------------------------------
I)   Patch ID

   Patch ID: 4.5.0-004

   Targeted Versions: Bare Metal Restore 4.5.0 for NetBackup

   Platforms: AIX, HP-UX, Solaris, Windows NT, Windows 2000

   This patch contains all of the fixes in the earlier patches
   (4.5.0-003 through 4.5.0-001). It may be applied on top of any of
   the earlier patches, or on a base 4.5.0 system.

----------------------------------------------------------------------------
II) Warnings and Caveats
   
   a) This patch should be installed on all BMR servers. Install the
      patch on the BMR Main server first, and then on the BMR File
      servers and BMR Boot servers in any order. The BMR Clients should
      be patched as needed only after upgrading all of the BMR servers.
      Patched BMR Servers can support unpatched BMR Clients.

      This installation order is different from earlier BMR patches.

      Once the BMR servers are upgraded to patch 4.5.0-003 or above, any
      BMR client running Windows 2000 that is not upgraded to
      patch 4.5.0-003 or above and that is also running NetBackup 3.4 or
      3.4.1 MUST make one manual configuration change every time after
      that client is successfully restored. If the Windows 2000 BMR client is
      running patch 4.5.0-003 or above, or the NetBackup version is later
      than 3.4.1, then this manual step is not necessary.  See TechNote
      http://seer.support.veritas.com/docs/251569.htm for more details.

         Manually create the directory pointed by the system's global
         variable TEMP or TMP after first BMR restoration and before
         any further incremental backups are performed. Make sure to
         use the TEMP or TMP variable for the SYSTEM rather than the
         TEMP or TMP variables for the USER.


   b) On systems running with low memory conditions, the patch process
      may take up to 30 minutes to complete.


   c) WARNING: While applying this patch to BMR main servers on HP
      platforms that are running patch 4.5.0-001, you may see the
      following error message:
            mv: hp/bmrd: cannot write: Text file busy
      In order to apply the new version of bmrd that is a main component
      of this patch you must run bmrpatchserver again. This will apply
      the patch for the second time and replace the bmrd as needed.


   d) On AIX platforms you may be asked the following question:
             override mode 755 on aix/bmrd?
      You should answer yes to this question.


   e) After patch 4.5.0-002 or above has been applied on Windows NT or
      Windows 2000 clients running base BMR 4.5.0 or 4.5.0-001, the following
      message will be displayed.
           "Patch 4.5.0-001 has been successfully applied."
      If any BMR patch is applied on top of 4.5.0-002, then the correct
      patch ID will be displayed.


   f) When creating the first boot floppy on Windows NT or Windows 2000
      clients after patch 4.5.0-003 or above has been applied, a screen
      will display the message:
          "You need the MS Client Software from Microsoft.  You can
           download it from the following link.  
              ftp://ftp.microsoft.com/BusSys/Clients/MSCLIENT/

      These files need to be downloaded from the specified site and
      the downloaded file location pointed to by the boot floppy creation
      wizard.  This procedure is described in the "Creating Boot Images
      (Floppies) for Windows Clients" section of the new User's Guide which
      is installed with patch 4.5.0-002.


   g) Boot floppies created after the installation of patch 4.5.0-003
      or above should be removed from the floppy drives only when prompted.  
      If they are ejected part way during the restore operation they
      cannot be used to restore other systems.


   h) When applying patch 4.5.0-001 or above on a BMR Server before
      bmrsetupserver has been executed, the message:
          "Could not restart BMR server daemon."
      will be displayed.  In this situation, this is an erroneous error
      message.  The application of the patch was actually successful.


   i) BMRserver has a prerequisite for the libucb.so library that is
      installable using the SUNWscpu package that comes with the
      Solaris OS CD. If not installed, when running bmrsetupserver, bmrd
      may fail to start and a message may be logged in /var/bmr/log/bmrd.err
      indicating libucb.so could not be found.  BMRserver uses the libucb.so
      library which is installable using the SUNWscpu package. Once installed,
      bmrsetupserver and bmrd should work normally.


   j) During client restorations, error messages may be logged indicating
      that some NetBackup files could not be moved.  On a Windows 2000
      restore, for example, the message would be similar to:
          "ERR: Failed to move C:\BMR\NBU\bin\BPJAVA~2.EXE to
           C:\BMR\NBU\bin\bpjava-usvc.exe--gle(2)."
      These messages are harmless and can be ignored.

   k) Media Boot is only supported on AIX versions 4.1, 4.2, and 4.3.3.
      When using Media Boot on AIX 4.3.3, do not use AIX installation
      CD's dated 9/2001 or later.

   l) Patch 4.5.0-003 and above contains a fix for the problem with the
      creation of media boot CDs when using Solaris 7 or Solaris 8 SRTs
      that contain the VERITAS Volume Manager (VxVM) software or the
      VERITAS File System (VxFS) software installed in them.

      As a result, the fix also introduces a change to the prompts output by
      the 'bmrmkcdimage' command. Prior to this fix, 'bmrmkcdimage' would not
      require a free partition or disk group name unless the SRT has the VxVM
      or VxFS software installed in it. With this fix, irrespective of
      whether the VxVM or VxFS software is installed in the SRT, a new prompt
      will appear.

      If the file server has the VxVM software installed on it, the
      following prompt will appear:

            Enter the name of a Disk Group with nnnnnMB or more free space:

      If the file server does not have the VxVM software installed on
      it, the following prompt will appear:

            Enter the name of a Partition of size nnnnnn or more blocks:

   m) When a BMR Windows client with an LSI Logic Integrated Ultra ATA 100
      IDE Raid Controller tries to boot from a BMR boot floppy, it may
      display the fatal error message "Divide Overflow" and hang at
      PC DOS start-up.
      Solution:
          Edit config.sys file on the BMR boot floppy and remove
          the following line
          "DEVICE=A:\BIN\EMM386.EXE i=B000-B7FF NOEMS"

   n) BMR 4.5.0-004 is required for running with NetBackup 4.5 FP3.  
      Do not apply this patch if you are using NetBackup 4.5 FP3 until
      you have read and understood the information in TechNote
      http://seer.support.veritas.com/docs/253582.htm.
      BMR clients using Windows NT should pay special attention to this
      TechNote.  

      Of particular note is that all Windows NT clients using any version
      of NetBackup will fail to restore using an SRT containing NetBackup
      4.5 FP3 unless the special procedures documented in the TechNote
      are used. This NT client issue requires that Setup Client be rerun and
      the "Service Pack required" option be selected after this BMR patch is
      applied for all such NT clients. This will ensure that enough space
      is reserved for the service pack needed to use NetBackup 4.5 FP3
      at restore time. The amount of space needed for a service pack
      increased from 313MB to 350MB in BMR 4.5.0-004 to handle the
      new requirement.

      Also to be noted is that any BMR client using Solaris 8 must apply an
      updated NetBackup bpbkar binary on top of NetBackup 4.5 FP3. NetBackup
      customer support must be contacted to obtain this binary.  Without this
      binary, BMR restorations will fail for Solaris 8 clients.  For
      details regarding this issue, see TechNote 254496 at
      http://seer.support.veritas.com/docs/254496.htm.  Should a problem with
      BMR restore be encountered before an updated bpbkar is applied, contact
      BMR customer support for a workaround for this issue.


   o) Any Windows NT client that selected the "Need Service Packs" option
      during bmrsetupclient, regardless of the BMR patch level, may
      need to take an additional step to allow successful restoration.

      .  If the Service Pack option was selected, and is truly needed, both
         the BMR main server and the Windows NT client must be upgraded to
         BMR 4.5.0-004 and the Windows NT client must rerun bmrsetupclient.  

      .  If the Service Pack option was selected, but is not truly needed,
         just do not click on the Service Pack option during Prepare to
         Restore.

   p) After creating a boot floppy on a Windows 2000 client, when bmrsavecfg
      is run without a CD in the CD-ROM drive, a popup message may appear
      requesting that a CD be placed in the drive.  Placing any CD into the
      drive and clicking OK will allow bmrsavecfg to complete successfully.
      Note that the automatic execution of bmrsavecfg during backups will
      not generate this popup message.

----------------------------------------------------------------------------
III)  What's new

   4.5.0-004

   Any Windows NT client that selected the "Need Service Packs" option
   during bmrsetupclient, regardless of the BMR patch level, may
   need to take an additional step to allow successful restoration.
   .  If the Service Pack option was selected, and is truly needed, both
      the BMR main server and the Windows NT client must be upgraded to
      BMR 4.5.0-004 and the Windows NT client must rerun bmrsetupclient.  
   .  If the Service Pack option was selected, but is not truly needed,
      just do not click on the Service Pack option during Prepare to Restore.

   This patch is required for running with NetBackup 4.5 FP3.  

   Do not apply this patch if you are using NetBackup 4.5 FP3 until you have
   read and understood the information in TechNote
   http://seer.support.veritas.com/docs/253582.htm.
   BMR clients using Windows NT should pay special attention to this
   TechNote.

   Of particular note is that all Windows NT clients using any version
   of NetBackup will fail to restore using an SRT containing NetBackup
   4.5 FP3 unless the special procedures documented in the TechNote
   are used. This NT client issue requires that Setup Client be rerun and
   the "Service Pack required" option be selected after this BMR patch is
   applied for all such NT clients. This will ensure that enough space
   is reserved for the service pack needed to use NetBackup 4.5 FP3
   at restore time. The amount of space needed for a service pack
   increased from 313MB to 350MB in BMR 4.5.0-004 to handle the
   new requirement.

   Also to be noted is that any BMR client using Solaris 8 must apply
   an updated NetBackup bpbkar binary on top of NetBackup 4.5 FP3. NetBackup
   customer support must be contacted to obtain this binary.  Without this
   binary, BMR restorations will fail for Solaris 8 clients.  For
   details regarding this issue, see TechNote  254496 at
   http://seer.support.veritas.com/docs/254496.htm.  Should a problem with
   BMR restore be encountered before an updated bpbkar is applied, contact
   BMR customer support for a workaround for this issue.

   A security update has been included with this patch.  See TechNote
   http://seer.support.veritas.com/docs/252688.htm for more details.

   This patch also fixes a problem with the automatic bmrsavecfg during
   backups of Windows clients. See TechNote
   http://seer.support.veritas.com/docs/252682.htm for more details.

   This patch also fixes problems extending OEM partitions with RAID
   controllers.

   4.5.0-003

   In addition to a number of general fixes, a data corruption problem for
   Windows machines was resolved with this patch.  See TechNote
   http://seer.support.veritas.com/docs/251487.htm for additional details.

   This patch fixes the problem with the creation of media boot CDs when
   using Solaris 7 or Solaris 8 SRTs that contain the VERITAS Volume
   Manager (VxVM) software or the VERITAS File System (VxFS) software
   installed in them.

   4.5.0-002

   In addition to containing fixes for the defects (bugs) listed
   in section 7, this patch adds support for Gigabit Ethernet
   devices, and allows for SAN co-existence on UNIX clients. Windows
   SAN co-existence enters Beta with this patch, and will GA in the
   follow-up patch. Refer to sections 5 and 6 for a description of
   these new features.

   4.5.0-001

   This patch contains general fixes.
----------------------------------------------------------------------------
IV) Patch Installation Instruction

   Installation Instructions:

   On AIX, HP-UX and Solaris platforms:
       1.  Download the patch file from
           http://support.veritas.com/menu_ddProduct_BMRNBU.htm
       2.  To apply the downloaded patch to a BMR server machine execute:
           $BMRDIR/bmrpatchserver -f <patch_file>
           where patch_file is the location of the downloaded patch file.
       3.  To apply the downloaded patch to a BMR client machine execute:
           $BMRDIR/bmrpatchclient -f <patch_file>
           where patch_file is the location of the downloaded patch file.

   Note:  On systems which have both Bare Metal Restore server and Bare
   Metal Restore client software installed, the patch must be
   applied to the server setup before being applied to the client
   setup.


   On Windows NT and Windows 2000:
       1.  Download the patch file from
           http://support.veritas.com/menu_ddProduct_BMRNBU.htm
       2.  To apply the downloaded patch run the bmrpatch utility from
           %BMRDIR%.
       3.  In the first screen displayed, type in the location of the patch
           file in the patch file text edit box or select the patch file by
           using the "Browse" dialog.  Click "Next".
       4.  In the subsequent screen click "Next" to begin application of the
           patch.
       5.  After patch application is completed, the "Finish" button will be
           enabled.  Click "Finish" to exit the patch utility.


----------------------------------------------------------------------------
V) Gigabit Ethernet Support Notes

   Gigabit Ethernet support is now available for Windows 2000, Windows NT,
   Solaris and AIX.

   Solaris
     Recent versions of the Solaris 8 OS CD have built-in support for two Sun
     gigabit Ethernet adapters: the "Sun Gigabit Ethernet 2.0/P adapter",
     supported by the SUNWged driver package, and the "Sun GigaSwift Ethernet
     Adapter", supported by the SUNWced* driver packages. Accordingly, a
     Solaris 8 SRT built from a recent Solaris 8 OS CD will also have
     built-in support for the adapter, and hence those Solaris 8 SRTs do not
     require any additional packages for the purpose of using these adapters
     during restores. Check for the existence of the package directories in
     $SRTpath/Solaris_*/Tools/Boot/var/sadm/pkg where $SRTpath is the location
     where the SRT is stored. If present, support is included.

     For Solaris 2.6, 7, and earlier versions of Solaris 8, there is no
     built-in support for either adapter, but installing driver packages
     will provide it. For the "Sun Gigabit Ethernet 2.0/P adapter use the
     package called "SUNWged". For the "Sun GigaSwift Ethernet Adapter" on
     Solaris 2.6 or 7 use the "SUNWced.u" package, and on the older versions
     of Solaris 8 use the "SUNWced.u" and "SUNWcedx.u" packages. (These
     packages are available on the CD that accompanies the adapter or
     from Sun). Install the package(s) into the SRT when the SRT creation
     process prompts for additional packages/patches. Note that due to the
     SUNWced.u and SUNWcedx.u packages internally referencing SUNWced and
     SUNWcedx instead of SUNWced.u and SUNWcedx.u, you may see a message:
         ERROR: information for "SUNWced.u" not found.
     or
         ERROR: information for "SUNWcedx.u" not found.
     This is a result of the package definition name variance and is harmless.

   AIX
     AIX clients can use gigabit ethernet adapters at restore time as long
     as the adapter can be used for network booting. In other words, if
     the gigabit adapter is recognized by the boot prom as one of the
     devices that can be used for network booting, BMR can use that
     interface to restore the client.

   Windows
     On Windows2000 and WindowsNT clients, no additional steps need to be
     taken to make use of the gigabit ethernet adapters during restores.
     The only thing that is required is a DOS (NDIS2) driver for the adapter,
     which should be made available to the BMR during boot floppy creation
     process.

   Known issues with Gigabit Ethernet Support:

     On Solaris, the BMR MediaBoot feature, can only be used with Gigabit
     Ethernet adapters if the Operating System CD  used to build the SRT
     had Gigabit adapter support builtin. Solaris 6, 7 and early versions
     of Solaris 8 may not contain the builtin support.


----------------------------------------------------------------------------
VI)  SAN Support Notes

   SAN co-existence
   
     SAN co-existence is now available for, Solaris, AIX and HP-UX.

     SAN co-existence is considered Beta for Windows2000, and WindowsNT. A
     specific action is required in order to enable the new Windows SAN code.
     This is expected to GA in the follow on patch.  The Beta code addresses
     a potential problem that can occur during the DOS phase of a restore.
     If the computer being restored has SAN disks that DOS can see then the
     disk numbering may prevent a correct restore.  The Beta code will allow
     you to correct this.

     If DOS cannot see the SAN disks then you do not need the Beta code and
     SAN co-existence will work on Windows2000 and WindowsNT with this patch.


   What does SAN co-existence mean?
   
     SAN co-existence means that a system with fibre-channel attached disk devices
     can be restored using BMR. BMR will restore any volumes on the internal
     (non fibre attached) SCSI disks. Any volumes on SAN attached disks will need
     to be recovered through manual recovery procedures after BMR is used to
     restore the system.
   
     With BMR there are two options to restore a system that has SAN attached
     devices. The first option is to do a system only restore. To achieve this
     in the "Prepare to Restore" window under "Restore Options" you would select
     "Only system disks/volumes". On AIX and HP-UX this will restore the root
     volume groups (rootvg and vg00 respectively). On Solaris this will restore
     all disks that have any of the root filesystems (/, /tmp, /var, /usr). On
     Windows 2000 and NT this will restore all disks that have %SystemRoot%,
     %SystemBoot%, and %TEMP%.
   
     The second option is to restore the entire system. To achieve this in the
     "Prepare to Restore" window under "Restore Options" you would select
     "All disks/volumes". Please note that for SAN attached systems this
     selection should be made with caution. If the HBA drivers and their


     configuration is not available in the SRT, BMR will not be able to
     restore the entire system. In these cases BMR will restore volumes
     on all internal disks and will not restore the SAN devices. On Windows
     platforms the SAN driver will be in the SRT and an attempt will be made
     to restore the SAN drives.
   
   SAN support matrix
   
     The following support table shows the HBAs and operating platform that
     can co-exist with BMR. Meaning the system (internal) drives can be
     restored followed by a manual restore of the SAN drives as outlined
     above.
   
   OS              Qlogic  Emulex  JNI        Cambex    IBM       HP
                   2200    LP8000  FCI-1063   PC1000    6228     A5158A
   ---------------------------------------------------------------------
   Solaris       |   x   |   x   |     x    |        |        |        |
   HP-UX         |       |   x   |          |        |        |    x   |
   AIX           |       |   x   |          |   x    |    x   |        |
   Windows2000   |   x   |   x   |          |        |        |        |
   WindowsNT     |   x   |   x   |          |        |        |        |
   
   
   Manual Recovery of other volumes
   
     After an AIX system is recovered using the "Only system disks/volumes"
     option you may need to perform these steps for the SAN attached volumes.
   
     % redefinevg -d <device> <vgname>
     % varyonvg <vgname>
     % synclvodm <vgname>
   
     After a SAN attached HP-UX system is restored the following steps need
     to be performed to recover the SAN attached volumes.
   
     % vgimport -v <vgname> <pvpaths>
     % vgchange -a y <vgname>
   
     At this point the file systems that were on the SAN devices are ready
     to be mounted. Manual steps can be taken to restore these file systems
     using NetBackup.
   
   Other requirements:
   
     In SAN environments BMR requires the use of persistent bindings. The HBA
     driver configuration files might need to be modified to bind specific
     devices on the SAN to specific targets on the hosts.
   
   Known issues with SAN co-existence:
   
     On AIX, the use of the IBM 6228 HBA requires the use of drivers that were
     supplied with the HBA.
   
     On SAN attached AIX systems, bmrsavecfg might produce warnings, if the SAN
     attached volumes are not available. These warnings need to be investigated
     as they might lead to BMR not being able to restore the SAN attached volumes.
     It is highly recommended that bmrsavecfg be re-run after correcting the
     conditions that caused the warning.
   
     On Solaris, the use of the Qlogic 2200 HBA means that the drivers for this
     HBA should NOT be added to the SRT. Some Sun hardware comes with built-in
     Qlogic SCSI adapters and the Qlogic 2200 HBA driver is known to conflict
     with them.
   
   
   
----------------------------------------------------------------------------
VII)  Defects Resolved


   CaseID            Defect     Abstract
   ------------    ------  --------------------------------------------------------------

   Defects resolved by patch 4.5.0-004

   140-525-774     12052   TESTWINSAN: Failed to extend oem partition with RAID
   N/A             12143   security update
   100-279-300     12176   Win: bpstart_notify does not run bmrsavecfg
   N/A             12439   FP3 requires SRT with Service pack installed

   Defects resolved by patch 4.5.0-003

   100-276-422     9087    TESTSOLMB: Veritas VM support runs out of disk space in Sol 7+8
   100-277-298     11671   WIN:if format command fails, still continues
   100-277-294     11718   NBU media server can not handle unresolved names in bp.hosts  
   100-269-846     11748   WIN2K-genericfloppy protocol.ini netflex name incorrect        
   140-474-537     11766   WIN - emulex drivers have elxcfg.lnk listed as a source file  
   N/A             11809   WIN: Make setup MSD installation similar to NICs              
   N/A             11898   TEST2000NBUSAN: ALL-DISKs restore hang on formatting drives    
   N/A             11941   NBURename file does not match NBU copied files                
   100-276-763     11952   NT:Restore returning continual "Out of Virtual Memory" messages
   100-277-342     11960   unable to handle preceding partitions with greater offset value
   N/A             11964   Down level client won't work with higher level server          
   N/A             11983   TEST2000NBU: Registry does not backup after BMR restore        
   N/A             11984   WIN: rename.ini contains file names that don't need renaming.
   N/A             12027   bmrpatch does not update old SRT's.
   N/A             12080   TESTSOLNBUDDR: trivial restore does not work: missing vfstab.

   Defects resolved by patch 4.5.0-002

   N/A             11450   SOL: attempt to format ALL attached drives
   N/A             11563   cannot reach host error because of disabled ping
   N/A             11639   HPDDR: only vgroot(primary volume group) was shown.
   N/A             11642   HPDDR: vgcreate failed by not enough physical extents.
   N/A             11643   AIX: client boots, but hangs after tftp and kernel start
   N/A             11644   enhance bmrc -v to show patch information
   N/A             11661   2000: Teaming NIC causes problems
   N/A             11663   HPSOL: clear text of hp/bmr_mkboot.bmr also present
   N/A             11669   HP:Restore fails if HP client has an extened swap
   N/A             11694   NBU: bmrrst fails to rename netbackup.dll
   N/A             11697   BMR/TSM SOL createBI fail error code 22
   N/A             11709   patch process is using # to comment out lines in inittab
   N/A             11722   DDR GUI screen says Mutli-select instead of Multi-select.
   N/A             11727   WIN:p2r restriction should be on Media Boot clients only
   N/A             11750   Boot Options Wizard fails if P2R is not done on any clients
   N/A             11763   Missing atapi.sys & intelite.sys in server setup.
   N/A             11791   AIX: bmcreatesrt offers default OS level as '50'.
   N/A             11799   HP: BMR dies on non-default swap space on raw LVs.
   N/A             11800   Filesystem on non-system disk created but not restored.
   N/A             11805   bmr_mkfs error after changes in bmrmap GUI.
   N/A             11814   Restoration stops after retrieve bmrcli.dat.
   N/A             11819   HP: Volume group not imported.
   N/A             11824   Fileserver connects to itself if can't ping master server.
   N/A             11832   Place the warning for bmrd overwrite in README.
   N/A             11833   AIX restore hangs with LED 608.
   N/A             11834   Remove warning messages from bmrrst.exe.
   N/A             11837   No filesystems were restored on AIX.
   N/A             11841   Restore script is no longer logged to main server.
   N/A             11842   listfile has enddate before startdate.
   N/A             11844   sd.conf not present, prevents disk use.
   N/A             11845   Document restriction for IBM 6228 HBA driver.
   N/A             11861   SRT changes cause strange errors in restores.
   N/A             11863   Solaris 7 fails to find new disk targets.
   N/A             11864   HP: /dev/vg00.prebmr was displayed on map GUI.
   N/A             11876   DDR restore failed at partitioning disks.
   N/A             11877   HP: Unable to create pv on bigger hard disk.
   N/A             11879   Document that DOS floppy cannot be ejected until prompted.


   Defects resolved by patch 4.5.0-001  (These defects are also include in patch 4.5.0-002)


   N/A             11080   HP: if vg00 doesn't exist createBI will fail
   N/A             11205   GUI: Save button in client screen causes PTR
   N/A             11235   WIN2K: Can't browse on SRT creation wizard window.
   N/A             11308   UNIX-PtR Should error out if some listfile values are NULL
   N/A             11359   BootLater option goes back to p2r instead of clients
   N/A             11394   NTDDR: 1st logical drive of extended partition not
   N/A             11396   HP:after only system restore,2nd vg was not imported
   N/A             11400   bail ERROR: cannot find a physical volume at location...
   N/A             11409   AIXGUI: garbage characters in PTR OK display
   N/A             11457   NT: savecfg failed to load MSD info.
   N/A             11459   GUI: NetBackup Servers letters shifts when hi-lited.
   N/A             11491   NT: Boot Options, Select Client menu has bad chars in IP
   N/A             11492   2000: PTR 2000 Client page shows bad netmask values.
   N/A             11493   NT: Error message refers to "VERITAS Server"
   N/A             11497   WIN: Cannot create boot floppy
   N/A             11498   2000: Media SRT Boot floppy w/o PTR fails AFTER writing
   N/A             11509   NT:Drive mapping out of order after restore
   N/A             11525   NTDDR: format failed randomly for certain partitions
   N/A             11527   WIN:bmrguirestore passes -p SPname incorrectly
   N/A             11529   WIN: Confusing Format command failed message
   N/A             11533   CUSTSOL: savecfg trashes good config with bad if VM di
   N/A             11536   BRANDING: the cd version file still says tkg
   N/A             11540   DOC: one more set of changes before 450 RTM
   N/A             11544   WIN: The Win95 dir is not on every WinNT CD
   N/A             11550   WIN: error in strncat operation
   N/A             11551   WIN: createPKG.exe access violation
   N/A             11553   SOLDDR: Setting new boot-device needs quotes
   N/A             11560   WIN: winnt runs out of memory gui.exe and aeb_part2.txt
   N/A             11561   HPTSM:bmrmain assumes root volume is vg00
   N/A             11608   NT: Drive letters still incorrect after dissimilar
   N/A             11612   2000: Fix ConstructBmrKey function header for 2000
   N/A             11618   DOSGUI:  gui.exe does not start Windows Installation
   N/A             11651   2000: Failed ripping drivers on Dell Server
   N/A             11652   AIX: AIX restore "cannot find a physical volume."