LIGHTNING UK!

Bugging me, and also I like 12x DVDRAM (not that I can buy the discs!) and 10x DVD+R DL sounds like fun I really do have a cupboard full of drives to buying another one is nothing out of the ordinary for me! Yup, I've got JJ11, just can't flash it when it's in my usb enclosure! Stupid thing just hangs. I've got some other bits to do first but then I'll connect it via IDE in another pc, flash it and test again.

Sod it, I couldn't find anywhere (from my normal bunch of online retailers) doing the GSA-H10N (and that had them in stock) so I went to good old PC World! Picked one up for ?35 which isn't really all that bad. I'm burning a Verb 2.4x DL disc @ 6x as I type this. This is with the standard JL10 firmware. Next I'll flash to JJ11 and try the same thing. I 16:09:55 ImgBurn Version 1.3.0.14 Beta started! I 16:09:55 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 16:09:55 Initialising SPTI... I 16:09:55 Searching for SCSI / ATAPI devices... I 16:09:56 Found 3 DVD-ROMs, 1 DVD?RW and 4 DVD?RW/RAMs! I 16:17:16 Operation Started! I 16:17:16 Building Image Tree... I 16:17:16 Checking Directory Depth... I 16:17:16 Calculating Totals... I 16:17:16 Preparing Image... I 16:17:20 Using Layer Break LBA: 2032270 -> 2032272 (VTS_01, PGC: 1, Cell: 8) I 16:17:20 Image Size: 8,238,813,184 bytes I 16:17:20 Image Sectors: 4,022,858 I 16:17:31 Operation Successfully Completed! - Duration: 00:00:14 I 16:17:31 Operation Started! I 16:17:31 Source File: -==/\/[bUILD IMAGE]\/\==- I 16:17:31 Source File Sectors: 4,022,858 (MODE1/2048) I 16:17:31 Source File Size: 8,238,813,184 bytes I 16:17:31 Source File Volume Identifier: DL_TEST I 16:17:31 Source File Application Identifier: IMGBURN - THE ULTIMATE IMAGE BURNER! ? 2006 LIGHTNING UK! I 16:17:31 Source File Implementation Identifier: ImgBurn I 16:17:31 Source File File System(s): ISO9660, UDF (1.02) I 16:17:31 Destination Device: [0:0:0] HL-DT-ST DVDRAM GSA-H10N JL10 (N:) (USB) I 16:17:31 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x) I 16:17:31 Destination Media Sectors: 4,173,824 I 16:17:31 Write Mode: DVD I 16:17:31 Write Type: DAO I 16:17:31 Write Speed: MAX I 16:17:31 Link Size: Auto I 16:17:31 Test Mode: No I 16:17:31 BURN-Proof: Enabled I 16:18:05 Filling Buffer... I 16:18:06 Writing LeadIn... I 16:18:13 Writing Image... I 16:18:13 Writing Layer 0... (LBA: 0 - 2032271) I 16:26:32 Writing Layer 1... (LBA: 2032272 - 4022857) I 16:34:43 Synchronising Cache... I 16:34:44 Closing Track... I 16:34:49 Finalising Disc... I 16:35:53 Image MD5: 28303352305f5b7f2c288148720d72c0 I 16:35:53 Operation Successfully Completed! - Duration: 00:18:22 I 16:35:53 Average Write Rate: 8,135 KB/s (5.9x) - Maximum Write Rate: 8,349 KB/s (6.0x) I 16:35:53 Cycling Tray before Verify... W 16:36:04 Waiting for device to become ready... I 16:36:30 Device Ready! I 16:36:30 Operation Started! I 16:36:30 Source Device: [0:0:0] HL-DT-ST DVDRAM GSA-H10N JL10 (N:) (USB) I 16:36:30 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x) I 16:36:30 Image File: -==/\/[bUILD IMAGE]\/\==- I 16:36:30 Image File Sectors: 4,022,858 (MODE1/2048) I 16:36:30 Image File Size: 8,238,813,184 bytes I 16:36:30 Image File Volume Identifier: DL_TEST I 16:36:30 Image File Application Identifier: IMGBURN - THE ULTIMATE IMAGE BURNER! ? 2006 LIGHTNING UK! I 16:36:30 Image File Implementation Identifier: ImgBurn I 16:36:30 Image File File System(s): ISO9660, UDF (1.02) I 16:36:30 Verifying Sectors... I 16:53:28 Device MD5: 28303352305f5b7f2c288148720d72c0 I 16:53:28 Image MD5: 28303352305f5b7f2c288148720d72c0 I 16:53:29 Operation Successfully Completed! - Duration: 00:16:58 I 16:53:29 Average Verify Rate: 7,903 KB/s (5.7x) - Maximum Verify Rate: 11,364 KB/s (8.2x)

I really have no idea what's going on here! That command reads what the drive thinks it's going to use as the write speed. See the 20 76 bit? That's 0x2076 (hex) which equals 8310 (decimal). 8310 / 1385 = 6. 1385 is 1x DVD speed. So your drive 'thinks' it should be burning at 6x, it's just not. The max write speed shown in the log also states 6x so it would be interesting to see where exactly it hit that 6x speed and for how long. I relalise you're probably a big cdspeed fan so might not like/use DVDInfoPro, but could you also save the IBG file and/or export it to DVDInfoPro and attach those screenshots/files. You can see that stuff from the 'File' menu. 'Display Graph Data using DVDInfoPro' etc.

Try searching google.

Happy Birthday! (and happy birthday to photoangel too!)

