Piper's Pit BBS/FTP: ibm 0020

home *** CD-ROM | disk | FTP | other *** search

/ Piper's Pit BBS/FTP: ibm 0020 - 0029 / ibm0020-0029 / ibm0028.tar / ibm0028 / BLUEMAX.ZIP / BLUEMAX.SEZ / README < prev next >

Wrap

Text File | 1990-11-29 | 20.9 KB | 408 lines

BlueMAX 5.0 - supporting BIOS compression on PS/2 386 and 486 systems as well as PS/2 Models 50 and 60 with the AOX or Cumulus 386 upgrade board. Welcome to BlueMAX! As we improve our product beyond what it was when the manual was last printed, up-to-date changes are reflected in this file. You will also find tips for special hardware and software configurations. Be sure to consult this file if ever you receive an update. If you need Information on.....Consult this File in the BlueMAX Directory ------------------------------------------------------------------------- PC-DOS Version 4.0........................................PC-DOS.400 AutoCAD/Extended Autolisp.................................AUTOCAD Windows Information and Installation......................WINDOWS.DOC Stripmanager..............................................STRIPMGR.DOC How to Restore CONFIG.SYS, AUTOEXEC.BAT, after Install or Maximize ------------------------------------------------------------------ The following files are created by BlueMAX and may be of use to you if you wish to restore your original CONFIG.SYS and/or AUTOEXEC.BAT. CONFIG.XXX (with XXX being 001 to 999) AUTOEXEC.XXX BlueMAX.XXX * PREINST is a .bat file that restores your CONFIG.SYS, AUTOEXEC.BAT, BlueMAX PROfile, and other .bat files to the preinstalled state. * PREMAXIM is a .bat file that restores your CONFIG.SYS and AUTOEXEC.BAT to the state before the last pass of MAXIMIZE. ADDITIONAL INFORMATION ====================== The information in this file is divided into the following sections: GENERAL INFORMATION MULTITASKING NEW OPTIONS DISPLAY ADAPTERS NETWORK INFORMATION DISK CONTROLLERS MISCELLANEOUS INFORMATION NOTICE: Owners of PS/2 or other Micro Channel machines can skip the sections on hardware listed below. If you are installing BlueMAX on one of these machines, please take a look at notes on software, networks, and other general and miscellaneous topics. By running Maximize, the Micro Channel adapters will be automatically configured and protected. GENERAL INFORMATION =================== IBM ROM Basic and BCF= ---------------------- Programs that rely on normally unused features specific to the IBM BIOS, but not found on other AT/386 or Micro Channel BIOSs, may fail when running with a BIOS compressed by BlueMAX. One example of this is IBM's BASIC program that was designed to work only with IBM Corporation BIOS computers. Because ROM BASIC, ABIOS (OS/2 specific), POST, and other non-critical parts of the BIOS have been compressed out of the PS/2 BIOS, programs dependent on the extra features of a specific IBM BIOS may fail. This is not a failure of the BIOS or of BlueMAX, but is an intentional sacrifice to return the most high DOS possible for the widest range of programs. To use programs that are dependent on the normally unused features, uninstall BlueMAX or remove the BCF= option from the BlueMAX profile. MS-DOS Version 4.00 ------------------- If you are running Microsoft's MS-DOS version 4.00 or later, do NOT attempt to put BUFFERS, RAMDISK, or FASTOPEN into EMS memory as there are problems with that code in MS-DOS 4.00 and 4.01. DOS 4.x INSTALL= Command and "Error in CONFIG.SYS line __" ---------------------------------------------------------- Beginning with DOS 4.x, you may load .COM and .EXE files in CONFIG.SYS via the INSTALL command. These files may be loaded into high DOS memory with 386LOAD.COM rather than 386LOAD.SYS. Be sure to use the GETSIZE option to determine the file size prior to loading into the high DOS region. If the load is successful, the entire .COM or .EXE file is placed into high DOS memory and 386LOAD.COM terminates as usual leaving no resident memory behind in low DOS. However, DOS expects a program loaded via the INSTALL= command to terminate and go resident; if it does not, DOS (erroneously) concludes that something has gone wrong and reports "Error in CONFIG.SYS line __". This message is harmless and may be ignored. LIM 4.0 Mapping --------------- In accordance with the LIM 4.0 specification, BlueMAX will map the area from 1000-A000 as EMS mappable pages. There are some programs that have problems when they encounter that area as mapped pages. In these cases, an EXCLUDE=1000-A000 is required in the BlueMAX.PROfile for the program to operate properly. The programs listed below may need an EXCLUDE=1000-A000 option or another special EMS option; Name BlueMAX Option or Special Instructions ----- -------------------------------------- Paradox 3.0............EXCLUDE=A000-B000 (for monochrome or CGA systems) SuperCalc5.............EXCLUDE=1000-A000 (see note at end of chart) Deluxe Paint...........EXCLUDE=1000-A000 (for versions 1 & 2) Smartware II...........EXCLUDE=1000-A000 Javelin................EXCLUDE=1000-A000 SuperProject+..........EXCLUDE=1000-A000 SQL Windows............EXCLUDE=1000-A000 Word for Windows.......EXCLUDE=1000-A000 (under Windows 2.11 and 2.1) hDC Windows Express....EXCLUDE=1000-A000 (under Windows 2.x or use WIN/N) Pagemaker..............EXCLUDE=1000-A000 (under Windows run-time 2.X, or use WIN/N) Excel..................EXCLUDE=1000-A000 (run-time version only) Ventura Publisher......FRAME=E000 (or below if the EMS page frame starts above E000) JLASER/SA..............FRAME=D000 (versions of the JLASER/SA software prior to 4.14 only) EGA/VGA programs that use monochrome ------------------------------------ Some programs that normally run in color mode may use the monochrome buffer area to access special characteristics of the VGA/EGA card installed. If these programs are used, the monochrome buffer area can not be reclaimed as high DOS or as an EMS area without video problems resulting. Here is a list of all known programs that run on EGA/VGA systems but use the monochrome area as well. Name BlueMAX Option or Special Instructions ----- -------------------------------------- SOFTKICKER..................*remove* INCLUDE=B000-B800 and/or USE=B000-B800 CLEAR (flow chart program)..*remove* INCLUDE=B000-B800 and/or USE=B000-B800 SUPERCALC 5.................*remove* INCLUDE=B000-B800 and/or USE=B000-B800 NOTE: Supercalc 5 can be setup to not use the monochrome buffer area. Consult the Supercalc manual for full details. Also, if running Supercalc on a CGA or monochrome system, you may have to use the VGA or EGA option. DISPLAY ADAPTERS ================ The following display adapters need special options to be placed in the BlueMAX.PROfile: Name BlueMAX Option or Special Instructions ----- ------------------------------------- Amdek 1280..................VGA Autograph...................RAM=C400-C800 Everex 659 & 673............NOROM IBM CGA.....................CGA Imagraph....................VGA and RAM= (their 64KB high DOS memory segment) Matrox PG 1281..............RAM=C000-C800 MDS Genius..................VGA (you may need to load VHRANSI.SYS before the BlueMAX device driver) NEC Monographics............VGA and RAM=C000-D000 Pepper Pro 1280.............RAM=C000-C800 Sigma Designs EGA 480.......NOROM Sigma Designs Laserview.....VGA and RAM= (their 64KB high DOS memory segment if not configured at A000) Targa.......................VGA and RAM= (their 64KB high DOS memory segment if not configured at A000) The CGA Solution Card.......VGA and RAM=C000-C800 Ultimate EGA................(Add the line DEVICE=D:\PATH\ULTIMATE.SYS to any blank line BEFORE BlueMAX.SYS) VMI COBRA...................RAM=C000-D000 WYSE 700....................VGA when using HI RES mode Zenith 449..................NOROM DISK CONTROLLERS ================ BUSMASTERING CONTROLLERS: To optimize performance, busmastering controllers bypass the sytem board DMA controller and perform their own DMA transfers. With a memory manager installed, memory may be remapped and not retain a one-to-one linear to physical relationship. So that DMA transfers are properly performed in memory which is not mapped one-to-one, a busmastering device must use one of two schemes, double buffering or VDS support. During initialization, BlueMAX displays an error message if it detects any bus mastering hard disk controller that is not VDS compatible. In order for BlueMAX to detect a busmastering controller, either high DOS memory or an EMS page frame must be present. Vendors of certain busmastering controllers that do not support VDS in ROM provide software drivers to support either VDS or double buffering schemes. VDS drivers may be loaded after BLUEMAX.SYS in CONFIG.SYS and may be loaded into high DOS memory. If the driver provides double buffering, it must be loaded before BLUEMAX.SYS and must be loaded into low memory. Some disk caches implement double buffering schemes (i.e. SMARTDrive). If you are using a cache which double buffers disk transfers, do not load the cache into high DOS memory. Doing so will cause the disk cache buffer to be loaded into memory that is not mapped one-to-one and can result in data loss. See BUSMASTERING DEVICES in the WINDOWS.DOC file for information specific to this problem and Windows. To bypass the BLUEMAX.SYS busmaster error message at startup, add the keyword NOSCSI to the BlueMAX.PROfile. If BLUEMAX.SYS has detected a nonsupportive busmastering controller and SMARTDrive is not loaded, an error message will result when loading Windows 3.0. If you are SURE you have a VDS compatible busmastering controller, place SET BUSMASTER=VDS in your AUTOEXEC.BAT to bypass this error message and load Windows 3.0. Note that using these options without regard or knowledge of your system setup can result in the loss of data. Contact your hard disk controller manufacturer for detailed information about your hard disk controller. To ensure correct operation of each of the following busmastering controllers, follow the listed steps for each: Adaptec: If you are using an Adaptec 1540 or 1542, Adaptec ships a software driver that must load in your CONFIG.SYS before BlueMAX.SYS. The Adaptec driver is available from Adaptec as part #ASW1410. Copy the file SCSIHA.SYS onto your boot disk. Insert the line DEVICE=d:\path\SCSIHA.SYS /V386 /B16 to your CONFIG.SYS file preceding the BlueMAX.SYS line. The driver can be obtained from the Adaptec BBS at 408-945-7727. All other requests for this driver should go through your Adaptec dealer. Storage Dimension: Storage Dimension SCSI drives use a 16KB RAM buffer area in high DOS memory. Protect the appropriate 16KB address area with a RAM= option in the BlueMAX.PROfile line. The default address is either C800-CC00 or CC00-D000. Therefore, add the statement RAM=C800-CC00 or RAM=CC00-D000 to the BlueMAX.PROfile. Western Digital FASST SCSI: This controller ships with two software drivers called FIXMEM.SYS and SSTBIOS.SYS. Copy these device drivers to your boot disk. Insert the separate lines DEVICE=d:\path\fixmem.sys and DEVICE=d:\path\SSTBIOS.SYS /WE to your CONFIG.SYS file preceding the BlueMAX.SYS line. VDS support in incorporated into ROM revision 3.36 or later. Other, non-SCSI, Hard Drives and Controllers: SEAGATE ST01 & ST02: These controllers both use a 32KB RAM buffer area in high memory. Protect the appropriate 32KB address with a RAM= option in the BlueMAX.PROfile. The default RAM= option should be RAM=C800-D000. This buffer area may vary from system to system. Other possible locations are RAM=D000-D800 and RAM=D800-E000. CONNER IDE Controller/Drive Combination: The Conner IDE Controller/Drive Combination do not function with certain BIOSes which do not save interrupts. Conner is currently working on a solution to this problem. In order to get the latest available information on Conner IDE drives, call 408-954-3200. AWESOME I/O: If your system contains an Awesome I/O card, be sure the AWESOME.SYS device driver precedes BlueMAX and place the appropriate RAM= statement in the BlueMAX.PROfile. The parameters to RAM= correspond to the 48 or 64 KB region used by the Awesome I/O card for its buffers. OMTI 8620: For optimal use of BlueMAX with this hard disk controller, add the following line to CONFIG.SYS before BlueMAX.SYS; DEVICE=d:\path\OMTIFIX.SYS where "d:\path\" represents the drive and path containing the OMTIFIX.SYS driver. If you chose the default settings when installing BlueMAX, "d:\path\" would be "C:\BlueMAX\". This program moves the extended EGA data area from 639-640KB to a more optimal location in Low DOS. Thanks to Steve Gibson, who writes the highly regarded Infoworld column "Tech Talk", for providing this driver to us. MULTITASKING ------------ MICROSOFT WINDOWS 3.0: Windows 3.0 is compatible with BlueMAX in REAL mode and 386 Enhanced mode. See the WINDOWS.DOC file for more details. MICROSOFT WINDOWS 286/386: For help in installing Windows 286 in conjunction with BlueMAX, see the WINDOWS.DOC file found in the BlueMAX directory. DESQVIEW: If you are using Quarterdeck's DESQview, you can provide additional memory for your applications by installing the QEXT.SYS driver (found on your DESQview distribution diskette). Be sure this driver is installed before BlueMAX.SYS. The effect is to reduce DESQview's low DOS memory requirements by about 60KB, thereby increasing the amount of available memory for your programs by the same amount. In order to further optimize for DESQview, it is advantageous to include up to four 16KB pages from your high DOS region. This can be accomplished by using the INCLUDE= option in the BlueMAX.PROfile. Use of this option will decrease the amount available high DOS memory. For specific information on the INCLUDE option, see Chapter 4 in your BlueMAX User's Guide. Certain versions of DESQview may require that you use XDV.COM rather than DV.COM for optimal performance. NETWORK INFORMATION ------------------- STARLAN: If you have configured your AT&T Starlan network to map its memory into the A000 segment, use the VGA option in the BlueMAX.PROfile. If you map its memory into any other segment, use RAM= to tell BlueMAX not to use those addresses. ETHERLINK PLUS: If you have configured your EtherLink/Plus network to map its memory into the A000 segment, use the VGA option in the BlueMAX.PROfile. BANYAN: The /NC option must be used on the first line calling the network in your AUTOEXEC.BAT. The line should read BAN /NC. The two remaining drivers must be loaded individually. In order to find the proper names for the drivers, load BAN.COM without the /NC option and look at the 386UTIL /M display. The following is a typical setup prior to loading into high DOS: ban/nc intr2ban epcbfs pcsem pcnetb login NETWORK DEVICE NAMES: If your network needs to know about device driver names used by BlueMAX (perhaps because the network allows access only to those names entered in some table), at various times we use the names EMMXXXX0, QMMXXXX0, and 386MAX$$. For example, some versions of 10NET must have our driver identified in the 10NET profile. Add LDEV=EMMXXXX0, LDEV=QMMXXX0 and LDEV=386MAX$$ to that profile. Use 386UTIL/D to see a list of currently installed device drivers and the names that they use. NOVELL ELS: The program NET$OS runs in protected mode, does not support VCPI, and therefore is not compatible with BlueMAX. TOPS: The DMA setting on the card must be disabled. Use /DMA=NONE on the TOPS ATALK or ALAP line. IBM TOKEN RING: In order for the network to function properly, you must provide BlueMAX with the RAM and ROM locations of the network board by adding a RAM= option in the BlueMAX.PROfile. With the default network settings, the appropriate settings are RAM=CC00-CE00, D800-DC00. The network RAM and ROM can be configured at different locations and the associated RAM= statement must reflect any such changes. The ROM address is jumper switch configurable. The RAM address can be configured with a command line switch to the DXMC0MOD driver in the CONFIG.SYS. See the Token-Ring manual for details. To maximize use of high-DOS memory, we recommend that the network RAM and ROM be relocated such that they occupy contiguous memory locations, and the RAM= statement in the BlueMAX.PROfile be adjusted appropriately. 3COM NETWORK CARDS: Some 3COM network cards use RAM buffer areas in high DOS memory. A RAM= option may be required in the BlueMAX.PROfile if the network does not function properly when BlueMAX.SYS is installed. Name BlueMAX Option or Special Instructions ----------------------- -------------------------------------- 3COM ETHERLINK............None. 3COM ETHERLINK PLUS.......None. 3COM TOKENLINK PLUS.......None. 3COM ETHERLINK II.........RAM= the 16KB address of the RAM buffer. 3COM TOKENLINK............RAM= the 16KB address of the RAM buffer. If your card is listed as using 16KB of buffer RAM, you need to add a RAM= option to a blank line in the BlueMAX.PRO file. The appropriate range depends upon the starting address determined by the dip switch settings on the card. Check the documentation for the 3COM card you have for more information. MISCELLANEOUS INFORMATION ------------------------- PARITY ERRORS: If the TIMEMEM utility encounters a Parity Error when timing memory, it now reports the address of the 4 KB physical memory page containing the bad RAM chip. This address is independent of any memory swapping or DMA transfers which may have rearranged the mapping of linear to physical addresses. With the knowledge of how memory chips are organized in your system along with the given address, you should be able to identify the row containing the bad chip. Because parity errors are sometimes intermittent, it may require several iterations of TIMEMEM to catch the error. The following batch file runs continuously until a parity error occurs: echo off :LOOP 386UTIL timemem >timemem if not errorlevel 1 goto LOOP type timemem PACKED FILE ERROR: If you see the message "Packed file is corrupt", then you must marginally increase the amount of conventional memory used by DOS. This is to work around a known bug in the compiler used to pack the file in question. Determine the current starting address of available conventional memory using the BlueMAX MAPMEM display. Increase the FILES or BUFFERS statement in CONFIG.SYS until the starting entry in the last row in low DOS memory is greater than or equal to 0FF0h. SUPER PC KWIK: It is suggested that if Super PC Kwik is loaded into high DOS, the /T:4 or /T- option should be placed on the end of the SUPERPCK line. This will assure more accurate loading of programs into high DOS memory. Once the disk cache is loaded into high DOS, the /T: number can be increased to better disk performance. Consult the Super PC Kwik manual for full details on how to use this option. PC TOOLS VERSION 6 MIRROR: For users of Mirror, if the message that Mirror is already loaded into memory occurs when Mirror is being loaded by 386LOAD, but not when loaded by itself, contact Central Point Software for a replacement or load Mirror into low DOS. COMPLETE COMMUNICATOR: The resident program CCBAK will not load properly into high DOS memory. It gives an error message indicating that it is unable to locate itself. Be sure to load this program into low DOS memory. AT&T SX: This computer may have a VGA ROM at E000-E800 or at both E000-E800 and C000-C800. To gain the most high DOS on this computer, use the SETUP program that came with the machine and "decode" the video ROM at C000 and E000. BlueMAX detects the dual ROMs at C000 and E000. The ROM at E000 will be eliminated leaving the standard VGA ROM at C000-C800. DELL 310 COMPUTER: Be sure this system is enabled for fast system and video BIOS. To enable, press Ctrl-Alt-Enter at startup and select the FAST BIOS ON and FAST VIDEO ON options. MYLEX SYSTEM BOARDS: To recover the maximum amount of high DOS memory, specify USE=E000-E400. Zeos 386 machines use a Mylex motherboard. COMPAQ 16 MHz SYSTEMS: If you have difficulty rebooting your COMPAQ 16 MHz system with BlueMAX installed, you may need a new BIOS ROM revision K or later. To obtain one, contact your dealer. The dealer should reference the memo dated 12/16/88, TRN#12168.007 in COMPAQ's database under the listing 386MAX. NEW 386LOAD OPTIONS ------------------- VDS: 386LOAD will not relocate a set of known disk caches into high memory if BLUEMAX.SYS has detected a busmastering hard disk controller that does not properly handle disk transfers into memory that is not mapped linear to physical one-to-one. (See "Busmatering Devices" for more details.) If you have received the error message, and you still wish to load the cache high, add the VDS keyword to the 386LOAD line. USE THIS KEYWORD WITH CAUTION. THE RESULT OF OVERRIDING THE ERROR MESSAGE WITHOUT REGARD TO THE TYPE OF HARD DISK CONTROLLER IN USE IS LOSS OF DATA.