Jump to content

UDF only build fails at cycle tray point


Edwin+

Recommended Posts

Hi everyone,

 

First of all, I'd like to say what a great application ImgBurn is. I used to use a Mac and was dependent on Toast, when I came to the PC it felt like everyone was using Nero and I hated it as well as all the problems it gave me. ImgBurn is sooo much better, I donated to the developer. Having said that I have come across a problem. I primarily build data CDs and DVDs, these are backups that I'll only use myself so compatibility with anyone else is not a requirement.

 

I spent several hours today trying to burn a DVD of a large directory. The directory has 13 sub directory levels and ISSO9660 complains its beyond the 8 level limit so I switched the file system to UDF only. I tried versions 1.5 and 2.01 which are supposed to be Windows XP compliant but both builds fail at the point at which burning has completed and verification begins with the message:

All attempts to automatically close the drive tray have failed. Please close it manually and then click OK to continue.

The tray opens and closes fine of course. This loops for the standard 3 attempts until a "media not recognized" message is displayed in ImgBurn. It seems like the UDF only format isn't being recognized by ImgBurn or Windows?

 

In the end I went into the Advanced > Restrictions > ISO9660 tab and enabled allow more than 8 levels then burnt a DVD with both UDF and ISO9660 as the file system, it worked twice in a row. However when XP displays the disk in Explorer it displays the UDF name I gave it, not the ISO9660 name. It's as though UDF won't work unless ISO9660 is there as well? I went back and tested a couple of DVDs I'd burnt earlier with UDF only file systems that had verified fine at the time and had problems getting Windows XP to reliably recognize them, on one occasion they mounted fine then later they refused to be recognized.

 

Is this a known Windows XP problem? It feels like a Windows issue and not ImgBurn, surprise. Hope someone can help.

Link to comment
Share on other sites

Thanks for the quick feedback, I've been at work today and just picked up your replies. It sounds like you think the media might be unreliable, I read your FAQ and my Media ID says Manufacturer ID: CMC MAG. AE1. If you think its worth it I'll order some new media from SVP with one of your recommended Media IDs?

 

I've included the log of one of the failed burns below, its from the earlier version of ImgBurn, I subsequently downloaded the latest ImgBurn and reattempted but with no difference. Thanks for the support, much appreciated. These are critical backups and I always produce two of each, I don't want to risk burning anything that will be unreliable in the future.

 

; //****************************************\\

; ImgBurn Version 2.3.2.0 - Log

; 日曜日, 10 8月 2008, 17:53:19

; \\****************************************//

;

;

I 16:31:08 ImgBurn Version 2.3.2.0 started!

I 16:31:08 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 16:31:08 Total Physical Memory: 2,094,732 KB - Available: 1,305,412 KB

I 16:31:08 Initialising SPTI...

I 16:31:08 Searching for SCSI / ATAPI devices...

I 16:31:08 Found 1 DVD-ROM and 1 DVD

Link to comment
Share on other sites

Apologies for the second reply but I just did a test. I burnt a test DVD of just 50 MB or so in UDF 2.01 only and it worked fine. I then burnt the same content again but added 11 or so nested levels of directories, each directory containing just a single text file and sub directory. This time it failed, I've posted the logs below. It looks like the UDF option is failing each time it has to deal with a high number of sub directories (8+)? If I'm correct you should be able to reproduce this problem yourself.

 

I 20:03:12 ImgBurn Version 2.4.2.0 started!

I 20:03:12 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 20:03:12 Total Physical Memory: 2,094,732 KB - Available: 1,534,656 KB

I 20:03:12 Initialising SPTI...

I 20:03:12 Searching for SCSI / ATAPI devices...

I 20:03:12 Found 1 DVD-ROM and 1 DVD

Link to comment
Share on other sites

I 20:55:04 Destination Media Type: DVD-R (Disc ID: CMC MAG. AE1) (Speeds: 4x, 6x, 8x, 12x)

That media is very low quality, and that's why some discs work and others don't. It's not related to the UDF filesystem at all. Try burning one at 4x (maybe 6x/8x) and it might work, but I wouldn't trust that media with any data I couldn't lose.

 

For reliable media use Verbatim or Taiyo Yuden blanks :thumbup:

Link to comment
Share on other sites

  • 1 month later...

Sorry its been such a long delay since I last posted, I've been snowed under with work. I haven't had time to conclusively repeat the same tests above but I did a ISO + Joliet format burn the other week of the same content. It failed first time with my old media, I swapped in the new media you recommended and it worked. I'll try a UDF format burn next time and post back the results.

Link to comment
Share on other sites

  • 2 weeks later...

OK, I can conclusively confirm it was a media problem. I just did a number of burns with the same media in UDF only format at full speed and didn't get a single glitch. I had no idea media was so important. I won't make the same mistake again. Thanks for the help and the great application.

Link to comment
Share on other sites

Thanks for the feedback Edwin but you are preaching to the converted/telling us something we already know. CMC discs are totally worthless junk. Use them as frisbees for the kids but do not ever attempt to write valuable data to them.

 

Regards

Link to comment
Share on other sites

Ha ha, understood. OK thanks :lol: . But remember most people are not as well informed as you on this subject so if they find this thread it will help them to know it was a media problem. I was talking to a friend of mine the other day and he had no idea either that good media makes such a difference. But cheers anyway.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.