LIGHTNING UK!

Don't 'tweak' settings, reset them back to default! We're not having problems and ours are on the defaults.

Those fields are for whatever made the file system - as 'Read' mode is not creating anything, merely reading it, it's not supposed to update the fields.

I actually prefer that it still tries to unlock it even if it thinks it failed in the first place. I have however made it fail silently when it knows the locking failed.

Hmm it's appending something random that shouldn't be there! I'm looking at it right now! EDIT: Fixed. Thank you :-)

Do you have 'Preserve Full Paths' selected? If so, uncheck it.

'AUTO' means the new 'Auto Write Speed' config takes over. If you don't configure anything, the discs will just burn at max. I think perhaps I need to do a guide or something for this new feature as I guess people don't understand what it is. Basically, you enter the MID of the media you use and select the write speed. Then whenever you use those discs, it'll automatically write at your pre-defined write speed. Once that's done, you never need to touch anything again. You can force any media to burn at any speed you like on any drive you like.

Get some taiyo yunden cds, they're not very expensive really. You can get some datasafe taiyo yuden ones for ?12.98 for 100 discs. http://svp.co.uk/products-solo.php?pid=1457 Even if you still have problems, at least you'll have good discs for the next drive you buy. Personally I'd never buy a 2nd hand burner.... there's just no point! You can buy them brand new for less than ?20

You should use v2.2.0.0 and preview each cell to find out where you'd be least likely to notice the layer jump glitch.

Yeah that's fine by me.

Did you submit that bug report to them for the unicode combobox? Even if the bug isn't directly in wine, I'd be interest to see what they have to say

I'd leave the write speed at 8x and also try to get some Verbatim DVD+R discs rather than DVD-R. Your drive might perfer +R over -R.

We'd burnt hundreds of DL discs with 2.2 during the beta cycle, and as always, it's the drive that controls the 'write strategies' (and ultimately, the burn quality), not the software. The software simply sends the data - and if that didn't work, nothing would work! I did another one last night upon reading this and it's working fine.

It would actually be the opposite to that. The calc is done by the read thread, not the write one. The write thread is the one that displays it.

Either it's an unprotected disc or you played it (perhaps automatically via 'autoplay') before loading ImgBurn.

That doesn't look/sound like an ImgBurn error. Do you know how to use an 'open file' dialog box? Once you've clicked the browse button you have to select a file. If it's a 'save file' dialog box, you have to browse to a folder and then type in the name of the file you want to create (or select and existing file to overwrite). This is basic windows stuff and nothing to do with ImgBurn really.

What EXACTLY does the error message say? Can you get a screenshot? I would guess you're trying to open a file that links to another one, and that 'other' one doesn't exist (it probably has a different name).

That's excellent advice about the booktype stuff, but it's actually automatic with v2.2.0.0 for LG and Samsung drives.

Yes, you have DMA issues. Check you're using a decent 80 wire IDE cable. Check the drive is set to master / slave and that other devices are correct too. Positioning on the cable may also be important - the master drive goes at one end, slave in the middle, motherboard at the other end. Reset windows DMA using the info provided in the FAQ. Ensure the drive is correctly configured in your motherboard bios and that it sees the drive as Ultra-DMA 2 (or 4). If you have 2 drives on the same cable, try disconnecting one of them, it might be screwing things up for the other one.

lol it wasn't so much me defending my baby, as it was just not having a clue why it wasn't working! I'd already spent a while researching after the 2.1.0.0 bug report and was a bit pissed off that you said it STILL didn't work! (Please note that I wasn't pissed off at you, just in general) I hate not being able to solve problems and this one had me completely stumped because the MD5 calculation code looked spot on

Read the guides section. Burning an image is VERY simple.

I looked at this earlier on today but couldn't see anything obviously wrong. Can you copy that file to somewhere else on your hdd? The function that's having problems just reads the file into a buffer, it's tricky to say where it's going wrong! I've added a bit of debug info to the function now so I may email you a version you can perform additional testing with.

I gave up waiting for LG / Samsung to follow suite with the rest of the manufacturers! I just made it user configurable, so besides the default device id string the program supports, the others are down to the user. That gets around me actually having to keep things updated.

For what it's worth, I just burnt a file in nero to a cd-rw disc with the option to 'start multisession disc' selected and 'finalise disc' NOT selected. The resulting disc could be read ok in ImgBurn. The info panel on the right said the following: HL-DT-ST DVD-RAM GSA-H22L 1.00 (ATA) Current Profile: CD-RW Disc Information: Status: Incomplete Erasable: Yes Sessions: 2 Sectors: 17,417 Size: 35,670,016 bytes Time: 03:54:17 (MM:SS:FF) TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 17416) -> LeadOut (LBA: 17419) ATIP Information: Start Time of LeadIn (MID): 97m34s23f Last Possible Start Time of LeadOut: 79m59s74f What does it say on your machine when you put this problem disc in the drive?

Your idea of sector by sector and my idea of it must be different. You can't just write the sectors and expect the drive to insert new sessions / tracks etc in the right places - it won't. The same goes for reading. Sessions and tracks are defined by additional commands - ImgBurn doesn't currently support them. If the CD only had 1 session / track but was still 'open', the 2nd (non existant) track/session must have been identified in such a way that imgburn thought it was not empty and hence it really was a multisession disc.

Your post already contained both these answers: 1. Update your drives firmware. 2. Ditch the Riteks and buy Verbatim DVD+R DL media instead.