I honestly have no idea why ImgBurn would be any different to DVD Decrypter. If the drive is behaving itself, the two should behave identically. Maybe a log from the burn would help. Also, some graphs / scans from DVDInfoPro would be useful. Maybe I'll be able to spot where the problem is coming from.

ImgBurn doesn't introduce anything! It sends commands -> drive deals with commands -> drive burns media. SAO and DAO are one in the same. DAO is just the correct name for DVD burning. The layer break position has nothing to do with burn quality, it's also much better in ImgBurn than it ever was in DVD Decrypter. You are using Verbatim DVD+R DL media yeah? Forget about using anything except that.

Ritek discs really aren't up to much these days. You'd do well to update your drives firmware with the latest official LiteOn version. http://forum.rpc1.org/dl_firmware.php?download_id=1934 That might involve a little bit of cross flashing as I guess yours is branded by whoever made your pc. Be it dell, hp, ibm etc. The Liteon forum over at www.cdfreaks.com should be able to assist you with that. When you've done that, if the media still doesn't work (or even if it does!) you should look at buying some better stuff. Verbatim or Taiyo Yuden are the ones to go for.

Sorry, I was just thinking about the new 1655 models! I think the 1640 also supports them at faster speeds than the std 2.4x.

As you're in the ImgBurn forum, I can only assume you want to burn with ImgBurn - and you know that right now ImgBurn only burns image (ISO) files. Yeah? So.... Make an ISO with some other program and then burn it with ImgBurn. Small files are always a pain, especially if you tell the ISO creation tool to add the ISO9660 file system. Crunching filenames down into unique 8.3 format names takes time - there's not much you can do about that. The fact that they're tiff files is no different from any other file type.

Corny is correct. DVDShrink doesn't build proper DL ISO images, you need to use something else for that. At the moment, the only free tool that does it properly is PgcEdit (which uses mkisofs).

BenQ doesn't overspeed this media. They force you to use 2.4x. Looking forward to seeing results of your next burn

Dunno really guys, it's just one of those things where the DVD + format doesn't support it. I guess they saw it as pointless - which in all honesty, it is! All it would basically be doing is testing to see if your machine could keep up with the speed - by you keeping an eye on buffers etc. As burnproof cannot be disabled on +R format media, not being able to keep up isn't much of an issue. Test mode doesn't test the drives ability to burn onto that media... it's still 100% possible for a burn to pass a test and then fail a real burn if shit media is used. When I speak about DVD + format, I mean everything +. So that's DVD+R, DVD+RW, DVD+R DL and DVD+RW DL (when it comes out). Not only that, but the command you send to a drive that contains the option for test mode (the 'write parameters' mode page) is supposed to be ignored by drives when DVD+ format media is present.

The actual ability to burn (but not burn!) - i.e. test mode - is only supported by the DVD - (minus) format discs. This isn't ImgBurn's limitation, it's just what the drives / media supports. What do you mean by verifying the image? Corrupt or not, test mode would not fail unless there was a physical hardware fault. The actual content of the image doesn't even come into it.

There shouldn't really be anything to fix here. ImgBurn sets the speed (which is good enough for all the other drives I've come across) and the drive does as it's told - or what it thinks is best. When you set it to max, the drive is sent 0xFFFFFFFF as a speed value. ALL drives are supposed to take this value as being the max speed, and all programs operate on that understanding. If ImgBurn can send that value and your drive still not burn at 6x when it's reporting 6x as a supported write speed, there must be an issue in the firmware somewhere. I don't suppose you've tried setting the speed to 8x, 10x, 12x etc have you? If it's working at a speed notch down (and ignoring MAX), maybe those would make it burn at 6x. If you fancy doing another burn, turn on I/O debug mode first (press f8) and then save + attach the log in your next post. I'd really rather not have to buy this drive just for this! EDIT: JL10 firmware appears to work ok on that drive. http://club.cdfreaks.com/showpost.php?p=1426443&postcount=9

Folder2iso only makes images with iso9660 and joliet file systems. DVD Video requires UDF (rather than Joliet). It'll play ok on a computer (beacause they'll read any file system) but standalone machines only have to understand UDF - and if it's not present, you're screwed!

I would guess overburning is the problem here. Your drive is probably rejecting the size of the image because it knows it wont fit on the disc. ImgBurn doesn't burn VCD/SVCD images anyway so you're kinda wasting your time! They're supposed to contain 2 discreet tracks but ImgBurn only deals with single session / track images at the moment. That's why there is no support for the cue/bin format yet.

Can you please tell me a little more about the image you're trying to burn. Copy out the info it says under 'Source' and also do a copy + paste job on the info in the window on the right. Then copy + paste the full log too. Thanks.

it's on private. Not to worry. I'll forget about it for now and wait until the next beta (or RC) and then try again.

Just copy nero's wnaspi32.dll file to the same folder as his tool.

The program automatically takes care of formatting / erasing if it decides it is needed. It's not something you should concern yourself with.

Yeah, please stop killing all of them.... I do like some serious ones!

As LG are the only ones (and possibly samsung, but they're pretty awful all round) that don't implement a nice version (where the drive remembers what it's told!) bitsetting, this is unlikely to happen. Take a look here, it might do the trick. http://www.alexander-noe.com/cdvd/bitsetting/index.eng.php

There are very few rules here but the 'Bugs' forum clearly wasn't anything like the right place for your post. I've never liked multisession personally. It makes disc duplication much more of a pain in the arse and opens you up to a whole load more 'possible' problems where drives can't read the X session properly. It's much better to stick with a clean disc and single session.

Yeah I'm sure you'll be fine. Just don't open any files called 'open me and i'll format your hdd.exe'