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/13/2019 in all areas

  1. 2 points
    They are correct for single-core. You should hide the update if offered again.
  2. 1 point
    idk what to say i just made an acc
  3. 1 point
    This entry is not needed, at least for my HTTPSProxy and / or I have additional entries in the config.ini. That's why you do not have to worry. @Mathwiz For [SSL Pass-Thru], try the entrys "*update.microsoft.com*", "c.microsoft.com*", "*one.microsoft.com*" and remove "www.update.microsoft.com" from [SSL No-Verify]. @ All Good News The faulty update KB4487085 is no longer available for AU / WU / MU.
  4. 1 point
    Only needed for the update catalog, not for the regular WU or MU site. I should've made that clear....
  5. 1 point
    VLC Media Player 4.0 may work on Windows XP if there is a way to edit out the dependency IF_NAMETOINDEX. The same type of issue appeared in March 2016 on GitHub and was resolved by removing at compile time: https://github.com/openslide/openslide-winbuild/issues/7#issuecomment-192429311 Does anyone want to take a stab at it? I don't have time at the moment. The latest VLC 4.x builds are available here: https://nightlies.videolan.org/build/win32/last/ (today's zip file is https://nightlies.videolan.org/build/win32/last/vlc-4.0.0-20190213-0246-dev-win32.7z)
  6. 1 point
    KB4462174 does not appear to be another Japanese calendar update fix, it's a real security fix. Is there anyone here who is using Office 2010 on a genuine POSReady installation (not a hacked XP installation) who could make an official support request to Microsoft about this, while there's still time?! Although Office 2010 is supposed to work with XP, IIRC unfortunately Microsoft's policy is that once an OS is unsupported, all applications running on it are also unsupported, so I don't think there's any use in an XP user complaining to them. If it's not working on a genuine POSReady installation though, that's a different matter, for a couple more months anyway!
  7. 1 point
    Unless people are seeing issues, in this case the delay-load linkage to brcypt.dll.as such shouldn't be a problem, even in the original Office 2007 Compatibility Pack SP3 (KB2526297) MSO.DLL (12.0.6607.1000) has it. I thought the same thing you did at first, but going back and checking earlier versions seems reassuring.
  8. 1 point
    roytam - I remain confident that dencorso, heinoganda, bersaglio and Dave-H will keep Win 7 going for at least 12½ years. I still have a flip phone.
  9. 1 point
    One possibility is to uninstall an update with ERD Commander 5.0 (bootable medium). If this is not possible, use another bootable medium (eg Kaspersky Notfall CD) in the registry under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations] to see the entries "x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.24558_x-ww_24ed72db" and " x86_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.24558_x-ww_32b5093b" delete (make sure that the entries may differ by name something that is the GdiPlus entries with 1.0.6002.24558). Under the folder "%windir%\WinSxS" "\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.24558_x-ww_24ed72db" delete (here also names may differ slightly, pay attention to 1.0.6002.24558). Restart and uninstall KB4487085 in Safe Mode. I wish you success!
  10. 1 point
    Unchartered but well traveled, for years now. Today was an unprecedented disaster courtesy of Microsoft. I've never had to do such a thing in my life...until today. Humiliating.
  11. 1 point
    At this moment I'm trying to figure out whether I do or not. A techie friend of mine doesn't think I would get much benefit from overclocking the CPU, unless my multimedia production projects sufficiently rely on the CPU and properly take advantage of hyperthreading. Since I don't know if I will need that extra horsepower, I wanted to leave the option open of pursuing it with a sufficiently beefy PSU rather than having to buy a new one down the road. Assuming that it would be safe to do so with my current UPS. If I don't do any overclocking, the peak load wattage for my intended setup would be 698W. The calculator recommended a 750W PSU for that. Well within my UPS' capacity. However, that techie friend of mine said that when buying a power supply, I should buy one that actually has 50% more wattage than the peak usage determined by power supply calculators. He says this factors in power supplies losing performance as they age, and he considered the PSU the most critical part of a computer. By his metric that would mean that I'd need to look at buying a 1200W PSU. So I'm not sure what to think. I've canvassed some of my other techie friends; most either say "don't hook your UPS up to a computer with a PSU wattage rating that's higher than your UPS' output, ever" or "As long as your peak wattage doesn't exceed the UPS's output it should be fine." Roughly an even split. I don't know what to think. Reviewing my posts in this thread, @dencorso, I have no idea how you came to such a conclusion. This leads me to believe you are intentionally and maliciously misinterpreting what I said. To be clear, I don't fault you for not remembering my previous posts and threads in MSFN over the years, like when I had asked almost five years ago about the feasibility of upgrading my desktop to a DDR4-based configuration. (Even though you were active in those topics.) I also don't fault you for seeing some of my recent posts elsewhere in which I have mentioned being in the process of buying a new set of parts of my computer. (Which outright invalidates your claims about what I've said.) I certainly can't fault you for not knowing about the extensive discussions I've had with friends and acquaintances on viable parts for a new setup, though @XP-x64-Lover can vouch for me. I do fault you for putting into people's heads (like @Mcinwwl, who upvoted you) the idea that I said something I didn't, particularly when there was no reason for you to stoop to such a level. That's an absolute dick move on your part, and I do not appreciate it at all. But fine. Let's clear the air, since this thread has gotten off-topic as it is. In 2008, I overhauled my desktop computer with the goal of having a long-lasting, future-proofed setup which would not need a complete overhaul for a long time. That included parts which were, for the time, a big investment. Up until these hardware issues started happening last year, it seemed like these parts would last indefinitely no matter how hard I pushed them on a daily basis. I don't like contributing to the e-waste problem. If a computer's still working, I'd prefer to find that computer a use. As I already mentioned earlier in this thread, I had plans to reuse the entire setup in another PC, something which would not need current-generation high-end parts. However, there's a two major considerations where I am in my life right now that shape my choices: First, I've been diagnosed with cancer and have a genetic predisposition for other cancers. I had to go through chemotherapy while I was studying for my Bachelor's, and that left me with very little money by the time I got started on my career. This is a major reason why I have not worked on upgrading my desktop computer sooner: I have had to spend the past year or two just trying to make back the money I had to spend finishing my degree and staying alive. Even then, I've been saddled with medical debt, some of which was sent to a debt collection company despite trying to stay on top of the bills. In order to ensure I live for a while longer I need annual monitoring with CT scans and MRIs. Where I live now, these are incredibly expensive. I would have preferred to wait a few more months before buying the parts I need for the new configuration, but the hardware issues with my current configuration have forced my hand. Yet it's still a slow process precisely because of my financial situation. I've been trying to rebuild my credit, which has suffered at the hands of debt collectors even as I continue to negotiate with them. I can't just snap my fingers and buy everything I want right this minute. The other major consideration is that I don't have a large living space. In spite of my best efforts, my career prospects required me to pack my bags and move halfway across the country to one of the more expensive places to live in the nation. I took only what I could fit in a car. To avoid having to spend half my paycheck on rent and half-again on utilities, I've been living in sublets. So, having walked you through my current life situation, you should now have a better understanding of my thought process. If the problems behind my computer's current configuration were relatively inexpensive to fix (replacing an aging, faulty PSU or a few RAM sticks) I would be inclined to hang on to those parts, even given my current living conditions. Just so we're clear, using a new PSU intended for a far more power-hungry setup in order to diagnose whether or not the PSU is the source of the hardware problems does not mean I would keep using that new PSU for my current setup. I would be more inclined to buy a less powerful PSU to replace the ailing PSU, were it confirmed that the old PSU is indeed ailing. Replacing the CPU or motherboard, however, is a different story. At that point I would be more inclined to just sell the parts that still work and recycle the rest. So, there you go. I didn't expect to have to explain my life situation just for because I sought help regarding how power supplies and UPSes interact, but here we are.
  12. 1 point
    Certainly a good idea, but it shouldn't be necessary. Windows updates should not completely hose an operating system. But regardless I can pull the data off the drive, no loss ~95% of my data was already backed up
  13. 1 point
    That's why one should do full backups before adding updates. Once I realized the system was foobar, I redeployed the jan 31 image, and lost nothing. I had to reinstall the latest Flash and Basilisk, though. Had I made a new backup imediately before updating, even that would've been unnecessary.
  14. 1 point
    Ublock origin legacy updater 1.6.7 ( Basilisk ) you may get it here : https://github.com/JustOff/ublock0-updater/releases/tag/1.6.7 Cheers PS : It is also good for firefox 52.9.1 esr and New moon !
  15. 1 point
    @dencorso, The KB4486463 update does appear to have been correctly installed. The system "dllcache" and "Driver Cache\i386" versions of "ntkrnlmp.exe" were both updated to version 5.1.2600.7649 and without having to do anything special. Although I use a multicore processor, I use the ACPI Uniprocessor PC HAL, and am therefore not actually using the KB4486463 kernel. My "ntoskrnl.exe" in use is version 5.1.2600.7581.
  16. 1 point
    Very cool. I don't really have any programming skills, but I keep the latest 32 bit version in my /palemoon directory, to have a standalone installer available for those who need it for offline use.
  17. 1 point
    With KB4487085 (gdiplus.dll, mf3216.dll), the file gdiplus.dll (version 5.2.6002.24558 vistasp2_ldr_escrow.190111-1700) causes a lot of problems. A test only to install the file mf3216.dll led to no apparent problems. Let's hope Microsoft released a working update for KB4487085.
  18. 1 point
    I had troubles after applying KB4487085. After installing KB4487085, many programs would not run correctly and I would sometimes receive errors like the following: "The procedure entry point sprinttf_s could not be located in the dynamic link library msvcrt.dll." "Error loading C:\WINDOWS\system32\NvCpl.dll" The second error message appear to be for the nVidia driver software. I removed KB4487085 and things seemed corrected.
  19. 1 point
  20. 1 point
    New Palemoon 27 Build! * This build is beyond official 27.9.4 build. 32bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190209-7450defff-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win64-git-20190209-7450defff-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from rmottola/Arctic-Fox: - Bug 1139152: IonMonkey: Don't improve types at MTypeOf for unknown types (d67dad359) - Bug 994016 - IonMonkey: Improve type information at branches with TypeOf (boolean, you are worthy too) (c90a6d6fc) (d9bf24c13) - import changes from rmottola/Arctic-Fox: - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) - Bug 1270591. Add support for checking for AVX & AVX2. Detecting AVX2 requires the use of a sub-leaf. (789319bd0) (eb895d30f) - import changes from rmottola/Arctic-Fox: - update libwebp to 0.6.1 (afa956138) - fix build on intel for libwebp 0.6 (97193d7a0) (7174a5119) - import changes from rmottola/Arctic-Fox: - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4) (74aff1670) - import changes from rmottola/Arctic-Fox: - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12) - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12) - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544) - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922) - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7) (805fc48eb) - reverting rmottola/Arctic-Fox changes in order to bisect memory leak and greasemonkey issue: - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb) - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34) - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da) - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340) - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313) - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256) - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85) - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979) - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2) - Bug 1137523 part 2 - Unprefix a few js_* functions I forgot in part 1 (e6beaf0d8) - Bug 1135816 - Handle unboxed object receivers when compiling getter/setter calls in baseline/Ion (82233087e) - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4) - Bug 1077002 - Give a better error message when showModalDialog is used (18d8ecc12) - Bug 1135792. Stop assuming that every binding for a global with a non-worker descriptor is a binding for Window. (dd0260c12) - Bug 1135810. Add more explicit checks for whether a descriptor wants Xrays or not instead of assuming that Xrays are desired if and only if descriptor.workers is false. (17ef71544) - Bug 1050456 - Part 1: Prevent prerendered pages from showing the slow script dialog (173044922) - Bug 1050456 - Part 2: Add a nsGlobalWindow::GetIsPrerendered helper (ac680a5f7) hopefully we can re-apply them later. (e1881afe9) - re-apply rev 805fc48eb20f089ae0b815ce137bd64d6993f451 (d1c585ecf) - re-apply rev 94617d85eb5ab3369bb44b099be3c6c4174fe6f6 (e07628294) - re-apply following changes: - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313) - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979) - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2) - Bug 1138265 - TraceLogger: Throw error when trying to enable in AsmJS (64c799042) (7450defff) following changes seem causing issues and they are reverted for now: - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb) - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34) - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da) - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340) - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256) - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85) - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)
  21. 1 point
    Hey guys, I put together an installer for Roy's browsers. It checks a file on my server to see the latest version (keeping that updated shouldn't be an issue for me) and then it downloads the latest browser version from roys site and installs it. Currently it supports Basilisk (x86 and x64), and New Moon (x86 and x64). Tested OSes with the installer include XP and Vista (both x86 and x64 editions) Other builds are not currently supported due to the sometimes irregular build interval http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe If you find any bugs, LMK Thanks for @WinClient5270 for noticing that you must have the visual basic runtime installed first for the installer to work. (Install VC Redist 2008 from Microsoft)
  22. 1 point
    So following changes seem causing issues: - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb) - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34) - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da) - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340) - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256) - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85) - Bug 1113369, part 1 - Introduce JS::ObjectOpResult and use it in js::StandardDefineProperty. (15663c476) - Bug 1113369, part 1½ - Avoid regressing error messages by adding obj to the ObjectOpResult methods that could throw a TypeError. (e063faf08) - Bug 1113369, part 2 - js::SetArrayLength ObjectOpResult support. (cf8326017) - Bug 1113369, part 3 - [[DefineOwnProperty]] ObjectOpResult support. (e16605a90) - Bug 1113369, part 4 - [[Set]] ObjectOpResult support. (6f94604d4)
  23. 1 point
    Since this issue has been discussed here , I would like to inform you that Mozilla 64 also suffers from the 23/25 min youtube mozilla bug. As it seems either they have not been able to fix it or simply they do not care. cheers
×
×
  • Create New...