Leaderboard

Try to ad this to registry by .reg file. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Google\Chrome] "ExtensionManifestV2Availability"=dword:00000002 On Chrome 131 under Windows 10, I don't even get warnings about the end of support for Ublock and some other MV2. Edit: I checked on CatsXP 132 x64 (5.1.1)on Windows 7 - UBlock works without problems, there are no warnings about the end of its support. WidevineCDM has also been successfully repaired.

Heya to all of you in the Community I'm here for some knowledge of how to make windows installer CD -> slipstream packs, drivers etc...

Hi and thanks for staying.

Later on, they became more "clever" to not openly add links to their pages in their scripts by using plain text, and now use Chrome's inbuilt Google Analytics, which is invoked via rather sophisticated and/or hidden scripts.

I'd classify this kind of behaviour as malicious.

https://blog.browserscan.net/docs/client-rects-font-fingerprinting

I always edit all those scripts and simply remove their lust for pings and callings home. I was under the impression you did exactly the same, no?

Well, looks like the lust for glory has finally caught up with win32, I don't know how else to explain it. Why would he intentionally edit that value? All those were supposed to be untouched, that value hasn't changed in decades. It's their internal coding, not related to the actual UA version,

Hiya to you on behalf of the Community.

Hi @ShinNoKabe, hello from Belgium and welcome to MSFN! I wish you to enjoy the forums! Have a nice day. hpwamr

Actually, "Black Monkeys" is waaaay more "racist" by the American standards. And in Europe, at least in France, we don't draw that much attention to one's skin colour. I served with a guy who had a bit yellowish tan on the skin, so, how was I supposed to call him? Hey, yellow male? No, I called him by the name. And in America they call Negroes (which is their official race name) "blacks". It's hard to understand why it's not considered "racist". It's almost New Year, and you, my friend, you're overthinking the whole situation too much. Just go and celebrate! Black males was simply the first suggestion when I started to type "Black M...." in the search window. I congratulate everyone in advance! @hidao Supermium has a lot of unique identifiers, besides fonts, you're better off making a standalone topic.

By scanning and exposing your installed fonts. https://security.stackexchange.com/questions/163376/why-do-browsers-expose-installed-fonts

I can only guess the same's happening with Supermium, that would be a perfect explanation why Brave is on the normal level of brightness, and Supermium isn't. One of the reasons I'm not getting back to it. sadly/

Go to your monitor and start adding the brightness slowly, see how the fonts become thinner and more washed out, so you would need to complicate with your contrast, But in most modern cards - you can't, because the plonkers already set it beyond the reasonable limit in the card BIOS. I had analysed many BIOSes, and in nVidia the RGB values can easily be at 157%, instead of the standard 50. It's called brightness wars, for the people to get a false feeling of the beefy and juicy card they bought.

