This patch adds KMX C 02 machine using 386sx CPU and Chips&Technologies 82C836(SCATsx) chipset that is successor of 82C235. Experimental 82C836 chipset emulation is also implemented in this patch and two more machines that uses 82C235 chipset is also included in this patch that is submitted but not applied in recent revision.
If you need BIOS ROM image file for testing, please send your e-mail address as PM for me.

It would be interesting to have a 386-SX with SCAT EMS support to compare the performance and features offered by these chipsets vs. EMM386/QEMM/386MAX. If i recall correctly, the EMM emulation provided by these utilities uses the 32 bit capabilities provided by 386 CPU, but since the SX variants had 16 bit bus,It took two clock cicles to execute one 32 bits instruction.

So for these systems, the EMS memory provided by the chipset was faster than the emulated.
The only drawback was some 386 games required VCPI fuctions avaiable only when the CPU is V86 mode with some EMS emulation software.

Sorry if it is a bit off topic. But is possible to add EMS support to NEAT machines?. The emulated AMI BIOS 286 and DTK-386 SX clone, both, have a NEAT chipset.
I know they uses a different EMS driver, but i don't how different are NEAT and SCAT chipset for instance.

Sorry if it is a bit off topic. But is possible to add EMS support to NEAT machines?. The emulated AMI BIOS 286 and DTK-386 SX clone, both, have a NEAT chipset.
I know they uses a different EMS driver, but i don't how different are NEAT and SCAT chipset for instance.

¡Thanks!

According to technical document, implementing EMS support to NEAT machines is somewhat easier than SCAT machines but I don't have machine that uses NEAT chipset so I can't confirm its behavior. Only highly experimental implementation is possible at this time like EMS implementation of Laser XT series did.

And behavior and approach of the NEAT chipset and the SCAT chipset are completely different.

First of all i want say i'm grateful to the effort you have done when yo added the support to theese SCAT chipsets.
It's interesting to test this emulated hardware because nowadays te real SCAT/NEAT/LEAP chipset are very rare.

And well, i'd like to ask about some emulated chipsets. I do not know if its a bios problem, a problem with the configuration or the way my SVN PCEM was compiled

* The GW-286CT GEAR works flawessly. And even count the XMS memory only once.
* The Award 286 work great too, but it has a minor glitch,it checks the XMS memory five times. Ohter than that has no problems.
* The Samsung SPC-4200P and 4216P both of the them have a problem when testing the XMS memory after configuring the EMS memory in the BIOS, they detect the remaining XMS wrong or directly as 0kb of XMS avaiable.
(also the 4200p only support 2MB of RAM and 4216p supports up to 5MB. 5MB is enought for any 286 systems however.)

* The KMX-C-02 works and load the EMM.SYS driver and even detects correctly as a SACTsx chipset, and the 128kb UMB memory is correctly detected by QRAM
But it does not support the Large Page Frame (No mapeable area found) and Word for Windows 1.1 (Which i installed in Win 2.11) looks up after i run Winword.exe.

PD: I used the same hard disk with the SCAT EMS driver and QRAM with all the SCAT machines. i do not know what the "Coprossesor READY cntrl by" do the possible values are 387SX and 82C836 (the SCAT chipset)

Fenix77 wrote:
* The Samsung SPC-4200P and 4216P both of the them have a problem when testing the XMS memory after configuring the EMS memory in the BIOS, they detect the remaining XMS wrong or directly as 0kb of XMS avaiable.
(also the 4200p only support 2MB of RAM and 4216p supports up to 5MB. 5MB is enought for any 286 systems however.)

4MB RAM configuration is not properly supported by SPC-4216P BIOS. In this case, it works like 3MB RAM configuration.

Fenix77 wrote:
* The KMX-C-02 works and load the EMM.SYS driver and even detects correctly as a SACTsx chipset, and the 128kb UMB memory is correctly detected by QRAM
But it does not support the Large Page Frame (No mapeable area found) and Word for Windows 1.1 (Which i installed in Win 2.11) looks up after i run Winword.exe.

Unlike the 82C235 chipset, the 82C836 chipset can map D000~EFFF segment area only. And I added STACKS=9,512 in CONFIG.SYS file, Word for Windows 1.1 works properly on Windows 2.11/3.0.

Out of curiosity, I saw in the commit that the Samsung SPC-4216P can use a file called phoenix.bin as well as (instead of?) the split roms. What was that file for, exactly? Sorry if this seems like a trivial question.

darksabre76 wrote:Out of curiosity, I saw in the commit that the Samsung SPC-4216P can use a file called phoenix.bin as well as (instead of?) the split roms. What was that file for, exactly? Sorry if this seems like a trivial question.

The phoenix.bin was dumped by MS-DOS DEBUG and splited ROM files was independently dumped by ROM reader. But those are acually same.