Leaderboard

For starters, Softpedia isn't the official vendor of 360 products, the Chinese firm Qihoo is... The browser linked in that SP page is, in fact, 360 Secure Browser/Explorer (a "relative" of the more widely familiar here 360 Extreme Explorer), which is mainly targeting mainland China and is bundled with Qihoo's "Security" products... Official download page: https://browser.360.cn/se/ Support forum (in Chinese): https://bbs.360.cn/forum.php?mod=forumdisplay&fid=141 https://bbs.360.cn/thread-15948589-1-1.html Newly released version 13.1.6066.0 is based on Chromium 86 core: i.e. the exact same core 360EEv13/13.5 are built on... Unless Qihoo have backported security fixes for publicly released CVEs from Google, I see no real merit on choosing this over the "sanitised" 360EEv13.x versions offered here in MSFN... For those of you feeling more adventurous, "Russian-Board" Forum thread for 360SE: http://forum.ru-board.com/topic.cgi?forum=2&topic=5854&start=0 "X-Portable" Russified+"cleaned-up" packages are linked there-in (but for older version 13.1.1774.0) ... As cautioned by Dave, NEVER run Chinese installers directly (extract the minimum set of required browser engine files and launch via portable launcher...) !

I agree! Recently as posted here by @NotHereToPlayGames: Sorry guys, trying to correct this. Ugh. So this latest build would appear Chromium v86.4240.198 is as updated (and sanitized) as its going to get.

Hello to all! Here is the next update on progress in the development of ProxHTTPSPoxy's PopMenu TLS 1.3 3V3. Actually, the programming work should have ended, but, after further tests I found some new bugs. I could fix them, at least I think so. I hope there are not more. As promised I uploaded a screenshot of ProxHTTPSPoxy's PopMenu TLS 1.3 3V3. Here it is: Looking at the picture you can see two new entries in the pop-up menu, Minimize ProxHTTPSProxy To Systray and Restore ProxHTTPSProxy From Systray. The arrow shows ProxHTTPSProxy minimized to systray. I replaced the new icon of @cmalex's ProxyMII by the old one. More new features are inside my package and not visible in the picture. One thing is clear, of course, the best feature of this package is the TLS 1.3 functionality, provided by @cmalex's ProxyMII. We can't thank him enough for that! Applause applause! More in the next days! Stay tuned! Cheers, AstroSkipper

True...

I can remember very well!

I think it's unlikely. My understanding was that versions after 13.x would not be XP compatible, and in fact would be 64 bit only. Be very careful if you do run that installer and it works, I tried one installer (13.6 I think) and it installed a lot of unwanted crap on my machine!

You are welcome. I hope it/they might be useful to other users, as well. For the sake of clarity, on the "Other Forum" they are suggesting that you "Throttle" the CPU down. I'm sure you understood what they meant. But since people here may not have read your thread "over there", I though it would help to clear things up "here". Most people "here" would assume you mean the Windows 9x CPU patch. Which is completely different than slowing your CPU down "Temporarily" to troubleshoot/play a game. Some "Older" Dos games "do" need a speed tweak, of some kind. I do "not" think Wolf/Sod should require it. If you can run the games in "pure" Dos, even if without sound, then likely speed should not be an issue; in Windows either. But, likely some unique situation(s) exist. Windows adds another layer of complexity, to the situation. Perhaps certain video drivers suddenly support Windows Dos environments better, when the CPU is limited. I apologize for not being more familiar with the "Black Screen" issue you are having. It is highly likely some other user would know more than I. But I have some ideas you could try. It probably won't help, but it has long been suggested to reduce video acceleration, then test if video problems persists. Who am I to argue with many years of trouble-shooters? Just remember to re-enable full acceleration, if it doesn't work. It might not be a bad idea to keep different versions of your video card driver. I seem to remember countless times people needed to upgrade/downgrade their video drivers, to fix various applications, features, and games. It may seem silly, but you could try temporarily installing the VBEMP driver. I've had good luck with the 2010.06.01 version (\VBE9X\UNI\vbemp.inf). On some of my video cards, the newer versions have caused garbled fullsceen Dos windows. But they may work fine in your system. If the black screen issue goes away, then you have "mostly" narrowed the issue down to the video card driver. You could reinstall the correct video driver, and start directing your attention on tweaking that specific device.

