The version of App Locale that runs on Vista?

by Michael S. Kaplan, published on 2006/10/17 03:00 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2006/10/17/834208.aspx


The question that Eiji asked me was simple enough:

Do you know the apploc version that supports Vista?

I got the question from Internal user (who needs it for Vista selfhosting on en-us and run Japanese ANSI apps with en system locale).

I tried the existing apploc on Vista, but the installation failed with unknown error.

And, in my opinion, the situation has not been changed since XP/WS03, I think we need the support for Vista.

Of course my first instinct in such situations is to scream Use Unicode! but I figured I should contain myself. So I stopped for a moment.

And then I thought about the issue that came up with Keyboards under LUA where an MSKLC-created install could not be installed on Vista unless it was run from an elevated command prompt....

So I tried the elevated command prompt in this new scenario and yes, App Locale (AppLocale) installed just fine. And I did my typical quick test (running Notepad with a Japanese system locale, typing the Hiragana vowels:

あいうえお

saving the file, and then opening it up from Explorer and seeing the text showing up as:

‚ ‚¢‚¤‚¦‚¨

but then looking correct again if I open it with the "Japanese'd" Notepad provided by App Locale shortcut.

So it looks to me like App Locale works fine under Vista. You just need to the right permissions to be installing it. :-)

Note that as Heath Stewart pointed out here and Robert Flaming pointed out here, an install program with a more conventional name like SETUP.EXE will try to be elevated all on its own, for backward compatibility, with the thousands of other installers that came before it (and without needing manifests or other adjuncts). So you can think of the programs that hit this problem as a much less common scenario of ruggedly independent projects that can't use ordinary and accepted names for their installers....

This may even inspire a decent idea for the next release of MSKLC -- adding a bootstrap program called setup.exe to start things up and work around the whole Keyboards under LUA issue simply? :-)

 

This post brought to you by(U+0c8c, a.k.a. KANNADA LETTER VOCALIC L)


# Tyler on 17 Oct 2006 4:11 PM:

Regarding naming things setup.exe to get elevation:

Please don't do that.  If you want your setup.exe to elevate every time, then USE A MANIFEST.  InstallDetection can be turned off and then you look stupid.

As for AppLocale, I assume this is an instance of a misauthored MSI.

# Michael S. Kaplan on 17 Oct 2006 8:09 PM:

Hmmm.... because the info on this is so widely available and intuitive that I would know how to do it instantly, right? :-)

j/k

# Ryan on 7 Jan 2008 10:59 PM:

I've tried to run apploc.msi on the elevated command prompt but it still won't install. If you could, please include step-by-step instrustions.

# Michael S. Kaplan on 8 Jan 2008 12:28 AM:

Are you an admin on the box? What is the error you get?

You should be able to just run it directly from the elevated command prompt....

# Ryan on 8 Jan 2008 1:35 PM:

I've tried different ways and for some of them, the installation remains incomplete, and for others, it can't find it, and a few others it just gives me a message saying it can't run a prgram needed to finish installing it.

# Michael S. Kaplan on 8 Jan 2008 1:40 PM:

There is only one way to run it:

  1. Be an admin on a box where no weid group policy issues might block the app.
  2. Open an elevated command prompt.
  3. Change to the same directory as apploc.msi is.
  4. Type apploc.msi from within the command prompt and hit enter

And that is it. I just tried it again on another machine and ut worked for me a moment ago just as it did when I first wrote this post....

# Ryan on 8 Jan 2008 4:48 PM:

I ran the elevated command prompt and I had already saved the file under the (C:) drive. In the command prompt, I typed in C:\apploc.msi, and it starts the installation, but then a message comes up saying the file maybe unsafe and it cancels the installation.

# Michael S. Kaplan on 8 Jan 2008 5:20 PM:

That sounds like group policy stuff  -- most people get the warning  that files from the Internet my not be safe but they give you the choice to allow it anyway. Does it happen if the file is somewhere a bit less protected than the root drive?

This has nothing to do with AppLocale -- this is policy on the machine.

# Ryan on 8 Jan 2008 5:45 PM:

I've tried it on a less protected area but it still says the file is unsafe and will not install it.

# Michael S. Kaplan on 8 Jan 2008 5:53 PM:

That error has nothing to do with AppLocale, as I mentioned. You can try looking at file properties to see if there is some way to claim it is "safe", maybe.

# Ryan on 8 Jan 2008 6:08 PM:

I've gone through the file properties and I could not find a way to make it "safe". Although the installer is listed in my program list, it does not appear as a file anyway, except for the installer.

# Michael S. Kaplan on 8 Jan 2008 6:27 PM:

In XP the text that shows up is: "Security: This file came from another computer and might be blocked to help protect this computer".

It has an Unlock button next to it, and group policy can disallow the ability to unblock if they want to. That is honestly what it sounds like is happening here....

# Ryan on 8 Jan 2008 6:50 PM:

That message came up last night but I clicked "unblock" and it still does not work.

# Michael S. Kaplan on 9 Jan 2008 4:04 AM:

I don't know what else to tell you, really -- this is an MSI installation issue, nothing to do with AppLocale specifically (these steps have worked for countless people so I am not sure what got you in this state).

The only other thing I can think of is that all of these different prior install attempts have left cruft on the machine that is blocking the install now, so that forcible uninstalls in all modes (non-elevated, elevated, etc.) would be the only way to clean out the system and let an install be successful. Beyond that, MSI is enough beyond me that I don't know what else to try....

# Christopher Thomas on 15 May 2008 11:19 AM:

Hey I got in the Admin Command prompt to vista I'm just now having problems changing Directories I'm currently in c:\Windows\system32

I need to be in c:\Users\DesertGecko96

then I would be able to run it I am in the right directory when I'm not on the admin

# Michael S. Kaplan on 15 May 2008 3:24 PM:

So you could type

cd  c:\Users\DesertGecko96

right?

# Andy on 17 Jul 2008 12:35 PM:

Hi, I was following your guide and managed to install apploc, but before is successfully installs, the set says it cannot create apploc.lnk and I need to verify if the file location exists and when I press "OK", the program says it's been successfully installed. I looked around, but I cannot find the program.

# Michael S. Kaplan on 17 Jul 2008 3:31 PM:

It should be in a directory under "Program Files"....


referenced by

2011/04/04 UXTheme in the non-Unicode world isn't "Double Secret ANSI"

2010/03/16 That Chinese Dictionary can work anywhere, if you let it

2008/04/23 On the clipboard, and why sometimes the dumber you are the better you can do

2007/03/17 A checkpoint on search engine results contrast, ultimately leading to an irreverent bit of exposition

go to newer or older post, or back to index or month or day