Humming Owl

Hello. I found some information that could be useful but I need you to test it on XP SP2 to see if it actually works. I tested this on Win7 with v9 and the "chrome.dll" file. The "GetLogicalProcessorInformation" function is present in the code of the "chrome.dll" file of v9. With HxD you can directly search for the "GetLogicalProcessorInformation" entry (Offset (h) = 01b312c0) in "chrome.dll" (screenshot 1 below). After replacing the code by 00 hexadecimal values I got the same error dialog but with no entry point (screenshot 2 below). After replacing "GetLogicalProcessorInformation" by "GetL0gicalProcessorInformation" I got the same error dialog but with "GetL0gicalProcessorInformation" (screenshot 3 below) so I thought that maybe changing the function name could result into something rather than erasing the code completely. In this webpage --> https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoapi-getlogicalprocessorinformation I saw that for the "GetLogicalProcessorInformation" function is required the SP3 update. In the left side of the page are a lot of functions and saw the "GetLocalTime" function that needed only Windows 2000 to work and decided to change "GetLogicalProcessorInformation" by "GetLocalTime" (screenshot 4 below) and the browser launched without errors. I am not sure if this type of modification could work directly but I can tell that when you do this it is probable that you will get another error but will be with a different function. If that happens then you can switch that other function by "GetLocalTime" and see if it actually do something. It will be very strange if this works with one change but I can not test it myself. Other files that have the "GetLogicalProcessorInformation" function are "chrome_child.dll" and "libglesv2.dll". Screenshots: 1 --> https://drive.google.com/file/d/1Zpjmb3nyJZUdAL5hBQgBtiVJe0R6f8Yl/view?usp=sharing 2 --> https://drive.google.com/file/d/1XhUttESaW0lNN7pHTikM7QDqnly9O64t/view?usp=sharing 3 --> https://drive.google.com/file/d/1P1m1KvOSBVpAK_oPhIFLK08LG8N7iRro/view?usp=sharing 4 --> https://drive.google.com/file/d/1yyuxn8j9kG7MZl39K6QZ0Lp9-NZE6x-B/view?usp=sharing Cheers.

The "Switch to another search engine when the default one is not available" option originally showed 3 search engines Bing, Baidu and So. That hex code has the URLs of those 3 search engines side by side and I figured I could disable that option by overriding that code. From the tests I did I think the option originally does nothing but I decided to modify it anyway.

I do not know if some Chromium flag could do something. With respect to your question I do not know anything on why they built the browser that way. Maybe from this link you can get something --> https://groups.google.com/g/angleproject/c/8wo3crBpats

Updated v9, v11 and v12. - Changed the homepage to "chrome://newtab/". - Erased some other stuff on the "chrome.dll" file. I have a backup of the older ones in case something happens. Cheers.

Hello. Test it in v12 for now. The modifications between versions are almost exactly the same, the location is what varies. Can you send a picture of the error you get when running v9 and v11? Maybe something can be done. No, I just replaced those entries by dots. Ok. I wanted to try it to see if I could remove the popup window that shows up on the first run of the browser, but it didn't work. Wow

I think this could be a good option. Is there any way to add that flag directly into the "360chrome.exe" file? The only way I know about is by creating a shortcut and from that shortcut you can add the flag.

@ArcticFoxie I think this could be a good information. I modified every "googleapis" and "gstatic" entries on the "chrome.dll" file and the google connections that appeared on every launch of the browser do not appear anymore (v11). I am not sure which of all the entries are the ones involved in the connections and if this modification could brake something with the browser. Let me know what do you get with this. Cheers.

It's soooo ugly! but... why not eat it, maybe tastes like chicken

Since I started testing this browser last year (RuRepack) what has always bothered me is that nothing came out about the modifications that the Russians made to it as in a blog. I want anyone to be able to know what was done to this browser and why it was manipulated the way it was done. I believe that trust and a good working environment can be formed for the advancement of this browser if at least that freedom of information can be realized. It is like an ideal because I would also like people who do not want to use my modified version of the browser to be able to experiment directly with the original version. I understand your point and I'm not trying to get information out of you or force you to do anything, I just wanted to mention this. I appreciate the information given from you and look forward to continuing to work with you. With respect to the differences between you and @ArcticFoxie I hope it gets better overtime. Not trying to question anything but I respect both of you and I want the best for you as well.

