dxwrapper
dxwrapper copied to clipboard
elishacloud
Revised informative post (working our code & FunkyFr3sh), Direct3d may be stable for Server Vista & community project
Mean Points, this is just info we are not looking for a fix (at this time) as we are busy with other things with our community. except DR Seuss which is on hold at this time.
We are working around FunkyFr3sh code with our own code for compatibility degrade. we do at occasionally might use DxWrapper unless it breaks Vista. We cannot fully support or endorse as we do have a mac rework division. We only know 2 wrappers with support like FunkyFr3sh (cnc-ddraw) or wine d3d our community is using.
Just skip to 3 if you don’t want the details.
1 Dr Seuss is a complete loss to all emulators with unclear workarounds.
Most likely is suppose work but don’t DirectX 1-7, DxWnd. Nglide, DxWeapper, DdrawCompat, cnc-ddraw, DXGL, Glidos, dgVoodoo, OpenGlide, psVoodoo, glraage, Rready, Xoutput, DSOAL,
even these emulators, that we tested ware made for DirectX 8 & above, DgVoodoo2, D8VK, DXVK, WineD3D, VKD3D-Proton, vkd3d, d3d8to9. Mesa3D for Windows + Mwsainjector, grvk.
as for cnc-ddraw, even if FunkyFr3sh did manage to work. They are some Dr Seuss games that can’t work due to direct3d 2-7, which DxWrapper, is the most likely candidate for a fix. as FunkyFr3sh appears or at less know the developer allthough we don't understand the connection of the 2.
2 DdrawCompat, clams to support Vista but based on our limited testing starting around 0.4.0 we dont thick that is the case although (extended kernel works). this developer might be mistaken. unless we are at fault.
We are a community of 38 people, 2 people on the team of which have windows vista with 2 partitions.
Person 1 with 2 500 gags partitions with Vista. Persian 2 Windows 7 & Server 2008 web edition.
Person 1 specs have with intel HD graphics 4000. support features open GL 3.3 with direct3d 11 support. 1st partition: Vista with clean 2017 Eos. 2nd partition: Vista with server 2008 updates. prerequisites
Step 1: prerequisites LegacyUpdate-1.9.exe These below is for server updates. step 2: KB4493730 and KB4474419 step 3: Vista_SHA2_WUC, & WU_DataStore_Fix, install as Mach or all updates from https://support.microsoft.com/en-us/topic/january-9-2024-kb5034173-monthly-rollup-88eb4c50-8e48-4443-ab60-8e0f6e24e4df step 4: newer mouthy rollups not included in windows update
person 2: same as 1 above except this person is mostly using Windows 7. Sometimes Server 2008 sp3 web with NVIDIA graphics 1060. for compatibility testing if person 1 fails due to features. as a bonus has open gl 4.6 support.
in other words, if you're planning to add newer DdrawCompat It will most likely fail or kill Vista altogether even than it does not work with Virtualization hypervisor which makes our jobs harder as our community is still targeting Vista.
3 Mean points conclusion, originally our community was made in 2018 to rework the learning company installers for 64-bit windows. In 2020, we were expending to other games like jump start -others. We started manipulating the learning company engine, even others. We have since windows 11 seen that manipulating the engine can go so far. Originally, we did look at the narzoul code originally, but we don’t feel comfortable or safe, as we have occasionally occurred very scary bugs mostly on Vista & 7 even from the community, that is why we choice FunkyFr3sh By default. as for DxWrapper only if we have no other option, Like direct 3d. Even than we will never use DdrawCompat code for stability,
At the end of the day this is your project Our community despite seeing github issues, we never had a problem or issue with vista under DxWrapper. It might be because we are remastering educational games engine. Which is simpler engine being our guess. unlike DdrawCompat at less you're not going out of your way to break Vista. If you can or know anybody to figure out DR Seuss, please due. we have to tell people windows me, no amount of manipulating the engine (we tried since 2018) or 3rd party intervention will work (recently tried with cnc-ddraw even DxWrapper. all 38 people completely given up 4 days ago. Who knows maybe years down the line that DxWrapper or cnc-ddraw can figure this out.
Aug 23 we will tomorrow test this theu windows 7 code. which can down be rerouting your code. this is the only way to tell if dxwapperXP is the issue. again im not sure how to do this, but i know others who can, and did in the past.
original question does the dxwapper support server 2008 R0 also known us vista, we had a report for a bug with i486 processor, with windows XP although windows xp never supported it. we also did other tests even Disney without [ACPI], thru emulation. to our surprise cnc-ddraw thru open GL just worked. as for dxwapper we did other tests with server 2008.
We found with our limited testing that dxwapper is having issues with server 2008 with A lot of games, and others https://archive.org/details/buzzlightyearag2000 (even others) like asking for k32getprocessimagefilenameA at kernal32, when we tried vista, it works? than we trad windows xp compatibility mode it just worked with server 2008. haa why+. we thoought that maybe https://www.catalog.update.microsoft.com/Search.aspx?q=kb5041850 which is 7 years newer is breaking the XP code due to Server 2008 is vastly different animal like windows PowerShell 3 (also known as KB2506146). which was never made compatible with vista. and the dxwapperXP can't read api's properly
he is the logs with xp compatibly mode. with the XP build dxwrapper-buzz.log
again, this game works outside of the box with vista. I and others, think you should know. We do most of the testing with that platform, as most virtualization even VMware has poor support for vista by itself
question does the dxwapper support server 2008 R0 also known us vista
I have not tested it with Vista, but on another issue someone was using it with Vista and got it to work. Server 2008 should be the same.
We found with our limited testing that dxwapper is having issues with server 2008 with A lot of games, and others
Are you sure this is an issue with Server 2008 or dxwrapper? Do these games work with dxwapper on other platforms? Is it just Server 2008 that has an issue?
Looks like the issue with K32GetProcessImageFileName is documented here: https://learn.microsoft.com/en-us/windows/win32/api/psapi/nf-psapi-getprocessimagefilenamea
Let me try to dynamically load this function to avoid this type of issue.
Ok, try this one. This should fix the issue with K32GetProcessImageFileName
Yes that fully work with server 2008 but it gives another windows 7 error but it does open the game, although not on Windows Vista by itself for some reason, this looks server 2008 only bug.
update aug 23 3:48 pm https://github.com/abbodi1406/vcredist/releases/tag/v0.61.0 it did stop the mfc140.dll. but it is odd it is calling that. my guess you are using visual studio 2022 or something is conflicting.
it is calling mfc140.dll also very odd, i believe 14.32.31332.0. is the last to support unofficial. i will found and test.
dxwrapper-buzz (Server).log dxwrapper-buzz.log
it does show this error below, but the game does open. Problem signature Problem Event Name: BEX Application Name: buzz.exe Application Version: 1.0.0.1 Application Timestamp: 39bfaa4f Fault Module Name: StackHash_617e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 0029dd7e Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.0.6003.2.2.0.1296.17 Locale ID: 1033 Additional Information 1: 617e Additional Information 2: cf86913bc0e69b6228fa82d7292de747 Additional Information 3: c69b Additional Information 4: 3d3b3d718446d3f1f73d23ca1d5d58cc
Looks like I fixed the specific Server 2008 issue. But there is still an issue with this game working. I noticed from the log files that the game uses a lot of functions I have not implemented yet.
Here are some examples:
1144 15:24:48.982 m_IDirect3DViewportX::AddLight Error: Not Implemented
1144 15:27:48.528 m_IDirect3DViewportX::DeleteLight Error: Not Implemented
Also, I noticed a lot of this log event:
1144 15:27:59.154 m_IDirect3DVertexBufferX::ProcessVertices Warning: 'D3DVOP_CLIP' not handled!
I am not completely sure that my implementation of ProcessVertices() works in all cases. I will need to download the game and check it out myself later.
Disney's Lilo & Stitch: Trouble in Paradise. People are seeing mfc140.dll. even under windows 7.
Also saying this application is not installed. Even thru it is. This operating system is not supported only on vista & 7. Compatibility mode. You mast use direct 3d 8. Again no logs.
Not on 8+ , the game runs but makes no dxwapper .log. I'm thinking the functions are in bad shape.
Even more odd this supports d3d8.dll and ddraw.dll. even under cnc-ddraw thru wine only.
We will try to get logs but all 8 people are getting northing. We are not understanding why it works.
Worse case we might give you cnc-ddraw logs. As the developer confirmed not possible to fix. Allthough thru wine not sure how it will help you.
Due you know anything or insert of this.
People are seeing mfc140.dll. even under windows 7.
That is not coming from dxwrapper. Dxwrapper neither uses nor loads that dll.
Also saying this application is not installed. Even thru it is.
I guess the game is not seeing what it wants to see and then shows these errors. Let me try and make an update to see if it helps.
do you think can properly support Dxwrapper with ddrawcompat as 2.1 did work with windows vista & 7 under Virtualization and older hardware, with 3.1 it was stating to break, more so with 4,0 that were expect broke it completely with vista altogether. it does work with 7 with nasty workarounds from our programing team. we did test your code with dxwrapper Don't fully load DDrawCompat when using Dd7to9. we did notice improvements with windows 7 and compatibility.
go to bottom for mean point. # 1
DDrawCompatNoProcAffinity & DDrawCompatDisableGDIHook gratly helps with windows 7. sadly putt putt saves the zoo from humongous, yes cnc-ddraw did add support for it but it is pare GDI without DDrawCompatDisableGDIHook it will break 7, that saves the zoo realize on, most people want it due to better upskilling and graphics improvements, even anti-aliasing with superior handwear mostly NVidia. but in our preparative even adding your code is risker as hardware without direct3d 9 is porting our community in dispense as we have told users this wrapper supports direct3d 9 only. we are away that windows 11 is the future, that is still our Goul, we were in shock and bewildered that cnc-ddraw reorganized i486 processor. as it did support open gl 2.1 https://www.intel.com/content/www/us/en/products/sku/49938/intel-pentium-ii-processor-333-mhz-512k-cache-66-mhz-fsb/specifications.html
we did fix out installers for it we just told the user, it was made in 2000, we can't guarantee, that FunkyFr3sh will with future releases support it, as we expect it was by accident. we are not saying to accommodate Pentium II, 3 or 4 as they are getting way to old, unlike DDrawCompat, we can tell you do care about your project and compatibility with older games. hick we seen you plan to add d3d10.dll, d3d10core.dll, d3d11.dll, d3d12.dll, and we respect that as we do notice issues with HW/screens, but our forces are 90's games.
1 here is the mean port we will never trust ddrawcompat code in our project, at the same time it is needed for GDI games like humongous even Scooby-case file # 1 the glowing bug man. without it may not work, but at the same time we are using cnc-ddraw for outside of windows compatibility. we would like to use ddrawcompat but we can't.
if it does get fix it will properly and most likely, be you. if you can't, we don't blame you it is on the developer.
question does this build with .logs might help you Windows (TM) Vista Enterprise 64-bit (10.0.6004) or do you prefer original kernel from vista, although we could use 7 instead if you won't more reliably source.
the reason why it sues 6004, as this is a special build of windows vista that acts and behaviors like windows 7 this build even supports K32GetProcessImageFileName from kernel32.dll (yesterday) not theu Psapi.dll, that vista uses. although not sure about windows xp. as we are now experimenting with other direct3d wrappers.
We also did some even other user32.dll improvements. for better support for direct3d wrappers outside of dxwrapper. we did give you this build by accident yesterday. that was why we give a windows 8 build last minute.
Not on 8+ , the game runs but makes no dxwapper .log. I'm thinking the functions are in bad shape.
If there are no dxwrapper log then is seems like dxwrapper is not loaded. Maybe you need to use a difference stub, dinput8.dll or dsound.dll. Some games will directly load dll's from the System32 folder. In these cases using a different stub may help.
do you think can properly support Dxwrapper with ddrawcompat
Probably not. However, if there are parts of DDrawCompat that have issues on certain platforms I can force disable those parts, like I did with DDrawCompatDisableGDIHook.
Part of the issue here is that DDrawCompat does most of if fixes in DDI, which I believe was only added in Windows Vista. Older versions of Windows does not even have DDI. This means the whole thing would need to be rewritten for the older OS. Also, a number of the DDI functions that DDrawCompat relies on does not even exist in Windows Vista.
Are you trying to use just DDrawCompat or do you want to use both DDrawCompat plus either dd7to9 or d3d8to9?
we did test your code with dxwrapper Don't fully load DDrawCompat when using Dd7to9. we did notice improvements with windows 7 and compatibility.
I can disable DDrawCompat when using Dd7to9 on older operating systems, like Windows 7, if that will help. Are you saying the current DDrawCompat functions used by Dd7to9 work good on Windows 7? What about older OSs?
that is right current DDrawCompat functions used by Dd7to9 work good on Windows 7? yes, they mostly work with the games just fine although We mostly test TLC games and some Disney's not all of them but yes. not sure about others.
as for DDrawCompat no we are not trying to use it by itself or going to our installer projects due to Vista & 7 issues however DDrawCompat with dd7to9 or d3d8to9?, to answer your question that is yes based on better upskilling support,
As for older systems, very unlikely as even in windows 7 it was staggering with virtualization but indeed working. it might be on vmware player as we & I notice that they are adding openGL 4.5 support although disabled with tools 12.4.5.
if it does work with vista (the generally public will be never), it will mostly likely be Windows Vista Build (10.0.6004)
which has stuff like "TryAcquireSRWLockExclusive", GetLogicalProcessorInformationEx, & SetThreadGroupAffinity even others I don't recall as someone us is making the kernel for better debugging with older systems. now I kinder know stuff like rerouting like with K32GetProcessImageFileName I did yesterday. but technically I'm doing is grey. I can't make or add new functions in the vista kernel, that never existed in the 1st place.
We trad everything we could the game clams it is d3d8.dll we strongly believe it is lying. as it works woth wine (software) it might be direct3d 7. if it is d3d8.dll, the closes we got was windows xp, sadly we got no log reports.
The game is definitely using DirectX7 not 8. It probably says it requires DirectX8 because when you install DirectX8 you get the latest version of DirectX7 included.
The issue with the game is the below logs:
820 01:49:39.348 m_IDirectDrawSurfaceX::Blt Error: no ddraw parent!
820 01:49:39.348 m_IDirect3DDeviceX::GetCaps Error: no ddraw parent!
820 01:49:39.348 m_IDirectDrawSurfaceX::Flip Error: no ddraw parent!
Basically, this says that the DirectDraw got removed while the children interfaces are still being used by the game. Not sure what combination of functions the game called to cause this. I will need to test it myself when I get a chance. This looks like a straight up bug in dxwrapper.
Iv just notice Check kernel32 for Windows Vista, 7 and 8. i thought let's try custom extended kernel. it works out of the box although SetSearchPathMode is disabled due to miner issues. so Jecob R decided to have a wait and see appose. even if it did cause problems in the long team, it's really our problem at the end of the day.
are you making sone sort of leveling system, that windows 7 or vista is not as bugged, or is it the case that really soon you will be adding code that Vista may break so to make sure it does not you trad to detect which operating system it is?
Iv just notice Check kernel32 for Windows Vista, 7 and 8. i thought let's try custom extended kernel.
I find that using the kernel dll to check what OS is being uses is more reliable. Querying for the OS can (and is fooled) by compatibility modes. I am not using this data yet but I put it in there in case something I do needs to be disabled in older OS's
it works out of the box although SetSearchPathMode is disabled due to miner issues.
What do you mean by SetSearchPathMode is disabled? Keep in mind I am just using the presence of the exports as an identifier. I am not using any of those exported functions for anything.
are you making sone sort of leveling system, that windows 7 or vista is not as bugged, or is it the case that really soon you will be adding code that Vista may break so to make sure it does not you trad to detect which operating system it is?
I am just preparing for the case where something may need to be disabled in these older OSs. I have no plans to add things that will break in older OSs. In fact, I am trying to do everything in a way that will work with all OSs all the way back to Windows XP. However, I don't really have time to test these older OSs.
What do you mean by SetSearchPathMode is disabled? Keep in mind I am just using the presence of the exports as an identifier. I am not using any of those exported functions for anything.
you somewhat misunderstand these are not mods Jecob R is revise reverse engineering windows 7, kernel32.dll. user32.dll, ntdll.dll even others I do not remember. they are some that we can't reverse engineering like https://support.microsoft.com/en-us/topic/platform-update-for-windows-7-sp1-and-windows-server-2008-r2-sp1-d97da9ca-c15c-b21f-ebb0-838f7be8d9f6 Although H.264 Video Decoder and Windows Imaging Component (WIC) works. he does pan to add limited support for it. fun fact Jecob R 3 years back to try to backpoint windows 8 kerna32.dll down to windows 7 it was not passable due to how different it was. windows 11 with 8.1 yes. 8 with 7 big No.
as for SetSearchPathMode, it might cause issues if vista is not quite updated that is why it is disabled? unless requested by application but warns the user about it. as for presence of the exports, Jecob R does not trust anybody, or company's he is in example google chrome ended at version 49, however unofficially it was version 82 or 83 just by rerouting code.
they were no reason for google to drop vista so soon. Jecob R thought they were being Lazy or cut vista early.
In fact, I am trying to do everything in a way that will work with all OSs all the way back to Windows XP.
I do believe in what you say but for how long until that you have to make sacrifices with your code. or too difficult to be found workarounds. that is why Jecob R made the kernel, as technically vista is still supported until about 2026.
Are you saying the current DDrawCompat functions used by Dd7to9 work good on Windows 7? What about older OSs?
We had Jecob R look at it, what we had expected for mouths that time we did not knew about D3dDdi, 0.3.2 might be salvageable, even under extended kernel at best he might get 0.4.0 to work according to him it is on a completely new complier. even if he did get it to work it will never fully work with clean windows vista kernel, without some sort of rewrite.
that bags to question why is narzoul still advertising Vista Support, as for windows 7 they are nothing in DDrawCompat 0.5.4, for it not to work in 7 although has to be quite updated. which we confirmed may work in real handwear.
Sorry 1 question is it passable, to add support for d3drm.dll. we notice a lot of 90's games uses it. to my understanding it is direct3d for DirectX 3 only but quickly removed out of 5. although it is mostly use as in extension to Dirertdrew (rendering). but no wrappers really support it. also, vista+ also does not have it anymore.
Install dxsdk_sum2004 (Windows 10).exe https://drive.google.com/file/d/1zBh5lpXLYriOicKdlYWzRpAGyof_Ng0H/view?usp=drive_link was the last for windows me unofficially (not 98 se). even installable dxdrm.dll under windows 7 and below. not for 8+. that is still under investigation. although you can copy d3drm.dll from windows XP x86 or x64 works with 8+ users.
we trade using dxwrapperxp under windows 2000 it appears to work. but not well tested. so, I can't say it works with all games. as windows 2000 in our experience has bad direct3d support.
backpoint windows 8 kerna32.dll down to windows 7 it was not passable due to how different it was. windows 11 with 8.1 yes. 8 with 7 big No.
Yeah, there was some significant changes starting with Windows 8.
I do believe in what you say but for how long until that you have to make sacrifices with your code. or too difficult to be found workarounds. that is why Jecob R made the kernel, as technically vista is still supported until about 2026.
I am converting the games to Direct3D9, which is itself quite old. I don't foresee any reason I will need to break support for older OSs. If it does get broken it will likely be by mistake, since I am not really testing these older OSs.
that bags to question why is narzoul still advertising Vista Support
I guess you would have to ask him. But I suppose it is because he does not test with the old OS and doesn't know about the issue you ran into.
Sorry 1 question is it passable, to add support for d3drm.dll. we notice a lot of 90's games uses it.
Games should not (will not??) ever directly load d3drm.dll. Instead the games load ddraw.dll and then ddraw.dll will in turn load d3drm.dll. Bottom line here is that dxwrapper should already support some d3drm.dll games, via ddraw.dll. My goal is to support all of them. However, there are a lot of weird functions in these old APIs and the documentation is extremely sparse so it take a bit if trial and error to figure them all out.
we trade using dxwrapperxp under windows 2000 it appears to work. but not well tested. so, I can't say it works with all games. as windows 2000 in our experience has bad direct3d support.
That is interesting, and good to know. Thanks.
After more testing this is odd. I've did a reformat and reinstalled wondows 7. I did not use 12.4.5 instead the 1st release that is 12.0.5 and it worked? I can think if 2 possibles one the ddrawcompat developer want out of his way to fix it, unlikely due to this, Running Windows in any sort of virtualized/emulated environment, e.g. in a virtual machine or through Wine.
2 most likely it was by accident I've noticed looking at his github they were requests to fix intel i-gpus. And windows 7 exclusive bugs. This issue got my attention https://github.com/narzoul/DDrawCompat/issues/349. That is because I've noticed in the logs it was showing ddrawex.dll. which does not exist in the windows 8 logs. I'm thinking is vmware pro is doing something differently with direct3d that DDrawCompat just can't understand. Is that being the reason with the 7 issues.
I've notice this in actions tab a crash when the driver's WDDM version is higher than the OS su… …pports. I'm thinking they is Various reasons. as for Direct3D Rendering not working compared to 8+ who knows.
I Might have someone us one of these days github this developer to be honest if I do it tomorrow, he will just say this. Not supported means not supported. No exceptions. He did it 2 other times with other people from our group. Personally, I'm not going to fight this developer for anti-Virtualizations.
In fact, we might never do it. This group is not here to make enemies. Some are telling this comment is not a good idea. But my policy is to be honest even give inserts for my theory's iv what is going on. https://github.com/narzoul/DDrawCompat/issues/311
Original comment:
We will like to tell you that starting with https://github.com/narzoul/DDrawCompat/releases/tag/v0.5.4
it appers windows 7 is fully fixed with ddraw.dll DirectDraw (Software) renderer only. not direct3d or GDI randering. DDrawCompat-5THAD32.log DDrawCompat-Cyberchase.log
we will try to github him but in the past this developer told us, Not supported means not supported. No exceptions.. however, i hope when we have some more time, he will go out of his way to found out why is not fully working still.
as for windows vista he broke it sense 0.4.0 (almost at 0.3.2).
question elishacloud do you have a build for Windows 11 IoT Enterprise LTSC 26100, mean point do you have a more up to date build this is final, but it was linked early for enterprise users.
Girl Talk= it is mostly fix, if it was going to Couse problems it will be windows 10 (Test later) Windows 11= this game is now only Direct3d 2 please use stub for dxwapper on top of cnc-ddraw. https://drive.google.com/file/d/1ldv4bkaXfpn8u3ZyNJO2SmecjW9KZi17/view?usp=drive_link
this game is now only Direct3d 2 please use stub for dxwapper on top of cnc-ddraw.
Unfortunately, if you are going to use the dd7to9 feature then it likely won't work. Direct3D2 does some weird things and I have not gotten any Direct3D2 games working yet. DDrawCompat may work though.
do you have a build for Windows 11 IoT Enterprise LTSC 26100
No, but I should be able to get a copy of it. However, I won't have time to look into this for a little while. I have a lot of personal things going on right now.
we tried DDrawCompat it worked think you we will just tell the installers, install on windows 11 users only.
Windows 11 (Directplay) uses Direct3D only. so, Windows 10 build 19045 was the last for DirectDraw rendering.
Windows 11 still uses DirectDraw rendering. Many older games only use DirectDraw and do not use Direct3D at all. These games still work on Windows 11.
are you sure even today like 15 minutes ago that windows 11 IoT Enterprise to 24H2. is forcing girl talk to Direct3D although it is both, likely https://github.com/narzoul/DDrawCompat game works.
however, games like https://archive.org/details/STRATEGO now can't becorse of Forcing Direct3d which leads to a nasty bug something if i recall is to do with visual studio 6 if I remember.
clarification (Aug 9:29 AM) nevermind your saying the games are DirectDraw only will work, but still even if that was the case it is breaking alot of Direct3D 2 & 3 hybrid Games, so far 12 in the community. likely only 2 that DDrawCompat can't work.
are you sure even today like 15 minutes ago that windows 11 IoT Enterprise to 24H2.
I cannot speak for forcing girl. But the DirectDraw APIs are even uses for some modern applications. These applications still work on Windows 11. Certainly Windows 11 supports DirectDraw.
Yes, Windows 11 breaks a lot of old DirectDraw games. Older DirectDraw games have certain expectations for the APIs that may not be true anymore. These APIs don't always work exactly the same as they used to.
We will have to apologize about direct3d retained mode and direct3d Immediate mode comment.
Iv personally forget that DirectX 3 has 2 different direct3d mods. but in realty all 10 direct3d wrappers does a good job with Direct3D 5-7. 2 & 3 is a mix bug, I can't blame devs on this really because Microsoft In one time used open gl instead. as Direct3D as it was difficult to work with. same goes for d3drm.dll which has poor support even for DDrawCompat.
again, thicks for the clarification. we would also like to clarify uses were using windows 2000 with extended kernal. so, i can't say that dxwrapper supports windows 2000 natively. ill test later when i have more time.
It sounds like Windows 2000 has some issues with Direct3D9. Also, DDrawCompat will not work on Windows 2000. So Windows 2000 may be hard to support with dxwrapper since I am just converting the function calls from older versions of DirectX to Direct3D9
As far as kernel32 functions, of course you will need to test with the Windows XP build of dxwrapper. But if there are kernel32 exports that dxwrapper needs that are missing in Windows 2000 let me know. I can try and fix these.
to be honest here i don't think it is worth it, to port it at all as will require rewrite all of it to the grand up, that the extended kernel project supports despite being closed source. it just works with dxwrapperxp. you better off improving or optimizing, Windows 2000 class hardware, under windows vista & 7. Pentium 2 & 3 sse type hardware.
or https://learn.microsoft.com/en-us/previous-versions/bb432254(v=vs.85)
September 4 10:21 PM After more research we found a newer version NVIDIA 258.96 someone from the group did test it, and it worked fine with Direct3D9 under extended kernel due to dxwrapperxp, still I feel like people are better off running Windows XP instead.