To me it definitely looks like an Asus distribution fault.
I searched the Windows folder for the location of PINTLGB.IMD on both my Asus K93SV and my older HP Pavilion DV8 (both running Windows 7 64-bit), and on the HP I found the file in only 2 locations:
C:\Windows\IME\IMESC5\DICTS
C:\Windows\winsxs\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b
whereas on the Asus the file was found in 3 locations:
C:\Windows\IME\IMESC5\DICTS
C:\Windows\winsxs\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7601.17514_none_763763505e93084b
C:\Windows\winsxs\amd64_microsoft-windows-i..lified-chinese-core_31bf3856ad364e35_6.1.7600.16385_none_74064f8861a484b1
All these files on both systems were 326858 bytes in size and dated 10-6-2009 23:02, such that superficially they all looked like identical copies.
I then ran "sfc /scannow" on the HP, resulting in "Windows Resource Protection did not find any integrity violations", so that system seems clean and I could consider copying its PINTLGB.IMD to the Asus. However, I wanted to know which of the 3 instances of
this file on the Asus were corrupted, so I ran Windiff on the clean HP copy from its DICTS and "4b" folder against the DICTS, "4b" and "b1" folder variants of the Asus. It turned out that the 3 PINTLGB.IMD copies on the Asus were all mutually identical, and
the 2 PINTLGB.IMD files on the HP were also mutually identical, while the mutually identical copies on the HP differed from the mutually identical copies on the Asus. So it looks like all 3 copies on the Asus are corrupt. I wonder what the best and safest
procedure is for overwriting the corrupted Asus copies, because Windows does not grant Administrator the permission to overwrite these system files (only "TrustedInstaller" has that permission). I probably need to reboot into safe mode with a command prompt
(pressing F8 during reboot) to avoid loading Windows, but I did not try this yet, and it would be a bit of a pain without further preparations because of the very long folder names.
Thanks!