今天放水一天！

samcsli

　　2.你可从Windows PE计算机通过网络直接访问服务器和共享。但不能从网络上的另一个位置访问Windows PE计算机上的任何文件或文件夹。Windows PE通过TCP/IP及其上的NetBIOS获得到达文件服务器的网络连接，不支持其他方法（如IPX/SPX网络协议）。

samcsli

　　3.因为涉及反盗版，所以只能从Windows XP Professional CD建立Windows PE的自定义版本。而不能从Windows XP Home Edition或Windows 2002 Server操作系统家族的任何成员建立。

samcsli

　　4.Windows PE太大，不能放在软盘上。Windows PE仅包括可用Win32 API的子集（包括I/O（磁盘和网络）和核心Win32 API）。如果Win32下运行的服务基于Win32 API子集，则它在Windows PE是否可用需具体分析。这里不详细列出Windows PE不支持的API了，反正rundll32.exe和shell.dll等是不被支持的，想要在Windows PE下面玩Quake的朋友还是趁早放弃。

samcsli

　不少朋友看到这儿无论是否有收获，肯定都会想Windows PE到底对自己有什么明确的作用，这里不妨总结一二。

samcsli

　1.方便易用的启动工具盘
　　通过刚才的叙述，大家可以看出，Windows PE启动相当快捷，而且对启动环境要求不高；最可贵的是，虽然名为启动盘，其功能却几乎相当于安装了一个Windows XP的“命令行版本”——别忘了网络支持哦。因此，对于个人计算机用户，只要将其刻录在一张光碟上，便可放心地去解决初始化系统之类的问题；而对小型网络环境（如网吧等）用户来说，这一功能尤其实用。

samcsli

　　2.有趣的硬盘使用功能
　　自定义的Windows PE不仅可放到那些可移动存储设备如CD上，还可以放在硬盘上使用。因为许多朋友会认为将Windows PE的自定义版本放在硬盘上没有什么意义，其实不然。把Windows PE放在硬盘上应该是最为有趣的地方，且不说你的操作系统损坏无法进入的情况下启动硬盘上的Windows PE可以方便地修复，关键是由于Windows PE在硬盘上，所以在Windows PE环境下安装应用程序就有了可能。呵呵，撇开题外话不讲，这里看一下如何把自定义的Windows PE放到硬盘上吧（只能在硬盘上放置Windows PE的32位版本）。
　　首先要安装恢复控制台：
　　（1）将Windows XP Professional CD放在CD-ROM驱动器中，这里指定其为cd_drive。
　　（2）在命令行CMD窗口中运行cd_drive\i386\winnt32.exe /cmdcons。
　　然后将Windows PE自定义可引导副本放置在硬盘上，如下操作：
　　（1）在目标硬盘上，创建“C:\Minint”的目录（这里必须将目录命名为“Minint”）。
　　（2）将Windows PE“根目录\i386”下的所有内容复制到C:\Minint。
　　（3）从Windows PE根目录下将Winbom.ini复制到目标硬盘的根目录。
　　（4）在目标硬盘上，将“C:\Cmdcons\txtsetup.sif”的只读属性改为读/写。
　　（5）在目标硬盘上，将“C:\Minint\txtsetup.sif”复制到“C:\Cmdcons”进行覆盖。
　　（6）重新启动目标计算机。在“引导”菜单上，选择引导到“命令控制台”，计算机将使用Windows PE引导。

samcsli

　　3.Windows XP OPK CD的本职工作
　　上面说了其实我们拿到的是Windows PE的一个可执行副本，即Windows XP OPK（Windows XP OEM预安装工具包）CD。从名字都知道它原来的本职工作是为了方便OEM工作的。如果你在Windows操作系统环境下打开光碟，它就会自动运行Autorun为你的系统安装一个“Windows安装管理器”的工具包。利用它，你可以轻易制造出带有计算机厂商OEM标志的Windows安装镜像。虽然这是Windows XP OPK CD的主要本职工作，但显然对我们个人没什么意义，当然，如果你想把手上的Windows安装CD都打上自己独有的印记，并在朋友的机器上安装时炫一下，那么使用它是个好主意。当然自己的“印记”绝非OEM标志那么简单，实际上你还可任意设定Windows PE携带的软件，并可设置这些软件在Windows PE启动时运行；理想的情形下你甚至可以为自定义的Windows PE版本加上类似于Windows Explorer的图形外壳程序——要不怎么叫专为厂商OEM设计呢？

