LIGHTNING UK!

Have you only tried 1x (or 6x which is the drive's lowest supported write speed) ? Give it a go at 8x, 12x and 16x. You might find you have more luck. For the disc saying it's incomplete, try using the Tools -> Drive -> Close (Track/Session/Disc) options. AnyDVD doesn't conflict with ImgBurn, it's just that it can modify the data read from the drive during a verify (after a burn) and make 'miscompare' errors pop up.

So you're already added 'SONY DVD RW DRU-830A' to the Samsung list? Ok so now check the commands are actually working - can you change the booktype manually and have it say 'success' ? (You'll need to have the blank in the drive obviously) and you've got the 'automatic change booktype' option enabled? and your drive burns + verifies the discs ok without any retries / errors? (a log would be nice!)

Unless you're setting the booktype option before every burn, it's not going to be automatic with that drive. You need to add it to the 'Samsung' list on the 'Advanced' page within the booktype options screen.

See, I knew it would work for me! http://forum.imgburn.com/index.php?s=&...ost&p=54612

TSSTcorp CDDVDW SH-S203B SB01 (ATA) Media Information: Results: I 22:23:23 ImgBurn Version 2.3.2.13 Beta started! I 22:23:23 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 2) I 22:23:23 Total Physical Memory: 3,406,220 KB - Available: 2,154,972 KB I 22:23:23 Initialising SPTI... I 22:23:23 Searching for SCSI / ATAPI devices... I 22:23:25 Found 3 DVD-ROMs, 1 DVD±RW and 5 DVD±RW/RAMs! I 22:24:02 Operation Started! I 22:24:02 Source File: -==/\/[DISCOVERY IMAGE]\/\==- I 22:24:02 Source File Sectors: 2,297,888 (MODE1/2048) I 22:24:02 Source File Size: 4,706,074,624 bytes I 22:24:02 Source File Volume Identifier: DISCOVERY_IMAGE I 22:24:02 Source File File System(s): None I 22:24:02 Destination Device: [4:0:0] TSSTcorp CDDVDW SH-S203B SB01 (M:) (ATA) I 22:24:02 Destination Media Type: DVD-R (Disc ID: TTH02) (Speeds: 4x, 6x, 8x, 12x, 16x) I 22:24:02 Destination Media Sectors: 2,297,888 I 22:24:02 Write Mode: DVD I 22:24:02 Write Type: DAO I 22:24:02 Write Speed: MAX I 22:24:02 Link Size: Auto I 22:24:02 Test Mode: No I 22:24:02 BURN-Proof: Enabled I 22:24:16 Filling Buffer... (40 MB) I 22:24:16 Writing LeadIn... I 22:24:32 Writing Session 1 of 1... (1 Track, LBA: 0 - 2297887) I 22:24:32 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2297887) I 22:29:34 Synchronising Cache... I 22:29:45 Exporting Graph Data... I 22:29:45 Graph Data File: C:\IBG\TSSTcorp_CDDVDW_SH-S203B_SB01_08-OCTOBER-2007_22-24_TTH02_MAX.ibg I 22:29:45 Export Successfully Completed! I 22:29:45 Operation Successfully Completed! - Duration: 00:05:42 I 22:29:45 Average Write Rate: 15,217 KB/s (11.0x) - Maximum Write Rate: 22,317 KB/s (16.1x) I 22:29:45 Cycling Tray before Verify... W 22:29:51 Waiting for device to become ready... I 22:30:04 Device Ready! I 22:30:04 Operation Started! I 22:30:04 Source Device: [4:0:0] TSSTcorp CDDVDW SH-S203B SB01 (M:) (ATA) I 22:30:04 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: TTH02) (Speeds: 4x, 6x, 8x, 12x, 16x) I 22:30:04 Image File: -==/\/[DISCOVERY IMAGE]\/\==- I 22:30:04 Image File Sectors: 2,297,888 (MODE1/2048) I 22:30:04 Image File Size: 4,706,074,624 bytes I 22:30:04 Image File Volume Identifier: DISCOVERY_IMAGE I 22:30:04 Image File File System(s): None I 22:30:04 Read Speed (Data/Audio): MAX / MAX I 22:30:04 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2297887) I 22:30:04 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2297887) I 22:36:16 Exporting Graph Data... I 22:36:16 Graph Data File: C:\IBG\TSSTcorp_CDDVDW_SH-S203B_SB01_08-OCTOBER-2007_22-24_TTH02_MAX.ibg I 22:36:16 Export Successfully Completed! I 22:36:16 Operation Successfully Completed! - Duration: 00:06:11 I 22:36:16 Average Verify Rate: 12,387 KB/s (8.9x) - Maximum Verify Rate: 22,545 KB/s (16.3x) Scans: BENQ DVD LS DW1655 BCIB LITE-ON DVDRW LH-20A1H LL0C

Seeing as how it errored out the split second it started to write, I'd have to guess the drive has issues with that media code. I'd dig a disc using that MID out myself, but knowing my luck it would work!

