New LIP language packs for all versions of Vista

Direct link and download
http://www.microsoft.com/downloads/details.aspx?FamilyID=94B6C536-E49C-4602-8D3C-37E8BDBE12DB&displaylang=en

the LIP provides limited customization of languages, unlike MUI that are full language packs. (see below for links for full MUI packages and tool to install them on all versions of vista)

This package applies to the following languages:
. Albanian*
. Bosnian - Cyrillic*
. Bosnian - Latin*
. Gujarati*
. Hindi*
. Indonesian*
. Kazakh*
. Macedonian*
. Marathi*
. Serbian - Cyrillic*
. Tamil*
. Uzbek - Latin*
. Vietnamese*
. Welsh
 

Full language packs (MUI) download:
Windows Vista SP1 Language Packs 32-bit -Official-

Free tool to install language packs on ALL versions of vista:
Vistalizator - Install Vista Language Packs MUI on

Written by computerboom on May 10th, 2008 with no comments.
Read more articles on 1340 and 1354 and 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and 544 and Contributors and Customization and Updates and programs and vista.

Vistalizator - Install Vista Language Packs MUI on all versions of Vista!

About Vistalizator

Did you buy a Vista laptop from abroad and want it to talk to you in your mother language?

(You can use this on a desktop too, have in mind this is not a microsoft supported tool but one made by someone else)

Try Vistalizator - this tool allows you to change display language in Vista editions other than (officially supported) Ultimate:
Starter, Home Basic, Home Premium and Business.

Features

• Change Vista display language in less than 5 minutes!
• Uses official Microsoft language packs
• You can install all 35 languages and switch between them easily
• Works in 32-bit Vista
• Works in 64-bit Vista (new)
• Compatible with Vista Service Pack 1
• User Account Control (UAC) compliant - prompts for administrative privileges
• No file is overwritten/changed during language installation - except for language upgrade after Vista SP1 installation

Vistalizator - change display language in Vista Home and Business

Written by computerboom on May 10th, 2008 with no comments.
Read more articles on 1340 and 1354 and 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and 544 and Contributors and Updates and freeware and programs and vista.

Windows Vista SP1 Language Packs 32-bit *Official* and TOOL to install them on ANY version of Vista!

We have made available updated Language Packs for users using Windows Vista SP1 as well as those running Windows Vista RTM. For those running SP1, the Language Packs should be showing up for you under Windows Update. 
The specific language packs which are being released are as follows:
German 
English 
Spanish 
French 
Japanese 
Korean 
Bulgarian 
Czech 
Danish 
Greek 
Estonian 
Finnish 
Hungarian 
Italian 
Lithuanian 
Latvian 
Norwegian 
Dutch 
Polish 
Portuguese (Portugal) 
Romanian 
Slovak 
Slovenian 
Swedish 
Arabic 
Hebrew 
Croatian 
Portuguese (Brazil) 
Serbian (Latin) 
Thai 
Turkish 
Ukrainian 
Chinese (Simplified) 
Chinese (Traditional) 
Russian

Download : Arabic
Download : Bulgarian
Download : Chinese (Simplified)
Download : Chinese (Traditional)
Download : Crotian
Download : Czech
Download : Danish
Download : Dutch
Download : English
Download : Estonian
Download : Finnish
Download : French
Download : German
Download : Greek
Download : Hebrew
Download : Hungarian
Download : Italian
Download : Japanese
Download : Korean
Download : Latvian
Download : Lithuanian
Download : Norwegian
Download : Polish
Download : Portuguese (Brazil)
Download : Portuguese (Portugal)
Download : Romanian
Download : Russian
Download : Serbian (Latin)
Download : Slovak
Download : Slovenian
Download : Spanish
Download : Swedish
Download : Thai
Download : Turkish
Download : Ukrainian

To read about a free program that allows you to INSTALL VISTA LANGUAGE PACKS MUI ON ALL VERSIONS OF VISTA, read my other post on this subject here:

http://computerboom.blogspot.com/2008/05/vistalizator-install-vista-language.html

Written by computerboom on May 10th, 2008 with no comments.
Read more articles on 1340 and 1354 and 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and 544 and Contributors and Customization and Updates and microsoft office and programs and vista.

Windows and Ubuntu Tweaks, Tips, Tutorials

• Customize Windows XP to look like Vista
• Boot Up Windows Faster
• Enabling Remote Desktop from XP to Vista
• Windows Vista PowerToys - Tweaks from Microsoft TechNet
• Get Ubuntu (Linux) to look like OS X Leopard!
  
