LIGHTNING UK!

The buffer size being used isn't going to make any difference so it's not that. I think it's just fluke that sometimes it works and sometimes it doesn't. You'd have to burn something like 20 discs, alternating between program versions and always having a successful burn in one and failure in the other for me to take a report like this even remotely seriously. (no offence) It's more likely that your ageing (and probably dirty) drive just has a problem with trying to burn at max speed on those discs. Even if I tried, I couldn't make the program cause the problem you're having, and as such, it can't possibly be a bug in it.

All you need is HKEY_CURRENT_USER\Software\ImgBurn and you can already use an ini file, look in the readme.txt file.

The first error is the important one - but unfortunately your drive returned an unknown variation (ASC 0x09, ASCQ 0x90). Other entries under ASC 0x09 branch are as follows... ASCQ 0x00 - Track Following Error ASCQ 0x01 - Tracking Servo Failure ASCQ 0x02 - Focus Servo Error ASCQ 0x03 - Spindle Servo Failure ASCQ 0x04 - Head Select Fault So that's the kind of real error you're looking at. Anyway, it still boils down to the same thing... your drive has a problem with the media you're using. You can go back to the current version of ImgBurn now, these problems are caused by external 'hardware' factors (drive and media) and not the software.

When a drive errors out, 99% of the time it's because it has a problem with the media you're using. That could be for various reasons such as... 1. The drive's firmware is out of date and can't handle the MID (RITEKF1 in your case) very well 2. The drive is dirty (clean it with a cleaning disc) 3. You've selected a less than optimal write speed (this is related to the drive/firmware/media combo) 4. The media is just cheap stuff - and by that I don't mean it cost almost nothing, you can get brands which rip you off for discs that use a low quality MID/dye. Attempting to (re)use a disc that has already failed to burn is never a good idea either. (I can't tell if you were doing that or not)

Post the log please - as per the pink box up the top.

ImgBurn doesn't convert anything video related. That's where programs like DVD Flick and ConvertXtoDVD come in (hence my earlier suggestion to use it). They'll convert your avi, mp4 type files into the proper DVD Video format - and yes, that's the VIDEO_TS folder containing IFO/VOB/BUP files.

Only a player supporting MP4 files will play MP4 files If yours doesn't then you'll have to go ahead and convert to the proper DVD Video format. ConvertXtoDVD is pretty quick - obviously the conversion speed depends on the spec of your PC.

I didn't have to when I preformed my tests, no. http://forum.imgburn.com/index.php?showtopic=18871&st=0&p=136519&&do=findComment&comment=136519 Things got pretty consistent for me after starting 'Attempt #8'.

I can see you've changed a few settings from their default values... can I assume you've therefore tried them all individually enabled/disabled? When I tested the modified firmware (around the time of its release), I only really tried it on the proper Verbatim media. I gave some Aone Plus a go and it burnt 1 and errored out on several others - that's when I gave up using anything other than the recommeneded media. Perhaps it's time you did the same? My drive worked best burning the Verbatim MKM-003-00 discs @ 4x with 'Force HT' enabled via its EEPROM settings ('Online HT' left disabled - its default). All the program settings were left on their default values.

Do you only want certain tracks or something? If not (and you wanted the full CD), why not just use Read mode to make an image? There's a guide for burning audio files in the Guides section - that's if you still want to go down the 'WAV' route. http://forum.imgburn.com/index.php?showtopic=5555 Once you've made the CUE file, load it in Write mode and then take a screenshot of the main window so I can see its calculated size.

Can you post a log from each version? The way data is written is the same in all versions, there's only 1 command that does it! That command being sent from 1 version is no more/less likely to complete successfully (or fail) than if it's sent from another version, so there must be something else coming into play here.

It's not currently possible, there's no 64 bit compiler for C++ Builder.

In the 'Advanced Settings' (or the EEPROM Tool - Google it), Clear OPC History and enable FHT. I 12:32:02 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes becomes... I 12:32:02 Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes Write at 4x. If it still fails, get another spindle of Verbs and try to get some made in Singapore.

There's a newer firmware available that you might like to try. http://www.firmwarehq.com/Lite-On/SHW-160P6S/files.html After that, it's probably just a case of trying to clean the drive with a cleaning disc - it is getting on a bit now and really shouldn't be having problems with 'MCC-004-00' media. That said, if you don't already have a cleaning disc, don't bother buying one. You can pretty much buy new drives for the same cost! (Depending in where you shop for said items)

The program saves the log automatically. Maybe this will help... http://forum.imgburn.com/index.php?showtopic=14632

Verbatim don't normally use anything other than Mitsubishi dyes on their discs. If you've ended up with Ritek dye then you probably have fakes or some 'value' ones. The Mitsubishi dye is the one to go for. If you read the pink box up the top you'll see that we want you to post a log (showing the problem) It tells us everything (for the most part) we need to know and it saves you writing loads of stuff.

Install the current version of ImgBurn too, I forgot to mention that earlier.

If you select the session item in that window and then click one of the CD-TEXT options, it applies that option to all the songs in that session. The top level disc item is different because the disc has its own CD-TEXT info (album name etc) - selecting a certain CD-TEXT option at that level therefore *doesn't* then also apply it to all sessions / tracks within those sessions.

http://forum.imgburn.com/index.php?showtopic=8000

Doh, I just finished replying to your email! --- copy + paste --- 1. I really need to see the full log rather than just 1 line of it. I assume that error popped up during the verify phase and basically it means the disc couldn’t be read. That isn’t a good sign! 2. The volume label is the name of the disc that gets displayed in ‘My Computer’ / ‘Explorer’. You can edit what ImgBurn suggests and change it to whatever you want it to be on the window that pops up (when you haven’t already configured one on the ‘Labels’ tab). If you want to make a donation, look in the ‘Help’ menu within the program (or check the main website at http://www.imgburn.com/ )

You'd have to get your program to output the full names (i.e. including the full path) of the files to a text file and then pass the name of that file to ImgBurn using the /SRCLIST command line switch (again, see the ReadMe for details).

It can only be CD-TEXT and you configure that in the 'Create CUE File' window.

Maybe... it depends on if you've overwritten that bit of your hdd. Any file recovery program should do it. Something like 'Recuva' springs to mind. http://www.piriform.com/recuva

There isn't a way, no. On the off chance you've got a LiteOn drive, I believe the combined read/write offsets work out to 0 anyway... so it would be both accurate and complete by simply using Read / Write modes in ImgBurn.

Creating an ISO of each CD using Read mode (giving you 3 ISO files) and then writing each ISO to a DVD (3 DVDs in total) using Write mode should be all that's required here.