I have tried the following 2 methods with external USB drives and have had no problems if these steps are followed and the indicated errors are avoided. WORKING WITH GTP HARD DISKS ON WINDOWS XP Update 2025-02-06: It can be done with any of the following methods depending on the hard disk connection mode. A - With the "Paragon GPT Loader" driver v. 8.0.1.0 on SATA ports. B - With the "Windows 2003" drivers on USB ports until 16 Tb. A - With Paragon GPT Loader driver v.8.0.1.0 on SATA ports. ¡¡¡CAUTION!!! +2TiB hard disks connected to the SATA port only work with Paragon GPT Loader driver version 8.0.1.0. -Higher versions of the driver cause data corruption when writing to sectors above 2^32 (4,294,967,296) this is 2TiB. -With PAE enabled to work with +4GiB RAM cause data corruption when writing to sectors above 2^32 (4,294,967,296) this is 2TiB. -The driver usually only works with the BIOS/UEFI set to IDE mode. With AHCI/RAID drivers generally cause data corruption when writing to sectors above 2^32 (4,294,967,296) this is 2TiB. If you have other hard disks connected in AHCI/RAID mode or you don't have IDE mode, the solution is to install a PCI Express SATA card with a switch that enables "IDE mode" or "No-boot mode". -This driver does not work via USB. -Most software tools for editing hard disk partitions do not work on Windows XP with GPT hard disks. -Make a partition table copy because in certain circumstances partitions disappear just by opening Windows XP Disk Manager without performing any additional operations.* -Chkdsk does not work until Windows XP is booted. In case of a file system error the boot will say that FAT32 and exFAT partitions are RAW. On NTFS partitions it will proceed to perform CHKDSK, but it will be invalid. Once Windows boots you have to run chkdsk manually. Most versions of Paragon GPT Loader do not work well with hard disks larger than 2TiB. If the first partition is larger than 2TiB, file system corruption will occur. If the second partition is larger than 2TB, the same will occur. If there are partitions larger than +2TB, then Windows XP will not recognize them. I have found that there is a version that does work well with +2TiB hard drives and also fixes the blue screen problem with FAT32 boot partitions. This version is included in Paragon Partition Manager 15 (aka 2015) Professional x86 v10.1.25.779 (2015-09-18) It contains the 8.0.1.0 driver, it is a downgrade driver but makes several registry changes that other versions containing the same driver or higher versions do not. Use only this version to install the Paragon driver on Windows XP. You do not use forks or other versions. Driver version 10.5.0.95 is limired at 4,294,967,296 sector (this is 2TiB). Also do not use the Paragon HFS v11.0.0.175 fork with a higher driver version as it contains the same problems. The issue is explained here https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/23/#findComment-1276273 To get GPT working on Windows XP via SATA port simply install Paragon Partition Manager 15 Professional x86 v10.1.25.779 with Paragon GPT Loader 8.0.1.0 option enabled and connect the hard disks to the SATA port with IDE mode enabled in the BIOS/UEFI or install a PCIExpress card with SATA ports that has a switch to enable "IDE mode" or "No boot". You can install two mod updates for Paragon GPT Loader 8.0.1.0 later but do not install the base mod as it will most likely cause BSOD. http://hardwarefetish.com/777-paragon-gpt-loader-3 http://hardwarefetish.com/612-gpt_loader-sys-revisited-file-read-problem http://hardwarefetish.com/524-paragon-gpt_loadersys-bsod-analysis-and-fix (on this website there are only patches, there is no full version) You don't use the fork version 8.0.1.2 this can cause BSOD. *Update: -In some circumstances when I open the Windows XP Disk Manager the partition disappears immediately, without performing any additional operation. To prevent losing the partitions I suggest making a partition table copy with Eassos DiskGenius from Windows Seven or higher in the menu Disk>Backup Partition Table. If you do not have a partition table copy, you can recover it from Windows Seven with this same program from the menu Tools>Search for Partitions , choosing the Whole Disk option and in the search, clicking on "Reserve" when the appropriate partitions appear. The pity is that we need Windows Vista or higher or use a bootable disc with a program, since once the partitions are lost in XP the hard disk only shows a capacity of 1493 Gb, so we need to boot an operating system that recognizes the real disk capacity. B - With the 2003 Windows drivers on USB ports until 16 Tb ¡¡¡CAUTION!!! This driver should only be installed for use with +2TB hard drives connected to a USB port using a SATA to USB adapter that translates logical sectors from 512 bytes to 4096 bytes. This allows 2^32 (4,294,967,296) sectors to hold 16 TiB of data as each one measures 4096 bytes instead of 512 bytes. +2TiB hard disks connected to the SATA port with Windows 2003 drivers cause data corruption when writing to sectors above 2^32 (4,294,967,296) this is 2TiB. -See the particularities of Paragon GPT Loader driver if you finally install the hard disks in the SATA port. Both drivers can coexist at the same time. Windows 2003 for USB and Paragon for SATA. -No problems have been reported with PAE and Windows 2003 drivers. Step 1 - From another operating system copy the Windows 2003 drivers replacing the current XP. "Partmgr.sys" copy in the folder: Windows \ System32 \ dllcache "Disk.sys" and "Partmgr.sys" copy in the folder: Windows \ System32 \ drivers Any version of Windows 2003 drivers works both v. 5.2.3790.3959 (W2003 SP2) as v. 5.2.3790.1830 (W2003 SP1). Both files have = number of bytes, only change version number. The files are valid for all languages (at least work with XP English & XP Spanish). Check that there are no more old versions in other folders such as \ Windows \ Lastgoods If these files are sought with the Windows XP search engine these do not appear, since these are special system files. Use an alternative search engine like "File Finder." Note: To copy them from the operating system itself, both files would have to be glued very quickly in both folders and then update the folder view checking that version 5.2 has been fixed Ideally, paste the files on the hard drive from another operating system, since we will not be able to perform step 2 from Windows XP itself. You can also try to deactivate Windows file protection: -To disable the Windows files protection, activate SFCdisable in the registry: HKLM \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon SFCDisable = 1 Restart Windows and copy the files. -Then activate the protection again: SFCdisable = 0 And restart Windows. Step 2 - Copy the "disk.sys" file of Windows 2003 inside the "sp3.cab" file that is in \ windows \ driver cache \ i386 with the Windows CAB file packaging" tool called "iexpress.exe" (Windows Cabinet) that is in \ Windows \ System32 Extract sp3.CAB: - Extract the files that sp3.CAB contains with Winrar or with 7zip or with IExpress (slower) in a folder whose name does not match "SP3" the name of the file to be created, since if it does not let it create it when packaging. - Paste the "Disk.Sys" file of Windows 2003 replacing the XP file. Packing sp3.CAB: - Go to start+run and write "iexpress". - In the menu choose «Create New Self Extraction Directive File» and press next. - In the menu choose «Create Compressed Files Only (Active X Installs)» and press next. - Add the files contained in the "ADD" folder. - To record the file to choose the location to examine, but the file.CAB is created in C: \ Documents and Settings \ User - Choose a name of 8 characters. Note: If the same file name is chosen as the folder enters the folder instead of saving it. - Mark allow compressed files to have a long name in "Store Files Using Long File Name Inside Package", leaving the other white box (Create Fixed Sice Cab File (s)). - Optionally save compilation. Note: If the same name as the folder has been chosen, the .CAB file is created in C:\Documents and Settings\user because the location is automatically blanked. Note: If step 2 is not done, then Windows XP stops booting when a new USB stick is installed. Since to install its drivers the original version of "disk.sys" of Windows XP is restored. There is no problem if you install the pen with the Windows XP drivers from before step 1 and then recopy the Windows 2003 drivers. At least until you reinsert a new pen. https://msfn.org/board/topic/183225-windows-xp-does-not-start-after-entering-kingston-usb-pencil/#comment-1210203 Step 3 - Star Windows XP The first time Windows XP starts with the new files takes several minutes. Be patient and wait. Note: Tested in Windows 2000, this gives blue screenshot with MBR discs, you can't access the Boot Device. Previous Post 2023-07-22 Edit: This is no longer necessary. This bug is present in previous versions of the Paragon GPT Loader driver 8.0.1.0. If you have the previous version of this same driver you should apply this fix only if your boot drive is FAT32. Remember that you should not use a version of Paragon other than 8.0.1.0 Error correction: Any version of the Paragon GPT Loader driver that we install, be it the original, the HFS or the modified fork, contains an error that will cause us to suffer a blue screen when rebooting the system, at least if we have FAT32 on the Windows XP boot partition . This is because the driver file name "gpt_loader.sys" contains 10 characters instead of 8. It is installed in the \WINDOWS\system32\drivers directory. To solve it, we will modify the Windows registry as soon as we install it and before restarting the system. Go to start + run, type "regedit" and search HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gpt_loader Here change the value of ImagePath which says: system32\DRIVERS\gpt_loader.sys by system32\DRIVERS\GPT_LO~1.SYS and then reboot. Problem solved. Fork version In addition to the official version there is a fork that fixes the bugs of Paragon GPT 8.0.1.0. The current fork version is 8.0.1.2 On their website they do not give the full version 8.0.1.2 (despite the fact that it exists on other websites). And they do legally give the patches to correct the official version 8.0.1.0 http://hardwarefetish.com/777-paragon-gpt-loader-3 (on this website there are only patches, there is no full version) How to install the fork 1 - Unzip 2 - Right click on the .inf file 3 - Install To uninstall the fork we need to install some official version and then uninstall it. But, as far as I've checked, currently it's better to install Paragon HFS for Win v.10.5.0.95 which contains the 10.5.0.95 driver.

