LIGHTNING UK!

Is it just this one disc? The cue is fine because I just made a dummy wav and it loaded it up fine. I can only assume this is something to do with pathnames. Are all the files in the same folder? Obviously I need to add an error message into whatever's failing about it, but I can't tell what that is until we dig into this a little deeper.

Check your Verbatim discs are from Singapore and not anywhere else. Try burning at one of the faster supported speeds, the drive might actually prefer it. The low average speed is low because the retries we going on for so long - during this time the timer is still counting.

It's 'Parse File System Timeout' and it's on the 'General' tab in the settings. If you don't have that option then there's probably no timeout in your version... I don't remember when I implemented it exactly, sorry. You shouldn't be using 2.3.2.0 anyway

It's nothing to do with them being faulty or not - unless of course you mean unreadable discs? Discs with tens of thousands of files on them might also take longer than 30 seconds to parse. You can extend the timeout or turn it off if you like, just look in the settings. Which application is this with btw?

It's a quick and dirty screen called 'Create CD CUE File'. By definition it only creates them.

Click the session level and do it there - it'll then apply it to all the tracks in that session. There's no way to turn it on by default (at the moment anyway).

This is a different message loco, that option has no effect.

If you need to get at something on your desktop without having to close/minimise ImgBurn, just use the 'Show Desktop' button on the quick launch bar (or right click the taskbar). That's exactly what it's there for.

If you could find a directshow filter to play these files in something like graphedit, ImgBurn should work too. Maybe ffdshow can be made to play them?

The translations files don't deal with hardcoded messages, just the text on the GUI windows. I think you're referring to the message when the file system parsing times out - which normally happens after 30 seconds.

ImgBurn will now autopatch the '\isolinux\isolinux.bin' file (on-the-fly so the original is not modified) with the required data for the 'boot information table' as per this website http://littlesvr.ca/isomaster/eltoritosuppl.php

I think I'd have gone for XP32 or Vista 32 straight off.

You could have asked that question in 1 line mate! ImgBurn doesn't do anything with c2 pointers. It's not in the same league as EAC for accurate ripping.

Where are your verbatims made? Singapore? (check the box/spindle/case). Burning a DL would be different to burn SL. I really couldn't say if 1 works that the other should do to. I would guess that the drive has to be more accurate for a DL burn. Can the drive read the DL's you burnt the other day? Can it read any DL discs? Originals (i.e. a pressed DVDROM) or otherwise.

It's just an error the drive returns. It must be having some issue initialising the disc - locating a certain something on it or whatever. Until the drive initialises the disc, no software can access what's on it - so you're totally out of luck.

How does that make *any* sense at all?! Do as mmalves said above.

If it won't read some discs properly then yes it might well be broken.

DVD Decrypter wouldn't be able to detect the errors during sync cache, close track/session or finalise disc, it didn't have the code in it to do so You might find the issue of ImgBurn discs not being readable is due to it retrying. That said, when 'Don't use immediate I/O' is enabled and it doesn't error out, the disc should then work - unless of course the drive performs its own auto retry, I really couldn't say.

I've used white spirit type stuff and a cotton wool ear bud type thing before. Should be fine so long as you're careful!

It creates everything that's needed for an El-Torito disc. If it didn't, you wouldn't be able to create bootable XP discs - and you can. I don't have any real interest in linux so if additions/changes need to be made, someone will need to tell me about them. EDIT: What's the location of the isolinux.bin file within your image? I've just read that this needs to be modified with info about the boot image you select.

If it doesn't provide enough data to fill the final sector ImgBurn will zerofill it regardless. That's all the digital silence there should be though if the decoder is accurate enough. I don't really know how to do anything other than what it's doing now.

Do you have any old/spare hdd's around the place? If so, disconnect your main one and install an OS onto it with nothing but ImgBurn, then try again. If it's hardware, it'll still fail. If not, at least you know where to start troubleshooting.

You've got DMA issues. Try replacing the cable to the drive and uninstall the controller entry from the 'ide ata/atapi controllers' branch in device manager and reboot as per the DMA post in the FAQ.

If it's a home made/non-protected dvd, follow the post in the Guides forum. If it's not, ImgBurn can't help you and you'll need to seek help elsewhere.

(Threads Merged) When you load the program (with I/O Debug Mode enabled), look at the statusbar message and make note of exactly what it says (could be multiple things) when it's taking ages to load up properly. Something is obviously not quite right on your machine somewhere, we just need to find it. What antivirus/malware/spyware programs are you running? What other burning software do you have installed? Do you have any virtual drive programs installed? Have you tried updated motherboard chipset/ide drivers as Cynthia mentioned? Have you tried uninstalling the controller entry from under the 'ide ata/atapi controllers' branch in device manager and rebooting?