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. 


Leaderboard


Popular Content

Showing content with the highest reputation on 02/07/2019 in all areas

  1. 3 points
    I helped out the cause and installed Windows XP on my laptop. I was using CentOS on it and I ended up messing up Samba so...here I am now on Windows XP. ;)
  2. 1 point
    Cooperation from XP enthusiasts might be helpful in many cases, but in this case has resulted in confusion. IE9 does at least support HTML5 (but not MSE), IE8 of course does not. I can't seem to find an official YouTube statement regarding final deprecation of Flash Player, but know of no reason to disagree with the OP of this thread. Support for Chrome Frame ended 5 years ago. When it comes to my own vintage Vista system, Chrome Frame would be as unwelcome as an Alien facehugger. The obvious workaround is to use a different browser for YouTube, but +1 for wishing this wasn't necessary.
  3. 1 point
    Switch to Potplayer: https://www.videohelp.com/software/PotPlayer
  4. 1 point
    The "browser" is actually the Eudora email client - we're trying to debug delays in certain HTML-formatted emails appearing - but I'm guessing it's using Microsoft's rendering engine under the covers. (@Dave-H tried installing Google Chrome Frame and making it the default for IE8, but it didn't affect Eudora.) The HTML source that Dave uploaded (for one of the troublesome emails) contains a few problems for IE8: There are three URLs that start with // instead of https://. According to Google these are "protocol-relative URLs" that point to an address, keeping the current protocol. Unfortunately in an email, there is no current protocol, because the HTML wasn't downloaded from a Web server. IE8 doesn't appear to handle these URLs correctly anyway. This appears to be what causes the delays in the email being displayed. IE8 has a bug in handling @font-face CSS rules that causes it to include extra garbage characters after the URL, so it doesn't find the .woff files even if you fix #1 by adding https: in front of the URLs. The usual workaround for #2 is to append a ? to the font URL, so the extra garbage gets ignored by the Web server. Unfortunately, IE8 doesn't support the .woff font files that these emails use anyway. Ironically, helpforum.sky.com's toolkit.css file specifies .eot fonts (which work in IE8) as well as the same .woff files that don't work, so the .css code in the email (that causes the above problems by trying to load the .woff files again) isn't even needed at all! Unfortunately, toolkit.css repeats IE8 problems #1 and #2, so you continue to get delays even after fixing its URL So lots of little problems, but I think #1 is the important one since it's the one that seems to be slowing everything down. Also, I think IE8 (and presumably Eudora) are misinterpreting those protocol-relative URLs as UNCs and trying to find local network servers called www.sky.com and helpforum.sky.com and since those obviously don't exist, it just sits there until it eventually times out. Anyone know of a way to terminate unwanted UNC requests quickly?
  5. 1 point
    Sadly, this is a problem I had to face myself, there's nothing you can do. Disabling/removing DWM/switching to Basic/Classic theme in Windows 7 disables global Vsync for the entire desktop that DWM provides. Since you're at more than 60Hz, it's even more noticeable. In Windows 8/8.1/10 DWM cannot be removed normally, therefore Vsync is always turned on and on there, everything looks fine. Not to mention, DWM in Windows 7 helps you with the GPU acceleration for the desktop drawing, rather than having it all on the CPU. While I myself had used classic theme on Windows 7 and disabled DWM in services.msc, I think the constant screen tearing is not worth the trade-off. Best bet is to turn on Aero, use small taskbar size, and disable any animations. Your GPU is between GT 1030 and GTX 1050, it can handle Aero Aero really got bad wrap back when Vista came out, people still had MX440's in their PCs back then. The drivers were very buggy at the beginning, as it was a completely new WDDM architecture. In Windows 7, Aero is not discouraged anymore and was perfected in my opinion. But the bad image stayed from the Vista days. Yes, there are some annoyances with Aero with the annoying messages (The color scheme has been changed to Windows 7 Basic,) but that's easily fixable: https://www.sevenforums.com/tutorials/70829-program-compatibility-assistant-enable-disable.html
  6. 1 point
    So Microsoft don't give a crap to even offer it to home users... We'll lay our hands on 'em updates anyway, MSFN collaborative mind has experience in it...
  7. 1 point
    Yes. If you use installer, it provides you an option to select which mode to use. If you install manually, then Accent mode is used by default (with opacity = 4).
  8. 1 point
    WE version can do that as well, just it's grayed out in older versions of Firefox, prob due to their limited support for WEs, but in Firefox 64 you can enable it just fine.
  9. 1 point
    Google will say you many bul***** like adblocker decrease performance but actual reason is that they can't milk money from users if they don't watch ads.
  10. 1 point
    It took over three years, but I've done it! It works on Windows 7 Professional SP1 64-bit (created a quick VM to test it) I've copied Windows 98SE files and made registry keys and folders as shown in the screenshot. (the .htm file was made while making the screenshot. Just like on real 98 system, it disappears shortly after launching the Easter Egg) The window will glitch out at first, but just move mouse around inside of it and then move it out of the sight and back again to redraw everything and voila! All the buttons run their expected programs, except the Connect to the Internet button which does nothing. The weldata Easter Egg works as well! The tickbox for running at every startup does work correctly. No compatibility settings required. On my main PC running Windows 10 Pro 1803 the app closes after the window glitches. Bummer The weldata Easter Egg still works there. Main thing is that WELCOME.EXE has a hardcoded path to Applications Data folder, so it will not look anywhere else. And it will differ in WELCOME.EXE from other locales.
  11. 1 point
    New version doesn't work for me: MKVMerge seems to be looking for "XPVCRT.dll," whatever that is. Should I rename MSVCRT.dll? Edit: That seemed to fix it. One of my pet peeves: a product drops support for users of an older product like Win XP, but only because they didn't think it looked "cool" enough.
  12. 1 point
    Well, considering that: Windows Embedded Standard 2009, Extended Support will end on Jan. 8, 2019. Windows Embedded POSReady 2009, Extended support will end on Apr. 9, 2019. ...it does make sense. That's not to say we'll give up on XP so soon, of course!
  13. 1 point
    6/13/2017 13:00 EDT Microsoft releases new Windows XP security patches, warns of state-sponsored cyberattacks: https://www.theverge.com/2017/6/13/15790030/microsoft-windows-xp-vista-security-updates-june-2017 The updates are available from the Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4012583 The official Microsoft article: Microsoft security advisory 4025685: Guidance for older platforms: June 13, 2017: https://support.microsoft.com/en-us/help/4025687/microsoft-security-advisory-4025685-guidance-for-older-platforms
×
×
  • Create New...