Tripredacus

I am not aware of a way for you to add space to a RAID1... - what is your RAID controller? - why are you running out of space on C: drive?

Glad you got it to work. Clearly, it was not considered to need to deploy Windows in that way, which is why it is a pain. Maybe some day we can dream of MS wanting to support that type of deployment.

As easy it was for me to read this post, I need to point out this is an English only forum. In future posts, use a translator if you do not know English, for those who do not read Spanish.

You'll need both kinds. SATA/IDE drivers for XP to use... USB drivers for your Setup to boot.

It is technically possible, although that method is not one I would recommend.

0x7B means that Windows does not have the drivers for your Mass Storage controller... aka IDE/ATA/whatever. If you get these trying to boot your install media, then you need the drivers for that method. Since you are using USB, you need to put in your USB drivers. Also since I have not done any of this type of thing, I am moving the topic to the correct place!

For reference, "services and controller app" is services.exe. ulli, since you're new, I didn't want to just vanish your post. This is the thread you should post in: http://www.msfn.org/board/topic/140264-how-to-get-the-cause-of-high-cpu-usage-caused-by-apps/

Its more likely that Windows is just entering the "Tribal tattoo" phase.

I looked into this program you mention... I have no dealings with it. I have seen some people have used either MDT or DeployStudio to do this type of work. https://groups.google.com/forum/#!msg/macenterprise/jR2VY6PvFqc/Hn39Bt-K7OEJ

As a test, I would try the following: 1. Install Windows. 2. At OOBE screen, use Ctrl+Alt+F3 which will put the OS into Audit Mode 3. Run your program. 4. Sysprep the OS If it works this way, you can capture the OS after step 4 for redeployment.

Xper is doing database work relating to this issue: http://www.msfn.org/board/topic/173567-mstests-topics-and-posts-not-showing-and-making-the-other-posts-invisible/ May be related.

For reference, LMDE is Linux Mint Debian Edition.

The process you want to attempt will not work this way. If at any time, the system is rebooted prior to OOBE being presented, the OS installation will fail and become unusable. However, Windows does actually do a reboot itself before presenting the OOBE pages. You can try running your command in the Specialize pass. I'm not certain if the specialize pass occurs during the first phase of installation or not.

No need to reinvent the wheel. They can just use what is in the Wingdings font!

Correct. UEFI will only be useful if you want a boot volume of larger than 2TB, or you want to use SecureBoot or one of the other security features that requires UEFI to be enabled.

Is the entire screen gone black (like the monitor being off) or is it that portions of your screen are black? You say "page" but what is it exactly? Is it a bookmark to a website?

Sounds like you're late to the party! Or more-so that IE/MS may be late to the custom User Agent party. Firefox and Chrome have had add-ons/plugins/whatever to change user agents for quite some time now. No hex editing required!

Software is better than Drivers I hope... Highlighting this.

IE in Windows 10 is annoying. It seems the default action of things typed into the address bar is to search for that in bing.... even if I type a url in there...

Welcome to the MSFN! I have removed the link in your signature. After you have been on the forum a while, you can post your link in the Websites and Boards forum. See rule 2.e for details.

Ah well, I was hoping maybe the XML used a switch on that EXE... An image will should either me 1 large file (over 2GB) or it may use multiple spanned-files in 2GB parts. WinRE's boot.wim is just a WinPE. So all those folders you see are from that. I highly doubt the TWinRERecoveryReminder.exe creates folders in the way you mention, although it is quite possible that it prompts to insert a disc. Do you have any other partitions on this system?

It is this: http://www.dell.com/support/home/cd/en/cddhs1/Drivers/DriversDetails?driverId=8J89J It is NOT a driver. It is a BIOS update that can be applied from Windows. It is also not an archive.

Well... the WinRE partition doesn't have the backup image in it. The boot.wim is just the PE that runs the recovery software to restore the recovery image. It was my understanding that you wanted to replace the recovery image with an updated one... You need to find where that image is. NOTE. it may not be a WIM... I would expect to find a setup.exe in your winre.wim, but there doesn't appear to be one. They may be using a custom software package to do the recovery. What is in the WinREConfig.xml? Regarding sysprep... Typically the generalize is used to make the image workable to different hardware. It may not be required if this image is only to be used on the same system it was captured from.

Hooo boy, no one can say for sure. Who knows what MS will change by then.