• Speed up your Windows Search
• Free Up windows resources which are slowing you down
• Customize Windows Send To (right click menu items)
• How to Change to Owner Name in Windows
• Customize your Windows Explorer View
• Disable User Account Control Popups
• Top 10 Free Downloads to improve and tweak your Windows Vista

Written by PCWizKid on May 3rd, 2008 with no comments.
Read more articles on 1340 and 1354 and 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and 544 and Contributors and Tips and Windows XP and Xp and howto and pcwizkid and registry and tutorials and tweaks and vista and youtube.

In Vista, How Does the FLAGS Switch of REG.EXE Work?

Note: this content originally from http://mygreenpaste.blogspot.com. If you are reading it from some other site, please take the time to visit My Green Paste, Inc. Thank you.

A while back, there was a topic (Virtual Registry vs. "Real registry") in the Sysinternals Forums that brought up the question of how to set the virtualization-related flags of a registry key programmatically in Vista, rather than through the use of the REG.EXE tool's FLAGS switch. (For more information on the flags, see Mark Russinovich's article in TechNet Magazine, "Inside Windows Vista User Account Control"). Even before that topic in the forum, I had wondered how it was done but had not had a chance to explore. It didn't seem that many others were curious about it. That topic had resurrected the idea, but it quickly fell to the bottom of the list. I've finally gotten around to experimenting, and that leads to this write-up. I still don't see much in the way of this discussed anywhere, by searching for terms involved (data types, function param names, etc.), so hopefully this will help someone. (Keep in mind that there very well may be a reason Microsoft hasn't made this available through another, more direct API.)

In the referenced topic, I had gotten so far as determining that REG.EXE was doing its work through the use of NtSetInformationKey, an "undocumented" API in NTDLL.DLL.

NTSYSAPI 

NTSTATUS

NTAPI

NtSetInformationKey(

  IN HANDLE               KeyHandle,

  IN KEY_SET_INFORMATION_CLASS InformationClass,

  IN PVOID                KeyInformationData,

  IN ULONG                DataLength );

After a bit of plonking around in WinDbg, I've come up with the following following details. REG.EXE calls NtSetInformationKey, specifying a value of 2 for the InformationClass parameter. This parameter is of type KEY_SET_INFORMATION_CLASS, which wdm.h tells us is an enum:

typedef enum _KEY_SET_INFORMATION_CLASS {

    KeyWriteTimeInformation,

    KeyWow64FlagsInformation,

    KeyControlFlagsInformation,

    KeySetVirtualizationInformation,

    KeySetDebugInformation,

    MaxKeySetInfoClass  // MaxKeySetInfoClass should always be the last enum

} KEY_SET_INFORMATION_CLASS;

So the 2 for the InformationClass parameter would correspond to KeyControlFlagsInformation. WDM.H also suggests that this class has a type that one passes for the KeyInformationData parameter - KEY_CONTROL_FLAGS_INFORMATION:

typedef struct _KEY_CONTROL_FLAGS_INFORMATION {

    ULONG   ControlFlags;

} KEY_CONTROL_FLAGS_INFORMATION, *PKEY_CONTROL_FLAGS_INFORMATION;

We have a basic idea of how to call NtSetInformationKey now. But what are the values that the ControlFlags member of KEY_CONTROL_FLAGS_INFORMATION can be set to? It would appear that the following (self-made) enum covers the pertinent flags - at least the ones REG.EXE FLAGS can handle (there may be more):

typedef enum _CONTROL_FLAGS {

    RegKeyClearFlags = 0,

    RegKeyDontVirtualize = 2,

    RegKeyDontSilentFail = 4,

    RegKeyRecurseFlag = 8

} CONTROL_FLAGS;

The control flags are a bitmask, so you can OR them to set more than one.

Now that we have this information, what's left? We need to put it all together in a call to NtSetInformationKey. So, we need to get a pointer to the function in NTDLL.DLL. Then, we can declare a struct of type KEY_CONTROL_FLAGS_INFORMATION, set the ControlFlags member to be what we wish, and open a key to the desired location in the registry, that can be passed to NtSetInformationKey. In the end, we wind up with something like the following (error handling has been omitted):

typedef NTSYSAPI NTSTATUS (NTAPI* FuncNtSetInformationKey) (

  HANDLE KeyHandle,

  KEY_SET_INFORMATION_CLASS InformationClass,

  PVOID KeyInformationData,

  ULONG DataLength ); 

