LIGHTNING UK!

Sense area data is clearly defined in the specs and it would be a bit weird if certain controllers / drivers changed the formatting - it would screw up all the programs that expect it in the documented format (like ImgBurn) ! Obviously you can't just ignore errors either, programs have to respond to them in certain ways as they don't always mean 'fatal error'. If the errors are just plain wrong then you're a bit stuck! Get the drive off that controller and I'm sure everything will start working just fine. That said, I'm semi interested to try and find such a controller (as a PCI card) so I can see if they all do the same thing. Is there any chance you could get the exact model number of it? The one in device manager might do if there's no standalone chip on the motherboard (I won't be buying a Via motherboard any time soon - yuk!)

Open the graph data file in DVDInfoPro so we can see the write/verify speed lines.

Damn, I think I got my CRC calculation wrong. I was doing it byte by byte but I think I need to do it dword (4 bytes) by dword. I might get you to test the change if that's ok?

FYI, I've fixed this now but you'll have to wait for the next release, sorry!

Ok, next I need you to right click on the isolinux.bin file within the ImgBurn built ISO file (We're still using IsoBuster for this) and select 'Sector View'. Post up a screenshot of that window.

Well we don't talk 'copy protection' on this forum so that never even entered my head

The log doesn't show any problem. If you're getting an error box or something pop up, please get a screenshot of it so we can see what you're seeing.

Ah ok, I see the problem. When you save the MDS to the same folder as the files the path and file name gets stripped regardless (it's done outside of the code for that 'Create DVD MDS File' window in a generic function that creates all the MDS files). What you need to do (until I fix it) is save the MDS somewhere else other than in the same folder as the image data. That way the full path and file name get preserved as per the 'Preserve Full Pathnames' option.

Sorry, I probably wasn't clear. Within IsoBuster, click on the 'Bootable Disc' entry on the left and see what the LBA is for the BootImage in the right pane. Then compare that to the LBA of the ISOLINUX\ISOLINUX.BIN file in that same image via the 'ISO' or '>>>' (Joliet) entry on the left. Different LBA's between images is perfectly fine and to be expected - so don't compare different images! If ImgBurn has patched the file at all, both the bootimage and the isolinux.bin with have the same LBA. If they don't, it hasn't Basically, when it patches the file, the one you specify for the bootimage is ignored because it really just points to a proper file in the file system.

Stranger and stranger... This is the error I get upon issuing a certain command with a DVD-RW disc in my Samsung S203B I 20:21:36 [5:0:0] TSSTcorp CDDVDW SH-S203B SB04 (O:) (SCSI) I 20:21:36 CDB: AD 00 00 00 00 00 00 11 08 04 00 00 I 20:21:36 CDB Interpretation: Read Disc Structure - ADIP Information E 20:21:36 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00 00 00 00 00 E 20:21:36 SENSE Interpretation: Invalid Field in CDB and this is what you get from your S203N. I 19:10:05 [6:1:0] TSSTcorp CDDVDW SH-S203N SB02 (L:) (RAID) I 19:10:05 CDB: AD 00 00 00 00 00 00 11 08 04 00 00 I 19:10:05 CDB Interpretation: Read Disc Structure - ADIP Information E 19:10:05 SENSE: F0 05 00 00 00 00 00 0B 08 E2 74 87 00 37 00 00 00 37 00 00 01 00 80 84 E 19:10:05 SENSE Interpretation: Unknown (0x00, 0x37) Remember that these drives are or should be almost identical. The entire sense area structure returned to the program by your machine is full of...erm... crap!

There's nothing I can do with this. If I submit a command to the drive and it comes back saying it failed, all I can do is display the error code it returned - that's what the 'Sense Area' stuff is. It's 110% out of my hands. They're all coming back as 'unknown' (there's a lookup table within the program to convert the ASC / ASCQ numbers (bytes 12 and 13 within the sense area data) to something in plain english) because the numbers are not specific within the MMC commands. That either means the manufacturer has implemented a few extra ones or the errors are coming from some other part of your system. As has been said time and time again in forums all over the internet, optical drives really don't like running under anything other than the standard 'ATA' mode - even 'AHCI' has its fair share of problems. Your drive is connect to a controller running with RAID bios and a RAID driver, hence why it has 'RAID' stuck on the end of the device identifier.

How much memory does your machine have available when ImgBurn starts (look in the log window). The more files you have to open, the more overhead there is - so it's easier to burn 1 x 1GB file than 10 x 100MB files. Also you have to take into account antivirus kicking in and checking the files are not infected etc - again, this is all part of the 'overhead'.

Yeah but 99% of the time you'll have an ISO or an IMG file (unless you're using weird software) - and it supports those just fine.

I like adding options to ImgBurn that give it the ability to mimic everything that any other program could use by default. So if someone says ImgBurn doesn't work and X does, there are ways to make ImgBurn work for them.

Doesn't that just disable themes or something? You could do that via the compatibility options when you right click the program exe.

The program would probably now use *.i00, *.i01 etc to make it easier to rename the files without then having to hex edit the mds file. Whatever the mds file is called (minus the file extension), that's what replaces the '*' when parsing the mds to load the actual data files. The ansi/unicode choices are totally unrelated.

Put it this way... if it wasn't ok to do that, the program wouldn't let you.

Virtual Clone Drive is free too.

If it's a DVD image then it's probably designed to go on a DVD. In any case, ImgBurn wouldn't be able to help you here. Can't you just burn it to a DVD?

Slow the burn down to 8x or 12x and try again. They're probably not playing because the drive isn't producing a very good burn. You could also look into bitsetting options on the NEC drives so that it'll booktype DVD+R to DVD-ROM, that makes them more compatible with players.

Have you been unlucky and got a pack made in India or something? Other than that, yes there's always a chance your drive is failing. You could try running a cleaning disc through it but those things can almost be as expensive as buying a new drive!

Can't you just download IsoBuster? It's free. Patching doesn't change the size of the file so you can go by size alone.

*cough* yeah that too

Uninstall the DC Bass one first or you'll never know which is being used Also, the DC Bass one takes over playing lots of formats by default, not just Flac. That might not be the behaviour you really want.

Oops, didn't see your edit madFlac works fine now in 2.4.2.0 and all the problems with the FLAC files not decoding to be 100% like the original WAV files have been sorted. madFlac is supposed to be more versatile because it's based on a different FLAC decoding library (or something like that!).