LIGHTNING UK!

An ISO image is a sector by sector copy of the disc. 'Quality' doesn't even come into it. An ISO image is also THE standard for disc images. Pretty much everything supports it.

No problem, you're not the first to come to us with this issue. As I recall, it was harder to work out the issue the first time - now I just remember the signs and put 2 and 2 together pretty quickly!

Ahhh well then you have a different problem! As it stands, I'd expect the device buffer bar to be empty if you're only getting so far as the leadin. Does it get stuck at this point no matter what you're burning? i.e CD-R / CD-RW / DVD-R / DVD-RW / DVD+R / DVD+RW etc.

So what happens if you disable the option on the one running Alcohol? It's the 'Ignore Media Type' one in the 'Emulation' options window. What happens if you boot into safemode and then examine the disc info via ImgBurn as you've done above? I have a SH-S183A and can't reproduce this issue (although it's a drive/system issue anyway and not a program one). I am on a more mature firmware though - SB02 - but that's not available for your drive. TSSTcorp CD/DVDW SH-S183A SB02 (ATA) Current Profile: DVD+RW Disc Information: Status: Complete Erasable: Yes Formatted: Yes Sessions: 1 Sectors: 2,295,104 Size: 4,700,372,992 bytes Time: 510:03:29 (MM:SS:FF) Supported Write Speeds: 2.4x, 4x TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 2295103) -> LeadOut (LBA: 2295104) Physical Format Information (ADIP): Disc ID: MKM-A02-00 Book Type: DVD+RW Part Version: 2 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 2,491,711 Last Physical Sector in Layer 0: 0 Physical Format Information (Last Recorded): Disc ID: MKM-A02-00 Book Type: DVD-ROM Part Version: 1 Disc Size: 120mm Maximum Read Rate: Not Specified Number of Layers: 1 Track Path: Parallel Track Path (PTP) Linear Density: 0.267 um/bit Track Density: 0.74 um/track First Physical Sector of Data Area: 196,608 Last Physical Sector of Data Area: 2,491,711 Last Physical Sector in Layer 0: 0 Current Format Capacity: Sectors: 2,295,104 Size: 4,700,372,992 bytes Time: 510:03:29 (MM:SS:FF) Preferred Format Capacity: Sectors: 2,295,104 Size: 4,700,372,992 bytes Time: 510:03:29 (MM:SS:FF) Maximum Format Capacity: Sectors: 2,295,104 Size: 4,700,372,992 bytes Time: 510:03:29 (MM:SS:FF)

Hmm it's being reported by the drive that it's not even erasable anymore! Do you have Alcohol 120% installed at all? There's an option in that program to make DVD+RW look like DVD-ROM's. If you have, disable it and the problem should go away.

can you please copy + paste the info in the panel on the right when current profile is dvdrom.

Ignoring the initial spin-up / initialisation period of the drive, all 6 of my drives instantly go to 'Disc Is Empty' in the status bar. What drive do you have and what media is this issue with? I just tested with a blank CD as that was closest to hand!

So once you click the 'Write' button, the program tries to erase / format the disc, then it gives up? At this point, the 'Current Profile' has changed from DVD+RW to DVD-ROM? If you eject + reinsert the disc does the current profile go back to DVD+RW?

1. Yes, many drives do this. The buffer normally drops down when they perform WOPC (testing the burn quality on-the-fly as it burns so it can adjust the laser power). 2. No (see above) 3. No - all that might do is give your drive a second to cool down!

It'll just be waiting for a response from your drive... it must be taking a while. I'll see if any of my drives are slow too and figure out if I can tweak something.

When it says 'Disc Needs Formatting', does it actually attempt to format the disc (before the real write) when you try to burn something? Copy + paste the log so I can see what it's doing. Thanks

The booktype has nothing to do with being able to burn the disc or not. 'CurrentProfile' is the one that's important and as you can see, that still says 'DVD+RW'. So what exactly is the problem you're experiencing?

lol, no, you're still cutting it off at 'Writing LeadIn...' ! The device buffer isn't checked until after that, and only then will it start logging.

Uncheck 'preserve full pathnames' ? (which is default anyway) Then you'll only get 'my backup folder' and not 'D&S' -> 'Me' -> 'Desktop' -> 'my backup folder'.

You don't have permission to create a file wherever you're telling the program to make it. Under Vista, pretty much the entire HDD is locked down. You only have access to write to your profile ('My Documents' etc) folders. So you have 2 choices... 1. When you run ImgBurn, right click the icon and select 'Run As Administrator' (you can make this permanent via the icon properties). You'll then have permission to write to anywhere on the hdd. 2. Write to a folder you know you have write permissions on.

Sorry, you won't ever see the .gi stuff, there's just no point in it. As for displaying sizes in other units (MB / GB etc), that's unlikely - and certainly not in the next version - I'm happy with how it is at the moment. I generally include that info in the log where it's useful but there's not always enough room in the GUI for it. Sometimes you can find it in the tooltip though.

Closing tracks / finalising the disc probably involves a whole lot of stuff. I don't pretend to know what exactly... you'd need to speak to the manufacturers for that!

Like I said in my previous post, the bitsetting stuff is done when the disc is finalised. As yours is failing at that point, that's probably why it's not working. That is VERY much related to the media.

What happened to the rest of the log?

The Pioneer drive itself controls bitsetting, the program doesn't have to do anything. That's not the case with LG drives, but 2.3.2.0 should send the appropriate command(s) automatically. My guess is that yours is failing to do it due to the error you're getting at the end of the burn (that's when the drive would probably do the bitsetting stuff). That is of course assuming you've not disabled that option in the settings?! As kev said, ditch the riteks and buy some Verbatims.

If you don't even know what an ISO is, ImgBurn isn't really the tool for you to use just yet. It's not designed for people with NO idea on what they're doing. Get used to the lingo via other 'user friendly' tools like Nero and then come back to ImgBurn when you're ready to.

ImgBurn is a burning program, so no, it won't ever include an 'IFO' mode. My days of DVD Video related stuff are over. (well, outside of burning them anyway)

When I say 'first', I mean least significant Sorry

Well either the command to get buffer size / state isn't working during the burn, or your drive is just always reporting that it's empty. This is a little weird - it should be empty! There's a way to enable logging of buffer commands during a burn, you have to add a registry entry. Under 'HKCU\Software\ImgBurn', make a DWORD entry called 'OVERRIDE_DeviceBufferWithLogging' and set it's value to 1. Then burn another disc having pressed F8 before you start. The program will log all the buffer status commands sent to the drive. Copy + paste that log (or save + attach if it's huge) When you've done that, delete the registry entry again.

Setting it to 1x (as you were) wasn't doing anything anyway. The drive only lists the following... ... i.e. 2.4x and 4x, so it would have ignored the request to burn at 1x and gone with 2.4x anyway. So it could be a fluke that it worked this time. On the other hand, you might have uncovered a bug in the drive's firmware. Keep an eye on things and if it happens again, let me know.