Leaderboard

This is the original version of Teardown, which uses a Windows 10 exclusive API function, SetProcessDpiAwarenessContext, running on Windows Vista with an upcoming update to user32.dll: Later versions of the game no longer use this function and as such will work normally on Windows 7, 8.x and 99.9% sure, Vista, though I have no proper way of testing DX11 games on Vista due to the age of my GPU. There are also other games known to use this function, so even though the developers of Teardown realized the demand for their games on older platforms, others may take a different attitude and force users onto the latest versions of Windows 10 to use their products. So, this will allow Vista/7/8.1 users to be prepared for such a future event. Since some interest has been shown in donations for my work, I have set up a method for users to contribute financially for this and some of my other works: https://www.patreon.com/win32

I forgot most of the update numbers too since I made a WildBill update collection that includes everything. I install SP5, Update Rollup 2, and the WildBill Update Collection on my test computer. Have you been able to replicate the issues I have on my test PC and do you have any idea what could be causing these issues?

You should direct some (most) of this displeasement to lazy web devs that insist on using bloated JS frameworks for everything on a simple page.

I don't use any sync service so I'm not familiar with it, but afaik you can create your own sync-v1 server and change services.sync.serverURL and services.sync.statusURL in about:config and point to your sync server address.

Death Stranding is Top 3 greatest games I've ever played and made the nightmare of Win 10 worth it, fight me.

My specs: Intel i5 8250U 8GB RAM 250GB SSD Windows Vista Home Premium x64 (German) I started using Vista in 2008, after our XP PC refused to start. Back then, I did not know that it was a driver error which led to the crash and not a hardware error (Nowadays I am the PC specialist in our family lol), so we bought a new PC. I cant remeber the processor but I know it had 2GB RAM and ran Business x32. Vista was very nice, we used it till 2013, before we upgraded to Windows 7. I remember that Vista did not support IE10/11 and Office 2013, which were the two major problems with it. We didnt use Windows 7 for a long time (I think only till 2014). In 2015 we upgraded to Windows 8.1, which was very fast in comparison to any other OS I had used before. When Windows 10 came out, our PC couldnt handle, so we made a fresh Clean Install of 8.1 and even nowadays it still runs veryy fine (we upgraded the RAM to 4GB)

Thanks for the post RainyShadow, hope you eventually finish the game. Make time gosh darn it, life is short. For me it's been fun to finish some games i've waited too long to play. Some are more fun that others, of course. Some anti-climactic, my life would not have been any less complete without them, did that make sense :) Recently rebuilt and thoroughly cleaned an old tower that sweetly runs Windows XP and Devuan Ascii (Debian 9). The hardware is a circa 2001 Giga-Byte motherboard, 800 MHz Intel Celeron Coppermine processor, 512 MB RAM, Intel i810 graphics, AC'97 sound, D-Link ethernet. If the Windows XP install dies hope to convert it to Windows 98. IIRC the system requirements for Windows XP were decent for older hardware. Huge jump in minimum system requirements with Vista onward, don't have the hardware for any of these more modern Windows OS'. Probably been over two years since this hardware was rebuilt. Want to do it every year but never enough time, guess it depends on the computing environment and runtime. If possible try to complete a rebuild in one session, makes it much easier to remember screws and connections, etc when re-assembling. With a decent work area and basic tools a thorough job takes 1-2 hours, especially if the power supply is opened and the processor is re-seated. The system has performed well for many years, nothing special with the rebuild. Highly recommend anyone with old hardware always clean out the power supply unit. Quite simple, don't need to worry about voiding a warranty. Just four screws to remove the power supply unit from the tower, another two screws usually opens up the actual power supply. Vacuum brush or blow out the dust to restore air flow and proper cooling. Dust is the enemy as it restricts airflow and acts as an insulator which contributes to overheating, hardware death and is a fire hazard. Ensure the fan blades are clean and turn freely, occasionally a half-drop of bearing oil if the fan is noisy or problematic. One of the main board capacitors is beginning to leak, will keep an eye on it. Two of the 4 pin peripheral power cable connectors from the power supply no longer fit tightly when connected to hard drives. This can lead to problems if the drive loses power during runtime due to thermal expansion, including data loss. This was improved by inserting a small jewelers screwdriver shaft between the plastic plug and the metal prong to re-crimp the prong tighter. Now it fits more snuggly when plugged into a hard drive. http://www.playtool.com/pages/psuconnectors/connectors.html#peripheral Everything was disconnected, inspected, cleaned and re-seated. Noticed one data cable had a cockeyed connection to a hard drive, the pins were inspected and nothing was bent, oopsy now fixed. There was some corrosion on one of the two RAM module contacts, cleaned with a cotton cloth and Isopropyl alcohol. New thermal paste for the processor's heat sink. The laser on the CD drive was cleaned last time and does not have issues so it was left alone. To jog my memory a sticky was placed on the tower with the rebuild date.

