Jump to content

ImgBurn Support Forum uses cookies. Read the Privacy Policy for more info. To remove this message, please click the button to the right:    I accept the use of cookies

Photo

I/O Error on MATSHITA drive - possible solution


Forum Rules

Read the Guides forum if you don't know how to do something. :readbook:
If you have a question or a problem, check the FAQ and use the Search to see if you can find the answer for yourself. :lightbulb:
If you're having trouble burning double layer media, read Here.
Still stuck? Create a new thread and describe your issue in detail.
Make sure you include a copy of the program's log in your post. No log = :chair:


  • Please log in to reply
1 reply to this topic

#1 gdiddy

gdiddy

    ISF Newbie

  • New Members
  • Pip
  • 1 posts

Posted 08 June 2017 - 12:45 AM

Hi Folks,

 

First post here and the usual ... blah blah ... sorry if it's in the wrong spot but ... 

 

Have been using this fantastic program for many years now - in the process I have stuffed a lot of disks but hey - you get that. 

 

Anyways - so I had issues trying to Write Bodhi Linux to a CD-R this morning with the same sort of error as seen here:

 

http://forum.imgburn.com/index.php?/topic/24602-power-calibration-error-and-io-error/

 

My drive is also a MATSHITA (alternatively MATS%#TA) but model BD-CMB UJ141ES.

 

I understand that write speed settings, quality of disk and a dirty laser can often be the cause of troubles when errors occur, however, for anyone using a MATSHITA in particular (and possibly others) the following may be worth a try.

 

At first I had the Write Speed setting on MAX (in the dropdown selector).

 

What fixed the issue here was setting it to AWS which I would assume is Automatic Write Speed with (MAX) still appearing to the right of the selector.

 

Now why this would make any difference whatsoever is beyond me but after the change the .iso was burnt to the same disk without issue.

 

I will mention that I am using Windows 10 on this particular machine, ImgBurn Version 2.5.8.0 and was only running one other operation at the time being a Recycle Bin permanent delete/erase from HD using Eraser.

 

So was it all coincidence? Possibly ... but it may be worth a shot along with the other usual culprits causing problems.

 

Hoping this might be of assistance to someone - Good Luck! :) 

 

 



#2 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,277 posts
  • Gender:Male
  • Location:United Kingdom

Posted 08 June 2017 - 06:00 AM

Yup, coincidence.

AWS is the feature whereby you configure different speeds for different discs based on disc type and MID.

The value shown in brackets is the speed at which the program will be using based on how you've configured the AWS feature (or in your case, not configured it).

So both times, you've burnt at 'MAX' speed.
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users