samcsli

　Bart's PE Builder 是一个可以帮助你快速的创建可引导的CD或者DVD光盘,用来诊断和修复系统错误时使用!最新版本支持Windows XP 和Windows Server 2003!不同于一般的引导光盘制作工具,本程序可以帮助你创建纯32位的图形界面操作环境,支持网络和远程管理功能,支持FAT/NTFS/CDFS等各种常见分区格式,采用800X600的分辨率,用此光盘引导系统,你可以进行系统错误判断和修复,文件数据的抢修,病毒的扫描和杀毒等操作,非常容易使用。

samcsli

　　Bart's PE Builder 帮助你建立和从光盘启动Windows XP和Windows Server 2003核心的迷你操作系统，类似Microsoft的Windows PE，直接刻盘在BIOS里设置光盘启动然后WIN PE会自动引导进入一个命令行界面（象从前的DOS），可以读写FAT32、NTFS等格式的分区，可以对硬盘分区、格式化（可以格成NTFS的）；还可以直接使用网络。

samcsli

BartPE是一个利用微软的Windows XP及Windows Server 2003安装光碟而达成的预先安装环境。用户只要到BartPE的网址下载相关档案，并依照说明的程序去做，就可以为自己制造一张“救机”用的光碟。凭著这张“救机光碟”，用户可以在电脑上的操作系统不能运作时，在原来的电脑启动 WinXP 或 Windows 2003，从而对有关资料进行备份，或当作临时的操作系统使用。这对于死机率超高的 WinXP 系统来讲，实在十分方便。另一方面，系统维护者亦可以先行购买一套正版的 WinXP 或 Windows 2003，然后制作一只随身携带的“救机光碟”，以便为其他电脑作诊断时，亦可以存取有关电脑的内容。

samcsli

虽然这个系统的作者声称有关技术乃系利用法律容许用户本身为系统所作出的备份而制成有关光碟，微软仍然坚持有关系统的制作侵犯了微软本身商品的版权。因此，若用户有意使用，必须先行理解使用时可能引起的法律问题。

samcsli

说明

Bart的“预先安装环境建立程序”帮助你从你的原装 Windows XP 或 Windows Server 2003 安装光碟建立一套属于自己的BartPE，以便日后进行维修。

samcsli

BartPE给你完整的Win32环境，包括网络支援、800×600解像度的图型界面、FAT/NTFS/CDFS等各种档案系统的支援。让你在无需要安装任何操作系统的情况下为你的电脑系统进行测试或抢救，并透过网络作备份、病毒扫描等各种工作。有了BartPE，就不再需要有“DOS启动软碟”了！

samcsli

“预先安装环境建立程序”并不是微软的产品，亦不会帮你建立微软的“预先安装环境建立程序”(WinPE)。使用“预先安装环境建立程序”不会赋于你微软WinPE的使用权，亦不用给你原来的使用者权限以外的其他权利。本产品并未经过微软公司验证，也没有得到微软公司准许使用。

samcsli

Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD
BartPE is Admin's best friend...
Version 3.1.10a (released on Feb 17, 2006)

samcsli

What is BartPE and PE Builder?

Bart's PE Builder helps you build a "BartPE" (Bart Preinstalled Environment) bootable Windows CD-Rom or DVD from the original Windows XP or Windows Server 2003 installation/setup CD, very suitable for PC maintenance tasks.

It will give you a complete Win32 environment with network support, a graphical user interface (800x600) and FAT/NTFS/CDFS filesystem support. Very handy for burn-in testing systems with no OS, rescuing files to a network share, virus scan and so on.
This will replace any Dos bootdisk in no time!

samcsli

Introduction

