Leaderboard

Chrome is trash. Firefox is now following said trash. Pale Moon is the last, best hope... (If only they weren't such an arrogant bunch...)

Excitedly using new DOS packet driver with Links v2.21, binary ported to DOS with OpenSSL v1.0.2u (Dec 2019). This provides TLS v1.2 support in DOS! Thus far connected to all sites tested. Although DOS geeks will have no problem setting it up a how-to may eventually be posted as a quick member project. Note 'cwsdpmi.exe' is already provided in the link below and a DOS mouse driver is preferred. It can be configured to run in text or graphic mode. Personal LINKS.BAT uses 'LINKS221.EXE -MODE 1024x768x256 https://www.google.com'. http://links.twibright.com/download/binaries/dos/ To my knowledge there are now three web browsers that provide TLS v1.2 support for vanilla Windows 98 SE: RetroZilla v2.2, K-Meleon v1.5.4 and Links for DOS v2.21. Tested out Arachne v1.95 (GPL v2 license) again, formally known as Arachne WWW browser for DOS, now labelled historic. Based on the link Arachne Labs no longer develops the browser. This is the second time i've played with Arachne and my reaction is similar. It is apparent a lot of time and effort was put into development. It offers some neat features, decent built-in help for configuration and performance. It is, however, glitchy and does not appear to connect to HTTPS sites. So for now it is truly historic, mostly just for playing and learning. http://www.arachne.cz/ Will eventually try the forks below and report only if there are significant improvements or changes. The build from glennmcc[dot]org is Arachne v1.97, the second link yet another fork from Ray Andrews. http://www.glennmcc.org/ http://www.glennmcc.org/rayandrews/ Since DOS' conventional memory is precious lots has been tweaked and developed over the years, including memory extenders. From olddos.exe, memmaker was already phased out by Microsoft before Windows 95 and it doesn't run in Windows 98's DOS v7, supposedly a quick and easy way to free DOS memory. There is another DOS memory manager often mentioned, Quarterdeck Expanded Memory Manager (QEMM). I have no experience with this but from the Wikipedia page it appears there would be little gained over using HIMEM.SYS and EMM386.EXE from Windows 98's DOS v7. Many 'heavier' DOS applications already utilize their own methods. For example, many old DOS games already use DOS/4G and the Links browser mentioned above is compiled with CWSDPMI support. Still wish i was around earlier to experience all this DOS goodness firsthand, would have a much better understanding. https://en.wikipedia.org/wiki/QEMM#DOS_equivalents Back in Windows 98 tried out MemMAX (freeware, Windows 98 - 2000). Pretty much what i remember from similar software years ago. Unless i'm missing something, RAM is meant to be used not cleared. Waste time and CPU cycles clearing RAM then left with a sluggish computer upon relaunch of previously cached applications. Claimed to be useful for hardcore gaming before game launch. IMHO better to simply ensure the system is set up to boot and run lean, properly configured, with minimal background applications and services.

There’s an old thread Upgrading IE8 to TLS 1.2. Personally, I’ve only done that for IE9 on Vista. TLS 1.3 is not possible for your IE but is possible for Firefox 52.

Perhaps I wasn't very clear above, I do apologize. Of course it's a fork, I never meant to infer otherwise. What I meant is that it wasn't based directly on a particular version, as in not a static carbon copy. 52 was the fork-off point. And there have been CSS/js implementations unique to UXP that its fork-point, that being Firefox 52(.6?) lack. globalThis is one that comes to mind. (waterfox classic is similar, albeit less consolidated. its more of a transitional project to tide people over with old extensions) Now of course, they are completely on their own from here on. No more shortcuts and cannibalizing newer Firefox engines with the 24 ESR UI. v29 seems to be touching on more CSS and DOM properties, which is a good development sign. The commits are all public. And yeah. It would appear we've scared the OP off -jk

I ran both the .exe and .msi installers and Inkscape was able to install and run just fine as well.

I'd take the route of calling the bank to complain about it. I would hate it if my bank went that route. I do not have anything on my phone connected to financials in any way and prefer to keep it that way.

There's always room for improvement. I don't like some of the decisions the PM team have made, but they're far ahead of the other "main" choices. Was just throwing out an opinion, since everyone else was doing so...lol

We got 'em! I'm here listening to MP3s on my X61 in Windows 98SE right now! This is awesome. Thanks so much, deomsh! The issue seems to have been that the AD1984 cannot handle volume set to the mx value and just shuts down the sound. I haven't tested the upper limit yet, but even the default of 0x27 is a bit too loud. I had actually tried changing that volume value in the HDAICOUT.HDA already, but there was still a separate volume setting in HDAcfg.ini causing the problem. Simply not setting a volume in HDAICOUT.HDA and setting it at $42004200 in HDAcfg.ini is working great, though. I also found that DAC_1 (widget $04) has to be used to get audio from the internal speakers. This makes sense now that I know what to look for in the AD1984 datasheet. Port D (line out/speakers) is only connected to $04 while port A (headphones) is connected to $22 which selects between either $03 or $04. A custom HDAICOUT.HDA is still needed, but with only a few verbs. unmute input on port A's mixer unmute output on port A select DAC_1 for port A unmute input on port D's mixer unmute output on port D enable EAPD on port D I think HDA2.DLL itself powers on and sets up the required DAC, so no verbs for $04 seem to be necessary in HDAICOUT.HDA. I'm attaching my working HDAICOUT.HDA and HDAcfg.ini files here. I left all the unneeded lines in HDAICOUT.HDA in case they're needed for future troubleshooting. Thanks again for all your help and explanations. This has made my day! HDAcfg.X61.ini HDAICOUT.X61.HDA

commits will have a look before landing to my tree, and if undesired changes were landed they will be reverted.

Windows always used to be the OS where you could do whatever you liked, theme the crap out of it and customize it to your liking. It's starting to become more like macOS where you can't do much and everything is the way Apple wants it to be.

Chrome uses the system's encryption system, so you need to install update KB4467770 and the latest update for IE8, and then enable support, as described in this article https://support.microsoft.com/en-us/help/4467770/update-to-enable-tls-1-1-and-tls-1-2-as-secure-protocols-on-winhttp This will solve the problem of opening most sites using TLS 1.1 and 1.2. But if this does not help, then we need ProxHTTPSProxy.

In new versions, they broke support for TLS 1.3, if you try to open a site with TLS 1.3 or where 1.2 and 1.3 are used at the same time, the browser will show a certificate error. https://www.howsmyssl.com/ shows the status of BAD. The latest version where there are no these problems is 12.0.1053.0.