jumper

I see a scrollbar that isn't disabled. If that is the complete call stack, OllyDbg has a broken user interface...and either the stack trace is incomplete or you neglected to mention (among many other things) that the exception occurs at app launch before any user code is reached (in which case there is nothing to debug!).

I've never used OllyDbg, but try scrolling the Call stack window down until Called from shows the most recent call from a non-system DLL. Maximizing the Call stack window would give the best big picture.

RtlInitializeCriticalSectionEx is in Kexbases.dll; it doesn't need to be in ntdll.dll. Make sure extensions are enabled on Kexstubs.dll (BASE is best).

Debuggers must attach after KernelEx has loaded the app or plugin: In Ollydbg: File > Attach In VC5/6: Build > Start Debug > Attach to Process..." In Ollydbg: Options > Just-in-time debugging In VC5/6: Tools > Options > Debug > Just-in-time debugging Debuggers can also be manually configured in Win.ini or HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to attach upon crash: [AeDebug] Auto=0 Debugger=C:\OllyDbg\OLLYDBG.EXE -AEDEBUG %ld %ld ;Debugger=C:\DevStudio\SharedIDE\BIN\msdev.exe -p %ld -e %ld ;Debugger="C:\Program Files\finesse.exe" -v -p %u -e %u

[Kernel32.dll] InitializeCriticalSectionEx=>Ntdll:RtlInitializeCriticalSectionEx Requires Kexbases.Ley0k or Kexbases.11 or later.

Your system should be a fresh (or well cleaned) OS install with no previous sound drivers or USP, DirectX, or KernelEx upgrades. The instructions on page 1 should work for the CT4780. Also, please read this CT4780 success story back on page 6.

The OllyDbg screencap shows the NULL pointer in EAX came from the first parameter. The code wants to check the first two bytes (WORD) of the input string for the disk designator sequence: "\\" (5C5C). Location of crash is in LoadLibraryExA_fix because LoadLibraryA_fix is: return LoadLibraryExA_fix (pLibFileNameA, 0, 0); Also, this is the last line in KM_ApiLog.txt: 4 fff78645 [XUL.DLL]02c0323a:LoadLibraryA(bfa4bb8c) bfa4bb8c is in Kexbases.dll (version 4.5.2016.20), so Kex wrapper of LoadLibraryA is called from XUL.DLL with return address of 02c0323a. Crash happens before LoadLibraryA returns. Kexbases.dll (version 4.5.2016.21) now contains a NULL-pointer check to prevent such a crash. (Note: over-explained in places for the benefit of non-programmers trying to learn.)

Check the hardware requirements. What is the exception? Does it happen at reboot or TV launch?

KernelEx 4.5.2016.21 delta.7z - 173KB KEXBASES.DLL 553,752 05-28-19 3:34a 4.5.2016.21 * ...asap... KEXBASEN.DLL 274,920 05-27-19 4:23p 4.5.2016.21 * ...asap... sheet.dll 17,408 01-24-19 3:14a 4.5.2016.19 * jumper's current version. * Known bug: [Okay] after [Apply] acts like "Undo" * Tip: Match "Disable KernelEx..." with "Override settings..." for best disable CORE.20i 10,136 06-11-19 3:40a 4.5.2016.20i * core.ini for use with .20 and/or .21 DLLs * supports all legacy modes

Which MSFN theme and browser are you using? And what desktop resolution are you using? If 1600x1200, try windowing the browser to about 800x600 and then slowly enlarge it first horizontally, then vertically. You can also try switching themes and disabling javascript.