I tested the browser from a clean Win7 machine with TcpLogView and LiveTcpUdpWatch and got no chinese connections (I could not test with WireShark because it did not recognize my modem). The only connections I got were the ones from always. @Gansangriff since you had this event, try to reproduce it, so that we can all look for a solution. I think it is a very nice browser . Chromium-based browsers were almost forgotten for WinXP (at least from what I could see). Firefox based ones got all the attention. I'm not sure why exactly (maybe how easy it is to deal with Firefox's source code relative to Chromium's) but it seems a bit strange to me that it wasn't that much considered and/or possible (at least from this part of the world) to make Chromium compatible for WinXP. With this I am not taking away merit from Firefox based browsers, those who have maintained them have done a great job that I am not even aware of, but, I like Chromium, in my opinion it is more efficient.

Maybe that connection you got is related to a very first run of the browser on a clean OS. @ArcticFoxie I need your help with this, if you can of course. I want you to run the browser (v11) from a clean install of Win7 or WinXP with TcpLogView and WireShark to see if the connection appear. I will also do this but I want to do several tests to see if this occurrence is not that common. WireShark --> https://www.wireshark.org/ Version 3.2 was the last version that was compatible with Win7. Version 1.10 was the last version that was compatible with WinXP. https://www.wireshark.org/docs/wsug_html_chunked/ChIntroPlatforms.html Cheers.

I'm sure that test was not done with my modified versions.

Updated the v9, v11 and v12. There are minor changes to the text in the browser's interface. The "en_skin.srx" was removed but the contents of it where replaced on the "iframe.srx" and "skin.srx" files. I have the previous v9, v11 and v12 in a backup if something happens. Cheers.

It is an interesting behavior. However, I don't know if it is possible to know if the option is activated or not, even when it is checked (after getting this behavior). It is an option that came out from the original Chromium but was removed (from the interface at least) in newer versions so maybe it is not that optional. With regards to the dark theme on v13 I found out a way to partially disable it through the "chrome.dll" file (the connection does not show after this) and that leaves the following options: 1) Erase the dark theme compressed file. 2) Partially disable the dark theme through the "chrome.dll" file (2250) (this change makes the browser to not load the dark theme in all the web pages that displays, it is like the v11 dark theme). Offset (h) = 06ae7e70 Entry "dark" --> Replaced it by 00 hexadecimal values. 3) Keep searching if it is possible to look out for the "qhimg" entry For know I will take 2). In relation to the v13 in general, I will modify the last version of that branch. I am not sure if the "2250" is the last one but I will be modifying that version to know it better after finishing with v9, v11 and v12. Cheers.

Oh. Seems that I missed that one. Nice to meet you to. Do not worry about the time, take it with fun if possible. Hope that you like it! Thanks for that info. I will include it in the modifications as well as the other translation fixes. With the redundancies you say, I know that they can be fixed but I only want to work with them when I can finish with the last translation and text fixes of the browser. I really do not know if modifying those redundancies could make the browser behave differently and/or crash. I want to proceed with caution. For example, if you delete the first "<item type="separator" />" entry in the "fav_menu.xml" file in the "en_skin.srx/iframe/menu" path and then you start the browser and click on the "star button" (the bookmarks manager) and then click the app menu button at the right, the browser will crash (at least for me). I tested this behavior on Win7 and WinXP and it does deactivate. I tested it from a clean unzip. Maybe a modification you added is the cause? Found this: https://www.reddit.com/r/chromeos/comments/a1a9wb/in_the_settings_use_a_prediction_service_to_load/ Unfortunately not yet. I really do not know from which file it is called that action.

Thank you very much for your comment. I will take into account the compressed file. I am really glad for your comment too, thank you for it. But this could not have happened remotely without the help of all those who contributed with excellent information. I hope counting on everyone to continue doing more with this browser. I will try switching between files and if it doesn't work, I will delete all the images from the dark theme zip file to see what happens. Something I want to ask @ArcticFoxie: I know you downloaded several v13 files, From which of them did the developer tools started loading in chinese? I would also like to ask you if you can look in the "resources.pak" file of each one of those v13 versions (if you still have them of course), if the "qhimg" entry is present. Thanks in advance. Cheers.