//... 

FuncNtSetInformationKey ntsik = (FuncNtSetInformationKey)GetProcAddress( 

          GetModuleHandle( _T("ntdll.dll") ), "NtSetInformationKey" ); 

KEY_CONTROL_FLAGS_INFORMATION kcfi = {0}; 

kcfi.ControlFlags = RegKeyDontVirtualize | RegKeyRecurseFlag; 

HKEY hTheKey = NULL; 

RegOpenKeyEx( HKEY_LOCAL_MACHINE, _T("SOFTWARE\\Whatever"), 0, KEY_ALL_ACCESS, &hTheKey ); 

ntsik( hTheKey, KeyControlFlagsInformation, &kcfi, sizeof( KEY_CONTROL_FLAGS_INFORMATION ) ); 

RegCloseKey( hTheKey ); 

hTheKey = NULL;

The code above is the equivalent of invoking REG.EXE FLAGS HKLM\Software\Whatever SET DONT_VIRTUALIZE RECURSE_FLAGS. To clear the flags, just set kcfi.ControlFlags to RegKeyClearFlags (same as REG.EXE FLAGS HKLM\Software\Whatever SET).

Hopefully, this will prove useful to those that have wished to set these flags programmatically. In a future post, I hope to explore querying for these flags, ala REG.EXE FLAGS HKLM\Software\Whatever QUERY.

Note that this exploration was done on Windows Vista SP1. I would expect the content here to also apply to Windows Vista (no SP) as well as Windows Server 2008, but...

Written by «/\/\Ø|ö±ò\/»®© on April 27th, 2008 with no comments.
Read more articles on 1340 and 1354 and 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and 544 and Contributors and Troubleshooting and Virtualization and registry and vista and windbg.

Shell Namespace Extension: Enabling Deep Search

Overview

From my past posts about implementing your own Shell Namespace, there have been some great questions posted by readers.  Many of these stem from the fact that the Namespace example is fairly simple in that it does not implement all of the behavior that is possible in Explorer.  This was done to focus on the core steps in getting a working Namespace implemented.  Yet, there are a few extra steps you can take that don’t require too much more coding on your part to add more useful features.  One question in particular that comes up quite often is how to enable deep searching in your Namespace.

You will notice from the existing Namespace example that if you enter a search term in the search box in Explorer, the search only filters items that are currently in the view.  It does not search into the folders.  In the below images, we try to search for “Two” in the search box which only results in 1 item.  Thus, the sub folders were not included.

What does a Namespace implementer have to do in order to include sub folders in their namespace search results?  This is actually fairly simple.

Implementing IShellFolderViewCB and IFolderViewSettings

In our previous code, we did not implement an IShellFolderViewCB for our Namespace.  This allows your Namespace to be notified of events associated with the view.  An implementation of IShellFolderViewCB can be specified in your call to SHCreateShellFolderView.  This is optional and previously we were just passing NULL for this.   We need to create a class that implements IShellFolderViewCB as well as IFolderViewSettings.  For our IFolderViewSettings implementation, we only need to provide a handler for the GetFolderFlags method.  It is through this method that we notify the Shell that we want to perform deep searches within our Namespace.

IFACEMETHODIMP CFolderViewCB::GetFolderFlags(__out FOLDERFLAGS *pfolderMask, __out FOLDERFLAGS *pfolderFlags)

This Namespace simply generates 10 virtual items to a default depth of 5.  The Search enumerates the contents of the Namespace to that depth.  It should also be called out that we had to implement our namespace's ParseDisplayName method in order for our namespace to function in the Search folder.

*Please note that the method described here only works with the default shell view (Defview).  It is not supported for custom IShellView implementations.

Building the FolderView SDK Sample

1. To build the FolderViewImpl sample, be sure to download and install the Windows SDK.
2. Download the modified FolderView SDK sample
3. Launch FolderViewImpl.sln in Visual Studio (The solution file is for Visual Studio 2008)
4. Open the properties for the project
5. Add a path to the SDK includes to the C/C++ - General page
6. Add a path to the SDK libs to the Linker – General page
7. Build

Installing the FolderView SDK Sample

1. Once you have built the sample, copy the FolderViewImpl.dll and FolderViewImpl.propdesc to the same directory
2. From an elevated cmd window, regsvr32 FolderViewImpl.dll
3. Restart explorer
4. Open explorer to Computer
5. There should be a list item named “FolderView SDK Sample”

