Leaderboard

@jacer4 Here is the new link for this file, good luck Dietmar https://ufile.io/p07xouxv

You can get the text back on Firefox 72 before whatever updated in the forum that broke compatibility, and Iron 109. For the MSFN links, when you paste the link, and the preview comes up, click the black banner that says to show only link. It seems that sometimes the preview option for forum links doesn't work.

Possible. But I have ran both on real hardware on old laptop and from VM on fairly-modern hardware. I get the same results in both - Supermium is the only one pegging at 100% for 2 to 4 minutes, dropping to 2% for 10 seconds, then pegging again for another 2 to 4 minutes. I can only speak towards what I witness - and that is that Thorium works better, much MUCH better, on my hardware. Supermium can NOT be ran from a VM, the 100% CPU is far FAR worse when ran from a VM. But I suppose that's okay, we should be targeting real hardware.

The website of the largest Russian social network has stopped opening. Returns an error: https://ibb.co/XS2StnJ

NTLDR is missing message comes from the OS itself, so this means it can see the disk. This message means that the BIOS did the hand-off to the disk, read the boot .ini and found where the OS is, but the path did not resolve. So the first thing to do is to check the boot .ini and see what is in there. One example of a situation where a BIOS update can cause this is if the OS volume where Windows is located had its drive letter change. Such as if you are using multiple hard disk and Windows is in D: a BIOS change could cause the re-enumeration of volumes and D: is now E:, etc. If it is a situation where your OS was on C: but now that volume is a different letter, then it may be better off reverting that BIOS version again as the Windows installation could have problems with the drive letter changing. NOTE: The forum will not let you type in the term I put in bold above without a space. You will get an error if you try to submit a post without the space. EDIT: I'd also like to report that while the retroweb (site linked earlier) is good for information, I find their software to be lacking. That site does not take into account board revisions such as is common with Microstar boards which means this issue will likely exist for other brands. That would be a reason why a BIOS update may fail. Also I've yet to find any drivers on there that have worked. For example, ones that are marked for Windows 95 requiring different OS like XP, or 32bit options are 64bit versions, etc.

360Chrome v13.5 Build 1030 Redux I inadvertently corrupted my original Build 1030 series when working on Builds 2022 and 2036 so this is starting brand new with several lessons learned from later versions, including 2044. I've always much preferred Build 1030 over anything "newer". They all technically use the same v86 Chromium engine "under the hood". Download link -- https://www.dropbox.com/scl/fi/d5sjhgshdrjtntd06iecb/360ChromePortable_13.5.1030_Redux_1_ungoogled_MSFN.zip?rlkey=etzsfb8m9z1kljxj10jwhw9wv&dl=1