Leaderboard

@roytam1 <-- Maybe RT could upload and list some 'clickable' HTML files that (aim/open) reference this MSFN.org Support Thread. For the BNAVIGATOR Browser, for download here: https://o.rths.cf/boc-uxp/ (Added: At above URL -- RT did add a 'clickable' reference that opens THIS Support Thread. And makes clear that RT 'XP OS' Browsers are NOT Supported by PALE MOON in any way.) You could upload these four HTML files to URL above, naming them: bnaa1--CLICK-For-BNavigator-Browser-SUPPORT-Forum-(MSFN.org).html bnaa2--PALE-MOON-Forum-does-NOT-SUPPORT-the-BNavigator-Browser.html bnzz1--PALE-MOON-Forum-does-NOT-SUPPORT-the-BNavigator-Browser.html bnzz2--CLICK-For-BNavigator-Browser-SUPPORT-Forum-(MSFN.org).html Under a 'NAME' Sort, these HTML files would list TOP and BOTTOM, bracketing the dated 'bnav' Browser files (versions). http://rtfreesoft.blogspot.com/search/label/browser RT could also make similar HTML 'CLICK' additions at the above URL. This is something that could be done fairly quickly, as a response to Mr. Tobin. And It would show that RT is 'doing something' to minimize the problem of any CONFUSION that the RT 'BNAV' Browser is associated with PALE MOON Browser. NOT saying this is a full solution, just a possible reasonable suggestion for consideration. Feedback --> "It's a two-way street ... " I knew that!

So much for the "more constructive approach." I had a feeling this was insincere. roytam1 has no control over the actions of those who decide to use his XP-compatible builds. Even if he were to change names, remove references, yada yada yada. there could still be "ignorant" users (or even troublemakers just trolling) who will keep going to the wrong places for support or to ask questions. How hard is it to say "I don't support those builds" and link them here? Much easier than ranting there, ranting here, and rewriting a bunch of code.

I'm with you, man, Don't make it even bigger "Everything-in-one-topic" mess, else two weeks from now noone will be able to find any meaningful info in here. @dencorso, as a mod who frequently visits the topic, I'm calling you. are you also with us? PS many thanks,! I think we should do it more often for those mega-threads

I decided to create a new thread for those wanting to test the portable "Blink" version of Microsoft Edge. New portable builds of the Canary channel are being issued on the Upload.EE site, and I'm fetching those as they become available. N-Sane Forums are supplying the update links: https://www.nsaneforums.com/topic/341437-microsoft-edge-canary-channel-updates/ And here are the three latest releases: https://www.upload.ee/files/9839860/MSEdgePortable_75.0.132.0.paf.exe.html https://www.upload.ee/files/9844163/MSEdgePortable_75.0.133.0.paf.exe.html https://www.upload.ee/files/9872797/MSEdgePortable_75.0.140.0.paf.exe.html ***** A major credit goes to user @jeff69dini for getting this going. *****

See Matty Tobin and Moon Marcus refuse to realize that they are serving customers. Customers as such ask the same questions over and over again - they just do. Politely just tell them that we ("we" being you two Moon-Matt, of course) don't support Roytam1 builds, but here's the link to MSFN where you can find out more. See how easy that is??? But alas, there's one big BIG problem with this - it required being "nice". I know that this is something that Moon-Matt have some difficulty with. Just practice. Nice - there you go!

Ah, so I guess that we have found the culprit then! Even though you did take some time away from me, it is all right . At least now we know that slipstreaming with HFSLIP2000 works fine under all versions of Windows, and I myself will definitely make use of the HFSLIP2000-info script in my future testing. You kind of motivated me to actually write the script, and for that I am very thankful. I would guess that it is nLite adding those drivers to cause the IE/DX issue. Installing from USB should normally not affect anything, unless you have used some kind of a fancy tool which tampers with the system files. I do not use nLite anymore, but as far as I remember, there is a special instruction on using it after HFSLIP. Please check https://web.archive.org/web/20171220125454/http://www.vorck.com/windows/2ksp5.html, especially "Step 13". "This utility" can be found here: Edit: I just want to say that I have not forgotten about the .NET incomplete installation problem. If you look carefully at the progress bar during the Windows setup process, you can clearly see that the .NET Framework components are being processed extremely quickly. I would say - too quickly. This likely means that the INF files responsible for their installation are simply being skipped there. I will try to troubleshoot the problem, but I may need some time to investigate all the possible causes.

