jumper

So we need a plug-in that hides plug-ins from nosey scripts.

Make sure the power Jack is fully inserted into the power socket. Wiggle if needed. The socket might already be bad from too much wiggling.

I'm seeing ads here in Opera Mini on Android 8.1.

Tell us about your hardware.

I think I see the confusion now. While neither of you said it, I think the KernelEx property sheet tab also displays (dimmed) that unique 4.5.120 value (that is neither property nor file version). However, when you look at the KernelEx files themselves: > KernelEx versioning IS very confusing in itself. Not really. The displayed resource version strings are product: 4.5.2, file: 4, 5, 12, 0. Only when using a debugging tool such as Dependency Walker can one see that the binary product and file versions are both 4.5.12.0. Not really a big deal. > but when you open any file properties it does say 4.5.120 By "it" you must mean the KernelEx tab for all PEs, not the Version tab for kex files. This is what took me forever to deduce; please be more specific in the future. > yet all only say "2016" in file properties Again, in the KernelEx tab. This is because of the design flaw that only allows three integer fields. <Edit> Good discussion, everyone :) I think we now have it all sorted out: > I thought 4.5.2 was 4.5.12. Yes: 4.5.2 (product) = 4.5.12 (file) = 4.5.120 (internal/Verify/tab) > KEX 4.5.1 has the Verification result 4.5.110. 4.5.1 (product) = 4.5.?? (file) = 4.5.110 (internal/Verify/tab) The ?? is probably 11, but need to look it up. So 4.5.12 is maybe not "Build 12".... </Edit>

> Yes but if you install it and look under the verification sheet it says 4.5.120. There you go again, not specifying the product version! However, what you are seeing is a debug message that reveals a design flaw in the internal version structure. It is a product version structure with only three fields. Release candidate build 12 of v4.5.2 has files awkwardly versioned 4.5.12.0. In Kernelex.dll file version 4.5.12.0, that was crammed into the product structure as 4.5.120 resulting in a value that is unique to product version 4.5.2, but is not a valid product or file version! So again, please use the real product version when referring to KernelEx or any other software package in use.

USB 2.0 Fortunately, most USB 3 devices are backwards compatible.

There is no version 4.5.120 of KernelEx. Please stop using that number in your posts! The latest versions are 4.5.1 and 4.5.2 (official), and 4.5.2016.x (unofficial). Product version 4.5.2 (final) does contain DLLs with the file version 4.5.12.0. Perhaps this is the cause of your confusion. Unless you need to refer to specific test versions of individual DLLs, please use the correct product version to refer to the standard release as a whole.

Not 100% Also, there have been some regressions in my builds so try v4.5.2 on a clean system.

> one does not display the Exports tab Not all PE files have Exports. Try SHFOLDER.dll and other system DLL's. Also try reregistering pshExports.dll. > The good news is that the control panel daemon still runs without rundll32.exe running as well. Any modules that are run via rundll32.exe need to have explicit modes set. Rundll32 itself should be mode disabled.

pshExports_alpha1.7z Install: regsvr32 pshExports.dll Usage: View Properties of any PE file with exports and select the new Exports tab (to the right of KernelEx) Tip: click the selection box beneath the vertical scrollbar to change the display from Named Exports to Ordinal Exports

But why were none of these HALs installed?

Maybe the new hal.dll is experimental and is not installed by default because it doesn't work on all hardware.

When prompted to reload drivers after a small change, try the "skip" option.

Backporting an app requires recompiling that app, not XomPie. XomPie allows some apps to run without being backported.

Redirection applies only to standard output, not to error output.

USB doesn't use LBA. If 9x can see it (another limit might exist), it should be safe to use.

Update the XP64 4500MHD drivers.

But first your bios must have LBA support for > 137GB. If not: backup the HDD, repartition, then restore. BTW, USP3 and Kex are still not fully compatible.

> It just works Until it writes past 137 or you scandisk in dos or... If you don't want to patch the os, use 120 or smaller internally. Larger is okay externally, USB fw lan.

New MSI file support is planned for the upcoming advanced fork.

Maybe do a New Hardware search from the Control Panel.

Mobile at the moment. 4.5.110/120?

4.5 introduced the driver that patches modules in memory instead of on disk. That hasn't changed a bit (yet). However "KernelEx" is now overused, so maybe k4xp and kfive/k5? Possible additions to the driver include rloew’s i686 + my finesse sse exception handling, and Wdmex code.

I'll add to the Sheet Todo list an option to customize the target filter string. Then wildcards could be added with no restarting needed. It could also search for conflicts and even create a dated backup. The current plan is to fork the project with ongoing development continuing as 4.5.2020. 4.5.2016 API support will then be slimmed down to XP and below for stability. (Kexstubs will still be supported.) (Or should 4.5.20 be the slimmed version and 4.?? or 5.0 the ongoing?)