README.TXT Driver File Contents (

README.TXT for Turtle Beach Systems CD Master II

This file contains information on the DOS SCSI drivers and various utilities 
that can help you troubleshoot your system.

The SCSI Configure Application allows you to specify drive letter assignments 
and other important parameters of your connected CDROM drives.

Session Selector is used to determine which session on a multi-session disc will 
be accessed by File Manager and any File...Open dialogs in other Windows applications.  
This capability only applies to the WIndows environment.

Note to Network users:

The Installation routine places CORELCDX at the beginning of your AUTOEXEC.BAT file.  
This may cause problems with network drive letter assignment if you have multiple 
CDROM drives or hard disk partitions.  To remedy this problem, move the CORELCDX 
line so that it comes AFTER the command which loads your network drivers.  In many 
Novell systems, this is called STARTNET.  When you do this, your network drive 
letters will be assigned before CDROM drive letters.

If you had a CDROM drive already installed:

The Installation routine scans AUTOEXEC.BAT for the MSCDEX command line.  If it 
finds one (which would indicate that you already had a CDROM drive installed), 
it will REMark out the MSCDEX line and move control to CORELCDX.  The device 
driver names that MSCDEX uses are specified by the /D: parameter.  The device 
names used by CORELCDX are stored in the CRLSCSI.INI file which lives in the 
same directory as CORELCDX.COM.  These two sections of CRLSCSI.INI are important:

[CDROM Drivers]
(This entry assigns the driver name to CDROM drives on the SCSI bus.  The driver 
names are assigned when CUNI_ASP.SYS loads in CONFIG.SYS.  If you have more than 
one CDROM drive on the SCSI bus, the first will be sub-unit 0, the second sub-unit 
1, etc.)

(This entry tells CORELCDX which driver names to look for when assigning drive 
letters to CDROM drive units.  If you had an existing CDROM using MSCDEX, as above, 
its driver name would be inserted before 'MSCD008'.  Drive letters are assigned to 
CDROM units left to right.  Therefore, your existing CDROM drive letters should be 

    AdvanSys Universal ASPI Manager

    This file contains important information and last-minute changes
    regarding the AdvanSCSI ASPI Manager for DOS & Windows.

    How to reach AdvanSys
    BBS:                    408-383-9540 (9600 baud, 8 bits, 1 stop, no parity)
    Interactive FAX:        408-383-9753


    ADVASPI.SYS is the AdvanSys Universal ASPI Manager for DOS & Windows.
    It is designed to support all AdvanSys host adapters (ISA, EISA, VL, and
    PCI).  It will support MS-DOS(tm) version 4.01 and better.

    ADVASPI.SYS is loaded in the CONFIG.SYS file.  For a default installation,
    simply add this line:


    Command-line options can be added on the same line, separated by forward
    slashes.  For example:


    ADVASPI.SYS can also be loaded into high memory, if the appropriate
    memory manager has been installed prior to loading ADVASPI.

    Command-line options

    There are several command-line options that can be used with ADVASPI.SYS.
    Most installations will not require any of these, but there
    are circumstances where one or more may be necessary.

    By default, logical units (LUNs) are not supported by ADVASPI.SYS.  To
    enable LUN support, specify this option on the command-line.

    ADVASPI will pause and wait for the user to press a key before continuing
    once loaded.

    A verbose display will be printed during initialization, showing adapter
    I/O ports, IRQs, and other miscellaneous information.

    This option can be used to specify a specific I/O port address that an
    AdvanSys ISA or VL adapter card can be found at.  Up to four of these
    options can be present on the command-line.  The I/O port must be specified
    in hexadecimal (the same way the BIOS and the AdvanSCSI Setup display
    it).  For example, to use adapters at ports 190 and 330, add this to the
    command-line in CONFIG.SYS:


    To avoid searching for any ISA or VL adapters, add a minus ('-') after the
    /I option:


    Note that ADVASPI will still automatically search for EISA and PCI
    adapters, no matter what port is specified.

    /NE and /NP
    These options will disable searching the EISA and PCI bus for AdvanSys
    cards, respectively.  The host adapters will not be controlled by ASPI
    and therefore unavailable for use by other drivers or applications.

    Command Queueing and DOS/Windows

    Because DOS/Windows is a single-tasking operating system, there is probably
    no need to enable command queueing in the AdvanSCSI Setup (Ctrl+A).
    Testing has shown that in some circumstances command queueing will
    actually degrade performance under DOS/Windows.

     AdvanSys ASPI Disk Driver

    ADVDISK is an ASPI Disk Driver for MS-DOS.  It is an installable
    device driver that is loaded in the CONFIG.SYS file.  To install,
    copy ADVDISK.EXE to your boot drive (C:) and add this line to CONFIG.SYS:


    Command-line options

    ADVDISK is actually two components, the resident driver (installed in
    CONFIG.SYS) and the executable (run from the DOS command-line).  Each
    component has it's own set of command-line options.

    The resident driver recognizes these options:

    The driver will pause after loading.

    ADVDISK will, by default, attempt to use all fixed, removable, and
    magneto-optical disk drives it finds on the SCSI bus.  If a particular
    device is being used by another driver, add this exclude option to the
    command-line, and ADVDISK will not control the device.  For example:


    will exclude the device on host 0 with device ID 3 from control.

    ADVDISK will only reserve one drive letter for each REMOVABLE device.
    Under most circumstances, this is sufficient.  However, if the media used
    by this device has more than one partition on it, ADVDISK will need to
    reserve more drive letters for each device.  For example, if using media
    with two partitions use:


    If ADVDISK does not detect as many partitions on the media as specified
    to reserve, it will report "drive not ready" for the undefined partitions.

    The executable component of ADVDISK has it's own set of command-line

    /? or /H
    Displays a usage screen detailing all the command-line options available.

    ADVDISK will display a map, showing which SCSI devices are associated
    with DOS drive letters, and their lock status.

    LOCK [drive: | ALL]
    This will lock a particular drive (or all ADVDISK drives) into place.
    Media must be present in the drive for this command to be successful.
    Once the drive is locked, the media can not be ejected from the drive
    using the eject button.  This is only applicable for removable devices.

    UNLOCK [drive: | ALL]
    This command will unlock the particular drive, and allow for the media
    to eject normally.  This is only applicable for removable devices.

    EJECT [drive: | ALL]
    The media will be ejected from the drive.  If the drive is locked, this
    command will unlock the drive and then eject the disk.  This is only
    applicable for removable devices.

    ADVDISK has a simple disk partition program built-in.  This program should
    be used for any unpartitioned media you wish to use with ADVDISK.

    The program will ask in an interactive manner which drive is to be
    partitioned.  ADVDISK will not generate more than one partition on the
    media, and will not selectively remove partitions.  It will re-partition
    disks simply by overwriting the old partition.

    PARTITION will completely wipe out any information already on the media
    and therefore should be used with care.  It will ask for confirmation
    before partitioning the media.

    Using ADVDISK with real-time disk compression

    Testing has not demonstrated any compatability problems with ADVDISK
    and real-time disk compression, such as Stacker, DoubleSpace, or
    DriveSpace.  However, these utilities will swap drive letters to
    make the compressed drive seem to exist where the uncompressed used
    to reside.  This can confuse ADVDISK's locking and status reporting

    To use these features, specify the drive letter that corresponds to the
    uncompressed drive when working with ADVDISK.

    Copyright (c) 1994-1995 Advanced System Product Inc.  All rights reserved.


Version 5.0 of Microsoft's SmartDrive disk cache utility, provided
with MS-DOS 6.2, is capable of caching CD-ROM drives. The program is designed
to work exclusively with MSCDEX CD-ROM driver.

Corel's PATCH_SD.COM program can modify the SMARTDRV.EXE to recognize Corel
CORELCDX as a valid CD-ROM driver and cache CD data.

The SMARTDRV cache uses memory more efficiently than Corel CDXCACHE - the
same block of memory will be used simultaneously for hard disk and CD disk

On the other hand, the CDXCACHE program has smaller overhead and operates
faster then SMARTDRV. Also, the CORELCDX /UNLOAD option will not work with
SmartDrive, as the cache program needs to be loaded after CorelCDX.

The PATCH_SD.COM program is designed to modify version 5.0 of SMARTDRV.EXE,
(45145 bytes in size only). If the binary image does not match, the patch will
not be installed.

The patching program scans memory to locate the active SmartDrive cache
program and from there locates the original disk image of SMARTDRV.EXE.
If the SmartDrive cache is not currently installed, the program will ask you
to enter the full path and name of the disk file to patch.

The original Microsoft SMARTDRV.EXE is saved in the same directory as

In order for the patch to work, you need to reboot the system (to reinstall
SMARTDRV.EXE). Also, for SmartDrive to recognize a CD device, the CorelCDX
driver needs to be installed before SMARTDRV.EXE (e.g. by changing sequence
of entries in AUTOEXEC.BAT).
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web3, load: 0.69