Leaderboard

Thanks for the hint! I took a quick look at this. Looks interesting.

I don't use Supermium, I use this browser, so nothing to "wait" for. https://msfn.org/board/topic/186346-i-moved-to-centbrowser-i-feel-happy-about-it/

No, it's not. "I will change the default for Sec-Ch-Ua to "Google Chrome". I think this may also help with some other website compatibility issues and reduce the fingerprinting surface of Supermium. And also introduce the option from ungoogled-chromium to disable UACH altogether, as well as options to report as Windows 11, iOS 17, Android latest version or macOS 15." https://github.com/win32ss/supermium/issues/779#issuecomment-2269497358

@Cixert Here are the sizes and number of files more detailed which were downloaded in my WSUS download sessions including the updates I manually added as their download failed: Windows XP x86: Size and number of files in the folder client\cpp: 87.6 MB and 12 files Size and number of files in the folder client\dotnet: 286 MB and 3 files Size and number of files in the folder client\dotnet\x86-glb: 673 MB and 95 files Size and number of files in the folder client\msse\x86-glb: 115 MB and 4 files Size and number of files in the folder client\wddefs\x86-glb: 55.4 MB and 1 file Size and number of files in the folder client\win\deu: 33.1 MB and 19 files Size and number of files in the folder client\win\glb: 115 MB and 4 files Size and number of files in the folder client\wxp\deu: 725 MB and 310 files Size and number of files in the folder client\wxp\glb: 10.0 MB and 3 files Office 2007: Size and number of files in the folder client\o2k7\deu: 430 MB and 3 files Size and number of files in the folder client\o2k7\glb: 31.9 MB and 2 files Size and number of files in the folder client\ofc\deu: 81.8 MB and 7 files Size and number of files in the folder client\ofc\glb: 5.08 GB and 572 files Office 2010: Size and number of files in the folder client\o2k10\deu: 628 MB and 1 file Size and number of files in the folder client\o2k10\glb: 101 MB and 1 file Size and number of files in the folder client\ofc\deu: 19.7 MB and 1 file Size and number of files in the folder client\ofc\glb: 5.00 GB and 200 files @Cixert Please copy this list, replace my values with yours for easier comparison and post it here! BTW, I have always enabled the option for the download of Service Packs. That's probably the reason for the different size of the folder client\wxp compared to yours. And it should be mentioned that Office 2010 is not XP-compatible as this topic here is located in the Windows XP subforum. That's why I downloaded Office 2010 updates with WSUS Offline Update 11.9.6 instead of WSUS Offline Update 9.2.6, BTW. In any case, it is only included here for reasons of comparison regarding downloading updates with WSUS Offline Update in 2024. Greetings, AstroSkipper

Honestly, I'd wait for the author to answer, don't listen to the strangers.* *That guy, especially.

As we all know, starting with Chrome 122 (Final release), they can't be forced off via the known cmd flag. Members are welcome to post their ways of dealing with 'em. Probably, someone already knows a crx extension? I tend to edit each Chrome browser manually, but it's not convenient for most of the users. Also, it has some disadvantages, sometimes leading to a unique fingerprint, In all, we need a working fake CH switcher.

Which one do you prefer more, mine, or Dave's: NT 5.1 x86 + Chrome 124. And what exactly do you think makes it unique? The space between the brackets is empty in mine. Thanks, https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=1268273

Can I use my proxy servers (paid, encrypted with a pass) for downloading from insta with it? Those proxies need to be changed via script 'cause insta blocks IPs after a couple dozens of pics were downloaded. I'm scrapping accounts with sports food.

The downloads depends on the weather. That's what my grandmother would have said if she were still alive. You are simply great.

No problem, as may already know, ClientHints are invoked by javascript, so search for the area around the browser navigator. There are also many other useless entries like navigator.userAgentData Navigator.usb.get Navigator.bluetooth.get navigator.userAgentData is the one responsible.

I agree with you, I'm still testing. But like I said, it's already a good result. I want to achieve all fields empty. But I, at least for now, don't know how to block the whole API.

