Leaderboard

Just to quickly report that I've now had a go with Supermium on Windows XP 32 bit, and it seems to work very well! Early days of course, but it looks very hopeful.

The new version is there https://codeberg.org/Theodor2/Mypal68/releases github things for update are broken so far, it is possible to poke issues though.

I have decided to expand the documentation of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 with a short explanation of the sixteen menu items based on the experiences from the beta test. Apparently, not all menu items are self-explanatory after all! Thanks for that especially to @mina7601!

Besides using those rebased dlls, it may also help rebasing chrome.dll libEGL.dll libGLESv2.dll vk_swiftshader.dll vulkan-1.dll. The specifications provided by @UCyborg (point 3) work in my multicore system Have a backup of the dlls to be rebased ready, just in case. 1-Search and download rebase.exe 6.0.6001.17129. Place it somewhere of your liking. Copy full path 2-Open a prompt box on your-path-to-Supernium\121.0.6167.81 3-In prompt, enter your-path-to-rebase.exe -b 10040000 chrome.dll libEGL.dll libGLESv2.dll vk_swiftshader.dll vulkan-1.dll

Glad to be of help, don't forget to switch the dimmer off, for Optimus notebooks.

Strange, this just joined spammer from India had no problems with the registering and spamming with his new ego boosting potion, as usual. https://msfn.org/board/profile/440513-sejefe1414/

@mina7601 Thanks for your offer! You are a great beta tester! Glad to hear I can count on you in future times! And, of course, I will!

Hi feodor. Beginning testing. It does seem to load faster. I also notice that the update addons function works out of the box now, so no need to replace omni.ja at root, as in the previous version. Will report back later. Thanks!

Notice: due to lack of changes in upstream, new UXP based builds will not be available tomorrow.

Yes, I'm sure that's right. I did wonder whether the USB lead connection could carry power as well as the data. I can try it out with my existing card, and I might do that tomorrow just to confirm.

Getting there! I now have two 'risers', and the correct eSATA card is now on its way to me! Just a quick question about the risers. They both have power connectors on them. One has more than the other, and that's the one I will use as it's physically slightly lighter. Am I right in assuming that those power connectors are there because the unit is designed to work with power-hungry powerful gaming graphics cards, which need more power than the PCI-E connector can provide? If so I guess I almost certainly won't need to connect them for my use.

Beta testing of ProxHTTPSProxy's PopMenu TLS 1.3 3V3 Hello again, my dear beta testers, @Dave-H, @mina7601, @NotHereToPlayGames, @George King, @XPerceniol! This was a beta test at its best! One week of testing, fixing code, and checking different scenarios! With very many helpful and exploitable results! You all did a very good job. But one after the other! First of all, thanks to @XPerceniol for the attempt to test my program package! Unfortunately, his computer did not want to participate in the testing. It's a pity that this could not be followed up! Next, I would also like to thank @George King for the willingness to test my package in Windows XP Professional x64, which unfortunately could not be done due to personal reasons! Furthermore, a big thank you to @NotHereToPlayGames for testing, reporting and confirming that my package runs on Windows XP Professional x64, despite private commitments! And on it goes! A big thank you to @Dave-H for the continuous testing and reporting, for your advices and support, especially for the correction of my documentation in terms of spelling, punctuation and grammar! I did my best, but unfortunately, I no longer have reading glasses, I need new ones , and I am not a native English speaker. And finally, a very special, huge thank you to @mina7601 for the in-depth testing, tracking down and confirming bugs, for the continuous reporting and your support! This is how a beta test provides solid and usable data. Simply great! Anyway, I have to thank you all for your efforts and time commitment! This is not something that can be taken for granted! This beta test was absolutely important and also necessary. Five times I had to send additionally corrected versions of different programs to you via PM. An early release of my program package would have been a disaster for sure! But now, all the problems we found have been fixed, and hopefully there are none left, although programs always contain bugs of some kind. Speaking of bugs, from now on we have a new terminus technicus, the one I christened "space bug". And, I love it sooo much! Anyway, you guys are a great team , and with this post I officially end this beta test. I hope I can count on you next time. Everything else soon! Greetings from Germany! Cheers, AstroSkipper

