One Last Vista Build Before RTM

Brad Goldberg, General Manager of Microsoft’s Windows Client Business Group, would, no doubt, prefer not to be called a horse.

But Goldberg did say on September 29 that Microsoft has one more EDW (External Developer Workstation) build of Vista slated before the product RTMs (releases to manufacturing). That means one more fairly widescale test release. Then it’s soup, Goldberg said.

As of today, Microsoft believes it will make Vista available to businesses in November 2006 and release the product through all other channels in January 2007, Goldberg reiterated. Yep, it’s all systems go.

Anyone want to bet on the business launch date for Vista? My guess? November 9. Why? Because it’s a Thursday (traditional Microsoft product launch day) and by then, we’ll all supposedly be ready for a new day.

Forum: Discussion Thread
News Source: ZDnet

GSM-и във въздуха

България да разреши използването на мобилни телефони в прелитащите над страната самолети. Това е поискал консорциумът „Аеромобил“ на среща с членовете на Комисията за регулиране на съобщенията.

Cisco Systems ще прави фонд за Балканите

Американската компания Cisco Systems има намерение да създаде венчър фонд (за рисков капитал) за Югоизточна Европа, който ще подпомага малките и средните предприятия, работещи в областта на софтуерната индустрия. Това е съобщил главният изпълнителен директор на компанията Джон Чембърс по време на срещата му с премиера Сергей Станишев, предаде правителствената информационна служба.

В момента Чембърс е заместник-председател на Националния консултативен съвет по инфраструктурата към президента на САЩ Джордж Буш.


Processor, memory may marry in future computers

On Tuesday, Intel showed off an 80-core processor at its developer forum taking place in San Francisco this week and one of the prominent features of the chip is that each core is connected directly to a 256MB memory chip through a technology called Through Silicon Vias, or TSV.
The memory wedded to the processor cores could constitute the entire memory needed for a computer, Intel CTO Justin Rattner told in an interview during the Intel Developer Forum. TSV could be used in a variety of chips, not just the 80-core monster. As a result, computer makers, when building a system, would get their memory when they bought their processors from Intel. They would not have to obtain memory chips separately from other companies like they do now.
Wedding memory directly to the processor would have huge performance benefits. Currently, memory and the processor in Intel-based computers exchange data through a memory controller, which moves at a far slower rate than the processor. It’s one of the big bottlenecks in computer performance. TSV, which displaces the memory controller, would shuttle data far quicker.
View: Full Article @ CNET

Стартират регистрациите на .MOBI домейни!

От 26.09.2006 стартират регистрациите на MOBI домейни, като до 08.10.2006 е обявена промоция за отстъпка от $5.00 на година!
.MOBI е новото разширение за домейни предназначени за мобилни устройства.
dom.BG първи в България предлага подобни регистрации.
За повече подробности за условията вижте:

Windows PowerShell RC2 Now Available

Microsoft announced the availability of Microsoft Windows PowerShell RC2, the command line shell and scripting language that helps IT Professionals achieve greater productivity and control of system administration. Using a new admin-focused scripting language and consistent syntax and utilities, Windows PowerShell accelerates automation.  Windows PowerShell is easy to adopt, learn, and use, because it works with existing IT infrastructure and scripting tools. 
This Release Candidate 2 of Windows PowerShell addresses numerous customer requests based on their evaluation of Beta3 and RC1 including:

  • Direct ADSI support to allow IT Pros to more easily administer Active Directory
  • Improved support for Windows Management Instrumentation through ability to change WMI properties via methods
  • Additional logical operators (XOR and binary XOR) that make it easier to write sophisticated scripts
  • Improved help content and help functionality including new views that make it easier to find the right information.

Windows PowerShell 1.0 will release-to-web in Q4 CY06
Windows PowerShell will be leveraged by Microsoft Exchange Server 2007 and System Center Operations Manager 2007.

Customers can download Windows PowerShell RC2 at

Microsoft Windows Live Writer

Microsoft Windows Live Writer 1.0.141 Beta beta

