LIGHTNING UK!

Might aswell update this thread even though I replied via email.... It's a CD image and it would appear that by definition, they don't ever just contain 1 track - hence the value I check is always more than 1. This has now been fixed. That doesn't mean I recommend using ImgBurn to burn CD images when they're in MDS/MDF format. ImgBurn doesn't take into account any of the 'special' bits included in the image file - basically, it doesn't burn in 'RAW' mode.

Is it media that your drive actually supports? It certainly doesn't look like it. Try the 1.02 firmware too.

As the Image has already been built, ImgBurn can't do anything about the physical location of the files within it. It would indeed need to shift them about in order to make a cell line up nicely. The recommended way of building DL images is via PgcEdit. You can play each cell that 'could' be a potential layer break position. It'll then build an ISO with the correct padding so your chosen one works. So basically, forget messing around with those other tools for the building part and just get PgcEdit to do it.

It can't have - or at least not according to the MDS file it doesn't. If you're really really really sure it's only a single track one, post the mds file up here (or email it to support) and I'll take a look at it.

wow, that's a shocking burn at 8x! No wonder you burn at 4x! I'm sure that can't be right though... either there's a bug in the firmware for that media or BenQ really need to get their arse in gear and support them properly I only wish I had some TY +R 8x discs to test with so we could compare I have some 16x DVD+R ones (Plextor branded) and I also have 8x & 16x real TY DVD-Rs. No 8x DVD+Rs though.

Any chance you could do a PIPO scan of a 4x burn and an 8x burn? I'd like to see the difference with that media. As you may have seen in our media forum, the TY discs burnt quite nicely at 8x in the 1640. I see no reason why you'd need to slow it down to get anything better. Do keep an eye on the buffers though. The 'Buffer' should always be on 100%. With BenQ drives, the 'Device Buffer' fluctuates around 80% - 100%.

Just click on the little folder icon to the right of where it says 'Please select a file...'.

I don't think that's the problem here. It might be that the drive just doesn't think the burn quality is quite what it should be and so is limiting the speed. Is there any reason you're slowing those discs down to 4x? TY media is normally burnt faster than it's recommended speed, not slower! The drives firmware will probably be optimised to burn at 8x. The drive is in total control of the speed - unless of course the buffers are always on 0% (where what dirio49 said above may apply).

Everything you've shown there looks perfectly fine. Why don't you do a Verify within ImgBurn (just check the box before you burn) and then do a PIPO scan in DVDInfoPro.

I just got the ?18 usb2/firewire one from SVP! Maybe you could bodge swapping the little board in them over into your nice blue lit case? They use the prolific chipset. Oh and Nero ASPI is just a wrapper for SPTI under NT based OS's. You'd need Adaptecs one to have any hope of getting around that timeout issue. Your Pioneer 110 needs a firmware update btw

You could only have found out about these settings at cdfreaks or something and there's already a post within that thread showing ImgBurn already has them Well, I say 'already'..... the unreleased 1.2.1.0 has them.

You're then limited to reading in the exact sector sizes of the hdd (from what the MSDN stuff says). Due to some weirdo image files that's not really an option. It was fine on 64k before so I'll just put it back to that.

Sorry, DVD Decrypter is finished, end of story.

ImgBurn doesn't care about the content of the ISO, so yes, it'll handle them ok.

You mean within the 'Open File' dialog box? It just defaults to putting name of the last file you burnt in the 'name' area. It's no big deal and it doesn't mean anything. If you REALLY can't live with it being there you'll have to remove the ISOWRITE_MRUFile entry in the registry within the ImgBurn key.

jmet, I expect that delay is due to the disc spinning up or something. The file transfer rate problem only comes into play during the actual burn...not before it, after it etc. Those other functions do things differently. dirio49, Nah, it'll be fixed back on 64k

No offence but you're better off asking the 'stripping' question in the PgcEdit forum over at doom9.org. AFAIK, when PgcEdit goes to make the ISO it'll give you a list of potential layerbreak positions for you to choose from. It'll then sort out the layerbreak flags. If you want to remove them manually to start with, that's up to you.

Jason, Your sales@ email box is either full up again or STILL full. Please empty it / expand the box size or change your email address on this forum to one that doesn't get all your spam! Cheers

You'd have to extract the contents of each ISO, merge the actual files in a different program and then recreate the image from that new set of files.

When you run the official pioneer firmware thing you downloaded, it should have extracted it to C:\DVR107D\FW122 When you bring up the command prompt, you should already be 'in' the C: drive so you type that command exactly as I wrote it. CD \DVR107D\FW122 All that'll do is change the 'working' directory to C:\DVR107D\FW122 'CD' standing for Change Directory

Well, besides just buying a new drive (which you'd probably have to also update anyway), you have 2 choices. 1. Use DVRFlash 2. Install Adaptec ASPI, and switch the DVRFlash.exe program into Win 9x Compatibility mode.

PgcEdit will take care of it all.

Take a quick look in the BUGS forum. It's a known problem due to me using UPX on the exe.

It's a windows caching problem. Seems windows doesn't cache me reading in the 4gb file if I read in 64k chunks. As I switched to 256k (to hopefully speed things up!), it now caches everything and eats all your memory. This was reported lastweek sometime and fixed almost immediately. Get 1.2.1.0 when I release it and you'll be fine. Cheers for reporting it though.

Ok, fixed it now. Phew, you reported that just in time to make 1.2.1.0 !