LIGHTNING UK!

It would burn it if it's > 1GB and it's size is exactly divisible by 2048.

It was done like that on purpose actually. It's just supposed to be quick and easy - cdrwin style rather than Nero style - and most importantly, fit in the tiny space that available in the GUI! It's meant for building discs from an existing structure rather than making one up. People who need a nice gui to build their discs should stick to using Nero for now, ImgBurn isn't supposed to compete / replace it.

Wow, I'm really confused now! What's playing a dvd got to do with your bkf file?! (Nothing so far as I understand it!) My previous post just said that it looked like YOU'D burnt the bkf file in Write mode - and write mode is for burning disc images, which your bkf file is not. So if you want to burn it to disc, you need to add it as a normal file in 'Build' mode. lfc then said guides for using Build mode can be found in the Guides section. Even though they primarily aimed at burning DVD Video discs, the same basic principals apply.

lol you'd think the screenshot I posted would have turned on that little lightbulb above your head! If your screen doesn't look like mine, you're in the wrong mode.

By the sounds of it, you're also in one of the writing modes rather than the 'Read' mode. Of course if the disc you had in the drive was supposed to be blank and you were in one of the write modes on purpose, it would appear your drive doesn't support the media you're using.

Yeah sorry, that's still not making much sense! This is what I'm looking for, the info that highlighted in blue. If you start the program without a disc in the drive, the status bar will eventually read 'Not Ready (Medium Not Present)'. Once you put the disc in, it'll change to something else and eventually it should put something in that info panel on the right. It's the drive that has to do the reading, not really the program. As such, there's no reason why Nero should be able to report stuff about the disc and other programs not be able to.

You can't do this with ImgBurn. ImgBurn is just a burning tool. Have a go at searching Google, I'm sure you'll find something useful.

Don't get DVD Shrink to make a DL image, it doesn't do the layer break properly. If you're outputting at DL sizes, just output to a VIDEO_TS folder and use ImgBurn in Build mode.

Eject the disc from the drive, then load ImgBurn and ensure the correct drive is selected. THEN insert the disc. The message you're getting sounds like a windows one - or at least caused by windows. Doing it via this method will give ImgBurn more control. A screenshot might be useful.

If you just type in a folder name (i.e. C:\Windows), it brings up this message box. --------------------------- ImgBurn --------------------------- 'Destination' should contain a fully qualified file name. At the moment it just contains a folder name. For Example: Incorrect: 'C:\' Correct: 'C:\Image.iso' --------------------------- OK ---------------------------

I just tried it having set the 'Destination' to 'C:\test' and then hit the build button. The program automatically added '.iso' for me, making it 'C:\test.iso'. I really have no idea where you're going wrong!

Get me a screenshot of what you're doing. This is the guide you should follow btw: http://forum.imgburn.com/index.php?showtopic=1778

Seriously, can't you just follow the Guide?! Look at the screenshots and you'll see where yours looks different.

Well it's hard to tell where you're going wrong because you're not really giving us much info. When in Build mode, have you change 'Output' to 'Image File' rather than 'Device' ?

There are guides in the Guides forum for building an ISO from files (inc VIDEO_TS stuff).

When you put the disc in, what does ImgBurn say on the right in the info panel? Personally I wouldn't copy that as is, I'd get the files off it and burn it again as a single track / session disc. You'll find it much more 'compatible' that way.

Closing a disc doesn't mean you can't then erase it. Erasing should always be possible, no matter what you do / don't do to it.

If it was built properly in the first place, you could have probably just loaded the ISO and it would have found some potential layer break positions.

Oh, did you just burn it in write mode? As it's not meant for burning as an ISO, you'd need to use Build mode.

Check for a firmware update for the drive and stop using Ritek media. Get Verbatim (MCC dye) or Taiyo Yuden discs instead.

Suspect or not, it's like buying a new plant for the garden and then complaining your microwave has broken down. Uninstalling ImgBurn = deleting the exe! There's no way on earth it could be interfering with your hardware or ability to burn.

This is by design. When left blank in the GUI, it uses my defaults (or what the specs say the fields should contain). So you can't ever leave these fields blank but you CAN change them to something else if you really need to. For 99.999999% of people, 99.99999% of the time, there's never a reason to do that. As for the command line stuff, at the end of the day, it's a GUI program! I've added *some* cli options because I'm nice like that. I've no intention of adding support for everything.

ImgBurn is JUST an exe file. There are no DLLs so there's no chance it could break anything else. There's also no way 2.2.0.0 is the cause of your problems. I'm sure that between us (myself and the beta team), we'd easily done a few hundred before 2.2.0.0 was even release to the world. If there was a problem, we'd have spotted it. Software actually plays a very small part in the burning phase, it simply supplies the drive with data. It has no control over burn quality etc so if you get errors when reading the disc back, you can ONLY blame the hardware / media.

There's no means of translating it besides editing the exe directly in a resource hacker type of program.

Isn't it funny how we often can't see what's right infront of us!