JosefReisinger

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