I006F.ADF - optional Init-File for @006F.ADF - see inside ADF @008E.ADF - Kingston MC MASTER 486 ADF v2.23 (VESA video slot) I008E.ADF - Initialization File for @008E.ADF Not sure of these... @706D.ADF - AOX MicroMASTER 486/386 ADF v1.4 I706D.ADF - Init file for @706D.ADF @706E.ADF - AOX MicroMASTER 4386 ADF v1.04 damaged... Installation Guide for MCMaster MC133PD or MC66PD MCMaster Utilities and Processor Upgrade Files (BIOS) MCMR236.EXE MCMaster Utility Diskette v2.36 MCM235.EXE MCMaster Utility Diskette v2.35 MC235I.EXE MCMaster Utility Diskette v2.35I MICROADF.EXE MicroMaster .ADF files Aox MicroMaster 486 32-bit (006F) PORT73.EXE displays various info about host system, installed SIMMs and memory mapping entries. MMPIDD.SYS is the v1.04 Installable Device Driver (IDD), required for recognition of the later (Version 2) adapter IDs. Internal name is MMIDD, as per the earlier v1.03 which appears to have been for the Version 1 adapters. Kingston MCMaster 486 (has the unsupported VESA Video slot) Overclocking the 25MHz to 32MHz Supported Memory Jumper Settings J801 Function ADF Sections Memory Options MCMaster Errors Incompatible Systems Incompatible Adapters Old 486 MCMaster (no VESA video slot) Super Server AOX OS/Master MCMaster 486 version ![]()
J1100 Local Bus Video- If you know more about it, tell ME! Jeff Marden wrote: 25MHz Base Speed Hacking
the 25MHz MCMaster Jim found a stable combination for the 25 MHz MCMaster overclocked to 32 MHz. To recap, the machine would lock up over a period of several hours running Win3.11 and Logstat 5.1 as a test program. This behaviour occurred with an Intel DX2-66 CPU and an AMD 5x86-133ADZ, and did not appear related to cooling. The current combination has a Cyrix/IBM Blue Lightning 486-100 CPU with interposer, and over the past several days, has proven to be stable. It has run 24+ hours without lockup, but must have the planar memory disabled in the MCMaster setup or it locks up almost immediately." All MicroMASTER 486 boards are 32-bit boards. 32-bit MicroMASTER 386 boards have a serial number starting with "AA27..." 16-bit MicroMASTER 386 boards have a serial number
starting with "AA16..." · Uses 5v 486 class microprocessor · Daughtercard connector for VESA Local-Processor · Two SIMM sockets- up to 64MB of onboard memory on 32-Bit PS/2 Models 70 and 80, or 16MB on 16-Bit PS/2 Models · Internal math coprocessor · 8K internal cache and 128K external zero-wait-state cache · Onboard clock · Full access to all of the PS/2 ® computer's Extended Memory · Support for all PS/2 compatible operating systems · Supports Micro Channel ® multi-busmaster capability Supported Memory MCMaster uses 80ns or faster FPM, or IBM PD coded 32-bit wide, 70 ns 72 pin SIMM memory modules. As per UZnal:
MCMaster can also function with no onboard memory installed, using only memory that is already installed in the system. Be aware, however, that running MCMaster with only off-board memory extracts a performance penalty, especially in a 16-bit PS/2 system like the model 50 or 60.
· If only one SIMM is installed, it must be installed in location U900. · If 16 or 32MB SIMMs are used, Jumper J801 is connected to 1 and 2. Function
of J801 Tim Clarke talks him down from the ledge with: adapterid 008eh MC MASTER ADF v2.23 There is a need for the unusual size of the ADF description. This adapter can "take over" and has a lot of features that are found in few other adapters. I have also gone wild on the differing memory options, because people want to use the planar memory on 8560s or 8580s and don't understand the performance hits. ;remove semicolon from next line if you wish to use
INITPROG Not sure of the function of the following stuff.
Operating mode Standard Mode INITPROG or IDD If the device driver is loaded in the
CONFIG.SYS file after the memory board's driver, or the
boot track initializer comes after the boot track
initializer for the memory board, the MCMaster will be
aware of the third-party memory and install its own
memory above the third-party memory. The
installable device driver is on the MCMaster option
disk. It's called MMPIDD.SYS. If you use the MCMaster driver, place it
after the driver for the memory board in your CONFIG.SYS
file. For example: IO selects NOTE: 3b0, 3c0 and 3d0 are normally used for video. Rem out the ";" if you want to use them. Arbitration levels
Interrupt level Option ROM address
The "Disable board" option renders the
MCMaster's ROM invisible to the Micro Channel bus: don't
select this option unless instructed to by Kingston
Technical Support for diagnostic purposes. AIX Flush Mode For most installations with no other
busmaster adapters in the system, Mode 1, the default,
will function perfectly well. If another busmaster is
present, select Mode 2. IBM SCSI controllers require
Mode 2. In a small number of cases, if Mode 2 does not
perform correctly, use Mode 3. Keyboard emulation
If your application experiences
unexpected keyboard behavior, try switching to software
emulation. Video Option board
Memory
options NOTE: OS/2 2.0 and higher is "aware" of the MCMaster and will load itself into its onboard memory regardless of the memory configuration. <Mapped, report
all> The disadvantage of mapping is that another busmaster adapter in the system sees memory from the host system's point of view, while the MCMaster has its own viewpoint. We supply drivers to allow mapping to work under Windows 3.0/3.1 or OS/2 1.2/1.3 with busmastering SCSI controllers. Their use is explained in "Special Drivers for SCSI Adapters." <Mapped, report all,
<16meg> The 16-bit version of the Micro Channel bus allows only 24 bits of addressing. If a DMA device, such as the floppy disk controller, attempts to write past the 16MB boundary, errors can occur due to this limitation. <Unmapped> <Unmapped, <16M>
<Report all> reports all useable memory (planar and MC MASTER) to the operating system. <Report MM> The disadvantage is that you can't have
any other memory boards in the system. If your system
has only 1 megabyte on the planar, this is not a great
loss. However, if you have a lot invested in Micro
Channel memory boards, you probably want to keep using
them. To use this other memory, you need to select
"Mapped" or "Unmapped." Note: In some systems, the MCMaster cannot disable motherboard memory. If the MCMaster signs on with "Hardware Rev 00.11," you have one of these systems. In this case, the MCMaster behaves as it would in "Mapped, Report All" mode except that the MCMaster uses only its own memory. The host CPU (and any other busmasters) still see system memory first, followed by MCMaster memory. <Mapped, report MM,
<16meg> <SS> and <SS16>
are reserved MCMaster Errors MCMaster Error 01:
DMA Set to greater than 16Meg MCMaster Error 02:
DMA Set for non-contiguous boundary crossing MCMaster Error 03:
Invalid Status MCMaster Error 04:
Bus Timeout Incompatible Systems Some early Model 80 planars do not support busmastership. Needless to say, this creates problems for the MCMaster. IBM has issued two different ECA's (engineering change announcements) ECA #048 and ECA #031, which cover a specified range of planars. Systems Affected by Serial
Number:
Problem Planar FRUs
IBM 386 Enhanced Memory
Adapter IBM SCSI Adapters About Third-party Memory
Boards Other memory boards add a small
configuration program to the boot track of your hard
drive. Such a program is called a TRACK0 INIT. To
support this feature, IBM has a new version of the Set
Configuration program, SC.EXE. If you've already
installed a board that uses this feature, you probably
already have the new SC.EXE. You will find detailed
instructions for using it with the MCMaster under the
heading "Operating Mode." If you haven't installed such
a memory board, you don't need to worry about this
feature. AOX MicroMaster 486 Card ID 006F ![]()
MM1200 Bus interface ASICs U1201 Plus Logic chip Memory/DMA controller ASIC U0508 Toshiba TC5508J-35 U0701-U0704 Toshiba TC55328J-25 U0705, U0706 Toshiba TC5588J-15 Scan courtesy of Jim Shorney. Micro Channel “Super Server” The term “super server” is one that IBM uses to refer to a number of possible application-specific LAN server configurations. The configurations are a combination of hardware and software products designed to deliver maximum performance for PS/2 Micro Channel systems in server applications. One of these potential solutions that IBM has shown in business shows as a technology demonstration is based on the PS/2 Model 95 XP 486, combined with several high-performance bus master adapters and OS/2 operating system software. It uses an asymmetrical multiprocessor implementation with a unique function split between the 486 microprocessor of the base system and a second processor, the AOX MicroMaster 486. The configuration features a huge amount of both internal and external storage capacity using SCSI bus master adapters, 3.5 inch 320MB disk drives, and the PS/2 3511 external enclosures. Figure 5.39 illustrates one of the possible IBM “super server” configurations that was demonstrated as a technology in business shows in 1990. There were six bus master adapters in the system: two 32-bit SCSI boards, two 16/4 Token Ring adapters, one Ethernet board, and the AOX associate processor. The software included OS/2 Extended Edition 1.2 and a customized version of 32-bit LAN Server designed to support the two 486 microprocessors. The SCSI bus masters used SCB architecture to provide chaining of commands. Up to 16 commands could be chained together and sent to the SCSI adapter for execution. The adapter also supported scatter-gather operations, which permitted the data to be scattered anywhere in memory and gathered by the SCSI adapter into it’s cache for execution. This process reduced the overhead required for data transfers by eliminating a number of steps. The LAN adapters used are also capable of command-chaining and scatter-gather operations. In the demonstration, each of the 486 microprocessors in the system had a copy of OS/2 loaded onto it. The associate processor was responsible for managing the file system portion of the OS/2 kernel and the LAN requests. The system board processor ran the Presentation Manager portion and user applications. The implementation also supported medialess workstations by loading OS/2 in the memory of the workstation. In another technology demonstration, another “super server” configuration connected two servers to the same disk array, illustrating the ability to recover from a failing disk drive or a failing server. In addition, a PS/2 Model 95 was configured with four additional 33-MHz 486 processors on expansion boards to provide even higher levels of performance. Aox OS/Master Darius Vaskelis wrote: As for multi-processing with Aox MicroMASTER adapters, it can be done. Currently, the only means to do so is with the Aox OS/Master program. It allows the motherboard CPU to run one operating system, and the CPU on the MicroMASTER to run another. Commercial appliations include running a joint OS/2 LAN Server/Manager and Novell Netware server, or as mundane as two isolated DOS machines in one box. OS/Master requires the Aox MicroMASTER 386-33MHz or the Aox MicroMASTER 486-25MHz adapter, and does NOT run on the 386-20/25MHz versions. |