Tripredacus

This is a last resort option really...

Welcome to the MSFN!

I can help with some "great info" http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules

I must add that I haven't tried to make a WinPE 4.0 yet, mostly because I don't see a reason for it. But I was disappointed that in Windows 7 SP1, you couldn't "make" the PE anymore, instead you got pre-built ones. Maybe that is for the better.

If it sticks to the plan, WinPE only will get updated when a new version of Windows, or a Service Pack comes out. That's been the way since Vista, but I'm not sure how WinPE 1.x related to XP and earlier OSes.

Some of that XML looks odd to me. I have heard similar stories of people trying to get Altiris to do this. I imagine your company doesn't have a Support Agreement with Symantec?

Of course MS will recommend the product that costs more! Maybe, but MDT can install programs too. I'm not sure about the "thin" image you mean.

PunkBuster is kinda hard to get rid of, but I wouldn't worry about it. It is the anti-cheat engine that runs in the background when you play some online games. Quake 3 uses it for example. While most games will open it, they rarely (if ever) will close PB down when you exit. But if the game is not running, PB doesn't do anything and shouldn't cause you any performance problems.

Well this isn't the first time I've heard of people finding things on their desktop that magically show up like this. Last time someone was asking about something similar, I recommended using the AU3 (AutoIT) Windows Info tool. This program is normally used to get detailed info from applications so they can be automated, but may also be able to tell you more info about whatever that is. You just drag the crosshairs onto that dot to see the info. You can't download the tool separately, but is included in the main installer download. http://www.autoitscript.com/site/autoit/downloads/

It is possible this issue exists for Vista as well but I did not test it. The Intel X79 SATA RAID driver (iaStorA.inf) current version for Windows 7 x86 is not compatible across all platforms. Problem description: After injecting the RAID driver (iaStorA.inf) with DISM into a 32bit Windows 7 image, after deploying the image first boot up returns a STOP error 0xC000035A. Boards tested: DH55TC = 100% replication using IDE and AHCI mode DH61BE = 100% replication using IDE and AHCI mode DX79SI = intermittant DQ67SW = 0% replication using AHCI DH67CF = 0% replication using AHCI DX79SI intermittant results, note that no changes were done to hardware (BIOS) or to the test images (Drivers or Updates) to get these results. - IDE and AHCI with 32bit worked 100% of the time. - RAID using JBOD failed (This new MSC does not support JBOD apparently) - RAID using mismatched drives in RAID0 on 6GB and 3GB ports failed. - RAID using mismatched drives in RAID1 on 6GB and 3GB ports worked. - RAID using matching drives in RAID0 on 6GB ports failed using Windows Setup DVD and F6 driver. - RAID using matching drives in RAID1 on 6GB ports failed using Windows Setup DVD and F6 driver. - The above RAID tests (except JBOD) that failed started working a few days later with no changes. Drivers used from Intel's website: - RSTE_3.0.0.3020_F6-Drivers.zip - RSTE_allOS_3.0.0.3020_PV.exe Note I did mention the older model Intel boards above. For the H55 and H61, STOP error for iaStorA.sys would appear if the image was deployed to it. It is a curios error since those boards (like the H67 and Q67) do not use the hardware (PCI\VEN_8086&DEV_2826&CC_0104) that iaStorA.inf supports. They would use ibexahci.inf or ibexide.inf (and ibexid2.inf) instead. So the first idea is to use DISM to take iaStorA.inf out of the image. Unfortunately, this resulted in those boards (which the image previously worked on before adding iaStorA) would then boot to a STOP 0x7B after deployment! So it was much safer to keep the iaStorA.inf in the image. Now as to why the error occurs on certain boards, it is because the driver is written incorrectly! Apparently, this isn't the first time this type of thing has happened. In fact, an older Intel driver (iaStor.inf) from 2009 had this same problem! Take a look at this from the iaStorA.inf 32bit: [Manufacturer] %INTEL% = INTEL, NTx86.5.2, NTamd64 You can see here that this driver is not (truly) compatible with Windows 7 x86! DISM doesn't seem to care about the wrong architecture being present, which I hope gets fixed someday in the future. The reason the STOP error occurs is because the 32bit driver appears to have been created using a 64bit INF as a base. The error is due to Windows being instructed to install the driver as 64bit on a 32bit OS, even though the actual .sys files are 32bit files. Since removing the INF with DISM after the fact does more damage than you would expect, the only current workaround I've found is to rename the INF instead. Instructions for that: 1. Mount image with DISM 2. Go into mount\Windows\inf 3. find the oem*.inf filename 4. Rename to oem*.bak (where * is the number in the filename of course! ) 5. Unmount/commit It may be possible to add the appropriate OS code into the Manufacturer section of the INF to fix this problem. I have not tried it, since there are instructions for installing it into an x64 OS in the INF as well.

