mjw@aluxp.UUCP (03/27/87)
I have a few questions about using the AT&T Display Enhancement Board (DEB) and the AT&T Extended Memory Board. Please send email if you have the answers and I'll summarize to the net. (1) Does the device driver (DEDRIVER) for the DEB contain the capabilities of ANSI.SYS (or NANSI.SYS or FCONSOLE.DEV)? (2) If it does not contain these capabilities, does using ANSI.SYS and DEDRIVER.DEV together result in any conflicts? (3) Assuming the drivers are compatible, what order should they appear in CONFIG.SYS? (4) Recently I added enough NEC 41256-12 DRAMs to bring my Extended memory board up to 2MB. AEMM.SYS shows parity errors during initialization and immediately locks up the system. Obviously a portion of the memory is not functional. Is there a quick and intelligent way of determining where the 'bad' chips are? Trial and error just isn't acceptable! Note: The hardware is a 256K motherboard, AT&T PC6300 with a DEB installed. Also, without using AEMM.SYS in CONFIG.SYS, the system sees an additional 384K on the extended memory board and reports no errors during start-up diagnostics. (5) Could someone recommend a procedure that will permit the following configuration (using a 256K motherboard and one AT&T Extended Memory Board): 640K of non-paged memory for MS-DOS, a 360K superdrive ramdisk (drive D:), a 64K superbuffer, and the rest of the 2MB board as a large ramdisk (drive E:). Please give SW1 and SW2 (on the memory board) settings as well as the entries for CONFIG.SYS and AUTOEXEC.BAT. (6) Why did Olivetti place only two dual-socket slots on the 6300? -- Michael Weber ...!ihnp4!aluxp!mjw AT&T Bell Laboratories Allentown, Pennsylvania (215) 770-2732 FREEDOM... The condition in which all sentient beings have a moral and social obligation to control their own destinies to the best of their abilities without hindering others from accomplishing the same.