cluberti

If you look in the options, under the plug-ins tab, I think, do you see any of the codecs/plugins you installed? You'll probably see them in the 32bit player, and perhaps not the 64bit...

Well, since the codecs are 32bit, how is the 64bit WMP going to use them? If you install x64 codecs, then it would work.

If you're having trouble, did it create a .log file in the \Windows\ folder (usually KB947864-IE7.log) that we can look at?

You'll need to install WMP11 and IE7 hotfixes not included in SP3. However, for IE7, at least, it's as easy as installing MS08-024 and you're up to date.

Assuming your key is valid, if you can't reactivate it after getting the code, perhaps you should be telling them this (they should be able to see it if you keep calling in on the same case #) - always try it when you have the rep on the phone. If it fails again, you'll have to ask them for another product key entirely.

Would you be able to get a hang dump of the application when it's hung?

Hmmm..... What happens if you run dcdiag /v on one of the DCs in each domain?

From the microsoft.com piracy site, under "Scams, non-Microsoft downloads": Since I know you're from the UK, and Microsoft EULAs apply to you there, this is definitely not legal. If Microsoft would shut down a group such as autopatcher for re-releasing HOTFIXES, why would you even think that hosting the FULL OS is even at the very least OK? Warez, closed.

Because Ghost editions require purchasing the Ghost software + licenses per seat for usage. WDS, WAIK, etc are FREE (you've already bought the server and client licenses, why pay more to use Ghost when you can use something you've already paid for, i.e. WDS). That's likely why. I don't know if there's an "advantage" per se in using Ghost over WDS, but WDS is cheaper and is produced / supported by the same company that makes the OS you deploy with it, and can be integrated with things like System Center.At least in this case, if there's a problem, the vendor (Microsoft) can't blame someone else if things fail, whereas I have gone through the "It's a Symantec problem / It's a Microsoft problem" vendor finger-pointing tapdance before when problems arose with Ghost (it ended up being a Ghost issue, but that's neither here nor there).

I've managed to get a full Vista DVD and a full Server 2008 DVD on two separate 4GB USB sticks, following this method. Much easier than the one laid out in the Vista resource kit .

Well, that could be for one or more reasons - could be that the USB bus is causing the slowdown, the USB stick could just have a slow memory controller, it could be the disk controller, etc. Is it fast when you build from a CD or DVD with the same Vista image?

That was premature I cannot get the task to accept the password I used on the old PC! -- Terry, East Grinstead, UK Is the account on the new PC you copied the task to using the same username and password combination?

Vista and Server 2008 are built from the same OS build tree - therefore, the Vista SP1 codebase is also the codebase that Server 2008 uses, hence the OS tree is at SP1, and Server 2008 will show as being "SP1", even though it's an RTM product. One can insert any statement or joke about Vista RTM being released too soon, and that they should have RTM'ed at what is now SP1, but nonetheless, 2008 and Vista SP1 are the same, hence 2008 "SP1".

Best thing to do would be to go through the wizard, select the option to activate over the phone (you'll get phone #s to call), and call the # listed for your region. It'll get you in touch with someone who can allow you to re-activate your key.

Yes, and correct . Used them for homebrew apps anyway.

http://www.msfn.org/board/Tutorial-Build-W...te-t114957.html It's for x86, but it should be basically the same for x64.

It's the KB for XPSP3, which means it will be updated to the final when final is available (already is, even though the documentation isn't updated yet for the KB). If you have the XP SP3 installer for KB 936929 and it's build 5512, you have the final, not an RC.

Not a problem.

Actually, this is one place where slipstreaming into an SP1 or SP2 source is "better" than RTM. I've found that if you slipstream SP3 into an RTM source, you need to provide a product key, always. If you slipstream into an SP1 or SP2 source, you can do the product key bypass...

BTW, kathpal.kapil, keep warez talk away from MSFN or find yourself banned.

Did you slipstream on a Vista or 2008 box? Also, try an SP2 source to slip into...

A little odd, yes, but how many normal people even see the Windows setup routine (and no, those of us here who do this thing regularly are NOT normal )? I can bet it's probably very low priority, if tested at all.

If all you're doing is slipstreaming a service pack, you don't need nlite for that - you can just run "WINDOWSXP-KB936929-SP3-X86-EN.exe /integrate:<source path folder containing i386>" (assuming englsh here, replace "-EN" with your language if not english). For example, I copied my RTM CD source to C:\TEMP\xpsp3, and then ran WINDOWSXP-KB936929-SP3-X86-EN.exe /integrate:C:\TEMP\xpsp3. From there, make the bootable ISO as necessary with your tool of choice (there are many, I won't go into them here). As to the structure, they're all basically the same (only tabletPC and MediaCenter editions have "extras" that aren't in XP Pro directly, but they're strictly additions and don't change the "base" XP Pro OS at all.

True. Although considering they couldn't really run anything not inbox, that's not much use .

I've found that I need to install IE7 (at least with 1.7.5) and WMP11 as GUIRUNONCE items, and then install 947864 on a subsequent reboot. Otherwise, I get wierd behavior with Internet Explorer (the icon in the start menu will only open Internet properties, IE opens and closes immediately with an error in ntdll (which there indeed is), etc). However, for now, GUIRUNONCE (with a cmd that sets a runonceex to install patches after another reboot) works fine, and is probably just as quick.