(New thread per JimH's request)
Digital-secure ripping woes remain. Although a configuration problem is still possible, I think a bug is more-likely for these reasons:
- MJ 7 worked on the problem drive
- EAC works now on the problem drive
- MJ 8 works on a 2nd (temp) drive now
- MJ 8 can be made to work often on the problem
drive by a weird combination of options/actions
SUMMARY
-------
1. Digital-secure worked fine with MJ 7.2 (drive is Dell-supplied Lite-On LTN486 48x Max).
2. Under MJ 8 (every build since I started with 8.0.265), digital-secure fails almost always; Message is: "failed to read sector _; Incorrect Function". Drive is set to IDE (it's on my secondary IDE channel), which is also what it's set to if I use auto-config.
3. Ripping works in modes other than digital-secure, but they are not reliable (e.g., comparing with EAC) so my practice is to use digital-secure always (I use APE exclusively and want every bit right).
4. Digital-secure DOES work, albeit extremely slowly, if I simultaneously play a track from the same CD; not practical, but cool and an important piece of data.
5. If I set the drive to ASPI, digital-secure works much of the time (but not always).
6. I just installed a new LITE-ON LTR-32123S drive (not permanent; borrowed from another system). Digital secure works fine.
7. EAC works fine with the problem drive.
8. System details (from MJ->SystemInfo):
Media Jukebox PLUS 8.0.284
Install Path: C:\Program Files\J River\Media Jukebox\
CPU: Intel Pentium 4 1893 MHz MMX
Memory: Total - 1047 MB, Free - 712 MB
OS: Microsoft Windows XP Workstation 5.1 (Build 2600)
Internet Explorer: 6.0.2600.0000
ComCtl32.dll: 6.00.2600.0000
Shlwapi.dll: 6.00.2600.0000
Shell32.dll: 6.00.2600.0000
wnaspi32.dll: 4.60 (1021) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1999 Adaptec, Inc.
Aspi32.sys: 4.60 (1021)
DISCUSSION
----------
Cotton-Eyed|PLS|Loo suggested recently that the problem might be with the ASPI layer, and that I might want to try Adaptec. However, the two aspi dlls cited above are from Adaptec. Furthermore, I don't know enough to safely fool with the ASPI layer. Finally, I don't understand in what way the ASPI layer is relevant. Given that this is an IDE drive, and given that auto-config yields IDE, isn't setting the drive to ASPI the wrong thing to do?
Given items 4, 6, and 7 above, it seems unlikely that this is a configuration issue (but still possible, of course).
Item 4 above seems to me to be a major clue to what's going on.
js