CompuServe Messages

ok,ok I'm sorry to say the system is speeds down. What I mean is: all PharLapDosExtender program's like 3DS, AniPro or AutoCAD first uses EMS memory and then XMS memory. When I say, the system speed's down is this my subjective opinion. I had not run benchmarktests. I only observe my system. Some examples for a system with 16 MB RAM: 1) – 16 MB XMS allocated with HIMEM.SYS – 8 MB of XMS allocadted as EMS, using EMM386.EXE Now when starting 3DS, 3DS can only!! use 8 MB of EMS memory. When useing -NORAM by EMM386 in order to have 16 MB XMS and no EMS for UMB's, the computer runs in virtual'86 mode so 3DS can't start. Useing EMS is bad, because the systemperformance speed's down, for example there is a high initialisation time for 3DS. At my opinion this is the worst way to manage your memory. 2) – 16 MB allocated with QEMM386.SYS QEMM allocates EMS memory and if an application want's to use XMS, QEMM simulates XMS from EMS (readme.doc of qemm). This way is much faster then using EMM386, and you can loadhigh your TSR's in order th have a lot of free DOS memory, but 3DS first checks EMS and then XMS, so 3DS uses EMS and no XMS. I mean QEMM's EMS is a little slower as HIMEM's XMS. I think QEMM is the best way, when it's nescesaary to highload TSR's and running diffrent programs that need XMS and EMS. 3) – 16 MB allocated with HIMEM.SYS Only one memory type is used: fast XMS. If there are no EMS program's and no reason to loadhigh TSR's, I prefer this way, because I have 32 MB RAM, so I can configure all Autodesk products with CONF386.EXE (or easier CONFPHAR.EXE from AutoCAD). All in all, QEMM386.SYS or HIMEM.SYS are very efficient, EMM386.EXE is a deadlock manager. -Ingo