LIGHTNING UK!

Hmm you're actually the second person to be having that issue with the Patin Couffin drivers. Maybe I need to look into it and speak with VSO to find the cause.

All DT is doing is loading it as a standard ISO image. So it looks like burning as Mode 1, 2048 will work. The rest is down to that MacDrive program. Perhaps it's not perfect! Try burning properly using Nero and the method I mentioned earlier and then put that disc in your Mac. Use an RW or something if you're short of discs

Queuing is in for the next release. There is nothing for multiple burners though.

It can't put it where it needs to be. You need to rebuild that image. Load it (via DAEMON Tools or something) into PgcEdit and have that create a new layerbreak / iso file.

You're probably burning something that started off on a PTP type disc rather than OTP (as DVD+R DL discs are). As such, the original layer break position is probably no longer valid or usable. Update your firmware to fix the other problem with it bombing out when burning sectors spanning the layer break position. http://forum.rpc1.org/dl_firmware.php?download_id=1917

Well something must be using the drives, or something has installed a filter driver that's stopping me from getting exclusive access on them. If you've just installed Nero 7 (and that's all you've done), I would guess that's the problem. Did you put that InCD thingy on too? That normally causes this issue. Of course the obvious thing to try is to remove Nero and see if it works again. You can put it back on afterwards, but it would be nice to know what's causing the problem. I'd also visit http://www.bustrace.com/downloads/free_utilities.htm and check out their filter driver load order util. It'll tell you which drivers all your systems I/O has to go through before actually reaching the drive! Without locking the drive, any other program can send commands to it and interrupt the flow of data - leaving you with a nice coaster. Even just opening up 'My Computer' or whatever can kill it if it sends the wrong command.

Will 8 do you?! (Cus that's what I've allowed for)

Yeah they do but it's probably down to the cdrom to read them at that size. I kinda assumed going DMG to ISO would put 512 in 2048 but that's not the case. The ISOs you gave me still have data in the exact same places... ie. 4 x 512 bytes in a 'normal' 2048 byte sector. It looks to me as if the OS itself must handle sector sizes and decompressing the files on the fly (unless Macs use weird drives that support reading 512 byte sectors). Is there no virtual drive type tool you can use to mount these DMG files? Maybe this could show us if the generic cd/dvd rom driver can understand what's in the image - compressed or uncompressed. I don't think I've got much chance of uncompressing the image, and I did say I'd only think about adding support for 'Basic' images

Hmm there's hardly any difference between the two! (DMG and ISO I mean) You can't do it in ImgBurn at the moment, but have you tried burning the DMG file in Nero without any sort of conversion? (Maybe just a simple rename to *.ISO) When it asks you for the foreign file format, just select MODE 1, 2048.

When it does that, press the F8 key and then post some of the log. It'll tell you (or me) what the drive thinks it is doing. There must be some problem with finishing the disc off - and they're internal drive routines, not anything I can really help with.

You're very lucky then! No question about it, they're the worst DL discs going.

I would say pgcedit.

Sony 710 firmware: http://forum.rpc1.org/dl_firmware.php?download_id=1917 Sony 800 firmware: http://forum.rpc1.org/dl_firmware.php?download_id=2074 You're way behind on both.

Just as in DVD Decrypter, ImgBurn's default settings are/work best. Leave them as they are. FYI: 1. SAO and DAO are the same thing. DAO is the correct term for when talking about DVDs though. 2. This is how DVD Decrypter talks to your drives. The common method is to open them using the path '\\.\CdRomX' - where X is some number. That's the 'Cdrom' class. The alternative is via their drive letter using the path '\\.\X:\' where X is the drive letter. That was mainly added for linux users who use the program via Wine. Any DL burning issues people are having with ImgBurn are exactly what they'd get from any program. They use crap media with crap firmware. The best they can expect from that combo is crap burns! No software can change that. Yes of course it's better to use ImgBurn. You can see the list of changes from the changelog. Of course every version has new features and improvements over the last one.... pulling it further ahead of what it was in the good old days of DVD Decrypter.

I hope to add this one day.

No luck with that but I have found something else. Any chance you could convert those 2 files to their ISO equivalents using the hdiutil program and then post them up too? I can read the parition map ok now and locate the start of the disc image partition, next I need to know exactly what has to go into the resulting ISO file - and hence burnt to disc! If you just burn the entire thing, that's pretty simple! The DMG's you've sent me are just ISO images but have a sector size of 512 instead of 2048. So I just have to expand 512 -> 2048 (I think )

No problem. I did go over all the code to do with that stuff but couldn't find anything that was obviously at fault. Please do let me know if it happens again (not that I would expect it to!)

already running? That's the error message? I don't have such an error message coded within my program. It could be an API call's error but I'd need to know the real error before I comment on that. So basically, before I can help / fix things I need lots more details off you please. A copy of the log would be nice. Screenshot maybe?

Sorry, I looked at the files you posted and that dmg util doesnt work with them. If only I had the code to Apples hdiutil program!

Ok, maybe basic ones.... but no promises

Update your drives firmware. It's on 2.1A now I believe. http://support.necsam.com/optical/downloads/flashfirmware/

lol, mine was a reply to the - 'Is this very wrong?' bit, not 'Am I a bad person'

No, just totally pointless!

Works ok in 2003 (SP1).. I assume XP (SP2) would be the same. That's enough for me I will double check that via VMWare though and if it doesn't work, I'll have to resort to manually setting it back.

Fixed, tried and tested. I also added the 'All' / 'None' buttons for you in the File Association box