With regards to that I found out the following link: https://github.com/bircoph/chromium-no-sse2-patch Apparently it is a patch that helps in the Chromium compilation process to not depend on the SSE2 instruction set (for Chromium 35/36). I do not know anything about the compilation process of Chromium or anthing like that in general but I leave this page here if it can be useful to someone capable of understanding it. That's great! However I am almost sure that the modifications I made do not relate to the functionality of Google services at all. I have a strong felling that the Google Voice problem is in the RuRepack version and because of the modifications they made. One thing that they add in the comments every time they post a new version in their page is "the vulnerabilities are closed". I do not know what they refer when they say that. That was one of the reasons that made me modify the original 360EE. Source: https://lrepacks.ru/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html In relation with that I have a problem. In the modification notes of v12 I had to remove a entry in the "resources.pak" file (p7.qhimg.com) and that entry relates to a chinese connection when visiting the bookmarks manager while being in the dark theme. That entry does not appear on the v13's "resources.pak" file (13.0.2250.0) but the connection shows on the v13 while doing the same (so it is somewhere). For the things I could see the "chrome_child.dll" file is gone, the "resources.pak" file is smaller in size but the "chrome.dll" file is bigger, all in comparison to v12. I think that the "p7.qhimg.com" entry is on the "chrome.dll" file but in the compilation process got replaced by other values (not sure). I want to see if in other v13 versions the entry is still missing. If it is missing I could delete the dark theme compressed file on the "skin" folder to not being able to load the dark theme, but I am not really a fan of that option. Cheers.

From what I could test, yes. Thanks! Hope that it works well. I think that the first attempt error you got was caused by the login popup remnant. You have to wait a little when the browser opens for the first time and then press Escape. Ok. Thanks for the info! Cheers.

I just verified the support of SSE2 instructions and my laptop have them. I really do not know if there is a way to avoid that.

@ArcticFoxie I wanted to ask you the following, have you used Google Voice on Ungoogled Chromium? I think I read somewhere that this browser had some unique identifier (do not remember the name of it) that was exactly the same as one of the versions of Ungoogled Chromium (I am not completely sure). So I wanted to see if the Google Voice problem also appear on Ungoogled Chromium since I can not use it on my country. Cheers.

Hello! sorry for not being active on this subject for a while. I was modifying the v9, v11 and v12 versions of the browser https://msfn.org/board/topic/182876-360-extreme-explorer-modified-version/ There you will find my modified versions of the browser with its respectives modification notes. Pastebin did not work for me unfortunately. v13 will be next but I am currently holding on to see which problems this version has. Nice work by the way! Cheers.