Hello @beansmuggler! That's Min2Tray, an open source program to minimize program windows to the systray. The installed hook is needed for keyboard shortcuts. Add it to your exclusion list or whitelist! Read my documentation! Min2Tray is very well known and totally harmless. Google it! And, it is definitely not this: Cheers, AstroSkipper PS: If you like my project or my program package, please, support it by liking or up-voting!

Hello @cnfcomps! Thanks for your nice reply! BTW, it was not only a collecting of information about restoring MU system in Windows XP but own work and solutions, too, which were very time-consuming. An Autostart option will be a feature in one of the next releases if I can see a real interest in my already published program package. An author lives from the feedback of the users, and the feedback on my project ProxHTTPSProxy's PopMenu TLS 1.3 3V3 is rather modest. Only few comments and reactions on my program package itself! You're welcome! Cheers, AstroSkipper PS: If you like my project or my program package, please, support it by liking or up-voting!

Update notification! The Root Certificates have been updated and are now from 23-08-2022. Here is a screenshot: My self-created, offline Root Certificate Updaters will be updated as soon as possible. Cheers, AstroSkipper

The computer has to work and do its job. If not, you have to solve it! But please, do not talk about it! It's boring. Ever experienced this?

Same here in Germany. Mina is the first name of a female. But in Egypt, it is vice versa! Right! Or, you can also use the TLS 1.3 proxy locally. The TLS 1.3 proxy and thus also my program package makes it possible to establish connections to servers or generally to the Internet via the TLS 1.3 protocol (and all other TLS protocols which was already done with previous releases) in Windows XP even independently of browsers, which was not possible before. You can test my program package with the old Firefox ESR 52.9.0. Here is a link, you still have to choose your language: https://ftp.mozilla.org/pub/firefox/releases/52.9.0esr/win32/ And, in any case, with the Internet Explorer 8, too. Some email programs and others also need such a proxy nowadays. All information about these proxies can be found in my article "ProxHTTPSProxy and HTTPSProxy in Windows XP for future use" in the first post of this thread. This article will be updated when time is available. My program package ProxHTTPSProxy's PopMenu TLS 1.3 3V3 is fully documented inside its archive.

