Leaderboard
Popular Content
Showing content with the highest reputation since 07/06/2025 in all areas
-
New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250712-3219d2d-uxp-b9ebe5b259-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250712-3219d2d-uxp-b9ebe5b259-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-20250712-3219d2d-uxp-b9ebe5b259-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.7a1.win32-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250712-d849524bd-uxp-b9ebe5b259-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2106 - Part 1: Un-prefix -moz-user-select (cc55a380f6) - Issue #2106 - Part 2: Align value names (17b594b705) - No issue - Fix mixing of tabs with space-indented code. (552cb8dbcc) - Issue #2045 - Part 1: Revert "Temporarily force hidden elements to be actually hidden." (dd2cf17d30) - Issue #2045 - Part 2: Add handling and storage for the revert unit and value (7f3f90eed4) - Issue #2045 - Part 3: Implement cascade origin tracking to CSS parser (b0f0972314) - Issue #2045 - Part 4: Parse "revert" in property values wherever "unset" is allowed (9105c58a30) - Issue #2045 - Part 5: Serialize shorthands using "revert" like those containing "unset" (801d4a2db8) - Issue #2045 - Part 6: Treat "revert" values as the same as "unset" when encountered in the rule node (c4b6135c99) - Issue #2045 - Part 7: Override revert values during presentation hint cascade (166e98d2b9) - Issue #2045 - Part 8: Remap revert keyword values to a higher cascade level (a47f44e93d) - Issue #2045 - Part 9: Include the revert keyword in the list of accepted values for CSS properties returned by inDOMUtils (5346e55655) - Issue #2045 - Part 10: Regenerate devtools CSS database and include the revert keyword in related devtools code (f0b8d1df2c) - Issue #2106 - Part 3: Add 'contain' as user-select value, retain 'element' (e6b48fcc95) - [devtools] Further improve special character escaping in "copy as curl". (2d9cb22a28) - No Issue - Add detection for medium in border shorthand (9f7430f8b9) - Issue #2124 - Adjust overflow parser to handle two values (f4ffb1ec16) - Issue #2662 - Implement axis-shorthand parsing (7c52fd934f) - Issue #2124/2662: Optimize overflow shorthand parsing and serialization (7626c99ceb) - Issue #2124/2662: Cleaning of code (dae72b452c) - Issue #2106 - Follow-up: Additional Un-prefixing (1a5b3dcae6) - Issue #2106 - Follow-up: Un-prefix DOM Attribute MozUserSelect (abb891ff26) - Issue #2106 - Follow-up: Additional contain Keyword Entries (f1815317c3) - Issue #2106 - Clean-up: Remove Defunct -moz-user-select CSS Directives (8f46cd0d63) - Issue #2106 - Clean-up: Un-prefix -moz-user-select in Comments (b11affbdf3) - Issue #2780: Add back the mismatch overflow handling in nsRuleNode.cpp (c3590da576) - Issue #2757: Create a new basicShape of type inset then set inset coords to zero. (67421b3048) - Issue #2757 - Follow-up: Add clip-path test (manual QA) (3f67905afc) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - gfx: relax DrawTargetCairo::IsValid() check, fixes crash when loading spectrumsurveys.com (10b96192dd) - layout: plug back alias of -moz-user-select so it won't break pages/extensions relying on this (4c8df426a8) Update Notice: - You may delete file named icudt*.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
-
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 https://o.rthost.win/basilisk/basilisk55-win32-git-20250712-6129895b4-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250712-6129895b4-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #2106 - Part 1: Un-prefix -moz-user-select (cc55a380) (cfadbb5d6) - ported from UXP: Issue #2106 - Part 2: Align value names (17b594b7) (3a0677ec7) - import from UXP: No issue - Fix mixing of tabs with space-indented code. (552cb8db) (4634fe9d1) - import from UXP: Issue #2045 - Part 1: Revert "Temporarily force hidden elements to be actually hidden." (dd2cf17d) (29e601bb8) - import from UXP: Issue #2045 - Part 2: Add handling and storage for the revert unit and value (7f3f90ee) (f49dc1068) - ported from UXP: Issue #2045 - Part 3: Implement cascade origin tracking to CSS parser (b0f09723) (13380336f) - import from UXP: - Issue #2045 - Part 4: Parse "revert" in property values wherever "unset" is allowed (9105c58a) - Issue #2045 - Part 5: Serialize shorthands using "revert" like those containing "unset" (801d4a2d) (f780f6a0c) - ported from UXP: Issue #2045 - Part 6: Treat "revert" values as the same as "unset" when encountered in the rule node (c4b6135c) (0ddba686d) - ported from UXP: Issue #2045 - Part 7: Override revert values during presentation hint cascade (166e98d2) (33497a7bb) - import from UXP: Issue #2045 - Part 8: Remap revert keyword values to a higher cascade level (a47f44e9) (7e8276dd1) - import from UXP: Issue #2045 - Part 9: Include the revert keyword in the list of accepted values for CSS properties returned by inDOMUtils (5346e556) (5b3195dad) - ported from UXP: Issue #2045 - Part 10: Regenerate devtools CSS database and include the revert keyword in related devtools code (f0b8d1df) (e92c563a4) - import from UXP: Issue #2106 - Part 3: Add 'contain' as user-select value, retain 'element' (e6b48fcc) (f073823cd) - ported from UXP: [devtools] Further improve special character escaping in "copy as curl". (2d9cb22a) (28bf4bcf2) - ported from UXP: No Issue - Add detection for medium in border shorthand (9f7430f8) (4f0690a20) - import from UXP: Issue #2124 - Adjust overflow parser to handle two values (f4ffb1ec) (ae483ab3b) - ported from UXP: Issue #2662 - Implement axis-shorthand parsing (7c52fd93) (f7844356c) - ported from UXP: Issue #2124/2662: Optimize overflow shorthand parsing and serialization (7626c99c) (55a3af5f7) - ported from UXP: Issue #2124/2662: Cleaning of code (dae72b45) (9c80beb8f) - ported from UXP: Issue #2106 - Follow-up: Additional Un-prefixing (1a5b3dca) (82ff6f599) - import from UXP: Issue #2106 - Follow-up: Un-prefix DOM Attribute MozUserSelect (abb891ff) (2b505c1fd) - import from UXP: Issue #2106 - Follow-up: Additional contain Keyword Entries (f1815317) (db2c8fdb5) - ported from UXP: Issue #2106 - Clean-up: Remove Defunct -moz-user-select CSS Directives (8f46cd0d) (37991f84a) - import from UXP: Issue #2106 - Clean-up: Un-prefix -moz-user-select in Comments (b11affbd) (477ab51c4) - import from UXP: Issue #2780: Add back the mismatch overflow handling in nsRuleNode.cpp (c3590da5) (0ee810368) - import from UXP: Issue #2757: Create a new basicShape of type inset then set inset coords to zero. (67421b30) (0ea914daf) - import from UXP: Issue #2757 - Follow-up: Add clip-path test (manual QA) (3f67905a) (1b8fbc344) - import from `custom` branch of UXP: gfx: relax DrawTargetCairo::IsValid() check, fixes crash when loading spectrumsurveys.com (10b96192) (6129895b4)3 points
-
I think we have to take Shane's word for it that the patch has been applied to Supermium 132. As I said earlier, it's an ESR version, which surely should be capable of having the patch applied to it, as it should be fully supported until the next ESR version is released. I'm not sure how we can test whether the patch has been applied successfully or not.3 points
-
@reboot12 Make some tests with disable and enable the Microsoft UAA drivers in System Devices. I remember, that I had the same problem and the admin @Dave-H here also with Baytrail Flex 10 and XP and sound Dietmar3 points
-
New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20250712-7bda12e7-uxp-b9ebe5b259-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20250712-7bda12e7-uxp-b9ebe5b259-xpmod.7z 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-20250712-id-656ea98-uxp-b9ebe5b259-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20250712-id-656ea98-ia-c642e3c-uxp-b9ebe5b259-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild2 points
-
Strange, but it appears that the issue has completely resolved itself.2 points
-
At least the acronym (BSoD) will still be valid, since both black and blue begin with the letter 'b' c2 points
-
Then it's a good idea to use the patched ungoogled for Server 2008 R2. No one knows and no one can guarantee how good and when the old 132 Supermium will (ever?) be patched for that serious vulnerability. https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_138.0.7204.96 Edit/ They say it's been patched in R5. But in the article they say the patch is for 138+! Contradictory. https://github.com/win32ss/supermium/releases/tag/v132-r52 points
-
That was clear, but from what they tell, looks like the patch is intended to be applied only to 138+. Who would write a patch for the old 132, while we are at 140+ already?2 points
-
off topic: after using for 5 years and wrote ~90TB, my SN750 1TB lost from system first time. following experience from last time, I grabbed my unconnected idle 970evo+ and did a quick clone and let SN750 idle without electricity instead. time to find another m.2 stick with DRAM.2 points
-
I sincerely hope Mr. D.Draker is simply on vacation...2 points
-
Thanks for linking! Unfortunately, such comparisons are not particularly useful. It also depends considerably on other components such as the RAM memory, north and south bridge, the bus clock, the graphics adapter, processor features, hyper-threading and so on.2 points
-
Not quite true. I use both my old Windows XP computer and my Android tablet for what you call "real work". And in some special cases, a notebook with Windows 7 and Windows 10. But that was not the point here. Anyway! This thread is actually about Mypal 68, and I am happy to confirm that this browser works well on my old hardware. And much better when optimised.2 points
-
Probably @Cixert assumed, and rightfully so, the double engine of 360 Explorer or something similar would be implemented in Supermium, too.2 points
-
2 points
-
2 points
-
I took a closer look at updated file "update.py": https://github.com/nicolaasjan/youtube-dl/blob/embedthumbnail/youtube_dl/update.py which you originally copied from: https://github.com/ytdl-org/ytdl-nightly/blob/master/youtube_dl/update.py The update process correctly "calculates" the hashsum of "current" version, Latest version: 2025.07.12.1, Current version: 2025.07.12 Current Build Hash 58815fc0de70a06e76a9e9ca0337dfcdda59b1db0ffed12d150df626d8cd7735 which is indeed identical to the value displayed at https://github.com/nicolaasjan/youtube-dl/releases/tag/2025.07.12 Which part of the code inside "update.py" is responsible for that? I understand that your tags/releases don't have a SHA2-256SUMSfile as asset... Updating to version 2025.07.12.1 ... WARNING: no hash information found for the release According to https://github.com/nicolaasjan/youtube-dl/releases/tag/2025.07.12.1 the missing hashsum value for youtube-dl.exe should be: 21534c1543d62f4543efff017da1c8dd18a47e64995fd7e8c84215a433752db5 Why isn't "update.py" able to "calculate" it and, more importantly, how can it be fixed? GitHub adding a "sha256:*" column under assets (not as separate asset) is a relatively new feature, AFAIAA... In file update.py, I can identify two hashsum calculating blocks: https://github.com/nicolaasjan/youtube-dl/blob/da27e0bb378940575d4ac1a5d2a9c9899f7f94ec/youtube_dl/update.py#L84-L91 Is this one for "current" (non-updated) binary? Then, there is: https://github.com/nicolaasjan/youtube-dl/blob/da27e0bb378940575d4ac1a5d2a9c9899f7f94ec/youtube_dl/update.py#L130-L138 which obviously pertains to the "updated" binary; I can see mentions there of files "SHA2-256SUMS" that your fork lacks; lastly, the WARNING is issued as a result of lines: https://github.com/nicolaasjan/youtube-dl/blob/da27e0bb378940575d4ac1a5d2a9c9899f7f94ec/youtube_dl/update.py#L172-L174 Someone knowledgeable in Python needs to review the "update.py" file and come up with a "fix"; perhaps if you kindly ask dirkf in GitHub, he could oblige ... C'mon, you know me better than that ... Sorry for being a PITA, best wishes !1 point
-
We need a "benign exploit" page (a page that triggers the bug but doesn't do anything harmful) to test for this vulnerability. We had one for the WebP vulnerability.1 point
-
They have. There's an "ancient" one called xoblite. It's kind of like using fluxbox on Windows instead of Linux. Check out the screenshots and you'll see what I mean. xoblite™ / Blackbox for Windows1 point
-
@VistaLover That's because of line 37 in `./youtube_dl/update.py`. UPDATE_URL = 'https://yt-dl.org/update/' For some reason it redirects to: https://github.com/yt-dlp/yt-dlp/update/ ---> 404. In version 2025.06.26 (and previous versions) I had it set to: UPDATE_URL = 'https://ytdl-org.github.io/youtube-dl/update/' (also 404, by the way) My version is not supposed to be updated with `-U`. Do you perhaps have any idea how to change `update.py` for my fork to actually make it work with `-U`? [Edit] I think I managed to fix it. Took `update.py` from youtube-dl Nightly as an example. youtube-dl -vU [debug] System config: [] [debug] User config: ['--console-title', '--rm-cache-dir', '-i', '-o', '/dev/shm/test-ytd/%(title)s.%(ext)s', '-f', 'bestvideo[height<=1080][ext=mp4][vcodec^=avc]+bestaudio[ext=m4a]/best[ext=mp4]/best', '--no-mtime', '--embed-thumbnail', '--force-ipv4'] [debug] Custom config: [] [debug] Command-line args: ['-vU'] [debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8 [debug] youtube-dl version 2025.07.12 [debug] Lazy loading extractors enabled [debug] Single file build [debug] Python 3.10.12 (CPython x86_64 64bit) - Linux-5.15.0-143-generic-x86_64-with-glibc2.35 - OpenSSL 3.0.2 15 Mar 2022 - glibc 2.35 [debug] exe versions: ffmpeg N-120171-g05094c1749-20250705, ffprobe N-120171-g05094c1749-20250705, rtmpdump 2.4 [debug] Proxy map: {} Latest version: 2025.07.12, Current version: 2025.07.12 youtube-dl is up to date (2025.07.12) Removing cache dir /home/nico/.cache/youtube-dl .. I also don't understand why @dirkf still hasn't updated the Installation section in the Readme. It's a complete mess. BTW, I've made a significant change to `./youtube_dl/utils.py`, as I suggested here. Youtube-dl actually works now.1 point
-
1 point
-
What for? It's obsolete, no matter how good it was 2 years ago. D.Draker no longer recommends this browser due to the age. https://msfn.org/board/topic/186346-i-moved-to-centbrowser-im-not-happy-about-it/page/5/#findComment-12758741 point
-
they did this because they want jemalloc to be integrated into C runtime, which is un-recommended by MS later.1 point
-
This is not a bug, but an improvement to indicate disabled window. There is/will be a setting to disable shading for confused ones [HKEY_CURRENT_USER\Software\StartIsBack\DarkMagic] FadeDisabled = (DWORD)0 There are acrylic effects alright, but it's not supposed to be pure black, maybe extra tweaks on your system.1 point
-
His post is neither useless, nor senseless. Learn to look for before you write your senseless posts It's been confirmed by reputable members of MSFN that those don't work. "This didn't work for me." https://msfn.org/board/topic/186420-mod-for-intel-haswell-4600-hd-graphics-drivers-for-xp/#findComment-1271208 "Edit: After a while (5-8hours) if the PC is not used, the mouse works but I can't open anything that was minimized in the taskbar. I have to restart the PC to get it working again. Did you see this kind of behaviour? I'm using 32bit XP." https://msfn.org/board/topic/186420-mod-for-intel-haswell-4600-hd-graphics-drivers-for-xp/#findComment-12714901 point
-
Eh, everything is described in this forum - learn to look for before you write senseless posts https://msfn.org/board/topic/183956-asus-b85m-e-with-core-i5-4590-code-10-in-device-manager/ https://msfn.org/board/topic/176356-simple-xp-32bit-64gb-ram-true-pae-guide/page/10/#findComment-12809871 point
-
Yes, I can. Then leave only one, what stops you? Never heard of XP using two modern cards all at once in one setup troub;e free.1 point
-
It appears that Windows Defender Updates may not work any longer without the Windows Update service enabled. Tried to enable the update service, and it worked. Turning off the service and trying to update Defender fails with an error now.1 point
-
Version 138 is required for the fix; the bug goes back earlier though: Good catch. Google is being tight-lipped on exactly when this vulnerability crept in. I doubt it goes all the way back to 2008, though. Today's V8 looks nothing like the original. I believe (and should have said) versions prior to the V8 optimizer are not vulnerable. I suspect 360EE (and Kafan MiniBrowser) aren't vulnerable because the option to turn off the optimizer isn't there (presumably because there's nothing to turn off), but I can't be sure with the limited info we have.1 point
-
hmmm in the past we had often a discussion about "32 bit is the 4 gb limit" or = 32 wires 32 bits can form 2^32 bits therefore 4´294´967´296 what represents 4 GB the problem with that is that even in 8 or 16 bit´s there are so called selectors those do actually still exits in 32 bit too also very important is that these 4 GB of possible "addresses" are not converted into that rather the representing PTE´s and PDE´s represent to a 4 KB page (in old normal 32 bit style) so going with that if you have 4 GB/ 4 k pages you end up in only using 20 bits ! (20 bits * 4k = 4 GB) a idea (very similiar to the discussion about 4 k sectors and 4 MB sectors with the harddrive(hdd/ssd)) would be just to increase the 4 K pages to 4 MB pages that would be 1024 times as much RAM the discussion about this are elder thats why that bit (PSE (page size extension)) was 1 candidate to pass that 32 bit limit the other candidate was the PAE bit (physical address extension) here is 1 catch PSE can extend the 4 GB by increasing the page size (even with a 32 bit PDE´s and PTE´s) in PAE mode PDE´s and PDE´s are 64 bit (yes even in 32 bit mode), that´s one of the reasons why PAE can address more then 4 GB of ram (to be more precise paging are mechanism´s there also some more things they play a role the CR3 register (also called the page directory base register) or the GDT, it would be to long to explain all but lets stay like this for now) so let us take the next important step in the old 32 bit system without PSE,PAE or "concrete use of segments", an app/executable had to use up the 4 GB ram because there was a user-mode (ring3) and a kernel-mode (ring0) there had to be a part in kernel mode and a other part in user-mode offsets are not a problem (as you can map a address like 0xFFFFFFFF to page 0 if you wanted) deviding the kernel mode and user mode is important, if that would not be the case every crash on a normal app/execuble would be a entire OS crash (BSOD or wrose) so the solution was simple usermode 0x00000000 - 0x7FFFFFFF - kernelmode 0x80000000 - 0xFFFFFFFF thats how the eldest 32 bit norms work it is not to bad to have kernel mode ram because many modules actually need space in memory (its not like an app is just made out of the app itself the app consits of many modules that also use ram internal) - also the video frame buffer often has a kernel mode area that takes memory for example so here we finally have our split 0x00000000 - 0x7FFFFFFF (2 gb) + 0x80000000 - 0xFFFFFFFF (2 gb) = 4 GB the app/executable now has the problem that it cant directly use the kernel mode offsets (it certainly use them but rather passiv (its some memory you need less in your app)) for this microsoft then made the /3 GB option in this one usermode has 3 GB and kernelmode 1 Gb (0x00000000-0xBFFFFFFF) + (0xC0000000-0xFFFFFFFF) = 4 GB but now the important part those offsets are not physical addresses ! actually you can map every of that "offset´s" to different places in memory (including the ones above 4 GB RAM) so thats why multiple applications/executables can use up the entire 64 GB of RAM (in j7n example he had 20 GB of 64 GB possible) thats more then 4 GB of ram and the proofes XP 32 bit can do it that way now we also have to mention the ramdisc solution, if you have like 20 GB of data and map then into the physical ram then the ramdisc use a chuck-wise solution it then maps for example 1 GB of that 20 GB data into an offset (that goes like fast) (when it wants the next part it just maps the next part - but it is chuckwise) now we have to mention the pagefile, in the pagefile windows stores memory data on the harddrive (HDD/SSD) when windows wants it use exactly that trick (it loads the data from the harddrive into that virtual offset) but this time there is an important differenz - the data is not from a RAM memory - it has to load that from the harddrive (and that is slow) for a SSD its faster - but still not as fast as it would be in memory so i guess some have reconized the increase in speed with SSD`s ? now you have a little more precision why this is the case so now to the part why a "normal app/executable" actually dont pass that 4 GB ram ram limit i already explained why it is rather like 2-3 GB ram + some kernel mode memory that is rather used like passiv but now the reason why it actually dont go beyond the 4 GB ram in "just one application/executable" here you have to know that all compilers form the past-now dont use segment selectors to pass that 4 GB ram i never seen a compiler that would be able to do so. probaly windows xp (even up to win10) dont have code for this either. but here is the thing normally in a code flow of a debugger you see a offset (or better called vitual offset this time) for the code flow it use a register called EIP (instruction pointer) - the E stands for 32 bits - for example only IP for 16 bit and REIP for 64 bit (R means 64bit) but here is the next catch ... the most common debuggers dont show the selector but for the code flow the CPU use a combination of a segment selector + virtual offset (the one you see in a debugger for example) this is called the CS:EIP combination - where CS is the segment selector (called the CODE SEGMENT(short CS) selector) EIP E for 32 bit and IP for instruction pointer now might be a good time to call out a wiki page about that: https://wiki.osdev.org/Segmentation that CS selector is 16 bits wide (in 32 bits) and 16 bits means 65536 possible selctors ... so the combination 16:32 or CS:EIP would be 65536 * 4 GB - that would be theoretical 262144 GB that it could select (+ you have 6 of segment selectors all in range 0-65536) but here is the catch windows (either xp - 10) dont use this to pass the 4 GB limit the only things windows actually did with these registers is that they point to small pieces of memory (like the EPROCESS structure) that is possible - but it leaves out the use to pass the 4 GB of ram limit by just using a few kilobytes with that method ... here is an example where microsoft accesses a small piece of ram using a selector : https://devblogs.microsoft.com/oldnewthing/20220919-00/?p=107195 (the problem with the way this is used, it not used that to pass the 4 GB ram limit, rather is use that as small memory storage) so the next step: back to the app/executable as mentioned there is no compiler that actually generate the useage of segmentation ... therefore you would need a specific app/executable that can do so - and that means chrome still would not pass the 4 GB ram limit (because it cant use segmention) (and then you also would need the windows operating system code also to control this kind of memory managment) also to mention is the FPU unit even the elder ones are 64 bit (or bigger) in modern cpu´s they are 512 bits (AVX) so actually you can make 64 bit moves in 32 bits or calculations, compessions like h.265 do so also some routines are written in the FPU, for example cpu intense sort mechanism´s - you might heared MMX, SSE ect. so in short 32 bit has 64 bit commands that it can use over the FPU unit (what is actually done sometimes) it can pass the 4 GB of ram over multiple app´s/executables it cant pass more then 4 GB of ram with just one app/executable - unless it use a chuckwise method (like the ramdisc) - the segment registers are actually not used to pass the 4 GB ram limit(that also goes for win10 32 bit) so i tryed my best to explain this as simple as i could1 point
-
Are you sure???????? https://en.wikipedia.org/wiki/V8_(JavaScript_engine) Excerpt from Wikipedia. "V8 is a JavaScript and WebAssembly engine developed by Google for its Chrome browser. V8 is free and open-source software that is part of the Chromium project and also used separately in non-browser contexts, notably the Node.js runtime system. Other server-side JavaScript runtimes use alternative engines, such as Bun and Hermes. Wikipedia Developer(s) Google Initial release September 2, 2008 Written in C++"1 point
-
Unlike in your country Armenia, in France sellers are under certain obligations before the customers, for example: they can't refuse to serve basic needs items like soap, condoms, cosmetics, refrigerators, etc. As for the Chanel bags I was going to buy, unfortunately, they can because they belong to the luxury segment. So no, he can't put deadbolts because he registered as a seller and owns a website that he must maintain in accordance with the French laws. And if we speak about that site in particular, the laws of Quebec, which aren't that different because they are an off-spring from France.1 point
-
He lied to you, the owner simply put the slider to the "maximum protection". Again, Cloudflare could care less what the owner chooses.1 point
-
I am not always right. But a pure comparison of CPUs is not sufficient. Read here, for example, about the difference between SD-RAM and DDR2-RAM: https://www.transcend-info.com/support/faq-296#:~:text=DDR2 SDRAM(Double Data Rate,(double of DDR SDRAM). Maybe now you'll realise what I'm talking about. And apart from that, an Intel Pentium 4 is not the same as an Intel Pentium 4. There were different series like Willamette, Northwood, and Prescott. And within these series different FSB clock rates. So, forget about these comparison sites! The only way to compare our computers is doing the same test regarding all hardware components. P.S.: Due to my motherboard layout, there are several bottlenecks. Firstly, the extremely slow SD-RAM memory, then the very low bus clock rate and finally the AGP 4x interface, although my graphics card actually is an AGP 8x one.1 point
-
1 point
-
1 point
-
1 point
-
Done! https://msfn.org/board/topic/186225-change-a-letter-game-part-ii/?do=findComment&comment=12664151 point
-
WMItracing.log OFF (Vista) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\Tracing\WMI] "SessionEnabled"=dword:00000000 "Level"=dword:000000001 point
-
1 point
-
That is of course possible. In any case, I do not have those problems with uBO‘s logger you have described.1 point
-
1 point
-
1 point
-
Probably they implemented some anti-hack feature, in addition to limiting youtube's videos frequently posted by some members?1 point
-
Well, this topic "win7-browsers-video-colour-range-stutter" doesn't specify Firefox only, try to switch to chrome then?1 point
-
I guess 3.5 would be enough since he wanted 3.2.1 point
-
Chip NEC D720200AF1 has certified Dell Vista drivers. Supported Operating Systems Windows Vista, 32-bit Windows Vista, 64-bit Windows XP Windows XP, 64-bit Don't worry about the Dutch language link, it will switch to yours automatically (it depends on the location). https://www.dell.com/support/home/nl-nl/drivers/driversdetails?driverid=36x7d1 point
-
I fail to understand why do they all patch only the standard chrome, not ungoogled.1 point