Leaderboard

>@msfntor, @VistaLover My best browser is K-Meleon 76.2 +Pro http://saveimg.ru/show-image.php?id=18307576433bbafba4a5adfb2be5d9c5

@AshtonLee.IT We had discussion about the version of BOOTICE, see here. Glad it works now. This slow down with Defender is a bit extreme. But i guess an option to disable realtime monitoring during capture would properly cause one more false positive.

Thanks, I like FTDeepDark v14.3 as it is. Mussala-856 meters => basilisk52-g4.4.2019121 => version does not fit...

@roytam1: I tested and confirm v.2019.12.13 of Serpent 52 again works perfectly with Adobe Primetime. Thank you very much! You do rock!

... Running XP SP2 32-bit, i.e. without SP3/SP4, does kind of put you in a minority of XP users here; most software still targeted at XP these days assumes SP3 plus all M$ updates until the End of Extended Support (for XP) ... That is why I said you need to be specific... FWIW, from my own recollections many years ago when I was on XP SP2, the Adobe Primetime CDM (which, for some obscure reason, has become quite en vogue in these forums ), does require SP3 to be present (all I know is I was unable to get it working there; it did install, but no MP4 decoding was possible; ofc, I could be wrong - and no way to retest now...).

The new version of Aero Glass with 19.09 support appears to be available. Big thanks to the dev!

I am sure you understand why I would write that it was incompatible seeing as it was listed as such. Thank you again for your assistance, especially in such thorough replies.

Hi again ; how am I to know that, since you never told us about this fact? ... You are correct; before Firefox Quantum (v57.0+) was finalised and made it to the release branch, a non-Quantum user could install lightweight themes (previously known as personas) directly from AMO; they were at the time simply renamed to just "Themes" by Mozilla, while Complete Themes (the ones previously called "Themes") where demoted and made much more difficult to discover in AMO; that is because they were slated for slaughter , as not being compatible with Quantum... Shortly after Quantum was released, AMO withdrew all "legacy" extensions, together with all Complete Themes ! To add fuel to the fire, they did also remove most "legacy" lightweight themes, while those they kept underwent the Web Extension treatment, to render them compatible with Quantum (similar things happened to language packs and search-engine plugins ). There's a relevant and quite interesting thread in the official Pale Moon Forums that discusses the old vs the new (WE) format of Firefox personas: https://forum.palemoon.org/viewtopic.php?p=177818#p177818 Some "legacy" personas are still recoverable via the Web Archive; the one you already have and suggest to others has, luckily, only one working web capture and can be installed in either FxESR52/Serpent52/Serpent55 through that page: https://web.archive.org/web/20170913041318/https://addons.mozilla.org/en-US/firefox/addon/mussala-856-meters/ This is also available via CAA (caa:addon/lwthemes) and is indeed useful to save to disk (and then be able to re-apply ) an already installed persona, no more to be found on AMO...

@VistaLover , @Mathwiz , and RT <-- Thanks for HELP offered here. https://msfn.org/board/topic/178259-instagram-videos-not-working-in-firefox-52-esr/?do=findComment&comment=1172626 Fairly recently, 'Mathwiz' helped me get (MP4) INSTAGRAM Video working with (BK)ST-55 Browser under WinXP. I am using the ADOBE PRIMETIME Plugin solution install manner, which 'VistaLover' did pioneer that. So, 'Mathwiz' did post a resulting SUMMARY message entry at URL above, and I draw worthy attention to that.

Try using the UOC Patch, it might improve scrolling on your browser, but you must use Serpent 52/New Moon 28, Firefox 45 ESR SSE, K-Meleon Goanna or New Moon 27, as I don't support codebases newer than 52 ESR.

