Intelman píše:
Tak to sem zkopíruj.
ako povieš šéfe!
SCSI/IDE Command aborted
If the error message SCSI/IDE Command aborted occurs:
• Please check if there is a program accessing the burner. Please deactivate the option switch off the automatic to be deactivated for the drives. In particular if the error message only occurs actually during the burning process and not during the simulation.
• If it is a case of a SCSI device, then please check the settings in the SCSI-BIOS . In particular Sync Negotiation should be set to yes .
• If you use SCSI devices and a relatively large number of devices are connected to the SCSI-Bus, then you should please check if the SCSI-Bus may be overloaded and whether this can be solved by setting the maximum data transfer rate and by updating theWinASPI drivers.
• If you are using an Adaptec SCSI hostadapter, the newest WinASPI drivers should be installed.
• Please check if drivers of other CD burner programs should be loaded and if necessary deactivate these. (For example, if more than 78 minutes is to be burned, the above mentioned error message appears)
The SCSI Command Aborted error message is a generic error message that applies to recorders connected via IDE, SCSI, USB, and Firewire.
This is a holdover from the very first recorders that were all SCSI, and it's from the MMC command set, not Nero. So this error message does not mean that Nero is only issuing SCSI Commands.
As to the cause of this issue, there are a number of possible causes, and it's usually a tough nut to crack.
I've seen this caused by:
1) Old drivers for the IDE controller, or new ones that are not properly working with the controller
2) Old versions of the CD recording software
3) Old firmware on the recorder
4) Media that will not support the high write speeds selected (at least not with that model recorder)
5) Conflicts with other CD Recording software, which is currently or was once installed on the system. Changes to the Registry from these other recording programs is the normal cause and only cleaning the registry after removing the software will resolve the issue. Which is why a number of times a fresh install is reported to have resolved a customers issue.
We use our own ASPI driver. To see if this is the issue, you can go to the C:\Program Files\Ahead\Nero folder and look for the WNASPI32.DLL file and rename it to WNASPI32.BAK and then reboot.
This will cause our software to default to the systems ASPI driver. And see if this resolves your issue. If it does, then we need to take a close look as our ASPI driver.
