Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


jumper

KernelEx 4.5 Core Updates (4.5.2016.17)

Recommended Posts

15 hours ago, jumper said:

@MiKl: I use SM2.0.4 but not the email client. Please narrow the problem down to Kexbases.17 or Kexbasen.17. .18 is packaged and awaiting final review. Kexbasen.16 exported 11 new print dialog functions--access them via Kexstubs.

Hi Jumper, the email-problem seem to be caused in Kexbases.17 ! When using v16 it works again.

I will look into the printing issue but unfortunately I believe I do not understand excatly what you mean.

Share this post


Link to post
Share on other sites

> the email-problem seem to be caused in Kexbases.17 ! When using v16 it works again.
Good. Now try comparing api logs (DebugWindow.exe). In Filter Settings, include "(bfa" to limit output to kexbases apis.

> I will look into the printing issue
In Kstub823.ini:
  [Comdlg32.dll]
  PrintDlgExA=>Kexbasen:PrintDlgExA_new
  PrintDlgExW=>Kexbasen:PrintDlgExW_2
  PrintDlgW=>Kexbasen:PrintDlgW_3
Check Kstub823.log or include filter "PrintDlg" to see which api to focus on.

Edited by jumper

Share this post


Link to post
Share on other sites
On Freitag, 26. Januar 2018 at 9:40 PM, jumper said:

> the email-problem seem to be caused in Kexbases.17 ! When using v16 it works again.
Good. Now try comparing api logs (DebugWindow.exe). In Filter Settings, include "(bfa" to limit output to kexbases apis.

Even with this filter in place debugwindow.exe lists hundreds if not thousands results.
Do you have maybe an idea what I could specifically look for - maybe 'createfile' or 'writefile' ??

Share this post


Link to post
Share on other sites

Allo !

It seems that one XMPLAY plugin to allow RAR compressed files use is broken since at least Release 4 on my machine with Win ME + RP9.7.2 + the new service pack, same configuration works properly with vanilla KEX 4.5.2.

I tested 4, 5, 7, 8, 9, 10, 11, 16 and 17 and with all of them the program dies with "corrupt data!" message after which it enters into endless invalid page fault error box throwing state, unkillable by any means so you got to do a hard reset to the machine in order for it to be shut down. Vanilla 4.5.2 has the program working fine without any sort of problems. I removed Kstub822 for testing purposes and it made no difference. All versions were tested by restoring Kex to 4.5.2 prior to updating the relevant files of each release. Disabling KEX extensions on the program would allow the plugin to work but since there are other plugins that do require KEX that isn't an option, also enabling ANY compatibility mode will cause the program to exhibit the problem.

I ended up looking for any possible updated version of the plugin and there is one which does work without problems, but that still won't address that there seems to be some sort of problem in the updated KEX that might affect other programs. Here's an archive that contains the problem combination for debugging/analysis : http://www.tmeeco.eu/Fileden/XMPLAYcrash.RAR

Nearly all other programs used on that machine seem to work without any surprises. (The one that doesn't won't work with Kex4.5.2 either so no discussion about it will happen here as per rules of this topic).

Thänk you for all this great work ~

Share this post


Link to post
Share on other sites

XmPlay and all the official plugins (which includes the Rar plugin) don't need KernelEx at all AFAIK, they still run on vanilla 98SE/ME.

Share this post


Link to post
Share on other sites

I use bunch of Winamp plugins with XMplay due to lack of native plugins for those particular formats and there are some that require help from KernelEx.

I also tried some older versions of XMplay and versions 3.4.1 to 3.5.1 crashed with an invalid page fault on startup unless extensions are disabled. With vanilla 4.5.2 they run fine.  Versions starting with 3.6 work fine up to the very latest one, I haven't tired any of the older versions to see how far back the particular problem goes.

Share this post


Link to post
Share on other sites

@MiKl: use Kexports+fc on Kexbases.dll to isolate the API changes. SetFilePointer is a likely candidate.

@TmEE: So don't use the new ME service pack. It clearly hasn't been fully tested and is using files that aren't compatible with KernelEx. You can also try disabling Kex extensions on _all_ files installed by the pack. And you should also uninstall Kex and reinstall with mode default: Disabled. Manually enable Kex on only those files that need it.

Share this post


Link to post
Share on other sites

The problem is not coming from the service pack. I just made a new installation and added nothing but KernelEx 4.5.2 to it. Old versions of XMplay worked fine then, including the crash test I set up, no invalid page fault error or that "corrupt data" message.

Then I upgraded vanilla KernelEx 4.5.2 to the release 17 and the old XMplay versions stop working and the crash test starts crashing so the problem is definitely introduced by updated KernelEx.

Share this post


Link to post
Share on other sites

Hey, Tiido! Great to have you around here again! :hello:

Share this post


Link to post
Share on other sites

@TmEE: Please follow my instructions.

Share this post


Link to post
Share on other sites

I didn't report this in this thread but, the newest extensions broke portable qtweb 3.85 for me in 98se.  I could only use vanilla kernel ex. 

Share this post


Link to post
Share on other sites

On July 16, 2017 I reported problems with installing DOTNET 2.0 (DOTNETFX20.EXE) in combination with KernelEx 45201617. After making a fresh Windows 98SE install to get rid of U98SESP3.56 and returning to last Dutch servicepack (sesp203nl), al reported problems were gone. I don't know why. :rolleyes:

But the problems with DOC/DOCX conversion when using Compatibility Pack for the 2007 Office system (FileFormatConverters ENG, version 12.6500.5000) were still there (see my report on June 29, 2017). I found following "workaround". Redirecting SetFilePointer to std didn't work when used in compatibility mode W2K or lower. Somehow I tried to incorporate KERNEL32.SetFilePointer=std in the higher W2K3-mode (I never use this mode). It worked when setting the two involded exe's in this modified mode (WORDCONV.EXE and MOC.EXE).

Without these settings I saw in the log files generated with KexApiLog SetFilePointer asked by OLE32.DLL only. With KernelEx disabled on OLE32.DLL NO log-entries anymore (except the ones that SetFilePointer is a new stub). I was very surprised to see when I filtered KexApiLog on SetFilePointer there was an instance left in the log-window:

Depth Thread Info Return
2 ffe3cbd3   [WORDCNV.DLL]31332b8c:<KERNEL32.DLL>SetFilePointer(bfa4d37d)
2 ffe3cbd3   [WORDCNV.DLL]31332b8c:<KERNEL32.DLL>SetFilePointer = ffffffff

Setting my modified compatibility mode on WORDCNV.DLL only was enough to convert DOC/DOCX again in combination with KernelEx 45201617.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×