TABLE OF CONTENTS ================= 1.0 INTRODUCTION ------------ 1.1 PowerIDE! Block Diagram 2.0 GETTING STARTED --------------- 2.1 System Requirements 2.2 IDE Controller Support 2.3 Installing PowerIDE! 2.4 Uninstalling PowerIDE! 3.0 DRIVERS AND UTILITIES --------------------- 3.1 Hard Disk Driver 3.2 32-bit Disk Access Driver 3.3 CD-ROM Driver 3.4 CD-ROM Extensions 3.5 Local Bus Configuration Utiltiy 3.6 Diagnostic Utility 3.7 CD-ROM Utilities 3.7.1 FDEJECT.COM 3.7.2 FDLOCK.COM 3.7.3 FDUNLOCK.COM 3.7.4 FDAUDIO.COM 4.0 ATASPI MANAGER -------------- 4.1 DOS ATASPI Manager 4.2 Windows ATASPI Manager 5.0 CUSTOMER SERVICE ---------------- 5.1 Troubleshooting Tips 5.2 Top 10 Questions and Answers 5.3 Contacting Future Domain 1.0 INTRODUCTION ------------ PowerIDE! 2.1 for DOS/Windows is a universal application interface and I/O manager developed by Future Domain that allows your application software to work seamlessly with most IDE (Integrated Drive Electronics) or Enhanced IDE hard disks and ATAPI compliant IDE peripherals such as CD-ROM and Tape drives. PowerIDE! features ATASPI, a full-featured DOS 16-bit and Windows 32-bit I/O Manager for IDE peripherals. PowerIDE! also contains several DOS CD-ROM utilities and a diagnostic program. Once PowerIDE! is installed, it operates in the background managing multiple input/output (I/O) calls from your applications software to any enhanced IDE peripheral including hard disk, CD-ROM and Tape drives. 1.1 PowerIDE! Block Diagram The following figure illustrates how PowerIDE! works together with your application software and peripherals: ------------------------ --------------- ------------- | Windows Applications | | ATAPI Tape | | ATASPI | ------------------------ | Application | | Driver or | | | --------------- | Application | | | | ------------- ================================= | | = | | = | | = -------------- ---------- = | | = | 32-bit | | CD-ROM | = | | = | Disk Access | | Driver | = | ----------- = | Driver | ---------- = | | = -------------- | ======================================== = | | | | = = | --------------------------------------- = = --------| DOS/Windows ATASPI Manager | PowerIDE! = = --------------------------------------- = = | = ======================================================================== | --------------------------------------------- | | | -------------- -------------- -------------- | Controller 0 | | Controller 1 | | Controller 2 | -------------- -------------- -------------- | | | ---------- ---------- ---------- | Drive #1 | | Drive #3 | | Drive #5 | ---------- ---------- ---------- ---------- ---------- ---------- | Drive #2 | | Drive #4 | | Drive #6 | ---------- ---------- ---------- 2.0 GETTING STARTED --------------- The following sections describe the minimum system requirements, the IDE controllers supported by PowerIDE! and how to install/uninstall PowerIDE!. 2.1 System Requirements To use PowerIDE! your system must meet the following requirements: * An IBM PC/AT or compatible machine with a 80386 or later processor * At least one of the following operating systems already installed: MS-DOS v5.0 or later PC-DOS v5.0 or later Microsoft Windows v3.0 or later Microsoft Windows for Workgroups v3.10 or later * For DOS users, your computer must have a minimum of 15 KBytes of free memory 2.2 IDE Controller Support Before installing PowerIDE!, the IDE controllers and peripherals must be properly installed in the system. PowerIDE! is designed to handle multiple IDE controllers, including those built into the system motherboard and/or the following Future Domain add-in controllers which may be installed in the system: * IDE-16000/16002/16003/16010 series of controllers (ISA-bus) * IDE-16020 controller with BIOS (ISA-bus) * IDE-16030 dual-channel controller with BIOS (ISA-bus) * IDE-32000 dual-channel controller with BIOS (VL-bus) Each channel of the IDE controller requires a unique I/O port address and Interrupt (IRQ) to work properly. The Primary channel (I/O port 1F0h, IRQ 14) is typically located on the system motherboard. The Secondary channel (I/O port 170h, IRQ 15) is typically provided by an add-in controller or it can be built into the system motherboard in newer PC models. Consult the installation guide that came with the IDE controller or the system User's Manual for configuration information. Each IDE channel can handle up to 2 peripherals with the first configured as the Master, and the second as the Slave. Consult the User's manual that came with the peripheral for configuration information. 2.3 Installing PowerIDE! Before running the PowerIDE! Setup program, make a backup copy of the PowerIDE! diskette. To install PowerIDE!, follow these steps: 1. Insert the PowerIDE! v2.1 diskette into drive A: or B:. 2. In DOS, type a:\setup or b:\setup depending on where your PowerIDE! diskette is located. If Setup detected that Windows is present you will be advised to exit the program and run Setup from Windows. In Windows, choose Run... from the File menu, type x:\setup where x: is the floppy drive letter for the PowerIDE! diskette. Click OK or press the key. 3. Choose the Install option and follow the instructions on the screen to complete the installation. 4. Remove the diskette and restart the computer to enable the changes Setup made to your configuration files. 2.4 Uninstalling PowerIDE! To uninstall the PowerIDE! drivers, follow these steps: 1. Insert the PowerIDE! v2.1 diskette into drive A: or B:. 2. In DOS, type a:\setup or b:\setup depending on where your PowerIDE! diskette is located. If Setup detected that Windows is present you will be advised to exit the program and run Setup from Windows. In Windows, choose Run... from the File menu, type x:\setup where x: is the floppy drive letter for the PowerIDE! diskette. Click OK or press the key. 3. Choose the Uninstall option and follow the instructions on the screen to complete the uninstall process. 4. Remove the diskette and restart the computer to enable the changes Setup made to your configuration files. 3.0 DRIVERS AND UTILITIES --------------------- The following sections describe the different drivers and utilities in PowerIDE!. The sections on the utilities is recommended reading for everyone while the sections describing the drivers are recommended only for more advanced users who prefer not to use the default support provided by PowerIDE! Setup. 3.1 Hard Disk Driver The driver FDATAHD.SYS is an ATASPI hard disk driver for DOS. It supports IDE hard disks through the ATASPI Manager, therefore the ATASPI manager must be loaded prior to loading FDATAHD.SYS. Hard disks previously partitioned and formatted by another controller via DOS' FDISK and FORMAT are automatically supported by this driver. Also, this driver will let you use DOS' FDISK command to create partitions and use the DOS FORMAT command to prepare the partition for file management. FDATAHD.SYS creates industry standard partitions that allow the hard disk to be used in other systems. Some third-party drivers create proprietary partitions which will not allow your disks to be used in other systems. The hard disk driver is loaded in the CONFIG.SYS file using the following syntax: DEVICE=[path]FDATAHD.SYS where path is the directory of the FDATAHD.SYS file. 3.2 32-bit Disk Access Driver The Windows 32-bit Disk Access driver (FDATA32B.386) is designed to take advantage of executing normal BIOS instructions in a 32-bit protected mode environment. This will improve performance for disk I/O intensive operations. This driver is designed to work with the Windows ATASPI Manager. It supports all hard disks supported by the Windows ATASPI Manager. The 32-bit Disk Access driver is loaded from the [386Enh] section of the SYSTEM.INI file using the following syntax which is not case sensitive: DEVICE=[path]FDATA32B.386 DEVICE=[path]FDINT13.386 where path is the directory of the FDATA32B.386 and FDINT13.386 files. The optional file FDINT13.386 is a Windows driver that replaces the Microsoft Windows' *int13 driver. This driver is mandatory if 32-bit disk access support for hard disks attached to a ROM-less controller is desired. 3.3 CD-ROM Driver The driver FDATACD.SYS is an ATASPI compliant IDE CD-ROM driver for DOS. It supports enhanced IDE CD-ROM drives which are also often referred as ATAPI compliant CD-ROM drives. ATAPI stands for ATA Packetized Interface, a specification defined by some of the leaders in the CD-ROM industry. The CD-ROM driver FDATACD.SYS must be loaded after the ATASPI manager in CONFIG.SYS. The CD-ROM driver supports the following CD-ROM modes: Data Audio Single Session Photo-CD Multiple Session Photo-CD CD-DA Digital Audio CD-XA (e.g. Karaoke CD) CD-I Video CD (e.g. Top Gun Movie) CD-I Digital Video (e.g. Bryan Adams Waking Up the Neighbours) Note that not all CD-ROM drives support all of the above modes. Refer to the CD-ROM drive's documentation for supported modes. The CD-ROM driver is loaded in the CONFIG.SYS file using the following driver line syntax which is not case sensitive: DEVICE=[path]FDATACD.SYS [/D: /T /C:,,] where path is the directory of the FDATACD.SYS file. The following explains the parameters used by FDATACD.SYS: /D: This parameter is used to assign a name to the CD-ROM driver. The default name used by FDATACD.SYS is FDCD0001. If this name is acceptable, there is no need to add the /D:FDCD0001 in the command line. If you want to use a different name, type the name after the : and make sure the name does not have more than eight (8) characters. Also, the driver name must match the name used in the CD-ROM extensions line in the AUTOEXEC.BAT file. Refer to the next section for more information about the CD-ROM extensions. For example, the following line assigns the name FDCDROM0 as the driver name for FDATACD.SYS: DEVICE=C:\PWRIDE!\FDATACD.SYS /D:FDCDROM0 /T This parameter forces the CD-ROM driver not to interface through the ATASPI manager but use its internal interface to the IDE controller. /C:,, This parameter is valid only if the /T parameter is used. This parameter informs the CD-ROM driver what IDE ports to support. The indicates the main I/O Port, indicates the interrupt level and indicates the port used as Alternate Status Register. Without the /C: parameter, the driver will look for support at the following port addresses: Port Address 1F0-1F7H, IRQ 14, Alternate Port 3F6H Port Address 170-177H, IRQ 15, Alternate Port 376H Port Address 170-177H, IRQ 10, Alternate Port 376H Port Address 160-167H, IRQ 10, Alternate Port 16EH Port Address 160-167H, IRQ 15, Alternate Port 16EH Port Address 150-157H, IRQ 11, Alternate Port 15EH For example, the following line supports the CD-ROM attached to the IDE port 160 using IRQ 10 and Alternate Status Register 16E: DEVICE=C:\PWRIDE!\FDATACD.SYS /T /C:160,10,16E 3.4 CD-ROM Extensions The CD-ROM extensions file is a software driver that allows your CD-ROM drive to be assigned a drive letter and be able to use file management commands under DOS and Windows. This file is required for proper CD-ROM drive support. PowerIDE! Setup will install this file if found during its installation process. PowerIDE! does not include the CD-ROM extensions file. The CD-ROM extensions file is originated by Microsoft and is shipped with MS-DOS v6.0 or later. The name of the file is MSCDEX.EXE. The following is the syntax of the MSCDEX.EXE line to be added in your AUTOEXEC.BAT file: [path]MSCDEX.EXE /D: /M: [/V /E] where path is the directory of the MSCDEX.EXE file. The following explains the parameters used by MSCDEX.EXE: /D: This parameter is used by MSCDEX.EXE to locate the device drivers it has to support. The string must match the /D: used in the CD-ROM device driver line in CONFIG.SYS. Refer to the previous section for more information about the CD-ROM driver. /M: This parameter determines the number of CD-ROM sectors to be used as buffers by MSCDEX.EXE. The default number used by PowerIDE! Setup is 10. /V This parameter asks MSCDEX.EXE to print more information about memory usage during its initialization. This option is not set by default. /E This parameter asks MSCDEX.EXE to use expanded memory if available. This option is not set by default. As an example, the following line asks MSCDEX.EXE to locate and support the driver with the name FDCDROM0, assign 10 sectors for buffers and use expanded memory if available: MSCDEX.EXE /D:FDCDROM0 /M:10 /E Corel Corporation also ships their version of the CD-ROM extensions file named CORELCDX.COM. The parameters listed above for MSCDEX.EXE are the same for CORELCDX.COM including some new ones. Contact Corel Corp. for more information. 3.5 Local Bus Configuration Utility If a Future Domain's Vesa Local Bus IDE-32000 VL controller is installed, a configuration utility named PWRCFG.EXE is available to change the controller's factory default settings to fit user's system configuration. It can alos be used to configure drives for optimal performance. PowerIDE! Setup copies this utility into your hard disk during installation. PWRCFG is a DOS utility. To start the configuration process, type the following from the DOS prompt: PWRCFG If Future Domain's IDE-32000 VL controller is found, PWRCFG would allow the user to either restore the controller to its factory default settings or make selective changes under Custom Configuration. The followings are the options available under Custom Configuration: Enable or Disable Display of Factory Default Message Enable or Disable Display of Floppy Controller Message VL Bus Speed VL Bus Width Configure Device 0 (Master) Configure Device 1 (Slave) Enable or Disable Second IDE Channel Configure Floppy Controller Serial Port Settings Parallel Port Address Parallel Port Mode For each fixed disk found, PWRCFG allows the selection of the device's operating PIO mode, the device's addressing mode and to enable or disable the Read/Write Multiple command support. For each the ATAPI device found, such as CDROM and tape, PWRCFG allows the selection of the device's operating PIO mode. 3.6 Diagnostic Utility PowerIDE! provides a DOS utility to exercise the different functional capabilities of your IDE peripherals. The PowerIDE! Diagnostic Utility PWRDIAG.EXE is used to execute basic commands to IDE hard disks and CD-ROM drives. PWRDIAG.EXE is an ATASPI utility which means it requires an ATASPI manager already loaded in order for it to detect IDE controllers and peripherals. PowerIDE! Setup copies this utility into your hard disk during installation. PWRDIAG is a DOS only utility. It must not be run in a multi-tasking environment such as Microsoft Windows. To start the diagnostic utility, change directory to where the PWRDIAG.EXE file is located and type the following from the DOS prompt: PWRDIAG When PWRDIAG starts, it first scans for all of the IDE controllers in the system. If more than one controller exists, they are displayed for you to select one. However, if only one controller exists, PWRDIAG will automatically select it for you. Next, PWRDIAG scans for all of the peripherals attached to the selected IDE controller. Again, if more than one peripheral exists, they are displayed for you to select one, but if only one peripheral exists, PWRDIAG will automatically select it for you. Once a peripheral is selected, information about the selected controller and peripheral is displayed on the screen. A menu of the available diagnostic commands is also displayed. For Hard Disks, the following diagnostic commands are available: - Identify Device - Execute Device Diagnostic - Read Test - Write Test - Verify Test - Seek Test - Recalibrate Device For CD-ROM Drives, the following diagnostic commands are available: - Identify Device - Execute Device Diagnostic - Inquiry - Test Unit Ready - Read CDROM Capacity - Read Test - Seek Test - Rezero Unit - Prevent Medium Removal - Allow Medium Removal - Start Unit - Stop Unit - Load Media - Unload Media (Eject) - Request Sense For more detailed information about each command, press the key when the command is highlighted. 3.7 CD-ROM Utilities The CD-ROM utilities are used to exercise basic functionality of an IDE CD-ROM. These utilities are designed to run only from the DOS prompt. If you are in Windows, exit first from Windows and run the utilities from the DOS prompt. PowerIDE! Setup copies these utilities into your hard disk during installation. The following describes how each of the CD-ROM utilities is used. 3.7.1 CD Eject Utility (FDEJECT.COM) The CD eject utility FDEJECT will eject the CD-ROM disc from the drive. If the drive door is locked, this utility unlocks the door before ejecting the disc. This utility is valid only for CD-ROM drives that support a software controlled eject. To run the utility, change directory to where the FDEJECT.COM file is located and type the following at the DOS prompt: FDEJECT [:] where the optional parameter is the drive letter of the CD-ROM drive that has the disc to eject. If is not specified, the utility will try to eject the disc from each of the supported CD-ROM drives. For example, typing the following line ejects the disc in drive E: FDEJECT E: 3.7.2 CD Lock Utility (FDLOCK.COM) The CD lock utility FDLOCK locks the door of the CD-ROM drive. On most drives, this disables the eject button on the CD-ROM drive. To run the utility, change directory to where the FDLOCK.COM file is located and type the following at the DOS prompt: FDLOCK [:] where the optional parameter is the drive letter of the CD-ROM drive to lock. If is not specified, the utility will try to lock all of the supported CD-ROM drives. For example, typing the following line locks drive E: FDLOCK E: 3.7.3 CD Unlock Utility (FDUNLOCK.COM) The CD unlock utility FDUNLOCK unlocks the door of the CD-ROM drive. On most drives, this enables the eject button on the CD-ROM drive. To run the utility, change directory to where the FDUNLOCK.COM file is located and type the following at the DOS prompt: FDUNLOCK [:] where the optional parameter is the drive letter of the CD-ROM drive to unlock. If is not specified, the utility will try to unlock all of the supported CD-ROM drives. For example, typing the following line unlocks drive E: FDUNLOCK E: 3.7.4 CD Audio Play Utility (FDAUDIO.COM) The CD audio play utility FDAUDIO is a TSR (Terminate and Stay Resident) program that plays CD audio disc under DOS. To run the utility, change directory to where the FDAUDIO.COM file is located and type the following at the DOS prompt: FDAUDIO Press the Alt, Ctrl and Shift keys simultaneously to display the CD Audio Panel. Refer to the file FDAUDIO.TXT for details on how to use the FDAUDIO utility. 4.0 ATASPI MANAGER -------------- An ATASPI (ATA Software Programming Interface) manager is a software driver that provides the interface between the ATASPI device drivers and the IDE hardware, i.e., controller and peripherals. An ATASPI manager can process multiple commands directed to the peripherals attached to the controller it supports. PowerIDE! provides the ATASPI manager for Future Domain's IDE-16xxx series and IDE-32000 controllers under both DOS and Windows. 4.1 DOS ATASPI Manager For the DOS operating system, the ATASPI manager ATASPI16.SYS is a loadable driver installed from the CONFIG.SYS file. The Setup program sets up this driver including appropriate command line parameters during the installation process. The following is the syntax of the line added by the Setup program and is not case sensitive: DEVICE=[path]ATASPI16.SYS [/C:[,,] ...][/V] where path is the directory of the ATASPI16.SYS file. The following explains the parameters used by ATASPI16.SYS: /C:[,,] By default, ATASPI16.SYS without any /C: command line parameters will scan for the following: IDE-32000 VL Controller ISA Port Address 1F0-1F7H, IRQ 14, Alternate Port 3F6H ISA Port Address 170-177H, IRQ 15, Alternate Port 376H ISA Port Address 160-167H, IRQ 10, Alternate Port 16EH ISA Port Address 150-157H, IRQ 11, Alternate Port 15EH To overwrite the ISA ports default, the ISA controllers' resources can be entered on the command line. The /C: parameter option is used to tell the driver what are the hardware resources used by the controller that it needs to communicate with. The is the I/O Port Base Address of the controller in hexadecimal convention. The is the interrupt request level used by the controller in decimal convention. The is the I/O Port Address for the alternate status register used in the ATA bus in hexadecimal convention. For simplicity, certain I/O Port Addresses are grouped with certain IRQ and alternate port address values. This allows the user to indicate the I/O Port Address and let ATASPI16.SYS deduce the appropriate IRQ and Alternate Status Port Address to be used. The following table lists the parameter to pass and the corresponding resources that ATASPI16.SYS uses: Command Line Parameter I/O Port Address IRQ Alternate Port ---------------------- ---------------- --- -------------- /C:150 150-157H 11 15EH /C:160 160-167H 10 16EH /C:170 170-177H 15 376H /C:1F0 1F0-1F7H 14 3F6H For some of the IDE-16xxx controllers, it is possible to have different combination of resources than the ones listed above. To support such combinations, all three parameters must be present, i.e., , and . For example, the following line tells the driver to support a controller set at I/O Port Address 160H, IRQ 15 and use the 16EH port as the alternate status register: DEVICE=C:\PWRIDE!\ATASPI16.SYS /C:160,15,16E /V This option tells the driver to output to the screen information about the controllers and devices. This option is set by default. 4.2 Windows ATASPI Manager For Microsoft Windows v3.0 or later versions, the ATASPI manager consists of two (2) Windows Virtual Device Drivers (VxD Drivers). The driver names are ATASPIXP.386 and ATASPI16.386. Both of these drivers must be loaded to provide ATASPI support under Windows. The Windows ATASPI Manager allows your ATASPI drivers and applications to run in 32-bit protected mode environment. This means faster execution and better performance for your drivers and applications. The PowerIDE! Setup program sets up these Windows drivers including required parameters during the installation process. The Windows created SYSTEM.INI file is modified to load the drivers the next time Windows is restarted. The following are the syntax of the lines added to the [386Enh] section of the SYSTEM.INI file: DEVICE=[path]ATASPIXP.386 DEVICE=[path]ATASPI16.386 ATASPI16=[/C:[,[,]] ...] PowerIDE!Options=[/V] where path is the directory of the ATASPIXP.386 and ATASPI16.386 files. The following explains the available optional parameters: /V This option is a broadcast parameter which means all PowerIDE! Windows drivers will receive the parameter. This parameter tells the driver to display information on the screen. If this parameter is not specified, no screen messages will appear. Setup does not set up this option by default. /C:[,,] If this option is present in the CONFIG.SYS file, the exact same parameters must appear beside the ATASPI16= line in the SYSTEM.INI. For more information on the meaning of this parameter refer to the previous section on DOS ATASPI Manager. 5.0 CUSTOMER SERVICE ---------------- The following sections provide troubleshooting tips, answers to frequently asked questions and information on how to contact Future Domain in the event you need help installing PowerIDE! or Future Domain IDE controllers: 5.1 Troubleshooting Tips PowerIDE! has been tested with virtually every IDE peripheral available. If you are experiencing any problems, here are a few things to look for before calling Customer Service: 1) If the system does not boot DOS, look for I/O conflicts (same I/O port or IRQ) between the add-in IDE controller and the motherboard. Refer to the User's Guide that came with the IDE controller to change jumper settings. 2) If the system does boot DOS but you can not access the IDE peripherals, look for conflicts (2 Masters/Slave) between the IDE peripherals. Most IDE hard disks are shipped as Master and CD-ROM as Slave. You must have only one Master and one Slave per channel to work. Refer to the User's Guide that came with the IDE peripheral to change jumper settings. 3) Use the PowerIDE! diagnostic utility (PWRDIAG.EXE) to determine the IDE controller and peripheral configuration. Refer to section 3.5 for information on how to run PWRDIAG. 5.2 Top 10 Questions & Answers The following are the most commonly asked questions and answers about PowerIDE! software and Enhanced IDE hardware. 1. What is Enhanced IDE? Enhanced Integrated Drive Electronics (IDE) offers new features including hard disk capacity greater than 528MB, a secondary IDE channel, performance up to 16MB/s (mode 4) and support for ATAPI compliant IDE CD-ROM and tape drives. 2. How many IDE peripherals can I connect to my Future Domain controller? For controllers with a single channel, up to 2 peripherals can be attached. Dual channel models can support up to 4 peripherals (2 per channel). 3. What is ATASPI? PC-AT Attachment Software Programming Interface (ATASPI) is a proposed industry standard software interface for management of IDE peripherals such as hard disk, CD-ROM and tape drives. The ATASPI I/O manager is at the heart of PowerIDE! software. 4. What is PowerIDE? Future Domain's universal application interface and I/O manager for IDE peripherals. PowerIDE! provides support for Enhanced IDE hard drives greater than 528MB, Windows 32-bit Disk and File access, ATAPI compliant CD-ROM, tape and multiple IDE channels. 5. Which IDE data transfer rates do Future Domain controllers support? The ISA-bus models support up to 3MB/s (mode 0), and the VL/PCI local bus models support up to 11MB/s (mode 3). 6. When do I need a Secondary channel in my PC? The Primary IDE channel (typically located on the system motherboard) supports up to 2 hard drives only. By adding a second IDE controller you can add ATAPI-compliant CD-ROM and Tape drives without impacting hard disk performance on your Primary channel. 7. Which system resources are used by the IDE controller? Standard Primary IDE channel on the motherboard uses I/O 1F0h, IRQ 14. The Secondary IDE channel uses I/O 170h, IRQ 15. Future Domain IDE controllers provide additional alternate channel support at I/O 160h, IRQ 10 (Default, except dual channel models) and I/O 150h, IRQ 11. 8. What is the recommended configuration for an enhanced IDE hard disk and a CD-ROM when installed on the same channel? The hard disk should be configured as the Master and the CD-ROM as the Slave. Refer to the peripheral users guide for more information on setting jumpers, etc. 9. Will all my CD-ROM application software work with the IDE CD-ROM? Yes, CD-ROM based application software is transparent to the IDE interface provided PowerIDE! has been installed. 10. Does Future Domain support 32-bit Disk and File access under Windows? Yes, support for Windows 32-bit Disk and Windows for Work Groups 32-bit File access for all IDE channels is included with PowerIDE! 5.3 Contacting Future Domain To help Future Domain Technical Support give you the best assistance possible, make sure you have: * The model of your computer and IDE peripherals. * The version of PowerIDE! you are using. * The version of the BIOS on your IDE controller, if present. * The name and version of the software application you were running when the problem occurred. * The information about what you were doing when the problem occurred. * The exact error messages and when they occurred. Have these items ready before you contact Future Domain's Customer Service department at: Future Domain Corporation Customer Service 2801 McGaw Avenue Irvine, CA 92714 Phone: (714) 253-0440 FAX: (714) 253-0429 Hours: Monday-Friday, 7 AM to 5 PM PST BBS: (714) 253-0432 MODEM: 14.4 Kbps, protocol:8,N,1 Hours: 24 hours, 7 days a week