I have no idea how many Mafia fans roam this board, but I'd definitely like to post this for anyone who may be trying to figure out how to get it running on Windows 2000 since there is no documentation out there that I can find. This is definitely possible. First, don't even try the Steam version, it's a lost cause from the very beginning since Steam doesn't even support Windows XP anymore, or Vista for that matter. So your only option is for the Retail version (maybe), or the GOG.com version. For the heck of it, since GOG.com was having a sale on Mafia II: The Director's Cut for only $7.99, I decided to purchase and download it. At first it seemed like it was going to work, but then it didn't. It installed without a hitch, didn't even complain that I was running Windows 2000 since even the retail version states that it requires at least Windows XP Service Pack 3. But then trying to run it, it complained about some "exception", you know, those pesky little things that pop up if there's an issue with a dependency. So I decided to fire up Dependency Walker and see what was going on with that. Turns out it was dealing with PhysX, which is also required in order for the game to run. I thought I had a version of PhysX installed but it didn't seem to work, probably too new to actually work but installed at some point. So I dug a little deeper and found an older version of PhysX. I installed PhysX version 9.12.0807 and installed it. After that I fired up the game and to my surprise, it worked! It is completely playable. No more booting into my Windows 7 install which is slow as heck because of all the updates and the fact it's running on an older (15 year old) HDD, so I avoid it at all costs. But now there's no reason to, it'll work perfectly in Windows 2000. Now as far as the vanilla version of Windows 2000, I can't say it would work since I haven't tested it. But I do have Blackwingcat's KernelEx version 3.0a installed (GameGuard version) and ForceWare version 182.50 and the June 2010 DirectX9 dependencies. I certainly hope that this at least helps someone out that is looking to play this awesome (but very short) version of Mafia on their Windows 2000 computer. Purchasing the Director's Cut means that it'll include all the DLCs as well, so no need to download anything else, everything else is just there. The original Mafia states it wants at least Windows XP, but unless anything at all changed, it originally ran on Windows 98 without a hitch, even stating it in the official system requirements. If I recall, it only required a 500MHz processor for the minimum. We sure came far since then.

After installing the original HFSLIP-created ISO in Hyper-V, I noticed that IE6 and DX9 reported as such. I failed to state that I deviate from this form of installation by integrating AHCI drivers in nLite and then installing from USB on real hardware. Sorry for leading you on this wild goose chase

Yes, if you take the original Vista, it will not support SHA-2, so it will not be able to connect to the Windows Update Server.

2000 and XP disabled. Vista will not be disabled, updates from Server 2008 are suitable for it, which is supported until January 2020, so there is an update that adds support for SHA-2 encryption.

So I try 111 and 121 and certain that 111 is the last fully functional out of the box JRE8 for XP we could however transplant javafx files from 111 into 211 (or 112 to 212) to have working JavaFX bin\ fxplugins.dll glass.dll javafx_font.dll javafx_font_t2k.dll javafx_iio.dll jfxmedia.dll jfxwebkit.dll prism_common.dll prism_d3d.dll prism_sw.dll lib\ jfxswt.jar javafx.properties lib\ext\ jfxrt.jar dont know if this ok but it works with javafx examples here https://github.com/controlsfx/controlsfx

I consider it axiomatic that if Windows 10 can't mess something up, nothing can.

