satgan

Thanks a lot. I'm not conversant with Visual Studio and slowly picking it up with VS2017. I have been able to compile the dependencies in VS but got stuck while building the dosbox solution. Would you be kind enough to point out where can I find the following files: 1. debug_memory_leaks.cpp 2. warn_static.h Are these your project files or some sort of standard source/headers?

Hi, This is gandhig from Vogons forums. Thanks a lot for your work on savestates with dosbox. Can you please tell which environment you are using for building DOSBox + xBRZ 1.6 + Save_States? I'm unable to get it going either in MinGW or Visual Studio.

Thanks for the commit.

Thanks for the commit & your previous reply. P.S.:If needed, unrelated posts w.r.t SSE issue may please be deleted. I will post in this thread, only if I have something relevant to the subject issue after more testing. I will edit this post, later.

let me get back to you, when we have something more concrete in place. Sure. I'm presently experimenting, to get to install MinGW in PCEM Win95 guest for debugging an application. I know it is far-fetched. Do you have any advice regarding the version I could try, btw. Or is it a fool's errand? MinGW GUI setup actually doesn't run in Win95 guest, so, I'm trying the CLI route

let me get back to you, when we have something more concrete in place. Sure. I'm presently experimenting, to get to install MinGW in PCEM Win95 guest for debugging an application. I know it is far-fetched. Do you have any advice regarding the version I could try, btw. Or is it a fool's errand? MinGW GUI setup actually doesn't run in Win95 guest, so, I'm trying the CLI route

Thanks for giving inputs in maintaining an organized setup. Frankly I have never used git or mercurial before, so, as indicated, I will start with mercurial and mimic your setup. Would you be interested in joining the project, in the capacity of "tester", with a particular emphasis on legacy systems support? It took me around 10 days to understand, identify and search a fix for the stack alignment issue under wine. So you can guess my knowledge level. I'm also doing testing for DosFreak's compilation...

FWIW, this is how I generated cpu_features.original.patch....Simple as that; I was probably sounding more naive than necessary on my earlier reply. I should have worded it as "I never felt qualified enough to propose it as a proper patch". What I meant by 'lacked the knowhow' was not w.r.t 'generating diff or applying a patch(which,thankfully, I do know)', rather, it was about the possible (ill?)effects of the 'added' code on other systems (that weren't tested by me). That said, your reply about...