Windows Live Writer is a desktop application that makes it easier to compose compelling blog posts using Windows Live Spaces or your current blog service. Blogging has turned the web into a two-way communications medium. The goal in creating Writer is to help make blogging more powerful, intuitive, and fun for everyone.

Windows Live Writer has lots of features which we hope make for a better blogging experience. Some of the ones we are most excited about include WYSIWYG Authoring, Photo Publishing, Map Publishing, Writer SDK, and Compatibility.

Latest Changes:

  • Tagging support
  • Support for Blogger Beta
  • Categories are sorted by name and support scrolling, plus improved support for reading categories from your blog
  • Improved startup performance
  • Paste is enabled for Title region and TAB/SHIFT+TAB navigation between title and body supported
  • Insert hyperlink added to context menu when text is selected
  • Title attribute in Insert Link dialog
  • Custom date support for Community Server
  • Improved keyboard shortcuts for switching views
  • Change spell-check shortcut key to F7
  • Add ‘png’ to insert image dialog file type filter
  • More robust image posting to Live Spaces
  • Improved style detection for blogs
  • Fixed issues with pasting URLs and links
  • Remember last window size and position when opening a new post
  • Open post dialog retrieves more than 25 old posts


    Windows Vista Corporate Activation (VLK 2.0)

    So… you’ve been wondering just what Microsoft has been up to in regards to implementing tighter measures with corporate volume licensing in Windows Vista and Longhorn Server, huh? Well, look no further, my friend, because you’ve come to the right place! Let’s take a moment to reflect upon the day „Devil’s Own“ leaked that infamous corporate copy of Windows XP of Intel’s for all the world to pirate. Sure, Microsoft took a big hit with that but what a lot of people fail to realize is how much Intel had to pay Microsoft (a figure in the millions of dollars) for that leak. (Read the fine print, if you’re a corporation with Volume Licensing… wink.gif ) Microsoft’s plans for foiling pirates with their brand new, shiny activation movement with Windows XP was certainly something seemingly laughable at that rate… especially when activation was exploited the way it was, but now it’s time to see just what they’ve learned from the VLK 1.0 experience.

    Key Terms:

    VLM: Volume License Media (SKU/SKU’s containing the files necessary for corporate activation which differ from files used to activate retail versions)
    VLK: Volume License Key (A key containing unique characters which works only with VLM; not Retail media, thus, the distinction between corporate and retail activation)
    KMS: Key Management Service (The central service in VLK 2.0 that handles volume activation of all clients and servers in an enterprise network. Target: Larger networks (at least 25 machines) that client machines can regularly connect to.)
    MAK: Multiple Activation Keys (This is the new implementation of activation via the VLK 1.0 method… but with quite a few differences. They will be leveraged the same way as original VLK’s were in XP and Windows Server VLM except, unlike XP and Windows Server-generation volume licensing, MAK’s, like retail keys, *WILL* need to be activated through Microsoft, so… bye-bye to corporate keys not needing activation!)

    Let’s go in-depth with KMS and MAK activations, shall we? Yes, we shall. =)

    KMS Activation: This is the service that will be used for managed environments where users are connected to a corporate network. Activation by means of KMS will go as follows:

    – Corporation obtains Vista and/or Longhorn VLK(s) and VLM from Microsoft.
    – Corporation installs Vista and/or Longhorn VLM, using their VLK, to a machine which will host KMS.
    – KMS is enabled and stores the VLK in its trusted store for security. (Think: nixing the use of “key-finder” programs by keeping keys off of each individual machine on a corporate network.) KMS is also configured so that required client machines will be able to communicate with it periodically.

    So, you have installed Vista and have enabled and set up KMS. Now what? Well, now every computer on your network that you install Vista on will need to be pointed to your KMS “server” so that it can activate. No key is entered or stored in the client machines and the KMS method requires that every client re-activate itself periodically! If a client machine is disconnected from the network for 180 days, it will be considered “out of tolerance” and will be placed into RFM (Reduced Functionality Mode). RFM makes it so that no user can log in to that machine. The way to alleviate RFM is to re-connect that client to the network and it will re-activate via the KMS “server.”

    It’s also worth noting that KMS will require a minimum number of clients to be rolled out successfully within a corporation. At the time of this writing, the current number of required clients is 25. In up-to-date documentation, Microsoft is still representing this number 25 with an “n” to show that it’s still subject to change, but what else is new? =) The first 25 clients installed will hit the KMS “server” first and will be kept in a list for 30 days.

    Every flavor of Vista, as well as Longhorn Server, will have KMS functionality and support for KMS in Windows Server 2003 is currently planned for post-Vista RTM.

    Over-simplified, KMS is essentially Microsoft’s counter-measure to the employees of a corporation getting hold of their corporation’s volume license key. With such a low number of machines set as a requirement to leverage KMS (at the time of this writing, 25 clients), you can tell that Microsoft is *really* pushing to get VLK’s into the hands of as few individuals as possible within a corporation. I’m guessing Microsoft will try to make the KMS solution as cost-effective as possible so that this initiative will really take off with great success. (See: More money and less piracy. smile.gif )

    Key policies to remember with VLK 2.0 KMS activation:

    N-Policy (Minimum # of machines per KMS): Currently 25.
    Expiration period until re-activation: 180 days.
    Hardware tolerance: Bound to system hard drive.
    Out-of-box grace period: 30 days
    Out-of-tolerance: 30 days (If user has gone beyond expiration or changed their hard drive.)

    MAK Activation: This method of activation stands to be leveraged for decentralized networks where users are rarely or never connected to the corporate network. In English, lol, this is THE key that pirates will hope to get and stand a better chance of getting a hold of to leak to the masses along with the appropriate VLM. (VLK 1.0, anyone?) Ah, but this time, Microsoft has a new plan. Let’s see what they’re doing with what they’ve learned:

    The foremost change with volume licensing is that no key will go without needing to be activated – period. Knocking VLK’s down to Retail level in terms of activation creates a whole new playing field for corporations and Microsoft. Perhaps equally as notable of a change is all MAK activations and activity can be viewed via Microsoft online portals. With MAK’s having an upper-limit in terms of how many activations each key can sustain, this keeps any one key from doing world-wide damage in terms of piracy. Something else unique about MAK’s is that the confirmation ID generated by them can be used to re-activate a machine! For instance, if you need to reinstall a client machine, you can use the confirmation ID that was given after installing with the MAK the first time you installed on that machine – so long as there have been no hardware changes. This also keeps it so that reinstalling a machine doesn’t count against your MAK total.

    So, in essence, a MAK is nothing more than a retail license that can be used a pre-determined number of times on multiple machines.

    Key policies to remember with VLK 2.0 MAK Activation:

    MAK total policy (Each key has a pre-determined number of activations.)
    No N-Policy
    No expiration
    Hardware tolerance: As with current retail versions of Windows, certain hardware changes will require a re-activation, and will count against MAK total.
    Out-of-box grace period: 30 days
    Out-of-tolerance: 30 days (For changed hardware only.)

    There is a lot more to learn about VLK 2.0 as Microsoft approaches Vista RTM. Likewise, there is also a lot that Microsoft could change between now and then, but until then, the information provided above should give those interested plenty of insight into what to expect with corporate licensing and activation.


    Resource: Windows Vista Volume Activation Overview VLK 2.0 (Partner Presentation)
    Source: In-house

    Рекордна скорост за предаване на информация

    Рекордна скорост за предаване на информация на малко разстояние е била достигната днес в офис на една компютърна фирма при падането от стелаж на височина 1 м на кутия,съдържаща 20 бр Seagate Barracuda 300GB. Общият обем на предадената на разстояние 1 метър информация е 300*20*8 =48 000 гигабита, като времето за предаване е било t=sqrt(2h/g)=0.4 секунди. При това средната скорост за предаване на информация се получава 120 терабита/с!