cluberti

Make sure you read the DISM documentation, specifically look at the /Add-Package command line. You would mount the WIM file and image number, then use /Add-Package to add the .msu packages to the .WIM file, then unmount the WIM. To gather information on a .WIM file (image index, names, etc): DISM /Get-WimInfo /WimFile:<DriveLetter:\full\path\to\.wim\file.wim> To mount a .WIM file: DISM /Mount-Wim /WimFile:<DriveLetter:\full\path\to\.wim\file.wim> /index:<1,2,etc> /MountDir:<DriveLetter:\path\to\temporary\mount\folder> To add .msu packages to a mounted .WIM file: DISM /Image:<DriveLetter:\path\to\temporary\mount\folder> /LogPath:AddPackage.log /AddPackage /PackagePath:<DriveLetter:\full\path\to\folder\containing\all\msu\packages> To unmount and commit the changes to the .WIM file: DISM /Unmount-Wim /MountDir:<DriveLetter:\path\to\temporary\mount\folder> /commit You can find all the DISM command-line options here.

Or you could put it in the same place, but in HKLM, and have it set for all users - far easier than mucking about with the user's registry (or SID registries for each user on the box).

In my experience with XPe, you likely will have to do that pre-image, so if you're already past that point you should start over to save yourself the headaches. However, if you're having any other real image issues with your embedded install you should contact your TAM or the OEM or VAR you got XPe from and get the support you paid for from the VAR and/or Microsoft .

Is there a reading problem here lately? [banned].

Read the rules before posting folks. [banned].

Yes, you will likely need to apply the post-SP3 updates again, as unlike the Office 2007 setup, the 2003 setup routine does not automatically update binaries from the install media with binaries for updates that are already installed - you'll end up with a mix of patched binaries for the other components installed, and Outlook still running the SP3-level binaries.

I know getting Office 2000 and Outlook 2000 in particular to work on Vista was problematic. It's on the compat list, but in all honestly it's not entirely straightforward. I found nothing officially, but I did dig up a blog post that talked about the steps needed to actually get Office and Outlook 2000 to work properly on Vista systems, so you might want to have a look and see if any of that applies, if doing some or all of those steps help, etc.

Error code 32 when accessing the filesystem is usually one of two errors, ERROR_SHARING_VIOLATION or ERROR_NOT_SUPPORTED. Given that this is a download manager and likely writing and combining multiple chunks of a file into one larger file during downloading, as most do, I'd say it was most likely the former. Which means some other process running on the machine managed to get an exclusive lock on the file whilst the download manager attempted to read to or write from one of it's files on disk, or the download manager itself messed up the sharing mode it passed in during a ReadFile or WriteFile operation, thus screwing itself up. If you download to a folder on a hard drive that you have configured any antivirus, antimalware, etc software running on this machine to explicitly not scan, does the problem reproduce?

You'll have to get this person to define "properly". If he means "works properly, browses web pages, and loads activex controls just like XP and 2000", then the statment is patently false - IE6 was ported back to Win9x properly. If he means "isn't as secure on Win9x or Windows 2000 as it is on Windows XP SP2 and higher", then he is somewhat correct. There are additional security mechanisms in place that are specific to running IE6 on Windows XP with Service Pack 2 or higher that do not exist downlevel in IE6 on Win9x or Windows 2000, although this doesn't make IE6 "SP1" (which is what IE6's version is for Win9x and Windows 2000) any less secure that it was when it was originally built and ported back in August of 2001 - it just makes it not as secure as it would be if the user was running IE6 on Windows XP Service Pack 2 (this is IE6 "SP2", and will indeed only run on XP systems). Your unnamed source is going to have to provide some proof of this - I believe he's probably comparing IE6 SP1 on Win9x with IE6 SP2 on Windows XP SP2, rather than comparing IE6 SP1 on Win9x with IE6 SP1 on Windows 2000 or Windows XP RTM or SP1. The OS shell depends on IE6 to be installed to perform functions, NOT the other way around - IE6 will behave similarly on an NT-based platform like Windows 2000 or Windows XP as it would on a Win9x platform like Windows 98 or Windows ME, because the browser functionality itself is NOT dependent on the underlying OS.There's not much more to discuss - the shell relies on IE, not the other way around, which is the common misconception most people have about the integration of IE into the Windows OS. A lot of people assume IE relies on Windows components for functionality, and the truth is actually the reverse. Sure IE6 relies on OS APIs to handle operations like writing files to disk, accessing the sockets layer to transmit packets, etc, but so does every other application that runs on Windows - IE is not special in this regard. However, IE self-contains all of the browsing functionality needed by the browser, and as such I cannot understand how one could assume IE6 is less secure on Win9x than it is on Windows 2000 or Windows XP RTM or SP1. There is no *browsing* feature that IE6 does on Win9x that it does *any* differently on Windows 2000 or Windows XP RTM or Windows XP SP1. With that, there really isn't anything further to discuss about the initial post. If there were specific questions, or specific points of statement of fact to address, we could probably discuss further. Otherwise, the answers here are likely the best answers you're going to get.

OK, if Outlook is freezing, can you get a hang dump of outlook following these instructions and post a zipped copy of the resultant .dmp file somewhere for us to download and look at?

Consider using MDT 2010 or nLite to create your installation media, application installation, and driver and hotfix package integration. I was speaking to where in the office installation media structure you placed the MSP, not where on the XP install disc. If you need unattended help above and beyond what to use to create your unattended DVD, we have an unattended guide here that you should be reviewing.

Unless the program is installed per-user (most .net applications are per-user, but most "Regular" apps are per-machine), no. Applications installed per-machine will show up for all users of the machine. You'll probably need to provide more information if you want specific comments.

Trial software is just that - if you decide to purchase, you MUST reformat and reinstall with non-Trial media. However, "regular" media has a 30-day grace period that doesn't require a reformat if you choose to purchase - you just enter the product key from installation media and activate.

Does it repro in audit mode?

Same here, Vista's taskbar is 30px at 1920x1200. Win7's taskbar is 40 pixels on large icons, and 30 pixels on small icons at that resolution by default as well. I believe this only changes if you've modified the DPI settings (it does get larger with a higher DPI set).

Indeed it's artificial from a functionality standpoint (I was able to get IE8 working on W2K with some hackery during the betas), but Microsoft doesn't want to pay to support writing new code on a platform they've already retired to their extended support sustained engineering group (read security updates but no bugfixes). If there are bugs introduced to the platform with IE7 (and trust me, IE7 nor IE8 after being hacked down worked well, but they did work) then Microsoft would have to pay someone to follow up with code fixes, make sure it's tested across the myriad of platforms they support, possibly multiple patch levels for systems that could apply the updates, etc. Even if IE7 had released in 2004 or 2005, we probably wouldn't have seen it for the platform - IE6 on W2K didn't get any of the XPSP2 updates that IE6 got on XP, and that was actually done while W2K was in mainstream support and was getting new packages.

It doesn't appear to have feature removal capabilities, making it on par with the free MDT 2010 from Microsoft that does everything this package does, but it's free.

Welcome back dude To the OP - I had that on a particular machine I had built years ago, and it cropped up about a year ago. It was indeed interference, and I could actually hear it until the monitor was off. Replaced the monitor, and all was well.

No. You're welcome

It looks like this starts being checked after installing MS06-021. It's not documented, but it seems like most of the Feature keys that procmon shows IE checking are not publicly documented. Most of these are built to fix specific bugs for customers that create support cases and aren't documented publicly anymore, so this is not surprising.

It's actually created during setup - I worked on a Windows 2000 .INF file that would do a "bare metal" WMI install, basically causing the setup engine to re-run all of the WMI portions of windows setup, but it was never 100% effective and would fail a few times out of 100. I never did get it working with Windows 2003, as it seemed there was even more to the setup routine that I hadn't been able to figure out, but I do know it was still entirely a part of the Windows setup routine that created the service reg entries and placed the binaries on disk (no amount of re-registering files is going to get the service created).

The answers you were given are the correct, legal answers. The Windows 7 DVD is copyrighted material, meaning you get it from Microsoft, directly from an OEM, from an authorized reseller (retail or otherwise), or you don't get one. There are obvious illegal ways to acquire a Win7 ISO, but they won't be discussed here as per the forum rules. [Closed].

Correct - you can have multiple member servers in a 2003 SBS domain, but none of them can be domain controllers.

Note on the file list, specifically the dx*.sys files, that they're actually IE interfaces to directx to draw components, they're not directx binaries themselves. Be careful omitting binaries (just as you are with including binaries) when copying updates, as the updates are designed to be used with all binaries shipped in the package. Just FYI, the dx*.sys files are NOT directx files, but they contain the "glue" for IE to call and use directx (when drawing activex controls, etc).

Unless the drivers for the sound card really are capable *and* configured for 5.1 (or more) and not just emulating stereo across a multitude of speakers, you aren't going to get surround sound.