Tripredacus

In order to do this, you would have to customize your WinPE and get the syswow or Win32 subsystem support into your PE. Or you can just do what I do, use x86 WinPE for systems that need 32bit software functionality.

Wow that is definately way too long. The longest I've seen was 5 minutes, but that is because there are a lot of programs installed. I do know of a sysprep delay issue with an updated IE installed but I can't seem to find it. You should look in Panther to see the log file, maybe it is encountering some problems (warnings) or it could be you just have a lot of files or programs installed.

A similar question was brought up here:

This can't seriously be "new" can it? Conficker used this vulnerability in version 2...

Welcome to the MSFN! If you are going to post trial software, best to link to the official website: http://www.quetek.com/prod02.htm

Welcome to the MSFN!

Whether it is normal or not, who can say. I would say that I never like the idea of using a glue gun inside a computer, but then again I am also not fond of the form factor arrangement that Shuttle uses. That wire on the top, looks (the picture is blurry) that it may be a 4pin that a floppy drive or some video cards use. If you do not have a floppy drive, that may be why it is not connected to anything. Here is a picture of what I mean: http://www.playtool.com/pages/psuconnectors/floppy.jpg

WDS does not natively support Windows XP. Are you using mixed mode and RIS for XP?

Sorry I didn't get a reply in before all these others. Yes there is a way to do it. Try these steps out: 1. Deploy the image. 2. Take the HwID and search the INF folder for it. The file you are looking for is OEM*.INF (where * is a number) 3. Mount your windows image 4. delete that INF file from the stored image (verify it is the same one, should be, but best to be safe) 5. Redeploy. That SHOULD do it. I've had to do that in the past after accidently injecting the wrong drives into images. Had to find the INF name and take it out. This is the manual way, and only way to take drivers out of images if you didn't use DISM to put them in there. Also, deleting the INF will stop the device from being installed, but its support files will still be on the system but that shouldn't be a problem.

Welcome to the MSFN! Check out our forum rules, especially Rule 11.

Indeed!

This driver appears to be a virtual device driver that is included in some video codec packs. Did you include any software into your master image?

You didn't post your operating system. Server 2003, for example, has shell32 marked as a protected system file. So as soon as you change it, Windows will revert to the original copy.

XP Downgrade Rights comes in different types. One of those types does indeed have no EOL status, but others will expire very soon. can you explain this a bit more? Well, not entirely. But for example, for Vista SP1, I ended up using this: http://www.microsoft.com/downloads/details.aspx?familyid=b0c7136d-5ebb-413b-89c9-cb3d06d12674&displaylang=en

They definately look pretty cool. As for using them, see if you can find them on newegg or amazon and if there are any user reviews of them.

Do not make posts or topics in all caps. Please read the forum rules.

This happened when installing the program? Did you download it from Apple?

Silly you! Resource kits usually come as an additional CD-ROM you can get separately. Sometimes these also came with MSDN or Technet subscriptions. As for downloading it... here is where you can get sysdiff for Windows 2000: http://support.microsoft.com/kb/927229

Is it at all possible that, at some point during the test, it is reading from the Cache or from memory instead of the physical disk? That would explain a speed increase at least. I moved all these posts out of the WEI topic.

I've heard that you can use 7Zip to modify WIM files but is there a specific reason you aren't using WAIK to do this?

I removed your duplicate post. Sometimes you need to import the disk to see it. Oh but its a basic disk not dynamic... What file system is on that drive? Here is some info on Disk Management that might help: http://technet.microsoft.com/en-us/library/cc771775.aspx

No, the binaries I end up using are different than the ones used for slipstreaming.

Well I ended up building the app without doing the things that the tutorial wanted me to, such as setting a custom icon and entering the versioning info.

I was thinking of getting this, but I'm going to wait for RTM as the image update instructions might have changed by then. I can only hope it is as easy as the Vista SP1 update, otherwise I'm going to have a long time to rebuild all my images!

To clarify, 2000 has been EOL for a long time, this is for extended support. So if you are still using 2000 in the enterprise, you are officially 100% behind the times!