sorry, nie gehöhrt. in welchem zusammenhang denn?

In the early days of CD-ROM, every manufacturer had his own interface and connections to the host. Standard interfaces, ASPI and CAM (which will operate ASPI devices and is functionally equivalent for Windows platforms) were devised and manufacturers of SCSI devices either conformed or wandered out of the market. The situation with IDE devices was similar, but the standard that was developed for them (ATAPI) made them look to the system like SCSI and allowed them to work through ASPI. For that reason, your computer's IDE adapter and devices may show up under the SCSI controls. More information on SCSI and drivers can be found at
http://www.europa.com/~diogenes/DSMFDSM/#CAMT
http://www.lionsgate.com/Home/Baden/publ…SI/SCSIgame.txt

The ASPI Layer is a collection of programs to realize the ASPI interface. Those DLLs work together and must be consistent and complete to avoid problems in communicating and interpreting commands. Some vendors package a subset of the DLLs with their products - scanners are notorious for this.Often, they will grab an old file (one that's good enough for their needs) and package that with their own software - but with the then-current date. It will then install even though a later version is on your system and it will not be removed readily, again because the date is misleading. (Okay, it's a lie!)

Note that there is an approach to interfacing the components via miniport drivers which does not require the ASPI layer; there is none in Windows 2000, for example. In general, CD-R gets along fine without an ASPI layer if the code is written appropriately for Win2K. However, code which is not fully Win2K-compliant may use an ASPI layer instead. That can work - if the layer is complete and consistent. Many support programs do rely on the ASPI layer, so one is needed for them even if not for programs such as Easy CD Creator 4.02 and above.

ASPICHK from http://www.adaptec.com will analyze your system and report the consistency and version numbers of your ASPI components. If it reports a problem, you may try Adaptec's repair program - but that runs into the date problem and may not resolve inconsistency. At this writing, the latest ASPI layer (1021) appears to be solid. However, it is subject to corruption if some device is installed which replaces parts of the package.

The variety of CD-R failures due to a faulty ASPI layer is remarkable and defies detailing. Any repeating error message dealing with communications to or from your writer should trigger a verification with ASPICHK. It sometimes appears that programs that really do not need the ASPI routines install them (badly) just to be sure. With ASPICHK and the Adaptec files, ensuring a working ASPI layer is painless. To steal from an American commercial: Just do it!