Goodmaneuver

If KernelEx is not running, which it does not with Kesbases25, then how can we debug it. These Faults will occur when KernelEx is not running. Nvidia software launches with rundll32 and cannot be run again if stopped until a fresh reboot occurs. I would not be concerned about the fault log as KernelEx is not running and after first overrun then with the next application to launch, triggering a Fault Log, the fault log can not be trusted. We have numerous modules with KEX settings including Rundll32 (BASE). How can we attempt to launch KernelEx manually to try and debug it. I am certain KEX modules do not load. I know that the OS should run without KernelEx and I have made sure it does with Safe Mode and debugging an application that requires KernelEx when KernelEx is not running does not make sense.

Here is the FaultLog but it is irrelevant due to memory corruption and pushing into the next application load. Everything will not load when Memory overshoot/overrun occurs unless it is stopped by trying to debug it then closing the debugger. Explorer then can be loaded but then you can only run applications that do not need modules that require KernelEx. WinMgmt.exe needs RegDisablePredefindCache as I have used 5.1.2296.1 - perhaps I should not have used this version but is first application to load that requires KernelEx. ********************************************************************** Date 11/24/2021 Time 01:40 WINMGMT caused an invalid page fault in module KERNEL32.DLL at 01bf:bff6bb07. Registers: EAX=00000000 CS=01bf EIP=bff6bb07 EFLGS=00000246 EBX=830c55ac SS=01c7 ESP=0064f7c8 EBP=0064f7d8 ECX=ffffffff DS=01c7 ESI=0052c510 FS=2267 EDX=830c5960 ES=01c7 EDI=bff7cf67 GS=0000 Bytes at CS:EIP: ff 76 04 e8 8a 87 ff ff 5e c2 04 00 56 8b 74 24 Stack dump: 0050021c 0051b736 0052c510 ffffffff 0064f7f0 0051b67c 00000142 00400000 00500218 00000000 0064f810 0051aa2e 00000142 00000000 0064f81c bff888ed ********************************************************************** Date 11/24/2021 Time 01:40 RUNDLL32 caused an invalid page fault in module KERNEL32.DLL at 01bf:bff6bb07. Registers: EAX=00000000 CS=01bf EIP=bff6bb07 EFLGS=00000246 EBX=00000000 SS=01c7 ESP=0065f774 EBP=0065f784 ECX=ffffffff DS=01c7 ESI=0053c510 FS=230f EDX=000001f0 ES=01c7 EDI=bff60000 GS=0000 Bytes at CS:EIP: ff 76 04 e8 8a 87 ff ff 5e c2 04 00 56 8b 74 24 Stack dump: 000001f0 0052b736 0053c510 ffffffff 0065f79c 0052b67c 000001f2 830b5000 830c8908 00000001 0065f7bc 0052c119 000001f2 00000001 0065f7dc bfa01f2a **********************************************************************

Debugging this will give differing results as to which application is trying to run. KernelEx does not run. RAM corruption is happening for me, see my above post, and TD32 can not debug it. Like I said, the best result was that KernelEx.dll could not load but it was not that exact word -(load) and it was not while testing Kexbases and prior to editing Core.ini. Jumper If you are running 98FE and have differing ImageHlp and DbgHelp modules then you may be getting Kexbases to run? My ImageHlp version is 6.05270.9 and runs in SafeMode along with DbgHelp of 6.9.3.113.

Some of my runtime applications require KernelEx and therefore I know straight away when KernelEx is not working when booting in. Some apps will break across RAM and corrupt other apps that are next in the load sequence if 1 or 2 of those apps do not load properly. I need to stop the App not trying to load again to halt further Memory/RAM corruption by choosing to debug it with Borland's Turbo Debugger TD32.exe instead of selecting to close the App. This way I can then start Explorer. WinMgmt starts before explorer I believe. I too lose the use of my USB after using Kexbases25 knocking out USB keyboard and USB mouse. PS2 devices should be OK. I think Dave-H is clarifying his use of the KEX modules as to hint on whether there was an update to these that we do not have. Kexbases25 introduces a new call to ImageHlp and KexBases25 stops KernelEx from running. Jumper if you have Kexbases25 running then is there an update to KernelEx.dll that we do not have or something like that?

'Only Sheet and Kexcom need to be registered' : - You have a shortcut of regsvr32.exe in the Windows\SendTo folder. Sheet and Kexcom are the only KEX modules that export DllRegisterServer and DllUnregisterServer.

Quadro FX5500 works without any problems with my ECS K8T890-A but would not install with 2 other AMD motherboards I tried as I believe that the PCI bus throughput width needs to be in proper condition. The install problem was a resource conflict indicting a hardware issue. The other boards had trouble with with just playing a low resolution video with other video cards with Pot Player but they are a lot better now after exercising them. See pictures for details about the K8T890 socket 939 machine. The 82.69 drivers indicate the 1GB memory but the card is unknown and therefore defaults are displayed.

