Tripredacus

Considering that XP doesn't support DirectX 10, I'm going to say Vista or 7. I guess some people can hack DX10 to work in XP but I never trusted that idea.

My first dumb thing was with my first computer! That makes sense right? My first PC had a 30MB HDD with WFW 3.11 on it. It also was partitioned to J drive letter for some weird reason. So I decided to delete the stuff that was in all the other partitions (besides C... I wasn't that dumb) and then I'd delete those partitions and extend the C volume. I remember seeing that there were other Windows files in those partitions but thought they were a backup or something. Nope... They were shadow copies. Alas, when I rebooted I got a nice error... to which I formatted the drive and reinstalled WFW.

Imagex would be faster for sure, but Setup can install a captured WIM as well. That is how I use it. The answer file is likely optional, but even if you have captured an image after using sysprep /unattend switch, Setup ignores that answer file. For example, even if your XML only specified the Locale settings (to hide the language select page of OOBE), after Setup applies the image, you'd still see that page. So if you didn't have any special settings, you don't even need to specify a custom tool or have the answer file. Just overwrite the install.wim with your custom WIM, but it still needs to be called install.wim. The only reason I needed to come up with this was because I needed the image in the recovery partition to deploy and then boot to the desktop. If the image is supposed to boot to OOBE, I don't use the custom tool option.

#3 is a program. You should not try to slipstream its driver in, instead install this program. It should give you the HD monitor when your drive type is set to AHCI or RAID. Do not use it if your drive type is IDE, since sometimes the program will crash. For the USB3 driver, grab this: USB3 Renesas from Intel. Extract the EXE with WinRar. In the Files folder, there are the x86 and x64 folder. Inside are the driver files you need. Make sure to use both the 'hub' and 'xhc' INFs because after the drivers for the controller are installed, a "Hub" device will appear and be flagged. As you can tell, I made that mistake already. As I said for the Intel Chipset, install it on something. Then there will be a C:\Intel\logs folder. In there is a log file that shows what it installs. Most importantly, it tells you where it extracts the driver files. Someplace near the top is going to be: [EnumDev] [GetDrivers] [Find INFs] Found INF = C:\Users\LIOKAI~1\AppData\Local\Temp\IPMx2\All\5000XZVP.inf Hello there drivers! of course you'll probably just need to grab the "All" folder. Its really the easiest way to get the files, and updating a chipset driver on some random PC isn't too bad either.

This is a fine place. If the troubleshooting moves into another direction and moving the topic to another area provides better visibility, it will be considered.

Well there are multiple ways to do it. By injecting the updates into the WIM, it will shorten your deployment time. Regarding hotfixes, noticed I removed the link in your post. See the forum rules:

You can make WIMs for XP but you can't service them. Your should probably look at MDT 2010 http://technet.microsoft.com/en-us/solutionaccelerators/dd407791 Cluberti has a 3 part series on how to use MDT http://www.cluberti.com/blog/2011/06/23/mdt-for-the-smaller-guys-part-1/

http://yourbrowsermatters.org/#/home I wanted to add while this would be a cool idea, it seems to rely too much on browser detection. As an example, i get a 2 with Firefox 7 and NoScript allowing access from the site. But if I disallow scripts from the site, I still get a 2. And some of the "failings" aren't fails, such as: Actually it does, because I have it enabled. It does with NoScript. Although Photobucket has gotten annoying lately with the XSS they started using about a week or so ago. Of course IE9 tests with a 4 out of 4... If I change my User Agent in Firefox to IE8, I get 3 out of 4. It would be better if it actually did test browser security, rather than just reading User Agents and returning static info about them.

My Win7 PC gives me the ability to "eject" my video card... Is this drive connected to the motherboard or an expansion card? What is the model of the board or card? Is that HDD your boot volume?

You can get to all of these drivers using WinRar with the exception of the Intel Chipset. In order to get that one, I will install it on a PC. When it installs, it will extract the drivers out and put them in a temp folder. The ones you will probably need are in the folder called "ALL" however if you install it on an XP system you can check the log file to see which ones it uses. MSI is usually a couple versions behind, you may want to get the 1030 Chipset driver from Intel.com. You can find it by looking for drivers of any 6 series board in the download section.

If you are going to use these updates and drivers every time, you can just put them into the image using DISM. DISM Add or Remove Packages Offline DISM Add and Remove Drivers Offline Hotfixes are not redistributable.

An x86 boot image can install both x86 and x64 using Setup for both Vista and Windows 7. You can also use an x86 WinPE to capture and deploy x64 images using Imagex. Anyways, just try a 32bit one. The only reason I ask is because of your server. I don't know if it has anything to do with it.

Maybe if I can see some device details or INFs. Sometimes a name may change with just a hardware revision.

Vista RTM was a shock since most people were buying cheap PCs at that time. Cheap PCs = low end hardware, which didn't mix well with Vista. The Service Packs have helped it out greatly.

Are you using a custom app for deployments, MDT LTI/ZT PEs or Windows Setup?

Shizuo vs Shizor - The Duty

Its worse on non-technical forums. I have given up trying to help people there. The commonly accepted answers are - you have a virus - reinstall windows - some other nonsense - none of my answers

Maxthon, a custom IE shell, supports SOCKS5 Proxy Authentication. Website: http://www.maxthon.com/ Documentation: http://www.bpsocks.com/maxthonmanual.pdf I used to use Maxthon back in 2005. I don't remember why I don't use it anymore. I'm sure there was a reason for it.

Starting your PC on fire... Easy way: have a certain part of the HDD touching the chassis and turn the PC on. Like touching one of the chips. Did that once by accident. As far as the USB issue... Not all case manufacturers are the same. I can't remember which one it was... it was either Chenbro or Inwin... their budget line didn't have their USB headers keyed. While most would say "OK i'll have to match up the colors in the book" which is fine... for older MSI boards this was a problem. Take your average assembler (who isn't technical which might also seem strange) and a non-keyed connector and a fault that spans all boards. Normally, if you hook up the USB front panel backwards on the board, USB should just not work. This is true on Intel boards. But on MSI boards it causes a short. The end result is the USB chip starts on fire (pretty colors come out of it) and also your USB key pops. We got real careful about doing it right and I haven't heard about it in awhile. Either way it gets annoying especially when your expensive HASP keys pop and melt on you.

The guides for setting up a PXE for WIM deployment (WDS) vary depending on what the server is. There are guides for Server 2003, 2008 (R2 is the same as RTM) and even Linux. Also, need to know what OS you are capturing images of?

Back to this again? If you want to keep your HTA on the network drive, that's fine. Try copying it to the RAMDISK and run it from there.

What media did you use to create the capture image? Try creating a 32bit capture image instead.

Many corporations will wait until the last possible minute to upgrade, when support runs out. I know a few companies that always wait... they waited for 2000 support to go away before moving to XP, and are waiting for XP support to end before going to Windows 7. For OEMs, the support ends WAY earlier than for Enterprise. As an example, Windows XP support ended in April 2009. So its partially true that OEMs drive people to upgrade, but its really a partnership with Microsoft. It might seem like OEM doesn't have a choice (well want to stay in business? ) but the partnership really shows during the alpha and beta period of a new OS.

What's all this jibber jabber?

Welcome to the MSFN!