What OS?

The New button is only available if there is enough space left on the disk to create a new partition. What size hard disk are you testing on?

A "whether you like it or not" type of approach only works when there is one option.

Many things have changed between XP and Windows 7, especially how profiles are used.

USB on Windows 7 can be flakey at times. I have some devices that won't work on certain ports. Are you using the Safe Remove Hardware function prior to unplugging the device?

Welcome to the MSFN!

Welcome to the MSFN!

Tripredacus is definately a Transformer but is also a faction. Tripredacus (Tripledacus in Japan) is a combination of 3 robots, each with their own personality: Cicadacon, Seaclamp and Ramhorn. Originally I picked the name after trying to register a domain name and trying 200 other Transformers name unsuccessfully through (then) Tucows. Tripredacus worked and I picked that, and then took up that name and things went on from there. K-Mart-ian Legend is a joke and a joke that I did not even come up with. Quite a few years ago, someone had defaced the Gobots page on Wikipedia, relabling instances of the term "Gobots" to "K-Mart Transformers" playing on the idea that they were an inferior product to Transformers. Another term found on the defaced page was that the "Gobots are the Transformers of K-Mart-ian Legend." I had reported this deface to someone else at the time who got it reverted, prior to me having an account on TOW or knowing how to use that site. You can see it in the revision history of the Gobots page (2006) or this history: http://en.wikipedia.org/wiki/K-Mart_Transformers After this, I was jokingly referred to as the K-Mart-ian Legend, so I ended up using that title everywhere. The character in my avatar is a Transformer, but it is not Tripredacus. The reason for this is that the Tripredacus gestalt didn't really have any good art representations until fairly recently. I didn't want to use one of the individual members since I related to the combination of personalities of the character rather than just one part of it. Here is a picture of what the Tripredacus gestalt character looks like. The character in my avatar is actually Ravage, who was one of the cassette characters that accompanied Soundwave. When Tripredacus made its first (non-combined) appearance in the Beast Wars "cartoon" series, Ravage was an agent of that organization. You can use that image on another forum, I have no problem with that.

There shouldn't any situation where your PC would boot a USB partly then failover to the HDD. Unless you aren't describing it properly. I've worked on an HP Mini so I know it doesn't have a ODD in it. Are you using a USB key to boot your PE or using a USB CD drive? If using a USB key, you may run into volume size limits based on what file system your PE is built. Try using a 1-2GB (max) size USB key if possible. If you have a USB CD drive, I'd try to boot up memtest in it.

What is the model for this notebook?

Look at your picture again... To me it would seem that the path would be .\Deploy\$OEM$\Operating Systems\Windows 7 x86\Sources\install.wim.

Well the 0x7B is related to the Mass Storage driver not being present. So you say that it works if you use an image that just has the Mass Storage drivers, but stops if you add sound and video?

You should be talking to your domain admins/helpdesk for this question! We have no idea what kinds of software or GPOs you could possibly have.

You only have to worry about a non-standard MBR if your PC is configured with dual boot. If your other partition is just a data partition, you shouldn't worry. The only exception is if there is a recovery/service partition which would technically make the system be a dual-boot anyways. Swapping drive cables is a simple enough fix to try. I've seen that happen as well, and especially for SATA cables that do not have clips or the soft orange ones.

I never researched it myself, but I have a server that has this problem. It doesn't have Symantec anything on it. There seems to be a few different attempts or solutions for this, try these out: http://windows.microsoft.com/en-US/windows-vista/fix-a-corrupted-user-profile http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/5ec0b949-effa-4e30-ba09-dc948a4c7a8b