You're just about the only person to have ever asked the question, so it's hardly worthy of going in the FAQ! You're also probably 1 in 10000 to actually use packet writing software - everyone knows it's very closely linked to the Devil and to avoid it like the plague.

You're using (low quality) 16x media in a drive that's almost as old as I am. Get yourself some decent 8x stuff (Verbatim or Taiyo Yuden) and you might have more luck. But in all seriousness, now would be a good time to start thinking about buying a new drive.

Well then hopefully the 8gb and 16gb ones won't be so bad If you need more than that on removable storage, you should get an external hdd!

That's where the registry entry comes in! Samsung drives are blocked by default and cannot be used. Unblock it and they should work.

Back then, ImgBurn probably didn't have 'Read' mode. Times change. I'll eventually get around to adding a 'Copy' mode but it's not a high priority as you can achieve the same thing in Read/Write modes - all be it a bit slower and with a couple more clicks.

If you want that kind of functionality might I suggest you buy yourself a USB Memory Pen/Stick thingy. They're far better suited to the task. Use CD/DVD's when you know you've got everything you want/need on the disc - i.e. to archive it.

Ok, that proves it then. If the 'automatic change booktype' option is enabled, your SATA controller / drivers are blocking the actual command and stopping it working.

lol yeah it would help if the log actually showed you burning something! All we've got there is a log of you making an ISO. When you do the burn, make sure you also have it verify afterwards (tick the 'Verify' box on the main screen).

If you're trying to burn a DVD, forget about it, you don't have a DVD burner. Your drive only READs DVD's (and writes CD).

It should be automatic on the samsung drives if you're using the latest ImgBurn. Just leave the settings alone and let ImgBurn do it's thing. Of course if you've disabled the automatic booktype option in the settings then that there would be your problem. As for the logs, look in the program's Help menu.

lol if you managed to enable it, I'd have expected you to remember how you did it! (i.e. by press F8 as blu said or by checking the box in the settings on the 'I/O' tab) Also, the debug mode doesn't help / do anything towards solving the drive locking issue - the FAQ deals with that issue and it certainly doesn't mention it.

Yeah these are drive / media / firmware combo issues. If your drive can't initialise the disc properly, you're stuck - this is where a firmware update may come in handy. Failing that, you need to get some different discs that the drive DOES like. Until they like eachother (drive -> media, at least a tiny bit!), no software can issue any commands to the drive related to accessing the media - i.e. reading from it or writing to it.

Ok so I've had a little play around with this now to figure out how much I'd have to change to implement *something* that could be useful. I've determined it's not possible (without load of hassle) to have total control over where the files/directories are placed (i.e. copied exactly from the order of the 'source' box), but what I can do is order them on file basis and then directory basis as taken from the 'source' box. i.e. I cannot support ordering like this: File 1 File 2 Dir 1 File 3 Dir 2 File 4 Dir 3 Dir 4 etc... I can support ordering like this: File 1 File 2 File 3 File 4 Dir 1 Dir 2 Dir 3 Dir 4 That is to say, the files in the root folder will always come first on the disc, but you can have them in the order they're specified in the 'source' box and the same goes for the folders. I can also (well, have actually) make it so it will traverse the directory structure like this: root dir 1 dir 1\dir 2 dir 1\dir 2\dir 3 dir 4 dir 4\dir 5 dir 4\dir 5\dir 6 instead of the current way: root dir 1 dir 4 dir 1\dir 2 dir 4\dir 5 dir 1\dir 2\dir 3 dir 4\dir 5\dir 6 If you look though, the latter (current) method is the same used on the real Windows CDs (made by Microsoft's CD Image program). So anyway, that would mean if you stuck your ghost image in a folder called 'z', it would come after everything - assuming there wasn't then a zz folder Please let me know if this would actually be of any use to you before I go wasting my time on it!

Not really these days, no. There's a limit (lower limit) beyond which you'll see no benefit and perhaps even start getting lower quality burns as the speeds won't be so finely tuned in the firmware. I would say this is particularly true with newer drives that are all about 'speed'!

8x is fine on TYGO2, for TYG03 I guess you should use 8x, 12x (16x is probably still ok though). For the MCC dye 16x Verbatims, again, 8x or 12x (16x is probably still ok though). As for the Verbatim DL's (MKM-001-00), normally 2.4x is what I'd recommend but my Samsung S203B gives a much better burn at 4x than it does at 2.4x. I guess what you need to do is burn a few 'dummy' discs (i.e. in discovery mode) at the different speeds and then scan them (using CD-DVD Speed etc) to get the PI/PO error levels. Every drive is different so you need to figure out what yours likes best. Of course don't forget to update the firmware on the drive too.

If you're even getting to the stage where it gives you sense area data from a command that's errored out, ASPI must already be ok.

You don't want 'Create Disc', you want 'Disc Quality'.

Ah ok so now you're saying it won't load if it's not below 4GB. From a technical point of view, that makes more sense than you saying it won't load if it's on the 2nd layer.

If you can find a tool to extract the data bit, you could just add it on the end of the cue sheet. So then you'd have a cue + wav + bin. ImgBurn would burn that just fine.