Jump to content

jumper

Member
  • Posts

    1,935
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by jumper

  1. 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.
  2. 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.
  3. 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.
  4. Also include K*stub* in the Vista and other contents= if needed. Retest Xpcom.dll with ImportPatcher set to Vista. Also Xpcom_*.dll
  5. 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.
  6. KernelEx v4.5.2016.25 updates.7z Readme's inside.
  7. Start by doing a Google site search for "missing" to find previous detailed answers to this request.
  8. Check again....
  9. Black list dePo ApiLog messages are formatted so [ < ( = can be used in powerful case-sensitive filtering. Use Procwin16 to disassemble at EIP. What version of Msvcrt is failing to load? Make sure you have an appropriate mode set on it.
  10. Well, yesterday I had to install Firefox as MSFN became completely unreadable in all other browsers on my Android 8 phone. So I'm glad Mozilla still exists.
  11. > EAX=00000000 ... SP=03effd6c Endless retrying to call a function that fails could mean a thread that is spinning instead of yielding. If the instruction at IP accesses a stack variable, that would confirm a stack problem. Try increasing the stack commit value in the exe's pe header. Also use apihook to check for the last call handled by KernelEx. Profile in Depends to see failed module loads.
  12. When posting screenshots make sure important details are readable. EAX, EBX, ECX = 00000000 often means the previous call failed. ESP = 02c8fc74 - the f often means stack overflow or failure of the virtual memory manager to grow the stack by paging in the next stack page.
  13. Not helpful. Please reread and try again.
  14. Nice to know, but not the same. Does declining load of all drivers still work? Remove the new NIC or disable it in BIOS. Also disable Wake on LAN. A device doing that might also try to sleep on no lan activity.
  15. When having problems, don't install a newer DX9 than the video drivers were officially tested with. For 77.72 this means June 2005.
  16. > Load all Windows drivers? [N] Uninstall all new drivers in reverse order going back several weeks before you noticed the problem. Alternately, restore a working registry.
  17. System error at app load, or app error later? 64-bit Vista, app, and Dbghelp?
  18. Not to split hairs, but I count oops x 5. I only get frustrated when the meaning becomes ambiguous. If you need help deciphering a post, politely ask for clarification.
  19. Quote implies partial support will remain.
  20. > know the APIs that are in use Use my build of ProcWin 1.6. Select a process in the left frame. Right-click on individual modules on the right, then select Properties->KernelEx->Enable API Logging. In ApiLog.exe (aka DebugWindow) right-click and enable Output to log file. Restart process to see what you missed. Also remember to check Kstub823.log to see what API's are actually called. These are the only definitions that must be correct. I have begun work on a KexVista module. It already has functional support for all ConditionalVariable and SRWLock API's. I'll add to the to-do list support for some MS-API things like ResolveDelayLoadedAPI that can't be forwarded. And I checked Kexstubs.c. The limits are: 100 DLL sections, 36KB of DLL section data (definitions and comments within DLL sections), and 1600 named functions. Unnamed (ordinal) functions and data variables are not yet supported.
  21. Maybe from the onboard diagnostic speaker/buzzer? Try covering the sound hole.
  22. Ktree11 now has a font chooser (F9). I'm also adding an HKLM\System\...\KnownDLLs branch. Any other requests?
  23. Incorrect; bad idea. Maybe; name one. Ktree10 is better than 9, but both already can. Like 10 says in the tital bar: press F1 for help.
  24. Thanks. Yes, the release page is viewable. But it contains no package download link. That's why i asked, not for the link, but for its location. The given link did work in Android's Google app. Package contents look good. Don't have an sse2 system atm, only sse, 3dnow, and mmx. Is it possible to build for any of those targets?
  25. Link fails. Forwards to "Webpage not available."
×
×
  • Create New...