LIGHTNING UK!

It would be handy to see if ImgBurn picks up on the same error when burning normal SL discs. I can't even find out what the error code the drive is returning ( ASC 0x00, ASCQ 0x0B ) actually means! Can you burn such a disc in ImgBurn and provide us with the log again please? Any SL discs will do... DVD-RW, DVD+RW etc... the more the merrier!

The decoding is done by directshow, it's nothing to do with ImgBurn. Unless you've got some weird files or very dodgy filters installed, I doubt they're as bad as you're making out. (It's hard to imagine these things) What kind of files were they? If you play the files in GraphEdit do they sound ok?

The image can be as big as you can fit on a disc, any limitation there comes from your BIOS more than anything. The 4GB limit is of a single file within the ISO9660 / Joliet file system. The field where you store the size of the file is 32 bits / 4 bytes / 2 words / 1 dword in length, hence the biggest value it can represent is just shy of 4GB. Assuming you've got the latest version (from the ImgBurn.com mirror), the program will auto correct any settings you might have got wrong if it notices you have an '\I386\NTLDR' file in your compilation. Once it's done that there's no reason for it to moan about anything NTLDR related.

I've added a 'None' option to the 'Shutdown Action' list just for you. So even if you click the Shutdown box (and 'None' is selected as the action) it won't actually do anything when the program has finished reading/burning etc.

Unless you have some way of reading UDF in the bootable bit then you're stuck. ISO9660 in ImgBurn will accept files up to 4GB but it's impossible to go any bigger than that. Vista DVD's just use UDF really, the ISO9660 part is purely there for making it bootable and that file system just contains a readme.txt file saying you need an OS capable of reading UDF to access the files on the disc. When you select UDF only in Imgburn and make the disc bootable, it does exactly the same thing.

Options to disable options... now why didn't I think of that?!

ok, that helps narrow it down. Now I really need you to capture exactly what happens from the moment you put the disc in until the 5 - 10 minute wait is over and it starts working again. So load the program without a disc in the drive, press F8 to enable I/O debug mode and then insert the disc. Leave it until you get control back and then save the log to a file and attach it in your next post - or email it to the support email address (look in the program's about box)

Are you burning an image or a video_ts folder? You're more likely to get multiple options when burning a video_ts folder in Build mode than you are when burning an ISO in Write mode. Yes the layer break often means there's a pause in playback... that's what marking the cell as 'seamless' helps prevent. It really is your call as to whether you should take the seamless route or not. As all the superbit dvds are marked as seamless by default I'd say 'go for it'.

If it installed the boot files on the wrong hdd then you must have the order mucked up physically or in the boot order sequence. Swap the cables around Disconnect D: Install onto C: Plug D: back in and copy everything off it Write zero's to D: before then reinitialising the disc and copying the stuff back.

ImgBurn just wasn't designed with your needs in mind, it was designed to build an image from an existing hdd structure and the current interface is fine for that. When I change it to make it more flexible I'm sure I'll implement some sort of explorer type tree view.

You need to actually post the error or the bit where there is a pause - that bit of the log is normal. Once you've inserted the disc, keep an eye on the statusbar in the main window. It'll tell you what the program is doing and might offer us a clue as to what's going on.

Reading a DL disc doesn't work how you think it does. The drive takes care of the switch between the physical layers, the location of shifted layer break has nothing to do with anything. If you have an error when reading then it should have been picked up on during the verify stage... you did verify didn't you?

There are several apps you can use to do the conversion stuff - ConvertXtoDVD, DVD Flick, Nero something or other etc... I'm sure a search here on the forum or on Google will get you started.

If it doesn't have 'divx' stamped on it somewhere then no, it can't play your AVI file. Yes you'll need to convert it to a proper DVD Video 'VIDEO_TS' folder complete with the normal IFO/BUP/VOB files.

If you set it to never then that's what it'll stay on - unless something else messes with your settings. Lots of programs call on ImgBurn for burning so it's not unheard of. Going between different versions of the program can also make it happen - like if one doesn't support all the values another one does it'll use the default value.

Ah that's clever! Lucky I made the installer save and read the previously selected options from the registry key! You should be careful when pushing out settings though, it's best to just import the ones you actually NEED to change and let the program configure the others.

You're looking at the wrong thing. Joliet is an option in the 'File System' drop down box.

Wow you must buy from expensive places. Even the verbatims are about

1. Sounds like you've enabled 'Preserve Full Paths'. Turn it off again. 2. ImgBurn truncates names according to the file system specs / restrictions. If you want to ignore them then you need change the options on the 'Advanced -> Restrictions' tab. It should be pretty obvious which one you need to change ('Folder/File Name Length').

That's perfectly normal. Samsung drives cannot be queried to find the current settings. ImgBurn takes care of the booktype stuff automatically on those drives anyway so you don't need to do anything.

Formatting for the first time takes a while to do it properly. (So that the 'Formatted' status in the disc info panel on the right says 'Yes'.) Just leave ImgBurn going and it'll finish eventually or error out.

I'm sure that once it's kicked into gear properly it'll write at full speed from ImgBurn too. ImgBurn is only using standard Windows API calls. Sometimes they just need a bit of a hard kick and random accessing can help achieve that! (I have a couple myself)

Shame on cdrinfo for not keeping their pages up-to-date

Don't worry, ImgBurn accepts APE or WAVE for the file type. It's more for internal usage than anything else. Thanks for the error report, at least I have something to go on now!

Update your firmware and try again. A105 is the latest. http://www.cdrinfo.com/Sections/Firmware/S...px?DriveId=1048 If that still doesn't work, you know to buy Verbatims 2.4x DVD+R DL (MKM-001-00 dye, made in Singapore)