PE Builder is not a Microsoft product and does not create Microsoft Windows Preinstallation Environment ("Windows PE"). Using PE Builder does not grant you a license to Microsoft Windows PE or to use the Windows XP or Server 2003 binaries in a manner other than stated in the End-User License Agreement included in your version of Microsoft Windows XP or Windows Server 2003. Microsoft has not reviewed or tested PE Builder and does not endorse its use

samcsli

Please do not contact Microsoft for support on the preinstallation environment that has been created by PE Builder!
Microsoft does not provide support for PE Builder or for the preinstallation environment created by PE Builder.

samcsli

The PE Builder program (pebuilder.exe) runs on Windows 2000/XP/2003/BartPE. It does not run on Windows NT4/ME/9x.

To avoid any confusion, the bootable CD generated by PE Builder should be called by its nickname "BartPE"!

samcsli

A word from the author

Hi, my name is Bart Lagerweij. I've been creating DOS based boot disks and bootable CD-Roms from Dos 3.x (not sure what year) until 2002. I have created the: Corporate Modboot, Network bootdisk, CD-Rom bootdisk, a hardware independent Dos CD-Rom driver eltorito.sys and lots of other tools needed to boot a PC the way I want it to.

As you can read above I've stopped doing that in 2002. Why? I saw a Windows PE (WinPE) bootable CD-Rom (from Microsoft) in action and I got very, very curious. I knew then as I know now, that in time PE-based solutions will be every PC technicians best friend.
Goodbye to all the good and bad dos-based NTFS utilities! Now we can boot from a CD-Rom and have full read/write access to NTFS volumes!

Here are a few things that are possible with PE and are not possible with any type of dos-based boot disk, even when using network support and ntfsdos:
Accessing very large (>2TB) NTFS volumes or accessing volumes that are not seen by the BIOS, like some fibre channel disks.
Very reliable scanning and cleaning of viruses on NTFS volumes using a "clean boot".
Active Directory support.
Have remote control over other machines, using vnc or remote desktop.

samcsli

While I was already thinking about what great things this could do, I noticed the end-user license agreement for Microsoft software that is included with Windows Preinstallation Environment (Windows PE) 1.2 (eula.txt). In section "1. ELIGIBILITY." it states the following:
..."You may only install and use the SOFTWARE PRODUCT if you are an active Microsoft Software Assurance Member ("SAM") for the systems product pool or servers product pool, if you currently have license coverage for Microsoft Windows operating system (OS) Upgrades via a Campus Agreement or School Agreement, or if you are a current or former participant in the Windows XP Joint Development Program, Windows XP Rapid Adoption Program, Windows .NET Server Joint Development Program, or Windows .NET Server Rapid Adoption Program. If you do not meet one or more of the requirements listed above, you may not install or use this SOFTWARE PRODUCT and you must terminate the installation of this SOFTWARE PRODUCT immediately"...

samcsli

Oops, that does not include me. As a matter a fact that does not include most of us! This was very disappointing. But then I started thinking, how difficult can it be to build something similar to Windows PE from a Windows XP installation CD-Rom? A quick file compare looked like most of the needed files are on the Windows XP CD-Rom. Only because I thought building this would be easy, I started coding my own builder program. Had I known how hard it would be, I would probably never have started programming PE Builder.
This first version (v1.0.0) of PE Builder was released on April 28, 2003. Yes, version 1 was a very simple, very static, very bad and copyright violating program. And the (very friendly) people at Microsoft had every right to kick my butt. But I learned from it and in May 2003 I started on a second version. In July (three months later) v2 was ready.
Version 2 did not have the problems that version 1 had. The version 2 build engine had its own registry hive builder which was not easy to program and took about 50% of my research and coding time. It also was dynamic enough that it could build from Windows XP and Server 2003. In v2.0.1 I added a small but very powerful menu program called nu2menu, which was written by my buddy Henk de Jong. The latest 2 version (v2.0.2b) even used a new ISO filesystem called "ISO-9660:1999 (version 2)" instead of the Joliet extensions. Some non-English versions of Windows XP had filenames longer than the maximum allowed length for Joliet filenames (103 chars). I had to patch the ISO building program (mkisofs.exe) so that the Windows NT bootstrap and setup loader would boot properly. The file and directory names can now be up to 207 characters. But again this version had something bad. When comparing some INF files they looked too much like the Windows PE builder from Microsoft.

