Puggsley

Most updated files since sp2 have been tagged as sp3 because when it is released they will be included.

Already Have! (Longhorn as well)

2003 Datacenter Edition supports 168 Physical Processors and I think 672 Virtual Processors. It's only limited to that because of Hardware addressing! This would be a VERY quick machine (Expensive as well!)

Boot your XP CD and at the first promp press "r" then follow the instructions. When you get to the prompt type "chkdsk C: /P /R" After this has finished type "fixmbr". If this doesn't work then reinstall windows. If it still doesn't work after that your probably looking at a filing harddrive.

Windows Update causes more DEP errors than all other apps in the world put together. Either don't use windows update or turn of DEP!

If your OS does boot then windows will only be using the first core as it will not change hals. For best stability you should reinstall, however I recently changed a PIII to and Athlon 4800+ X2, without a single problem! Guess that was just luck!

Don't you not need a x64 host OS to run a x64 Guest OS. I know you do with Microsofts Virtual PC

If your folder structure looks like this then probably. VRMHOEM_EN \$OEM$ \I386 \win51. \win51IC. \win51IC.sp2 If not then just give it go! It Might

Both Vista and Longhorn have compatibility issues with VMWare and Virtual PC. Some builds work well, some not at all. MS has private betas of Virtual PC 2007 which corrects these issues.

Have you removed internet explorer or internet explorer core?

T-13 is when windows finishes the registry and runs any scripts in svcpack.inf. Windows SBS 2K3 hangs for about 20 mins at T-13, and this is normal. During this time you propably don't have disk activity, but your processor will be under heavy usage, as rebuilding the registry and other thing that happen here require a lot of power. If you have QFECheck on your CD, this is when it runs, along with SFC, to ensure that all updated file are legit, and the newer version gets kept if there are multiple versions of the same file. If you integrateded a LOT of updates then i would expect this to take 5-10 mins, but that is far too much.

When Blackcomb/vienna does come out, it will only have half the features planned, be 2 years late, and will be the most unstable os ever! Microsoft cannot cope with upgrading products, have you seen how many redundant files there are in XP? To make vienna a success they need to start from scratch, and remove the thousands of lines of code that don't do anything.

Could you not copy a dos floppy to the flash drive, then edit autoexec.bat? to run winnt.exe (Setup App intended for dos prompt). I managed to do this for win 98se, but i know a few of the dos files need tweaking a bit. Your flash drive should be formated as fat, not fat32 or ntfs as dos does not support these.

run "regsvr32 C:\WINDOWS\System32\comctl32.dll" You might also need to do the same thing with comctl.ocx

Is there anyway of setting this using nlite, or a reg tweak i could integrate into the cd.

This is probably a corrupt driver. If not then you have bad ram, but it should affect the host OS as well so its unlikely

If you want to completely disable it, remove the file sfc.dll, sfc.exe, sfc_os.dll, sfcfiles.dll. I have never found a problem by doing this, and it ensures that it can not run.

This is most likely to be a hardware problem. Try installing with a normal cd to find out.

textmode drivers are used when you boot from cd to format drives and copy initial files. PNP Drivers are the drivers you use everyday when in windows. If the image is too big to put on a cd then us a dvd.

From MS Website: "To enable verbose status messages by using Registry Editor Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. To use enable verbose status messages by editing the registry, follow these steps: 1. Click Start, and then click Run. 2. In the Open box, type regedit, and then click OK. 3. Locate and then click the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System 4. On the Edit menu, point to New, and then click DWORD Value. 5. Type verbosestatus, and then press ENTER. 6. Double-click the new key that you created, type 1 in the Value data box, and then click OK. 7. Quit Registry Editor. Note Windows does not display status messages if the following key is present and the value is set to 1: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableStatusMessages" I think if you set verbosestatus to 0 it will turn it off

I've had this problem when integrating nForce RAID Drivers. They are not compatible with some other RAID drivers I integrated. This wasn't an nLite problem, and I never found a way round it

I had the same problem with an old version of nLite, but it only ever happened once, re-ran nlite with the same settings file and it worked fine!

There is a tweak in sysoc.inf which allows you to see these options in Windows optional components, but you can see them and they don't install though..

the 180 day trial is genuine. I had an x64 trial from MS which actually expired. Been 64bit, and made by MS i was amazed it lasted 6 months!

Most windows images/icons are in shell32.dll However I dont think this one is!