JosefReisinger

Hey I've localized nearly all Exkernel-version-systemfiles into DEU, but without installer, since I use the Exkernel Installation DVD 2017 localized DEU including excore16; then I only replace the old files with dual boot system if a new exkernel version of bwc comes up. Sometimes, also the .inf - section has to be changed, I do it manually. So, if you are interested, I could upload DEU system files v3.0 or also latest v3.1L, but you will have a lot of work ;-) PLZ PM to discuss this deeper! Greetings from Austria, Joe

Hey There seems to be a regression bug in user32.dll v7170 from Exkernel 31lM. Older program Microsoft Money 2000 crashes on Mouse Action on omap in split half transactions, but also randomly in other circumstances.. This behavior (Access violation of memory with "read") cannot be reproduced when introducing old Exkernel user.dll v7167 into the Exkernel 31l System, nothing else changed. So, perhaps @blackwingcat could find a solution for this Greetings from Austria, Joe

Hey, roytam1, "nosniff" problem is gone with palemoon 12102024, thank you so much Greetings Joe

Hey ;-) One website of the vpn connection is working after upgrading to palemoon-28.10.7a1.win32-git-20240810-d849524bd-uxp-fde09c8b49-xpmod.7z, thank you so much. The other website complains about mime mismatch: "Fehler: Die Ressource "https://XXX:11443/remote/login?lang=en" wurde durch einen MIME-Typenkonflikt blockiert (X-Content-Type-Options: nosniff)." With mypal68 I'm able to work with the website, but it is a little bit buggy (crashes). Could palemoon be adviced in a future version to ignore the mismatch? Or could you provide instruction how to get rid of the mime problem for this particular website with the current version? Greetings Joe

