Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by Puggsley

  1. heres the support,

    Xp home - 1 physical 2 virtual

    Xp pro (and 64 bit) - 2 physical 4 virutal

    2000 pro - 2 physical or 2 virtual

    2000 server standard - 2 physical or 2 virtual

    2000 server advanced - 16 physical or 16 virtual

    2003 server standard / small business - 2 physical or 4 virtual

    2003 server enterprise - 64 physical or 128 virtual

    a virtual cpu would be from hyperthreading, not dual cores.

    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!)

  2. 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.

  3. 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.

  4. 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:


    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:


    I think if you set verbosestatus to 0 it will turn it off

  • Create New...