LIGHTNING UK!

It'll tell you if it needs erasing (even though it's automatic) - by using those very words. Unticking that box did nothing. If the button was greyed out it's because your drive was reporting it as BD-ROM again, and that's out of my hands I'm afraid.

That log doesn't show anything is wrong. You should try and fix the root cause of the problem, I can assure you that ImgBurn isn't it.

This has all been taken care of in the next version. It tells you exactly what it's going to modify and you no longer need to add files to a make a bootable cd.

It's in the code and the correct flag in the 'Close Track / Session' command is deffo being sent. It's not burning 1gb anyway, you're getting that from nero (or one of my previous posts where I was wrong!). The drives are supposed to burn until they reach a 30mm radius. Burning 300mb in Discovery mode, I can see a clear difference between burns with it on and off. With the option OFF: ATAPI DVD A DH20A3P XV66 (SCSI) Current Profile: DVD+R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 153,600 Size: 314,572,800 bytes Time: 34:10:00 (MM:SS:FF) Supported Write Speeds: 4x, 6x, 8x, 12x, 16x TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 153599) -> LeadOut (LBA: 153600) Disc Control Blocks Information: ATAPI Physical Format Information (ADIP): Disc ID: TDK-003-00 Book Type: DVD+R 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 Physical Format Information (Last Recorded): Disc ID: TDK-003-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: 350,207 Last Physical Sector in Layer 0: 0 With the option ON: ATAPI DVD A DH20A3P XV66 (SCSI) Current Profile: DVD+R Disc Information: Status: Complete Erasable: No Sessions: 1 Sectors: 153,600 Size: 314,572,800 bytes Time: 34:10:00 (MM:SS:FF) Supported Write Speeds: 4x, 6x, 8x, 12x, 16x TOC Information: Session 1... -> Track 01 (Mode 1, LBA: 0 - 153599) -> LeadOut (LBA: 153600) Disc Control Blocks Information: ATAPI Physical Format Information (ADIP): Disc ID: TDK-003-00 Book Type: DVD+R 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 Physical Format Information (Last Recorded): Disc ID: TDK-003-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: 350,207 Last Physical Sector in Layer 0: 0 As you can see, the disc info remains the same on both (as expected). It would totally mess up UDF file system if the drive just padded the user data with zeroes.

'DVD+R Reserve Track' has always defaulted to off. It's not ImgBurn that does the padding, it's the drive. I've never actually tested it myself but I wouldn't have expected the drive to add 670mb of 'nothing' to the end of the user data area, I'd have expected it to be 'hidden'.

Commands shouldn't just hang like that, you've got something that's preventing it from working properly... a driver / filter driver etc. The drive itself works with the command just fine because I have that very same drive in my PC.

Writes errors happen a lot on laptop drives I'm afraid. They're just pretty rubbish compared to the desktop drives. It might be worth investing in a decent external one. All you can do with your one is try again and perhaps check with the laptop manufacturer for any firmware updates.

It's purely cosmetic, don't worry about it.

I'm sure my mate has tested this for me before and he said the ImgBurn stuff worked fine. What exactly does the xbox do with ImgBurn burnt discs? Can't it see the content at all?

Is this fix needed for a specific type of disc? i.e. DVD Video, AVI etc or is it for all of them? If someone could get me an example of a super basic *working* one and a non working imgburn one (of the same content) I'll compare the two.

Incase you're monitoring this thread r0lZ, was the latest beta any better?

Probably not with that dye. Them being 'Memorex' means nothing I'm afraid. It's the dye that's important and 'RITEK-S04-66' is too new for that drive.

It would appear the newer version MDS files are using Unicode filenames - ImgBurn didn't support that but it does now.

You've got the oldest drive in the world there and the media you're using is quite a new dye. I doubt any firmware update you could do to it would fix that so your best bet is to buy a new one. Other than that, buy some Verbatim DVD+R DL 2.4x MKM-001-00 discs - they're probably the only ones it supports properly.

Please post the Verbatim log too. That said, if it really won't burn the Verbatims either (and they're the 2.4x MKM-001-00 made in Singapore discs), it does sound like a new drive is in order.

Sorry maa, it really doesn't interest me in the slightest. I looked at the link quickly and it seemed to want me to register for a license etc. (even if it is free, I wouldn't do it)

Just so long as you know the file isn't perfect. The hard read errors have now just become blank sectors.

Verify the disc again manually in Verify mode and see if it still errors out in the same places and with the exact same miscompare byte data. Any chance in you trying that drive in another machine? Or trying another drive in yours? They're only about

Anyone a member on the DVD Flick forums? Perhaps you could mention it to the author and point him in the direction of this thread.

I 11:17:35 Operation Started! I 11:17:35 Device: [3:0:0] HL-DT-ST BD-RE GGW-H20L YL02 (N:) (ATA) I 11:17:35 Media Type: BD-RE (Disc ID: TDKBLD-Wfa-00) (Speeds: 2x) I 11:17:35 Quick Erase: No I 11:17:35 Erasing Disc... I 14:49:59 Synchronising Cache... I 14:49:59 Operation Successfully Completed! - Duration: 03:32:23 3.5 hours... lol Best to format these things overnight

Damn, I noticed this in my code the other day but didn't actually fix it! I'd commented out the important line (probably during testing) and then forgot to uncomment it again. So basically, MRU is broken. It'll be fixed for the next version.

You've just got a bad sector in a file other than the 6 you're able to copy.... it's not exactly what I'd call 'very interesting', but perhaps that's just me?!

Oops, mine are TDK. I 11:17:35 Media Type: BD-RE (Disc ID: TDKBLD-Wfa-00) (Speeds: 2x) I can't find Panasonic ones here so I may have to get them imported via some US suppliers on eBay.com

Ah so it's a floppy disc image then! Try a program called WinImage on the boot image file. It should be able to manipulate the image without killing it's bootable properties.

It should be the other way around really. Big image + small disc fails. Small image + Big disc should be fine. That way around, it's a known problem and has been addressed for the next version.