Jump to content

Leaderboard

Popular Content

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

  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. Google finally announced the End Of Life date for Windows 7 as well as Windows 8.1, which will be in February 2023, with the release of v110 of their Chrome browser Source: https://support.google.com/chrome/thread/185534985/sunsetting-support-for-windows-7-8-1-in-early-2023?hl=en This will automatically also affect Google Chrome for Windows Vista Extended Kernel (although that might not be the biggest drama after all, since we Vista users can already be grateful that we got 61 versions higher than Chrome‘s initial EOL on Vista), Microsoft Edge for Windows 7/8.1, as well as many other Chrome forks like Opera. I hope Google only changes minor things, so that we can still run the browser, with a little tweaks here and there. If I think back to 2016, there were no ports for higher Chrome versions for Windows Vista, since we needed a kernel extension before we could run the necessary functions. What do you think? I wish Google would also offer an ESR channel, where W7/8.1 would continue to receive only security based updates for the next 12 months to come. I‘m using Firefox and I already know that Mozilla will probably merge W7/8.1 to the next ESR channel (v110-112?) too
    1 point
  11. Redirect the original ole32.dll file locally, perhaps it will help.
    1 point
  12. ... 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
  13. I direct you to Forum Rule 2.a. 2.a Use some common sense. Do not create identical topics or make identical posts in more than one forum. Think before posting and choose the right topic for your question or answer. Do not "bump" newly created topics until at least 24 hours have passed. If a topic has been "bumped" three times without any new replies, please consider reviewing and editing your original post and adding any information which you think may help other members in answering your question(s) or concern(s). When posting, have something to say, not just "My First post!" or "Cool site!!!" We sort of have the idea by now. :-)
    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. 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
  16. I will upload a "rebuild_8" of my version that has WebGL ENABLED out-of-the-box. But you will have to PICK ONE OR THE OTHER, it is not advisable to run MY version and Humming Owl's versions side-by-side! Humming Owl's versions SAVE data to the Windows Registry permanently. Mine only uses the Windows Registry for temporary data storage - but it will "see" the PERMANENT data stored by Humming Owl's versions. Again, PICK ONE OR THE OTHER, it is not advisable to run both side-by-side - not even if one has been "exited" before the other is launched - Humming Owl's registry writes are PERMANENT. I will have a "rebuild_8" new thread later this weekend or so.
    1 point
  17. 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
  18. FantasyAcquiesce, probably has done what I have done, a time or two. It is easy to duplicate. First you install Vbemp, then you install whatever Win2k+ driver has a matching hardware vendor and device identification, and finally you reboot with your new driver. But you are not using the Win2k+ driver. You are using Vbemp. The registry changed the name of your device, to match the Win2k+ driver. But if you go to "Device Manager" > properties on the video device in "Display Adapters" > "Driver" tab > "Driver File Details", you will find the the Vbemp driver files are still listed. FantasyAcquiesce has even said, in that thread: The Intel video driver from RetroSystemRevival will not work. In fact, if you don't install Vbemp first, you'll end up with the default (16 color 640x480). I will gladly eat my words, if wrong. The only way to have evidence, the driver works, is to have a screenshot of the "Driver File Details". But I've installed drivers from 2k/XP, on Win98, and have seen the results; even the exact same driver we are talking about. It doesn't work. But, on the bright side, some of those Intel 8**G** chipset and video device drivers seem to support Win98. The device I pointed out had one. The issue is finding something without a fan. It seems anything that old, tends to have a fan.
    1 point
  19. Then your Windows Registry has been polluted with 360Chrome entries that should not be there. Step 1 - CLOSE 360Chrome Step 2 - verify in Task Manager that 360Chrome is NOT RUNNING Step 3 - launch regedit - 360Chrome must NOT BE RUNNING Step 4 - go to this section of your Windows Registry Step 5 - if you have any 360 or 360chrome keys between Software and where I have 7-Zip, DELETE THEM and REBOOT THE COMPUTER Step 6 - delete the entire 360Chrome folder, PROFILE AND ALL, and extract a brand new folder
    1 point
  20. there's not one, there are multiple patches and beyond 4GB they all are unstable. the patch with best positive feedback was made up by @daniel_k anyway with the chrome360 rebuild 7 @NotHereToPlayGames this patch seems to be no longer necessary this patch is also the cause of some unexpected BSOD which is one of the main issues with the buggy Mypal68 @AstroSkipper
    1 point
  21. Mind telling where you got this info? I know the fact that each 32-bit Windows handle up to 4 GB RAM.
    1 point
  22. Yes, I know and I am already aware. I am talking about maximum RAM that can be used in XP 32-bit originally without patches.
    1 point
  23. Windows XP 32-bit in any edition (except Starter edition) can handle up to 4 GB RAM at maximum. Windows XP 64-bit, however, can handle up to 128 GB RAM at maximum, which is 32 times the amount XP 32-bit can handle at maximum.
    1 point
  24. @Ryder252! As we all know, Windows XP is an old OS. I would try the .NET Framework Setup Verification Tool first. Strictly following the rule: old tool with old OS. Here is a link from archive.org as the original site is no longer available on Microsoft: https://web.archive.org/web/20170213203348/https://msdnshared.blob.core.windows.net/media/2016/10/netfx_setupverifier_new.zip
    1 point
  25. New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230311-33f0551ea5-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230311-33f0551ea5-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20230311-33f0551ea5-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20230311-33f0551ea5-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - lineContainer can be NULL in nsIFrame::InlinePrefISizeData::ForceBreak(), workaround it to fix crash when loading https://football.kulichki.net/england/ (40afff632d) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 599328 - Clicking a label shouldn't draw a focus ring if clicking the control wouldn't have. r=enndeakin (fe391aecaa) - Bug 1221947 - part 1: add BYTOUCH flag to nsIFocusManager, r=jaws,smaug IGNORE IDL (41b191e6f1) - Bug 1192573 - Require tablet-mode (Win10+) to show the on-screen keyboard. r=masayuki (9244e1d044) - Bug 1197722 - Respect Win10 pref about bringing up the touch keyboard outside of tablet mode. r=masayuki (00e20db670) - Bug 1210033 - Add on-screen keyboard diagnostic information to about:support. r=masayuki r=felipe (0101168557) - Bug 1211805 - rework keyboard detection for on-screen keyboard, r=jaws (d6eee8e170) - Bug 1221947 - part 2: add TOUCH cause to IME Handling and use it to avoid checking for a keyboard, r=masayuki (b39ad48728) - Bug 1221947 - part 3: pass touch information to focus manager in RenderFrameParent, r=kats (84bbf77326) - Bug 1229258: Implement dummy asmMergeWith/retargetWithOffset functions in none backend; r=h4writer (cb7c19dbfa) - Bug 1210577. Remove useless virtual keyword from ScrollFrameHelper::ComputeScrollClip. r=mstange (5c40b8bd98) - Bug 1177505 - Make all continuations fluid within non-bidi paragraphs. r=smontagu (6d7956c20f) - Bug 1216096: restore previous RTL caret behaviour by backout of bug 1164963, bug 1177505, and bug 1180417. r=jfkthame (11d974c609) - Bug 1157752 - In vertical writing modes, text-orientation:upright should force LTR directionality. r=smontagu (b8843ce65e) - Bug 1002466 - Use SK_ScalarNearlyZero instead of 0.0f to render dots r=mattwoodrow (79406a8ce9) - Bug 1214309 - nudge zero dash intervals to be non-zero under Skia. r=jmuizelaar (b781a0c63a) - Bug 1208234: Stop the null pointer crash. r=bas (e7fb7f56ad) - Bug 1202317. Bail out early if RequestRect is going to do redundant work. r=mstange (cc85741516) - Bug 1167026 - Avoid division by zero when flattening a bezier curve segment with equal control points. r=bas (11e036081a) - Bug 1166879. Avoid uninitialized read in FlattenBezier. r=mstange (893177de38) (f3497a0291) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1193786 - crash in mozilla::dom::Element::FindAttrValueIn, r=marcoz (1f03b9594f) - bug 1172516 - fix firing caret move events for proxied accessibles r=lsocks (6a62915a27) - Bug 582024 - ARIA active-descendant should work for ARIA owned elements, r=yzen (4fc7049fe1) - Bug 1212457 - crash at ARIARowAccessible::GroupPosition(), r=marcoz (dd058e3dcd) - bit of 1139049 (ae765adc6a) - Bug 1221542, bug 1221543 - crash in mozilla::a11y::DocAccessible::SeizeChild/PutChildrenBack, r=davidb (8a35b14523) - Bug 1105611 - HyperTextAccessible should set DOM range outside of pseudo elements r=surkov (19e2cf65cd) - Bug 1177765 - Add xmlroles for MathML. r=surkov (381201ae27) - Bug 1176683 - crash in mozilla::a11y::HyperTextAccessible::LandmarkRole() const, r=marcoz (f3fd977d35) - Bug 1176123 - Add NODE_CHILD_OF/NODE_PARENT_OF relations to mroot. r=surkov (36f08faa15) - Bug 1179483 - Fix crash in mozilla::a11y::HyperTextAccessible::RelationByType. r=MarcoZ (fec7fde5b3) - Bug 1177765 - Make nsIMathMLFrame expose the fence and separator properties of operators. r=karlt (91e45d9980) - Bug 1139709. Cache nsMathMLContainerFrame's intrinsic width. r=mats (ac40d07d89) - code style (c5f50fc0c3) - Bug 1226875 - Remove nsIFrame::GetLastChild(). r=mats (9b88566b77) - pointer style (6a5b9599f4) - Bug 1177093 - mathfont.properties does not need to be preprocessed after Bug 1000745 r=fred.wang (d114e285a1) - Bug 1224951 - Part 2: Fix -Wunreachable-code warnings in layout. r=dholbert (5854ee5e3e) - Bug 1141443 - Remove unused rpcns4 from OS_LIBS. r=mshal (1a5ccc985b) - bug 1218762 - proxy ia2Accessible::scrollTo{,Point}() r=davidb (db1db8e703) - Bug 1182208 - Add support for android scrolling and range accessibility actions. r=mfinkle r=yzen (29df38ee29) - Bug 1144516 - Remove offset of mozbrowser iframe. r=yzen (c7473a8feb) - Bug 1176292 - Send 'toggle-shade' control event to content on 3 finger triple tap. r=yzen (536932619a) - Bug 1182222 - Make Layerview support accessibility HTML navigation. r=yzen r=mfinkle (2beb411989) - Bug 1203697 - Add braille navigation. r=yzen r=mfinkle (d5a513e79e) - Bug 1209054 - Make 2 finger tap toggle pause speech. r=yzen (28bc8c16a6) - Bug 1214398 - Add highlight box to doc body if it is available and set z-index. r=yzen (9cca205849) - Bug 1182214 - Update highlight rect as you scroll. r=yzen (6d2738366a) - Bug 1182214 - Follow-up to fix Presentation.displayedAccessibles getter. r=me CLOSED TREE (6dd8ec3652) - Bug 1212528 - ensuring first seen document in ancestry is announced first. r=marcoz (fb8e9bc406) - Bug 1217038 - Remove for-each and legacy array comprehension from accessible/. r=yzen (810590b5d3) - Bug 1220860 - fixing an error with getting documentElement on AccessFu stop. r=eeejay (4a35fabc3d) - Bug 1169019 - Removed screenreader announcement from gecko. r=yzen (2b1732cddc) - Bug 1211122 - ensuring that we check position against an actual doc/dialog on doc load event. r=marcoz (78b7cc8a77) - Bug 1019432 - [AccessFu] Only capture explore by touch events in Android. r=yzen (eee4b09c72) - Bug 1182311 - Make 3 finger triple tap more reliable. r=yzen (7cf926a839) - Bug 1201146 - Introduce "Section" traversal rule. r=yzen (253d53ec8d) - Bug 1203283 - Introduce Android "Control" traversal rule. r=yzen (4d14ffa973) (e0e84a7434) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1216851 - Allow flattening of opacity when it contains text. r=roc (f62dead4b9) - Bug 1219833 - Respect composition underline color; r=masayuki nsTextFrame didn't use the composition underline color if the composition didn't have a foreground color defined. This patch makes it use the underline color if foreground color is not defined. (02bcedf5fb) - Bug 1211085 - Disable global reuse on b2gdroid r=khuey (a4bfc7c4e1) - Bug 1206817 - Take ownership of error reporting in the component loader. r=bz (d8b9b02dfb) (40ee015dc8) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1172382 - Enable AccessibleCaret on B2G. r=roc (f5c58c2798) - remove duplicated (8823cc4a43) - Bug 1219310 - part 1 - ask the prefs file for its size directly; r=njn (93073cbc5e) - Bug 1219310 - part 2 - keep track of how much pref file we have read; r=njn (6a2a10a8b1) - Bug 1213123 - Make Preferences::SetString accept char16ptr_t instead of char16_t*. r=froydnj (a895a36861) - Bug 1216901 - Make the FasterMake backend reticulate splines when moz.build or jar.mn files are modified. r=mshal (ed4ec93b18) - Bug 1219122 - Move webapprt.ini definition to moz.build. - Add corresponding webpprt files. (da6bc91b5c) - Bug 1219126 - Move greprefs.js definition in moz.build. r=mshal (52f404c935) - code style (1b1e543834) - Bug 1162690 - Remove malformed uri warning in nsURLParser::ParseURL r=mcmanus (8534fcebb7) - Bug 1163028 - URL: stop escaping [ and ] in path r=mcmanus (f2f3deec40) - Bug 1163030 - URL: stop escaping ` in query r=mcmanus (17d6c07640) - Bug 1191423 - Disallow illegal characters in cookies set via HTTP. r=jduell (b1786d140f) - Bug 1210235 - Skip package verification if pref out or no signature. The package would be treated unsigned. r=valentin (63870dd7ef) - Bug 1216062 - Notify OnStartSignedPackagedRequest with package identifier. r=valentin. (81a14af3db) - Bug 1214079 - Doom the package cache if the signature verification failed. r=valentin (83824c2d5d) - Bug 1178448 - Use imported CA in developer mode. r=keeler,valentin (b9cf64b477) - Bug 1216469 - Bypass verification for signed packages from trust origins. r=valentin (a36d0a6d2f) - Bug 1218284 - Match signed packages' with trust origin without suffix. r=valentin (45529dc7df) - Bug 412457 - should unescape hostname first, then perform IDNA r=mcmanus (23ebe47574) - Bug 1217316 - Remove for-each from netwerk/. r=jduell (8d0ca69e9e) - Bug 1208847 - Add telemetry to measure how often secure cookies are set from non-secure origins r=mcmanus (57ecf3651d) - Bug 1165267 - Part 1: Replace appId and inBrowser by originAttributes v2. r=honzab (7710301407) - Bug 1165267 - Fix downgrading issue by restoring appId and inBrowserElement columns v3. r=honzab (3e8b8e4dfb) - Bug 1221049 - Use originAttributes from TabContext. r=kanru (5eaebe3b28) - Bug 1197944 - Change pref so that the http auth dialog is presented for sub resources as well. r=jduell (e3a7e2a1a7) - Bug 1202421 - Rename the network.auth.allow-subresource-auth pref. r=michal (87e29e1fdf) - Bug 1213577 - Use OriginAttributes in nsHttpAuthManager, r=mcmanus (33d0a25ac4) - Bug 961049 - Part 1: Remove unused members and methods; r=baku (0f3e6de06b) (33f0551ea5)
    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. There is a special tool to check a .NET Framework installation called .NET Framework Setup Verification Tool. Download it from the internet! The more recent tool is now called Microsoft .NET Framework Repair Tool. Here is its download page: https://www.microsoft.com/en-us/download/details.aspx?id=30135
    1 point
  28. Was having issues installing, but fixed it: EDIT: I had the order of the update packs wrong when I created the ISO... put them in the order you listed in your post and it installed fine... sorry noob here... (included all 5 + the Flash player optional update and it works great!!!) Thanks again!
    1 point
  29. 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
  30. OT ...Then, most probably, this one: https://www.youtube.com/watch?v=N2qqfafRdEQ /OT
    1 point
  31. @Rod Steel Here's the answer to your question from approximately 2 years ago:
    1 point
  32. Already aware. If you look at the releases discussed at MSFN, you will find that none of them contain this .dll. MULTIPLE .dll's have been removed during beta-stage telemetry-removal and testing. Several members contributed to that testing.
    1 point
  33. Somebody know how to fix this? It's just too wide
    1 point
  34. 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
  35. 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
  36. Doesnt work for me though, also win32 mentions an extended kernel thread, could you please link me to the whereabouts. Edit : i think i found it.
    1 point
  37. 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
  38. True, in fact a screenshot was posted in October 2020 thread about Among Us.
    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. It's sad to see legacy support dropped yet again for legacy hardware. Although I agree PC's older than 2005 are pretty slow, cutting them off will make it hard for those who can't afford new PCs...
    1 point
  41. No, those builds are only needed by computers that don’t even support SSE2, which is only a fraction of the remaining Windows XP diehards. I think browsers that support SSE2 will be around for a long time - they just won’t be based on the latest Chromium.
    1 point
  42. Yes, those discussions are mostly buried in the lengthy sticky thread about “last versions of software for [vanilla] Vista.” I don’t recall any issues being reported there either. Personally, I never used a version higher than 4.6.0 on Vista because I never especially wanted to run a program that required a higher .NET version. In fact I only have one program that needs 4.6, or else I might still use the 4.5.2 that Windows Update gave me before the apocalypse. But in these post-apocalyptic times, running software that officially requires Win7 is all the rage, and some such programs naturally need newer .NET versions. I wonder if the OP was trying to use a web installer, and wouldn’t be surprised if M$ has blocked those for Vista and XP by now. The OP started another thread on October 27, but hasn’t visited MSFN since then and may have given up on Vista.
    1 point
  43. What part of me says "I play Roblox"?
    1 point
  44. No , not even with the extended kernel.
    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. Some readers may not know what a broken record sounded like. In the days when music and other audio was sold on vinyl records, a crack or scratch often prevented the stylus (needle) from following the groove containing analog audio. In some cases the stylus skipped forward, but in a good many cases it skipped backward, causing the same passage to repeat over and over until someone intervened to break the cycle. I have seen many of your posts far and wide. Your preferred topic is always old Vista patches, but you seem to have an aversion to post-EOL patches (such as the one that was required to solve this thread), and you seem to believe that Firefox 52.9.0 is the only browser worthy of discussion. Your “broken record” analogy seems appropriate.
    1 point
  47. OT really, but Chrome required SSE2 long before that (see this 5-year-old post).
    1 point
  48. Right you are! Unfortunately, it's beginning to look like you are the only MSFN member running Vista or XP who is really concerned about Roblox support - or perhaps there is simply no solution.
    1 point
  49. ... And I'm so tired reading that same ol' mantra there: As if they (third party software developers) would give one nickel whether someone's setup is secure or not; what is the underlying truth inside this PR talk is that Microsoft themselves make it gradually impossible for third party software developers to target older OSes with their (M$'s) updated Windows SDKs! ... and it always comes down to that! Win7 will soon reach End of Extended Support, hence it'll also be "outdated and unsupported by Microsoft", with no more "security patches"; what is their stance on Win7? Security reasons my... behind!
    1 point
  50. it should be easy to start from chrome 51 as it already partially opens , also ive heard over many places that WMP 12 will work if you copy and replace it from Windows 7 7000 beta build , IE10 should be able to work although there seem to be artificial block or something which prevents it from loading , if you can figure it out , it would be a massive thing , i too love vista and have it till today dual booted with windows 7.
    1 point
×
×
  • Create New...