schwups

I think it has to do with the KernelEX update and it isn't caused by ReactOS files. Probably jumper has changed a lot inside KernelEX. Many compatibility modes are introduced. Changing the modes fixes the problem here. "IsProcessorFeaturePresent" is still supported, but you must set Windows 2000 or higher! Try "Legacy Base enhancements", if Win2000+ works incorrectly.

I tried f3e, but it isn't a good value here. There are too many adverse effects. Also K-Meleon 74 doesn't start. Better is o3e0. My method was by trial and error. So far, I haven't found any problems. Of course Foxit 9.2 doesn't run. The gui opens and it crashes immediately. KernelEX: 4.5.2016.21 / Core20i [KERNEL32.DLL] ConvertFiberToThread= InitializeCriticalSectionEx=o3e0 QueryThreadCycleTime= DbgHelp.dll of Vista - SymSetSearchPathW and SymGetSearchPathW More Api's are required with KernelEX 4.5.2. How can I keep the KernelEx mode setting on Kstubs.dll for testing? It always falls back to disabled after restart.

Yes, I had overlooked it in Ktree. I tried different modes on Kexstubs.dll. I get this Faultlog, e.g.: Kexstubs set on Base enhancements (api fixes + extensions) Date 06/28/2019 Time 12:33 FOXITREADER caused an exception 03H in module <unknown> at f577:00000001. Registers: EAX=00000000 CS=0177 EIP=00000001 EFLGS=00000246 EBX=000002f6 SS=017f ESP=0509fdac EBP=00000fa0 ECX=00000fa0 DS=017f ESI=03a18290 FS=4887 EDX=bffbb490 ES=017f EDI=03a18288 GS=0000 Bytes at CS:EIP: 00 ff ff e4 d2 6a dc c3 e2 00 f0 2b 04 70 00 2b Stack dump: 03a18290 0509fdc4 0283ebe8 03a18290 00000fa0 00000000 0509fdf4 02838c6c 03a18290 02d17660 00000004 0046c768 028cbb58 00000000 815b4210 04f90000 Kexstublog: = Kernel32.dll:InitializeCriticalSectionEx=>ntdll:RtlInitializeCriticalSectionEx = Also K-Meleon 74 doesn't start anymore: Date 06/28/2019 Time 12:41 K-MELEON caused a stack fault in module KERNEL32.DLL at 0177:bff64277. Registers: EAX=815b5c88 CS=0177 EIP=bff64277 EFLGS=00000283 EBX=00000000 SS=017f ESP=007d220c EBP=007d2230 ECX=f5776210 DS=017f ESI=815d36b0 FS=65c7 EDX=815ce6bc ES=017f EDI=815b5c7c GS=0000 Bytes at CS:EIP: eb 95 8b 54 24 04 50 e8 04 00 00 00 58 c2 04 00 Stack dump: bff641cf 815ce6bc bff899f1 815ce6bc 815ce65c 815b5c7c 19983272 00000002 19983272 007d2260 bff818a8 19983272 00000000 19983277 19983296 bfa4be27

Is it meant as an approach or is it already worked out? RtlInitializeCriticalSectionEx was introduced with Ntdll.dll of Vista. The ME ntdll.dll doesn't support it. I tried to rename the Vista ntdll.dll to 9xdll and changed the line to - InitializeCriticalSectionEx=>9xdll:RtlInitializeCriticalSectionEx -, also without success. KernelEX: 4.5.2016.21 / Core20i

Does someone have a working definition for InitializeCriticalSectionEx or is there any possibility for a useful definition, e.g. Foxit Reader 9.2+ needs this API? InitializeCriticalSectionEx without value or a bad one causes a lot of problems.

It looks good so far. VLC 3 runs again - the runtime error is gone. What has caused the error? But I get errors at VLC close: ********************************************************************** Date 06/22/2019 Time 00:20 VLC caused an invalid page fault in module KERNEL32.DLL at 0177:bff8e066. Registers: EAX=01740028 CS=0177 EIP=bff8e066 EFLGS=00010206 EBX=0aa8c748 SS=017f ESP=0173ff0c EBP=0174002c ECX=0173ffd8 DS=017f ESI=01740134 FS=260f EDX=0174004c ES=017f EDI=0174004c GS=0000 Bytes at CS:EIP: 50 51 ff 75 08 8d 85 e0 fe ff ff 50 ff 75 0c e8 Stack dump: and or ********************************************************************** Date 06/22/2019 Time 00:41 VLC caused an invalid page fault in module NVOPENGL.DLL at 0177:0a4fe005. Registers: EAX=86d9e19c CS=0177 EIP=0a4fe005 EFLGS=00010202 EBX=00000002 SS=017f ESP=0193fd7c EBP=00000001 ECX=0054d080 DS=017f ESI=0054d080 FS=2c8f EDX=00000000 ES=017f EDI=0a400000 GS=0000 Bytes at CS:EIP: 8b 46 68 89 44 24 08 64 a1 18 00 00 00 03 05 14 Stack dump: 00000000 0a4fdd1c 0054d080 00000000 0a4fde22 f8773dcb 00000000 00000002 0193fdc0 0a400000 0a7b4fb1 0a400000 00000002 00000000 00000000 0a400000 ********************************************************************** However, the system remains functional. The first error can only be eliminated by reboot.

