lajackson wrote:For the adventurous, this is already possible. There is a two-character setting in one of the MLS files. If you edit the file to change the language code, MLS comes up in the new language.
The details are in this post.
lajackson wrote:For the adventurous, this is already possible. There is a two-character setting in one of the MLS files. If you edit the file to change the language code, MLS comes up in the new language.
I made a VBS (script) that make this work before, I changed also Unit ID to start directly from the right database. This was done because Military branch's clerk doesn't care about Italian Windows version.lajackson wrote:For the adventurous, this is already possible. There is a two-character setting in one of the MLS files. If you edit the file to change the language code, MLS comes up in the new language.
I'll give it a look!Supposedly, Microsoft's Multilingual User Interface Pack is supposed to eliminate the need for dual booting just for language preferences. It stores the language preference with the user's settings instead of setting them globally for the entire installation.
The MUI Pack is only available through Volume Licensing (VL) programs from Microsoft and I believe the Church just buys the OEM operating systems from the computer vendor(s) and so does not have/need a VL agreement.jbh001 wrote:Supposedly, Microsoft's Multilingual User Interface Pack ...
Well, now that's a good question. Yes, all the machines I've seen have the Microsoft sticker on the side which suggests OEM licensing. However, when we load an image such as Desktop 5.5, or the image for FHC machines, it's licensed however the "master" computer was licensed. Seems like the Church owns enough computers that Volume Licensing (VL) could make sense. In fact, when I loaded Win2000 on our FHC machines, I know SLC gave me the licensing info - so they must VL some of it.Mikerowaved wrote:I believe the Church just buys the OEM operating systems from the computer vendor(s) and so does not have/need a VL agreement.