Change the background color of the new tab In userContent.css put @-moz-document url("about:blank"),url("about:newtab") { body, #newtab-margin-top, #newtab-horizontal-margin, #newtab-margin-bottom {-moz-appearance: none !important; background: #303030 !important;} }

UPDATE! All the versions of the UOC Patch, including the Enforcer, have been rewritten from scratch. This time, I have extensively reworked the tweaks used for the rendering engine, which allowed me to double the scrolling speed of the patched browsers, increasing the general responsiveness. Loading times have also been shortened, thanks to some tweaks backported from K-Meleon Goanna. The New Moon 28-specific version of the UOC Patch has been withdrawn, since now the Patch no longer comes with E10S enabled, due to compatibility issues on some machines with some video cards (especially ATI ones). Users of the SeaMonkey browser, especially version 2.48, can use the 45 ESR version of the Patch once again. As all the changes are too many to be listed in a single post, I will limit myself to say that all the versions of the Patch have been extensively remade and tailored upon the peculiarities of each codebase, and this has required me to write thirteen different revisions, before coming out with the final version, which might be subjected to minor updates in future, as usual. I have successfully managed to mitigate the occasional stuttering issue that affects Mozilla based browsers, especially Firefox 45 ESR SSE, and thanks to the backporting of some parameters from K-Meleon Goanna and Serpent 52, I have managed to dramatically improve the overall speed of the browser and reduce the page loading times. This, at least on the machines where the pre-release versions have been tested, proved to be a real game changer, turning old computers, no longer usable on the web, into decent web browsing machines. I also have reintroduced favicons, since some people complained about the lack of those in the previous versions of the Patch. The Awesome Bar has been disabled, keeping only the autocomplete feature active. Please update to the newest version of the UOC Patch and the Enforcer, and start with a new, clean profile, as a "dirty" profile might hamper the performance of the patched browser. The new build number is N2M. Happy RDDin'!

Good! Next step: go in Device Manager and disable ALL usb controllers. Without mouse: use TAB, arrow's and ALT+e to go to right places, and SPACE to enable/disable white square boxes (sorry, can't upload pictures, I have only 20KB upload space left...). Further if you want to disable SATA for the time being, set hard disk controllers to "None" (or something like that).

Thank-you for your provocative post @bphlpt. Thus far running vanilla has served my purpose and i have little desire to delve into kernel extensions and the like. The primary reason for repeatedly mentioning vanilla is to keep this from turning into yet another hybrid system thread, with numerous posts related to mis-matched software versions and broken software. Most members have tweaked their systems to such degree that they are no longer certain which software runs on a fresh install. Recent examples above. Believe me, getting tired of typing 'vanilla'. My system and i are not pure, there are inconsistencies, we are all hypocrites, i have been transparent. For example, my system uses Windows ME ScanDisk and Disk Defrag, mentioned early in this thread. They are just drop and replace from MS, no compatability layering required. So i pick and choose too. If the software installs without manipulation, then to me it's vanilla Windows 98 compatible. If it's been custom coded and/or compiled to work with Windows 98, such as RetroZilla or a Bash script, that's fine too. In the end, the system administrator decides where to draw the line. I just want a stable system, using software intended for the system. In the Linux world, doing otherwise is referred to as a Franken* system and often leads to instability and unintended complications. All the software i've installed has been specifically coded for Windows 9x, most tested on thousands of Windows 98 systems back in the day. If someone modifies and compiles software specifically for Windows 98, as with RetroZilla, then why not. An about:config change in a stand-alone browser should not be compared to kernel extensions or modifying system files, that is not fair play. The component has already been compiled in, it's just a default about:config oversight. If my future hardware exceeds Windows 98 limitations, then of course i would make changes to get the system running. If RetroZilla continues to be unmaintained and stops working well with the ever changing internet, then i too would consider 'enhancements'. Almost all of my browsing is without JavaScript anyway, poor page rendering is par for the course. This is a trade-off i have happily lived with for many years for a calmer computing environment and to prevent unauthorized code execution. In general what is acceptable to me is software that can easily be installed and removed, without affecting the kernel or any critical system files. I do not desire compatability layers, nor do i necessarily need more recent versions of software, to me this is what a newer OS is for. In my assessment, if upgrading Firefox from v2 (vanilla) to version 3 or 8 is still inadequate to securely perform banking and emails, the improvement is negligible. This thread is intended to be an archive for users that just want a basic Windows 98 system in the present day, the barriers, knowing some software versions that may work, some work arounds and what to expect. More experienced Windows 98 members may want to start a new thread, as you proposed, showing off the best Windows 98 is able to roll out. In my opinion this would be worthwhile, if for no better reason than providing a clear and simple how to. To newer members, the many, often overlapping, enhancement projects are probably overwhelming. Another fun project would be to install Windows 95 for it's 25th anniversary, tweak the heck out of it and see how it runs.

