Mathwiz Posted December 28, 2025 Posted December 28, 2025 20 hours ago, VistaLover said: https://en.wikipedia.org/wiki/International_Components_for_Unicode Thanks. I actually thought it might have something to do with the fact that the initialism ICU, when read in English, sounds like the sentence "I see you!"
anton12 Posted December 29, 2025 Posted December 29, 2025 Hello roytam1 and nicolaasjan, Thanks for the feedback ! roytam1 said: "v31l here and it just triggered vc++ runtime error." nicolaasjan said: "I have Windows 2000 with extended kernel here in a VM and the latest New Moon works fine." "Ah... I have Windows2000-KB935839-v30fM-x86-ENU" anton12 says: Win2000-KEX-KB935839-v31lM here and I have Visual C++ Runtime error as well (s.a.). ------------------------------------------------------------------------------ roytam1 said: "runtime files are not changed and it works on XP SP2 with hotfix or SP3 using same runtime files, so the problem could be in w2k extended kernel." Which M$ Visual C++ Runtime do you use in W2K-Kex (v31lM) and XP SP2/SP3. Is it newer than M$ Visual++ Runtime 2008 ?
nicolaasjan Posted December 29, 2025 Posted December 29, 2025 1 hour ago, anton12 said: Which M$ Visual C++ Runtime do you use in W2K-Kex (v31lM) and XP SP2/SP3. Is it newer than M$ Visual++ Runtime 2008 ? I have : msvcr100.dll 10.0.40219.473 (Windows 2000) msvcr100.dll 10.0.40219.325 (Windows XP SP3) Those belong to Microsoft Visual C++ 2010 (direct link; no idea if it will work for your system). msvcr100.dll 10.0.40219.473 copy from my Windows 2000 here.
roytam1 Posted December 30, 2025 Author Posted December 30, 2025 (edited) On 12/28/2025 at 11:31 PM, nicolaasjan said: Ah... I have Windows2000-KB935839-v30fM-x86-ENU hmm, confirmed v30i and v31 also works. and it seems to be broken in v31a and later. since there is no release note and/or changelog for v31a, nothing is known besides ntdll and kernel32 are newer in v31a. Edited December 30, 2025 by roytam1 3
anton12 Posted December 31, 2025 Posted December 31, 2025 (edited) Hello nicolaasjan and roytam1, nicolaasjan said: "I have : msvcr100.dll 10.0.40219.473 (Windows 2000) msvcr100.dll 10.0.40219.325 (Windows XP SP3) Those belong to Microsoft Visual C++ 2010 (direct link; no idea if it will work for your system)." I tried Windows2000-VC2019u2-INTL.wlu for W2K by blackwingcat which installs the latest M$ Visual C++ 2019, together with W2K-Kex v31l, and it didn't help (runtime error). Next I returned to my old v30fM and NM28 25-12-24 and St52 25-12-24 work ok. roytam1 said: "hmm, confirmed v30i and v31 also works. and it seems to be broken in v31a and later." W2K-Kex from v31 to v31h had problems that were finally fixed with W2K-Kex v31l. The strange thing is that this fixed version v31l that worked quite well for over a year - incl. NM28 and St52 - now has problems with the latest version of NM28 and St52. Edited December 31, 2025 by anton12 1
modnar Posted 10 hours ago Posted 10 hours ago On 12/29/2025 at 6:51 PM, nicolaasjan said: I have : msvcr100.dll 10.0.40219.473 (Windows 2000) msvcr100.dll 10.0.40219.325 (Windows XP SP3)... I have msvcr100.dll v. 10.0.40219.473 in XP. I use abbodi1406's CPPredist AIO x86 v35 (XP_last). 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now