Jazkal

Well the x86 winpe.wim file is 160 mb. It is in the winpe.cab file in the image. I would be intrested to know how your going to use the wim file (without all the other tools in the package) in your Multi-Boot DVD.

You need to install the whole thing. It puts the files you are going to need to create your own modified WinPE. There are a couple of other things included, but I would say that 97% of that package is WinPE, and not other fluff you don't need. Once it's installed, if you don't need x64, you could delete those parts, and would save you around 50% or so in space.

You can use it to install XP. You would install XP from WinPE using the winnt32.exe with command line switches. You could even put all the logic inside an HTA, it would give you a GUI of sorts. However, Vista uses it differently, because the method used is image based instead of file based. And I posted a link to download it, in the thread directly under this one.

WinPE is a stand alone tool. It is a slimmed down version of Windows, that runs 100% from RAM. Windows Vista uses PE as the install platform. BartsPE is a version based on Windows XP, and was reverse engineered so that the general public could have access to this tool. It wasn't until this last version (v2.0) that Microsoft has released it to the general public. And in your example of multiple OS installs and PE on the same disc, you wouldn't "need" PE to install XP, but you could use it to fix problems on an already installed XP.

Here is the FINAL version of the WAIK: (Updated on 2/13/07) WAIK Final Now everyone has access to WinPE. This install includes WinPE v2.0 for both x86 and x64. EDIT: updated link(s) to include the newest build released by Microsoft.

Did your keys show up also? or just the media?

I don't use the PNP switch, but I have seen some drivers that won't work without it, unless you find a special RIS version of the driver. And I have seen some drivers that don't work correctly if you don't use the /oscd: switch for drvinst.exe Goodluck

Here are some assumptions, let me know if they are correct: 1) You are using WinPE based on WinXP SP2 or Win2k3 SP1. 2) you are using the /PNP switch? 3) you have installed the driver with the command line: drvinst.exe /inf:%DRIVERINF% /oscd:%OSSOURCE% %PESOURCE% /q

What kind of NIC do you have?

Thank you very much for that info. Have your guys run into any problems so far running dot net apps on PE?

Can you give some examples?

I did a search here, and couldn't find the info i needed to disable the Import Wizard in my Firefox 2.0 silent install. I tracked it down here: Bugzilla the short of it is: create a file named "override.ini" with the following text: [XRE] EnableProfileMigrator=false And place this file in the same directory as your "firefox.exe" file.

I know this is an old thread, but I wanted to see if anyone knows if SoF will be updated to handle Firefox 2?

I ran into that myself. never found the root cause, but the workaround I used was to put the source files to create the iso on the local drives. When I tried to build it over a mapped network drive, I had issues like yours.

I am getting the error below when I run this command: D:\Temp\x86\imagex.exe /boot /compress max /capture D:\PE20_x86 D:\boot.wim "WINPE" Error: Title: "imagex.exe - Aplication Error" The instruction at "0x7c93426d" referenced memory at "0x00000000". The memory could not be "read". I have tried replacing memory, swap file, hard drive, rebooting. It just stoped working yesterday, and I can't get it to work again.

The idea of WGA is fine, in theory. I think Microsoft has a right to check and see if the OS is pirated or not. The problem I have is the daily check in. Maybe someone can explain the logic behind it, i mean once the OS checks out as legit, why keep checking in?

Maybe in Canada copyright theft is considered a criminal theft, but in the USA, it's not. I'm not condoning anyone that does pirate software, that not what I'm saying. You steal a hard drive, the cops will charge you with a crime. You pirate software over the internet, then the affected parties can sue you in a civil court. Big difference IMO. And the way things are going, I think it will soon be a changed here in the USA. I think that is a big shame, as I think the cops should be out there looking "bad" criminals, ones that hurt other people.

As far as I know, there isn't any "legal" definition for "spyware". And by your personal definition: "Spyware sends and recieves data used in a malicious intent or to produce a profit." Lets break apart your definition into it's 3 component parts: 1) It does send and receive data. 2) "malicious intent" could be assumed because they didn't inform us of this "feature", mainly because (IMHO), they knew it would not be well received. 3) You even agreed this was done for the main reason to increase their profit. So by your own definition, it is "spyware". You are entitled to your opinion. Personally, IMO, they stepped over the line with this one. I don't expect Microsoft to explain all the details of all the products they release, they are Microsoft after all (I mean hey, they are a convicted Monopolist). When my own computer starts treating me like a criminal, it's time to start questioning the designer. And you are right, they don't have to answer to our demands and requests, but they do have to deal with those that decide enough is enough ($$ the bottom line $$).

First off, I want to remind everyone of the following rule: CYA. Two web articles, the first from the Inquirer: Microsoft admits XP phones home every day the second from Yahoo News: Microsoft plans better disclosures of tool What total crap Microsoft is pulling, totally unethical IMO.

Ok, well I don't feel bad, didn't want to be the only one.

In my Connect account, I have all the other Beta2 files, but I don't see the WAIK listed. Anyone confirm that you see the WAIK in your Connect list?

I'm waiting for the Beta 2 version of the WAIK to come out. The older version doesn't work on this one. My testing is being done via WinPE over PXE and a network share that has all the files, most of it works, just have to choose the version to install, which is what I'm trying to figure out for the XML file.

I'm trying to a 100% unattended install of Longhorn Vista Beta 2 5384. In my unattended.xml file, I am trying to select the correct image inside the WIM file: in the sample file it shows this section as the part to make this selection: <MetaData> <Key>/IMAGE/NAME</Key> <Value>TestScripts</Value> </MetaData> I have tried all kinds of combinations from the out put of: XIMAGE /INFO install.wim I just can't seem to find the correct info to put in this section. Anyone have this working?

can you give use the output to these commands run manually: diskpart list disk And one question: Is your WinPE image built with the PNP switch?

You can not just add drivers to an image without running sysprep. Sysprep is what integrates the drivers into the Windows install, makes it so that windows understands the hardware it is trying to boot from.