Firefox 24 - 52 for ME and 98

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[schwups]

Which are broken? You must be logged in on this forum.

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[schwups]

KERNEL32.DLL:VerSetConditionMask: This happens, if the exe isn't set Win2000SP4 or higher. KernelEX supports VerSetConditionMask. Make sure that the Firefox.exe and the portable exe are set to XPSP2 or XPSP3.

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[schwups]

Does Firefox 31 or 35 run on your machine?

9 minutes ago, MSwin98forever said:

This error was fixed when I set "XPSP2" in registry

Why don't you easy set XPSP2 on the KernelEx Tab of the Firefox.exe file?

11 minutes ago, MSwin98forever said:

KERNEL32.DLL:IsProcessorFeaturePresent.

KernelEx supports IsProcessorFeaturePresent. So I think there is something wrong with your KernelEx installation.

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[schwups]

Did you run KernelEx\verify.exe? 

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[schwups]

Please check, if Opera 12.02 or 11.64 (Win2000SP4) run to verify 4.5.2. That's not needed, if you can run Firefox 31 or 35.

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[schwups]

Now look at the Help page on the KernelEx Wiki. Do you have the correct unicows.dll version in your system folder?

Ok, now I saw your upload. I recommend to reinstall KernelEx. It seems you chose the third party installer for the core updates (24). This installer isn't tested here! It installs incompatible reg files of version 18! And delete exact these registry entries of LZDLL.reg and API-MS-Win.reg before you install KernelEx again.

Edited October 30, 2021 by schwups

[MSwin98forever]

.

Edited February 22, 2022 by MSwin98forever

[Goodmaneuver]

39 minutes ago, MSwin98forever said:

MSVCR120.DLL associated with the missing component KERNEL32.DLL:IsProcessorFeaturePresent

IsProcessorFeaturePresent is deactivated by Core.ini for non-NT modes but these lines can be removed. Make sure that Msvcr120 has an appropriate KernelEx setting and that there are no conflicts in the registry in the Kernelex AppSettings, Use a search to see if there are more than one setting for each module, that is, you can not operate with say a mode setting for MSVCR*.DLL of DCFG1 and have MSVCR120.DLL of Win2K nor can you have any with a mode setting and also be disabled, that is, a 1 set in Flags. I use MSVC*.DLL = DCFG1 at this stage as DCFG1 at the moment supports all necessary function requirements.