Firefox Para Windows 10 Pro
Taj Lash
I would like to express my thanks for the work. Jumper, I know you've spent endless hours with the further development of KernelEX. I'm able to run Firefox 35 and even 52.9 and see almost the whole contents of the web on Windows Millennium again.
Explanation: Xul.dll is set to 2k in the Registry (HKEY_LOCAL_MACHINE\SOFTWARE\KernelEx\AppSettings\Configs). This string entry *\XUL.DLL="NT2K" can be deleted to get the file in follower mode (default). Reboot required. 2k mode was set on Xul for older FF versions like 9.0.1.
* Adding bookmarks doesn't work (also the popup - dialog window doesn't occur). Recently visited addresses aren't saved. Partial solutions: The History and the Bookmarks created on XP+ can be used on ME/98. Copy the file places.sqlite of your Firefox profile on XP+ into the profile folder of Firefox on ME/98. And there is the bookmark extension PlainOldFavorites.
* Firefox crashes with Adobe Flash plug-in activated. Make sure that this plugin is disabled. If it is still needed, deactivate the plugin container: dom.ipc.plugins.enabled;false and dom.ipc.plugins.timeoutSecs;-1. The boolean "dom.ipc.plugins.enabled" has been removed with version 43.
Problem solving: With the first run you can remove search engines you don't want from the Search Engine Manager list and then set the search.json file in the profile folder quickly to read only. After that add your favorite engines and set a Home Page. Restart FF and check the functionality. If the first attempt fails, delete "search.json" and "searchplugins", restore the original state (Restore Default Search Engines ...) and try it once more. If you despair, delete (or rename) search.json , create an empty text file, rename it to search.json and set it to read-only before you start the browser.
* Low GDI resources - Possible problems with programs starting/running at the same time. Open about:memory and press "Minimise memory usage". The addon FreeMemoryButton allows to minimise memory with one click only.
* Sometimes I can't close Tabs after a while. Restart Mypal when it annoys.
* Sometimes - Error in Xul (browser restart required)
A safe method to troubleshoot is to run the portable version on XP once. Afterwards on next start on Win ME/98 the functions "restore previous session, recently closed tabs and recently closed window" work and the pages load as they should. On XP Firefox repairs garbled created data profile files.
* Firefox freezes or crashes on some websites. Disable Javascript or CSS/Style Sheets for these sites. The extension QuickJava allows you to rapidly switch Javascript (JS), CSS/Style Sheets (CS), Images and more. Depending on the system, it may make sense to deactivate Javascript permanently. There are reports of systems in which JS does not work at all. Add "user_pref("javascript.enabled", false);" in profile\prefs.js or open about:config and toggle "javascript.enabled" from true to false. FF42 and the higher versions are less affected. If a website suddenly stops working and Firefox crashes, then clear the Cache (Tools>Options>Advanced>Network>Cached Web Content>Clear Now) or delete it in the folder (e.g. FF32+: FirefoxPortable\Data\profile\cache2\entries).
* Firefox could crash when opening a new tab. Open about:config and set "browser.newtabpage.enabled" to false. This leaves the new tab blank. It's possible to modify the string "browser.newtab.url" with a search engine or another url of your choice. FF42 and higher versions haven't the string "browser.newtab.url" anymore. You can use the ClassicThemeRestorer to set an url.
Apparently the glitch is related to OMTC (offmainthreadcomposition). From version 33 on OMTC is enabled by default. Switching "layers.offmainthreadcomposition.enabled" off solves the glitch, but makes versions 33 - 35 unusable. These versions eats up the GDI resources and Firefox will crash sooner or later. Versions 42 - 48 and also Icecat 38.8 are probably not affected, so there is the possibility to disable OMTC.
Versions 33 - 35.0.1: The problem can largely be avoided, if you don't start and run Firefox with maximised window. Reduce the window size a little bit. Other possibilities: Click "Show Desktop" on Taskbar twice to refresh the Firefox interface (UI). You also can press F11 (Full Screen) twice or leave FF with Full Screen. Then it starts with Full Screen again and afterwards click F11 to exit that mode.
Versions 42 - 47.0.2: Click "Show Desktop" on Taskbar twice to refresh the Firefox interface (UI). Usually it is sufficient to press the button twice after starting. Or: The boolean "layers.offmainthreadcomposition.force-basic" doesn't exist anymore, but if you create it and set it to true, it's possible to start and run FF with a slightly reduced window size without this UI glitch.
* "browser.search.showOneOffButtons" => false to restore Firefox's classic search where you could see the favicon for the current search engine (FF33 - 42). However, the new search should be a bit faster.
Use portable versions or create different profiles for the installed. In the second case call the Profile Manager (Start > Run > ..../firefox.exe -P) or open "about:profiles" (Firefox 46+ only) and start the Profile Wizard.
All my observations, tests, and findings were on real machines and not on a VM. All processors (Intel) meet SSE2 or higher and memory sizes are 2 and 3.5 GB RAM. The graphics cards are NV GF7800GT, NV GF7900GS and NV GF5900XT(AGP). And my OS is Windows Millennium.
You can try this, but first it is easier to paste MEdll.dll into the Firefox program folder, here ... FF35.0.1Portable\App\Firefox. I see "App folder" is ambiguous. There is no need to register a dll file. And make sure that you really set xul.dll to XPSP3, too. Then the XPCOM error should go away:
I tested as following instructions and FF35 still wants to load XPcom.dll. What I do not understand is the MEDLL.dll how is this involved? If NTDLL of another OS is placed in the Windows directory along with the correct Kernel32.dll it slows down system but still operational last time I checked. In WinME NTDLL is loaded first and it is solely directly linked to ME's Kernel32. NT based OS' s load the other way around Kernel32 first. What might be able to be done is to search for files altered in the time frame of when you got FF to work and see if other modes are necessary.
It depends on whether the DLL is in the mapped paths. A Dll can only be registered if it contains function DllRegisterServer and is said then to be self registering. When installing, a program can write the necessary registry settings if the Dll does not self register. If the Dll is in the same folder as the program then the program does not need the registry to find it. If outside the set paths then it will not be found if not registered. In KernelEx folder/subfoldereds the the Dll has to be KnownDll registered for kernelEx to use it. Dlls are shared and icons need to be directed/selected that are within the Dll. They can do direct decoding all types of stuff and generally if it has DllRegisterServer then it should be registered. If within the Dependency Walker Dll tree there is NTDLL and NTDLL has all red Dependency Walker imports, no input functions compatible, then the DLL may still register but may not work. If there are some compatible imports (green) then the DLL will not register.
Of course, don't use the ntdll.dll of 2K or XP named ntdll.dll in the windows/system directory. A renamed ntdll.dll to MEdll.dll doesn't hurt your system! The patched Firefox don't need the ntdll.dll, but MEdll.dll. That's all.
I think if we compare KernelEx ApiLog results it might help but it is good that you have it running. There is no altered file dates in the download except prefs.js, they seem to represent the original and this is why I don't understand the MEdll mod how is this file involved?
I just rebootet without Kstub823 and I write here on FF 35. I will make list of XP files in my system folder, and I would like to add, that I'd installed hjsuffolk14's me service pack on the test system. Currently I'm at my main machine, but at the moment I 'm not sure, if that SP is installed.
If you use Process Explorer or CodeStuff Starter while FF is running it will show what files are used therefore narrowing down the files to just the ones used. Process Explorer will show version numbers - a lot more info than Starter but I use both. I think from memory PSAPI has to be removed from Starter.
When you put the NTDLL of another OS in the KernelEx folder/subfolder and registered it in the KernelEx known Dlls, if you use one of the above programs I mentioned you will see that the NTDLL in the KernelEx folder/subfolder is not loaded and therefore is not used and does not play any role in the operation of the operating system. It cannot load unless all its import functions are linked except any forwarded functions and forwarded functions although shown to link in Dependency Walker do not work with WinME. Forwarded functions are shown in DW having an arrow pointing down with a blue folder like symbol.
I will try the ones that are different to mine. The MSVCR100 and MSVCP100 were the ones in the FF program folder? When profiling with DW the first thing that comes up is the message couldn't load XPCOM then after acknowledging this the profiling begins. Straight away there are many red can not hook modules then it reaches the all implicit modules loaded successful point. So DW is not going to display properly when the modules can not be hooked I would think. In saying that though, it says that there is a memory location 998 problem of which I have encountered with other profiling. The other thing is I have WTSAPI32 have you got WTSAPI32? My WTSAPI32 will not load though : - missing functions and disabled in KEX. Yours did not load either as shown in PE unless you had not included it.
d3342ee215