Yeah, that is true - on an 8mb card that's a lot of DIP chips...

Orchid RamQuest 8/16 supports up to 32 MB, and can be used in an XT.
But it's hard to find...

The only easily available EMS card seems to be the Lo-tech EMS 2MB.

Impressive! One of them or four Everex and the complete 32MB capacity of LIM4 EMS is being utilized! grinning face with big eyes

Yeah.. The Lo-Techs seem to be the only ones here, as well as Pico based universal boards.
Both seem to be LTEMM based, so we have a mixture of LIM4 EMS Manager and EMS 3.2 boards (LIM4/EEMS had more optional features, like backfilling or a larger-than 64KB page frame).

PS: Central Point's PC-Tools 7 had some Norton Commander style file manager, too, I think.

Jo22 wrote on Today, 03:41:

PS: Central Point's PC-Tools 7 had some Norton Commander style file manager, too, I think.

It has PCShell, but it's *NOT* NC-style.

More like DOS Shell, or Windows File Manager:

Unacceptable for me.

for quick stuff I always use LIST by the late V. Buerg
ofcourse it is not a 2-panel file manager but for quick viewing/copying/deleting/extracting I cannot think anything better
on slower machines I use DOS NAVIGATOR and on faster one Necromancer's DOS NAVIGATOR

Some things to consider...

Some machines don't like norton-commander or volkov-commader, some software has also issues when started with either of both.
It could be related to mouse-support to, so with a wrong mousedriver you can also get into trouble.

very early versions of NC rely on dos-executables (NC 3 and before). I also like VC because it never relied on dos-executables, but it has a bigger memory footprint and that has also to be considered for games/software that requires a lot of free dos-memory (<640KB). On my MCA IBM PS/2 Model 56 486SLC2 I use the beta of vc that makes use of XMS and has a small footprint on dos-memory-consumption.

I always favorize the two file-windows, things like PC-Shell or Dosshell are not very handy for filemanagement if you want to copy/move stuff around.

There are situations when it's better to avoid commanders...

Commanders occupy some memory even when running a command - if a program refuses to run because of not enough memory, just quit the commander and try again.

I also avoid loading TSRs from a commander - it's a good idea to load all the necessary TSRs first, and *then* run the commander.

The general idea of Norton Commander, however, is BRILLIANT!

There's so many operations with TWO arguments - source and destination...
copy, move, compare, convert, create archive, extract archive...
It's so natural to have TWO panels for such operations!

And at the same time - the CLI is always at hand!