getwired

BartPE is just like WinPE. It's a reverse engineered (questionably licensed) version. Booting one is the same as booting the other. If you don't have the latest verion of WinPE (or BartPE) but you want to PXE boot, you need RIS. If you have the latest version, you can use RIS or any othe PXE server - but you still need some sort of PXE server if you want to boot WinPE from the network.

The functionality to apply the WIM files lives within the Windows setup code itself. It doesn't use XImage. XImage is available as a part of the WAIK, from Microsoft. I can describe how the PE boot to WIM works, but I'm not sure how it will help you. Are you just trying to familiarize yourself with the infrastructure?

This functionality is avalable in Windows PE 1.6. Documentation included with it explains how it works.

That is quite by design. ERD Commander has it's own version of Windows PE in it that it is licensed and tested to work with.

Actually, factory -winpe runs the exact same code as what you just specified, and will additionally process a winbom.ini. To the original poster - are you sure your NIC driver is in WinPE? Have you added it if not?

Is this only on one specific system, or multiple systems? If multiples, do they all have the same NIC? What I'm getting at is on a large file transfer, if the NIC burps, it will corrupt the file. Often it will do it uniformly.

1: There is a way to build 64-bit support for X64 - you need a copy of XP or Server 2003 for 64-bit extended, and the build tools that shipped simultaneously with Windows Server 2003 SP1. That's the first version that could build an X64 version. 2: WinPE licensing hasn't changed - it isn't a product. It's still only licensed to ISV's, OEM's by way of the OPK, enterprises/schools/gov't by way of Software Assurance. A MS field office can't help you acquire it. 3: Access to systems isn't the reason why WinPE is licensed the way it is - it has nothing to do with security. WinPE gets you nothing more than a side-by-side installation of Windows would, or even Linux with a good NTFS driver. Physical security = compromise. EFS data isn't readable from within WinPE, as noted.

Add /makelocalsource to your switches.

During the ISO wizard you can add networking devices. Is that not working for you.

RAMDisk boot ONLY works if Server 2003 SP1 is your source. There is no way to use Windows XP (any version).

Not CDONTS - CDOSYS. CDONTS isn't in XP or 2003, which are required for PE to work.

The error you are seeing is virtual PC's ineptitude at dealing with images of "CD's" that aren't CD's. In the case of booting Windows CD's or WinPE CD's, depending on what ISO creator you use there is a different error you can hit at boot time.

You can't see one or the other - the operating system presents one to 32-bit and the other to 64-bit applications - each will see only one. I doubt that what the original poster asked about is possible.

Correct.

Actually, this is exactly what the latest version of WinPE is capable of doing.

Stupid argument for piracy. Do you work? Do you appreciate it when others steal your work? If you don't like the prices, don't buy the product. Porsches are too expensive for me - but I don't steal them.

<{POST_SNAPBACK}> Is that really news to anyone? You wouldn't even be able to boot the CD on an Itanic system. Or were you pointing it out because it is amusing that it's an FAQ? Also, you misspelled it. It's "MS" - you were off a couple of keys.

There is indeed a scenario where this can caus this problem. And it totally depends on where those 4GB of files are sitting.

What is the exact path of Programs on the DVD? What is the error you get when booting?

I may be mistaken, but it doesn't have to be in the EULA. It’s a little bit of Federal law called "Fair Use". As far as the EULA is concerned, it hasn't been tested in court about whether or not it's even legally binding. Fair Use and the right of first purchase have been around for a while and are proven in court. Can't say the same for the EULA. If you followed BartsPE when it first came out, Microsoft did attack it, and quickly I might add. All they came up with was copyright violations. These have since been addressed, and Microsoft isn't doing anything towards BartsPE now. <{POST_SNAPBACK}> When it comes to software, unless it is in the EULA, it is a hazy gray area. Fair use has been proven when it comes to video content. It has not been proven with software. It's not rocket science to take a 64-bit copy of Windows XP and twist it into 64-bit Server 2003. You're still using the same binaries - and the EULA likely doesn't say anything to that point - but do you think that's legal? That is exactly what is done with BartPE - it's a reverse engineering of a Microsoft product, end-arounding a licensing avenue Microsoft has in place. I did follow BartPE from the beginning - and I believe that it is still a gray area - but Microsoft is standing off for now. Personally I don't think they're keen to create the melee about it that the RIAA has done over recorded music. I believe any company that uses BartPE to any significant extent is potentially putting themselves in an uncomfortable place, legally.

Find where in the EULA for XP it says it is acceptable, and then I'll stop saying that. It isn't within the bounds of the XP EULA. The problem with XP Embedded isn't the price, it's that it was never designed to be a multi-platform (white box) solution. It was designed for embedded single source (black box) devices. WinPE is the solution that was designed for multi-system booting for deployment, and later licensed to ISV's for recovery, backup, deployment, and could be for spyware as well - but I have not seen that done so far.

That is an assumption Bart made and has repeated. I don't believe he is a lawyer, and I don't believe his statement has been endorsed or validated by Microsoft in any way... Frankly while BartPE does have a better process for adding in additional components, it's still not as smooth as Windows XP Embedded if one is trying to actually build an embedded operating system - which WinPE was never designed to be - though it seems many on this board want to try and make it.

All BartPE was/is is a reverse engineered version of WinPE with a different build process (that others have hacked new bits into)... I wouldn't even bother with Bart's if you are using this within your company - you are walking a fine legal line with Microsoft... Anyone who advises you on how many/what kind of licenses you need to stay in compliance with is pulling advice out of their bum... Unless they work for Microsoft licensing. BTW, you can accomplish what you want from WinPE...

Weird - it works perfectly for me... :-/

All versions of WinPE from the very first one delivered with Windows XP RTM to the latest delivered with Windows Server 2003 can be used to install any version of Windows 2000, Windows XP, and Windows Server 2003. There are Itanium and X64 variants of WinPE that can be used to install Windows Server 2003 and Windows XP as well (XP obviously only for X64, since it has been thankfully dropped for the Itanium). You can also use WinPE to install images of Windows 9X (requires work) and IMAGES of Windows NT SP6a.