LIGHTNING UK!

Besides the log, I'd also like you to copy + paste the info from the panel on the right of the main screen when you've got one of these problem blank CD's in the drive.

When you add a single folder to the source list, ImgBurn will prompt you and ask if that folder represents what should be the root of the disc. So just say 'Yes'. Then all you'll have on the disc is the 'Pictures' and 'VIDEO_TS' folder... the 'MY_DVD' one won't actually be on there (just everything that lives within it).

Make a folder structure like this... [some random folder path]\MY_DVD - (JPG files go in here) [some random folder path]\MY_DVD\VIDEO_TS - (IFO/BUP/VOB files go in here) or [some random folder path]\MY_DVD\Pictures - (JPG files go in here) [some random folder path]\MY_DVD\VIDEO_TS - (IFO/BUP/VOB files go in here) Then add the '[some random folder path]\MY_DVD' folder to the source list in Build mode.

The real BenQ firmwares support loads of extra stuff that the philips one probably doesn't. For instance, you can now use the 'book type' / 'advanced settings' features. They're located in the Tools -> Drive menu.

A font manager?

lol keep splitting cells until you find one that works! The next version does make it a bit easier as it points you in the right direction as to which cell you should split. All I'd do at the moment is look at the entire VIDEO_TS folder and find the midway point - size wise - as a file. Then figure out where that point is in terms of positioning within the VTS set. Then just split some of the cells around that point.

I believe the functionality you're talking about is only possible with packet writing software or on formatted DVD-RAM. ImgBurn doesn't let you delete anything from a disc. Once you've burnt something, it's burnt forever and the disc is closed/finalised. You cannot turn off finalising, the option in the settings is for something else to do with finalising. I would actually advise you to NOT use DVD+RW as if it's a big floppy disc, use a memory stick or DVD-RAM disc instead.

look very closely at the path + name of the file it's opening, it wouldn't be saying it can't open a file unless it really can't! If you could get us a screenshot of the error that might help. OR press CTRL+C (copy) when the error box is on the screen (and active) and then CTRL+V (paste) into your next reply.

You'll probably need to follow chewy's link above and convert to a BenQ 1620. Then you can use ImgBurn to make it booktype to DVD-ROM via the 'Book' icon down the bottom right of the main screen (in build mode it's on the 'Device' tab).

All you can do is try some decent MCC or YUDEN DVD+R discs and booktype to DVD-ROM. You might find they work better.

Do you have a note of the exact error it pops up?

Well then it's pretty simple. Just copy the contents from both dvds into a folder and make a new image from that folder. No idea if it'll actually work though - that's a chance you take. Also, some of the files might want to overwrite each other.

Seagull, please create your own thread and when you do so, post a log of a failed burn so we can see what's going on.

FYI, I've now added a fallback whereby if the 'Disc ID' isn't found in the list (and it's therefore about to default to 'MAX'), it'll go through each item and compare it to the drive name. So where before you could add things like: TYG02, 8x TYG03, 12x DVD+R, 8x DVD-R, 8x You can now extend that to include PLEXTOR DVDR PX-760A, 4x PIONEER DVD-RW DVR-212, 8x Then, as you can see, the AWS feature knows that you want to burn at 8x whenever the Pioneer drive is selected and the media you're using is not defined in the list.

You've got hard drive problems - or whatever drive E: is that you're trying to read from.

What model standalone do you have?

Yeah but it'll get set to non-seamless regardless of it's current setting (unless the seamless option is ticked).

You can make a layer break in that ISO (if you could, it would have worked straight off). You need to strip it back down so you just have the files and then build a new one in 'Build' mode. The easiest way to do that is to mount the existing ISO in DAEMON Tools and then point Build mode at the virtual drive.

The preview window should help to pinpoint the best place... hopefully you've figured out how best to use it? It displays 2 cells (unless you're previewing cell 1) and so when you see the 'Cell' marker go from one to the other, you know that's where the layer break is gonna be. Cell '1' will be the last cell on the 1st layer, Cell '2' will be the first cell on the 2nd layer (i.e. after the slight pause). So yeah, you want to pick a Cell where if you step back a frame from the start (first) frame of Cell '2', it's totally different. (a different angle / scene)

I reeeeaaaally wanted to release it this weekend but I was so busy with other stuff last week that I've only just been able to pass out (what I hope will be) the final beta (after some pretty big changes were made to one of the new features). So it needs another week of testing and then fingers crossed it'll be good to go

Wow, 'DH20A3H YP5S' gets 1 result in Google and this page is it! lol I'm not aware that setting the LB position is something I have to 'wait' for before then checking it again - certainly it's not something I've come across before with any other drives. You might find that updating the drives firmware to the latest one will fix the issue. http://club.cdfreaks.com/1952787-post659.html Try the 4th link down in that post - i.e. http://www.yourfilehost.com/media.php?cat=...5P_HT695WIN.rar

What I mean is... Either you allow updates (and allow it to pass through the firewall) or you turn updates off. You shouldn't allow updates and then block it, that's just pointless. When you install the program it asks if you want to check for updates so there's really no excuse. The error you've got there is nothing to do with the program checking for updates or not checking for them. The update code runs in it's own thread (in the background) so unless your firewall is corrupting ImgBurn's memory, it wouldn't go anywhere near the other threads doing the burning. The update code is also only called at the moment the program loads - so for it to error out when the drive did, it would have had to have taken over 20 minutes to realise there was a problem. Would the firewall really block the connection in a way that it takes that long to bomb out? What if it wasn't multithreaded - you'd be waiting 20mins for the program to start! If you've always used RICOHJPN-D00-01 media, no wonder you got errors. The quality of that media can vary quite a lot - that's why we only recommend Verbatims for DL burning.

That's a bit harsh, I wasn't trying to be cocky at all. I just wanted to check it was still that same error code being returned when it really could be considered stuck - and I wouldn't consider it stuck after only 10 seconds - it's quite normal for the drive to return that error code after such a short period of time. Erm ok, good luck with that. Your system has the problem here, not my piece of *** software.

You need to work out the overhead for the filesystem... I'm not sure it's an easy thing to do without actually creating the file system! ImgBurn's Build mode works that way when you press the 'Calculate' button. I think you might be better off just adding a field where you can type in the info from ImgBurn.

If they're all about the same and the camera angle doesn't change as the cell changes, you might aswell go for the 50/50 with the least padding. There's no sense in burning more than you need to.