Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

37 Excellent

About luweitest

Profile Information

  • OS
    XP Pro x86
  • Country


  • Country Flag

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I don't know your origin problem, but nlite does support POSReady 2009, and I made a Intel AHCI driver integrated into it, installed successfully in Virtualbox (Have no chance to install to a real machine yet).
  2. OK then I applied the registry patch according to MS to "completely mitigates the issue though can introduce usability issues in rare cases". Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows] "DisableATMFD"=dword:00000001 No issues observed till now (3 days).
  3. https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/adv200006#ID0EMGAC The above link does not mention Windows XP is affected, but say vaguely as "before Windows 10".
  4. I am using the last official Intel driver for 4965AG, yet apparently no WiDi features, maybe too old network adapter. Is official driver the only hope?
  5. Is it possible to install a program or driver in WinXP to support Miracast protocol (or WiFi direct, screen mirroring, smart screen, screen cast , whatever synonyms)? As cast source (client), target (server), or both? Is there any hardware barriers (Intel 4965AG)?
  6. I mean it is superseded by POSReady updates. I randomly picked one so I could not remember which one. I am a user of POSReady and cannot understand the logic to update XP after SP3 but exclude POSReady. So I'd rather not bother to find it out again.
  7. The main difference I see is uBO 1.17.4 has javascript blocking. So I think 1.16 is enough if using Noscript at the same time.
  8. I am using uBlock Origin 1.17.4 on latest Serpent 52 without problem.
  9. As the original https://github.com/CNMan/MicrosoftHotfixesList/issues/2 poster said I checked some of them, one is superseded, one for IE8 is not necessory (although not marked as superseded, in fact only last IE cumulative patch is needed). I think others might also be like that.
  10. As this is a WIP, it is not suited to be a blog post; cooperative editing is needed. Github, Wiki, or google doc?
  11. I am just back reporting that scale factor definitely does not work on XP... Thanks. Replacing simsun is not my intent, but a prerequisite to resolve the incomplete display of some English software. Before doing that scaling factor experiment, I have found a better way to accomplish this: Mactype. It is not mainly designed for this purpose, but it can replace font without rebooting! Scaling issue could be resolved too, but the result is not very good -- It's font tuning, the main feature, seems not as clear as the original font with cleartype on. Anyway, since I can hot switching fonts, it could ignored now.
  12. Whatever the size of *.fon file (they are all Latin font), chinese fonts always have different size. Yes, Simsun have no (or less) scale problem as MSYH. I changed font link to simsun.ttc, then the mixed character display got better, though still not as before. Thanks for the link. I replaced my old MSYH.ttf, yet it did not work. I found this page may give the right hint about scaling: https://shajisoft.com/shajisoft_wp/fontlink-for-cjk-on-english-windows-10/ I'll try it and report back.
  13. Is Microsoft download center not searchable anymore? I once asked a related question that the search box do not show completely, which is still the same; but now it seems I cannot search anything. There are "shop" and "explore" category, but no "download center". Clicking the menu "All microsoft" -> "other" ->"free downloads & security" will bring you to a page for browsing, without search function.
  14. My XP version is simplified chinese (thus some text below may display blank box in your screen, but you could ignore them). Many English software‘s dialogue box will not render correctly -- some characters not shown, lines truncated or wrapped to non-display, bottom elements not displayed, etc. I find if I could change the font of the dialogue box to another (maybe Latin) font, then the problem would be solved. The default font for simplified chinese is 宋体(Simsun.ttc). I changed the fonts list in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts as: replaced every fonts pointing to simsun.ttc to msyh.ttf (微软雅黑). But, instead of using msyh.ttf, the dialogue box then uses the font from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware Profiles\Current\Software\Fonts\Fonts.fon value. The value is svgasys.fon by default, but the font is displayed large thus some dialogue text still not displayed. I changed it to sserife.fon, and the display is good. Then another problem arises: Many system chinese texts display blank box, which could be expected since sserife.fon has no chinese glyph. According to https://docs.microsoft.com/en-us/globalization/input/font-technology , I add a font link at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink\, value="MS Sans Serif" (the name of sserife.fon), data="msyh.ttf,微软雅黑". Then chinese texts get displayed, but very small: As in above picture, aside from those chinese characters in windows title are normal size (whose font is set by "appearance" and display good even no font link is added), English character is way bigger than chinese character , and some chinese character is still displayed as blank box (has been solved by changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FontAssoc\Associated DefaultFonts)). The MS document says it is the problem of scaling, and quote: "Note that GDI+ is not able to parse these scaling factors. Thus, references to fonts with scaling factors are repeated without these scaling factors. In GDI+, the first reference, with the scaling factors, will appear to be to an unrecognized font and will be ignored. In GDI, the second reference will be treated as redundant and ignored." But even if I added a manual scaling line fist as suggested format: "msyh.ttf,微软雅黑,128,85", there is no change. Now my problem is: 1, Does XP not support this scaling factor? GDI+ and GDI are both supported by XP according to MS. 2, Why instead of my replaced font name in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts , it looks for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware Profiles\Current\Software\Fonts\Fonts.fon ? The latter value could not use *.ttc|*.ttf files but only *.fon, which forced me to use font link and then encounter the scale problem. p.s. All changes take effect after reboot.
  15. nLite can integrate all PosReady updates. I did it using a SP3 iso, but I think there should be no problem starting from SP1.
  • Create New...