> MaxPhysPage=3E6FF (or change value accordingly If it already exists, do we use the higher or lower of the two values? (Are we trying to increase or limit this system setting?)

Did you try googling "ERD 2003"? Adding "site:msfn.org" finds many threads on that subject.

> I finally got to look at debugging. There is no errors with DW for AdvSplash.dll or any other file. How did you determine that SetLayeredWindowAttributes not exported from User32.dll and stubbed? by KEX was the problem? AdvSplash.dll can't be profiled directly in DW, it must be done indirectly by profiling KMPlayer.exe. Method 1 directly identifies SetLayeredWindowAttributes. SECUR32.DLL is missing some functions; Kexbasen forwards them to Unicows.dll, but some are just stubs. They seems to be present in DIGEST.DLL, MSAPSSPC.DLL, and MSNSSPC.DLL. Does everyone have all of these DLL's? Which DLL should we use and what functions should we forward to it? KTree and DW can be used for this investigation.

rtfreesoft.blogspot.com

Investigating... > ffox10_98SE.thumb.PNG Haven't seen results like this. I'll retry firefox-10.0.12esr-rayflood-win32-vc8e (it's been a few years). > ffox10_98FE.thumb.PNG Looks good--must be something in the SP 2.5.8 water. The missing ellipsis at the end of the first tab (should be: "in 201...") can probably be fixed with a font update. > kml74olly.thumb.PNG I think this is the first report of someone trying KG74 on 98fe. Unfortunately, OllyDbg didn't pick up the function names from the Kexbases debug info (GoBug does). The crash is because LoadLibraryA is called with a null pointer instead of a filename string, resulting in the page fault in LoadLibraryExA. I can update LoadLibraryExA_fix to check that parameter before using it, but that won't solve the underlying problem. Because of 52Ch bytes of local variables, the stack dump doesn't show the return address. It would be nice if the crash dialog also showed the call stack or even an [ebp] dump. (Dr Watson dumps do, but I always have trouble deciphering those or even getting DrW to capture the crash.) OllyDbg probably can display the call stack, but it isn't in the screenshot. > KM_ApiLog.7z Call to LoadLibraryA confirmed. Profiling in Depends might also confirm the NULL parameter.

In February 2018 I was able to surf simple websites with KG76 on 98se+Kex..19(pre). The main problem was all menu text truncated to one character (unicode strings not getting converted to ansi). After a few weeks it seemed to get stuck in offline mode--maybe a iphlpapi issue. Only this January (2019) did I start testing KG74. It works pretty well on older websites or with js disabled (and sometimes on newer sites with js enabled). Error console is okay. What are ExExceptions and "xul page"? Have you tried RoyTam's FF3.6+tls1.2 build?

Why are you posting in the Windows 9x/ME section? Thanks, LoneCrusader.

If not Firefox 2.0.0.20 running on stock Windows 95, please provide version and operating environment details.

> I do not think that USP10 was set disabled with 4.5.2 from what I remember. Check settings.reg. Regarding GDI32.GetCharABCWidthsI, the Kernel4.5.2 source code states in UberGDI.c: //NOTE: usp10 is probing for that function, don't forget to exclude it GDI32.GetCharABCWidthsI is disabled in Core.ini for Base, but reenabled for Win2000. So Usp10 must be set to Base or disabled. If set to default, it will inherit from the app that loads it resulting in incorrect behavour for Win2000+. > LH5048 USP10 had to be set disabled were as LH4093 and MS Office XP 1.420.2600.5969 did not need be disabled. LongHorn or other upgraded versions might probe for other functions, so Disabled is the safest mode for USP10. Thanks for testing these other versions and reporting what modes to use for each of them.

@Goodmaneuver, > CharNextW = 40f118 cycles endlessly incrementing last number Increments by two because it is a WORD pointer. Slow for long strings, it should end eventually. "Exclude" filter it. > It takes a long time to get to the splash screen after the file check when ApiLog is running. Use the filters and/or minimize the window to speed ApiLog up. > Is there any other debugging that can be done? 1. EAX is 0, so 099515ee (first stack value) may be the return address following a "call eax" instruction. Use Procwin to disassemble the instructions just prior to 099515ee. Look for a GetProcAddress() call. Notice that the last line in ApiLog2K.txt is "1 ffe77dd5 [ADVSPLASH.DLL]099515c1:GetModuleHandleW = bfc00000" 2. Profile it in DW. Any GetProcAddress() failures should be highlighted. I was able to reproduce the original problem in KMPlayer_EN_3.0.0.1442.exe. The definition for SetLayeredWindowAttributes changed in Kex..11 so this regression must be that old. This issue is arguably a design flaw in the KMPlayer installer: Instead of testing for the functionality it wants, it tests for the platform and then assumes what functionality is available. @Dave-H, repeated sections are ignored (or maybe just repeated section+names ???). Try changing descriptions; one place will work, the other won't. Leaving repeated sections in place now risks problems later. @Goodmaneuver, I don't understand: > causing problems with CometBird what are the symptoms? > which relies on USP10.dll for text why do you mention this? > I use USP10 KEX disabled. Good. That is how 4.5.2 sets it because it is required! Any other setting would be an invalid installation.

Oops, missed a few Aliases! Try appending the following to CORE.INI: --- Aliases to support legacy (old) registry settings --- [DCFG1] inherit=BASE contents=std,kexbasen,kexbases desc=Alias for Base enhancements [WIN98] inherit=WIN98SE desc=Alias for Windows 98 SE [NT2K] inherit=WIN2000D desc=Alias for Windows 2000 SP4 [NOHEAP] inherit=WIN2Kstd desc=Alias for Windows 2000 SP4 (standard heap) [WINXP] inherit=WINXP2 desc=Alias for Windows XP SP2 Also (optionally) delete the DCFG1, WIN98, and WINXP sections from higher up . Thanks!!!

#define SHGetKnownFolderPath(a,b,c,d) (0x80004005) #define SetProcessDPIAware() (0) #define SymGetSearchPathW(a,b,c) (SetLastError (120), FALSE) #define SymSetSearchPathW(a,b) (SetLastError (120), FALSE) > Windows ignores my fake Shell32.dll and uses the one in System32 In the same folder as the app, try creating a subfolder .exe.local and put your dlls there.

Sounds like it hangs autodetecting one of the internal devices. If you can't boot in safe mode, try a logged or stepped boot. Otherwise you'll have to try all the regular installation problem suggestions.

@Dave-H > 4.5.2016.20 just contains an updated kexbases.dll for instance. Incorrect Not quite. It also includes the Core.ini update that unlocks all new Kexbases.dll improvements. Both should be installed together. @Goodmaneuver KexBeta18.7z was nearly cumulative, but .19 and .20 are just "delta" (changes to .18) updates. > Having install trouble with KEX20 on anything above NT6a on an install that only requires KEX enabled before. KMPlayer any vs 3+ installed on any setting before except disabled. Is this an expected outcome? No, please debug it. TIA.

> latest kernelex 20 updates + SMPlayer 0.8.6 (portable) Using both Core.ini and Kexbases.dll? Please confirm the compatibility mode used. Thanks for the good news! > MPC-HC 1.6.4.6052 will only install but does not work. Please try MPC-HC 1.7.5. > There are a few issues though: screenshots taken with the software will appear as black in the video area and the play button and time won't change. With what software? Is this a new issue or a regression?