Leaderboard

This page now provide the SHA-2 signed dotnetfx35.exe (it's signed since July 2021, but the server timestamp for the file is February 2022) https://dotnet.microsoft.com/en-us/download/dotnet-framework/net35-sp1 they also signed the inner installers (exe, msi, msp..), but the content is still the same old dotnetfx35.exe

That's fine. But at first read what this fix does and create an image of your system partition only in case the fix fails and has harmed your system.

I come back again for some updates. The patches provided by _Smoker and me are for different versions of IO.SYS. It is confusing, but essentially the same thing. The patch knocks out a far call instruction to a procedure that install handlers to INT 15H AH=87H/88H and AX=E801, also INT 2FH AX=4300H / 4310H and 4309H, also the source of some GDT entries. This will make HIMEMX.EXE to work. However, if some one has tried our way of patching, some side effects will be found. like wrong mem command output, system hangs in safe mode, running to massive non-sense output in loading some applications. Also, to start the wfwg in enhanced mode, some tricks like I mentioned must be used. To solve all these problem. I made some analysis and developped a small new driver program for the purpose of loading EMM386 and WFWG. I call it IO8EMMOK. it can be downloaded from GitHub https://github.com/pufengdu/IO8EMMOK IO8EMMOK.SYS is a wrapping driver that convert the built-in XMS driver to a generally normal XMS driver. I wrote the tech details in the comments of the source codes. Here is a short summary of the details of technology. In general MS-DOS 8.0 is a DOS always in HMA without any stub below 1MB. The XMS driver is also in HMA. Since XMS driver is in responsible of controling A20, it becomes a key behind the lock case. Therefore, every time an application abitarily disable A20 and try calling DOS or XMS driver, system reboots or hangs. Every time an application rely on the address wrapping mechanism tried to run, the system reboots or hangs. This is also why MS-DOS 8.0 seems so unstable. Its A20 must be kept ALWAYS ON. However, this is an old case for DOS services, but new to an XMS driver. Most programs, including Win3x, thought the XMS driver is some where below 1MB. Therefore, it should work even with A20 off. But, this is not the case on MS-DOS 8.0. My IO8EMMOK driver provide a very simple wrapping layer to the XMS driver, making it callable with A20 off. In this case, the driver tun on A20, forwad the call, then turn off A20 again. This creates the minimal side effects, but not zero. With this driver, no patch is needed to load EMM386.EXE. Just load the IO8EMMOK.SYS as the first driver in the CONFIG.SYS EMM386.EXE will be happly to load as normal, no HIMEMX.EXE nor HIMEM.SYS. I also adapted the W3XStart patch in this case as a hotfix patch, which only modify memory. It can also be downloaded from the same github repo. There is no need to decompress the IO.SYS. The compressed form IO.SYS with the one-byte real-mode patch can be used now. With the IO8EMMOK driver, and my W3XStart hot fix, it would be easy to start WFWG in enhanced mode. The last element of making this happen, is to use a serial mouse, not PS/2. And set mobo option of Gate A20 to "Normal" The WFWG default mouse driver is not going to work in this way. Update it using Microsoft Mouse Driver 9.01. It is easy to find online. I finally achieved the attached effects. WFWG is fully functioning on MS-DOS 8.0, without hanging, without tricks, without decompressing IO.SYS. If someone found bugs of the driver, fixes are welcome.

StartAllBack 3.2.9c https://s3.amazonaws.com/startisback/StartAllBack_3.2.9c_setup.exe [Updated Feb 7 7PM EST] Please find any unreadable color combinations if you can

All of my BNav extenstions have an install.rdf with the following addition (please do not call it Borealis) [that is, if you are referring to Roytam's release, if you are indeed referring to the official Borealis, then yes, call it Borealis] - <!-- Borealis Navigator --> <em:targetApplication> <Description> <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id> <em:minVersion>0.9.0a1</em:minVersion> <em:maxVersion>2.*</em:maxVersion> </Description> </em:targetApplication>

It works with NVME SSDs also!! Tested on a friend's PC and it worked, though his PC ran Windows 8, not 8.1 to be specific. Still, it should work more or less the same on XP.

[OT] Thanks @XP-x64-Lover for helping me!!! I'm a Vista user who was struggling to find a free SSD trimming program and Kingston SSD Manager does not support Vista, as you may know (I use Vista on an a400 SSD). Smart Defrag was the solution to this problem of mine! Best regards, Win10-Hater (I'm on my phone now and there are no angular brackets on the Gboard, so had to use square brackets for the OT tags) [/OT]

@TrevMUN Smart Defrag will assist you in Trimming your SSD Drives. That's what I use, and it's free too; simply run the program and click on Trim & Intelligent Optimize. Now, sometimes your SSD Device will show up as a Hard Drive instead of a Solid State Drive. Simply hoover over where it shows the HDD Icon and your Drive Name; and Two Arrows will appear, click up or down until you see it change your drive to SSD. As stated above, click Trim & Intelligent Optimize, just hoover your mouse over the arrow that's pointing right (It's next to the Trim button) and it will give you that option. I have yet to test Smart Defrag's Trimming abilities with NVME based drives but, I would expect it to work the same way; as long as windows sees it; it should also see it. Enjoy and Good luck!