Leaderboard
Popular Content
Showing content with the highest reputation on 03/12/2023 in Posts
-
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=13 points
-
A rather funny Serpent 52.9 crash just happened - I was watching youtube for some time and then HWunBoxed video RTX4070Ti against RX7900XT and the message about basilisk encountering error popped up. The video was still going for a while and then stopped and if I dragged the error window all over the screen (which I did) resulted it this lovely picture (attached). When I "click(ed) here" it said it has to do with mozglue.dll or something similar. BTW thank you for the new release, roytam1, starting from last week's each now is much more up to date and faster working than ever before. After a Serpent restart it works normally again.3 points
-
Unless he has a good GPU. In such a case, the heavy lifting is shifted to the GPU, and not the CPU. I was using Vista x64 Ultimate on an HP xw8200 (a dual Xeon system, based on Netburst P4), I had 7 GB of DDR2 RAM in it, and my PCI-e slot was knackered, so I put in a nicely accelerated PCI dadapter. Aero sang sweetly on that, and I had no issues with Vista. This was especcailly the case with SP2 built in and the Platform update. On an XP-era computer? Sure disabe Aero.3 points
-
this is an old problem since feb uncovered by https://github.com/roytam1/UXP/commit/9824659d3c6b1c4fdc2616f789f0696d1cbe2ef8 and https://github.com/roytam1/UXP/commit/b7e4530861fcc971aee9d867b3b376e31263486c and they said it is fixed by https://github.com/roytam1/UXP/commit/1f0df8f421626bcbc397512773f3043d72d96a4f but I still need to revert first 2 mentioned commits in order to make it not crashing.2 points
-
Pull-quote from another thread about a different site with this problem (https://forum.palemoon.org/viewtopic.php?f=70&t=26061&p=207349#p207323): Emphasis added. And further down the page: So it looks like Google gets the blame after all. They gave sites a needlessly complicated way to do something simple for no benefit (unless they consider breaking older Firefox-based browsers a "benefit")2 points
-
I should be able to do this one of these weekends.2 points
-
He's a troubled fella, sometimes he seems to change OS multiple times a day. Don't expect it to last.2 points
-
Doh! Didn't even dawn on me, thanks for the clarification.2 points
-
The (partial?) answer is on Pale Moon forum - UXP doesn't support <link rel="preload" ...>. Unsure if above is related to current work-in-progress on Web Components, but here's a good URL to crash right away in xul.dll: https://www.cbsnews.com/news/asteroid-2023dw-could-hit-earth-valentines-day-2046-nasa/?ftag=CNM-00-10aab7e&linkId=204708560 Should be fixed already by upstream.2 points
-
No, appears to be .NET Windows Forms app with WebBrowser control, so just a frame around Internet Explorer's Trident engine provided by the operating system. You cannot pack actual complex web browser with ability to handle modern web in few megabytes.2 points
-
ive been using your browsers as well and have never had any problems with them (way better than chrome) I'm also following this now2 points
-
@NotHereToPlayGames Your efforts are always appreciated, I really like 360Chrome. Thank you so much for that. Continue on your hard work, and never let people who don't like your personal work discourage you!2 points
-
Everything needs to be tested first, disable unnecessary processes! And if that doesn't help, then you need to change the SSD!2 points
-
Using Chromium with SwiftShader: https://chromium.googlesource.com/chromium/src/+/6b68d1e9b4fec5a7ded58c4ba0fd08078c740c70/docs/gpu/swiftshader.md WebGL Renderer on WebKit Browser #2864: https://github.com/microsoft/playwright/issues/2864 - with Chrome 85 picture ... What Is WebGL and How to Enable It in Any Browser: https://techwiser.com/enable-webgl-chrome/ TEST: WebGL Report (with Platform and Browser User Agent): https://webglreport.com/2 points
-
If I may say so, anyone who would flame you/criticize your hard work isn't someone I would want to associate with, here or elsewhere. I took a few days off to consider things, and was giving serious thought to returning to XP x64. Seeing you did another 360v13.5 build was all the motivation I needed, so I'm back (and plan to stay with it; thankfully, any concerns about future upgrades are now settled, so for now I can use XP safely and happily). Thank you very much for continuing to devote time and effort to this fantastic project! I've never had a problem with 360 at any point...aside from the weird 'rewriting files' bug for which a very simple workaround exists (one you don't need an addon for), every version of 360 I have tried, from you and other sources, has been an absolute joy to use. I think at this point I'm going to stick with 360, while allowing for other options (Mypal68, MiniBrowser, older/newer roytam1 builds, etc.) as alternate browsers and, of course, keeping track of any new developments. 360 is pretty much as good of a balance as possible: it uses a good modern engine with solid support for recent web standards, still has Flash support (and can even use NPAPI plugins!), and thanks to your optimization is performing well on my old HP S5-1020. Actually, the performance is far better than Mini and competitive with 9.5/11/12, something I wasn't sure could be achieved with 13.x. It's funny because every time I try something newer, I keep going back to XP. It is a near-flawless masterpiece of an OS. I still maintain, and I'll stand by this until the day I pass, that if Microsoft had simply let XP be the last Windows and just kept offering updates and kernel improvements, they would have avoided a lot of BS and still made a lot of money. Again...thank you for doing what you do, sir!2 points
-
One may want to use the password manager. Will depend on your graphics card. I do not need to change any flags to enable WebGL on any of my computers, I only need to not disable via the loader.ini. On XP, WebGL on Chromium can only work using SwiftShader (doesn't use GPU, very slow), which should work if WebGL wasn't disabled or required DLLs deleted. Due to above, results from St52 don't say much. Mozilla-based forks don't have SwiftShader fall-back, fair comparison on XP is therefore impossible. https://bugzilla.mozilla.org/show_bug.cgi?id=15283972 points
-
You are bumping it constantly. So be warned, you can be banned from MSFN for doing this kind of IMPATIENT bumping of your topics.2 points
-
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)2 points
-
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.2 points
-
2 points
-
2 points
-
Hi, the integrated network card in my computer is probably broken... I found an old 3COM on PCI, unfortunately it only has drivers for 32 bit systems. I am not able to install it through the device manager because the architecture does not match. Is it possible to get around this somehow? Thank you in advance for your answer1 point
-
1 point
-
Are you sure? There's only 7 bits there instead of 8.1 point
-
I saw that some time ago, apparently WebGL was properly supported on XP years ago. I haven't tried with mentioned version on XP since I've been pretty much daily driving Win7+ ever since I bought a decent PC over a decade ago, these days it's probably a PITA to navigate with such an old browser...only tried getting 360Chrome 13.5 to use any form of 3D acceleration on XP in relatively recent times, but no luck. Haven't inspected deeper, but it's quite possible it loads D3D DLLs from system folders and putting WINED3D DLLs near 360chrome.exe or chrome.dll was completely pointless...1 point
-
webGL is disabled by default on Centaury browser. despite this the maps work well with it.1 point
-
... Very true , however "yt-dlp" is a much richer, feature-wise, fork, supporting now many more extractors (sites) than the original project, youtube-dl, not to mention the fact they have currently a team of numerous active and very skilled devs, ready to "jump in" and attempt to fix all the "counter measures" various media sites impose on downloaders ; to put it briefly, I'd dare say youtube-dl is currently in "maintenance mode", with only one active maintainer, who, when not closing multiple duplicates, spends his coding time backporting fixes from "downstream"; better than nothing, still ... So, maintaining "yt-dlp" support (in XP/Vista - when it comes to that ) as long as possible is a desired thing ...1 point
-
Your chrome.dll file needs "rebased". If you upload your chrome.dll and provide a link to that upload, I will "rebase" it for you and send it back to you.1 point
-
It was 17 hours, can you give me the script to me now?? I also corrected in the quote for you. Does the script work for this gadget that I need a fix on? Thanks1 point
-
1 point
-
@VistaLover thanks for the suggestions. I do use CTR, TMP, S4E, all the popular extensions that attempted to undo Mozilla's efforts to 'Chromeify' the Firefox UI. But this effect is odd because it only occurs once many tabs are open. It can't be just a CSS thing, so I don't know what it is. Yes, or right-click a tab and use Close Tab. Lots of ways to skin this cat. The thing about a UI is that there is often no 'better' way, just different ways, and most importantly, the way we get familiar using. Ben.1 point
-
... 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
-
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
-
New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20230311-409cc309-uxp-6f99b9744-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20230311-409cc309-uxp-6f99b9744-xpmod.7z My changes since my last build: - [Navigator] ported PM version of tab caption fading to here (409cc309) source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20230311-id-656ea98-uxp-6f99b9744-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20230311-id-656ea98-ia-93af9a0-uxp-6f99b9744-xpmod.7z My changes since my last build: - suite: ported PM version of tab caption fading to here (1b3cb632) source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.1 point
-
I do wonder if I can just port PM changes to BK. (can't find a time for this right now since $DAYJOB is still busy these days)1 point
-
@roytam1 I investigated the cause of the issues reported here and on the Pale Moon forum. The issue happened in this commit https://repo.palemoon.org/Basilisk-Dev/Basilisk/commit/dcb4e31c2c47f8daf7978e801aa632853d8ef922 I am going to release updated Basilisk builds with this commit reverted. You should revert that commit and release a new build of Serpent as well.1 point
-
sure, layout is changed by upstream commit: https://github.com/roytam1/UXP/commit/89dd425fd22a6cbbbbef2d2b47e2a4bc9fc14fc31 point
-
Everything is possible, but what you report is strange, in the sense that (AFAICR) Windows 2000 (like NT 4.00) was essentially a "same" OS with only a few differences in the Registry and/or in a few other files, the installation, drivers and booting should be exactly the same. Errors *like* line 53 of INF file" is wrong may be due to *something* in nlite targeting the specific Professional edition (which is of course the "popular" one) and creating a problem in the .inf on the "other" edition, or maybe those SATA drivers are somehow not compatible with Datacenter edition. Still, if your BIOS has IDE compatibility mode, no drivers (integrated or not) should be needed. You could try not integrating the drivers with nlite but use the "normal" F6 floppy way to install them (it is possible to use a grub4dos mapped virtual floppy to replace the "real" floppy which likely you don't have) but it is of course very little documented and experimental, really tested only on XP installs. (by the time grub4dos came out and floppy drives became extincted the only NT os people were interested in was already XP). jaclaz1 point
-
Finallyyy i got it workkk Office 2010 portable version worked fine on Windows 20001 point
-
1 point
-
1 point
-
I never got Office 2010 to install on Windows 2000. Office 2007 worked just fine though except for Outlook, which was completely unusable which made it a dealbreaker for me. But honestly, I prefer the older versions of Office more and more each day. I felt much more productive in them when everything was laid out and not organized the way Microsoft thought it should be.1 point
-
Go to the folder where your screen reader is located and make a file named nvda.exe.local (or whatever the name of the exe is). Copy the original dlls into the screen reader's folder. Only if you want to use my ntoskrnl/ntkrnlmp on a UEFI system.Though you could use that loader/driver I mentioned earlier. But if you just need to use ntdll, it won't be needed anymore.1 point
-
Yes. Hoping there are no issues that may arise once the appropriate functions are added.1 point
-
It is a bit of a precautionary step (I had trouble loading them with my initial modded mfplat.dll and the OS/subsystem minor versions untouched), but yes they do!1 point
-
Using the W7 versions of mf.dll, mfplat.dll plus msmpeg2adec.dll and msmpeg2vdec.dll (plus my newest kernel32.dll), I have restored H.264/AAC support to newer Firefoxes. You will have to use a tool like CFF Explorer to change the Operating System and Subsystem Versions from 6.1/6.2 to 6.0 before applying these files to your system. The issues facing later releases of Chromium, as far as I can tell, seem to be rooted in RtlFreeOemString's subroutines, which seem to differ between Vista and 7. With this in mind, I may start tampering with ntdll.dll in spite of its lack of redirect-ability and its digital signature (which other usermode dlls lack; but that changes in Windows 8). If I were to start extending ntdll, you would have no choice but to boot with my version and likely have to disable driver signing enforcement (which is how I run my 2012R2 in order to use my GPU drivers anyway). While I'm at it I could add NtOpenKeyEx (which later Chromiums ask for) as well as RtlQueryPerformanceCounter in order to simplify the process of preparing new Firefoxes. And all of those functions that some installers call when running with my kernel32.dll! And maybe ensure that winSAT works when display drivers use my user32.dll!1 point
-
And look at that, Aero Glass is back. And it looks much better than the blue window borders in the last official versions. Remember, Vista is not XP! Visual Studio Code 1.46 (based off of Electron/Chromium 78) is working, as is PassMark PerformanceTest 10.0 x64 (except for the DX12 part obviously).1 point
-
I have decided to prioritize the x86 extended kernel over the x64 Haswell Logon Bug Fix as the latter is non-fatal, while lacking functions for x86 software is (unless you switch to a newer OS of course). Unfortunately there seems to be severe restrictions on what can be done to the x86 kernel32.dll. Unlike with the x64 one, you cannot put the export table wherever you like. And even moving the reloc and rsrc tables (plus the directory addresses) makes the PE32 image bad. So I cannot make a new section before rsrc that would house the expanded export table like in the 2000/XP extended kernels. At present my only solution is to remove seldom-used functions from the export table to ensure that enough room is present for mine. Nonetheless, oCam 511.0 is working (515 may work on vanilla Vista). You do it by the book and your hard work is rejected. update: After eliminating the debug directory and moving down the import table, I only have enough room for about four functions. Actually I can put the code in a section below .reloc like I've done with x64, leaving .text open for a bigger export table. But it would be rather difficult to move a thousand+ bytes worth of it. At least everything between 7DE37F10 and 7DE38F10. SECOND UPDATE: I was finally successful in placing a new export table section between .data and .rsrc without breaking the image. Here is the specific procedure: -Open up kernel32.dll in WildBill's PETool. Go to the .rsrc section. -Click "Insert section before..." on the Sections drop-down menu. Select your preferred name and size. -However, the section will not be the preferred size by default. To make it so, select "Consume slack..." from the Sections drop-down menu and press OK on the dialog that appears; the amount of slack expansion offered by default is the max. Any deviation from these three steps produces breakage! -Then use BWC's PE Maker to move the export table.1 point
-
The update.exe module in the WhatsApp x64 installer is still 32bit. And I noticed they only support Windows 8 and above. Though it probably works on Windows 7 too since all Windows 8+ functions are currently in a broken state in my kernel. But I noticed that the application itself is stored in X:\Users\User\AppData\Local\SquirrelTemp\WhatsApp-2.2027.10-full.nupkg\. I extracted it from that package with 7zip and it ran.1 point
-
Windows 2000 exkernel v3.0e actually has all the necessary functions, but the lack of D2D1.dll is a real killer, as Direct2D needs Vista with Platform Update. I've managed to change incompatible NT6 functions to compatible NT5/6 functions by editing import tables using CFF Explorer, with varying success. It's apparently not supposed to work, as the functions' signatures usually don't match, and the replacement functions usually don't have the functionality of newer functions, but it worked for Blender 2.80 and Chess Titans from Vista build 5270 (versions from Vista 6002 and 7 SP1 didn't work). On XP/2003, you might be able to solve your advapi32 issues with xompie (keep in mind I've never used it or even looked at the wrapper DLLs) but D2D will be very difficult if not impossible. UPDATE: here's what to do if you want Sumatra PDF 3,2 on Windows XP (only tested on 2000 though): -download win2k exkernel v3.0e, open the executable in 7zip and extract msvcrt.dll from the vista folder (seems to rely only on XP functions) -place msvcrt in program folder, rename to "msvcr1.dll" then hex edit all instances of msvcrt in Sumatra exe to msvcr1 -copy all wined3d for 2000/XP files (contained in dx folder in exkernel exe) to the program folder. that or get d2d1.dll from Vista/7 and hex edit all instances of msvcrt in it to msvcr1 -it should work, as a similar procedure with windows 2000 works. But you will probably not have titled tabs or a toolbar.1 point