Svyatpro

you can use fix128 to remove XP limit up to 128GB.

If you have created the topic just give a link, we will support it.

It could be very useful if you would post a petition or just open a thread at least at GeForce forums about Vukan support for XP. I think you should do this only for NVIDIA because AMD and Intel abandoned XP users long time ago and IMO their drivers quality is a crap.

I don't know whether it should be GeForce forums or NVIDIA Developer forums.

How naive, this is futile because WDDM driver should be backported. XPDM driver cannot recognize sm4/sm5 opcodes for direct3d . But even if he will really backport WDDM driver (I am very doubt of it) he will at least lose GDI/GDIPLUS HW accel on which XP's interface relies. The best solution to implement DX10/11 for XP is DX to OGL wrapper at this moment. WineD3D is the most suitable for now. And it doesn't concern me much, because it will certainly be implemented soon, this is just a question of time. Vulkan support for XP mostly concerns me, I hoped that NVIDIA would implement Vulkan support in their new drivers, but they didn't. WE NEED TO "ATTACK" NVIDIA TO MAKE THEM BRING VULKAN SUPPORT FOR XP AS THEY PROMISED! : P

All I can say, Dibya is a fraudster. 1) kernel32.dll and other dlls were stolen from BlackWingCat's WindowsXP-KB2584577-v0.4-x86-ENU.exe Here is MD5 of BlackWingCat's kernel32.dll extended for XP: DFB76D26C9F67EF92571D9F4D5A9A60A And here is MD5 of kernel32.dll from DibyaDX11-x86-ENU-v1.exe package: DFB76D26C9F67EF92571D9F4D5A9A60A They are equal. MD5 completely matches, functions list is the same. And all we perfectly know that BlackWingCat is an assembler guru, read his blog. 2) He said he took original d3d10.dll from Vista Beta 2, but in fact there is d3d10.dll 7.0.6002.23771 inside his package which is Vista SP2 LDR. I managed to successfuly use Vista's native d3d10.dll with my WineD3D build by writing a stub function for d3d10core.dll that native d3d10 required. Of course I wanted to use latest compatible native version of d3d10.dll which was taken from Vista LDR update (this trick should be added to Winetricks). And after all I kindly presented my WineD3D build to BlackWingCat for his Win2K KernelEx because I am excited of his incredible work. See this post And now I communicate with BlackWingCat personally and we are both interested in bringing DX10/11 to Windows 2000/XP/2003/ReactOS. So this project is WIP and mostly depends of official WineD3D developement and it is too early to advertise it because it is still unreliable, just for simple applications. 3) He said he took wined3d from adolfintel But unfortunately guys, adolfintel's wined3d build is somewhat wrong, perhaps he incorrectly applied Wine Staging patches so his build cannot run any Direct3D 10/11 application at all. And starting from WineD3D 1.9.8 the GetDC() function was switched to D3DKMT dependency that is unavailable on NT5.x. So there is no point of using adolfintel's wined3d build for XP. Maybe I will personally contact adolfintel and give him an advice how to correctly apply Staging patches. BTW, those posts about ReactOS files in adolfintel's website are mine, I also took part in ReactOS hardware testing so I am very closely associated with ReactOS team, and if you know ReactOS's Win32 API is based on Wine so I offered in adolfintel's blog to use ReactOS wined3d files as fully Windows XP compatible. And we need to remember: WineD3D is a property of WineHQ and Crossover and it is open source, so I don't claim anywhere that I ported anything, unlike Dibya claims. Dibya had to be a good guy, I like his sign "Fighting against death of Windows XP" but he shouldn't assign foreign labor to himself and try to justify his false.

Yes, but it was on other unofficial WineD3D branch (PigFlyGames) that contained more D3D10, but almost nothing of D3D11. I expect to get a little better of DX10 and 11 in the end of week.

I have almost the same results as you, here is basiccompute11 log: And have the same DirectX10 Tutorials behavior, because Wine is not complete and this is a Wine's bug. But it develops fast from recent time, and almost everyday Wine get commits for DirectX10-11. I will release updated WineD3D for Windows at the end of week that will include some more DX10-11 patches and commits.

Here is updated version of WineD3D 1.9.6 for Windows including my customizations. It includes initial support of Direct3D 10/11, Direct2D, Direct3D 9Ex and DirectWrite (requires several Vista+ functions). Yes, it is not complete and doesn't allow to run most of D3D10/11 apps, but really allows to run simple D3D10/11 apps and you can check and maybe find more working apps. Direct2D and DirectWrite are not working completely but it needs more testing though. Also DirectWrite is incompatible with WinXP/2003 because of functions lack. GDI32.DLL: GetFontFileInfo GetFontRealizationInfo KERNEL32.DLL: GetLocaleInfoEx IsValidLocaleName LCIDToLocaleName Divekick D3D11 game running on Windows Server 2003 SP2: You can download updated binaries and test on Win2000/XP/2003: http://rghost.ru/78WF5FMnt And as always BIG thanks to WineHQ and Crossover!

Is it feasible to add following functions to BWC's KernelEx? iphlpapi.dll: ConvertInterfaceLuidToGuid kernel32.dll: AcquireSRWLockExclusive AcquireSRWLockShared InitializeSRWLock ReleaseSRWLockExclusive ReleaseSRWLockShared It is needed for Pro Evolution Soccer 2015 to run. These functions are missing on Win2003, so I suppose they should be missing on W2K too.

