This file is compiled from responses of CdSpeed users. Thanks to them... 1) There may be some conflicts with some "Intel IDE busmaster" drivers. Versions 3.0+ lock your system. BMIDE version 2.85 is working. This was detected on the system like: AMD K6 166 (old system) HX chipset board with 64 Mb RAM controller 0 - (SCSI - HDD's only) controller 1 - IDE Primary (busmaster driver enabled for HDD) device 0 - Fujitsu 5.2 Gb HDD (detected by CDSPEED) device 1 - GoldStar 8240B 24x (not detected by CDSPEED) controller 2 - IDE Secondary (standard Windows'95 driver [ESDI506.PDR]) device 0 - GoldStar 8240B 24x (detected by CDSPEED) device 1 - (no device) 2) The program doesn't work with Adaptec AIC-7895. Got a Pioneer DR-U16 cdrom and a Plextor Plexwriter 4/12 connected and program just reports: ERROR occured while executing SCSI command No. 0x2... SCSI command has completed with an error. Got WinNt4 sp5 and latest Adaptec WinAspi (logged on 1999-09-17). 3) The program doesn't set the speed correctly or somehow the CDROM speed is changed (without cdspeed use). May be next text helps you find out what is the problem in. In ATAPI CD-ROM Specification is written that "SET CD SPEED Command" implementation is optional. So, when one has ATAPI CD-ROM it does not mean it supports "SET CD SPEED Command". One argument of the command is called "Drive Speed" (clearly). The Specs says about this that the Drive Speed parameter contains the requested Data Rate the drive should use; the drive may choose to select the speed specified or any slower rate. Well, when cdSpeed writes e.g. "Speed should be set to 706 KB/s", this only means that "SET CD SPEED Command" finished without any error. This and the text from ATAPI Specs are the reason I used "should be" and not "is". If you want to know what actual speed was set by your drive always use get statement immediately after the set one (e.g. "cdspeed 0 1 0 sg x4"). Now you know that the drive is not due to use exactly the speed you specify in "SET CD SPEED Command" or it can even reject the command. May be you would like to find first what speeds your drive is able to use (launch cdspeed more times with various speeds and look what the get command returns). For example my drive "TOSHIBA CD-ROM XM-6202B Rev 1110 11/20/97" knows only these speeds: 176; 706 and 5645 KB/s. 4) Could you clarify the installation instructions as I do not understand "it requires ASPI installed". ASPI is programming API for SCSI devices (by adaptec???). It is important to install it only if you use cdspeed under WinNT4.0. Well, you need ASPI drivers to install, but the problem is you must not install the latest version from adaptec (which installs only when you have an adaptec controller). The latest version does not support IDE drives (and this is the actual reason you cannot use it). It is possible to download the drives somewhere from web (sorry I don't know exact URL). Remember you need the drives ONLY when using cdspeed under WinNT4.0. You don't neeed the drives when you are using cdspeed under Win95/98. 5) I encountered error like this one: ERROR occurred while executing SCSI command No. 0x2... SCSI command has completed with an error. Target Error No: 0x2 HEX DUMP OF SENSE DATA FOLLOWS: 70 00 06 00 00 00 00 0a 00 00 00 00 28 00 00 00 00 00 HEX DUMP END > some problem detected in SetCdSpeed() What should I do and what does it mean? First don’t mind program reports something about SCSI commands and you have only ATAPI (IDE) CDROM drive. There is a way to send SCSI commands to ATAPI drives. "Target Error No: 0x2" means that SCSI command has been aborted. Typically aborted commands can be reissued later ... and they often success when tried later. From "HEX DUMP OF SENSE DATA FOLLOWS" I know that your drive was not ready due to media change or reset (error code 0x06), when you tried to change its speed. From error code 0x28 I know that this happened due to media change in the drive and not a reset. All error codes can be found in ATAPI specification.