Jump to content
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. ×

jumper

Member
  • Posts

    1,574
  • Joined

  • Last visited

  • Days Won

    6
  • Donations

    $0.00 
  • Country

    United States

jumper last won the day on August 13

jumper had the most liked content!

3 Followers

About jumper

Contact Methods

  • Website URL
    geocities.ws/jumper

Profile Information

  • OS
    98SE

Recent Profile Visitors

8,097 profile views

jumper's Achievements

176

Reputation

  1. I can reproduce. A second, high priority, Explorer process is created when Opening Containing Folder from search results if Launch...in a separate process is enabled.
  2. Right. The opcode is 59hex, the instruction is POP ECX. But we're not interested in that. Stay focused and tell me about the call.
  3. Did you spot my typo? The address in the stack dump we are investigating is actually BFA01F2A. If that is (hopefully) a return address, we want to know what the call was. Run Winproc16 on any system. Select MPREXE in the process list on the left. If Kex is even partially running, you will see KernelEx.dll in the module list on the right. If not, select process PROCWIN; find and load KernelEx.dll with File>Load a Dll; move aside but do not dismiss any popups. Double-click on Kernelex.dll for module details. In the code tab, do we see what we were hoping for?
  4. Install FineSSE or DrWatson so you get a Debug option in crash dialogs. I need you to identify the problem startup item. Disable all items individually or in batches until you can get to the desktop. Or disable them all, then run them manually from the desktop.
  5. @Goodmaneuver - Take a deep breath. We are not going to debug. We are investigating. Please stay focused and respond with only the exact information I request. You know about load addresses. In what module is bfa01fa2? @schwups - Are you also using Nvidia apps? If so, disable their auto-start and see if you can get to the desktop.
  6. KU211123.7z .25 refresh KexbasenKexbasesKstub824 dll+iniKexVistaCore.25g to fix some issues Core.24a fallback example KernelEx.dll v.25 to match, but not new3 additional files for IE9 and 360ee support Tools ImportPatcher 42 - Test and patch PE importsKtree 11 - View KernelEx API's - New: choose and save fontProcWin 1.6 - View running process image detail w/disassemblerMinisnap 5 - Displays module versions and KernelEx modes for each processKexports/Exports 5 - List Exports as .ini or .def
  7. My previous response was for schwups, but looking at your logs I see bfa01fa2. This is our best clue. Investigate.
  8. > The installer of 4.5.2 doesn't register these files as Kex knowndll's. It registers them as shell and com extensions. On hang, is there a Debug option? Do you have a debugger installed? Try disabling auto-start apps. Try modding core.ini to use the NtClose alternates. (I'll do this in the update).
  9. 7d011b65 push ebp Stack overflow/frozen. Error message and stack dump would have been useful.
  10. If that's the Rundll32 initial report, determine the command line and reproduce the error while profiling and logging. From the initial report, it appears to be a bad pointer in Kexbasen passed from jemalloc to EnterCriticalSection in Kernel32. Also a stack leak unless Kernel32 is somehow calling back into Kexbasen. Only Sheet and Kexcom need to be registered.
  11. Only those three that are invoked need valid definitions. Save space and reduce typo risk by not repeating the function name after the colon. The last = is an artifact of using the private profile APIs for logging. The first = is put there to balance it. Ignore them. Split the definitions by using multiple copies of Kstub824. Right-click in ApiLog console window to modify settings.
  12. Using numbers is a simple way for KernelEx.dll to enumerate all active modes and also for Sheet.dll to order the menu items. Yesterday I noticed setting a mode below the first gap didn't stick. If KernelEx.dll isn't recognizing modes below the gap, it will use the default instead. I'll debug it later, but eliminating gaps avoids problems for now. Filling them with <nn>=. works. Just checked: Core.20i has 0..46, no gaps.
  13. Also include K*stub* in the Vista and other contents= if needed. Retest Xpcom.dll with ImportPatcher set to Vista. Also Xpcom_*.dll
  14. Core.ini ApiConfigurations need to be renumbered without gaps in the sequence. This should reenable the legacy modes. I will refresh the package with that fix, a version-matching Kernelex.25, and also the Core.24 that got left out of the v24 package.
  15. KernelEx v4.5.2016.25 updates.7z Readme's inside.

×
×
  • Create New...