Hi! Nice to meet you all. My name's Carlos, I'm a former sysadmin and huge fan of IT and all tricks & hacks related to how Operating Systems work internally. Sometimes I like to write guides and tutorials for beginners, which also serves me to improve my skills. Big Thanks to @Tripredacus for helping me accessing to these forums!

I'll comment on it in one word - paranoia

Unless I am mistaken, nothing discussed in this thread would work unless Vista x64 has been modified in violation of Microsoft’s EULA, so this concern about modifying Opera seems rather hypocritical. To his credit, the developer of extended kernel for Vista x64 has “gone straight” and currently devotes his efforts to modifying open-source Chromium (Supermium), which is perfectly legal AFAIK.

Not entirely true. Somebody here should ask win32ss direclty on just what "vulkan" is and is not when it comes to not only XP x86 but also to XP x64 which is not the same beast driver-wise. MANY x64 users have witnessed this for themselves. I think win32ss would know more about this than folks that simply delete files willy-nilly and check a checkbox, "yep, it 'works' without this file". Deleting a file in x86 does not carry over to deleting a file in x64. Speaking solely for XP. I think UCyborg has also researched the matter in the past, do not recall offhand.

Quite some time already passed, so it would've been known, yet to this date, the developers declare - it still didn't happen. Will it, ever? We don't know. "Contrary to popular belief, AES-128 is not broken in practice by quantum computers" https://blog.cloudflare.com/post-quantum-to-origins/

Oh my, that's wow! Enjoy latest Chromium in your XP PC, and I hope it's running smooth, and that you are not facing any crashes at all.

Good to know - I'll keep an open mind then for the next release. Thank you @Dave-H and @dmiranda.

StartIsBack++ 2.9.20

Report spam posts

I'm now running Supermium 121.0.6167.81 for a few weeks and it seems work well, even some pages that failed in 360EE 86.x and MyPal68 so still can live with XP

... Please, read this ... Best regards !