https://positivepsychology.com/neuroscience-of-gratitude/ Happy <- at first glance seems attractive, but seeking happiness often (most times) doesn't lead to such (recipe for tragedy) , but recognizing the things (we may take for granted) to be grateful and appreciate makes for a more realistic vision going forward, and sometimes looking back we can recognize those things we mistakenly labeled as 'thins we wish didn't happen' - 'bad experiences' - 'things we wish we could take back' were a lesson and a blessin. https://www.highlevelhealing.com/blog/the-lesson-and-the-blessin Keep your head up, looking down and you could miss the blessings that have been placed in your life, for they helped you to spirit to shine https://www.theodysseyonline.com/life-full-lessons-blessings Just speaking personally .. I wouldn't change a thing doesn't always "correct" mishaps, and sometimes there is no way to reconcile the conflict (Fear and gratitude can't coexist) but doesn't give that conflict any less merit when there is no solid 'blank and white' answer in stone. Most people deal with some level of conflict. When I was younger I didn't notice the conflict because I was unaware (just thought everyone was against me), whereas, now, with eyes wide open, I also (in turn) recognize more conflict but also more confusion (as things make little sense in society). Although I'm less caught 'off guard', the price is a huge wall with no exception for the ever changing tide and removing oneself from life and becoming ad odds and THEREIN paves the way for contradiction. Guilty as charged. That being said: Reality is becoming even more a blur and too much time overthinking with fear and (the dreaded) worry eats away at any resolve and the setback is tremendous.

Hi alacran, just run it from command prompt: WinNTSetup_x64.exe NVRAM NVRAM 1.00 Usage: NVRAM option [ID|DisplayName] Options: (A)dd "full_path_to_EFI_File" "DisplayName" (D)el [ID|DisplayName] (S)etfirst [ID|DisplayName] BootNe(x)t [ID|DisplayName] (E)num E(n)ter UEFI on next boot It's a command line modification of the boot entries and boot order stores in UEFI NVRAM. Kinda a command line version of BOOTICE UEFI options. WinNTSetup_x64.exe CATTRIM CatTrim 1.00 - Only use with WinPE or MinWin installations! This Will delete "non essential" catalogs in \System32\CatRoot folder! Usage: CatTrim "Windows directory" CatTrim will remove most catalogs in \System32\CatRoot and delete or rebuild the cached database in \System32\CatRoot2 folder. That would be fatal for any full windows, but will save some space for a MinWin or WinPE installation. It uses Tools\CATTrim.ini as a list of critical files and lookup what *.cat files hold their signature. It support online or offline installations.

Nothing was changed with VHD creation, maybe your system has a problem with VDS service. I will add differencing VHD creation option to next version. Don't run it from something else that a NTFS formatted drive, that not fully supported.

@daniel_k no IFR setting -> to hard to 1) find exact uefi module 2) find inject place inside module in old leaked AMI UEFI sources, tolud used in NBPEI.c/NBPEIBoard.c, i dont know name of final module VirtualBox: 1) limited cpu support, max 8 cpu on real 4-core cpu 2) ssdt table very simple, no packages/power control and other stuff from real boards: DefinitionBlock ("", "SSDT", 1, "VBOX ", "VBOXCPUT", 0x00000002) { Scope (\_PR) { Processor (CPU0, 0x00, 0x00000000, 0x00) {} Processor (CPU1, 0x01, 0x00000000, 0x00) {} Processor (CPU2, 0x02, 0x00000000, 0x00) {} Processor (CPU3, 0x03, 0x00000000, 0x00) {} Processor (CPU4, 0x04, 0x00000000, 0x00) {} Processor (CPU5, 0x04, 0x00000000, 0x00) {} Processor (CPU6, 0x04, 0x00000000, 0x00) {} Processor (CPU7, 0x04, 0x00000000, 0x00) {} } QEMU: 1) doesn't have SSDT(i use patched 2.11), only DSDT exist 2) DSDT dont have CPU related definitions So it is useless to test cpu related DSDT/SSDT tables on VM because it is amost virtual or stubs