killerb255

Edit the registry of your PE before running the diskpart command: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vds\Alignment] @="Alignment Settings in Bytes" "Between4_8GB"=dword:0 "Between8_32GB"=dword:0 "GreaterThan32GB"=dword:0 "LessThan4GB"=dword:0

Yes, but Make_PE3 doesn't support SP1 or IE9...

Wimb: Will Make_PE3 be updated to be compatible with a Windows 7 SP1 source and Internet Explorer 9? Using Windows 7 SP1/IE9 results in an RTM Make_PE3 build and a broken Internet Explorer (the icons look as if IE9 ported over, but opening up IE9 results in the browser opening and closing after about 1/2 second...)

Start -> Run -> type in msconfig and click OK. Go to the "Boot" tab and click "Advanced Options." Is "Maximum Memory" checked? If so, uncheck it.

So...what's the minimum amount of RAM to fire up this bad boy? Is it still 512 MB (like a basic PE build) or is it something north of that?

I didn't manually copy files at all. Instead, I created a batch file to swap update.inf files: http://blogs.msdn.com/rds/archive/2009/08/21/remote-desktop-connection-7-for-windows-7-windows-xp-windows-vista.aspx Maybe that'll help you integrate it...

I'm sure it's going to involve some serious BCD editing... Probably somewhere between the time you unmount the PE image and make an ISO, you would copy your Vista source files to the same source. Edit the BCD from there to determine which starts up (I'm sure you could even make a 30 second menu if you wanted to). This should work in theory. How to do it in practice...more research needed... I'm not sure if the wim files need to be consolidated or if you could use two wim files...

Roger that. I'll do so once I get a fresh source going as well as a virtual machine to test.

It is possible to make a WinPE 2.1 flat file disc. Follow the instructions here, for the most part (special thanks to paxamime for going through the trouble to make those batch files in the first place!): http://www.msfn.org/board/index.php?s=&amp...st&p=577244 However, you will need to make these modifications: 1) On 2Mount.bat, change boot.wim to winpe.wim. 2) Create a new batch to run after 5Unmount.bat called 6Apply.bat with the following: REM 6-Apply.bat REM This will apply the winpe.wim image to a new directory called winpe_flat. REM No mounting or unmounting of images are necessary in a flat file structure. %systemdrive% echo Applying the current winpe.wim to C:\PE\winpe_flat to create a flat-file structure. mkdir c:\PE\winpe_flat cd \ cd %programfiles%\Windows AIK\Tools\x86 ImageX /apply c:\PE\winpe_x86\winpe.wim 1 c:\PE\winpe_flat echo Adding a boot directory to C:\PE\winpe_flat mkdir c:\PE\winpe_flat\boot xcopy c:\PE\winpe_x86\ISO\boot]*.* /e /f c:\PE\winpe_flat\boot\ pause 3) Make a 7Bootloader.bat file with the following contents: @echo off echo 7-Bootloader.bat echo This will create a new BCD database for your flat-file PE disc. :STEP1 set peiso=%systemdrive%\PE\winpe_flat goto STEP2 :STEP2 echo Deleting the existing BCD directory and preparing to create a new one. del C:\PE\winpe_flat\boot /q goto STEP3 :STEP3 echo Creating a new bcd Bcdedit /createstore %peiso%\boot\BCD Bcdedit /store %peiso%\boot\BCD /create {bootmgr} /d "Boot Manager" Bcdedit /store %peiso%\boot\BCD /set {bootmgr} device boot Bcdedit /store %peiso%\boot\BCD /create /d "WinPE" /application OSLoader > guid.txt goto STEP4 :STEP4 echo The previous command returns a GUID value. echo The next command parses the GUID and adds it to the remaining commands. for /f "tokens=3" %%h in (guid.txt) do (set guid=%%h) goto STEP5 :STEP5 Bcdedit /store %peiso%\boot\BCD /set %guid% osdevice boot Bcdedit /store %peiso%\boot\BCD /set %guid% device boot Bcdedit /store %peiso%\boot\BCD /set %guid% path \windows\system32\winload.exe Bcdedit /store %peiso%\boot\BCD /set %guid% systemroot \windows Bcdedit /store %peiso%\boot\BCD /set %guid% winpe yes Bcdedit /store %peiso%\boot\BCD /set %guid% detecthal yes Bcdedit /store %peiso%\boot\BCD /displayorder %guid% /addlast echo The custom boot loader has been created. pause 4) Change 6MakeISO.bat to 8MakeISO.bat. 5) Burn ISO to CD. 6) Boot from it. You will NOT be asked to "Press any key to boot from CD or DVD..."

One thing I have noticed after integrating 955839 is that, although the time zone is correct (in my case, it's "Central Time (U.S. and Canada)"), a fresh install of XP using the nLite'd source during the Extended Daylight Saving Time periods: 1) 2nd week of March thru 1st week of April or 2) Last week of October thru 1st week of November ...results in "Central Standard Time" instead of "Central Daylight Time." If I try to reinstall 955839, I get an error stating that the patch has already been installed or has been superseded. However, an install of 951072v2 works and correctly changes the Time Zones... Any ideas?