As most following these threads probably know already , all the XP/Vista compatible 360EE variants (v11/12/13/13.5) are NOT compatible with MV3 Chrome extensions (which require at least Chromium 88) and, in the same vein, are NOT compatible with the "new" Chrome Web Store (CWS) ... Since sometime on Feb 13th, 2024 (depending on your location), "old CWS" URIs for extensions/themes/etc., of the format: https://chrome.google.com/webstore/detail/* now auto-redirect to the "new CWS" URIs for the same extensions/themes/etc., of the format: https://chromewebstore.google.com/detail/* This isn't a first occurrence, the same thing used to take place during the autumn of 2023, when the eventual migration to the new CWS was announced beforehand: https://support.google.com/chrome/thread/231812199 https://blog.google/products/chrome/google-chrome-web-store-redesign/ https://9to5google.com/2023/11/20/google-chrome-web-store-redesign-preview/ In late December 2023, this auto-redirection (old -> new CWS) in non-supported Chrome versions stopped taking place, but in the loaded old CWS appeared a top info-banner indicating that: The user could disregard/remove this banner and continue as usual ... Well, Jan 31st 2024 came and went, but the "status quo" remained in place until Feb 13th, when the auto-redirection to the new CWS resumed ... Google staff seem to have a perverse sense of "humour" , because after the auto-redirection has been completed, in non-supported Chrome versions, a new in-page banner is being displayed, stating: However, clicking on the "Visit legacy store" area (JS-controlled button) will only start a vicious circle , resulting in that same "new CWS" page ... Issues with the "new CWS": The older the 360EE version you have, the more page rendering issues you'll get ; below, a screengrab with 360EEv11 (Ch69-based): Apart from the overlapping fonts, all "carousels" in the page are absent/non-functioning, because they require JS+CSS code not supported there ; these rendering issues are less/absent on higher versions of 360EE (v12+) ... But the main issue is that you can't install/download extensions from the "new CWS", because the "Add to Chrome" button is greyed out ... Mitigations This third party userscript, when installed (requires a userscript manager, e.g. Violentmonkey, Tampermonkey, etc.), will make the "Add to Chrome" button active again, however its functionality will now be limited, in that it will only enable a .crx file download to disk, not proper installation (as was the case with the "old CWS"); after saving to disk, the user has to drag-n-drop the saved file onto the "chrome://extensions/" internal tab, for the installation to proceed... The problem with that userscript is that the "name" of the downloaded extension always comes up as "undefined" (the "version" comes up correctly), so some renaming is in order after the download (perhaps one savvy person here could fix the script in that regard? ) ... Another solution I've been using is based on this extension ; the problem is that the latest version, 1.51, compatible with the "new CWS", is of the MV3-type, thus incompatible with 360EE (and Kafan MiniBrowser); here's an MV2 custom patch that will install and function as expected under Ch<88: https://www.mediafire.com/file/on5h2vit08a1xk6/1.51-mgdjkephahlgejakcnbooghhocmoppai-MV2.crx/file BTW, this is an "anonymous" upload that will expire after 2 wks of inactivity ; once installed, use the context menu on a "new CWS" tab to fetch a .CRX file to disk... Caveats of the two solutions above is that the "new CWS" won't label incompatibilities with Ch<88, so the .CRX you end up saving to disk may well be an MV3-type extension, incompatible with your "legacy" Chrome browser ; I probe the CRX files with 7-zip, opening their manifest.json files with an editor and checking for the "manifest_version" value (to be 2, that is...). A third option that might die any day now is the following: Make a bookmark of below URI: https://chrome.google.com/webstore/old/ Once loaded, it'll auto-redirect to: https://chrome.google.com/webstore/category/extensions which is STILL the "old CWS"; as long as your browsing remains confined inside that very one tab, you can access extension-URIs in the old format, e.g. by clicking on suggestions or searching in the old-store's searchbar (and make sure the search result is opened in the same tab): The back and forward nav buttons are allowed, but be sure not to click the reload one (will get you to the new CWS) ; since this is the "old CWS", it won't offer (to your "legacy" browser) MV3-type extensions in the suggestions/search results ... Of course, as time moves on, the MV2-type extensions now found inside the "new CWS" will be eventually all migrated to MV3 or purged completely, thus these workarounds will become moot... Save your MV2-type indispensable Chrome extensions while you can... PS: I'm dead certain evil Google will make sure your Ch<88 will become less effective in browsing the web over time, but I feel it'll still be good for the next two years, at least - here's hoping (of course, browsers based on much newer Chrome versions have recently surfaced that can launch under XP/Vista, granted with several issues so far, but this analysis was targeting mainly 360EE/KMB users) ...

No, it's Blaukovitch crack, you can easily find it, here the link I will not give. The reason I share this is that he created wrappers for many system libraries and rewrote a few (api-ms), and I am very positively surprised that it works on Vista with the extended kernel.

It's a 3D gaming profile, the one I use for Injustice 2, doesn't work for 2D apps.

No. What I quoted from his post didn't contain any reference to a certain person. It is just your kind of interpretion. No more, no less. You don't always have to relate everything to yourself. Take the words as they are! It's as simple as that. And now, over and out!

The saga continues, I'm afraid. The people I ordered the card from are still trying to let me know whether their warehouse can actually supply the card I ordered! The PCI-E 'extender' I ordered still hadn't arrived several days after the last quoted delivery date. I reported this to eBay, and sent a message to the seller. It was supposedly despatched on January 31st, but is not recorded as delivered. I heard nothing, until I got a message from eBay saying my money had been refunded. I then ordered another one from a different source. Then, I got a message from the original seller apologising for the fact I'd not received the first one, saying he'd refunded the money, and he was sending another one! Oh dear! So, it looks as if I'm going to end up with two extenders, possibly three if the original one now arrives! I'll get there eventually!

I'm rather hoping that I don't have to do that!

This is the half height bracket that was sent with the incorrect card I received. It should do the job I think, as the 'top bit' is definitely shorter than on a normal bracket, so hopefully the card will hang in the air high enough above the PCI-X socket below it to enable the PCI-E extender to go underneath it. I have spoken to the people I ordered the card from, and sent them a picture of the incorrect card. Hopefully they will come back soon to let me know if they can send the right one. Naughty I know, but if they want the other card back, I'm going to quietly keep that half height bracket just in case I can't find the right card supplied with one!

