A good friend of mine known as Utakz posted that the February CTP build of Windows Vista and Server Code Name: “Longhorn” is supposed to be 5308.winmain_idx01 (a very recent compile), and should be released by Microsoft tomorrow (Feb 22nd). This particular build has been recompiled more than ten times which would mean that the original code did contain bugs. Microsoft will also publish an updated version to the Windows AIK (Automated Installation Kit) which contains the deployment tools for Windows NT 6.0, including the famous XImage tool for creating, editing, mounting and deploying Windows Images.

According to Utakz, the build will indeed contain the anticipated Windows Sidebar, perhaps updated versions of the Calendar and Digital Library features. (Do note that Windows Sidebar is anticipated by some people, while the others either don’t like it or would like the 4000-era Sidebar back - including myself.)

Hopefully, known drivers and common bugs have been resolved in this new build and testers will be able to continue testing the next version of Microsoft Windows.

Today I added a new section to this blog, Applications & Code Snippets, where you can find code I have published to the web. Currently, there is only one console application added to the section, a ‘crawler’ for Internet Explorer windows’ URLs. I have coded it a while ago, but I have recently shared it at Channel9 since another ‘Niner’ was looking for such an application. I intend to upload sample code every other day so feel free to request any code via the Contact form.

That’s right,

I haven’t posted in this blog for a lot of time, but as you might have already noticed I have bought the domain name stoyanoff.info, so I will try to keep this blog updated as frequently as possible. I would be posting news, thoughts and code snippets for technologies, such as the Windows Presentation Foundation (that is, Avalon), Windows Vista and Server Code Name: “Longhorn”, and programming itself. I might also edit the current WordPress theme a little, so don’t worry if the elements are messy for a bit.

 Thank you for reading this blog, and I hope you enjoy your stay here. Feel free to comment regarding the topics you would like to be discussed and don’t hesitate to contact me via the contact form - I will try to respond as soon as possible.

Yesterday Microsoft surprisingly announced the first BETA of WinFS (compiled on the Aug 15 2005), but it is intended for use in Windows XP with SP2 only. However, it can easily be made to work in Windows Server 2003 and Vista (code name: “Longhorn”). Here are two ways to do it:

1. Get a HEX Editor application.
2. Start en_WinFS_Beta1.exe and it will extract the necessary contents to C:\\winfsbeta1 (by default). When the extraction process is done, you may get an error message on non-WXP SP2 systems - just disregard and close it.
3. Drag C:\\winfsbeta1\\winfs.msi to your HEX editor and go to offset 0×1FE9E.

Now you can choose one of the following:
#1 4. Look at the ASCII pane and replace = 501 with > 500.
#2 4. Look at the ASCII pane and replace 501 with [NTVersion_Major][NTVersion_Minor]. E.g. “501″ for Windows XP, “502″ for Windows Server 2003, “600″ for Windows Vista (fka. “Longhorn”).

5. At offset 0×1FEBC replace byte 0×32 with 0×30.

-Stanimir

WinFS Beta 1 is out for MSDN Subscribers now. Microsoft has started a new, only WinFS-related blog as well.

Recently, the WinFX SDK and the Avalon Binaries Beta 1 have been released. However, Xaml files are still opened by Notepad and the nice preview in Internet Explorer is still gone. This is why I decided to update my XamlViewer application which can be used on Windows XP SP2, Server 2003 SP1, Vista, and Server Code Name: “Longhorn” Beta 1.

You can download it from here.

The Internet Explorer team has done great job with the new Internet Explorer 7 Icon and Logo. However, there will be another icon used in Windows Vista™, they say - this one will be used in Windows XP SP2, Server 2003 SP1, and Windows XP x64 only.

The last week, AlphaAlien, y_notm and myself worked on a guide regarding customizing the Windows Search and Indexing Engine experiences. I have coded a little application that loads itself in the background and waits for Windows Search windows or Open/Save file dialogs to appear. It enables the Search button and you are able to search in both indexed and non-indexed custom folders (although, it is recommended that you search in indexed folders only, otherwise the search would take some time). The application is acompanied by a few Command Prompt scripts which allow you to make it run on Start Up automatically, stop it, or remove it from the StartUp folder.

You can get the application here and the guide is available here.

Note: The application is tested in both Windows Vista and Windows Code Name: “Longhorn” Server and works fine. You need .NET Framework, at least v1.1, and v2.0 comes pre-installed with Windows Longhorn.

AlphaAlien, y_notm and myself have been working on a guide to customize the Windows Search Engine experiences in the recent release of Windows Vista Beta 1. The guide covers the following themes: creating custom Virtual Folders (search queries), making the Indexing engine index files in usual folders (not only in the \Users\ one), and the incompleted ‘Custom-location indexed search’ - so far this can be done using a third party handle viewer and manipulator to enable the appropriate combo box; I am working on an application that should do this automatically.

You can read the guide here: HOW TO: Customize search locations in Vista Beta 1.

On the other hand, Nighthawk and myself made a little pack for the Window Desktop Manager that allows it to read per-user settings, so that every user on the computer can have different settings. The package also contains a few Registry key files that allow fast switching of the available features, such as Blurring, Slow Animations when the Shift key is held, Animations and Glass effect. You can download the pack here: Per-User DWM Modification.

The highly anticipated Beta program of Windows® Vista™, formerly known under the code name “Longhorn”, has just started. Bets 1 has been given to first batch of testers for feedback: primarily bug reporting and suggestions. The press kit, which contains official screenshots, too, can be found here.