Tripredacus

It looks like a typo. Should be RD /s/q. C:\Users\xxxx>rd /? Removes (deletes) a directory. RMDIR [/S] [/Q] [drive:]path RD [/S] [/Q] [drive:]path /S Removes all directories and files in the specified directory in addition to the directory itself. Used to remove a directory tree. /Q Quiet mode, do not ask if ok to remove a directory tree with /S

I've never used rearm before since there wasn't a valid reason for it. Are you generalizing your images? This is required for deployment, as it takes out the machine-specific data that can cause duplicate CMID error. I see your SKU (presuming it is the same) you posted Windows 7 Enterprise in another thread. Are you using KMS for your activation?

Tripredacus, I am curious how you do this. Is it the 32/64 nature of setup.exe that is causing the 'Load driver' function to fail to find a mass storage driver? Is this a work around for that problem? Thanks and enjoy, John. I use Imagex. I do have normal DVDs that use setup.exe, but their install.wim only have 1 image in them. The only time I used one with multiple in the install.wim was with WDS which was I saw this issue where the Setup boot.wim from 7PRO64 would not display 32bit images. From my understanding, setup.exe uses drvload to install the mass storage drivers. As far as drivers not being found, I've encountered this before, but usually to do with either a corrupted ISO or with poorly written drivers. Either the 32bit or 64bit boot.wim does not support WoW. So if you got that error while running a program on the 64bit boot.wim, then your program or required libraries were not 64bit.

Did you see if you could replicate the behaviour while in safe mode?

Do not make duplicate topics!

Unfortunately, the percentage of users who are even aware of such things is extremely small compared to the amount of people who would end up using Windows 8.

Ah yes. The 32bit setup.exe can show either a 32bit or 64bit index from install.wim. The 64bit Setup.exe can only show a 64bit index from install.wim Note I chose the term "show" as in will appear in the image selection window. For example: I never tried to force 64bit Setup to install a 32bit install using an answer file. My 64bit boot images do not use Setup.exe.

Not yet. Presuming I have some time to try it next week I will.

Microsoft has made available a CTP of Windows Embedded 8 you can try out. If there is any way to get rid of Metro, it can probably be figured out with this. http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-standard-8-ctp.aspx

Switches for what? Anyways, as far as drivers go. For the boot.wim you only need LAN and Mass Storage drivers. If you are not doing a network deployment, you may not even need LAN drivers. Since all my WinPE use is from PXE, those two driver types are the ones I use. However, I don't go about adding drivers willy-nilly. Only if a hardware isn't working properly, I add its drivers.

It certainly is a neat idea, but in practice I've found it doesn't always work for some reason and it times out connecting to the MS DL site. Which is fine since I did have the ISO somewhere already.

What are you using re-arm for? What Windows SKU is it?

What is the exact error you get?

I can't find anything on MSDN referred to SP1U. The only thing I can think of is if your DVD was originally a Windows 7 en-US source with something other than a Wave-0 SP1 applied to it.

Of course not. WinPE (boot.wim) doesn't support WoW, so you need to match archs for either build. I use x64 boot.wim to do everything nowadays tho.

That is not a normal behaviour. I'd expect the issue isn't related to the command prompt. When you go to run your command prompt, do you use COMMAND.COM or CMD.EXE?

This is a duplicate topic.

Does this Flash functionality in IE10 exist in the RP? I don't think I have it installed anymore to play with.

Someone I know on another forum recently won an above-ground pool in a contest but then gave it away. It was a concept he hadn't considered before, being a huge turtle fan, of using a pool as an aquarium. So he decided to up the ante and plan on a budget for whatever would be required for a large above ground pool for his turtles. His excitement seemed to let him ignore all of our warnings about why a large outdoor water spot like that could be very bad for him and his neighborhood. Think about having a pool that doesn't have chlorine (it would kill turtles and the other fish) and wouldn't ever get a cleaning a pool would normally get. Mosquitos and other bugs would be in heaven. Remember this is an open-air aquarium outside, open to the elements and the creatures of the night, not safely kept within a house. To help illustrate the potential dangers of such an endeavor, I was commissioned to provide something to put it all in perspective. I still don't think he gets it, but whatever!

One easy WIM to get to is the boot.wim on the Windows Setup DVD. But you still can't add any WinPE packages and if you keep adding things for JFX's tool to get, you might as well just download the entire thing!

You should be using a .cmd extension for Windows 7! This is a good test but FirstLogonCommands doesn't use a command prompt (opened by a user) to process the command. You can try outputting your command to a file using the " > file.log" method to see what exactly isn't working. Have you tried using CMD /C instead of /K and see if that makes any difference?

Well, then I managed to just do something impossible. jaclaz Well yes, using an unlocker (or closing some handles) might be considered "cheating"

We're talking about XP here. It came out in 2001... Do you remember what computing was like back then? A large picture file was 300k and digital cameras had floppy disks in them. Video files were not as common of something to download (and the quality was horrible). I'd expect the planning for XP and its My Documents folder was even earlier than that. The fact that they were smart enough to include those folders it remarkable enough. But TBH, I never used My Documents or any of those "My" folders inside due to performance issues with how it is tied into startup and the profile.

It would appear so. It isn't the securest method of prividing service. If any of the company's systems are on that network (like accounting or whatever) then they are open to be attacked, even if they don't show up in the Network list. That may be enough motivation for them to set their network up differently.

The RAID driver that the boot.wim uses is just for WinPE to be able to write to the drive. It isn't related to the RAID driver in your install.wim. WinPE/Setup writes everything (contents of install.wim) to the disk and the next boot doesn't have anything to do with it. You can use a 64bit boot.wim to install x64 images only, but x86 boot.wim can install both archs.