Provided you 1) use rloew's PATCHATA to update ESDI_506.PDR on your Win98 installation (and your intended hardware does in fact support 48-bit LBA), or 2) keep your 98 partition limited to ~120GB at the beginning of the drive, then no, there is no problem using the 250GB drive. If the larger disk is connected via SATA, you will most likely also need rloew's SATA patch. re: 32GB limit; This is totally nonexistent. Windows XP (2K as well?) and later impose a false limitation and prevent you from creating a FAT32 partition larger than 32GB, but they manage larger FAT32 partitions created by other software/OS'es just fine. No such false limitation exists under 9x. I believe the origin of this falsehood can be traced back to an old KB article that claimed that the size of a FAT32 volume under Windows 95 was limited to 32GB.. but this was never true to begin with.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20201114-355db4de-uxp-4aeaea919-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20201114-355db4de-uxp-4aeaea919-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom-older * 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-20201114-id-eed0566-uxp-4aeaea919-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20201114-id-eed0566-ia-41157bf-uxp-4aeaea919-xpmod.7z 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.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201114-ffb32e0-uxp-4aeaea919-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201114-ffb32e0-uxp-4aeaea919-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.7.win32-git-20201114-ffb32e0-uxp-4aeaea919-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.2a1.win32-git-20201114-fcd19efc9-uxp-4aeaea919-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201114-fcd19efc9-uxp-4aeaea919-xpmod.7z Official UXP changes since my last build: - Issue #1677 - Part 3: Create shim definitions for V8-specific code in new regexp implementation (cb0208163) - Issue #1677 - Part 4: Implement shim for regexp (77746f1d9) - Issue #1677 - Part 5: "Simplify" regexp re-import process (and re-import from later revision) (51468e998) - Issue #1677 - Part 6: Implement NativeRegExpMacroAssembler for new regexp import based on irregexp/NativeRegExpMacroAssembler.cpp (c732425e1) - Issue #1677 - Part 7: Add unicode/uniset.h to check_spidermonkey_style.py for some reason (74ebcea40) - Bug 1328948 - Add is(), as() to Cell. (4694c6096) - Bug 1466909 - Use AddLvalueReference for UniquePtr's operator*(). (e8a6ee355) - Issue #1679 - Part 1: First pass account for some of the refactoring differences in regexp-shim.h (0ba1d49ae) - Issue #1679 - Part 2: Some small issues to address buildability. (4aeaea919) No official Basilisk changes since my last build. No official Pale-Moon changes since my last build.

someone over there https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/ made a WU patcher to enable its function again. you can get it from here https://1drv.ms/u/s!AubsH71V5bOkkmIPXEQi0fbX_45f?e=5KEwYg i canconfirm that it works for me.

I wouldn't go quite that far. If you were Tim Cook you wouldn't be in pursuit of patching an OS from 2007, you'd be too preoccupied depreciating one from 2017 Fair enough, I didn't take into account the x86/x64 subsystems. It's easy to forget x64 NT 6.x is like 2 OSes.

Do you want to know how to easily integrate the final version of IE8 (Internet Explorer 8) with nLite? You've come to the right place. 1. Download the IE8 addon here: http://www.winaddons.com/internet-explorer-80/ 2. Insert the addon file you downloaded into the hotfixes page of nLite. 3. Run the nLite process and enjoy. note: there's no need to slipstream IE7 first, this works fine without it. Also, I highly recommend that you slipstream XP SP3 (Service Pack 3) first. I'm not sure if this works with the x64 version of XP, maybe someone who knows can post a comment.