Jump to content

Leaderboard

Popular Content

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

  1. They fixed it in their code tree before you posted about it here. I don't know about that notification thingie causing high CPU usage, either it doesn't happen here (Pale Moon beta) or I'm missing something. https://support.microsoft.com/...No idea, but since I don't like messing with these things unless it's the last resort, I just added the rule to my Proxomitron to rewrite links to CSS in supported fashion... Name = "Microsoft Support - no stylesheet preload" Active = TRUE URL = "support.microsoft.com/ $TYPE(htm)" Limit = 256 Match = "<link rel="preload" as="style" onload="this.rel=\'stylesheet\'" \0>" Replace = "<link rel="stylesheet" \0>" Just did it the way I know it can be done... Palefill as provided on martok's GitHub page will indeed still impact GitHub in a significant way even when Web Components are provided by the browser because some checks aren't there so some stuff still gets injected unconditionally, but even when certain injected code has checks to not do anything if not necessary, I suppose its code must still be parsed by the browser. I use modified version that more thoroughly checks browser features and prevents processing rules that polyfill functions that already exist in the browser. But if one must toggle web components between on and off, changes take effect after disabling/enabling extension in the new browser window, which you must open beforehand, or restart the browser. palefill-1.25.4.xpi
    4 points
  2. Hi all! I'm Frances Walsh from the city of Austin. I am a girl who loves working with computers and technology, so I joined this community. I am here to share my knowledge and learn something new from other members. I'm hoping for interesting people and introductions with an individual passion for technology. I would be happy if anyone would like to chat with me or share their experiences !
    2 points
  3. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230318-3219d2d-uxp-85f6a4929-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230318-3219d2d-uxp-85f6a4929-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-20230318-3219d2d-uxp-85f6a4929-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-20230318-d849524bd-uxp-85f6a4929-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230318-d849524bd-uxp-85f6a4929-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230318-d849524bd-uxp-85f6a4929-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230318-d849524bd-uxp-85f6a4929-xpmod.7z Official UXP changes picked since my last build: - Issue #2135 - Follow-up: Check for aElement not being null (2249fbdf4) - Issue #2137 - Part 1: Modify :not() selector to accept a complex selector list (82fa9fb80) - Issue #2137 - Part 2: Implement SelectorParsingFlags and use it to pass info around (3bb3c193d) - Issue #2137 - Part 3: Don't always use the internal pseudo-class for handling negations (b257a71cc) - Issue #2137 - Part 4: Fix namespace regression (ef36c5659) - Issue #2135 - Destroy the host frame and restyle when there are content changes (18e693464) - Issue #2078 - Follow-up: Ensure empty selector lists aren't iterated when serialized (2be0261d5) - Issue #2046 - Follow-up: Fix deprot in RelativeTimeFormat. (77b618055) - Issue #80 - Fix deprot in js/ipc. (261dc37ad) - Issue #80 - Fix deprot in js/xpconnect. (0b039ff7a) - Issue #80 - Move implementation of CPOWTimer::CPOWTimer to header. (c2c95eff9) - No issue - Make content-type on JAR channels behave the same as HTTP channels (091a2aab8) - Issue #2046 - Follow-up: Fix deprot in builtin/intl (a2d6260cd) - Issue #2160 - Initial support for notarizing during DMG package. Added --with-macbundle-idenity configure option to set a codesign identity. If no identity is set or cross-compiling from Linux no codesigning will be done. Currently doing a full deep bundle v2 sign, instead of limited v1. (3d2a4f406) - Issue #2148 - Don't null out RegExpObject -> RegExpShared pointer on GC. (ad8d9639a) - Issue #2148 - Discard RegExpShared data tables when discarding regexp JIT code. (cdd91edd7) - Issue #2148 - Make Vector not use AlignedStorage for its inline element storage (0365f940f) - Issue #2148 - Shrink Vector from (usually) four pointers in size to three when no inline storage is used. (481069044) No official Pale-Moon changes picked since my last build. Official Basilisk changes picked since my last build: - [Basilisk] Add useragent override for instagram port of MoonchildProductions/Pale-Moon commit d641959f15cb1172f6f39130b579ccf6111a6f2f and 6d41a6139440a9c396308deca1725b0db823e127 (76cd3dfac) - [Basilisk] Port Pale Moon version of Tab fading Backport of roytam1/UXP commit https://github.com/roytam1/UXP/commit/2a32b18f465a8d068d1b1866d027374b4706cd5a.patch (4abf53728) - [Basilisk] add tab caption fading to CtrlTab backport of roytam1/UXP commit add tab caption fading to CtrlTab (78bb7159e) My changes since my last build: - Reverting rev b7e45308 and 9824659d again as I can still get a crash in `RegExpShared::finalize(FreeOp* fop)` (bb547a1b5) - Revert "Reverting rev b7e45308 and 9824659d again as I can still get a crash in `RegExpShared::finalize(FreeOp* fop)`" (0bfc6e378) 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.
    2 points
  4. Hi @FrancesWalsh, hello from Belgium and welcome to MSFN! I wish you to enjoy the forums! Have a nice day. hpwamr
    2 points
  5. Notice: ( especially @adata and others ) Please don't report bug(s) of my browsers using forum's Message function (to me) unless you're providing login credentials for reproducing the bug, or your report(s) will be ignored.
    2 points
  6. 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
  7. Hi, i've dowloaded a Windows 11 Enterprise ISO called LTSC what the difference with Windows 11 Enterprise IoT? Thank you
    1 point
  8. New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.4.7-Goanna-20230318.7z Changelog: Out-of-tree changes: * update Goanna3 to git 33f0551ea5...393bc6639f: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1168263 - Exclude perspective transforms from the transform used to convert from screen coordinates to an APZC's coordinate space. r=kats (dab02eb359) - Bug 1225950 - Remove unnecessary parameter from SetNeedsComposite. r=mchang (0fb6099bd5) - Bug 1225950 - Make mNeedsComposite a counter rather than a boolean. r=mchang (4d46dba314) - Bug 1225950 - Force a composite if we have requested one but haven't gotten a vsync in a while. r=mchang (06f0d4553e) - Bug 1221697 - Add a telemetry probe for time-to-composite. r=kats (c333e2ea87) - Bug 1213120 - Ensure we don't try to use an uninitialized map. r=BenWa (99069b78fe) - Bug 1228133 - Guard against a race condition that could result in an illegal pointer access. r=BenWa (65e1393908) - update, mostly shadow warnings (5ca9c8ec0c) - Bug 1119106 - Increase the radio button rendering bottom margin on 10.10 so that the button hits its frame more accurately. r=smichaud (2b55533095) - Bug 1221451: Don't pass nil when an argument is required. r=spohl (7adfcf2543) - Bug 1153579 - Fix -Wpointer-bool-conversion warning by removing null check of an array address. r=mstange (8c7ad82e8f) - Bug 1204620 - Don't prepend 'image.' to CUIDraw image names on 10.11. r=stefanh (9a4794ecd4) - Bug 1181289 - Specify size: small when drawing small scrollbars with CoreUI. r=smichaud (e75bff6036) - Bug 1138359 - Make the margins of native-themed Cocoa buttons aware of writing mode. r=smontagu (49afef0f00) - Bug 1220358 - Fix -Wunreachable-code warnings in widget/cocoa. r=spohl (720c720afc) - fixup widget/ios from EventMessage change (no bug, NPOTB) (ab33d61f95) - Bug 1217818 - Add support for the mHandledByAPZ flag on touch events as well. r=botond (d4658c671a) - Bug 1209772 - 'mozregression was installed. please re-run your command.' when running ./mach mozregression. r=ahal (5febef290b) - Bug 1204787 - Add |mach power|. r=glandium. (5a0d84f480) - Bug 1214924 - Add "WindowServer" and "kernel" processes to |mach power|'s output. r=BenWa. (89c3a515f7) - Bug 1197694 - fflush() rapl output so it always appears immediately. r=erahm. (052568f395) - Bug 1194560 (follow-up) - Only build rapl on Linux if the arch is x86 or x86-64. r=glandium. (0101937ffa) - Bug 1198137 - Add some summary stats to tool/power/rapl's output. r=erahm. (53052f366b) - Bug 1198137 (follow-up) - Add a missing #include to unbreak Mac OS builds on a CLOSED TREE. r=me (27862d34ff) - Bug 1203834 - Fix's rapl's handling of unsupported power domains. r=glandium. (facb022467) - Bug 1203811 - Clarify two error messages in tools/power/rapl. r=heycam. (07a6bb847e) - Bug 1201811 (part 1) - Don't use integer arithmetic when summing totals in rapl. r=erahm. (57a1de1376) - Bug 1201811 (part 2) - Don't print distribution stats if there was only 1 sample. r=erahm. (e5c085a4df) - Bug 1222887 - Suppress -Wunreachable-code warning in tools/power. r=njn (4fbbbe81e1) - Bug 1222352 - Resource Timing - nextHopProtocol does not work in e10s r=nwgh (57029cf33d) - Bug 1211636 - use ToInteger64 in PopulateFromSuffix. r=bholley (d67e5fe9d1) - Bug 961049 - Part 2: Remove Utilities.h; r=baku (3c09679a40) - Bug 961049 - Part 3: Move PersistenceType serializer from indexedDB to quota module; r=baku (021478905a) - Bug 1186809 (part 1) - Replace nsBaseHashtable::EnumerateRead() calls in dom/quota/ with iterators. r=janv. (8933726851) - Bug 1186809 (part 2) - Replace nsBaseHashtable::EnumerateRead() calls in dom/quota/ with iterators. r=janv. (cb7c6f27dc) - Bug 1186809 (part 3) - Replace nsBaseHashtable::EnumerateRead() calls in dom/quota/ with iterators. r=janv. (1ded98347c) - Bug 1187151 (part 1) - Replace nsBaseHashtable::Enumerate() calls in dom/base/ with iterators. r=khuey. (a409e8590e) - Bug 1187151 (part 2) - Replace nsBaseHashtable::Enumerate() calls in dom/base/ with iterators. r=janv. (bd4fe93dfc) - Bug 1187151 (part 3) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (de0f2dda26) - Bug 1187151 (part 4) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (e72d744118) - Bug 1187151 (part 5) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (18eddd5225) - Bug 1187151 (part 6) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (36fb6272e1) - Bug 1187151 (part 7) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (594438d35f) - Bug 1187151 (part 8) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (d8de2742d8) - Bug 1187151 (part 9) - Replace nsBaseHashtable::Enumerate() calls in dom/ with iterators. r=khuey. (d2b4a29111) - missing namespace (0b0453cc40) - Bug 1187701 - add_task function for mochitest chrome and plain; r=jmaher (1c31a40c7c) - Bug 1223831 - SpecialPowers API to create files in an e10s-compatible way. r=jmaher,baku (a04646cb50) - Bug 1178526 - Create docshell with packageId from TabContext. r=sicking. (c89edfc7ab) - Bug 1217694 - Signed package should come from the moz-package-origin specified in its manifest. r=valentin (705aeae07a) - Bug 1225422 - Update the PrivilegedPackageRoot certificate. r=keeler (2a90eed63c) - Bug 1204301 - HttpChannelParent needs to be able to GetInterface to an nsIPrompt. r=billm. (4937a2fbbe) (f7d677cddd) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1209162 - Create OriginAttributes subtypes. IGNORE IDL r=sicking. (c2cbe04ef3) - Bug 1220570 - Potential cookie lost while downgrading from Aurora 44 to 43. r=jduell (1a0111c842) - Bug 1217456: Add a security flag for controlling redirects. Use this flag in fetch() implementation. r=bkelly,jduell (79d449e479) - Bug 1112040 - Add a mochitest. r=bholley (566a05f720) - Bug 1171215 - Compute third-partyness in the loadinfo instead of nsIHttpChannelInternal so that other protocols correctly respect the third-party cookie pref. r=sicking/ckerschb (06f7a10a83) - better backport of Bug 485941 - Stack overflow using overly-deep XML tree (DoS). r=bzbarsky (ac43feeffa) - Bug 1182546 - Use channel->Open2() in parser/htmlparser/nsExpatDriver.cpp (r=bz) (42768f373a) - Bug 1163435 part 1 - [css-grid][css-flexbox] Propagate an explicit CB width/height to the reflow state to resolve percentage lengths for grid items properly. Resolve percent against the size in the same axis for abs.pos. children too. r=dholbert (a55463fb05) - Bug 1163435 part 2 - tests. (bb683c5fc6) - Bug 1223282 - Make NS_AUTOMARGIN be a different value than NS_UNCONSTRAINEDSIZE to avoid having clamped huge margin values be interpreted as auto margins. r=roc (4cdfe0f277) - Bug 1224230 - Explicitly store the lineContainer's writing mode in InlineIntrinsicISizeData. r=dbaron (6474515223) - Bug 1221043. Revert to including trailing whitespace for accessibility APIs. r=marcoz,mats (406018c163) - Bug 1227113 - Fix some indentation issues in ServiceWorkerManager, r=janv (2b343bde09) - Bug 1223116 P1 Expose nsIServiceWorkerManager.shouldReportToWindow(). r=catalinb (02899e429d) - Bug 1226441 - Part 1: Add wpt test verifying fetch event waits for activate to complete; r=catalinb (e8eb3e6e7a) - Bug 1209865 - Add gecko profiler marker when mark() of User Timing API is called. r=baku (f48d76e395) - Bug 1169068 - Performance.translateTime(), r=bz (38cd1c31b2) - Bug 1226441 - Part 2: Delay functional event dispatch until service worker is activated; r=catalinb (778cd3dd24) - Bug 1178233 - [non-e10s] The update process doesn't work within about:serviceworkers in non-e10s mode. Test. r=baku (4f8b6f53f8) - Bug 1188545 - Disable unstable test: test_aboutserviceworkers.html. a=testonly (4bbe106693) - Bug 1219255 - We should be able to attach to a service worker;r=amarchesini (0d6b71b4ec) - Bug 1222464 - Part 2: Implement FetchEvent.clientId; r=jdm (9c8abd62dd) - Bug 1218150 - Mark the members of Clients as NewObject; r=bzbarsky (b6b00a586c) - Bug 1222464 - Part 3: Implement Clients.get(); r=jdm (f5ca60d801) - Bug 1222464 - Part 1: Save a client ID for top-level navigations on the docshell and assign it as the document ID when we start loading the document; r=jdm (7dcb5ce2b6) - Bug 1218141 - Add some SameObject and NewObject annotations to ServiceWorkerGlobalScope; r=bzbarsky (5019f58c7a) - Bug 1218190 - Add a pref to enable Clients.openWindow, r=catalinb (dbb6d007dd) - Bug 1218142 - Remove ServiceWorkerGlobalScope.onbeforeevicted/onevicted; r=bzbarsky (029de6f8ec) - Bug 1218146 - Move WindowClient.frameType to Client.frameType; r=bzbarsky (00f0211276) - Bug 1218147 - Make WindowClient.focus() NewObject; r=bzbarsky (3c6aea4b67) - Bug 1189659 - Part 1 - Continue service worker job queue when life cycle events expire. r=bkelly (aa09cd9c60) - Bug 1227932 - Fix Service Workers SoftUpdate and registration.update code paths. r=ehsan (24567b23c0) - Bug 1189659 - Part 2 - Remove set of scopes being updated from ServiceWorkerManager. r=bkelly (ce581b095c) - Bug 1189659 - Part 3 - Use separate synchronization queues for service worker register jobs and install jobs. r=bkelly (9c408a22ed) - Bug 1189659 - Part 4 - Fix race in test_install_event.html. r=bkelly (3186ffb808) - Bug 1189659 - Part 5 - Fix race in skip-waiting.https.html and add some logging for SkipWaitingFlag in ServiceWorkerManager. r=ehsan (4e5ddda6f3) - Bug 1229056 - Implement ClientQueryOptions.includeUncontrolled; r=jdm (dbe56aa60d) - namespace (3b0863d42d) - Bug 1201127 - Return the same ServiceWorkerRegistration object from service worker APIs dealing with the same underlying registration object; r=jdm (c542688ae0) - Bug 1171583 - Remove mutable warning from |nsSimpleURI::SetUserPass|. r=bz (73934deaad) - Bug 1206199 - Extend channelwrapper to mediate OnStartRequest, OnStopRequest, OnDataAvailable (r=sicking) (758a7ec65c) - Bug 1186783 (part 4) - Replace nsBaseHashtable::EnumerateRead() calls in netwerk/ with iterators. r=valentin. (681bdba278) - Bug 1186783 (part 3) - Replace nsBaseHashtable::EnumerateRead() calls in netwerk/ with iterators. r=valentin. (76b8b7191e) - Bug 1186783 (part 2) - Replace nsBaseHashtable::EnumerateRead() calls in netwerk/ with iterators. r=valentin. (5c0743ac49) - Bug 1186783 (part 1) - Replace nsBaseHashtable::EnumerateRead() calls in netwerk/ with iterators. r=valentin. (952cc720cc) - Bug 1186783 (part 5) - Replace nsBaseHashtable::EnumerateRead() calls in netwerk/ with iterators. r=valentin. (25b9735c52) - Bug 1186783 (part 1) - Replace nsBaseHashtable::EnumerateRead() calls in netwerk/. r=michal. (ae52425809) - Bug 1186783 (follow-up) - Bustage fix for Gonk. (d4a1b769bd) - add back some hotfix stuff, even if unused (fe32076c5b) - Bug 1068087: Switch about:plugins to run remotely. r=mconley (bc4316dd03) - Bug 1214058: Part 1 - Add a simplified JSON-based add-on update protocol. r=Mossop (a3198884d5) - Bug 1214058: Part 2 - Run add-on update tests against comparable JSON and RDF manifests. r=Mossop (aa6a796e6f) - Bug 1152977 - Enable by default DEAA for desktop platforms that use OpenGL compositor. r=jmuizelaar (bfa9efd5c8) (393bc6639f) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76
    1 point
  9. ... And his "Notice" writes: https://github.com/abbodi1406/vcredist#windows-vista-notice ... And he's actually right; the last standalone file "VC_redist.x86.exe" provided by MS that will install out-of-the-box on Vista SP2 32-bit is of version 14.31.30919.0: https://download.visualstudio.microsoft.com/download/pr/8c1c2dbb-0856-4dc3-b863-b16c637bc245/E55681B9E07A58F7143E5AB5941F45DE0B485E0C9933B0CB6B702D3921F48527/VC_redist.x86.exe Subsequent versions 14.31.31005.0, 14.31.31103.0, 14.32.31302.0, 14.32.31326.0 and 14.32.31332.0 had their installers blocked from launching under Vista SP2, but their "payload"/content (various DLLs) continued to remain Vista-compatible ; next version 14.34.31823.3 had several of its DLLs contain Win7+ function calls ... So, the last of abbodi1406's vcredist AIO custom pack with full/proper Vista SP2 support is v0.6.1 (2022-06-21): https://github.com/abbodi1406/vcredist/releases/download/v0.61.0/VisualCppRedist_AIO_x86_x64_61.zip What point would there be in doing so ? Its VS2022 DLLs are incompatible with Vista and, if force-installed, would fully break all apps requiring the VS2015-2022 runtime ...
    1 point
  10. Hello @FrancesWalsh, welcome to the forum!
    1 point
  11. Sad to see that it isn't up anymore. I actually used some good info from there when I started searching these browsers. Forgive my ignorance but, what does OP mean? Cheers. EDIT: I think it is Original Post after thinking for a bit.
    1 point
  12. welcome to the forum @FrancesWalshits good to see another fellow texan on here (I'm from near dallas)
    1 point
  13. Any drivers designed for Windows 7 or higher can be backported to Vista using NTOSKRNL Emu_Extender. For the user-mode components, use Extended Kernel version spoofing.
    1 point
  14. ... Can confirm ; the page does load, but clicking any of the download options (buttons) doesn't initiate a download ; it's JS related: What's worse, I couldn't get a download to happen with any of 360EEv12/13/13.5 and KafanMiniBrowser, so I'm not able to fetch the Edge files under this Vista SP2 x86 laptop; any working workaround will be appreciated ...
    1 point
  15. Thanks for the list. With software of that kind, combined with an older OS, and particular use cases, versions matter a lot. As for HqMame. I noticed some other versions gave stuttering audio on a Sandy bridge laptop. And from 2012 to 2016 executable size grew from 60MB to a whopping 120 MB.
    1 point
  16. 1 point
  17. Edge browser download page: https://www.microsoft.com/en-us/edge/download?form=MA13FJ do not work in Serpent 52
    1 point
  18. Nice findings! I recall 0.147 was (and is) quite a good version. Just about all the essential stuff was supported by then, with great accuracy and performance. I don't want to go too far off-track here, but to quickly sum it up, a few important versions of MAME for anyone who wants to tinker: -0.37b15 and 0.37b16 (the first releases with DirectDraw bilinear filtering and hardware stretching, last of the 0.37bX line) -0.57 (the first release with fixed protection for WWF WrestleMania and the first to include Revolution X, good for Midway fans) -0.61 (the last release tested on consumer-grade hardware of the time [2002] where it was confirmed that every game ran at full speed at maxed-out settings. Starting with 0.62 you now needed a processor far, FAR beyond anything on the market at the time to run all games at full speed) (I have a personal 'eight years' theory that starting with 0.62, you need a PC roughly 8 years newer than the MAME release itself to be able to run all games at full speed. So if your PC was manufactured in 2010, you're good to go with 0.62; if mfgd in 2014, you can run all games in MAME 0.106 [2006] at full speed.) -0.67 was the last release where the original coordinator (Nicola Salmoria) was still overseeing the project; starting with 0.68 those responsibilities shifted to a young David "Haze" Haywood. This is very important because under Haze's 'regime' there were various changes made that sent MAME on the course it's on today, including the removal of a lot of hacks that made it possible for most games to run well on modest hardware. This is a great version to use if you're on an older PC, such as a PIII or an early P4. Other notable versions, summed up a bit more succinctly: -0.69 (easy to find ROMs for, has some bugs from 0.68 fixed and runs well on 'trash picked' PCs) -0.72 (last release with DCS Sound System hacks that allowed 90s Midway games to run at full speed on weaker hardware) -0.78 (easy to find ROMS for, support was added for a few more cool games, some emulation improvements made with others) -0.84 (easy to find ROMs for, has more games supported and a few more emulation improvements, still runs well on older PCs) -0.92 (last version before the sound engine was rewritten) -0.106 (a very famous version that is still often referenced, and the last true 'classic' MAME before the video engine was rewritten) -0.139 (easy to find ROMs for; this was also one of the last versions before the MAME devs began adding mechanical games) -0.160 (easy to find ROMs for; by this point Raiden II/DX were now working, and other games had some emulation issues resolved; notably this is also the first version with OpenGL support, which improves performance for certain games) If I had to recommend one MAME version, JUST one, to stick with and not change, it would be a toss up between 0.106 and 0.160 (yes, swapping two numbers). 0.106 is a reliable old version that will run on pretty much anything you find laying out in the street, but you need a PC made in the last decade or so to be able to play all of the games at full speed. By comparison 0.160 needs far beefier hardware to run well, but all of the simple 68K and Z80 stuff should run fine on it, and by that point a lot of the loose ends had been sorted out for the games that matter. I honestly don't think anything of true significance has been added since 0.160. (However, a lot of emulation improvements have been made for games that 0.160 supports, so that balances things out a bit.) It's not to diss the hard work of the devs because I am impressed with how far MAME has come. But it's also a long ways removed from the lightweight, intuitive, fast emulator it used to be. It puts me in a quandary because on the one hand I do like to have a certain level of accuracy, but if you go too far in that direction you sacrifice speed. 0.106 & 0.160 are good balances in that sense. And that concludes my off-topic MAME 'rant'...I'll try to keep it on-topic from here on out.
    1 point
  19. Six months ago I was curious about some old arcade games. Which, as usual, got me tinkering with software without playing much I found it preferable to use the HqMAME fork, because it can smoothen the pixelation out nicely, and it does it internally to the sprites or layers for better effect. This one: HqMAME v2.2 based on MAME v0.147u3, dated 11-12-2012. Modded with HqMAME v2.16 scaler dlls, which seem to work fine. On Windows XP SP3 x86 that is.
    1 point
  20. Thank you for sharing those articles, UCyborg--I can definitely relate. It took a lot of consideration, but I decided to migrate back to Windows 10 LTSC, but went for 2021 instead of 2019. I've said before you pretty much can't go wrong with any of the LTSB/LTSC versions, but it seems that the newer releases offer various improvements, small but quite meaningful in some cases, over the earlier ones. (And a big benefit you get with using any version of 10 is being able to use modern browsers...the latest Chromium runs great.) For what it's worth LTSC 2021 does seem to have a few bug fixes compared to 2019, but both are excellent, the bugs are nowhere near significant, and LTSB/LTSC in general, again, comes highly recommended for anyone who wants to bite the bullet and ride the '10 express'. It's really up to your preference: the older ones will play nicer with older hardware and the newer ones may work better with newer PCs. For my part I'm still using my trusty old HP S5-1020, and when properly tweaked (there's no exact science, and in my cases it's taken a ton of trial and error) it pretty much runs as well as you could hope for it to on something that's now over a decade old. Actually, the performance is competitive with 7 and 8.x...it still falls slightly short, but not nearly as badly as it would if left untweaked. I've learned more about 10, and it seems to be the absolute best option going forward for old and new PCs. Turns out Win11 went the x64 or bust route so 10 is the final version of Windows that supports 32-bit processors, and also appears to be the last that retains a good amount of legacy NT code; it appears that much of it has been rewritten or removed in 11 already, and I predict MS will stay on this path going forward. So if you're running legacy hardware & software, Win10 may be your final refuge before a Linux leap. (I'm not opposed to that in the future, having experimented with Linux before, but to me that's the last resort.) To sum it up I still rank XP as the greatest OS Microsoft ever made. 7 comes in second, and 10 LTSB/LTSC takes a respectable third. Vista and 8.x are fantastic despite the bad reputations they unfairly gained, but honestly neither is a big leap over its predecessor. (They did introduce some nice innovations that their follow-ups improved upon, though.) If you're willing, I would give 10 a try. It's gotten a lot better with time and I believe it will be remembered as a great OS when the plug is inevitably pulled, many years from now. Just as XP and 7 ascended to the pantheon of the great OSes after early struggles, I believe 10 will also get there one day. (Depending on who you ask, it might even be there now.)
    1 point
  21. We should not forget that there is a further tool for updating Root Certificates in Windows XP. The creator was @Thomas S.. The tool is called CAupdater. Here is the link to its original post: It is also embedded in his HTTPSProxy package. In his original post, the download link of CAupdater as a single archive doesn't work anymore. BTW, both versions of my self-created Root Certificate and Revoked Certificate Updater are meant to be used in case no internet connection is available. Generally, @heinoganda's Certificate Updater 1.6 or @Thomas S.'s CAupdater is completely sufficient. All facts about Root Certificates can be read in the section 5.2 of my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use". Greetings, AstroSkipper
    1 point
  22. True, but not in the sense discussed here; in 360EEv11, navigate to "chrome://settings/advanced", then scroll further down to "HTTPS/SSL": If you press the top first button (Manage certificates...), you are presented with an OS window: a clear indication it's using the OS cert store... Now, if you click the third bottom button (with Chinese characters), you do get access to its built-in cert store, but that is only meant to be used within China, for mainly Chinese sites: What's more, the user has no edit access whatsoever to that cert store, i.e. expired certs can't be deleted, nor new ones be imported... FYI, all variants of 360EE (v11/12/13/13/5) have the same cert stores structure (access to the MS cert store + QiHoo provided one); more info about the QiHoo/360 cert store can be found at below link: https://caprogram.360.cn/#plan (in the header, select "English") Regards.
    1 point
  23. My primary browsers in Windows XP are New Moon 28 and Serpent 52/55. I use 360Chrome 13.5 only for testing purpose in my Windows XP installation. It is great to have alternatives but I prefer UXP browsers under Windows XP. I am also an Android user, and there you have a pure Chrome/Chromium world offering the most recent browsers. Or I use Windows 7/10 to surf the internet with the more/most recent Chromium browsers. But no need to do that in my beloved Windows XP system, and 360Chrome 13.5 is not recent anymore, either. When starting my Windows XP system, I dive into another world and enjoy the recreation of all this Chrome/Chromium stuff. All Chromium browsers are extremely restricted, especially in terms of extensions, custom buttons, customizations and modifications. That's one of the reasons I love and prefer my UXP browsers New Moon and Serpent. And to have them at all, I am very thankful to our creator @roytam1! Welcome back and of course, a good decision! Cheers, AstroSkipper
    1 point
  24. ... For starters, you shouldn't do that (when testing), as palefill conflicts/interferes with native WC: https://forum.palemoon.org/viewtopic.php?p=237202#p237202 From Moonchild himself: Second, I have always been talking about Serpent 52 (actually, its previous version of 2023-03-02); but just to humour you and be on the same ground as you, I did launch a quasi-fresh profile of latest NM28 [v28.10.6a1 (32-bit) (2023-03-10)], where I installed and enabled palefill-v1.26 and then restarted it, for good measure... My GitHub testing repo this time is https://github.com/violentmonkey/violentmonkey/commits/master At first load, the relative timestamps do appear (in the "hours" range) - this is now with both palefill+native WC enabled, as you suggested; now try and continuously soft reload that page (by clicking the "reload current page" toolbar button); soon enough you'll get (I did, on my 5th attempt ) the missing timestamps bug: If, like me, you spend hours inside GitHub, then you "can't miss it"; this bug exists, as I've tried in fresh profiles (mainly St52, but lately NM28, too) and combinations of: a) native WC+SR enabled, palefill disabled (recommended by Moonchild) b) native WC+SR enabled, palefill enabled c) either of the two above, being c1) logged-in to GH or c2) logged out from GH The only combination (for me) where the relative GH timestamps remain permanently fixed is d) native WC+SR disabled, palefill enabled FWIW, with the above combination, the (latest) NM28 with fresh profile used to generate above screengrab consumes virtually 0 CPU when being minimised here: Conclusion: Everyone's setup may behave slightly differently, in a stochastic fashion , and this makes troubleshooting and fixing bugs quite a daunting task on the part of the devs ... Best regards.
    1 point
  25. 1 point
  26. The Office Update website should be released, but there are still bugs.
    1 point
  27. Note regarding versions: The regular version will have a file name ending in _rebuild_#. Versions with a file name ending in _ungoogled disables embedded Google APIs in much the same way that "ungoogled-chromium" ( https://chromium.woolyss.com/ ) disables embedded Google APIs. The "ungoogled" version is recommended for those that prefer tighter control over a Google-based browser basically giving special treatment to Google cookies and violating user preference settings. A side effect to this approach (which also exists in "ungoogled-chromium") is that the Chrome Web Store is intentionally broken only in as far as the "Add to Chrome" button is concerned. This is great for those that prefer to manually install extensions as opposed to obtaining from the Chrome Web Store. A workaround to restore the "Add to" button (special thanks to @VistaLover for this solution) can be obtained from here -- https://github.com/NeverDecaf/chromium-web-store Mileage may vary, for me this only added the "Add to" button but clicking it only downloaded the extensions .crx (which I personally prefer anyway) as opposed to 'adding to' 360Chrome. I had similar results with official "ungoogled-chromium" on the official Chrome Web Store (restores "Add to" button but does not actually 'add to'). Special thanks to @Humming Owl for translated .png files. Special thanks to @Dixel for discussions leading towards the "ungoogled" versions. XP x86 SP2: v12, v13, and v13.5 work as-is in XP x86 SP2 but v11 requires special modifications - see this post by @we3fan Download links for starting from scratch with a NEW PROFILE: Regular: https://www.dropbox.com/s/mes4wez1v34w9k4/360ChromePortable_11.0.2031_rebuild_8.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/wol8va166au2p7j/360ChromePortable_12.0.1247_rebuild_12.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/6lnst7yp0dt34s5/360ChromePortable_13.0.2206_rebuild_9.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/8h4z346251wg7r8/360ChromePortable_13.5.1030_rebuild_6.zip?dl=1 (last updated: Jan 11, 2022) Ungoogled: https://www.dropbox.com/s/6z65t5yo08fr0ym/360ChromePortable_11.0.2031_rebuild_8_ungoogled.zip?dl=1 (last updated: Jan 9, 2022) https://www.dropbox.com/s/j5zxk7aqv9ljjjc/360ChromePortable_12.0.1247_rebuild_12_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/ld5dz2uwdowf1cz/360ChromePortable_13.0.2206_rebuild_9_ungoogled.zip?dl=1 (last updated: Jan 11, 2022) https://www.dropbox.com/s/glulv6r8sce6xpy/360ChromePortable_13.5.1030_rebuild_6_ungoogled.zip?dl=1 (last updated: Jan 11, 2022)
    1 point
  28. I work in an Engineering office with 60 other Engineers (two of them are IT but they are lumped in with Engineering Department). My computer "brightness" is not any different than any of theirs, both by "my eyes" and by "their eyes". It is the "vampires" eyesight that I worry about - I'm 20/20 and "healthy as a horse". My only doctor that disagrees is my Dentist - but that's a Mountain Dew issue I guess my BIGGEST thing is this - I have HUNDREDS of software packages installed on this system. It's an EYESORE for ONE of these software packages to be "dark" and the other HUNDREDS MINUS ONE to be of a "universal color scheme". I guess, to ME, it's also this - when I buy a book or newspaper, there is no such thing as a "dark theme". You get black text on white paper - period. I do have a "theory" but it's also admittedly just an off-the-cuff theory with no research behind it. My theory is this, that 'gamers' are huge into "dark themes" but those of us that read to read (anything from Aristophanes to MSFN) are fine and dandy with "black text on white paper". However, I do acknowledge that one of our IT guys does use a task-specific software package where all of his text is red, maroon, cyan, blue, yellow, green, purple, and white all on a dark gray almost-but-not-quite black background. But his WEB BROWSER is still black text on white background. I would hate to have his job and have to constantly toggle back and forth between the two. So for him, "I get it". But also for him, he never once has ever complained that his web browser, his AutoCad, his Microsoft Office, his dozens of other software programs, he's hever once complained that they don't have a "dark theme". Oh well... Carry on, fanboys
    1 point
  29. Question -- for you "vampires" <chuckles> that prefer a "dark theme", does the dark theme effect only the GUI or does it also effect web pages that you visit?
    1 point
×
×
  • Create New...