is Primetime Decryption different to Widevine ?? yet I've the Primetime decription activated and widevine in the folder yet it is a no go how do i get the widevine to appear in firefox addons and activated the version I have of widevine is 1.4..8.903 and 1.4.8.1008 Amazon Prime videos use DRM (Digital Rights Management), that is full encryption of streams. Adobe Primetime was/is a deprecated (not valid anymore) CDM (Content Decryption Module), whose only current use is by Windows XP users to enable h264/aac (patented video+audio codecs) decoding for HTML5 media playback inside Firefox web browser. No media delivery service uses Adobe Primetime for the purposes it was originally made, that is to decrypt DRM'ed content! 99% of services that offer encrypted audiovisual content (Netflix, Amazon, Spotify and many other media portals like national TV sites all around the world) rely on the Widevine CDM (currently owned by Google) ; Widevine module is closed-source and connects in real-time (during media playback) to specialised licence servers (equally owned by Google) to acquire decryption keys. Google updates the Widevine modules and lic servers very often and the browser vendors have to follow close; unlike Adobe Flash player plugin, which can be updated independently from the browser, a certain browser version (be it Firefox or Chrome) can only support a certain type (called "interface") of the WV CDM; this is because support for a specific "version" of widevine is coded inside the browser's own code; updated versions of the CDM can't/won't work with older browser versions. Widevine in Firefox is being updated as the browser itself is (i.e. newer versions come with updated Firefox builds); in recent Chrome versions, one can manually update the module to the latest - but still supported - version via "chrome://components" internal page... In what concerns Widevine CDM and Windows XP, these two are indeed incompatible in the case of Mozilla-type browsers, because the CDM is coded in such a way that it only looks for (patented) decoders in the OS via Windows Media Foundation framework (WMF), a Windows feature that first appears in Windows Vista SP2; this is why the Mozilla devs have hidden the Widevine CDM from appearing inside about:plugins when the OS used is Windows XP! Even if you made it appear back (which would've required modifying the browser's code and recompiling), it would be totally useless under XP! (if Widevine were open-source, it could have been patched to look for decoders elsewhere, but, sadly for XP users, that's NOT the case!). In the case of Widevine CDM PPAPI in Google Chrome, there the module uses the patented codecs bundled with the browser, but the versions of Widevine (1.4.6.xxxx to 1.4.8.xxxx) supported in Chrome 49 (last WinXP compatible) are now severely outdated and will be denied access by licence servers; as such, they are simply not working anymore! As of this writing, minimum supported "version" of Widevine CDM, of any type (NPAPI/PPAPI), is 1.4.9.xxxx (version 1.4.9.1088 to be revoked at the end of May) - to my knowledge, no browser under XP has support for current valid Widevine versions! (Under Vista, the only browser that I know of that supports WidevineCDM is @roytam1's Serpent 52.9.0 (very recent builds), thanks to a gallant effort by the Moonchild team to restore partial support for WV v1.4.9.xxxx in official Basilisk; support for the next generation of WV ("interface" 10, versions 4.10.xxxx), currently in place in Firefox Quantum, is not there yet, so at the end of May Serpent's WV support under Vista+ may become broken, too...) For those that may want to read more on the WV subject: https://github.com/Feodor2/Mypal/issues/26#issuecomment-456969027 https://github.com/MoonchildProductions/UXP/issues/962

Of course. But only the Chinese are so hardworking to port the chrome engine to XP and Vista. I haven’t had a cases that website is closed... It’s possible that this restricting functionality doesn’t work outside of China. Yes, it is a Chinese product. To use it or not is a personal matter. For me, this is a great program, bringing a modern engine to Vista :)