Same here, so probably that's normal. (NV7800GT/ driver 82.16). Agp texture accelaration is certainly no PCIE feature and dxdiag from 2004 is older than these graphic cards.

Take the full package 4.5.2 from sourceforge. A full package 4.5.2016.18 or .19 doesn't exist!

I have to keep "opera.dll", "html5_entity_init.dat" and the gstreamer folder of 12.02.

19 looks good. The KernelEx.dll works again. So far, no new errors have occurred here.

Sorry, I didn't say it here, that I extracted 7.0.2 with 7Zip and ran the GoogleEarth.exe in the client folder. GE is or should be installable up to version 6.0.2.

Thanks, if I figure out something, I'll let you know.

For about a month, maybe a little more, GE 6.0.2 or a lower version doesn't work anymore. The server login failed. Error Message: "GE can't contact the imagery server to download new images. GE detected an error while trying to authenticate." I guess something like a handshake Problem (SSE/TLS). I tried higher versions and succeeded partially with version 7.0.2.8415 (VC++ 2010). Test system WIN ME / KernelEX update 18). On my main computer (G41/Core2DUO Wolfsdale), I can start and run it, but ME crashes after close. Best is to restart directly by CTRL-ALT-DEL. On another machine (ME/KEX18/G31/Core2DUO Wolfsdale) GE 7.0.2 starts, do login, the globe appears and the zomm works, too. However, no new images are loaded here. I suppose a missing dll on the second one. I had ruled out KEXT after a test. Does anyone have any ideas or suggestions about this?

Yes, install the Chipset drivers directly after OS. That's the normal procedure.

Did you install the chipset driver first, before you install others?

So far I can see you didn't install the VIA 4in1 chipset driver. You have "PCI standard host cpu bridges" in your device manager. This indicates there are only standard MS drivers. The Via device name is "VIA standard host bridge". I don't believe that there is a problem with ACPI. I've a VIA P4M800 (VIAVT8237R). It isn't a laptop, but there aren't any problems.

@jumper: According to my tests should the culprit exist since update 11 in Kexbases. Like I said VLC 3 works up to update 10. You added "KERNEL32.CheckRemoteDebuggerPresent=" and many more API's to Kexbases 11. I entered "KERNEL32.CheckRemoteDebuggerPresent=" to k452stub to overwrite kexbases here. That's the only way it makes sense to me. The function in the stub file on the left (contents=kexstubs,std,kexbasen,kexbases) is irrelevant, because it should be overwritten by Kexbases 11 or higher. VLC 2/3 is useless in XP mode. Probably the same applies to version 1.x.x. Goodmaneuver described the errors.

I tried this with two different lines in the [BASE] section, but I can't see an effect. [BASE] contents=kexstubs,std,kexbasen,kexbases - here in [WINXP.names] KERNEL32.CheckRemoteDebuggerPresent= kexstubs .0 and [[BASE] contents=kexstubs,std,kexbasen,kexbases,k452stub - here in [WINXP.names] KERNEL32.CheckRemoteDebuggerPresent=k452stub.0 The second case was to overwrite kexbases. The runtime error on VLC3 start still persists. I don't comprehend your advice to test that line in the core.ini. Why Kexstubs (CheckRemoteDebuggerPresent=kexstubs.0) and why in [WINXP.names] section, although VLC must work with "default mode" and not XP mode?

I don't get a detailed error message. (This application has requested the runtime to terminate it in an unusual way.) DumpPE creates a very large logfile of 14MB. What should I look for? Taking into account the changes from release 10 to 11, only these api's have become conspicuous for me. It is only my suspicion. I tried to override the added api's with K452stub.ini or core.ini. The two abovementioned showed an effect. Already the Explorer didn't start. MSVCRT.DLL was mentioned in that message.

I would like to report that VLC 3.0.x runs with the Kext entry "[Kernel32.dll] CheckRemoteDebuggerPresent= " up to Release/Update 10. The runtime error occurs since kexbases 11 and higher. Could it be to do with LeaveCriticalSection and SetCriticalSectionSpinCount?

I'm surprised how easy it is for me to run VLC 3. Only the Kext entry "[Kernel32.dll] CheckRemoteDebuggerPresent= " is required. Thanks for the hint. System: ME, KernelEX 4.5.2 and Kext. VLC 3.0.4 runs also up to KernelEX update 8. Using update 12 and higher VLC fails to start and gives a runtime error. As far as I can remember the updates 9 to 11 made problems for me, so I didn't testet them.

The Opera HTML5 Player still plays some interviews and documentations, but no music anymore here. The you tube HTML5 testpage gives the same information for FF9.0.1 and Opera (12.02 / 11.64), that WebM VP8 and HTMLVideoElement is supported. The other formats have the exclamation mark. I found this to use Greasemonkey user scripts in Opera, but it doesn't work: https://www.ghacks.net/2008/08/10/greasemonkey-in-opera/

Marvellous, I also tested it with Flash 21.0.0.242. Is it possible to make the script working in Opera Presto, too?

I only use ME with KernelEX and not in a VM. In my opinion Opera 10.63 from October 2010 should be your best choice. But you can give Retrozilla a try, too.

Y2mate works well. Thanks. Other (webm): Audio streaming mp4, mp3, Audio: I've two possibilities open with e.g. VLC or saving