I followed your step- by- step and the froze the cdrkit- based packages. All the bugs and problems promptly went away. This has been an interesting debugging journey. The cdrkit tools (wodim, et al) on Hardy have bugs that don't show up until later and, in my case, if I hadn't had an XP system to test on, would have resulted in a huge waste of time, energy, money, and good will. And, the bugs have been known for quite some time and have not been addressed in Hardy. I don't trust cdrkit any more. I understand that there are strong personalities involved and licensing subtleties that matter to distribution support.
Legacy-homebrew - :skull: The former home of :beer: the missing package manager for OS X. The first time you install cdrtools, the link step. Installing XO Wave on Mac OS X and Linux. Installation: Mac OS X. However, for my personal use, I just really couldn't care less about any of that. Bottom line, I need for the tools to work reliably; cdrkit doesn't, cdrtools does. If there are licensing issues, well, that's what the ? What about the poor Windows user trying out Ubuntu for the first time? There's absolutely no excuse for not packaging cdrtools and making them available in an alternative repository. The average user should have a choice. Cdrtools with SPTI (Win. Diese Seite auf Deutsch. What is it? Windows NT/2. XP comes without installed ASPI, so it must be installed individually. Adaptec ASPI). But under this OS, there is another access- method. SPTI (SCSI Pass- Through Interface). In meantime this is used by many burning applications and preferred by Microsoft. AKRip here essentially emulates the ASPI functionality. Advantages: Cdrtools run without ASPI installation. Alternative accessability, also with installed ASPI. Possibly devices are supported, which are not recogniced by ASPI but available under Windows. Device can be opend non SHARED, then simultaneous access (and disturbance) by other programs is not possible. Disadvantages: Administrator privileges necessary, can possibly be worked around, see EAC- FAQ (Q: I use Windows NT/2. EAC seems to have problems to store the options or get any SCSI response)AFAIK, some functions are not possible, but are not not necessarily needed by Cdrtools, though implemented in. SC. If anybody knows, how to implement it, please tell me. BTW: This ASPI- FAQ says, these functions do not work also with Adaptec ASPI, my test with ASPI 4. There may exist devices (respectively drivers), which only work with ASPI, not SPTI. Function. SPTI is running under Windows NT/2. XP, not 9. 5/9. 8/ME. If working ASPI is detected (wnaspi. Otherwise SPTI is used automatically. SPTI can be forced by preceding the string . Get the Cdrtools source code, use the. The patch modifies libscg/scsi- wnt. All versions of. cdrtools- 2. New: From cdrtools- 2. Therefore it should be tested first on computers, where. ASPI is present. To be very careful you can also compare with Cdrtools without this extension, finally there could. ASPI code, although the changes are minimal here. If malfunctions occur, the two access. If you see the errors with ASPI and SPTI, then it is probably not because of SPTI. If errors occur. only with SPTI, re- run under both access methods and create a log file with program option . Further on, independently from my extension. I recommend to apply a patch to cdda.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2016
Categories |