samcsli

I had to change the entire INF file layout to use its own format. And on Sep 1, 2003 (almost 6 months after starting) version 3 was ready. After adding plugin support, PE Builder got very popular. People from all over the world are writing their own plugins to add the program they like and use.

samcsli

BartPE vs. Windows PE?
BartPE is not supported by Microsoft. Windows PE is an official Microsoft product.
BartPE has a graphical user interface. Windows PE has a command line interface.
The tools needed to make a BartPE installation are free software. Windows PE is available only to Microsoft OEM users.
BartPE allows unlimited custom plugins. Windows PE has a limited range of plugins options.

samcsli

What is the technical difference between BartPE and Windows PE?
Target - Microsoft sees Windows PE as an installation platform. Bart sees Windows PE as the next generation rescue platform.
Start-menu - Bart's builder gives you a simple, dynamic and powerful start-menu (Nu2Menu, see screenshots). Microsoft's builder does not give you a start-menu, it uses a command prompt.
Build from - Bart's builder can also build from Windows XP Home Edition or from a preinstalled Windows XP version (without CD).
Plugins - With PE Builder you can easily add applications, drivers or tools using plugins. This makes PE Builder extremely powerful. The end user can even combine plugins from different software vendors into one CD image.
Network support - PE Builder includes its own network support tools (bartpe/penetcfg) to start TCP/IP and Microsoft Client. The TCP/IP settings like: dynamic/static ip-address, subnet-mask, default gateway, dns-servers computer-name, workgroup can be changed on-the-fly. You can create pre-defined profiles, that you can select. Microsoft Windows PE only supports DHCP or fixed settings using winbom.ini.
Also there is a plugin (NwDskPe) created by Erwin Veermans that loads the Netware Client on BartPE (IP/IPX).
Fileshare - BartPE can start File Sharing support so you can connect to the system through a share.
VNC - Because of the File Sharing support you can also run UltraVNC.
Dos support - Bart's builder has a plugin called "dospe".
License - Microsoft Windows PE is only for Enterprise/OEM customers (see previous), BartPE is for everybody!
64-Bit - Bart's builder does not support Windows 64-bit editions.

samcsli

Requirements to build:
The files from your Windows Installation CD-Rom.
Supported Windows versions are:
Windows XP Home Edition (must be slip streamed with Service Pack 1 or higher)
Windows XP Professional (must be slip streamed with Service Pack 1 or higher)
Windows Server 2003, Web Edition
Windows Server 2003, Standard Edition
Windows Server 2003, Enterprise Edition
PE Builder runs on Windows 2000/XP/2003/BartPE systems.
CD/DVD writer if you want to creat a bootable CD/DVD.

samcsli

Why did I build PE Builder?

Microsoft only provides Windows PE to OEM and Enterprise customers. So the small companies and end users do not get Windows PE. I think this is really bad. With PE Builder they can build a Bootable XP CD-Rom (called BartPE) to use for maintaining their systems.

samcsli

Licensing issues

In order to make a BartPE installation, your must have a properly licensed copy of the operating system. BartPE does not grant users who do not have a proper Windows XP/2003 license the right to use a BartPE installation.

Also, according to the Microsoft EULA for Windows XP/2003, a user may not simultaneously use more installations of these operating systems than the user has license(s) for. This also goes for BartPE. In practice this means that the user may not use, for instance, a single license installation on one computer while simultaneously using a BartPE installation (created using that license) on another computer.

More information:
Your local Microsoft Windows end-user license agreement (c:\WINDOWS\system32\eula.txt)
PE Builder license file

samcsli

Getting started

This page will help you create your very first BartPE CD. It assumes that you are using Windows XP.

samcsli

Make sure that your system has about 500MB of free disk space!