Hey @roytam1, I use palemoon-28.10.7a1.win32-git-20240720-d849524bd-uxp-8fbf81bb8a-xpmod.7z on w2k extended kernel (blackwingcat v31L, perfectly localized into DEU), and find it the most stable and capable browser, thank you so much . But all of the backported browsers (also mypal68 and ExtremeExplorer360) cannot handle VPN calls against fortigate, which I have to use with my company. Any help is appreciated, so I will describe the details: It is possible to log into 2 vpn sites in my company via (A) web interface or with (B) forticlient. (A) If I use the web interface with palemoon, I get connection. A web interface is presented after logging in. There I have a window to fill in the page I want to reach (https://xxx), get a token (salt) to the website, but then I have to enter my user and password again, this causes infinitive registration loop, the form with the user and pass is not accepted with palemoon and every other modern XP browser (tested on w2k extended kernel, but also on xp64 (native)). It works with firefox browsers >100, tested on win7. It seems not related to the system, the routines seems to stuck in the browser (tested with process explorer). (B) The Forticlient app needs Win8 or higher. It could be really hard to get a proper forticlient for XP in these days, as the company hides the offline installers and a paid service contract is needed to get forward to them. It is also true, that these old versions couldn't be able to connect. But if they could, it could be useless. if the browser cannot handle the registration on the requested vpn site. I can provide sceenshots, forticlient logs (Ubuntu 22,04, but also Win11), but also palemoon console logs. PLZ help, I don't want to reboot permanently into a modern system to get to these pages Greetings from Austria, Joe

Thank you very much for your answer and insights, I posted it to the author in the mypal68 thread. Greetings, Joe

Hey Guys Thx for Mypal 68!!!! I tried Mypal 68.14.2 on exkernel w2k and found hardcoded breakpoint which should not be in an application, is it possible to remove it? It causes crash https://msfn.org/board/applications/core/interface/file/attachment.php?id=54635&key=c2786a644e4b70a1faedee5ea3f8dd9c Greetings from Austria, Joe

I tried Mypal v68.14.2 with Exkernel 31L. Unfortunally there are a lot of crashes with omap. Any help appreciated - watson log: Greetings from Austria! Joe crashreport.txt

Of course, I have these options, as you can see, furthermore 2560x1440 is listed as native resolution (PC), but not for the monitor. I succeeded in installing HP monitor-inf-file by deleting the service installation instances in xpx64 and w2k exkernel, but this did not resolve the problem :-(( Greetings Joe

Thx for your answer, Goodmaneuver! If I try to adjust with control panel with res 1920x1080, I can see the menu item "2. Change size of desktop", and I can use it. if I use it with 2560x1440, the menu item is gone, instead I see information symbol, but I cannot read the text because of the underscanning. So I will try to put the relevant contents of monitor driver inf. file by hp in monitor.inf, as suggested by Jumper. Monitor driver file was written for win10 64 bit, I tried to install it but failed due to "wrong inf-section", see attachment (I yet changed the [HP.NTamd64] in [HP] for proper installing in w2k). It also failed in XP64. This gave above error message. W2k will install it without error, but then show exclamation mark with code 31. Greetings Joe OMEN_32q_QHD.inf

Thx for your answer! The monitor is connected with dvi -> hdmi cable, there is no auto-resize button on the monitor. It is a HP Omen 32q. Greetings Joe

I bought a new monitor 2560x1440@144 and I get max. 1920x1080@60 with w2k and Exkernel v3.1, nvidia geforce gtx 960, driver 6.14.13.4788. If I switch to 2560x1440 - yes, I'm able to do so: Left and right on the monitor is black, in the middle "compressed" image. Same Error occurs with XP x64, no kernel extension (!). Is there a limit in monitor.sys ( I use Plug&Play Monitor)? Perhaps @blackwingcat can help. Greetings from Austria, Joe

@blackwingcat I found out that kernel32.dll exkernel31 (in my case 5.0.2195.7281) is buggy with installing some programs when slipstreamed into w2k dvd. Adobe IX will refuse to install ( I use: START/WAIT CMD /C CALL qfcwin.cmd msiexec.exe msiexec.exe /passive /norestart /i AcroRead.msi msiexec.exe /passive /norestart /p AdbeRdrUpd11023.msp installation window will be seen as long as I want with no result - I have to stop it with taskmgr to proceed). Adobe Reader IX also cannot be installed afterwards with cmd/msiexec. If I use kernel32.dll 5.0.2195.7273, everything is fine and installation will proceed. Also, some VB runtime and update installations are affected. Greetings Joe

SAD NEWS! Zoom 3.5.53922.0620, actually has stopped to work at all, as I had to notice, video connection crashes and forces the program to prompt for update, although it was patched and shows "up to date". The reason - problem with connection to server, I suppose ... so we need help from our Guru Blackwingcat - is there a possibility to get XP Version 5.0.5 (26213.0602) working with Exkernel W2k? Please, please, please!!!!

@blckwingcat Perhaps tp.dll crashes because it wants to see wireless api XP, what do you think? Greetings

Zcrashreporter produces dump files in zoom\logs. I don't have a dump viewer. But as I can see, cpthost.exe crashes with ntdll on screen sharing (old version 620). Perhaps you can have a look on it. zoomcrash.zip

Can you give advice how to solve the sceen sharing? Sorry for my impatience! Greetings

I tried to run zoom actual xp version with tp.dll 3.5.53922.620. It is not possible because of missing depends ?new_instance@socket_ctx_t@ssb@@SAPAV12@PCIIPAVmsg_db_t@2@@Z in old tp.dll. Greetings Joe

@blackwingcat: did you get my email?? Greetings

I debugged CptHost.exe with cdb.exe (old version): It seems that d3d9 is involved. d3d8thk.dll xpsp3 has function DdEntry1 ....10 in it,, d3d8thk.w2k does not, so if I use d3d8thk from XP, complaint about "missing dependency DdEntry1" in GDI32.DLL is the result. Start Screen sharing: 0:004> g Unknown exception - code 406d1388 (first chance) ModLoad: 4fd50000 4fef6000 C:\Dokumente und Einstellungen\Administrator\A ungsdaten\Zoom\bin\d3d9.dll ModLoad: 01120000 01125000 C:\WINNT\system32\d3d8thk.dll ModLoad: 768d0000 768fb000 C:\WINNT\system32\WINTRUST.dll ModLoad: 799d0000 79a56000 C:\WINNT\system32\CRYPT32.dll ModLoad: 77400000 77411000 C:\WINNT\system32\MSASN1.dll ModLoad: 76c50000 76c78000 C:\WINNT\system32\IMAGEHLP.dll If I close the app, CptHost.exe crashes: Access violation - code c0000005 (first chance) eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=001395f8 edi=000000 eip=7788f281 esp=0012fb68 ebp=0012fbc8 iopl=0 nv up ei pl nz na pe cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=000102 ntdll!RtlpWaitForCriticalSection+8a: 7788f281 ff4010 inc dword ptr [eax+0x10] ds:0023:00000010=?????? 0:000> On "Exit" in systray, Zoom.exe will not shut down. One of two instances will stay. With XP, it will close all instances. Now I need a hint of the more experienced users here: how do I find out "code 406d1388"? If I disassemble CptHost.exe, adresses are different. Greetings Joe

I disassembled CptHost.exe and got Imports and Exports. CptHostImportsExports.txt PE Explorer Disassembler found errors. *Unexpected Opcode (mov r/n16,Sreg) at 0041C200h *Line caused Error (F3 retn) at 0041BA14h The interesting entry: L00401255: mov eax,[ebp+08h] push 00000007h push [eax+04h] push [eax] call [USER32.dll!GetDesktopWindow] push eax call [USER32.dll!ChildWindowFromPointEx] L0040126C: mov edi,eax L0040126E: mov eax,edi pop edi pop esi pop ebp retn 0004h Greetings Joe

I would like to know the windows functions which are called by desktop sharing in the zoom app. Fortunally, the zoom sdk for windows is available in the net. Unfortunally, only the latest version and not v3.5. For the more advanced it should be possible to program a proper app for w2k exkernel with visual studio 2008. I found the source of screen sharing: meeting_sharing_interface.h Perhaps the more experienced users here can find out something, but I am not sure if this info is relevant. Greetings Joe

Thank you for your comment! I changed crypt32 to XP, no effect, app works but screen sharing only seems to work - conference partner only sees black screen. I think the problem could be related to graphics. In the middle of examing the graphic components, CptHost.exe will load vga.dll in XP. It will not do so in w2k exkernel. Perhaps the app needs vga service XP? I have uploaded the different outputs of procmon on w2k Exkernel and XP. Any help appreciated. Greetings Joe 2kCptHostLogfile.xls XP64CptHostLogfile.xls

Back to zoom investigation (error with black screen - screen sharing): Investigation with Pe-Explorer: CptHost.exe is loaded if video is started. If I click "share desktop", depending setupapi will load crypt32.dll, which will load msasn1.dll and wintrust.dll. Also, imagehlp.dll will be loaded. I tried to replace these with XP ones, no change. Also, changing of gdiplus will not resolve the black screen error with screen sharing. Ivestigation with procmon: zoom.exe will call msimtf, "create file mapping", and then has a lot of activities with zoomus.db in the data directory. CptHost.exe will load d3d9.dll and has a lot of registry activities checking the graphic components. So I think it will be necessary to debug CptHost.exe. Greetings Joe

Perhaps there is a problem with d3d9. If I use exkernel v3.0e d3d9.dll with zoom cloud meeting, on my system the app gets buggy, screen flickering etc. So you can copy XP d3d9.dll (I used 5.3.2600.5512, but it should also work with 5.4.21.95.5513) into the zoom folder. The app will use this one. Greetings Joe