@6127.adf Future Domain MCS-700 / MCS-600 with TMC-1800 chipset
@60E9.adf- IBM PS/2 SCSI-2 with TMC-18C50 chipset
@5F77.adf Future Domain MCS-350 (no discrete SCSI controller chip! Uses PALs)
IBM SCSI-2 Adapter/A Option Disk v1.00 For IBM/FD SCSI-2
Descriptor files for the MCS-350, MCS-600 and MCS-700
Future Domain's SCSI Device Analyzer
IBM BIOS v1.01 for FD MCS-700 card used in PS/2 Model 77s. 27C64
FD MCS700 BIOS 3.61 Future Domain MCS700 v3.61. 27C64
Design of the software interface for a multimaster bus system
The Future Domain Story
or IBM SCSI-2
The SCSI-2 Adapter /A was OEM'd by Future
Domain, based on the MCS-700 (18C50 VLSI chip). Early
Future Domain branded MCS-700 SCSI controllers may
use the TMC-1800 SCSI controller AND the termination
resistor arrangement of the MCS-600. The MCS-700 and
MCS-600 can do Narrow-Fast of up to 10MB/s to the SCSI
bus and up to 3MB/s to the MCA bus. Please remember
the Future Domain was designed (successfully!)
to be a secondary SCSI adapter.
based on the chip can implement MFM-compatible BIOS
parameters, allowing AT or MCA computers to interact
with SCSI drives as if they were standard MFM hard
drives. This capability will allow use of products
such as PC Kwik disk caching (Multisoft) or Speedstor
(Storage Dimensions) that modify drive parameter. "
18C50 vs 1800 Based Adapters
> What are the differences between the TMC-1800 and
I have to see if these different
chipsets return different values for the Future
Domain BIOS call "Get SCSI Controller Information" INT
13h, Function 18h. The book I have shows only values for
the older FD chipsets. There is another BIOS call that
determines ANSI SCSI-1 or SCSI-2 compatibility. Of
course the TMS-700 will have a much newer BIOS as well.
On the versions I have the boards are remarkably similar
despite the 3 year difference in production. Tiny
differences that add up on the finer points of
The FD design is PIO, not a busmaster. If you have a heavily loaded system, or one with low powered CPU, you might look for a busmaster. If you have a 486DX class system (or above) chances are the PIO will work just fine, because the CPU has more than enough clock cycles to service it.
Jim Shorney pulls a few out of the weeds and says:
Alternate for U4 - CY7C185-20 - 8Kx8 static RAM.
TERMENA Enables integrated
terminating-resistor. Remove if
both INTERNAL and EXTERNAL SCSI -
devices are connected.
on IML System
Lacuna Convenience Partition
That's what I said. The system partition will not work with the *original* Future Domain MCS-700 without the "IBM Support BIOS" .... It works on the IDE-machines (utilizing the IBM Int4B ABIOS extension hooked to generic Bios Int13h -which is the boot / harddisk interrupt- ... attached to hardware IRQ 0Eh) and on the SCSI Models only with the reworked IBM controller BIOS. Reason why (to my opinion): the FD-controller can utilize other hardware IRQs than only 0Eh (14).
My 9577-BTG has the IBM-version MCS-700 with the Rom
BIOS 1.01 (I think) and it has the "convenience
partition" as well. I had the cached SCSI in that
machine as well - it also supports the partition, but is
officially not supported in the Lacunas.
MCS-600 and the DB25
Al Savage confided to the group:
Um, only the DB25 (early SCSI-1) used only one wire per data line, with a combined data ground (unless I'm wrong). All the other SCSI wiring uses a separate ground for every data line, which is why I sold off all my DB25 stuff and went C50 everywhere.
This shows the MCS-600 uses the TMC-1800, lacks active termination, DB25 external port, unshrouded 50 pin internal header, uses a 40.850MHz osc, and has a 12v 2A and 5v 2A rating (the SMD caps are 10u, 16v)
MCS-600/700 or IBM SCSI-2 under W95
Chances are, W9x won't get it right, and you might get a Future Domain TMC-16xx series adapter installed. Which works, but not the best.
FD and IBM BIOS Differences
Tim Clarke tossed this out-
For the Future Domain MCS600/700 adapter ROMs -
a) Future Domain V3.nn = Future Domain and
supports Int 13h via Int 4Ch (SCSI-CAM). Does boot-drive
scan from Id. 0-6. (Peter)... but does not support IBM's
ABIOS functions which use Int 4Bh, which is the one that
establishes / handles a "convenience / reference
partition". And which is the function that reports back
the attached SCSI devices. Max drive size directly
controllable with the latest Future Domain BIOS (v3.61,
IIRC) it's around the 8GB mark (actually 8064MB), as
limited by the Int 13h BIOS call parameters' max. values
(1024-cylinders x 256-heads x 63-sectors x 512-byte
b) IBM V1.0n = Supports Int 13h via Int 4Bh (IBM SCSI). Does boot-drive scan from Id. 6-0 and supports RefDisk Config and Diags. If using the IBM v1.01 BIOS, it has a max drive size of 3.94GB (1024-cylinders x 255-heads x 63-sectors x 512-byte sectors), again IIRC.
> For using the MCS-700 as a secondary controller, allowing drivers to be loaded, how big can the secondary drive be?
This is only limited by the driver's and OS's design, but has limits set by a 32-bit "Logical Block Address" (LBA) of 4 Gigablocks and the assumed 512-byte logical block size = 2 terabytes. Check your OS doc.s and any READMEs for the driver for that OS.
I'd tried that on a machine with IBM
Controller BIOS Rev. 1.0 and the system refused to even
recognize the CD-ROM. I switched to a 1.01 controller
and -voilá- there it was. However: when I set the CD-ROM
to "Slave" it failed to work properly even with 1.01 on
the SCSI controller.
There seem to be dependencies within the Boot-BIOS part of the IBM SCSI Bios on the FD-controller.
1.01 works fine with bigger HDs and CDs ... but dislikes CD-ROMs solely attached to the IDE jumpered as "Slave".
Finally, Peter sez:
18MC means 1800, otherwise the table wraps
and P70 ESDI Adventures
The ROM version on the MCS-700 is 1.01. I've tried it in both slots as well as tried changing the IRQ and such in the Reference disk setup. All of this had no effect on the error.
1) reinstalled the MCS-700 with the IBM
BIOS 1.01 still installed. It continued to give the
error and I ran diagnostics from the Refdisk. The
SCSI test gave an error of 0210000U.
I had tried to disable the BIOS in the system setup on the Refdisk, but it didn't help. Removing the BIOS chip altogether seems to have fixed it though. My only complaint is that it insists on formatting the external hard disk with 32k sectors! I'll have to play with that some more. Now the question is, what functionality have I lost by removing the BIOS chip? Am I correct to assume that it won't be possible to boot off a SCSI disk in this configuration?
ADF File for MCS-600/700 board (TMC-1800 VLSI) Version 1.1
AdapterID 06127h Future Domain SCSI Adapter
Adapter Memory Location
Adapter I/O Location
Select Interrupt Line
ADF File for MCS-700 /IBM MC
SCSI-2 adapter (18C50
Adapter ROM BIOS Address
Adapter I/O Port Address
SCSI Adapter Address (ID)
Select Interrupt Line
Direct Access Fix?
>I've tried to add a 2GB 0664 drive as ID4 to my system. The added drive at ID 4 is listed as "direct access" instead of "hard disk," and no size is listed. When I attempt to low-level format, the list of available drives does not include the drive at ID 4. Can someone please tell how to revive the 0664 that responds as a "direct access" device???
The Magic Christian responds:
'The following procedure should read the firmware parameters from a SCSI drive and then write those parameters back to the media. This will normally restore a fixed disk to the factory default parameters. Not all drives will support this procedure. Future Domain will not be responsible for the results stemming from the use or misuse of this procedure.
1. Insert the Future Domain "SETUP" utility.
This should update the media with the
parameters from the firmware. The drive must accept and
finish the low-level format for the above procedure to
work correctly. Also, some drives do not support a
low-level format. When in doubt check with the drive
PS/2 SCSI-2 Adapter/A and MCS-700
BASEDEV= ---- FD8XX.ADD
After looking at an MCS-350, there is no discrete SCSI
controller. I >assume< the controller
functionality is within one or more PALs.
AdapterID 5F77 Future Domain SCSI Adapter
DMA Arbitration Level
Select Interrupt Line
Use Front Panel Disk Busy
Use MC BUS Wait (IBM Model 80)
The external port is the Apple DB25 style SCSI pinout.