You shouldn't have to use a GUID. By default, PE assigns the first NIC the name "Local Area Connection," the second "Local Area Connection 2," etc.

Are you using single or dual-layer DVDs? On a side note, has anyone tried integrating the Vista Enterprise DVDs (both 32 and 64-bit) into one installer? Same instructions, except you're actually merging four DVDs (retail 32-bit, retail 64-bit, Enterprise 32-bit, and Enterprise 64-bit) instead of two. EDIT: I've done so recently, and it works great! 10 different Vistas (Home Basic, Home Premium, Business, Enterprise, and Ultimate x86 and the same five x64)--all install just fine!

Use this command: netsh interface set ipv4 address "[name of the connection]" static [iP address] [subnet mask] [default gateway] [metric number] For example, to set a static IP to two NICs, you would use two commands: netsh interface set ipv4 address "Local Area Connection" static 123.45.67.89 255.255.255.0 123.45.67.81 1 netsh interface set ipv4 address "Local Area Connection 2" static 123.45.67.88 255.255.255.0 123.45.67.81 2 Substitute the IP addresses, subnet mask, and default gateway you want accordingly.

That's just human nature. The more we learn, the less we want to learn, and the more we want to apply what we know. Change stimulates fear. After all, fear is nothing more than a perceived loss of control. When things change, we don't feel as "in control" as we did beforehand. However, when there is no change at all, people end up lamenting in their comfort zones, even if that zone is a danger zone of sorts. Abused women are a perfect example of this. They would rather keep things the way they are, even if their lives are at risk, than to remove themselves from the situation and deal with the unknown--something that they don't think they have control over. Bottom line: Zero change is unhealthy. Change for the sake of change does more harm than good (dealing with the resistance and having little to gain from it). Were the Windows 7 UI changes simply "change for the sake of change"? To many, yes it is. To some, not really. Being a veteran in the IT business, I'm sure you remember people complaining about the changes in Windows being too minute. In other words, a new version of Windows is pointless to the "S" (sensing) personalities out there that learn solely by their five senses (sight, hearing, taste, touch, smell). To an S personality, Windows 95 and Windows 98 were pretty much one and the same. The "N" (intuitive) personalities familiar with both OSes knew the differences, though (for better or worse): better networking support, FAT32 support out of the box, better USB support, integrated Internet Explorer... So in reality, the Windows 7 UI changes were most likely to convince the S personalities out there that Windows 7 is "new," "different enough from Vista," and "different enough from previous versions of Windows in general." QFT!!!! I can't count how many times I've had to rebuild Windows 2000 and XP roaming profiles!!! I haven't dealt with a single corrupt Windows Vista roaming profile yet!

At least this is an easy way to distinguish the beta testers from the leeches...