cluberti

70-260 was about as difficult as the XP test for the MCSE (70-2whatever, I don't remember and am too lazy to look it up on the mcse site). Can you find the power button? Can you create a user account? Do you know what UAC stands for? Great! You pass! I'm sure in 6 months when the tests stabilize it'll get harder, just like they did for 2000 and 2003 (so take them now! ).

ZeDMaN is correct, that is the build number.

Yes, it's going to report itself as genuine, even though it's not (otherwise why develop and run the crack, in the mind of the cracker...). Just contact MS, give them your story, and provide them any screenshots or data they need. Trust me, they're very likely to go after the guy.

If you create a batch file that does a dir /s, and output it to a text file, it should be sufficient. dir /a /r /s x:\path\to\directory\you\want\listed\ > x:\path\to\text\file.txt This will be all you need.

That's what the eval versions are for - test it, come up with reasoning why this will save you $x over y years, and (in best Vito Corleone voice) make 'em an offer they can't refuse...

Hyper-V is included unless you download a version specifically WITHOUT hyper-v. The MSDN iso includes hyper-v, btw.

In these scenarios, either I would down the original domain controller, exchange, and file server boxes and copy them each to a Ghost image file one at a time and then restore to test hardware on a separate LAN, or I would make a VM using VMWare converter of each machine and then copy and load the VHDs into my virtual server(s).

For any device to allow autorun, it must not be marked a removable device (and your USB devices are obviously removable). There are 3rd party utilities you can install on the host OS to allow USB flash drives to autorun, and there are even (somewhat expensive) packages that you can put on the USB key itself when you format it to allow it to work in XP and later systems. But out of the box, autorun for USB doesn't work unless the device itself is formatted a specific way (SanDisk keys come with some software they wrote to make this happen, for instance).

(i)yes (ii)yes (iii)and yes

Someone will come up with another, but yes, SP1 disables the current BIOS cracks. I'd call the number and rat out the seller, as he's up to no good. Your buddy got shafted out of $70, but when it's too good to be true, it usually is.

It improves performance quite a bit, tames trustedinstaller.exe, and makes it feel snappier overall with Aero enabled.

2008 brings a lot of features to the table that 2003 lacks, if you need them. If you plan these to be around quite awhile, and want to expand, 2008 is probably better long-term, but getting some training (in either) is always preferred. There's nothing wrong with a 2003 installation, but since you're going to have to forgo using SBS (it only supports one domain), I'd say you couldn't do wrong choosing either.

You should never get that error during install unless you're installing with less than the minimum requirements. Which means I have to ask - how much RAM did you give the VM?

Try NotMyFault from sysinternals. Just download, extract, go into your architecture folder (x86 or x64) and click the notmyfault.exe binary. The default is High IRQL fault (kernel), which is great - just click "Do Bug" to bugcheck the box. Just make sure the "Automatically reboot" option is selected in advanced options .

Key: HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_POPUPMANAGEMENT Value: iexplore.exe Type: REG_DWORD Data: 0

The only two problems I have with the Apple TV were the two that totally turned me off as both are "showstoppers" to me: 1. It doesn't support playback of anything higher than 720p - no 1080p (or even 1080i). 2. It doesn't support playback of anything other than MP4 or H.264 (no support for anything else, period).

Have you checked carefully your <productkey> section? It should look something like this: <ProductKey> <WillShowUI>OnError</WillShowUI> <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key> </ProductKey>

That's normal. Prodspec isn't used to determine the service pack level, not anymore. My SP4 install for both server and pro also have ServicePackNumber=0.

My French is awful, but I believe the OP is saying he had 3 XP machines come back with a virus, and he believes he's cleaned them with Kapersky, but is getting errors importing a registry file. mtbbac, if you can back up the data and reinstall Windows, that would be preferable to fixing the issue with the D: drive and registry errors. Unless this is a learning exercise, you will never be sure those machines are not infected with the virus, and as such booting with a recovery CD and backing up the data before doing a clean install of XP and patches is far preferable to fighting the errors.

This has actually been investigated somewhat, and was found that XP and 2000 had basically the same footprint and performance, and the user opted to go with XP for updated hardware and software support with XP after running nLite on the XP install to remove the unnecessary (for him) features.

Vista SP1 and Windows Server 2008 are finished, and Server 2008 was up on Connect and MSDN at approximately 9AM ET today. Vista SP1 will be available to enterprise and OEM customers but home users using Windows/Microsoft Update may have to wait until March or April to get the SP1 due to last-minute hardware/driver incompatibility issues. http://blog.wired.com/monkeybites/2008/02/...soft-set-t.html

If you could do that, why would anyone buy Exchange?

I think the XP EULA is actually pretty clear on this - let's just say you are FAR better off purchasing a Server 2003 or Server 2008 license and a Terminal Services install and CALs to comply:

Is it always the same bugcheck, or are they always different stop codes? Perhaps post a minidump or three here and see what we can find.

And in recovery mode, read only is good enough as you're just backing up data at that point to reinstall in most cases anyway.