Written by chrdavis on March 3rd, 2008 with comments disabled.
Read more articles on API and Coding and Programming and Search and Search and Organize and Windows Vista and extension and namespace and shell and vista.

Shell Namespace Extension: Enabling Deep Search

Overview

From my past posts about implementing your own Shell Namespace, there have been some great questions posted by readers.  Many of these stem from the fact that the Namespace example is fairly simple in that it does not implement all of the behavior that is possible in Explorer.  This was done to focus on the core steps in getting a working Namespace implemented.  Yet, there are a few extra steps you can take that don’t require too much more coding on your part to add more useful features.  One question in particular that comes up quite often is how to enable deep searching in your Namespace.

You will notice from the existing Namespace example that if you enter a search term in the search box in Explorer, the search only filters items that are currently in the view.  It does not search into the folders.  In the below images, we try to search for “Two” in the search box which only results in 1 item.  Thus, the sub folders were not included.

What does a Namespace implementer have to do in order to include sub folders in their namespace search results?  This is actually fairly simple.

Implementing IShellFolderViewCB and IFolderViewSettings

In our previous code, we did not implement an IShellFolderViewCB for our Namespace.  This allows your Namespace to be notified of events associated with the view.  An implementation of IShellFolderViewCB can be specified in your call to SHCreateShellFolderView.  This is optional and previously we were just passing NULL for this.   We need to create a class that implements IShellFolderViewCB as well as IFolderViewSettings.  For our IFolderViewSettings implementation, we only need to provide a handler for the GetFolderFlags method.  It is through this method that we notify the Shell that we want to perform deep searches within our Namespace.

This Namespace simply generates 10 virtual items to a default depth of 5.  The Search enumerates the contents of the Namespace to that depth.  It should also be called out that we had to implement our namespace's ParseDisplayName method in order for our namespace to function in the Search folder.

*Please note that the method described here only works with the default shell view (Defview).  It is not supported for custom IShellView implementations.

Building the FolderView SDK Sample

1. To build the FolderViewImpl sample, be sure to download and install the Windows SDK.
2. Download the modified FolderView SDK sample
3. Launch FolderViewImpl.sln in Visual Studio (The solution file is for Visual Studio 2008)
4. Open the properties for the project
5. Add a path to the SDK includes to the C/C++ - General page
6. Add a path to the SDK libs to the Linker – General page
7. Build

Installing the FolderView SDK Sample

1. Once you have built the sample, copy the FolderViewImpl.dll and FolderViewImpl.propdesc to the same directory
2. From an elevated cmd window, regsvr32 FolderViewImpl.dll
3. Restart explorer
4. Open explorer to Computer
5. There should be a list item named “FolderView SDK Sample”

Written by chrdavis on March 3rd, 2008 with comments disabled.
Read more articles on API and Coding and Programming and Search and Search and Organize and Windows Vista and extension and namespace and shell and vista.

Windows Vista Service Pack 1

• Microsoft says it's a little faster, and it does seem a little more lively, though this computer was pretty quick before, and
• Before the update, memory usage tended to build up throughout the day until it reached 55 or 60%. Now it seems to sit at about 35%, going up or down slightly as applications are opened and closed.

• The select zone that extends all the way across the main window of Windows Explorer instead of being limited to the file name,
• Windows Calendar reminders still don't work if Windows Calendar is closed, even though I have selected the option that should make reminders work,
• Windows Task Manager still asks for permission to continue, when I ask it to display all running processes, even though I'm logged on as Administrator, and
• All of the other Vista annoyances.

Written by Don on February 21st, 2008 with no comments.
Read more articles on Contributors and sp1 and vista.

Windows Vista One Year Vulnerability Report

Written by Madhukar on February 5th, 2008 with comments disabled.
Read more articles on Downloads and vista.

Small Update Regarding Previous Post Pertaining to Plagiarism

Ahhhh, alliteration. Anyway, just noticed that one of the other sites has posted the cheesy comment I referenced in my previous entry, Set the Priority of a Process By Name Automatically, in Vista - Part 2. So, both saw fit to post the comments (took a while for the one site, though) - the first stamped 2008-01-31 2:37 GMT, and the second stamped 2008-01-30 13:40 GMT. No sign of Part 2 on either of these sites, though... Hmmm...

Written by «/\/\Ø|ö±ò\/»®© on February 2nd, 2008 with comments disabled.
Read more articles on CpuPriorityClass and Plagiarism and comments and copycat and vista.

« Older articles

No newer articles