Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250125-3219d2d-uxp-789327be17-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250125-3219d2d-uxp-789327be17-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-20250125-3219d2d-uxp-789327be17-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-20250125-d849524bd-uxp-789327be17-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250125-d849524bd-uxp-789327be17-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250125-d849524bd-uxp-789327be17-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250125-d849524bd-uxp-789327be17-xpmod.7z Official UXP changes picked since my last build: - [network] Don't try to use non-existing connections. (624ff30bfc) - Issue #2676 - Don't keep AbortController alive for AbortSignal (949e3f0ac6) - Issue #2676 - Implement AbortSignal.abort() (9fa4b6fd5d) - Issue #2676 - Implement AbortSignal.timeout() (14c84e22a9) - Issue #2678 - Don't use QI to canonicalize nsISupports pointers in the purple buffer. (9f4fe4275c) - Issue #2678 - Switch DOMProxyHandler::EnsureExpandoObject to using normal wrapper preservation instead of RegisterDOMExpandoObject. (45bb4cb8b4) - Issue #2678 - Remove the DOM proxy expando object hashtable in xpconnect. (32da3f4de4) - Issue #2678 - Stop using EnsureExpandoObject in codegen code when we just want to preserver the wrapper for a DOM proxy. (c9c941f321) - Issue #2678 - Remove now-unnecessary ClearExternalRefsForWrapperRelease. (0121aefb61) - Issue #2678 - Avoid QIing for NoteXPCOMRoot. (38daeffb9b) - Issue #2678 - Optimize inherited cycle-collectible QueryInterface() implementations for nsCycleCollectionISupports; (85aa4cb31e) - Issue #2678 - Clean up some uses of the table-to-map segue. (33a120eb9f) - Issue #2678 - Define a new macro for CC isupports. (5d82de9eb6) - Issue #2678 - Use a new macro for CC isupports in some locations. (c37e68d59f) - Issue #2678 - Default NS_INTERFACE_TABLE_HEAD_CYCLE_COLLECTION_INHERITED to NS_ERROR_FAILURE (33140a9b1b) - Issue #2678 - Make QIing to a few often-used CCed classes faster. (85f8f23a23) - Issue #2678 - Remove unnecessary second QI for nsCycleCollectionISupports. (9464d0ed6d) - Issue #2678 - Remove NS_INTERFACE_MAP_BEGIN_CYCLE_COLLECTION_INHERITED (139e7a7ac6) - Issue #2681 - unprefix :-moz-modal-dialog (d9b107f32f) - Issue #2681 - Expose `:modal` to content. (147713a6ac) - No issue - Turn worker runnable assertion into something harmless in debug builds (41eb02d1e1) - Issue #1765 - Follow-Up: For parsing calc() in non-hue component of hsl/a(), explicitly expect <percentage> values (2e3953399a) - Issue #2078 - Follow-up: Don't try to resolve ancestor link elements when matching for Has*DependentStyle (77728935ef) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes since my last build: - Issue #2678 - addendum to rev 139e7a7a (f67e22d3f0) 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.

The card I ordered arrived, and it turned out exactly the same as the ones I tried before! It's still an Asmedia 106x chipset card of course. D'oh! I've now ordered this one, which has the magic mode switch. I'll let you all know how that goes!

Done, done and doner.

You might want to consider a newer browser, 109 is simply too dangerous to use any further. Chromium's latest beta is at 135, a mesmerising difference. Stable is at v.134. https://www.techspot.com/downloads/4936-chromium.html There are only two rather serious options left for Vista/7/8. I don't suggest you the China made CatsXP, it's mostly for extreme riders like me. But Supermium is made by a guy from Canada, I'd assume it's safe to try, especially if you're that much dedicated to an OS many years out of support. From what we saw earlier, uBlock Origin can simply discard v.109 soon.

Eassos DiskGenius (formerly PartitionGuru) has been my favourite partition manager for years. As far as I know, the last XP compatible version is 5.5.0.1488 from 2023 and works very well under Windows XP. Many, many features, and you get very detailed information about your drives. It is even able to create images of partitions. In any case, I no longer allow any other partition tools to access my hard drives. And I tried a lot of them in the past.

Thanks, from the bottom of my heart. You'll never regret skipping that pile of -rem- No. it's not. There was some info about uBlock not working in CatsXP 132, but no problems on Win10. I tried myself, and it acts weird on 7 and Vista. Some ads aren't blocked, the browser is rather heavy on start.

I think such language use and especially fecal language needs urgent moderation. After all, we are not in the USA.

@egrabrych So that patch is not enough now, make a new, look this is about "picture in picture".