This project has NEVER been intended to carry XP into the year 2030 and beyond. NEVER. This project was intended only to "extend" XP and buy me some time before migrating to Win10. This project has served the purpose that I needed it for, I no longer install XP on any of my re-installs, all re-installs have been migrated to Win10 one-by-one. I follow the lead of "professional programmers", none of them devote time to XP, Vista, or 7. Hobbyists, yes. But "professional programmers" have moved on. As much as I respect and appreciate the user base (which you yourself, D.Draker, admit that you are not among) of my 360Chrome "rebuilds", I encourage that user base to actually take that same path. That path being to migrate away from XP, skip right over Vista and 7, get 10 or 11 to your liking (you will need other forums for that learning curve), and you should be fine until the year 2030. Trying to get XP to carry me into the year 2030 is a dog chasing its tail, I am not a dog. Again, I never set out to carry XP into the year 2030. What we have currently should carry us forward 2 or 3 more years, that is pure speculation for any of us to guess. That has served the only purpose I set out to fulfill - buy me some time. "Mission accomplished."

Dear Astroskipper, just a friendly warning - be on your guard with that user ! I had to block him. Not only he (she?) likes to spam topics with meaningless and even offensive messages, his (her) behaviour is rather weird and suspicious. Some of such users also sent me dangerous links.

What about that poem you were going to write to honour the presensce of XPerceniol ?

Very simple ! It supports XP, without XP being supported.

Is this the same company ? If so, then it's not German, and definitely not 15 generations of Germans involved. https://en.wikipedia.org/wiki/Webroot

Sal, a very, very good TV show for you would be the third season of Twin Peaks 2017 ! I trust you'll get to 100% soon !

For information only! At the moment, my focus is on the publication of my program package and further development with regard to optimal use and user-friendliness. Everything else I will put to the test later.

Hello @George King! Thanks for your request and tips! At the moment, support for multiple languages is not envisaged. I will look into this in due course, but English is an international language and, in my opinion, quite sufficient. But anyway, thanks for that! Cheers, AstroSkipper

Thank you very much for your offer! You can use the proxy and all its features as usual. Maybe, try some you usually don't use or need! In any case, the daily use is a second test, too. This beta test will be ending very soon by a special post of me. But it won't be the last one. The development of ProxHTTPSProxy's PopMenu will go on. I hope I can count on you next time, too.

Yep! The strings of PopMenu's settings window can't be changed unless you'd decompile PopMenu.exe, replace the strings, and recompile it again. The problem is the decompiling, a kind of reverse engineering. In most cases you won't get the complete code. I forgot to mention that in some cases you can replace code or images by Resource Hacker. I used it to replace the icon in @cmalex's ProxHTTPSProxy,exe to get back the old, well-known icon of whenever's or @heinoganda's releases. Resource Hacker can recompile such a modified executable. But this won't work with all files. You have to have luck, too.

Yep! The strings of PopMenu's settings window can't be changed unless you'd decompile PopMenu.exe, replace the strings, and recompile it again. The problem is the decompiling, a kind of reverse engineering. In most cases you won't get the complete code.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190302-e64dae886-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190302-e64dae886-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win32-git-20190302-e64dae886-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190302-e64dae886-xpmod.7z Official repo changes since my last build: - WIP fix 1 (c962e2051) - Move default-enable pref to application. (c08b490c5) - Update Basilisk FE code with HTTP Auth DoS protection. (f227feb6e) - Make the Auth prompt DOS protection a browser-element opt-in feature. (c1ece93c2) - Improve the http basic auth DOS protection heuristics. (e64dae886)

both download index and release note posts should be free from "the names". lets hope he will have positive feedback.

I wouldn't react prematurely. In a couple days, this will blow over. It appears the parties are rectifying what they can. Don't let a nasty person chase you away.

To fully compliance with their rules, names need to be changed besides artworks, including New Moon and MailNews and Navigator.

It is not an abbreviation of Binary Outcast™ and I never declare it is. "boc-uxp" / "BOC/UXP" is just *my* reference for that group of binaries.