jumper

Check again....

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.

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.

> 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.

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.

Not helpful. Please reread and try again.

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.

When having problems, don't install a newer DX9 than the video drivers were officially tested with. For 77.72 this means June 2005.

> 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.

System error at app load, or app error later? 64-bit Vista, app, and Dbghelp?

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.

Quote implies partial support will remain.

> 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.

Maybe from the onboard diagnostic speaker/buzzer? Try covering the sound hole.

Ktree11 now has a font chooser (F9). I'm also adding an HKLM\System\...\KnownDLLs branch. Any other requests?