On the Toshiba HDWD260 6TB hard drive I created 3 GPT partitions and connected this from various operating systems as SATA and USB with different adapters. Then I repeated the process as an MBR disk with another 3 partitions until I completed the 6TB. Almost any system used reports different values for the logical sector size and the physical sector size. How can Windows Seven x64 report a 4096 bytes physical sector while Windows XP x86 reports 512 bytes? This does not seem to represent any change in the number of sectors Windows can read in MBR but it does in GPT. Also the Logilink adapter reports a 4096 bytes logical sector size while any Windows version can work with MBR +2TiB. How can we trick Windows XP into reporting that our GPT disk has a logical sector size = 4096 bytes? BIOS firmware modification? Firmware modification hard disk? (some manufacturers provide tools) create a bootloader, perhaps like the Paragon driver does? USB firmware modification? GPT GPT Paragon 8.0.1.0 SATA XP -4 GiB RAM Logical sector: 512 bytes Physical sector: 512 bytes first partition GPT Paragon 8.0.1.0 SATA XP 5 GiB RAM with PAE Logical sector: 512 bytes Physical sector: 512 bytes first partition GPT Windows Seven x64 5 GiB RAM Logical sector: 512 bytes Physical sector: 4096 bytes MBR MBR JMcrom USB on Windows Seven x64 Logical sector: 512 bytes Physical sector: 4096 bytes MBR Logilink USB on Windows Seven x64 Logical sector: 4096 bytes Physical sector: 4096 bytes MBR SATA on Windows Seven x64 Logical sector: 512 bytes Physical sector: 4096 bytes

