LIGHTNING UK!

Media: Maxell 12x DVD-RAM [MXL22] Burnt With: LITE-ON DVDRW LH-20A1H LL0B (SCSI)

For DVDs, yes. For CDs that would required 'RAW' mode, no. When burning CD's the program uses SAO and works with the user data areas, not the subchannel / leadin / leadout ones. So it all depends on what you're really asking about! For normal data discs, yeah it's pretty much 1:1. If you've got anything with protection on it, no it's not 1:1.

It's the size of one of the files inside the image that's important, not the size of the image itself (i.e. the total size). Where you'd normally be limited to a file Apologies if you already meant one of the files was > 4GB in size

I think they mean file size donta, not file name length Yes it supports large files if you just use UDF.

This is a recent Wine problem. They did a patch for another unicode issue a few days (weeks) ago, and now it's broken other stuff. Take a look at the bugs page at winehq and you can see their progress with the issues. http://bugs.winehq.org/show_bug.cgi?id=7512 http://bugs.winehq.org/show_bug.cgi?id=8963 http://bugs.winehq.org/show_bug.cgi?id=8624 So going by those, they've pretty much all been resolved now. Update to the latest version of Wine perhaps?

Build mode was designed to work form an existing folder layout / hdd structure. If I ever change that, it will of course become much more flexible.

Try Nero Recode, it's basically an updated version of DVDShrink anyway.

If it's a DVD ROM, Write mode wouldn't find it as it only shows burners. Look in the log window and ImgBurn will tell you what it found as part of the device scan. Copy + paste the info here if you like.

I know the calls used to disable the screensaver etc but they're not used/called within ImgBurn. As such I've no idea where this issue is coming from I'm afraid!

ImgBurn doesn't perform any sort of compression/conversion, it's purely a burning program and whatever you tell it to burn will be burnt 'as-is'. Basically, as with everything in ImgBurn, the default settings work best so just leave them all alone! There is another guide that explains the build mode ones in a little more detail. You can always use Google to figure out what certain technical terms might mean if you've not seen them before.

As the 'browse' box is a standard windows API call, any program that uses it should be the same (speed wise). Do remember that the OS will probably cache the info too, so it may only be slow the first time you open it - as Windows may then be working out the details of the files within that folder - this may include playback time and resolution if the folder contains AVI files etc.

That hotfix only mentions UDF v2.00. ImgBurn uses v1.02 - as is the standard on DVD Video discs. So I'm guessing it doesn't really apply.

If it supports the LG commands, it'll already work. If it doesn't, there's no chance in me making it I'm afraid.

DVD Maker would have converted your files to a DVD Video format, that's why it takes so long. ImgBurn is burning the files 'as-is', so they'll NOT be in DVD Video format. >> It may also be a media issue whereby the player can't read the discs full stop. I mean the drive can't read the discs - full stop (a.k.a. end of story).

Sounds as though a simple 'Verify' would have spotted this issue right from the start. That is after all the whole point of it! When some drives have issues writing on some discs, the 'Write Type' can actually make a difference (it shouldn't, but sometimes it does). If you really must stick with using those discs rather than some decent Verbatim / Taiyo Yuden ones, switch it to 'Incremental' rather than 'DAO' and then try it again.

I thought someone was gonna buy one and set me up with remote access to the PC? They're not available here in the UK and I have no use for one besides just 'getting it working'.

Click the 'Tools' menu and goto the 'Filter Drivers' option. Click the 'Clipboard' button and then 'Paste' into your next post. Maybe you've got some dodgy filter drivers installed that shouldn't be on there. ASPI is not used/required. I don't even have a system wide ASPI manager on my PC these days. Could you also please copy + paste the latest log of you burning something. You might also like to try removing that dvdrom from the 2nd ide channel so it's just the Pioneer 111 on it - configured (via the jumpers) as 'Master' and make sure it's on the opposite end of the cable to the motherboard (i.e. so there's a spare block in the middle).

This is covered in the program description on the main website. But even then, if you think about the program in terms of ISO (disc) images, it's pretty simple to work out what each mode does! 'Write' - It writes a disc image to a blank disc. 'Read' - It reads a disc to a disc image. 'Verify' - It compares a disc to a disc image. 'Build' - It creates a disc image (ready for burning or for burning on-the-fly) from a bunch of random files on your hdd. 'Discovery' - It basically does a (destructive) dummy run on burning a disc to it's full capacity. This is useful for testing when used in combination with the varios PIPO scanning programs to test the quality of the burn.

Are you in 'Read' mode, trying to read a disc to an image file that you've called 'D:\DVD_VIDEO.ISO' ? It looks like you don't have permission to modify that folder (create files in it) - i.e. the 'D:\' drive, or there's already a 'DVD_VIDEO.ISO' file there and you don't have permission to modify / create / delete it. Even if you are in 'Write' mode, you still don't have permission (this is a system thing, part of the NTFS file system) to access it.

Well the log shows you're using all 3 filesystems so the player should hopefully at least have something it can work with! There's not really any reason for it to be failing, or at least none that I can think of. You could try burning to a rewritable, going through the various different options for filesystems - i.e. Just ISO9660, then ISO9660 + Joliet etc etc. It may also be a media issue whereby the player can't read the discs full stop. What exactly does the player say when you put one of the burnt discs in it? Does it just give you an error code or does it show you files (but you can't then play them) ?

Yup, Verbatim discs are the way forwards! You're getting bad burns on those RITEK ones - so bad in fact that the burner itself cannot even read them back!

If when it cycles the tray, the drive continues to say it's not ready, it'll just sit there until it is - polling it every second and asking 'are you read yet?'. It's VERY odd that you could (if I understand what you're saying correctly) cancel it and the drive magically starts to recognise the disc - without you having to eject it again or anything. If that's the case, there must be another program or driver on your system that's messing around with the drive's return codes and is feeding ImgBurn false information.

If the little GI file wouldn't load straight off, it must be in a format that ImgBurn doesn't currently recognise. If you could upload the file or email it to me, I'll examine it and see if changes I've already made for the next version will also mean this file is burnable.

This is a format limitation, not a program one. The DVD + (plus) format doesn't support 'test mode'. BenQ drives can somehow get around that, and ImgBurn already supports that feature anyway.

It's odd that your HDD's think they're running UDMA 5 if you're only on 40 wire IDE cables! The limit for those is UDMA-2. The Pioneer should be on UDMA-4, hence it requires an 80 wire cable too. If you use the right cables (80 wire ones), all drives should be running UDMA 4 or 5. If things still fail after that, clean the drive and try to find some other blanks. Verbatim +R discs are better than the -R ones. For -R, go with Taiyo Yuden (TYG02 are the best).