Jump to content


Gold Sponsor
  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

  • Country


Goodmaneuver last won the day on July 25

Goodmaneuver had the most liked content!

1 Follower

About Goodmaneuver

Profile Information

  • OS

Recent Profile Visitors

5,434 profile views

Goodmaneuver's Achievements



  1. In the Core_8.zip is Core.ini and in Core.ini I made default=1. This did not make default mode = Base. Default mode is still DCFG1. So making default = 1 did not do as I thought it would and Base (verify version) needs to be selected to enable that mode and make SumatraPDF work.
  2. DW errors have returned after updating a module its seems but it is not the modules fault. I am not ready to comment further.
  3. I have experimented before and taking out certain (most of them) DCFG1 names is not a good idea. It would corrupt the system. Even taking out SHELL32.SHParseDisplayName=none had consequences. WMP10 WMP.dll if not using XP mode took on a silvery skin colour like WMP11. The blue skin returns once making WMP.dll XP mode. Inheritance in Core.ini takes on the contents as well so there is no need to include it in any inherited modes later on down the list. Ktree does no necessarily pick up on Modes that do not have Contents though and therefore will need to be altered or just be aware of that fact. Adding Content down lower in Core.ini may have made Ktree list all modes but alters KEX functioning. You would think that Microsoft would know what was NT SP4 and what was NT SP5. I have tested it also on several games as well and they do not install complaining that NT40 mode is not SP5. What difference is it to change the description, what's the good of testing? Here is a proposal and I am confident that the new custom mode of BASE can be taken on as the Default Mode if desired. Also BASE settings will not need altering prior to rebooting. Watch out though I have added 4 x Kstubs so make sure that is configured/corrected before rebooting. I do not think that all OS version Modes included are needed though and some could be trimmed out. Just the original 4.5.2 ones would do. Core.ini proposal is in the zip. CORE_8.zip
  4. I thought I was purchasing the RAM locally but is was overseas and just arrived a few days ago. The funny thing is that I already had ECC unbuffered RAM installed. The good part is the newly purchased RAM works. There was no change in the Process Explorer commit charge reading. The DW issue was marginal in the first place on the DDR3 machine and seems to be non-reoccurring once I had fixed several registry errors along with addressing some well used system files so that they are referencing internally %WinDir%\system instead of Windows\System32 etcetera. I have also worked on KernelEx and it now has less errors in my Kstubs (no == or=>=> or duplications). Only a couple of redirects untested. I am thinking my Kstub errors may have been a main contributor to the DW issue. GDI32 now has correct CRC. The registry errors were checked using RegDllView and most directories that were wrong were corrected. The only issue without trying to run any KernelEx dependent programs was that on opening the root directory of C: I got the scripting error in Sysroot.htt.
  5. Take note I said this. The original naming must be written into 4.5.2. If the original mode/profile names are changed then the functioning of KEX is altered. The new BASE core names are only good if I do not alter my 4.5.2 settings. If I do then system will be corrupted and will not do as it was doing prior to changing mode settings to new names. It does not work properly upgrading to new names. Please do not change the original naming. To get SumatraPDF to display eBooks all that was required was to add a mode name of SPDF for example and I placed it below MIN; 6=SPDF [SPDF] inherit=BASE contents=std,kexbasen,kexbases desc=eBook Paser [SPDF.names] KERNEL32.VerSetConditionMask=kexbases.0 KERNEL32.VerifyVersionInfoA=kexbases.0 KERNEL32.VerifyVersionInfoW=kexbases.0
  6. SumatraPDF 3.2 needs Legacy Base Enhancements mode selection where VerifyVersionInfoW is enabled in later KEX otherwise if selecting another 2K setting prevents eBook's from displaying. The menu only displays with 2K settings and it took me a while to figure this out. So DCFG1 is special.
  7. That part is true. I am not lying about what I said that my build recognizes case changes in file names lower case being the default but I had uppercase and lower case mix, Kstub01 to be precise. I do not want to be chatted about mentioning other OSes but I have a directory named Videos on the network drive and if you write to that drive via those OSes then it renames the videos folder "videos". When I access the network drive via WinME afterwards I then have 2 folders named "Videos" and "videos" both contain the same thing which means I have 2 names for the same folder showing up in WinME on the Android based network drive. Your Kstub824 needed to have the same characters in the INI as the DLL including case. Can this statement be explained further, Please explain definitions and profiles and how they can be accessed in Core.ini.
  8. SOLVED! ExKernel was not loading because Kstubs were not loading and there were several reasons. My build recognizes a file name change between uppercase and lowercase names in explorer. There is no need to rename the file with a different character at first. Uppercase and Lowercase is recognized straight away as a different name. I had to make the Kstub.ini name equal the Kstub.dll name exactly matching the case of which I did have but in WinMerge if a slow double chick occurs it makes the name comparison equaling the LHS name being case sensitive and that how the change came into being. The other reason in another build was that I had not sorted alphabetical some of Kstub entries and there were several duplicates and quadruplicates of the same API function.
  9. I had an instance of ==> in Kstubs instead of just => and it made a difference but there is still a limit and because it involves a module Jumper has shown discretion about, I think I might have to write about it in a separate topic.
  10. Note If using Dibya's Exkernel.dll from my instructions, CancelSynchronousIo does not work so do not make a Kstub entry for this. It does work! Machine struggling to load ExKernel at times now I think. Reason to be investigated. Some reasons may be too many files in system directory, registry changes or hardware. CancelSynchronousIo=>Kernel32:CancelIo can be used too. It should not be a problem unless both CancelIo and CancelSynchronousIo are called at the same time and I do not know what happens then as I have not tested.
  11. There are several of us using Windowscodecs.dll of which I can speak of what I use. RtlSetBits came into being in Windowscodecs about LH5308 so any Windowscodecs up to LH5270 will work. The thing is that it was continually evolving and final versions may be required for some software. A solution is to use ReactOS version of the module of which SumatraPDF requires. ROS 4.2 year 2017 is what I am using and it is equivalent to Vista service pack3.
  12. In response to previous post. The executables that do not finish profiling like MPC-HC; DW shows that KernelEx stops working because of the Fls and Decode and Encode Pointer function calls are not dealt with. (My fault here as it only occurs on one build and normally not the case). I would say that DW in this case of profiling MPC-HC has pushed the OS to its limit some how. MPC-HC loads many ACM modules.
  13. If KernelEx redirects or has stubbed functions only then the original DLL for those functions will not be loaded. If the DLL cannot be loaded and is not an explicit then it will not be included in DW's profile log. DW indeed does not hook some modules with NT40 or above but having DW set to NT or higher mode does not stop the executable loading. The NT40 or above errors are found to be the same when profiling different executables. Here are 2 such errors. Error writing a breakpoint at the entrypoint return of "c:\me\system\WOW32.DLL". Entrypoint cannot be hooked. Invalid access to memory location (998). Loaded "c:\me\system\WOW32.DLL" at address 0xBFDC0000 by thread 1. Cannot hook module. Note well that LegacyBaseEnhancements is OK for DW also. DW indicating the red dependency function is DW doing its job correctly. It is once profiling that KernelEx then is operational and if all is OK there will be no red function call failures. Implicit API function calls and delay loaded calls are displayed just by dragging and dropping the module into DW. https://www.dependencywalker.com/help/html/dependency_types.htm I find dependency Walker an extraordinary helpful program. For instance when profiling PotPlayer firstly there are no red instances. This is testimony for Jumpers KernelEx; a job well done. There are no failed explicit functions with Desktopdll.dll but if I disable DesktopHook.dll then DW stalls when it goes to load Desktophook.dll. If I make Desktopdll Kexbasen then PotPlayer finishes profiling but Desktopdll is not loaded. If I then make it Kexbases then Desktopdll loads but there was an exception in Kernel32. The next file to show in the DW log was Urlmon after Desktopdll and I had this one disabled. I then made Urlmon Kexbases and there was no exception created in Kernel32 and Urlmon did not show after Desktopdll in DW log.
  14. Tell me what the issues are? Only use DW in BASE mode do not profile in NT or above modes. Leave the file to be profiled in what ever mode it needs. If a dynamic link library which has register server function registers it means that it loads into RAM prior to registering. I test with KernelEx disabled first and if it works then I usually leave the DLL in follower mode. There are the odd ones which need KernelEx disabled so testing again in follower mode will be necessary. Otherwise I step up the mode setting until it registers. Some will fail to register.
  15. If you do not want to map the KernelEx folder then place Depends.EXE, Depends.DLL and CHM into the KernelEx folder and operate DW from there.

  • Create New...