Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/11/2023 in Posts

  1. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230311-3219d2d-uxp-6f99b9744-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230311-3219d2d-uxp-6f99b9744-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230311-3219d2d-uxp-6f99b9744-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230311-d849524bd-uxp-6f99b9744-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230311-d849524bd-uxp-6f99b9744-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230311-d849524bd-uxp-6f99b9744-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230311-d849524bd-uxp-6f99b9744-xpmod.7z Official UXP changes picked since my last build: - Issue #1693 - Use scoped enums for IDBTransaction. (c920f32df) - Issue #2135 - Bug 1430303: Implement ShadowRoot.pointerLockElement (3dfffeaec) - Issue #2135 - Bug 1430305: Implement ShadowRoot.fullscreenElement (e286eb8ad) - Issue #2135 - Bug 1413102: Ensure Shadow DOM boundaries are dealt properly in event handling (24572438a) - Issue #2135 - Bug 1413102 (Follow-up): Ignore current target because of shadow DOM retargeting (1bb2009f6) - Issue #2135 - Bug 1323815: FocusEvent.relatedTarget should work consistently with MouseEvent.relatedTarget (1185cfe3f) - Issue #2135 - Bug 1438129: Remove ShadowRoot.applyAuthorStyles. (3350af82c) - Issue #2135 - Bug 1430301: Implement ShadowRoot.elementFromPoint/elementsFromPoint (e64aeea52) - Issue #2135 - Bug 1356496: Don't use nsIDOM* in ConfirmSelectionInBody (b2c77e5ed) - Issue #2135 - Bug 1066965: Make contentEditable and spellchecking to work in Shadow DOM (010db07bf) - Issue #2135 - Bug 1453789: Remove Element.createShadowRoot (45c179d01) - Issue #2135 - Bug 1410578: Make <link rel="stylesheet"> work in shadow trees (588c2154a) - Issue #2135 - Bug 1455891/Part 1: Improve StyleChildrenIterator (263b719ef) - Issue #2135 - Implement sequential focus navigation for shadow DOM (56193120c) - Issue #2135 - Bug 1518795: Properly track responsive content in a connected ShadowRoot (7b395189a) - Issue #2135 - Bug 1329877: Optimize AncestorFilter usage in lazy frame construction (7924a2f60) - Issue #2135 - Bug 1414692: Adopt shadow roots when adopting a shadow host across documents (b72ddcf65) - Issue #2135 - Bug 1393806/Part 1: Change nsNodeUtils cloning/adopting stuff to use an ErrorResult for errors (e65a864a3) - Issue #2135 - Bug 1393806/Part 2: Modify AdoptNodeIntoOwnerDoc to use the non-XPCOM version of document.AdoptNode (3062964d2) - Issue #2135 - Bug 1393806/Part 3: Change dom::ReparentWrapper to take an ErrorResult (9f0fb9c16) - Issue #2135 - Bug 1425864: Ensure printing documents which have shadow DOM works (015148fcc) - Issue #2135 - Bug 1419803: Use GetComposedDoc instead of GetUncomposedDoc in ContentEventHandler (70d493586) - Issue #2135 - Bug 1433669/Part 1: Remove dead function (2f9186959) - Issue #2135 - Bug 1433669/Part 2: Flush the document instead of the shell in ContentEventHandler (4d778226e) - Issue #2135 - Follow-up: Fix crash for passing nullptr as an argument to the aNodesWithProperties parameter (c194fbf6a) - Issue #2135 - Follow-up: Fix typo (9cb33ab84) - Issue #2046 - correct debug assert for intl_FormatRelativeTime() (3fb11e542) - Issue #2135 - Follow-up: Fix potential crash if shadow root is null (ad929c5dd) - Issue #2136 - Part 1: Implement CSS inset property (21d468ee6) - Issue #2136 - Part 2: Regenerate devtools CSS database (ae26d8a04) - Issue #2143 - Implement CSS env() Environment Variables (2b903a20b) - Issue #2135 - Follow-up: Ensure document is not null in nsImageLoadingContent::BindToTree (cfef3fa48) - Issue #2148 - Root the RegExpShared in RegExpMacroAssembler. (1f0df8f42) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Set compatversion for hardcoded overrides to 102.0 (5a627b6ce) - [Pale-Moon] Issue #1915 - [SSUAO] Add override for Instagram (c8488397e) Official Basilisk changes picked since my last build: - Revert "[Basilisk] Fade out tab label on overflow instead of ellipsis" (15e3a38b5) My changes since my last build: - [Basilisk] ported PM version of tab caption fading to here (2a32b18f4) - [Basilisk] add tab caption fading to CtrlTab (f159e44b2) - [Pale-Moon] add tab caption fading to CtrlTab (5db2ae1aa) - Revert "revert last rev (7faa37b7) and revert rev b7e45308 and 9824659d instead." (1b1d672dc) - Revert "reverting rev 22dc363c and 233802c9 for now since I got a crash in destructor of RegExpShared." (6f99b9744) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.
    5 points
  2. All you need to do is delete the updater.node file.
    3 points
  3. https://www.nirsoft.net/utils/chromepass.html chrome stored passwords can be retrieved with this little free portable utility.
    3 points
  4. Windows Live Essentials applications are x86, so Dependency Walker x86 must be used.
    2 points
  5. ... But do take note that the password encryption used by Chromium forks uses data specific to the host system, so that utility can only decrypt and retrieve account credentials from the "machine" they were "created"/stored on, i.e. the browser profile isn't just enough to retrieve the credentials (unlike Firefox and forks) ... I was painfully hit by that when my laptop "died" (actually, its iGPU did) in the start of 2022; my portable 360EE versions (11/12/13/13.5), each with its separate profile, live on a USB HDD - when I connected that to a second laptop in my household (Win7SP1x64), the browsers+profiles launched fine, but I was unable to retrieve site account credentials with chromepass on that second machine ... So, I advise everyone reading this: Keep account credentials on a physical (piece of paper)/digital (USB drive) copy "unattached" to the machine you're currently working on ... FWIW, I retrieved 90% of my credentials from within a stored Serpent 52 profile ... In the end, my laptop was repaired and I retrieved (and backed up on paper) those missing 10% credentials (for sites running ONLY on a 360EE variant, not St52) via launching chromepass there ...
    2 points
  6. https://github.com/abbodi1406/dotNetXP https://github.com/abbodi1406/vcredist/releases/tag/v0.35.0
    2 points
  7. ... For me, the first map there (Wifi Triangulation) loads (both map/satellite view) if I enable the geolocation API (in St52: geo.enabled;true - I had it toggled to false, for privacy concerns ); but the second map (IP Address based on ISP) still displays the quoted error in satellite view, map view loads a lightblue colour:
    2 points
  8. I don't THINK that they lock threads here so much. I know on a lot of places that necro-posting is frowned upon, but not so much here.
    2 points
  9. Note - there is a known issue if you run this browser with a very long sub-folder file name. Please rename the downloaded file upon download, the names here are only to distinguish their differences. This thread is devoted primarily to WinXP and a Chromium fork based on Chromium v86. Any discussions regarding v86 and its "age" will be reported to the mods as "disrespect" and in direct violation of Forum Rule 7.b. 7.b This community is built upon mutual respect. You are not allowed to flame other members. People who do not respect personal opinions and/or personal work will be warned in first instance. If you ignore the warning and keep on flaming, you will be banned without notice. This project is my personal work that I share with MSFN because there is a need for a "relatively modern" web browser for use in WinXP and v86 has performed "reasonably well" in that regard. The user-base is perfectly aware that XP will not serve 100% of our needs, that v86 will not serve 100% of our needs, we know this and accept this, we are not here to be told to "move on" from XP and what works for us in XP. We The Community can respect this endeavor in the same manner that we respect content shared at MSFN threads devoted to Win98 and Win2000 without trolling such threads and citing "age". Many thanks to all that continue to support this personal work. There is a combination of several versions to choose from. Regular versus Ungoogled -- ungoogled intentionally breaks telemetry sent to the Chrome Web Store, this in turn breaks the "Add to Chrome" feature at the Chrome Web Store so extensions need added via other means. WebGL enabled/disabled -- WebGL may or may not work on older hardware, so mileage may vary. Translation enabled/disabled -- Chromium-based browsers have an embedded Google Translate context menu feature, I offer versions with and without this embedded feature. WinXP / Win10 skin -- I only use this browser in WinXP and therefore I prefer it to look-and-feel like everything else I run in WinXP. Others prefer the more "modern" Chrome GUI and the Win10 skin attempts to please that crowd. https://www.dropbox.com/s/wsch5owpc8yv184/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/fl9ureunhg2k2x7/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/whki7vldp655nx1/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/59561mewhx0ufzb/360ChromePortable_13.5.1030_r8_regular_webgl-disabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/l3e5m48tzzb30bj/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/npnxobadg89m7uj/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/ithrm1ttt2nypb1/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/f2935ei6q5d0w3u/360ChromePortable_13.5.1030_r8_regular_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/i9t2rul2t5g99ml/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/wqm2tzaum2088ph/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/wqzujgi97cyuf7u/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/tbt5g1pv9nazfo4/360ChromePortable_13.5.1030_r8_ungoogled_webgl-disabled_translate-enabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/g4g0jdgogoexa3p/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-disabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/bcsexi8cm5tw2np/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-disabled_win-xp-skin.zip?dl=1 https://www.dropbox.com/s/yz8usl2hgsbxtk0/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-10-skin.zip?dl=1 https://www.dropbox.com/s/pi43092cazygjz6/360ChromePortable_13.5.1030_r8_ungoogled_webgl-enabled_translate-enabled_win-xp-skin.zip?dl=1
    1 point
  10. Anyone have a problem with 3rd party sidebar gadgets that are not re-loading after reboot since new kernel update? Everytime I reboot the computer I need to re-attach them to sidebar
    1 point
  11. The original (Chinese) 360EE variants do NOT contain such a feature (nor do they contain the ability to export stored passwords) ...
    1 point
  12. I use an excel file to save all of my passwords but this site is an exception because I don't have too much interest on it. can you tell me if the original chrome 360EE features the button to unveil the passwords or was it removed from the modified versions for whatever reason else.
    1 point
  13. ... Where do you plan to go, BTW? From my standpoint, this "project" will be discontinued once pukkandan abandons support for Python 3.8 altogether, which might very well be before its official EoS in 2024 ... IIRC, 3.7 is supported for a minority of users (on Vista and some Unixes where it can't be updated further) and 3.8 is still supported for the sake of Win7 users... Win7 support by most app authors/vendors will be waning as 2023 progresses (spearheaded by Google's decisions, no less), so the "inevitable" will happen... Anyone planning on backporting Python 3.9 to Vista SP2/XP SP3, please?
    1 point
  14. ... As others have hinted already, it may very well be an issue with your specific graphics card/its non-updated driver... Can you test that link you posted in latest Serpent 52? It works fine here via HTML5+WebGL (Adobe Flash hasn't been enabled): St52 doesn't block WebGL by default if your H/W can support it, so if you can't get it working in St52, "rebuild_8" will be moot for you... My 2c, of course ...
    1 point
  15. sorry I only tried on 8 and xp great to see it's working
    1 point
  16. I'm wondering what will exactly happend with win32 apps and Windows 10 LTSB 2015 in 2025. I love that version of Windows 10!
    1 point
  17. No Sorry necessary at all @AstroSkipper as i can see (and appreciate) all your helpful input and contributions here! Well, coming from Thunderbird 2.0 (as i wrote here, pt 4.) i observerd this "alt row highlight" had gone in mailnews (at least per default), didn't find a reltated switch in the preferences, so i searched the web. Found this link where is described the solition with a userChrome.css: #threadTree treechildren::-moz-tree-row(odd) { -moz-appearance: none !important; background-color: rgb(232,232,232) !important; } which i've putten in the .\Profile folder of mailnews. Since this didn't show the desired result, i even added the preference toolkit.legacyUserProfileCustomizations.stylesheets set to true - but it didn't work neither. What was your way to get "alt row highlight" in mailnews?
    1 point
  18. Why not just unplug the fan and underclock the CPU? (might require modding BIOS to avoid CPU fan error if it causes a system halt) You can use CrystalCPUID on 9x for this and there's plenty of software for DOS to slow down the CPU in it. My ThinkPad T42p has Intel 855PM chipset and it seems to be the latest one from Intel that is fully officially supported under 98.
    1 point
  19. Good to hear that more people are able to make it work on older OS's, so that it won't be discontinued when I'm gone. That said, why version 2023.02.17? That was before a fix for a new throttling issue (see here). Also, you could make it start faster, when enabling "Lazy loading extractors" before compile from master: python devscripts/update-version.py python devscripts/make_lazy_extractors.py python pyinst.py
    1 point
  20. Is there any way in how to get the Windows 10 build 98xx Start Menu, otherwise known as the RT 8.1 Update 3 Start Menu, on Windows 8.1?
    1 point
  21. @win32 I managed to add the missing features needed to run FF 60 ESR on Vista x86, but I get an appcrash error. I disabled DEP via a command in CMD. What could I have done wrong?
    1 point
  22. chrome://flags/#ignore-gpu-blocklist As pointed by @VistaLover for example.
    1 point
  23. you can't get past 3.25 GB with any 32-bit windows without patching the system
    1 point
  24. There is also a "PAE Patch" for XP x86 that also allows you to use up to 128GB of RAM.
    1 point
  25. New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rthost.win/basilisk/basilisk55-win32-git-20230311-bceff7b5b-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20230311-bceff7b5b-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #1693 - Use scoped enums for IDBTransaction. (c920f32d) (e979bbad9) - ported from UXP: Issue #2135 - Bug 1430303: Implement ShadowRoot.pointerLockElement (3dfffeae) (a539f47bb) - ported from UXP: Issue #2135 - Bug 1430305: Implement ShadowRoot.fullscreenElement (e286eb8a) (85c7bdf68) - ported from UXP: Issue #2135 - Bug 1413102: Ensure Shadow DOM boundaries are dealt properly in event handling (24572438) (261bfcadc) - import from UXP: Issue #2135 - Bug 1413102 (Follow-up): Ignore current target because of shadow DOM retargeting (1bb2009f) (5a7b071dc) - import from UXP: Issue #2135 - Bug 1438129: Remove ShadowRoot.applyAuthorStyles. (3350af82) (5a041769a) - ported from UXP: Issue #2135 - Bug 1430301: Implement ShadowRoot.elementFromPoint/elementsFromPoint (e64aeea5) (b7a513b2a) - ported from UXP: Issue #2135 - Bug 1356496: Don't use nsIDOM* in ConfirmSelectionInBody (b2c77e5e) (9f1361118) - import from UXP: Issue #2135 - Bug 1066965: Make contentEditable and spellchecking to work in Shadow DOM (010db07b) (df33d59d4) - ported from UXP: Issue #2135 - Bug 1453789: Remove Element.createShadowRoot (45c179d0) (0d44f7d04) - ported from UXP: Issue #2135 - Bug 1410578: Make <link rel="stylesheet"> work in shadow trees (588c2154) (5ccbebc42) - ported from UXP: Issue #2135 - Bug 1455891/Part 1: Improve StyleChildrenIterator (263b719e) (7a99dec57) - ported from UXP: Issue #2135 - Implement sequential focus navigation for shadow DOM (56193120) (fa81bc7c9) - import from UXP: Issue #2135 - Bug 1518795: Properly track responsive content in a connected ShadowRoot (7b395189) (5b04b8ae3) - import from UXP: Issue #2135 - Bug 1329877: Optimize AncestorFilter usage in lazy frame construction (7924a2f6) (e951c9e2d) - import from UXP: Issue #2135 - Bug 1414692: Adopt shadow roots when adopting a shadow host across documents (b72ddcf6) (4ecb58c73) - import from UXP: Issue #2135 - Bug 1393806/Part 1: Change nsNodeUtils cloning/adopting stuff to use an ErrorResult for errors (e65a864a) (fbefa53b8) - import from UXP: Issue #2135 - Bug 1393806/Part 2: Modify AdoptNodeIntoOwnerDoc to use the non-XPCOM version of document.AdoptNode (3062964d) (30e05716d) - ported from UXP: Issue #2135 - Bug 1393806/Part 3: Change dom::ReparentWrapper to take an ErrorResult (9f0fb9c1) (2e76049ac) - import from UXP: Issue #2135 - Bug 1425864: Ensure printing documents which have shadow DOM works (015148fc) (e96983c69) - import from UXP: Issue #2135 - Bug 1419803: Use GetComposedDoc instead of GetUncomposedDoc in ContentEventHandler (70d49358) (31b47cb97) - import from UXP: Issue #2135 - Bug 1433669/Part 1: Remove dead function (2f918695) (e31a4854b) - ported from UXP: Issue #2135 - Bug 1433669/Part 2: Flush the document instead of the shell in ContentEventHandler (4d778226) (d1e5efcf8) - import from UXP: Issue #2135 - Follow-up: Fix crash for passing nullptr as an argument to the aNodesWithProperties parameter (c194fbf6) (b5e5cd188) - import from UXP: Issue #2046 - correct debug assert for intl_FormatRelativeTime() (3fb11e54) (56df8a677) - import from UXP: Issue #2135 - Follow-up: Fix potential crash if shadow root is null (ad929c5d) (ef8466fa6) - import from UXP: Issue #2136 - Part 1: Implement CSS inset property (21d468ee) (2d1a95825) - import from UXP: Issue #2136 - Part 2: Regenerate devtools CSS database (ae26d8a0) (e652e63b1) - import from UXP: Issue #2143 - Implement CSS env() Environment Variables (2b903a20) (44882a2d2) - import from UXP: Issue #2135 - Follow-up: Ensure document is not null in nsImageLoadingContent::BindToTree (cfef3fa4) (105fae466) - Revert "revert last rev (3ffaab07) and revert rev b1214c8d and 1d47bb34 instead." (20a127dae) - import from UXP: Issue #2148 - Root the RegExpShared in RegExpMacroAssembler. (1f0df8f4) (cb016b322) - Revert "reverting rev d5eb68a1 and 9535b71a for now since I got a crash in destructor of RegExpShared." (bceff7b5b)
    1 point
  26. Do not copypasta text from other sites and make it a thread. Put the link to where you stole this info from. MSFN is in EU so we have the EU Copyright Directive to deal with.
    1 point
  27. I haven't much info on this machine, but maybe the Xplore iX104C2 or iX104C3. It seems to come with the Intel 855GME. The audio is AC97. Up to 1Gb memory. 1Ghz or more. I also have no experience with the Intel 855GME. But it appears to support Win9x. Maybe not Win95? Edit: Nope. Watched a harddriver replacement video, and it has a fan. But it is a fairly small fan, and in an ideal location. Temps me to try the C4 at 1.4Ghz, with CPU throttling and a custom (larger) heatsink (Digikey). However, it would probably need USB for a keyboard. So no unicorn here.
    1 point
  28. OT ...Then, most probably, this one: https://www.youtube.com/watch?v=N2qqfafRdEQ /OT
    1 point
  29. Check out https://learn.microsoft.com/en-us/lifecycle/products/windows-10-enterprise-ltsc-2021?source=recommendations
    1 point
  30. my god just has to manually unlock and resize it, solved, ty so much
    1 point
  31. Just resize the taskbar, google how.
    1 point
  32. Exactly! Even the newest supported Chromium (109) is still going to work fine for a long time to come. Luckily Firefox is still supported, which is fantastic. There are many options for 7 at this moment, and while it may eventually end up where XP is at now, the future is much brighter right now for 7 users. (It's even brighter than that if you're on 10/11, but I'm staying with 7 for now because I prefer the old-school interface and the speed).
    1 point
  33. Checking back in, this time from 7 x64. At this point there's nowhere to go but forward from here, as much as I hate to say it. Unless I'm on a PC so old that I need to use XP for full driver support, I'm pretty much sold on 7 for the foreseeable future. Though in some ways it was a regression from XP, it managed to improve in many ways that are important to me. Download speeds out of the box are MUCH better, so there's no serious need to keep a download manager around unless you are dead set on getting every last kilobyte your router is capable of routing. The kernel is significantly better too...besides being able to run a much wider range of browsers (and having much more modern options available), browsers seem to be much snappier and perform a lot better. I've currently settled on Waterfox G3 (Firefox 78-based). It's very fast, still has the now-deprecated Flash support, and just seems to be a good 'base' browser to put on a 7 build...and of course you can still download and experiment with other browsers too. I figure that I can download and try a newer version of Firefox, or a modern Chromium build, if a site gives me trouble in Waterfox. It seems 7 is on the road to taking the torch from XP as the new 'superstar' of legacy OSes and I predict that there will be many, MANY browser options for 7 users as time goes on. In general, it's good to be able to look at your options and see what works best. It was impressive to see the Mini Browser working so well in XP, but the aging XP kernel is being pushed to its limits, and of course the performance of Chromium 87 in Win7, both x86 and x64, just blows it out of the water. The fact that Chromium 87 even works in XP is amazing in itself, so I wasn't expecting miracles performance-wise.
    1 point
  34. I actually did manage to get both running eventually with the help of R3n from eclipse and thanks to win32 to make this possible, mspaint gave the same error as wmp12 which makes me believe its pretty close to be workable
    1 point
  35. Judging by the "wsus.reg" on the desktop... You're probably not using the normal windoze update servers. This poster is banned now so they wont be responding, but i highly suspect people are not lying when they say the original MS servers dont cater to 2000 and XP anymore. Third-party WSUS servers are the only way to do it reliably since I think almost a year ago now.
    1 point
  36. We are fortunate to have a security guru like @Sampei.Nihiraat MSFN! Too many users of legacy Windows seem to think online threats are just a hoax.
    1 point
  37. okay it seems like you're not objective cause you are windows 7 hater (I looked on your profile) my core 2 duo t5870 is 2 ghz at base clock! I simply asked why are you recommending vista when we can't use it? (security reasons and office) I don't have any experience in kernel stuff or programming. so extending something isn't my cup of coffee. I would buy new laptop if they were in stock (I already said that) like paying 800 dollars for pentium laptop is something I simply refuse to do. We already upgraded the ram to 4gb so it seems to be little better and I'll try to reinstall windows 7 32bit as you suggested and I'll not update it. (even though that will limit my ram to 3 gb and something?) Please try to not attack me for having older laptop... I mean you could be windows 7 hater but this was inadequate.
    1 point
  38. It’s pretty clear that M$ does not want Windows Update to work for anything older than Windows 7 SP1. At last report, SHA-2 support did not have to be manually installed in order to get Windows Update working for Win7 (but it must be SP1 rather than RTM), which raises doubts about the official explanation - which btw still does not list the latest error code 0x80072EFE.
    1 point
  39. You could run sfc /verifyonly (which does not “fix” anything if I remember correctly), then check CBS log to see if anything other than extended kernel files was found, but that does sound rather tedious to me.
    1 point
  40. I was under the impression that this topic is about using software that requires Win7 or above on Vista with the aid of win32’s extended kernel. It has become clear to me that you are not particularly interested in security software, and therefore see no reason why others wouldn’t be content with a legacy version of Malwarebytes. Personally, I am not very interested in gaming, but I would never presume to declare all discussion of PC games as being OT in someone else’s thread.
    1 point
  41. Frankly, that is false, and your screenshot is of some higher version that contains the EOL time bomb. As I already stated, it is well known around here that 4.4.304.0 did NOT contain the April 2017 time bomb. In July 2019, I posted a screenshot of that specific version working on Vista here. The only thing “not working” to my satisfaction was that it failed to prevent download of the EICAR test file more often than not, which is why I prefer Avast antivirus on Vista. (Also It Is Not Customary To Capitalize Every Word In America.)
    1 point
  42. I regret to deviate off topic, but reading this made me laugh the hardest I've laughed all week
    1 point
  43. The fact that Chrome 50 will run on Vista has been known for years, as posted in Last versions of software for Windows Vista and Windows Server 2008 under Web Browsers , which even has links to FilePuma. I don’t think it will run on XP though.
    1 point
  44. Figured it might come to that, I noticed the comment about unauthorized distribution in one of the files shortly after I uploaded it. It doesn't look like much more than an user agent spoofer for facebook.com. Let's see what happens when they go YouTube route...
    1 point
  45. The author would have to pack the extension separately for old Chrome versions and distribute that version outside of Chrome Store because CRX_VERSION_NUMBER_INVALID. Edit: file removed
    1 point
  46. Just an interesting observation on my Dell Inspiron running Windows 7: once you first install "the classic" Adobe Reader XI, you will be presented with a notification in the system tray. Once you click, it will give the following window, encouraging you to update to Adobe Reader DC. You can decline it if you change it from "Upgrade" to "Remind Me" or "Don't ask again", etc. If you blindly click upgrade you will likely get DC.
    1 point
  47. Your link basically says that Slimjet is as bad as Chrome (perhaps a bit worse). If Chrome contains "spyware," then a browser containing spyware now has 63 percent market share. OP yoltboy01 evidently likes Chrome very much, and would go to great lengths just to use a slightly different but still obsolete version released in 2016. Personally, I would never recommend "Advanced Chrome."
    1 point
  48. Hello yoltboy01, I share your fondness for Windows Vista, but the obvious answer to your desires is to buy a Windows 7 product key and upgrade (except the browser versions you mention are very old for use on Windows 7). Chrome is not a developer's project. As you already know, developers were able to backport a few open-source Chromium versions that did not support Vista. I tried Slimjet 11 and 12 (based on Chromium 51 and 53 respectively) on Vista x86 when they were new, back in 2016. If no developer's project is satisfactory to you, then you could always become a developer yourself. Regarding IE10 for Vista, see https://msfn.org/board/topic/176927-internet-explorer-10-on-vista/. Regarding Office 2013, see https://msfn.org/board/topic/177934-install-office-2013-on-windows-vista/. Regarding Firefox forks that are still being actively developed (including a build of Basilisk based on Firefox 55): https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-for-xp/.
    1 point
×
×
  • Create New...