I really wanted to name this "My browser builds of roytam1's browser builds (Part 1)" to be funny, but I figure it makes more sense to give the names. This started since I wanted Interlink Mail & News but portable. Then I figured since I'm already forking UXP, I might as well build UXP stuffs too. So that's what happened. Eclipse Mail or eMail is my own fork of Interlink Mail & News, or mailnews. Some advantages over upstream are installer and true portable variants, compatible with IA-32 i686 class hardware, more optimizations, and the use of SQL instead of DBM for better compatibility with upstream profiles. Main download: https://github.com/Eclipse-Community/eMail/releases Alternative download: https://sourceforge.net/projects/email/files/ Eclipse Lun3r is my own fork of Pale Moon or New Moon. Some advantages over upstream are installer and true portable variants, more optimizations, features from Mypal like duplicate tab, experimental and very broken e10s support (it works better in Hydra), and the use of SQL instead of DBM for better compatibility with upstream profiles. Main download: https://github.com/Eclipse-Community/UXP/releases Alternative download: https://sourceforge.net/projects/lun3r/files/ Eclipse Hydra is my own fork of Basilisk or Serpent. Some advantages over upstream are installer and true portable variants, more optimizations, features from Mypal like duplicate tab, experimental e10s support, and the use of SQL instead of DBM for better compatibility with upstream profiles. Main download: https://github.com/Eclipse-Community/UXP/releases Alternative download: https://sourceforge.net/projects/lun3r/files/ I don't guarantee consistent updates, or work on fixing features like e10s or WebExtensions. I am too busy with r3dfox and other projects to dive into that. If you run into any bugs or issues, please report it on GitHub under the issues tab. I am more likely to get to it and remember to fix it if it's there. If you don't have a GitHub account, here is fine too though.

Thanks !