Thank you @bigmuscle!! Special thanks to Microsoft for not trying to reinvent the wheel on this update. Aside from aeroglass needing an update (which was only because it's coded for specific versions), this update didn't break any of my settings or programs. All bigger updates should be like that. Update security features.. maybe a new feature.. but not reset settings and break programs.

anyone up for updating this one to work on windows 10 1909?

You are kindly asked to check the validity of what you post ; the OP asked for a "theme" for his Serpent 52.9.0 copy and what you've linked to is a (lightweight) theme (previously known as persona) packaged in a Web Extension format, targeting at minimum Firefox 53.0; that WE persona won't even install in Serpent 55.0.0, because both UXP and Moebius do not support WE lightweight themes... Most unfortunately, there's currently a very limited choice for Personas compatible with Serpent 52.9.0: https://addons.basilisk-browser.org/personas/

Comodo IceDragon 64-bit, forked from Firefox Quantum v65.0 and run on Windows 7 SP1 64-bit is a tad Off Topic for this thread, IMHO ; be that as it may, per my recent post, CID (Fx 65.0 derived) will download and install Widevine CDM v4.10.1146.0 when Play DRM content (or whatever it's called in Fx 65.0) is ticked in Options; but that specific version is currently DEPRECATED by Google (their Widevine licence servers), so if you visit a media site with DRM that requires the Widevine CDM to play its content (video/audio), then you're out of luck with CID; you must use a version of another browser (FirefoxESR 68.3.0, Firefox release 71.0, Google Chrome latest, Waterfox Classic 56.2.13) that has support for the latest supported version of Widevine, v4.10.1440.19 The CID devs will have to either patch their current browser milestone to enable it with v4.10.1440.19 support (which shouldn't be that easy in itself, but definitely easier than porting v4.10.1440.19 support to UXP ) or rebase their fork to use at least a Firefox 68.3.0/69.0+ codebase, which comes with native support for WVCDM v4.10.1440.19 ... Also, on your Comodo forums post, you wrote: Please, DON'T MIX completely unrelated things! The Adobe Primetime CDM was an older DRM implementation (offered by Adobe) that 1. is no longer used by any media site for DRM purposes, 2. it was only internally supported by Firefox versions up to (and including) v52.x.x; starting with Fx v53.0, all Adobe Primetime CDM support code was obliterated from inside Firefox; so, there's no chance a Firefox 65 based fork would download and install APCDM... I re-iterate: (Google) Widevine and (Adobe) Primetime CDMs are NOT interchangeable! And even if you use a browser that does support APCDM, you don't need it at all (as a h264/aac decoder) under Windows 7+ (see more below...) If you're using Serpent 55.0.0 under Windows 7 SP1 64-bit, you have absolutely no need to even install and use Adobe Primetime CDM there; you can't use it as a replacement to the non-working Widevine CDM v1.4.8.903 that St55 installs under Vista+, and you don't need it as a decoder for h264/aac (html5 MP4 video), because, under Win7, St55 already comes with two such decoders: a.) the OS provided one via WMF framework, media.wmf.enabled;true b.) the one bundled within the browser in a custom ffvpx library, media.ffvpx.enabled;true If you're using Serpent 55.0.0 under Windows XP, then, likewise, APCDM can't be used for DRM purposes... And if you need html5 MP4 video decoding support, then media.ffvpx.enabled;true is still valid... Should you wish to install APCDM as an alternate second decoder in St55, then, a) Serpent 55.0.0 originally was forked from a Firefox 53.0a1 snapshot, where APCDM support code was already removed! b) @roytam1 , at some later point after Basilisk/Moebius was abandoned by upstream, did re-introduce APCDM support in St55: https://github.com/roytam1/basilisk55/commit/8dc3c7f3ece162392af056a3b82ce43105ee8938 (ported change from iceweaselXP-53: Restored eme-adobe plugin support for Windows XP systems) As you can see, that support was imported from another fork (not straight from Firefox <=52.x.x); in any case, Serpent 55.0.0 reports itself as being Firefox 55.0, so its GMP-manager will never download APCDM by default... You can try the trick posted in the APCDM thread (and recently mentioned by @Mathwiz): (which, IMHO, should be modded to read: "52.x.x ESR, Serpent 52.9.0, Serpent 55.0.0 users...") and if that wouldn't work, you'll have to manually download and install APCDM v17 as detailed in the relevant thread; but, again, this won't solve any DRM issues you might be experiencing, on any Windows version you might be running Serpent 55.0.0 I have provided, I hope, very clear and detailed explanations/instructions, so make the best you can with them...

That would be v2019.6.27 ; actually, AMO, again , made a big blunder there and marked the extension as Firefox 60.0+ compatible; but if you manually download the .XPI file https://addons.mozilla.org/firefox/downloads/file/3060290/https_everywhere-2019.6.27-an+fx.xpi and manually install it in FirefoxESR 52.9.x (drag-n-drop it in about:addons), you'll find it's still compatible: Nothing to apologise for... Simply another case of being misled by the wreck that Mozilla and AMO have now become...

It's out dude, the 19.09 supporting version, but in feature please don't request it so frequently. He/she's got a long history with this project and it's unlikely they'll just abandon it, new versions are always on their way and will be ready when they're ready.

Well, I'm home for the weekend, so I decided to try on my home system (also Win 7), but discovered that here, I already had the v1.4.9 installed that has been so elusive on my Win 7 work PC.... But I'm sure you're onto something. I noticed with interest that Serpent 52 is "lying" to the Mozilla server and claiming to be FF 60. Serpent 55 claims to be FF 55 (even though it's closer to FF 53), and as you noted, it's stuck with v1.4.8.... (I suppose the proper "lie" would cause the server to download v1.4.10 , although it wouldn't work since Basilisk and Serpent don't have the required hooks yet....) The only question is, even if you migrate a profile from another browser (a practice I'm aware you're implacably opposed to, as you first made clear when I migrated my profile from Serpent 52 to 55; but my migration from FF 52 to Serpent 52 occurred long before then), defaults don't get migrated - only user set prefs do! So if it's wrong, I must have changed it manually, either back on FF 52 or an early version of Serpent 52. But why on Earth would I have ever modified that obscure pref? So I went searching, and am rather sure I found the answer. The following is in a "spoiler" at the Adobe Primetime thread: Thanks go to @mixit for keeping those obsolete instructions for "historical" reasons! Turns out Primetime works on both FF 45 and FF 52, but neither of those versions supported it officially, so to get the server to download it, you had to "lie" and tell the server you were running the closest supported FF version! That "lie" is no longer needed or useful with Primetime, but it would have the side effect of downloading Widevine v1.4.8. So I'm sure when I get back to work Monday, I'll find that pref user set to spoof FF 51 vs. the default of 60.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.4.win32-git-20191214-dacb3da00-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.4.win64-git-20191214-dacb3da00-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.rths.ml/basilisk/basilisk52-g4.4.win32-git-20191214-dacb3da00-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.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20191214-dacb3da00-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20191214-dacb3da00-xpmod.7z Official repo changes since my last build: - Bug 1509685 - Add more bounds checking in nsMsgDBView::UpdateDisplayMessage() to avoid crashes (717be395f) - Bug 1482248 - don't crash on empty file name in nsMsgLocalStoreUtils::nsShouldIgnoreFile. (b797607a8) - Bug 1571481 - Improve multipart/alternative. (282cdd6ba) - Merge branch 'master' into release (642032029) - Merge pull request #1314 from g4jc/mailnews_patches (ca46bc1f6) - Merge branch 'release' (5ba7f92d5) - No Issue - Execute the precomplete command on *nix AltPackaging (647d14de8) - New cycle version bump (7758b9a26) - Update default bookmarks toolbar FAQ entry to redirect to forum. (d2a1d638b) - Issue #1317 - Increase the XML nested depth limit to 2048. (dacb3da00) My changes since my last build: - Revert "Issue #1259 - Adjust Widewine strings after removing Adobe Primetime support" (37e153f59)

Please fix AeroGlass for Windows 10 1909