The thing about EMM386 is that it tries to use whatever memory regions you specify for upper memory. If you try to use a region that is used for something else (like a piece of hardware or a video mode), there will be a conflict, and likely a crash. The regions available for use are likely to differ greatly depending on the system and on the applications you try to run.

For starts, I would remove most of the switches you have in your EMM386 line, and stay with something simple. For example, RAM I=B400-B7FF I=CA00-CBFF AUTO has been working well enough for me, with sufficient amount of available memory, and few conflicts.

Aladdin may not work if there is too much EMS memory. Try giving it only 8MB of EMS memory.

And there is no single configuration that could work with everything you throw at it, so back in the DOS era people usually had boot menus to select if they want XMS, EMS, CDROM or whatever configurations. This can workaround programs that fail if there is too much memory so they cannot understand it, or to specifically omit EMM drivers for games and demos that just use the memory in protected mode or flat real mode themselves.

Well, I also think that your EMM386 setup is overkill and too complex, and has side effects I would not want.

For instance, are you absolutely sure your video BIOS is 32k, from C000 to C7FF, so C800 onwards is free? Some video BIOSes are bigger, and some motherboards with integrated ethernet adapter might have its boot ROM located at C800 onwards. The M3 parameter forces the page frame to start from C800.

Including the monochrome video area B000-B7FF will remove all support for those modes and cause the machine to hang if a program tries to use it. I don't know how video adapters react to that, I always leave B000-AFFF area for the video.

And about the overkill part:

A=64 creates 64 alternate EMM register sets, while default is 7 or so. What could possibly use so many alternate registers? Sure, in some multitasking environments it is beneficial for each task to have their own set of registers maybe, but for DOS gaming, no. Even so, that would consume 10k-12k extra memory as well.

H=128 creates 128 handles for handling EMM memory. That's double the default. Again what could possibly need that?

D=256 means largest DMA transfer will be 256 kilobytes. Even 16-bit ISA DMA channels can transfer only 128 kilobytes, and for the most part sound related DMA is usually up to 64 kilobytes. I suppose the default 16k can be a bit too low for some applicatios.

I'd just leave the EMM386 with RAM parameter.

thanks , Ive done some tidying up in regards to EMM386 , as well as replaced MSCDEX with SHSUCDX, which helped bring the conventional memory to a more acceptable 592k as opposed to 550 before, and Aladdin works too.

not perfect, but does seem to work well enough for the games I tried. Of course one can't expect every game to work , but as long as most games work decently , Im ok with it.

I would setup a boot menu in CONFIG.SYS (the [MENU] section) with DOS (noems), DOS (ems) and WINDOWS items.
This gives you three config.sys/autoexec.bat separate sections for tweaking.
No need for "one size fits all".