TCHAN TCHAN TCHAN, MYSTERY ABOUT TO BE SOLVED. I think it is ready for... FINAL JUDGMENT!!!! THE CLUES 1- From Italy @silverni reports that the limit with Windows 2003 drivers is 2 TiB. Also reports from the Dominican Republic @realisty 2- From the Dominican Republic @realisty reports that Paragon drivers do not exceed the 2TiB limit using PAE. Also reports from Italy @Andalu 3- From Italy @jaclaz reports that some USB adapters modify the physical sector information reporting that this is 4096 bytes instead of 512 bytes. He also reports that actually he has not yet seen a SSD that has the larger size a 4096 byte sector size and that disks with physical sector 4096 he thinks only exist from 8 Tb. He also reports that Paragon drivers do not work via USB. 4- From Andorra @Milkinis reports that Microsoft officially only supports disks with 4K physical sector since Windows Eight. 5- From the United Kingdom @Dave-H reports that the physical sector of his Seagate ST3000 disk has 512 bytes of physical sector. 6- From Spain @Cixert reports that his Seagate ST3000 disk has 4096 bytes of physical sector in contradiction with the same unit that @Dave-H exposes. @Cixert also reports that the error does not occur when the disk exceeds 2 TiB, but rather when writing to logical sectors located above those 2 TiB, even if the disk is empty. That is what we will see next and that I think is the key to solving the criminal case. According to the device that I am using to connect the hard disk, it reports a different size of physical sector and logical sector. As a defense we will call @Bill_Gates Oops, he's not on the forum? He must be using a pseudonym Then upload screenshots for this Toshiba HDWD260 disk... *There may be some data transcribed incorrectly, if so I will correct it in the next few hours. AS GPT DISK Logilink USB adapter on any system: Logical sector: 4096 bytes Physical sector: 4096 bytes JMcrom USB adapter on Windows Seven: Logical sector: 512 bytes Physical sector: 4096 bytes JMcrom USB adapter on Windows XP: Logical sector: ???? Physical sector: ???? I will confirm with w2003 drivers SATA on Windows XP 32 bits with Paragon Driver: Logical sector: 512 bytes Physical sector: 512 bytes SATA on Windows Seven x64 with native driver: Logical sector: 512 bytes Physical sector: 4096 bytes AS MBR DISK Logilink USB adapter on any system: Logical sector: 4096 bytes Physical sector: 4096 bytes SATA on Windows XP 32 bits: -Does not work. I will try to find some value. SATA on Windows Seven x64 with native driver: Logical sector: 512 bytes Physical sector: 4096 bytes It seems that the solution is to find a way to make Windows report that the hard drive has a logical sector size of 4096 bytes, since SATA is reporting that the hard drive on Windows Seven x64 has a physical sector size of 4096 bytes and yet MBR with +2 TiB does not work with SATA, only with the Logilink adapter that reports a logical sector of 4096 bytes. There are still many mysteries to be solved that surely someone knows but we are not getting all the information. Why are some disks limited to 4 TB? What I still don't understand is how the Paragon 8.0.1.0 driver works with SATA +2TiB drives while other versions of this driver don't and Windows 2003 drivers don't either. I think that if we try to solve this we are on the right track. Thanks to all the necessary contributions made by all the users in the thread... @RainyShadow @ED_Sln @WINUSERUntil2023 @Zollex @patcat88 @j7n @tekkaman @Houfino @Saxon @Dixel @D.Draker @Jotnar @mina7601 @dmiranda @TSNH @pappyN4 @aoresteen @user57@roytam1@Outbreaker @Multibooter Remember that the mystery is partially solved and we can read SATA +2TiB disks only with the Paragon 8.0.1.0 driver without PAE. Other versions do not work.

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-20250125-a94d1a733-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250125-a94d1a733-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: [network] Don't try to use non-existing connections. (624ff30b) (fa638329c) - import from UXP: Issue #2676 - Don't keep AbortController alive for AbortSignal (949e3f0a) (295237469) - import from UXP: Issue #2676 - Implement AbortSignal.abort() (9fa4b6fd) (e292cff9d) - import from UXP: Issue #2676 - Implement AbortSignal.timeout() (14c84e22) (2ccb1cf04) - import from UXP: Issue #2678 - Don't use QI to canonicalize nsISupports pointers in the purple buffer. (9f4fe427) (2f8f872a1) - ported from UXP: Issue #2678 - Switch DOMProxyHandler::EnsureExpandoObject to using normal wrapper preservation instead of RegisterDOMExpandoObject. (45bb4cb8) (71fd0ba60) - import from UXP: Issue #2678 - Remove the DOM proxy expando object hashtable in xpconnect. (32da3f4d) (c8236aa01) - import from UXP: Issue #2678 - Stop using EnsureExpandoObject in codegen code when we just want to preserver the wrapper for a DOM proxy. (c9c941f3) (985fb0dbb) - import from UXP: Issue #2678 - Remove now-unnecessary ClearExternalRefsForWrapperRelease. (0121aefb) (9f5ad3546) - import from UXP: Issue #2678 - Avoid QIing for NoteXPCOMRoot. (38daeffb) (e4ff8ad59) - import from UXP: Issue #2678 - Optimize inherited cycle-collectible QueryInterface() implementations for nsCycleCollectionISupports; (85aa4cb3) (687008863) - import from UXP: Issue #2678 - Clean up some uses of the table-to-map segue. (33a120eb) (b118aaf0c) - import from UXP: Issue #2678 - Define a new macro for CC isupports. (5d82de9e) (ebac6fdea) - import from UXP: Issue #2678 - Use a new macro for CC isupports in some locations. (c37e68d5) (b1f3fb7c0) - import from UXP: Issue #2678 - Default NS_INTERFACE_TABLE_HEAD_CYCLE_COLLECTION_INHERITED to NS_ERROR_FAILURE (33140a9b) (8fa4681bd) - import from UXP: Issue #2678 - Make QIing to a few often-used CCed classes faster. (85f8f23a) (b808a6054) - import from UXP: Issue #2678 - Remove unnecessary second QI for nsCycleCollectionISupports. (9464d0ed) (ffc47a0cf) - ported from UXP: Issue #2678 - Remove NS_INTERFACE_MAP_BEGIN_CYCLE_COLLECTION_INHERITED (139e7a7a) (7bc855bb7) - import from UXP: Issue #2681 - unprefix :-moz-modal-dialog and expose `:modal` to content. (d9b107f3+147713a6) (85d2472c0) - import from UXP: No issue - Turn worker runnable assertion into something harmless in debug builds (41eb02d1) (699ead5df) - ported from UXP: Issue #1765 - Follow-Up: For parsing calc() in non-hue component of hsl/a(), explicitly expect <percentage> values (2e395339) (6114c9ea9) - import from UXP: Issue #2078 - Follow-up: Don't try to resolve ancestor link elements when matching for Has*DependentStyle (77728935) (a94d1a733)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20250125-7bda12e7-uxp-789327be17-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20250125-7bda12e7-uxp-789327be17-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-20250125-id-656ea98-uxp-789327be17-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20250125-id-656ea98-ia-93af9a0-uxp-789327be17-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

The new 68.14.6 version is complete https://codeberg.org/Theodor2/Mypal68/releases

A very nice picture, regardless of the size. When I added mine, I did upload a jpeg, all was fine. Could be the new limit, we'd have to wait for an official response.