Strangely I had tried Kexstub824 before and it stopped KernelEx but now it works. I have modified Core.ini K25 to renumber it correctly prior to testing Kexstub824. The only change I have made to Core.ini is to use KexVista for more modes. Core.ini uploaded in Zip. Kstub824 has a larger definition range see picture :- ( using the same Kexstub823.ini unmodified as in previous posting renamed Kexstub824.ini ). core.zip

MultiVMR9.dll from Alias the game needs a final release version of Quartz to work it seems so now I use Quartz form Win2K3 SP2 vs 6.5.3790.3959. Below are install registration values for WMP10 vs 10.0.0.3997. You will need wmp.dll, wmploc.dll and wmplayer.exe of 10.0.0.3997 version distributed with Win2K3 SP2 for the registry installation confirmation. I have included a set of modules in use HTM for some help with other modules which can be of your choice but need to be compatible. Register new modules. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\Setup\Installed Versions] "wmp.dll"=hex:00,00,0a,00,9d,0f,00,00 "wmploc.dll"=hex:00,00,0a,00,9d,0f,00,00 "wmplayer.exe"=hex:00,00,0a,00,9d,0f,00,00 MP10.htm

I get these logs repeated K24 Kstub823.log = MSVCRJ.DLL:sscanf_s=>MSVCR90D:sscanf_s = = MSVCRJ.DLL:_ftol2=>MSVCRS:_ftol2 = = MSVCRJ.DLL:_ftol2_sse=>MSVCRS:_ftol2_sse = When you say these are the only definitions that must be correct. do you mean that these function redirects are correct and are the only ones needed in Kstub823 or otherwise? What does the log mean generally and with the = on the end? I should have noticed before but Kstubs seems to stop working before the 15000 character limit (an approximate suggestion). The character limit stops KernelEx completely. Take a look at the picture the lower down Kstub823 definitions are not listed in Ktree10 it stops at SetupDiGetClassRegistryPropertyW in this instance of Kstub823.ini. Logging Kstub823 does not bring anything to the ApiLog window.

KernelEx is for Win98/ME none for XP. Win9x has a sole user environment and compatibility for certain other applications where as the NT Operating Systems have multiple users and an upgrade path. This is why KernelEx is important for WinME.

I tried that but what does the ApiConfiguration numbers mean or do? Core.ini 20i had some gaps in the numbering configuration but it still worked. EDIT I should have checked myself. As per Jumpers next post Core.ini 20i does not have any numbering gaps.

Notepad++portable version 1.6.8 I would suggest to try and Internet Explorer 4 or above update will need to be installed for a version like 5.5. I am running WinME but looks OK as IsDebuggerPresent is not used and runs in Safe Mode.

My Notepad++Portable.exe is version 1.6.8.0 but when the program is run the version reported is ++5.5 (ANSI). Plugins using are Compare, Light Explorer, NppExec, NppExport, TextFX Characters, Spell-Checker, Document Monitor, MIME Tools and NppNetNote. Notepad portable 1.6.8.0 should be OK.

Kstub824, kexbases and kexbasen all do not work from the K25 upload. I tested them individually and the best result was that KernelEx.dll could not be loaded message occurred. EDIT Kstub824 and kexbasen are good after fixing core.ini. See https://msfn.org/board/topic/157173-kext-diy-kernelex-extensions/?do=findComment&comment=1208164

API-MS-WIN-CRT-Runtime-L1-1-1-0.dll should not be called as UCRTBASE.dll should be in your system and API-MS-WIN-CRT-Runtime-L1-1-1-0.dll should be redirected to UCRTBASE.dll via the registry. See page 18 here and download the TXT file and rename it a REG file and merge into registry. The UCRTBASE module; I have not investigated the later versions to see what has changed and I am using 10240. Schwups is using 14393 see page 19 here. To export log from Dependency Walker, click the File tab and select Save As which has format options, or just copy and paste into text editor.

It should not happen if the application is selected to run with NT Service pack 4 or above. The Core.ini description for [NT40] should be changed to NT 4.0 SP4 as NTSP5 required apps do not install unless Win2K or above mode is operative with KernelEx. IsProcessorFeaturePresent is a native function of Kernel32.dll. Check it out with Dependency Walker. The only line that should be in Core.ini for this function as stated by Jumper was for Win95 of which IsProcessorFeaturePresent is not a function of Win95 Kernel32. So the error of IsProcessorFeaturePresent can be removed by deleting the lines that have it in Core.ini. If you right click on the ForeFox.exe and in the KernelEx property sheet display it should state what mode you have chosen for the app. There should be a decisive black radio dot with white around it with no other high lighted option. Run Dependency Walker with the same mode as the App that does not run and choose to profile it. It might show up a hint to why it does not run. Why are you running only 16 colors? How far back can you go with System Restore? Is everything else that should run without KernelEx working as it should? FireFox 9.01 will not run without KernelEx as far as I know.

Yes it can be swapped around a little but not std last from my memory of such but that is not the main issue. The issue is that the uploaded Core.ini has kstub823 and kstub824 in its contents and 2 kstubs at once does not work.