I will ignore this (and don't report), I want to see the link. I didn't ask for any "images", I asked you to give a link to what you always claim, the "IT industry professor" work, Do you have a Pro LinkedIn account, or published studies? Edit. Do you understand this sentence?

There couldn't be a "constructive debate" with you because you again simply attacked D.Draker and went very personal on him, again. Telling to wait for the author to answer is NOT something out of the ordinary! Telling don't trust third parties (strangers, esp. the obscure ones), also not. Get real. Edit. Your screenshot doesn't work! There's no CentBrowser developer here. You both are very welcome to write to him on github or wherever he (she?) is.

You're welcome! Now first the procedure how to check whether you need to correct any of the known-to-have-issues-groups: In registry editor you click on HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services and then press CTRL+F (Edit/Find...) and write into that window the name of wanted group, e.g. Filter; also tick "Match whole string only" so you don't get false results. Updated: Filter 0b is not necessary with factory filesystem (not disabling LastAccessUpdate or other similar useless stuff). Filter 06 is good and also a factory setting when installing XPSP3 anew with Unofficial SP4 from Harkaz. Besides - the system is faster this way. The other 2 files are Primary Disk and SCSI Class groups of which the last is either 03 (factory) or full up to 2d (with all 45 members /that don't exist/). Please, do check Tags before editing. GroupOrderList_Primary_Disk_05_XP_USP4.txt GroupOrderList_SCSI_Class_03_XP_USP4.txt GroupOrderList_Filter_06_XP_USP4.txt

Thank you! Very good. Yes, I do have them enabled. Windows made a MEMORY.DMP about 400mb, also it was able to create Report.wer, from this report I found out that Thorium has a conflict with Vista's generic KB driver! For some reason Thorium uninstalls it! Then Windows reinstall sit with the error code 24, resulting in BSOD. AppCrashView.exe by nirSoft was useless, it couldn't even open my Report.wer. I was shocked to discover an app from 2015 doesn't support drag-n-drop. Ridiculous since it's basically a txt file! With the good ol' WinHex, suggested by @D.Draker, I got the job done. AppName=Standard PS//2 Keyboard AppPath=C:\Windows\System32\drvinst.exe ReportDescription=Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 24.

The blind leading the blind, anyone...? Do you know what an API is? It's easy for non-programmers to confuse an application programming interface concept with implementations of that interface. API: - https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_2/nn-dxgi1_2-idxgiadapter2 - https://learn.microsoft.com/en-us/windows/win32/api/d3d11_1/nn-d3d11_1-id3d11device1 KB2670838's versions of dxgi.dll, d3d11.dll, and co provide this API. The associated symbols and structures of this API exist on Windows 7. They are exported. They are callable. No access violations. Try arguing that this application programming interface does not exist on 7 to the programs which interface with it on 7. As I already explained, it was provided on 7 to simplify code for applications that expected Windows Store distribution but wanted to maintain less separate logic for d3d devices on 7 vs 8. The differing implementation of the API on 7 vs 8 doesn't magically invalidate the fact that this API exists on both platforms. That's why we have a difference between interface and implementations. Upgrade's implementation has the shiny new features. Downlevel's implementation might be full of ERROR_UNSUPPORTED query results. Interface ≠ implementation. Here, you can educate yourself regarding the topic. - Step 1: Any introduction to C book will do. Or, since you fancy yourself a programmer, you can jump to this book that Google found regarding interfaces and implementations: http://www.r-5.org/files/books/computers/languages/c/mod/David_R_Hanson-C_Interfaces_and_Implementations-EN.pdf - Step 2: Refer to msdn: https://learn.microsoft.com/en-us/windows/win32/api/dxgi1_2/ Accurate documentation with precise explanations. You can write a sample program to observe how these things work, if you don't believe the literature. Here's a springboard for you: https://walbourn.github.io/anatomy-of-direct3d-11-create-device/ from legendary DirectX team member Chuck Walbourn. Do you know what a feature level is? Microsoft terminology is admittedly a little muddy regarding this, but it becomes apparent while working on these kind of programs. https://learn.microsoft.com/en-us/windows/win32/direct3d11/overviews-direct3d-11-devices-downlevel-intro I was talking D3D11 feature levels, not 12, so let's use this link about D3D11 Feature Levels, not your link about D3D12 Hardware Feature Levels. These are different things. If you can't figure it out, here are precise and simple explanations for you: - Windows implements Feature Levels. The D3D11.1 API (remember what an "API" is?) is the interface between your application and the abilities of the Feature Level you want. A lack of the Feature Level you want does not magically mean the API has ceased to exist. - Graphics drivers implement Hardware Feature Levels and advertise their compatibility with them. When your application uses the D3D11.1 API to request an ability of the 11_1 feature level from Windows, Windows in turn must request that ability from the graphics device driver, which in turn can only offer that ability if the graphics device hardware is capable of it and the graphics driver is programmed to drive said ability. Feature Level ≠ Hardware Feature Level. Mono knows there is no 11_1 feature level on 7 and does not bother trying to acquire an ID3D11Device1. Again, you have entirely failed to understand why KB2670838 was created and why it does what it does. Microsoft policy required all Microsoft Store programs to use the D3D11.1 API when using the machine's graphics device. There was (and still is) absolutely zero need for Mono to become compatible with distribution on the Microsoft Store. KB2670838 was a simple standardization effort to reduce manhours of programmer labor and conform to manufacturing requirements. It happens all the time. KB2670838 was never about blessing Windows 7 users with the shiny new Windows 8 features. That would reduce Windows 8 sales. It was about saving costs. Just like how the similar D3D11 platform update for Vista was never about enabling Vista users to play D3D11 games. It was about reducing manhours of programmer labor in the Internet Explorer team to enable a single codebase from which IE 9, 10, and 11 could all be built as efficiently as possibly. Vista needed to be uplifted to the D3D11 common denominator of that unified code base to enable its continued contractual servicing. These are just ABCs of standard software development. APIs provide stability and insurance against time and varying implementations. Your program talks to Windows API to get an implementation. Windows talks to the graphics driver API to get an implementation. The graphics driver talks to the hardware to get a result. Just because one of these links in the chain doesn't exist and you don't like that (11_1 feature level), does not magically mean that the rest of it doesn't exist either (D3D11.1 API). Someone somewhere once said, "if you aren't a programmer, don't blah blah..." ...especially if you are going to be arrogant, rude, & condescending about something you don't know. And hijack a random person's thread, no less! I created this thread to try to find a solution to a problem I'm facing. You get the satisfaction of derailing my attempt to find a solution, and I get the fun chore of having to clean up the dump you took in this thread. Ironic. This was the thread you followed me from, btw. Shame on me for making a post in that thread. It was only my fourth post on MSFN and within 48 hours I ended up on the radar of two trolls itching for a fight. I thought MSFN was better than that.

StartAllBack 3.8.2

You're welcome, glad to be of help, the driver I gave, it's one of the best for the Pascal gen., Let's not forget, GTX1080 is 8 years old. So don't chase newer drivers.

I already modified the 360Loader.ini. I changed the name of both files to ThoriumLoader.exe and ThoriumLoader.ini and replaced the Icon Group of the ThoriumLoader.exe by the one from the thorium.exe. This modified loader works well to call up Thorium. And due to its separate ini file, the command line flags set by the user can be easily changed at any time. Here is a screenshot taken from my current "Open with" context menu in Windows XP: Everything I have written so far proves that Thorium can successfully take up and load a link via a command line call, initiated from the registry, when using a loader such as ThoriumLoader. Cheers, AstroSkipper

[Setup] AppName=Thorium [FileToRun] PathToExe=.\Chrome\Application\$AppName$.exe Parameters=--user-data-dir="$Profile$" --no-proxy-server /high-dpi-support=1 /force-device-scale-factor=1 --disable-component-update --use-angle=d3d9 --ignore-gpu-blocklist --single-argument [Environment] Profile=".\Chrome\User Data" This is what I actually meant. PS: Think of the Space Bug! Can you still remember?

Do not remove the [Environment] section! Simply set there your current profile path and replace the path D:\Program Files\Thorium\Chrome\User Data under the [FileToRun] section by your enviroment variable $Profile$.

That's very simple. Perform a right-click on a link to be opened, click on the item "Select a programme" from the "Open with" context menu and point to your 360Loader! When done, an entry is automatically created and stored in the registry under the HKEY_CURRENT_USER\Software\Classes\Applications\360Loader.exe key. From now on, you have an entry in the "Open with" context menu for taking up links by the 360Loader.

@AstroSkipper Just check this out - Office 2007 UpSourcer. Real problem solver There is also 2010 ones which is realy builded to works with XP and 2003 too! https://forums.mydigitallife.net/threads/upsourcer-slipstream-patches-for-office-2007-2010-2013-2016-and-rebuild-setup-source-files.87111/#post-1794847

Something tells me that device is locked to the OEM manufacturers drivers only. I had a similar case in the past, only the supplied drivers worked, all drivers from Nvidia site simply crashed during high load.

It's because they were boiling the frog very slow, now it's used up to the much wider extent.

Thanks, but I specifically pointed out to Chrome only browsers in the topic's title.

I didn't say that the files in the client\ofc\glb folder are exclusively for Office 2010 or higher. I said: Inside this folder, there are of course many updates for Office 2007 (12.0.xxxx.xxxx), too. Simply have a look at the xml files inside the cab files! All files with the version number 12.0.xxxx.xxxx are targeting Office 2007. As you already cited the creators of WSUS Offline Update 9.2.6 correctly, the download of updates for older Office versions leads to dynamically determined updates which are also downloaded. Either leave them in that folder or delete them before creating the iso image!

StartAllBack 3.8 is a major update with fully recreated taskbar. It will be necessary for August 24H2/23H2 update. It's like 70% new app. It's free update and it's buggy and it's your fault for not testing!

Official Palemoon uses System accelerated codec(Media Foundation) for decoding video, not my build

Please try official build(on Win 7 or newer OS of course) first. If official build doesn't work, report a bug to them.

I can try updating libvpx with 52esr one, but I think I can't use ffvpx because palemoon's build system can't use assembler flags. Not to mention you have to fix code to use ffvpx. BTW: https://forum.palemoon.org/viewtopic.php?t=13086

There is no difference with LAV and VLC as they all use ffmpeg libraries.

Try extracting with 7-zip as archive is compressed with LZMA2.

Pale Moon XP get no Graphic card based acceleration for video playback (unless you use new OS and use OS' Media Foundation codecs). So if your CPU is not fast enough, video playback may become choppy.

X264 is for ENCODING.

jemalloc may be the one who limits 1.5GB RAM usage. If you know how to change the limit without breaking it, please tell me.

https://o.rthost.cf/palemoon/sources_patches_20171004.7z Some changes from Feodor2 are not integrated, maybe I should update the source patch archive after $dayjob.

You can always use `git apply my-patch.diff`to apply my patches. Git may complain there is trailing spaces in the patch file but the patch will be applied anyway. If you're applying my patch without git environment, use GNU patch utility then: patch -p1 -i my-patch.diff