Thinking about, this topic would make a nice place for an overview of roytam's builds :-) There have already been some great postings across the forums, perhaps can be linked here. What I'm unsure about are especially the differences to the original builds. Just know that for some VERY old browsers (even FF2) his goal was to add modern TLS1.2, making half the web which is broken with "cipher errors" now readable again! Amazing how accessible the web can still be, if it weren't for such articial blocks. If the monopolies would only want to, instead of blocking without need and even deleting all older stuff. And so far his builds contain only engine updates, the GUI remains untouched. Nearly all of the engine updates are also collected commits from other devs and projects, like waterfox etc. Still the mass of browsers he manages to update regularly just blows my mind. My personal interest is mainly: ------------------- K-MELEON --------- KM-Goanna exists in 2 Roy-versions too: KG76+KG74 Attention Confusion: there are also much older K-Meleon GECKOS with the SAME version numbers, by KM-dev Dorian, called K-Meleon74 and 76 (engine 24esr+38esr) - Roy-KM-Goanna 76.1.1: palemoon27 engine plus selected updates, shell of Dorian's KM76RC2 from 2016 for XP SP3 or newer (SP2 with tricks, if a special OS dll copied over from SP3) http or https://o.rths.ml/kmeleon/ http://rtfreesoft.blogspot.com/search/label/kmeleon KM-Forum for latest 76.1.x http://kmeleonbrowser.org/forum/read.php?19,148500 MSFN-Forum mainly in NEWMOON topic, a bit in others too - Roy-KM-Goanna 74: final palemoon26 engine plus selected updates Shell of Naruman's KM1.8, a very customized old user-fork of Dorian's KM74 (incl. hardcoded ABP in browser/components, etc.) for Win2000 or newer (partly also usable on 98SE with latest KernelEx, very shaky yet, but best TLS1.2) http or https://o.rths.ml/gpc/files1.rt/KM74-g22-20180718.win2000.7z http://rtfreesoft.blogspot.com/search/label/kmeleon KM-Forum KM-Forum http://kmeleonbrowser.org/forum/read.php?19,146040 MSFN-Forum mixed in various topics ------------------- Guess there's also a pure Palemoon26 for Win2000 build. Most such exotic one-time builds can be found here (list needs JS+XHR enabled): https://o.rths.cf/gpc/files1.rt/home.html Or without JS but pure xml: https://o.rths.ml/gpc/files1.rt/index.php?sitemap Retrozilla is especially confusing with different authors/builds/same versions numbers, but deserves an own post too

Just in case someone not know, the reason Sun drop XP is JavaFX8 component: Webkit isn't working (need SRW) EDIT: found another mirror https://github.com/frekele/oracle-java/releases/ that also have tarball. So just ignore my previous post

if you have 7zip something like this: 7z e jre-8u211-windows-i586.exe Data1.cab 7z e Data1.cab installerexe 7z e installerexe .rsrc\1033\RCDATA\* && ren 5 new.patch && ren 6 old.zip && ren 7 bspatch.exe bspatch.exe old.zip core.zip new.patch 7z x -ojre core.zip del Data1.cab installerexe bspatch.exe old.zip core.zip new.patch for /r %f in (*.pack) do jre\bin\unpack200.exe "%~f" "%~dpnf.jar" && del "%~f" jre\bin\java.exe -Xshare:dump EDIT: no errorlevel check there oops

I confirm it works: 1.) stop MS Antimalware Service ; 2.) put the 4 .vdm files in "C:\Documents and Settings\All Users\Application Data\Microsoft\Microsoft Antimalware\Definition Updates\Updates"; 3.) restart MS Antimalware Service; MSE updates and the "...\Microsoft Antimalware\Definition Updates\Updates" becomes empty. Great work, folks! Y'all rock!

One goes beyond Chrome 51.0.2704.63, things start not working. 49 => 51 is not much of a spoof, but that's as far as one can go.

MSE is not much of a loss. It is/was possible to try to get a virus intentionally and have MSE fail. This had been documented on sites that compared it to other virus scanners and it showed to be weak. To be 100% honest I do not know how to actually get a virus aside from downloading sketchy cracks off the darkweb and trying to install pirated software that had been infected, I don't know how you can actually get a virus on XP. I suppose there is a threat of opening email attachments and getting a virus, but honestly you should know better to do that if you are so worried about it in the 1st place. Moving forward Clam Win is going to be the best option for XP.

I raised a bug on firefox before to request that pref be changed automatically, (https://bugzilla.mozilla.org/show_bug.cgi?id=1356939 ) but was redirected to an older bug (https://bugzilla.mozilla.org/show_bug.cgi?id=383582), which is still there unsolved.