Leaderboard

I also don't see how frank was rude at all, sounds like you could use an emotional support animal.

I see no rudeness whatsoever in Frank's post. Yours, OTOH, is unnecessarily offensive. People nowadays are too oversensitive...

You can force "multiprocess mode" (aka "e10s") in Firefox 52 or @roytam1's Serpent 52 and 55, by creating the Boolean preference browser.tabs.remote.force-enable and setting it to true. This splits Firefox or Serpent into two processes. To allow more than two, set dom.ipc.processCount to a value greater than one (i.e., setting it to 2 allows 3 processes, etc.) Don't try this in New Moon, though; it will crash! It doesn't work in BNavigator or IceApe either; setting the above preference makes it appear to work in about:support, but Windows Task Manager nevertheless shows only one task no matter how many tabs are open. Edit: Summarizing what was discovered below, this preference is required to enable e10s (multiprocess mode) in FF 52 on Windows XP. But with later Windows versions, or some other FF forks on XP (confirmed with Serpent 55), you can instead use the preferences @VistaLover recommends in the next post: toggle browser.tabs.remote.autostart from false to true, and if necessary (due to add-ons flagged as incompatible with e10s), toggle extensions.e10sBlocksEnabling from true to false. In Chrome, each tab is a separate process; but in FF the maximum number of processes is limited by that preference. If you open more tabs than that value, tabs will begin to share processes vs. creating new processes.

1. in german its not filter output but search. i tried but i think was unsuccessful or made something wrong. maybe due to wrong lav-files. standard lav not mmx. we will see. but i simulated except the .mp4-filtering and using standard-lav-files worked. sorry had overseen mp4 in search window. will test again and tell about outcome in SSE. On XP-SSE2-PC in next weeks. Thanks a lot

Good. So, now that I gave it it's own topic, I hand to you the task of giving it a proper title (unless you think the one I gave it is good enough).

^^^Destro, this is on modern computer in virtual machine for testing purpose, I would not even dare to try it on PIII hardware. I have a collection of 9x dedicated machines and a collection of 9x compatible graphics cards, some of these machines are strong enough to do all the things you mentioned. ^^siria It is Kex 20 and it is set to "Alias for Base enhancements (old)", if i set compatibility to win2k it just show blank page and cannot load any page. No crashes at all, but can not display text. ^jumper, I think this is some sort of configuration issue because the same thing happens to Aurora 7.0 and Firefox 10 if they are set to "Alias for Base enhancements (old)", if is set to any other mode it crashes during startup. But on another VM where i have installed Win98Fe + SP 2.5.8 + Kex 20 both Aurora 7.0 and Firefox 10 work correctly if it is set to "Windows 2000 SP4 (Multi-Threaded)", if other mode is set it can not display text. On that installation KM 74 can not be started at all, it crashes during startup. K-MELEON caused an invalid page fault in module KEXBASES.DLL at 015f:bfa4b9c9. Registers: EAX=00000000 CS=015f EIP=bfa4b9c9 EFLGS=00010216 EBX=00000000 SS=0167 ESP=008cdb24 EBP=008ce050 ECX=80007878 DS=0167 ESI=044fa3a0 FS=0f0f EDX=80004f68 ES=0167 EDI=7d00fe86 GS=0000 Bytes at CS:EIP: 0f b7 00 3d 5c 5c 00 00 74 1e 8b 45 08 0f be 40 Stack dump: 000016d7 014f2737 12a70000 014f2737 3d76ab94 000416f7 10e90000 00000903 ab9416d7 db563da6 0000008c 00470000 04700470 00000000 00000000 00000000 KM_ApiLog.7z

Well, while what you suggested would indeed work for FxESR52, you need not create a new pref to initiate e10s; already existing prefs control multiprocess activation in the browser: browser.tabs.remote.autostart;false Toggling that pref (to true) and restarting the browser will enable e10s; in the event you have installed conflicting legacy extensions, you should also toggle (to false) the following pref: extensions.e10sBlocksEnabling;true (followed by a new browser restart) The number of additional processes can be manually configured via the following about:config pref: dom.ipc.processCount;1 The default value of 1 means that when e10s is enabled, one additional content process is spawned (two overall present in Task Manager); modify to 2 and you'll get three in total and so on... But the multiprocess support present in Firefox 52 (and UXP) is not that mature and increasing the value to high figures (>= 4) will probably result in adverse effects (e.g. I have experienced frequent crashes); also, the more processes you configure, the better CPU you should have (e10s works best with recent, powerful, hardware... ). JFYI, the Moonchild Productions developers are currently in the process of removing any multiprocess code still extant in their UXP code tree, as they do not endorse e10s; Pale Moon never supported e10s, the same fate awaits official Basilisk (and hence Serpent 52.9.0); this is being tracked in UXP issue #953

I have had this occasionally happen to me. Usually it's just a faulty Windows attempt to mount the disk. On every occasion just pull out the disk and, usually, on the second or third attempt at reinserting the USB plug the drive starts to work again.

Well, you're much welcome to vent up. So am I to rant, right? Yeah, it goes like this: 1.) All the issues you mentioned have solutions described in detail in this very forum. 2.) Athough it's easy to filx the Word 2010 issue, one can remain using Word 2000 (or even Word 97) for most if not all tasks commonly performed with it. Same goes for XL and Powerpoint. 3.) Al that is required is to arm oneself with patience and read the threads where the solutions are described. XP went EoS, then POSReady 2009 went EoS. MS did it because it was in their power to do so and they've decided it was in their interest to do so. Regardless of what any of us thinks about it. So it's up to us, the die-hard users, to support ourselves 'n one another... it's less confortable than leaving all responsibility fall on MS. Then again, for one who loves XP or just isn't confortable (or able) to cave in, it sure is worth it. One may whine. Then again, one may stand up and fight. Long live XP!