It works on XP SP3 NT5.1 as well as on Win2003. Tested on Acer Aspire TravelMate 5520G with HD2400XT onboard. I just had to install your Vista's msvcrt.dll update, also MSVCR90 and DirectX redist files may be required. Here is a little bit more updated version: http://rghost.net/6LHwrNxM9 Changes: -Added SM4 UGE opcode recognition from Wine upstream I noticed one interesting thing, when you copy these D3D libs to System32 folder, Crysis 2007 runs with a "-dx10" switch but the screen is black and sound is playing. If you are experienced in C programming you can wisely merge Wine-Staging-patched repository with PigFlyGames repository. I tried to do it myself, but not all the patches can be merged correctly. Wine-Staging-patched repo: https://github.com/wine-compholio/wine-patched PigFlyGames repo: https://github.com/PigFlyGames/wine/tree/crysis

I enhanced this WineD3D branch somewhat, here is the download link: http://rghost.net/8gYX4dzq5 Changes: - Some implementations from Wine upstream - Updated d3d10.dll according to KB3015171 BlackWingCat, I haven't tested it on Windows XP yet, cuz I need XP with support of msvcrt.dll from Vista, I don't have such a computer on hand. But it works on Win2003 without problems. I compile these binaries with "-march=presscott" flag, maybe your problems are because of lack of SSE3 support.

But if you manually register MSXML6.DLL from older Windows versions, for example MSXML6.DLL 6.20.2503.0, and then copy and paste newer MSXML6.DLL 6.30.7601.22640 to System32 folder, it will work. Its operation can be tested in Microsoft Office 2010 ------------------------------------------------------------------------------------------------------------------------------------- I dunno if it will be useful and worthy for you, but I know some interesting facts that I discovered by own experience about several Microsoft updates: 1. KB955536 for Win2003 x64 has newer (w)msvcrt.dll 7.0.3790.4400, than x86 one msvcrt.dll 7.0.3790.4341 that you are using in your pack. 2. GDIPLUS.DLL starting from 5.2.6000 (vista's branch) has notably worse performance in 2D benchmark of "Passmark Performance Test 8.0 Suite". Older gdiplus.dll 5.2.3790 shows better results in 2D benchmarking. The results may vary depending on different hardware configurations, but the fact is that older gdiplus.dll always shows performance benefits. Here is gdiplus.dll 5.2.3790.4377 and msvcrt.dll 5.2.3790.4400: http://rghost.net/8xKjsRjSr

I noticed an interesting bug, maybe OS specific; if you try to register the msxml6.dll from Win7 that you have bundled with your extended kernel, it doesn't add any information to the registry, hence the registration fails without any error messages. Tested on Win2k3

That should work, I downloded from your link and it works for me, maybe this is because of graphics vendor and drivers, I use Nvidia Try using d3d10.dll from Vista RTM, because mine is SP2 LDR branch. Try using Wine's d3d10.dll, but some samples will not work. NOTE: I am using Win2003, I haven't tested it on Win2000 yet.

That's not the same, its D3D10 doesn't work at all. PigFlyGame's WineD3D branch made it possible to run some D3D10 applications. In PigFlyGames's D3D10 is used native d3d10.dll from Vista + lots of patches that fixes problems that appears in regular Wine branch. Also WineD3D's for Windows DirectX 9 doesn't have CSMT patches. Try to run Mortal Kombat Komplete Edition using regular WineD3D branch, you won't get any success, but using WineD3D9 with CSMT patches, it will work with one workaround.

DX10 dlls that is in a BlackWingCat's extended kernel pack may never work, because of lack of WDDM architecture, but there is an alternative solution: There is a blog "PigFlyGames" where resides patched version of WineD3D10, you can check it and compile the binaries for Windows and you will be able to run some DirectX 10 samples under Win2000/XP/2003. Here is this blog: http://pigflygames.com/index.php/blogGitHub repo: https://github.com/PigFlyGames/wine/tree/crysis/ And if you don't want to compile it yourself, you can check out already compiled version along with samples:http://rghost.net/6CVTqrR4H (Also includes completely unfinished DirectWrite, Direct2D and DirectX 11 libriaries) NOTE: This project is not completed, outdated, and supposed to be freezed. In order to run these samples you need to have hardware and driver level OpenGL 3.x support, also Vista's msvcrt.dll is required. WineD3D is not a native D3D implementation, it is an OpenGL wrapper, that translates D3D calls into OGL ones, this may affect performance. -------------------------------------------------------------------- I also have a temporal solution to add OGL wrapped D3D9Ex function into native d3d9.dll, this allows to run several D3D9Ex applications like Mortal Kombat Komplete Edition, but it also has some regressive aspects.Here you can check my d3d9.dll from Windows Server 2003 SP2 with D3D9Ex support: http://rghost.net/69m446YGB The Direct3DCreate9Ex function in native dll is forwarded to d3d9ex.dll which is compilled from Wine 1.7.42 with Wine-Staging patches and with CSMT support.

msxml6.dll and msxml3.dll from Windows 7 cannot be registred as well, because it requires correct "API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL" to add registry information. So, when you slipstream msxml3 or msxml6 from Win7 to Win2000/XP/2003 distribution - you will get not working msxml! You should remove msxmls's from Win7, and use from XP/2003/Vista ones, then.

msxml6.dll and msxml3.dll from Windows 7 cannot be registred as well, because it requires "API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL" to add registry information. So, when you slipstream msxml3 or msxml6 from Win7 to Win2000/XP/2003 distribution - you will get a nonworking msxml!

Sorry, but I suppose that it could be a lot better to integrate updated .NET 1.1 together with .NET 2.0, 3.0, 3.5.

Thank you for advice, but I want to replace outdated .net 1.1 from original W2K3 image.

I want to build compact .NET Framework 1.1 for Windows Server 2003, because I've deleted it from my distribution. But your .net compressing utility don't want put .NET 1.1 for Win2003.