 |
Daniel Cohen
Guest
|
 Posted: Mon Jul 02, 2007 9:48 am Post subject: Pioneer 112D won't burn |
 |
|
I recently bought an external Pioneer 112D from Other World Computing. I chose them partly because the firewire chipset was the Oxford 912 and also because they were one of the few dealers who would accept a British billing address with a US shipping address.
ALL my attempts to burn with Firewire have failed, though the one burn I tried using USB worked.
This happened with various burning programs and various ways of hooking up the drive, as the middle of a daisy-chain, as the end of a daisy-chain (with an external hard drive as the other item in both cases) and as the only item connected.
Using Toast and burning at 4x, the burn failedwith DVDs in data mode, DVDs in copy mode (from a disk image), andwith CDs in audio mode. In the latter, even using simulation rather than an actual burn gave a failure (unfortunately, I had forgotten about simulation, and made several coasters).
Using Disk Utility, and also a program called Burn, failed when burning data. This is not so surprising as I believe they use maximum speed.
Burning an audio CD using a program with a GUI to cdrdao at 4x also failed. I got an error message here suggesting a buffer under-run.
And, from Disk Utility trying to burn files to a CD, there wasa log that said
Disk Utility: Burn started, Tue Jun 12 11:04:13 2007 Disk Utility: Burning to CD-R media with SAO strategy in PIONEER DVD-RW DVR-112D 1.15 with generic profile via FireWire. Disk Utility: Requested burn speed was max, actual burn speed is 40x. Disk Utility: Burn underrun protection is supported, and enabled. Disk Utility: DVD-RW DVR-112D: SCSITask 8664.583008 CDB: Write (10), block: 34432, count: 32 failed with service response = 1 (SERVICE_DELIVERY_OR_TARGET_FAILURE), status = 2 (ProtocolTimeoutOccurred)
Disk Utility: Retry #1
Disk Utility: DVD-RW DVR-112D: SCSITask 8681.083008 CDB: Read Buffer Capacity failed with service response = 1
(SERVICE_DELIVERY_OR_TARGET_FAILURE), status = 2 (ProtocolTimeoutOccurred)
with the last line repeated many times (with slightly different SCSI Task numbers).
So what is happening? I can think of a number of possible causes.
1. Poor quality media. But would bad media cause problems with Toast when it is only simulating?
2. Poor quality firewire cable.
Both the media (which is unbranded) and the cable were supplied by Other World Computing. This means that I have no idea of their quality, but I would not expect them to supply items that don't work well with their drive.
3. A faulty drive. But would a USB burn be successful if the drive were faulty?
Obviously we need to test the drive with another Mac. Unfortunately, my friend knows only one other Mac user, and it isn't very convenient to get to him.
4. A fundamental incompatibity with the computer. It is running OS 10.4.9, which has just had a clean re-install. But the computer itself is an ancient second-hand PowerBook G4 Titanium, so I wonder if there could be issues with its firewire port.
The system belongs to a friend, who has used Macs for a fair length of time, but is not likely to have any idea of how to check for problems and their solutions. I was visiting her, but am now back at home, so I can't do much myself except advise her. |
|
| |
|
|
|
|
