(Reworking our code & FunkyFr3sh), Direct3d may be stable for Server Vista & community project #283
Comments
MicahMoo11
changed the title
|
Aug 23 original We found with our limited testing that dxwapper is having issues with server 2008 with A lot of games, and others he is the logs with xp compatibly mode. with the XP build again, this game works outside of the box with vista. I and others, think you should know. |
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.
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 Let me try to dynamically load this function to avoid this type of issue. |
|
Ok, try this one. This should fix the issue with |
|
Yes that fully work with server 2008 but it gives another windows 7 error but it does open the game, update aug 23 3:48 pm https://github.com/abbodi1406/vcredist/releases/tag/v0.61.0 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 it does show this error below, but the game does open. |
|
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: Also, I noticed a lot of this log event: I am not completely sure that my implementation of |
|
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. 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. |
That is not coming from dxwrapper. Dxwrapper neither uses nor loads that dll.
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 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. |
|
問題の署名: オンラインのプライバシーに関する声明をお読みください: オンラインのプライバシーに関する声明が利用できない場合は、プライバシーに関する声明をオフラインでお読みください: cnc-ddraw-1.log 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. |
|
question does this build with .logs might help you Windows (TM) Vista Enterprise 64-bit (10.0.6004) the reason why it sues 6004, as this is a special build of windows vista that acts and behaviors like windows 7 We also did some even other user32.dll improvements. for better support for direct3d wrappers outside of dxwrapper. |
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.
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?
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 |
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: 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. 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 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
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.
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. |
you somewhat misunderstand these are not mods Jecob R is revise reverse engineering windows 7, 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.
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. |
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 we trade using dxwrapperxp under windows 2000 it appears to work. but not well tested. |
Yeah, there was some significant changes starting with Windows 8.
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.
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.
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.
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 narzoul/DDrawCompat#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… 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. 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. narzoul/DDrawCompat#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. we will try to github him but in the past this developer told us, Not supported means not supported. No exceptions.. as for windows vista he broke it sense 0.4.0 (almost at 0.3.2). |
|
https://github.com/narzoul/DDrawCompat/releases/tag/v0.5.4 this is in extension to other comment We tried windows 7 RTM with no updates, the very last VMware tools are 10.2.5. windows vista is still quite broken, however with the extended kernel as it is starting once more to work. neatherless this developer might not like us with the anti-Virtualizations nonsense, but we tried all kinds of wrappers, and emulators, they might have issues even dxdwreapper with virtualization at times have issues, however (not importtant now i'm going to bad i am surprise, |
|
question elishacloud do you have a build for Windows 11 IoT Enterprise LTSC 26100, Girl Talk= it is mostly fix, if it was going to Couse problems it will be windows 10 (Test later) |
Unfortunately, if you are going to use the
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. 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) |
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. |
|
do you know that windows 11 still supports Windows nt 4, i know that windows 10 did but it is getting tougher to activate it, it is also showing deterioration, but not as bad compared to DirectDraw. we are asking because FunkyFr3sh did fix it 2 days ago, We expect if nt 4 is applied it will fix it temp. untel FunkyFr3sh fixes once more or again. assuming it can still be done unless we have another, STRATEGO issue again https://archive.org/details/paddle_202301 |
|
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. |
|
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. |
|
Madeline math 1st & 2nd grade really needs windows nt 4 without it. it will panic, iv notice add check to GetVersion functions by FunkyFr3sh (it did work only one time by accident it is going at a right direction). will do plan later in the week to contact DDrawCompat about Vista support. assuming he is not trying to fix it. we notice your code is still based on DDrawCompat v0.3.2. it appears that v0.5.4 appears mostly fixed with our limited testing's, with intel hd graphics 3000 & hypervisor thru DirectDraw (Software) renderer only. |
|
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 |
|
We tested your new release v1.2.7200.25 support for Direct3d 2 & 3 even d3drm.dll are not great. although I can say was greatly improved. some are beginning to work. Some workarounds we use ddrawcompat 0.3.2. on windows 7+ We have not done the xp build, as we are too busy to test pre vista systems. We will when we look at more direct3d 2. direct3d 2 barble was tested and fully worked we did not give logs as since windows 2000 it does not properly work due to engine issues. that it wants something from windows 9x was long been gone, due to this it will randomly close at times. |
Yeah, Direct3D v2 is not yet working with dxwrapper. I have implemented many of the functions but it seems there are texturing and other issues I need to troubleshoot. I only have a handful of Direct3D v3 games. The main one I test with in S.W.A.T. 3. The ones I have tested work perfectly with the latest release. But I have not implemented all of the Direct3D v3 functions yet. I will need to investigate other games that don't work.
I tried to look up that EncodePointer and I cannot see anywhere that I use it. I suspect it is being used by the VS runtime, which I built into the dll. If that is the case I am not sure how that can be solved. Maybe the only way to solve that would be to stop using any of the runtime functions, which would take a fair amount of rework for the whole module. So I think for now, at least until I learn more, Windows 2000 will be off the table. Sorry about that. |
|
you misunderstood we were talking about Barbie as Sleeping Beauty, which is direct3d 2 fully works, however they are a nasty bug in the engine, that starting from windows 2000 it randomly closes at times. that is why I did not include any logs. as a patch is needed but 2 decides has passed. it will never happen sadly, we are testing what's more stable cnc-ddraw or dxwrapper, for the closes and other abnormally. |
|
question due you plan to add newer ddrawcompat in your code as 0.5.4, appers to work in 7 but direct3d does really weird things big time direct3d 5, 6, 7. 2 and 3 appear fine we are useing TEMP if we have no other choice. except d3drm games. as windows vista extended kernel fully supports 0.3.2 (clean may work in vista) and 0.5.4 only 0.4.0 - 0.5.3 will never happen due to so many 8 functions. and incompatible D3dDdi functions. what plan is ddrawcompat going Forword. |
|
I am not planning on updating DDrawCompat. I may pull some features over from DDrawCompat, specifically, I want to pull the |
|
did you add limited support for d3d9 A & B, in the windows xp code, as no virtualizations at less we know of in windows 2000 some do have ddraw rendering & direct3d7, support they are workarounds, but they only include, d3d9 C only, so we can't test A or B. as users confirmed yes, however some AMD and NVidia cards. did had d3d9c support but had serious issues on complaints with Microsoft 9.0c specification and was cut short by Microsoft. did you add A & B, support or was it Microsoft 9.0c specification, and it worked in the windows 2000 class handwear. |
|
Currently, the only wrapper I have for Direct3D8 is The Windows XP release has all the features of the normal release excluding DDrawCompat. Direct3D9c is the best one to use. I am not sure how well |
|
sep 23 12:33 pm this was reedited for clarification as it was all over the map, and a lot of misspellings. From our community with extended kernel, it does work. D3d8to9 does not give windowed mode. Which our community wants. But can't as the hardware isn't supported, or not officially by Microsoft certification. All we are asking is better support. Hardware from early 1999 does not translate well with windows 7 but can be done unofficially. Windows 7 is the last known by some processors. Microsoft visual studio 2008 is the last for windows 2000 targeting. Due to VS runtime witch FunkyFr3sh bypass by has code. This developer added limited windows ME support. We have Pentium processor 2 & 3. Which is unfortunately not supported by Microsoft sense Windows 8+ Microsoft made sure of it by requiring sse2. Windows xp hardware like Pentium 4. Works today with windows 11. 2 & 3 that is stick with 7. FunkyFr3sh is DirectDraw rendering only that is why called manage it. We want him to do direct 3d. We understand why he can't. All we are asking is at less add basic support for windows 2000 hardware who has no other option than windows 7. |
|
When you talk about windowed mode, I assume you are not talking about in-game windowed mode. dxwrapper's dd7to9 and d3d8to9 both support in-game windowed mode. dxwrapper also already has a windowed mode feature that works with d3d8to9 and dd7to9. As far as Windows 2000 support, I will look into this. I don't have Windows 2000 setup yet so I will work on that. |
|
We are closing this as we are now testing windows NT 4 with cnc-ddraw with high success with directx 5 & 6 games, 95% We even had limited success with direct x 7 with NT 4, although dinput.dll has serious issues it is a mixed bug. We will still update this post, here and they but leaving it open, just makes no since, as we are basing our code within cnc-ddraw. with fallback mostly DXwrapper with windows 2000. rarely DDrawCompat for 8+ users only due to odd issues. |
|
Nov 6 12:47 AM just tested windows 2000 under XP build it still works under extended kernel. I'v just try the new release Windows vista is starting to break oddly DDrawCompat still barely works although extended kernel strongly advised. it does work with TLC however it is under force fullback, meaning redirecting comparability code. i will be testing windows 7 with intel hd graphics 520 and 4000 for windows Vista tomorrow. oddly it makes no debug logs, allthough the windows XP build works. not a big duel i guess, unless want DDrawCompat. |
|
It looks like that is coming from the Visual Studio Runtime. I have no idea which runtime call I am doing that would call that code. However, removing all runtime code from dxwrapper would be a lot of work and I have no plans to do it. If the Windows XP version works that should be the one to use for all pre-Windows 7 cases. |
|
that is fine we do have a windows vista extended kernel. and it works without issue, however it still does not changed the fact that direct3d developers are gearing for windows 10 users. again windows vista & 7 are old by today's standards. if vista breaks 7 is next, in fact some of our users with windows 7 has stopped working. due to they get update past, 2018 due to no sse2 processors support, likely cnc-ddraw still works. unless direct3d which is getting scary for wrappers. they is demand for DDrawCompat. that is why we are using windows 7 builds. but the extended kernel can go so far. DDrawCompat is is a fight with Vista extended kernel. yes 0.5.4 has restored some vista code. but it is very likely the next release will break it again. so the community is now forking 0.5.4. to make sure narzoul don't break it going foreword. |
|
one more thing i forget to say windows 7 extended kernel does not exist. and the overall community has no intrust. as windows vista plays more nice with older hardware. the only thing I care really are TLC and 90's educational games. it is true that i am now targeting windows 95. but it was by accident really due to FunkyFr3sh adding windows ME support. near i understand why or how cnc-ddraw community managed limited direct3d 2 & 3. when mean developer clams otherwise. again i wont ask as majority of games are directdraw (software rendering) except a few exceptions which i use dxwrapper for 8+ users. as for Vista & 7 i use wine D3D. due to better compatibility with old hardware. |
|
this TLC Fully works intact for some odd reason Under Windows Vista. yes it still works for some games. now i'm thinking are they direct3d 2 games, or dxwrapper is doing something vista does not like. old comment: i finally got the debugger logs to work, by downgrading the 2022 runtime. again all TLC works by going to super dubug or dxwrapper reroute. the logs are for the public that has no idea about extended kernel or jecob R custom TLC engine. |
|
Update 2 nov 7 12:02 Am: updates kb976902, kb976932, kb3138612, kb4474419, kb4490623, kb299226, fully restores DDrawcompat under windows 7 even Vista that our extended kernel is based on. however dxwrapper still does not work. although TLC Works under fallback, it looks miner based on logs If 7 gets more up to date it should solve it self. Update Nov 6 10:52 pm, if narzoul tested DDrawcompat under virtualized/emulated environment. It never would've broke old windows like Vista & 7 barely escaped until 0.4.0 as it did allthough 0.5.4 was restored I expect by accident . your new release is almost thru. again I'm not a programmer. it is going at a right direction. at the end of the day this is your project. windows 7 RTM with DDrawCompat is very close for working they is extreme performance issues or some games due to kernel conflect. dxwrapper has failed same as vista. not under DDrawCompat same as Vista more or less updated. this logs are windows 7 RTM only (not sp1 due to some hardware can't do it or can with performance issues). I'm thinking this is be accident or you are testing windows 7 trying to restore functionality. |
True. I am working on the better support for older Direct3D games. I do all my development and testing on Windows 10 because that is all I have time for right now.
I just checked and the Win XP version of dxwrapper should work on processors without SSE2 support.
I am using the DDrawCompat 3.2 code. Dxwrapper's DDrawCompat should work the same as DDrawCompat 3.2.
Most games of that era added a fallback to DirectDraw if Direct3D 2 or 3 was not available. It sounds like they are just forcing the game to failover. I am doing the same for Direct3D 1 in dxwrapper, at least until I can add support for Direct3D 1.
I did add better support for Direct3D 2 games in the latest release.
That is good news.
Which feature of dxwrapper are you using that is not working here? I presume if you need DDrawCompat it would be better to use narzoul's version rather than dxwrapper's. |
|
kb976902, kb976932, kb4490628, kb2670838 (Vista does not call this under investigation and incompatible with extended kernel, explains 7 RTM unstable this game needs HandleExceptions (does not work with windows 2000 extended kernel) although working with FunkyFr3sh code under investigation & needs kb4474419. I'm expecting no sha 1 support. same as above but worse, im now going to windows update. to mach time testing 1 update at a time. this even does not work under, ddrawcompact or dxweapper is yikes, but it is known to be bugged. even under FunkyFr3sh at 1st. this not sure. really does not mettle as cnc-ddraw works without new HandleExceptions. |
MicahMoo11
changed the title
Question how did you fully restore ddrawcompat back to Windows 7 even RTM? (selectively unstable) (0.3.0 - 0.3.2) back to virtualized/emulated environment, Looking at actions was unclear was this accident. My guess you added 0.5.4 code. Sorry your right as long as ddrawcompat works or windowed mode, Is the only thing I care about really. |
|
i just tirade the true narzoul's version 0.3.2 it failed with 7, although works with vista extended kernal. i hope you know what your doing windows 7 extanded kernal does not exist unlike vista, even if you or most likely narzoul kill it vista has a community that will recover support. this can;t be said for windows 7. ill keep v1.2.7300.25. narzoul's version |
|
this is my last update on this subject. Microsoft visual studio 2022 was comparable, with windows 7-8 sense 17.6 despite not documented by Microsoft. although the community is using and planning for LTS 17.12. but Microsoft is quickly killing windows 7 support from the kernel level already. so most likely 17.10 LTS will be the last for the group. In fact i am using 17.8.15 made last mouth. (unofficially) under vmware only targeting and making sure the extended kernel plays nice with Vista. as the community is using windows web server 2008 as a base. which may not not work with Vista. due to quite a difference or updates not fully installing from the code base and finding workarounds with Vistas limitations vs windows 7, that 2008 R2 fully supports today i beleave about 2026. although this might change as windows 7 POS was dropped last mouth, as server 2008 r2 is the last 7 verint even dropped or no windows 7 x86 because of this. the point is since 17.9 the community has notice that they is server degrade in the Vista runtime support. that is another factor was or why 17.10 will most likely be the last based on restoring code from the runtime level targeting vista. it is very unlikely windows 7 will be effected same as windows XP that way seen at this point. |
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.
The text was updated successfully, but these errors were encountered: