Jump to content

jumper

Member
  • Posts

    1,836
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by jumper

  1. Change: [AVRT.DLL] Then add "..\system\avrt.dll" to Contents= Might be simpler to use the KnownDLLs / LZ32 method with avrt.dll in KernelEx folder.
  2. Kex25 not seen. Your configuration is a mess. You really need to start over from scratch. Use more stubs to avoid the cows, resulting in fewer modules and fewer stubs needed overall. Use all latest KernelEx and aux. files and the correct Unicows. Do not mix-and-match from different KernelEx versions. Do not use post-XP files. Do not use files from other extenders.
  3. Try cloning kstub825.dll. Use Kexports on Avrt.dll to get a list of exports to use for definitions. Put the new Avrt files in Windows\System so KernelEx will work on it. Can you load Avrt.dll in a dll loader such as Ktree or Procwin?
  4. Cow (can of worms). For multimedia, probably delay-loaded, so delete for now. Export DW results as text. The PNGs were of no use.
  5. 11Feb hangs in AVRT.DLL. The others do appear to start, then crash internally and exit. Check the Kexstubs log to see if any stubs were invoked just before the hang or crash.
  6. Removing the dot from the end of your link, it appears ConditionVariable_windows.cpp is a cross-platform abstraction layer that was rewritten to avoid Vista CV api calls that XP doesn't support, but KernelEx does. But I don't know what all was changed when. To debug, we'll need to compare before and after DW profiling logs to see what modules might be failing to load. Then more detailed KernelEx debug logs to find the difference in api calls. Doing the same with Opera Presto might give us some additional insight.
  7. Under IRQ Steering, first deselect Get IRQ table using ACPI BIOS. What does the IRQ Routing Status say?
  8. Workaround found: Add an equal number of dummy named stubs. At most, half plus one of the definitions in each section are converted to ordinals. Update: Fixed! Coming soon.... Thanks @Goodmaneuver
  9. Reproduced. Smaller numbers can also fail. 0418 sometimes works, sometimes fails. No workaround yet.
  10. Thanks, I'll try to reproduce. Looking at the addresses, it might be a problem with Ktree or the way Kstub825 hides the dummy names. What tree branch is displayed in the left window?
  11. Then you are definitely posting in the wrong topic thread. And as an end user, post-4.5.2 versions are not for you. Please remove them from your systems immediately.
  12. None of your responses to me make any sense, so I recommend you stop experimenting with current versions of Kexstubs.
  13. Is this a regression from previous versions of KernelEx? (Yes or No) Only if Yes: what was the last compatible version of KernelEx? Do not post anything more than just what I have asked for.
  14. Reread my last post until you understand it. If you still can't figure out how to ASCII sort, keep your definition files very small and let Kexstubs do the sorting for you. Blank definitions are no longer needed. There is no problem with using multiple renamed copies of the latest Kexstubs.dll. Ktree loads each module individually and shows addresses based on each module's preferred address. Ktree can't predict how the loader will rebase them on-the-fly when they are used together. This is why you are seeing multiple api's at some addresses when using multiple copies of Kexstubs. A future version of Kexstubs might allow selection of a base address in the definition file.
  15. I still don't know what you mean by this. There are no special characters. All are ASCII. The sort is correct. Sort by Hint, not Function.
  16. "All extensions, by address" in Ktree.11 lists Kexstubs api's in reverse-sorted order. Useful for verifying that they are efficiently defined in sorted order.
  17. Create a bookmarklet with (or type into the address box) the following script: javascript:document.body.innerHTML.split('https://').join('http://')
  18. IE2 runs in NT4, so it should also run in NT5. You may need to set the compatibility mode to NT4. Use ImportPatcher or Depends to find all missing API dependencies. Then patch the IE6 files or update libraries as needed.
  19. Yes, MS-DOS Prompt window or batch file. Read the launcher configuration files to get the name of the executable. Start with no parameters, then add slowly. Limit is about 250 characters.
  20. Launchers are never needed. They just hide the runtime parameter details.
  21. Don't use a launcher. Don't use custom installers.
  22. Try again focussing on MC and Java. Explain "custom installer". You're making this this problem too complex by adding Mesa and multiple MC launchers. Use just the basic versions of MC (ver ?) and Java (ver ?). Confirm that each is working by itself before combining them.
  23. Which part of your install process. Lwjgl32.dll might not exist. What happened when you deleted lwjgl64.dll? Please summarize your complete install process as you actually did it.
×
×
  • Create New...