Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Burrrn Troubleshooting (Read 8989 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Burrrn Troubleshooting

I've been trying to burn FLAC files (I've tried other formats with the same result) with Burrrn and get the following result:

Finished processing file #1.
Initializing ASPI ... OK!
ASPILOCK:1,0,0: MATSHITA DVD-RAM UJ-820S        Rev: 1.00
ASPILOCK:1,0,0: MATSHITA DVD-RAM UJ-820S        Rev: 1.00
Starting write
Starting write at speed 16...
Starting write at speed 16...
Turning BURN-Proof on
Turning BURN-Proof on
ERROR: Cannot set write parameters mode page.
Turning BURN-Proof on
Executing power calibration...
?: Input/Output error.  : scsi sendcmd: retryable error
CDB:  54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.003s timeout 180s
ERROR: Power calibration failed.
ERROR: Use option --force to ignore this error.
ERROR: Writing failed.

I cannot burn any audio from Mediamonkey, Mediaplayer, etc. DVD burning has been no problem in the past but I haven't tried recently

Any ideas as to how to fix this problem? I thought it might be a driver issue or a scsi/aspi issue, but I am not sure. I've used other programs to burn cue/flac/ape and get similar results. Thanks in advance.

Burrrn Troubleshooting

Reply #1 –
I got a similar error, I just unistalled and reinstalled again. Then it worked fine

Burrrn Troubleshooting

Reply #4 –
Try uninstalling the drive via device manager and rebooting and let Windows redetect the drive.
"You can fight without ever winning, but never win without a fight."  Neil Peart  'Resist'

Burrrn Troubleshooting

Reply #5 –
maybe give imgburn a shot?

Burrrn Troubleshooting

Reply #6 –
Quote from: 123004 on
Any ideas as to how to fix this problem? I thought it might be a driver issue or a scsi/aspi issue, but I am not sure.

Maybe try the Raw Driver in the drive settings of Burrrn.