If you are using the uploaded Core.ini then the contents= line under {BASE} is wrong it should be one line and be std,kexbasen,kexbases,kstub823 You also should have Kstub823.ini in the KernelEx folder along with Kstub823.dll. The upload ini file is not named correctly.

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.

If this is a new message after replacement of DbgHelp from wow64 into the applications folder then it could be a 32bit app. So you need both a 64bit DbgHelp and a 32bit version of DbgHelp I would think but not sure. Even though you have tried a different version of DbgHelp sometimes the app comes with its own DbgHelp which can be too old to interact with other OS components and I would try a different version again. For example Dungeon Siege 1 comes with DbgHelp and originally my WinME system had to use this version with the game. Now my ME system does not work with the Dungeon Siege 1 original DbgHelp and I have to remove it from the apps folder and use/rely on my system DbgHelp which is version 6.9.3.113. I use this version because it has more functions available over any newer version that is compatible with WinME. I think from memory that DbgHelp, ImageHlp and ImgUtil, to which I use LH5270 versions of the latter have to be compatible to each other. Use Dependency Walker to see if it is 64bit or 32bit.

First it depends on what you mean by sleep. Sleep means that the machine can be woken up by pressing the appropriate key board key for example which can be set up in BIOS. Those startup settings really just mimic safe mode as far as I know. Safe mode does not load the hardware software drivers and runs hardware off BIOS. Most problems occur when a monitor is installed on a Standard PCI graphics adapter driver then the nVidia drivers are installed afterwards. First install a Standard PCI graphics adapter and then reboot. When system reboots do not allow a monitor to be installed, this is the important part. Now install the nVidia driver and then reboot. If your monitor goes blank or says "not supported" on reboot, go into safe mode and right click properties and choose the display settings of 640x480 @ 4bit color. This is the same as safe mode. Then when rebooted do not allow the monitor to be installed just yet, : - important. Change settings to 256 bit color and 800x600 or what you want, there will not be many choices. It will ask for a reboot most likely, so reboot. The nVidia driver after 256 color is running it will run the nVidia other software and now it is safe to the install the monitor driver. You may wait till 32 bit color is running first though then reboot and allow the monitor installation.

I have Kstub823 loaded with Vista screen savers like Branded, MPREXE.exe, KMPlayer 4.06, PotPlayer 1.545995, VLC 3 & 2, MPC-HC 1.4.2499 and probably others, Ktree shows the APIs that are in Kstub823 but I wanted to know the APIs that are in use by the programs that are loading Kstub823. The Vista screen savers will not work without my Kstub823.ini. In a normal window the text lines can be highlighted with left click/slide then Control plus C for copy, if this can be done in Ktree then it could make it easier to work with. If IsValidProgramGroup and IsValidLocaleName both return a Boolean then it might work. See picture for the IsValidProgramGroup showing KexBases and Kernel32 with DW. I have been wanting the ResolveDelayLoadedAPI solution for a long time, we are nearly there to be able to use most windows modules that are in use and ResolveDelayLoadedAPI will be necessary to resolve this. If we use KernelEx KnownDlls and KernelEx Subfolders without the system mapping the location then it makes KernelEx conditional and complicated. I have shied away from this idea. I have spent most of my time recently on updating hardware. Objective is to update to a 4.2GHz + processor and I will update your Roll Call 2021 https://msfn.org/board/topic/182230-roll-call-2021/?do=findComment&comment=1193596 with all the details when completed successfully with each board, time willing. The modules I wanted to use were not kept but for a few, Oleacchooks, Dsparse, D3d10level9, WmpDui. I have WMP10 working and 11 could work too with ResolveDelayLoadedAPI. With more modules able to load then more applications will work. Nvidia device properties defaults to DX8 when the graphics card is unknown. Even though the picture says G73 it still does not know the video cards name it should be 7300 GT. The 82.69 drivers should display this correctly. I think I have a hangover from the older drivers and the registry will need cleaning and driver reinstalled.

IsValidLanguageGroup is stubbed in KexBases when it does not need to be. I was going to try IsValidLanguageGroup function substituted for IsValidLocaleName in Dwrite but cannot as it is stubbed. We have had a stub for DelayLoadFailureHook for a long time but is it possible to get one for ResolveDelayLoadedAPI as this function call is used along side DelayLoadFailureHook in a many modules. Is there any chance that the functions in use by KexStubs be determined with Ktree? This could be used to trim down KexStubs.

Thank you for backing me up on this Schwups, it means a lot. I like 10 as it gives the entry points of the module and I think it would be a good idea if we can redirect back to KexBases for example to use a stub again in a new defined module. I do not think it works though and memory locations can/will change. With the pictures uploaded the system fonts that are in use in that case are Arial western size 10 for all except Menu and Selected Items which use Verdana Western 11. So the default window font should be Arial western 10.

The font size does not change with Ktree10 and has always been this way for me on all builds. You can see the square + size that the window metrics is working on Ktree9 and the window title bar font is the same for both. What could be different? There were no font changes, I have launched Ktree9 and Ktree10 both are running at the same time. What do you mean by Ktree9 and Ktree10 use different fonts? Ktree10 does not use my system window font: Ktree9 does.