Jazkal

what happens when you run: wscript.exe script.vbs

Yes, the new BuildOptionalComponents.vbs, is now here are the packages that I install to get HTA and scripting installed: %PETOOLS%\peimg.exe /install=WinPE-HTA-Package %isosource%\Mount\Windows %PETOOLS%\peimg.exe /install=WinPE-WMI-Package %isosource%\Mount\Windows %PETOOLS%\peimg.exe /install=WinPE-Scripting-Package %isosource%\Mount\Windows %PETOOLS%\peimg.exe /install=WinPE-XML-Package %isosource%\Mount\Windows %PETOOLS%\peimg.exe /install=WinPE-MDAC-Package %isosource%\Mount\Windows only "WinPE-Scripting-Package" should be needed to handle your VBS files. Read up on "peimg" in the help files, it will answer your questions.

I can't help with most of it, but I can tell you that you will run into problems if your \boot folder isn't "Boot". something about the windows boot loader is case sensitive.

it's in the file named: "Windows Automated Installation Kit User's Guide.chm"

In the docs that come with PE2, look at "Walkthrough: Deploy an Image by using PXE". You have to use the new boot loader, BCD.

how about a real rough idea of the steps needed?

A little birdie told me it has to do with corrupting the vista registry when you mount the WIM and load the vista reg hives. Something about vista registry permission flags. Still waiting to get my hands on it, and the actual kb article.

If you mean boot x86 on a x64 machine, then yes you can.

Search

Without removing anything, just re compressing to max, you can reduce it down to 125 mb.

WinPE2 and Imagex works fine with Win2k3 on most of systems, it's just a few that we are having problems with. And our tests of WinPE 2005, work fine, it's just that we want to move to WinPE2.

Did they reply to your question?

IMO, I will not be migrating to Vista for the following reasons: 1) I don't see it as a stable platform. Way to buggy for a RTM release, it's how Microsoft releases software nowadays, Microsoft's RTM should be Beta. It's not stable enough IMO for business use until at least SP1, if not SP2. 2) Besides DX10, and new Aqua GUI, What am I getting above Windows XP? Not anything worth jumping through the activation/WGA crap that treats me like a thief. 3) When I'm ready for something that looks like Vista, why not go with the orginal; Mac OSX? 4) When Vista come back from sleep or hibernate, it loses the network connections sometimes. When it does, you end up having to reboot the machine to get them back.

Well, I'm still having the problem under Win2k3. It may be a separate issue but I'm not sure.

Glad to hear it, now wait till you try to convert over to WinPE2. That's a whole new can of worms.

Yes, we keep the whole CD on the network share. I found it's quicker to just install it from there. If you are copying the files down locally first, you would need to have the amd64 and i386 folders in the same root folder. I think that is the problem you are seeing.

I've been running Win2k3 x64 installs from WinPE since it came out. My Windows source files are on the network. My setup command line is: Z:\W2K3ES64\AMD64\winnt32.exe /s:Z:\W2K3ES64\AMD64 /syspart:C /tempdrive:C /makelocalsource /unattend:C:\unattend.txt The x64 setup does access both the amd64 and i386 folders. Looking at your command line, it looks like your source files are already on the hard drive? "C:\Progra~1\<company>\amd64\"

This would be better answered in the Unattended Windows Setup forum.

I will give this some testing. I've included a command line tool I just created to use these settings. (I hate using REG files, but thats just me) run the EXE file as follows: (only one example at a time) (only run under WinPE v2.0) DriveAlign.exe XP DriveAlign.exe 2003 DriveAlign.exe Vista It will adjust the registry as needed. If you want to look at the source code, It's included.

Did you get those reg settings from Microsoft?

I'm planning on releasing it open source, let those that are intrested in it, maintain and improve it.

I'm really busy with work right now, trying to hit our project goals for the end of the quarter (end of Dec), so I don't have a lot of free time. I can say though, that BartsPE supplies the plugins (turned off), without the actual binaries. So that people that do have valid licensed software can add their binaries to the plugin, and use it. First step would be to figure out which ones are warez, then remove the binaries. This would make the project 100% legit. If your app becomes the defacto standard for building WinPE2, then others would no doubt start providing the plugins. I know of at least 3 other WinPE Builder apps in the works (including mine). It will all depend on ease of use and plugins.

Nice to see some work done in this direction. Looks good. You may want to remove the warez plugins from the base download though.

And I have one issue that doesn't fit into that explanation from Microsoft. Using WinPE 2005 (based on Win2k3 SP1), and deploying Windows 2003 images captured with ImageX, I see the same kind of Issue. This is using the older "working" diskpart, with and without bootsect/mbrfix (before and after image lay down). Anyone know if there is an older pre-WinPE2 version of bootsect ?

Do you know the hotfix number? That would help greatly for when I call in to ask for it. Thanks.