Tripredacus

I think the best representation of this type of image is to reference the end credits song from the Lamb Chop Play Along show... But I warn you once you know this song, you will remember it forever! Also for background, this particular meme is called the Demotivational Tunnel. There are other examples here: http://knowyourmeme.com/memes/demotivational-tunnel/photos

Look at IcemanND's guide. It tells you how to use startnet.cmd to handle this. Its pinned in this forum and he also posted a link to it in your other thread.

I can't remember exactly if I have booted a WinPE on an Axp but I must have. I would wager that it isn't so much a problem with the CPU but with how the board works. If you are using an ATAPI or SATA ODD, try using a USB one. Or try having your WinPE boot from a USB key. I rarely ever will use a CD to boot a custom WinPE, so I don't have much experience in that. To see if there is an actual problem with those boards and WinPE 3, presumably a Windows 7 RTM DVD would have the same problem, if not SP1.

Ok, for some reason I was thinking that the programs having this problem were using a non Save As type method to write files.

Well of course. Only certain kinds of drivers will work with just the INF file. An INF is just a set of instructions which includes copying relevant files. If you didn't have these files in that folder, then DISM would give you an error when trying to execute the INF.

If you have made this WinPE disc, you should still have the boot.wim in the winpe_x86 folder that you used WAIK to create. You can mount that with DISM and add drivers. Read the WinPE .chm from the WAIK menu in the Start Menu to find DISM's servicing commands, or they can be found on TechNet as well.

MDT would be the way to go for sure. If you want to impress your boss/teacher, you would tell them that a real company wouldn't do everything manually. Either way, we can point you to documentation on how to use MDT but since you are working on a school related project, we can't do the work for you.

While the image is offline (best to make a copy of it first) search in the WinSxS folder for the original file. Replace that and then try again. Windows may not be smart enough to know that the "original backup" file was replaced, and will still restore it. I had to do the same thing when I had changed a Server 2003 box to look like XP Embedded.

Well I don't think any program actually would use Explorer to copy files. It would either be done via the API or Comspec call. Why opening the file in Explorer first would make a difference, I do not know.

Using the method to remove Action Center icon does not disable it.

Welcome to the MSFN!

This is redundant. DISM isn't smart enough to overwrite an existing driver I don't think, so if you did both of these commands, you'll have e1c62x64.inf as two different oem*.inf. I don't think it would cause a problem but it is an unneeded step.

Well yes, the old Intel HECI driver is the only one I've removed from my SP1 images. I'm glad they have all that in the Chipset driver package now, makes it much easier. In fact, even the newest Chipset driver package (9.2.3.1002) has audio drivers in it too!

That is the question. This animation you see in the VM, is it the bootscreen for the WInPE (boot.wim) or the deployed OS?

Microsoft OS files are not redistributable. Your attachment has been removed. Hdaudres.dll should definately be in there. For one, it is included in the ever popular KB888111. Both of these files show that they do have a different date, which is off by 1 minute.

For Vista, you may need to provide the Mass Storage drivers. If Vista needs these, it should prompt you for them and provide a browse button. On the other computer, you can initialize the disk from Disk Management. But even if you end up creating a partition and formatting it there, it still may not be detected in the other PC by Vista Setup if those drivers are missing.

You need to have NIC driver support for any PCs that your WinPE is running on. To see if you need it at all, just go to CMD and do IPConfig. If you have an IP then you don't need to add the driver.

My co-worker is trying Windows 8 for the first time. All I keep hearing is: "WTF?" "Where is the Desktop?" "WTF?" "Where is the Start Menu?" "WTF" "Where is the Control Panel?" "WTF" Doesn't look too good.

It may be what accounts those programs are running under. Are they running on one of the local machine accounts?

Are you saying that when you install the new image, your bootscreen is missing?

Do DVDs and CDs work in it still?

Walkthrough: Create a Windows RE Image: link Deploy a System Recovery Image: link That's about it.

I usually only remove drivers if they are causing a problem.

In Local Security Policy, Security Options, try playing with the Network Access objects. Honestly, I would not have disabled any of those features, and instead created an account to map network drives with the appropriate permissions required for your tasks.

Welcome to the MSFN!