schwups
Content Type
Profiles
Forums
Events
Posts posted by schwups
-
-
No - https://msfn.org/board/search/?q=sound&quick=1&type=forums_topic&item=181424
I myself have no sound problems, but it happened on VM's. What kind of system do you have?
-
I guess I took that 7.0.3790.4341 (srv03_sp2_qfe.080724-1204) (346KB) from Win2000 Extended Kernel. Therefore Msvcrt.dw7 from Dx9W2kFx.zip is another one I don't have.
-
On 1/26/2022 at 2:09 PM, Goodmaneuver said:
The character limit was solved with Kstub825.dll. Apart from increasing the limit a little over Kstub824 what is done is have 2 or more INIs and 2 or more Kstib825.dll files in the KernelEx folder. So you use Kstub825.dll and copy this file and rename it Kstub826.dll for example then have corresponding INI's of the same names in the KernelEx folder. You then split the definitions across the 2 or more INIs.
Now obsolete:
Known issues:
plug-in limit is 4: std + kexbases + kexbasen + two more
Does this mean unlimited plugins are possible? Do you have already Kstub825.dll?On 1/26/2022 at 2:09 PM, Goodmaneuver said:To overcome MSVCRT missing functions I suggest using Win2K3SP2's MSVCRT as MSVCRT. Schwups you know this file works if you redirect NTDLL NtClose to GDI32 DeleteObject. This has the advantage of having ??0exception@@QAE@ABQBDH@Z function where as any other known substitute did not have this. It works with VLC and there are no useless functions that are not used as it is a real MSVCRT. MSVCR70 as a MSVCRT substitute is pretty good but it did stop DivX Player and you will gain these functions over those of MSVCR70.
??0exception@@QAE@ABQBDH@Z
__CppXcptFilter
__CxxFrameHandler2
_abs64
_get_heap_handle
_mkgmtime
_mkgmtime64
_rotl64
_rotr64Once using the 2K3 MSVCRT Black Wing Cat's GDI wrapper Msvcrt.dw7 from Dx9W2kFx.zip can be used by directly linking the DLLS that require it. (I do not know where Dx9W2kFx.zip is located on the WWW now) This will improve the processing speed over using Kstubs as function redirection. Add these in Kstubs for BWCCRT where BWCCRT is the name of the Msvcrt.dw7 wrapper as they were not included and are redirected to MSVCRT (2K3).
[BWCCRT]
??_U@YAPAXIHPBDH@Z=>MSVCRT:
??0exception@@QAE@ABQBDH@Z=>MSVCRT:
??2@YAPAXIHPBDH@Z=>MSVCRT:Yes, I tried MSVCRT (BCW) repeatedly. In practice, however, I do not recognize an advantage over msvcr70 and I don't use a DivX player. Both files have a few differences, but they are very similar. These had no discernible effect on my browser tests so far.
To make the versions clear. The 2kSP4 file version I have is 6.1.9844.0 (281KB), BCW's is 7.0.3790.4341 (srv03_sp2_qfe.080724-1204) (346KB), msvcr70 (332KB) 7.0.9981.0 and the ME version is 6.1.8637.0 (285KB). And finally there is latest version 6 (273KB) 6.1.9848.0 and msvcr80 (572KB) version 8.0.40607.52. All are basically usable.
-
2 hours ago, Goodmaneuver said:16 hours ago, schwups said:
A Tool counted more than 17000 letters.
What tool was that?
Wortgenerator/wordcreator: https://www.sttmedia.com/wordcreator
- Additionally integrated Counter for letters, characters and syllables
I used the old version https://www.sttmedia.com/download=WordCreator.
I haven't tried the new on ME.
2 hours ago, Goodmaneuver said:Vista does not like saving a reg file download it seems so could you rename APISetStub a txt or zip it?
changed
-
My Kstub.ini had exceeded the character limit, too! A Tool counted more than 17000 letters.
Here is my ini file (Not too many characters/ trimmed notes) also with latest definitions of jumper. It is experimental and it's still not suitable for Firefox 57 (Quantum) or Serpent 55 or Chrome based browsers.stubs.7zSupplement: APISetStubreg.txt
Menu/submenus problem K-Meleon - quite interesting but a bit obsolete now, because that is not suitable for K-Meleon76:
The replacement of K-Meleon.exe version 75.1 (Gecko31) by 75.0 makes the submenus readable. K-Meleon.exe 75.0 is compatible with KM 75.1.
I only had replaced the Kplugins bookmarks.dll, favorites.dll and hotlist.dll by those of 75.0.
Then I had changed version info of the exe with ResourceHacker and Hex Editor from 75.0 -> 75.1.
A small blemish or side effect is that there are question marks in the OS titlebar as with version 74.Furthermore, I began to test Win 7 files. Currently used APPHELP.DLL, AUTHZ.DLL, GDIPLUS.DLL, NTDSAPI.DLL, RASMAN.DLL, REGAPI.DLL, SAMLIB.DLL, utildll.dll, W32TOPL.DLL, WinSCard.dll, WINSTA.DLL.
Not used: DNSAPI.DLL. Icecat38 doesn't start with ACTIVEDS.DLL, ADSLDPC.DLL, MPRAPI.DLL, RASDLG.DLL, RTUTILS.DLL. Prolonged testing could reveal more problems?
I also began to test IE8 and 11 files and some more system files.
Also used: XP 5.1.2600.6198 Imagehlp (but usually 5.0.2195.6613 2KSP3)My tests with msvcrt of XP, Vista and 7 are still unsuccessful.
-
-
If someone wants to tinker something this year:
NewMoon 28.10.4a1
Don't expect everything to work (see issues).
- missing magnifier icon in search
- missing folder icons (PlainOldFavorites/Favorites)Solved: Try - Set KernelEX mode on palemoon.exe to Vista or higher.
1. Extract NewMoon
2. Replace three files with those of MyPal 29.3:
mozglue.dll
omni.ja the one next to palemoon.exe
Xul.dll3. Add MyPal 29.3 file: gkmedias.dll
4. Alter platform version with a HexEditor:
PaleMoon.exe version 4.8.3 -> 4.8.2
or
Xul.dll 4.8.2 -> 4.8.3and I wish you all the best for the upcoming new year
-
1
-
-
I am for improvement and I will probably not miss the legacy modes.
-
It's mentioned here somewhere, but I had not yet investigated this in detail. I am basically not interested in cookies, so I usually have set "Keep until I close Firefox". Not all versions may be affected. It may help to run the portable version (profile) on XP once and set there "keep cookies". I'm currently using NewMoon 28.9 and it does save them, if desired.
-
-
IE9stubs.ini:
On 9/27/2021 at 7:45 PM, jumper said:Unnamed (ordinal) functions and data variables are not yet supported.
Jumper, have you made progress? I don't think that I can run IE8/9 without support for the ordinal functions.
-
8 hours ago, mzltest said:
(import all /System32 *.dll from win XP to KernelEx folder
Import the dll's into a separate folder and do not mix in the KernelEx folder. Choose the 21 XP dll files and GDIPlus.dll for KM76 and paste them into the 98 system folder. Don't substitude win98 system files. Restart from the scratch could make sense.
8 hours ago, mzltest said:Thats all you need for Firefox 24 - 35.
Install KernelEX 4.5.2 and then overwrite (copy) the old with the new KernelEX files in safe mode (F8).
KernelEx Folder (version 24):
Note:
https://msfn.org/board/topic/181424-firefox-24-52-for-me-and-98/?do=findComment&comment=1207100
8 hours ago, mzltest said:And in Update 18,besides LZ*.reg ,there is another reg files that is API-MS-Win.reg .Shall I install that reg file?
The knowndll registry settings are required for Firefox 49 and higher, not for Firefox 45. The API-MS-Win.reg of 18 is a test file, but incomplete to run Firefox 49+. I do not recommend it. Merge the reg entries of the txt file linked on the first page only!
8 hours ago, mzltest said:Finally,do I need to install system updates(Is my Win98 SE,4.10.2222A,too old for this)?
A ServicePack isn't required to run Firefox.
-
Your primary aim is to run Firefox 45. So use KernelEX 24 with Kstub823 first and follow exact my instructions. Make sure that you have all required and correct dll files in your system folder. XPSP2 files are preferred for the first attempt. You can also check and profile with DependencyWalker, that you have all needed Dll's (see Modul List View / yellow question mark symbols). Make sure that you have not LZDLL.reg entries (KernelEx update18) in your registry (Firefox will crash on start). If everything works, copy the KernelEX folder as backup and then you can test and update to KernelEx25 / Kstub824. The Core.ini 24a is is largely untested!
-
10 hours ago, jumper said:
.... and find for both 6 and 7 the last combination of files that worked with Base.
KernelEX24 (Kexbasen/Kexbases): I haven't noticed any problems in this regard, but I have certainly not tried all of the modes. I am sure that default, Base and Basesn modes are OK. As we said, the problem apparently starts with Kexbases25.
-
1
-
-
The complete list for Win ME/KernelEX25:
Working modes (MSVCRT):
Disabled
BASEstd
BASES
MIN
WIN2Kstd
Not working modes:
default
Base
BASESN
BASEN
WIN95 up to WIN10A (except WIN2Kstd)
all legacy modes
98SE: Quick short tests produced no errors with all Kex modes on MSVCRT.
-
1
-
-
3 hours ago, jumper said:
=- deletes the entry.
Msvcrt 6/7 should also work in Base (with the heap enhancements).
Revert any kexstubs.ini definitions and find for both 6 and 7 the last combination of files that worked with Base.
BTW, nobody should be using kstub24.ini directly. It is a sample file with new instructions and examples.
On ME, the dbghelp->lz32 redirection should not be used. It is for 9x only.
0x80 is the definition valid flag.
Thanks
MSVCRT also works in Bases and Win2000 standard heap, not in Basen and Basesn mode.
-
Goodmaneuver thanks, now I've ME running with Kex25 - Kexbasen and Kexbases. I simply changed my favoured kexmode BaseSN on Msvcrt.dll (7.0.9981.0) to "Base enhancements standard heap". It can be so simple. Jumper, I don't think, that it's intended, but rather an issue, that Basesn and probably higher modes on Msvcrt.dll lead to this error. Sure, that need more checks and a fresh KernelEX installation to verify this. This KernelEX registry key is very old here . Indeed, the problem appears to be primarily related to MSVCRT. The original MSVCRT registry entry in KernelEX 4.5.2 settings.reg is: "*\\MSVCRT.DLL"=- ([HKEY_LOCAL_MACHINE\Software\KernelEx\AppSettings\Flags]). Not sure what =- means. I guess due to my experiment with the fresh installation of ME and KernelEx the setting on msvcrt have to be changed on Win ME.
-
3 hours ago, jumper said:
Clicking on the button causes the error a second time?
KernelEx must be disabled on Msdev.exe. Then it indeed starts, but hangs/freezes on loading symbols.
-
Jumper, I hope I have usable log files now. Example: Firefox.exe
error in Kernel32.dll at :bff6bb07
- changed the machine
- KernelEx set to disabled
- started Firefox in XPSP2 mode
ProcWin - screenshots(undefined memory)/ Minisnap - txt/ DependencyWalker - log/ KexApiLog - log
-
Debug Button of VS 6.0: Msdev caused the same error in Kernel32.dll at :bff6bb07. That was what I expected and doesn't change the situation.
-
Goodmaneuver, sorry, I still haven't fully tested your workaround. I see that was a lot of work! I have taken other approaches and I wasn't able to run Kex25 with Kexbases25 on ME so far.
I spent hours working on the core.ini today. Jumper, I also tried to overwrite the Api's of the changelog (Kexbase 4.5.2016.25 notes). The main problem may be related to "Lz32.ImageNtHeader". The page fault doesn't occur, if I set "Lz32.ImageNtHeader" in the core.ini to none, but then ME runs without KernelEX only (no messages). Is this API somehow required to start KernelEX 25?
A second abnormality: A runtime error message after removing "LZ32.MakeSureDirectoryPathExists=none" - "Lz32.ImageNtHeader=none" remained in the core.ini. Result: One program couldn't start because of this error.
Lz32.ImageNtHeader -> ImageNtHeader (for Dbghelp)
Lz32.MakeSureDirectoryPathExists -> MakeSureDirectoryPathExists (for Dbghelp)
Lz32.SymCleanup -> SymCleanup (for Dbghelp)
Lz32.SymGetOptions -> SymGetOptions (for Dbghelp)
Lz32.SymInitialize -> SymInitialize (for Dbghelp)
Lz32.SymSetOptions -> SymSetOptions (for Dbghelp)For what is this support of these API's necessary? What's the point? All these Api's are already supported by the original DbgHelp file of ME.
-
21 hours ago, MiKl said:
Unfortunately I have somewhat lost touch to 98SE in the last months and so I am stuck right now. I have installed the new version and I reach desktop but no KernelEx dependend prog starts.
First error message msvcrt.dll -> ntdll:RtlAreBitsClear, then after adding this to kstub824.ini -> ntdll:RtlAreBitsSet
I guess I have missed any other important development lately. Any ideas ? Thx, MiKl
I suppose you're the only one with RtlAreBitsClear call here. First I would try to avoid the call. Disable Kext entries which could trigger the call. Maybe it's enough to disable itself. In my opinion it's no issue of Kex25.
https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-rtlarebitsclear
https://msfn.org/board/topic/173302-kernelex-auxiliary-dll-updates/?do=findComment&comment=1119417
-
On 11/26/2021 at 10:00 PM, schwups said:
Today I installed KernelEx 25 on this vanilla 98SE build. It booted and no errors occurred. My checks where only with Verify.exe and Ktree so far. I also tried to install the Nvidia graphics driver, but this attempt failed. The installation of the driver on ME with this Motherboard is no problem. I could fiddle with a lot of patience or I change the board. There is no need for the RevolutionsPack without a high resolution.
I moved to another board with 98SE support. I repeated this test and installed the Nvidia driver. The core.ini is 25g. I got a large number of messages I could klick away:
"KernelEx 2016 4.05.2016.25
LoadLibraryA_fix2 retry"
The messages don't occur, if I remove the line "KERNEL32.LoadLibraryA=kexbases.1" under [BASE.names.98] in core.ini.
I deduce "invalid page fault in module KERNEL32.DLL at 0177:bff6bb07" is Win ME only and has nothing to do with the Nvidia driver or apps.
-
I had set up a fresh vanilla ME. The problem occurs with and without the Nvidia driver installed. I installed the WinInstaller 2.0 and the graphics driver only, nothing more.
Kext: DIY KernelEx extensions
in Windows 9x Member Projects
Posted
Today, I tried two more plugins:
--- No OS override ---
[BASE]
contents=Kexstubs,stubs,Kstub824,std,Kexbasen,Kexbases,kexvista
desc=Base enhancements (api fixes + extensions)
1. Test: Splitted my ini in three parts (A-I, J-N, O-Z)
2. Test: Basically my ini and these for 360EE and IE9
As far as I can tell these plugins work. I've captured them all with DependencyWalker when profiling different programs.
Does it make sense to split the ini so that we have one ini for every dll? I think, only some more make sense. Some more and smaller ini files can, for example, simplify troubleshooting in many cases. It could be useful for two or three programs.
I haven't tested anything related to "exceeding the Kstub character limit" again so far.