And, just to be clear, I am not a Bavarian!

Right! The probability of success to talk to a female person in this forum converges towards zero. A pity, actually!

Hello @SC7601! That's correct! I would be very pleased if I got feedback from users who can test my program package in a real installation (no VM) of Windows XP on a period-correct hardware. BTW, my Windows XP computer is equipped with a Pentium 4 2.8 GHz Northwood single core CPU and only 1.5 GB SD-RAM. No SSD, no SATA but IDE hard disks, and the graphic card is NVIDIA 6200 AGP 4x. You see, we both are running Windows XP on a Pentium 4. You do not need to use old Chrome browsers. In the MSFN forum, we have a lot of browsers compatible with Windows XP and quite recent to surf the web nowadays. Here is the link to the post of my program package: And here is the link to the forum with topics referring to browsers in Windows XP: https://msfn.org/board/forum/201-browsers-working-on-older-nt-family-oses/ If you have any questions, do not hesitate to ask me! Greetings from Germany, AstroSkipper

OT, too! This morning I looked at a brochure from ALDI and there, in the online shop, they offer a gamer laptop with 1 TB SSD, 32 GB RAM, Intel Core i7 12700H and NVIDIA Geforce 3070 Ti laptop GPU with 8 GB GDDR6 VRAM for 2299.- €. No neighbourhood of 1000 Euros! ALDI?

Yes, and that was the reason why I replied with No. I will stay on my old, slow, and beloved computer, of course. More recent hardware, more recent OS which means no Windows XP on that computer. Unfortunately, that is exactly the real problem. On new hardware, old OSes are nonsense. Old OSes can't really handle new hardware which they are not developed for. That's the truth! Here in this forum are a lot of people trying to install Windows XP, or much worse, Windows 98, on a brand new machine. Nonsense, unfortunately! But, each to his own, a second time today! We all can do what we want to. Even if it doesn't make any sense at all!