On my Dell D620 Win 98 se system, I have not encountered any issues due to the driver. I also played a bunch of music files using the vlc 0.8.4 edition and did not encounter any crashes. I did not try a lot of games but I did hear the starting sounds from the Unreal Tournament before a crash. I generally do not intend to game on the laptop but I think the crashes might have to do with things other than the driver.(My installation is quite minimal and I run the system using a modern SSD. I only applied the RLoew PATCHMEM for the 4gb RAM that is there on the laptop) Volume Control can be achieved in multiple ways. The volume UP key on my Dell D620 works as does the VLC volume cone slider. The WAVEOUT.EXE can also be used if I am not mistaken. In my opinion the HDA driver along with the universal VBE graphics driver is the way to go for anyone attempting a Win 98 install on newer hardware configurations.

The OP asks strictly about Windows 7. Did you notice they behave differently?

I assume you rather have a problem with a Windows XP SP3 essential security update since you didn't specify which update you are referring to. This, however, means that no one can help you.

How to disassemble. https://www.youtube.com/watch?v=HuhT6fo7GsY

Look for topics like this, often posted on Reddit, too. https://community.wd.com/t/what-kind-of-hard-drive-is-inside-my-book-wd-elements-desktop-8tb/235378 or this https://forums.sandisk.com/t/which-drives-are-inside-the-wd-8tb-my-book-desktop/264819

You're very welcome! As an advice to a friend, there's a much higher chance to get a decent HDD inside of My Book, and then simply throw the box away. It will save you money. It's usually cheaper than buying a retail dive. But like I said, please do a research, people oftenly post photos of what they get inside of that box.

Since you replied to @ItCoder, I assume that you are using his proxy server method for restoring MU/AU. Your image shows the error code 0x8024400A which is listed as SUS_E_PT_SOAPCLIENT_PARSE - failed in parsing response. This error can also be found in your uploaded WindowsUpdate.log. A very short research led to the following: The error 0x8024400A often occurs in connection with a Windows Server Update Services (WSUS). The reason for this may be that the WSUS configuration was not carried out correctly or the settings were not distributed correctly via the global group policy. Check the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate Additionally, you can use the WSUSClientDiagTool tool for checking your WSUS settings. BTW, I personally have never been using @ItCoder's proxy server method. Therefore, I can't say more about it. Cheers, AstroSkipper

Then you should aligned it using this function in MiniTool Partition Wizard. Click in Minitool with right mouse button on your 240 SSD, press "Align" (sorry my Minitool use not English interface, so i don't know how exactly this options called in English version) and then press in left upper corner of program button "Apply". Also pay attention of info and warnings that program give to you (i mean read it with attention). It means that Cluster is 4K, it's just not aligned. In my case it's also 8 sectors per cluster, just my partitions are aligned. I guess it's do both. What a weird question. In Windows misalignment happens when you format drive with old windows before Vista. Your cluster is 4K, just it's start in wrong place - meaning program cluster of file system are not Coincides with physical cluster on HDD\SSD.

Which method are you referring to? The patch + proxy method uses the TLS 1.2 or TLS 1.3 ProxHTTPSProxy which is needed to connect to MU via Internet Explorer. The service Legacy Update provides their own client software which means no additional proxy is needed. Here is my report from August 2024 when testing the Legacy Update service: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1270925 One thing is clear. Today, most connections require at least the TLS 1.2 protocol. Please, first read about the methods before asking! All is described in detail.

Actually it was 15 years ago. It is a minor problem for windows XP cause by default XP will format with cluster size of 512 bytes, and also not aligned to disk 4K advanced format sectors because: HDD will suffer speed penalty from wrong cluster size and misalignment much more then SSD. But if your HDD and SSD correctly formatted with 4K cluster and aligned correctly - there will be normal fast work with winXP. I use with winXP both HDD and SSD that are 4K Advanced Format devices - i create partitions on them using program mentioned below - program that works under windows XP and give ability, when formatting disk\partition to set 4K cluster size and correct alignment. There is a method to format disk in 4K with command prompt in winXP, but i never used it and instead use 2 programs to check alignment and format in 4K with correct alignment. The first program is MiniTool Partition Wizard Server Edition 7.8, - it can format drive correctly with 4K size of cluster and set correct alignment, and also can aligned correctly already existing partition. If you want this program in Server Edition write me Personal Message i will give you a link. The Home Edition is free and can be downloaded via wayback machine - http://web.archive.org/web/20140904082151/https://www.partitionwizard.com/download/pwhe7.exe The second program is Disk Alignment Test - very simple program, it just checks are your partitions and disks correctly aligned. It is free and you can download it via wayback machine http://web.archive.org/web/20160221100017/http://diskat.net/