360 Extreme Explorer Screenshot of the browser: (360 Extreme Explorer, Ver: 13.0.2250.0, "Chrome" Theme) Modified Version download links: v9 --> (Updated 22/03/23) Version: 9.5.0.138 Based on Chromium: 63.0.3239.132 v11 --> (Updated 22/03/23) Version: 11.0.2251.0 Based on Chromium: 69.0.3497.100 v12 --> (Updated 22/03/23) Version: 12.0.1592.0 Based on Chromium: 78.0.3904.108 v13 --> (Updated 22/03/23) Version: 13.0.2250.0 Based on Chromium: 86.0.4240.198 (Updated 22/03/23) Version: 13.0.2310.0 Based on Chromium: 86.0.4240.198 Archive with all versions --> https://archive.org/details/360EE_Modified_Version See: https://retrosystemsrevival.blogspot.com/2019/05/360-extreme-chrome-browser.html https://web.archive.org/web/20210925152949/https://xpforever.miraheze.org/wiki/360_Extreme_Explorer Note: The changes I made are so many that maybe some little errors related to translation and/or the building of the modification notes can be present so please tell me if you find any. Also, if you want to propose something else, please be aware that I do not have a lot of free time and that at any moment, I could be gone for a while for whatever reasons (I do not intend to be rude with this comment, feel free to speak yourself). If anyone wants to help, it will be truly appreciated. Kafan Mini-Browser Another Chinese Chromium-based browser that seems to be pretty much like a standard Chromium build. Official Page --> https://browser.kfsafe.cn/ Forum --> https://bbs.kafan.cn/forum-298-1.html Screenshot of the browser: Modified Version download link: v1 Version: 1.0.0.121 --> (22/03/23) Version: 1.0.0.127 --> (22/03/23) Based on Chromium: 87.0.4280.66 Folder --> https://archive.org/details/360EE_Modified_Version Observations: - On startup the browser will connect to the website of the search provider selected as default because of the search bar provided on the new tab. - Browser crashing when inserting a USB drive? --> Disable the "Enable new USB backend" flag in "chrome://flags/" (Thanks to @realisty). - Only natively compatible with XP-32bits. It can be used on XP-64bits thanks to @Matias Groen (see XP x64 folder). - Very heavy for old computers. - Doesn't have NPAPI support. Original download link (you can unzip the EXE file with 7zip): http://browser-download.kfsafe.cn/MiniBrowserSetup.exe (currently down) Internet Archive alternative link --> http://web.archive.org/web/20221201234530/http://browser-download.kfsafe.cn/MiniBrowserSetup.exe DC Browser A Chinese Chromium-based browser. The only version compatible with XP is v4 (Chromium 75). Official page --> http://dcbrowser.cqttech.com/home Screenshot of the browser: Modified Version download link: v4 --> (Updated 22/03/23) Version: 4.0.7.22 Based on Chromium: 75.0.3770.100 Folder --> https://archive.org/details/360EE_Modified_Version Observations: - On startup the browser will connect to the website of the search provider selected as default. Similar to Mini-Browser. - All default extensions were removed (the PDF Feature and Screen Capture will not work). You can get them out of the browser's interface through the settings. - Doesn't have NPAPI support. - Has DRM support (Win7+) --> https://bitmovin.com/demos/drm Original download link (you need to install to get the browser files, fortunately you can set the location of the installation): http://file.cdn.cqttech.com/dcbrowser/DCBrowser_1261_4.0.7.22.exe Patcher to retrieve the translation function for all browsers modified --> https://archive.org/details/360EE_Modified_Version Usage: - Inside the "trans_patch.7z" there is a "trans_patch" folder. Extract it. - Copy and paste the folder in the same place the browser executable file is. - After that, enter the folder and execute "trans-patch.bat". - A command-line interface will show up. Depending on the browser you are trying to apply the patches a small question will be promted on CMD. If everything goes correctly the program will show you at the end "Press any key to continue". Press any key, open the browser and check if the translation function was restored. After all that you can delete the "trans_patch" folder. It should work without errors. If anything else happens tell me. Thanks to all the following for the information I could gather for the modification of these browsers: @Windows 2000, @VistaLover, @Sampei.Nihira, @win32, @DragonSC7601, @redapple0204, @blackwingcat, @404notfound, @Cixert, @thebuildone, @ArcticFoxie, @Dixel, The Russian Repackers, @dmiranda, @we3fan, @athlonxpuser and @Greyfox77 I really hope this can help someone, Cheers. - Humming Owl

I just updated the v9. I think this is the final one. The reason for the re-upload was that in the adfilter exception list there were Chinese URLs. I removed those entries through the "chrome.dll" file. https://www.mediafire.com/file/bzpet4joy7y9vcq/360EE_9.5.0.138_Modified.7z/file Here is the pastebin with all the modifications to the browser. https://pastebin.com/XGgXhUtC It was a very hard work, I hope it works well. Cheers.

Deleted comment.

In v9 this are the audio codecs supported by the browser. https://drive.google.com/file/d/1TlLCYieqkpdjmliBvyvtDqSjSHneDaAS/view?usp=sharing https://drive.google.com/file/d/1n5hRjxGk-biyTDOr0dszY69LnBQvHZ7V/view?usp=sharing The info is from https://html5test.com/ In relation to the DRM support, I really do not know what to do (maybe it is a feature that it is added before the compilation of the browser). I will search some info but I think I can't do anything in that area. Everything that can make this browser compatible with most of the stuff of the internet is welcome.